Every expense process eventually meets the receipt that does not exist. The parking meter that printed nothing. The taxi receipt that dissolved in a jacket pocket. The airport purchase made at a sprint. However good capture becomes, some fraction of spend will always arrive without paper, and a process with no formal answer for that fraction accumulates permanent open items.
The standard treatments are all bad. Blocking the expense entirely punishes employees for reality and encourages fabricated documentation. Waving it through unrecorded creates an audit gap. Leaving the charge open forever, the most common outcome, builds the aging unmatched list that makes every subsequent statement reconciliation slower and every audit request a spelunking exercise.
The long tail of card spend needs a workflow, not a shrug.
Lost Receipt Declarations
In Finofo, a missing receipt is declared and tracked rather than left open. The employee completes a lost receipt declaration for the specific charge: what it was, why no receipt exists, attached to the expense as a formal record.
For corporate card expenses, the matching statement transaction itself serves as proof of purchase, the bank already confirmed money moved to that merchant on that date for that amount. The declaration supplies the business context the statement line lacks. For reimbursable expenses, where there is no statement line to lean on, the employee attaches whatever supporting proof exists, a booking confirmation, a calendar entry, a card statement of their own.
The result is that the exception resolves. The charge is explained, the explanation is documented, the approval chain sees it explicitly, and the statement can still tie out because the line has a formal disposition instead of an empty receipt slot.
Duplicates: The Other Long Tail Problem
Missing receipts are one end of the exception spectrum. The other end is receipts that show up twice.
How duplicates actually happen
Rarely fraud, usually friction. An employee texts a receipt, forgets, and submits it again through the app. A purchase made on a corporate card gets claimed as a reimbursement too. A shared team dinner gets submitted by two attendees. Each is an honest mistake that, unchecked, becomes a double payment.
Detection at submission, not at audit
Finofo detects duplicate expenses as they enter the flow, matching on the signals that reveal the same underlying purchase, so the second submission gets flagged before it moves toward approval and payment. The awkward recovery conversation after a double reimbursement simply does not happen, because the duplicate never got that far.
Exceptions That Trend Toward Zero
The measure of an exception process is whether the exceptions list shrinks or grows. Declarations give missing receipts a terminal state. Duplicate detection stops double claims at the door. Unmatched statement charges stay visible until resolved, and nothing unresolved flows into the export.
The compounding effect is that each month starts clean. There is no inherited backlog of mystery charges from prior periods, no aging list that everyone has agreed not to look at. Auditors reviewing card spend find every charge either matched to a receipt or carrying a documented declaration, which is the difference between an expense sample that closes quickly and one that generates a findings list.
For finance, the long tail stops being a tax on every close and becomes what it should be: a small, visible, fully explained set of edge cases.
Start Here
Count the unmatched card charges older than ninety days in your current process. Each one is an exception that had nowhere to go.
Finofo gives missing receipts a formal declaration workflow, flags duplicates at submission, and keeps every exception visible until resolved, so the long tail of card spend gets explained instead of accumulating.
