Receipt Capture: Killing the Shoebox for Good

The shoebox never actually goes away. It changes form. It becomes a Slack thread of blurry photos, a shared drive folder named receipts_final_v2, an expense report someone reconstructs from memory in the last week of the quarter.

Receipt capture is one of the easiest things to automate well and one of the most commonly half-automated. The hard part isn't the OCR — that was solved years ago. The hard part is matching, and getting humans to stop being the transport layer.

Capture where the money is actually spent

• Email forwarding. Every serious tool gives you an address. Set it as the billing contact for Amazon, airlines, and every SaaS vendor, and those receipts arrive without a human touching them.
• Mobile snap. For paper only. Eight seconds at the counter versus four minutes of archaeology in April.
• Card-linked auto-capture. Ramp and Brex pull merchant-side receipts for a growing vendor list. Free coverage on a real slice of your spend.

The matching engine is what you're buying

A receipt floating on its own is worthless. Its job is to attach itself to a transaction. Good tools match on amount, date window, and merchant string, then hand you the leftovers.

Matching fails in predictable places: tips added after the fact, a pending authorization that settles at a different number, and merchant names that look nothing like the brand on the door. Set the date window to three days and amount tolerance to a few percent, and the exception queue shrinks to five minutes of work.

Every receipt a human forwards, files, or renames is a receipt your system failed to catch.

Categorize with rules, review by exception

Once matched, the category is usually obvious from the merchant. Uber is travel. AWS is software. Encode those rules and stop asking employees to guess at your chart of accounts — they will guess wrong, consistently and creatively.

Set a policy and let the machine enforce it: receipts required above $75, business purpose on meals and travel, nothing accepted after 30 days.

Chase people with software, not with you

The worst part of expenses is the nagging. Automate it. A card charge with no receipt after three days pings the cardholder. After seven, it copies their manager. After fourteen, the card freezes. Nobody argues with a rule that applied to everyone else last month too.

The attachment is the whole point

The image ends up attached to the transaction inside QuickBooks — not in a portal, not in a Drive folder someone will reorganize. When a question surfaces eighteen months later, the answer is one click from the register line.

We build capture pipelines that land clean, attached, and coded — start with Workflow Automation or Bank & App Connections.