Corporate card statement reconciliation has a quiet failure mode: the statement never fully ties out, and everyone learns to live with it. A handful of charges have no receipts. A few receipts do not obviously belong to any charge. The gap gets carried, the export happens anyway, and the unmatched residue accumulates month over month until nobody remembers which charges were ever explained.
The problem is not that matching is conceptually hard. Most charges match their receipts on amount, date, and merchant without ambiguity. The problem is that the last ten percent, the near misses and the genuinely missing receipts, has no good workflow in most tools. Near misses require manual detective work. Missing receipts have no formal state, so they linger as open items indefinitely.
A reconciliation process is only as good as its treatment of the exceptions.
How Matching Actually Works
Finofo matches receipts to card transactions using merchant, amount, currency, and date, with statement data pulled directly from the bank or card provider, or uploaded when a direct connection is not used.
Exact matches happen on their own
Where amount, date, and merchant line up, the receipt links to the statement line automatically. This covers the bulk of card spend without anyone touching it. Employees who submitted receipts at purchase time see their expenses arrive pre matched when the statement lands.
Near misses get proposed, not dumped
Real world matching has legitimate fuzz: a tip pushes the charged amount above the receipt subtotal, a merchant bills under a different legal name, a charge settles a day after the purchase. The model proposes these as suggested matches for a human to confirm rather than leaving them in an undifferentiated unmatched pile. Confirming a proposed match takes seconds; finding it manually takes minutes.
Missing receipts get a formal state
When a receipt genuinely does not exist, the employee completes a lost receipt declaration. The charge is declared and tracked rather than left open, and for corporate card spend the matching statement transaction itself serves as proof of purchase. The exception is resolved with an audit trail instead of lingering as an eternal open item.
The Statement Completes Only When It Ties
The structural discipline is at the statement level: reconciliation completes only when the balance ties to recorded expenses. Every statement line is either matched to an expense or explained through a declaration. Unmatched lines stay out of the export until they are matched or explained.
That last rule is what prevents the accumulating residue. Nothing ambiguous flows downstream into the accounting system, which means the GL never inherits the unexplained charges that traditionally get exported under deadline pressure and cleaned up never.
Finance sees the state at a glance: what is ready, what is missing, and what needs attention. Duplicate expenses, the same receipt submitted twice, or the same charge claimed on both a card and a reimbursement, are detected rather than discovered at audit.
What Changes at Month End
For teams accustomed to statement reconciliation as a multi day month end project, the shift is that the work has mostly already happened. Receipts submitted at purchase time matched as statement data arrived. The month end task shrinks to reviewing proposed matches and resolving declared exceptions, a session measured in minutes rather than days.
The close benefits directly: card spend enters the accounting system fully reconciled, with receipts attached and exceptions documented, instead of arriving as a bulk export with a to be reconciled asterisk.
Start Here
Look at how many unmatched card charges your last three statements carried into the export. That number is the residue a tie out discipline eliminates.
Finofo matches statements line by line, proposes the near misses, tracks lost receipt declarations, and completes reconciliation only when the balance ties, so nothing unexplained reaches your accounting system.
