Receipt Scanning That Survives a Real Expense Report
Receipts are the hardest easy document. They're small, they're everywhere, and they arrive as crumpled paper, dim phone photos, and PDF confirmations from a dozen different vendors. Each one carries only a handful of values — but get any of them wrong and an expense report bounces at reconciliation or, worse, at audit. The goal isn't just to read a receipt; it's to read it in a way that holds up when someone checks it three months later.
The fields that actually matter
Most receipt data is noise. For expense reporting you need a specific, small set of fields — and each one has a failure mode worth watching:
| Field | Why it matters | Common extraction error |
|---|---|---|
| Merchant | Categorizes the expense | Reads the payment processor, not the store |
| Date | Determines the reporting period | Confuses DD/MM and MM/DD |
| Subtotal | Feeds tax calculations | Grabs a line item instead |
| Tax | Often reclaimable | Missed entirely on receipts that bury it |
| Total | The reimbursable amount | Picks the pre-tip total on restaurant receipts |
| Currency | Critical for travel | Assumed, never captured |
If your extraction reliably nails those six, the rest of the receipt is decoration.
A pre-submit checklist
Before a batch of receipts goes into an expense report, run each extracted result against a quick gate:
- Does the total equal subtotal plus tax (plus tip, if present)? A failed sum is the single best signal that a field was misread.
- Is the date inside the reporting period? A date outside the month usually means a format swap.
- Is the currency explicit? Never let it default — travel expenses live and die on this.
- Is the merchant a real store, not a processor? "SQ *" prefixes and gateway names are a tell.
- Are low-confidence fields reviewed? Trust the tool's own uncertainty flags and check those first.
This checklist is cheap to run and catches the errors that auditors catch — before they do.
Batch a whole month at once
The real time saver isn't scanning one receipt faster; it's processing a month of them in one sitting. Collect the images and PDFs, run them through the upload page as a batch, and review the flagged results together instead of one at a time. Reviewing in a batch also surfaces patterns — if the same merchant always misreads, you learn to spot-check it.
For anyone doing this at volume, the pricing page is organized around pages per month, which maps cleanly onto "how many receipts does my team file." Sizing by volume beats guessing, and it means a heavy travel month and a quiet one can use different plans.
Key takeaways
- Only six receipt fields matter for expenses — nail those and ignore the rest.
- The subtotal-plus-tax-equals-total check catches most misreads for free.
- Always capture currency explicitly; never let it default.
- Batch a month of receipts and review the flagged ones together.