By the Scan2Sheet Team
Your bookkeeping can balance perfectly while you quietly pay part of your client's bill.
Every receipt is recorded. The bank reconciles. The client pays the final invoice. Nothing appears overdue, because the expense you forgot to rebill never became an invoice line.
The cost itself is visible in your accounts. The missing recovery is not. A spending report can show transport of 68.00; it cannot tell you that a particular client agreed to cover it unless you recorded that obligation somewhere. An invoice report only knows about charges you actually raised.
That is the trap with rebillable client expenses: an absence stays invisible until you build something that expects the missing item to exist.
Maya's finished project has an unfinished expense trail
Maya is a freelance brand designer. On 4 May, she starts a packaging launch project for Alder Studio, including a small product shoot on 12 May. Her design fee is fixed, with certain external costs charged separately.
The agreement allows print production at cost plus 10%, local travel at cost, and shoot props up to 150.00. Anything above that prop allowance needs written approval. Her normal software subscriptions are included in her fee.
All figures below use the same billing currency. Taxes on Maya's client invoices are excluded from the worked calculations; the eligible cost basis has already been established for this example.
By 18 May, her records contain these purchases:
| Cost ID | Date | Merchant | Purchase | Recorded cost |
|---|---|---|---|---|
| C-101 | 6 May | Northline Print | Packaging mock-ups | 240.00 |
| C-102 | 11 May | CityLink Rail | Return ticket for shoot | 68.00 |
| C-103 | 12 May | Frame & Field | Shoot props | 180.00 |
| C-104 | 14 May | LayoutCloud | Monthly subscription | 24.00 |
| Total | 512.00 |
Maya prepares her invoice from the project folder. The printer's invoice is there, alongside the client's prop approval. She adds 264.00 for printing and 150.00 for props.
The rail ticket is saved in her expense records, not the project folder. She bought it the evening before the shoot, so a quick search for receipts dated 12 May does not find it. Her invoice goes out with 414.00 in expense charges.
Nothing is numerically wrong. One charge simply never entered the calculation.
Capture the right to rebill, not just the purchase
Maya's repair starts when she captures a receipt, not when she writes the next invoice.
She uses Scan2Sheet to extract receipt data into her own Google Sheet, with automatic categorization and a cloud-stored receipt image linked from each row. She checks the extracted merchant, date, and amount, then maintains her own project and billing fields beside that data.
The important distinction is that “Travel” describes the purchase. It does not say who should ultimately bear it.
Her custom fields are:
- Project:
ALD-LAUNCH, so the cost follows this engagement rather than merely the client. - Rebillable:
Yes,No, orReview. - Eligible cost: the portion allowed under the agreement.
- Pricing rule: at cost, a stated markup, or another agreed basis.
- Approval reference: a contract clause, purchase order, or saved client message.
- Expected charge, invoiced amount, and invoice reference: the recovery trail.
A blank rebillable field is not treated as No. It is unfinished work. Maya filters for blanks and Review before each billing run, because otherwise “I haven't decided” quietly becomes “I won't charge.”
On 11 May, the rail ticket would receive ALD-LAUNCH, Yes, eligible cost 68.00, and pricing rule At cost. Its purchase date stays 11 May; a note records travel for the 12 May shoot. Changing the receipt date to match the project activity would damage the record rather than fix the search.
Automatic expense summaries remain useful for checking spending totals. They do not replace this billing decision: no merchant name or expense category can establish what Maya's client agreed to pay.
A markup is not permission to recover the whole receipt
The printer and prop purchases demonstrate two different calculations.
Northline Print's 240.00 invoice is entirely eligible. Under the agreed 10% markup:
240.00 × 1.10 = 264.00 expected client charge.
That is a markup on cost, not a 10% margin. Dividing by 0.90 would produce 266.67, which is a different price and not what Maya agreed.
The props work differently. Maya spent 180.00, but the client authorized only 150.00. She chose an extra backdrop without asking first. The recorded business cost remains 180.00; the eligible amount is 150.00, and the remaining 30.00 is absorbed by Maya.
She does not overwrite the receipt total with the recoverable amount. That would make the expense record disagree with the payment and conceal the overrun.
LayoutCloud provides the contrasting case: a real business expense with no separate recovery entitlement. Its eligible cost is zero because the subscription is included in her fee. Attaching it to the project does not turn it into a reimbursable purchase.
Her billing view now looks like this:
| Cost ID | Rebillable | Eligible cost | Pricing rule | Expected charge | Decision evidence |
|---|---|---|---|---|---|
| C-101 | Yes | 240.00 | Cost + 10% | 264.00 | Agreement §4 |
| C-102 | Yes | 68.00 | At cost | 68.00 | Agreement §4 |
| C-103 | Yes | 150.00 | At cost, capped | 150.00 | Client email, 5 May |
| C-104 | No | 0.00 | Included in fee | 0.00 | Agreement §2 |
| Total | 458.00 | 482.00 |
For foreign-currency purchases, Maya would also retain the original amount and currency, conversion rate and date, and the contractual conversion basis. A card-settled amount and a published exchange rate can produce different charges. She would not automatically pass through card fees unless the agreement allowed them.
“At cost” also needs a defined tax basis. Whether recoverable purchase tax belongs in that basis, and how tax applies to the onward charge, depends on the arrangement and jurisdiction. Check the relevant tax authority's guidance and a qualified local adviser; a receipt total alone does not settle either question.
The receipt proves a purchase, not client approval
Before invoicing, Maya assembles evidence for the client's accounts-payable team. Their onboarding instructions require itemized receipts, the project reference, and a short explanation for travel. The printer charge also needs the agreed markup identified.
Her travel explanation is specific: “Return rail ticket purchased 11 May for Alder packaging shoot, 12 May.” That resolves the date mismatch without asking the client to infer it.
Client requirements vary, but commonly include the merchant, transaction date, itemized goods or services, amount and currency, and the business purpose. Some also request proof of payment or prior approval above a threshold. A bank transaction may prove payment while providing none of the itemization needed to assess eligibility.
For Frame & Field, the full receipt matters: the last item and total sit below the first screenful. Multi-page long-receipt capture preserves that evidence; Maya checks that every section is legible before discarding any paper under her applicable retention rules.
If a receipt is missing, she requests a replacement from the merchant and marks the charge Evidence pending. She does not quietly remove it from expected recovery. If the client accepts alternative evidence, she saves that acceptance too.
The internal receipt link is not automatically a client-ready evidence pack. Maya tests access from outside her account and shares only the relevant documents, not her whole expense sheet. Where a receipt includes unrelated purchases, she retains the complete original privately and supplies an appropriately redacted copy if acceptable to the client.
Reconcile expected charges against issued invoice lines
On 19 May, before closing the project, Maya compares the billing view with issued invoice INV-052.
| Cost ID | Expected charge | Net charge invoiced | Still to invoice |
|---|---|---|---|
| C-101 | 264.00 | 264.00 | 0.00 |
| C-102 | 68.00 | 0.00 | 68.00 |
| C-103 | 150.00 | 150.00 | 0.00 |
| Total | 482.00 | 414.00 | 68.00 |
The control is simple:
Expected charge − net expense charges on issued invoices = uninvoiced balance.
“Net” here means after invoice credits and before any tax added to Maya's charges. The design fee is excluded. Comparing total project spending with total project revenue would bury the discrepancy.
Maya records an invoice number and line reference against each billed cost. If several receipts become one invoice line, a supporting schedule maps their cost IDs to that line. If one cost is billed in installments, she keeps separate invoice allocations rather than squeezing several amounts into a note.
A draft invoice does not count as issued. Nor does a checkbox marked Billed substitute for an amount: it cannot reveal a partially billed cost.
Payment status stays separate. Once the 68.00 is invoiced, collection belongs in receivables. Until then, it belongs in the recovery queue. Mixing those stages makes a paid invoice look like proof that every expense was charged.
Late receipts and credits keep the project open
Maya finds a 14.00 station-parking receipt on 20 May, paid from her personal card. It is eligible travel for the shoot but never appeared in her business bank feed.
She records the business expense with the appropriate owner-funded payment treatment, adds it to ALD-LAUNCH, and sends a supplemental invoice for 68.00 + 14.00 = 82.00, with evidence and an explanation. Had the contract prohibited supplemental invoices after final acceptance, she would have needed to resolve that restriction rather than assume late billing was allowed.
Three other exceptions need deliberate handling:
- Duplicate capture: an emailed printer invoice and a photographed copy may describe the same purchase. Review duplicate warnings against merchant, amount, document number, and payment; two genuine identical purchases should not be merged merely because their totals match.
- Shared purchase: if a receipt covers two clients, allocate the eligible portions and retain the allocation basis. Link both allocations to the original document without counting its full amount twice.
- Refund after billing: if Northline later refunds 40.00, record a linked negative cost. Under Maya's cost-plus agreement, the corresponding client credit is 44.00, including reversal of the markup on that portion. Handle the invoice credit and any tax adjustment through the applicable local process.
On 22 May, Maya checks supplier emails, card activity, and outstanding approvals before closing the expense review. Every expected charge now has an issued invoice allocation or an explicit, evidenced decision not to recover it. Any disputed or waived amount retains its reason and date; it is not erased to force the balance to zero.
That leaves a useful exception queue for the next billing run: unresolved eligibility, missing evidence, unbilled balances, and refunds awaiting client credits. Unlike a folder of receipts, it tells Maya what still needs to happen.
Use Scan2Sheet to get receipt data and linked images into your Google Sheet, then add the billing fields that connect each recoverable cost to an issued invoice.