Unmatched transaction
An unmatched transaction is money that moved through your accounts but isn't tied to an invoice, order or ledger entry — so nobody yet knows what it was for.
An unmatched transaction is a payment or receipt that has landed in a bank or PSP account but hasn’t been linked to the invoice, order, or ledger entry it belongs to — so it sits there without an explanation.
How it works
- A payment arrives with a reference that doesn’t match any open invoice.
- A payout leaves but isn’t yet posted against the right expense.
- An amount is short, combined with others, or paid early — and the automatic match misses.
Each one has to be run down by hand: who sent it, for what, and where it should post. Until then, it’s a line the books can’t close over.
Why it matters
A pile of unmatched items is where reconciliation quietly turns into a part-time job. Worse, it distorts everything downstream — your cash position looks wrong, a customer chases you for a payment you already received, or a real problem hides in the noise. The volume tends to grow with the business, right when there’s least time to clear it.
Common causes of unmatched transactions
| Cause | What you see | The fix |
|---|---|---|
| Bundled deposit | One processor payout covering many orders, net of fees | Break the deposit into its orders and fees |
| Unusable reference | A payment whose reference was truncated or replaced by the bank | Carry an ID the rail preserves, or match on amount and date |
| Partial or combined payment | One invoice paid in parts, or several paid together | Allow one-to-many and many-to-one matches |
| Currency difference | The right payment at a different amount after conversion | Post the FX difference instead of forcing a match |
| Timing | A payment recorded in one period and received in the next | Match across periods, then clear |
How to clear unmatched transactions
- Sort by cause, not by date. Bundled deposits and bad references clear in batches; one-offs clear by hand.
- Break bundled deposits first. One processor payout usually clears dozens of lines at once.
- Match partials and combinations, then post fees and FX differences to their own accounts.
- Fix the source, so next month’s payments arrive with a reference that survives the rail.
Unmatched receiving reports
In accounts payable, an unmatched receiving report is a goods receipt with no matching invoice or purchase order yet. It blocks the three-way match that lets an invoice be paid. It usually means the supplier hasn’t invoiced, the invoice went to the wrong inbox, or the quantities differ. See three-way match.
How Fynex does it
Fynex matches payments and payouts to the books automatically and attaches a confidence signal, so the handful that genuinely need a human are the only ones surfaced — not the whole day’s flow. That keeps bank reconciliation an exception queue rather than a full re-do. See reconciliation.