An operating standard
What should happen when a bank transaction cannot be matched confidently?
A bank transaction that cannot be matched confidently should stop and become a visible exception — held out of the settled figures, described in plain language, owned by a named person, and dated — rather than posted to whichever account looks closest.
An unmatched transaction is a question the business has not answered yet. Five things should happen to it: hold, clarify, gather evidence, resolve, and preserve the history. A guess skips all five and then looks exactly like a correct entry, which is what makes it expensive.
Hold, clarify, gather, resolve, preserve. In that order.
Nothing in this standard requires particular software or a particular kind of provider. A bookkeeper, an accounting firm and an internal finance team can each be measured against it, and the answer they give tells you what happens to the part of your ledger nobody shows you.
| Step | What it means | What it looks like when it is skipped |
|---|---|---|
| 1 · Hold | The movement of cash is recorded, and the classification is explicitly marked unresolved. The money is real; what it means is not yet known. | The amount lands in a plausible expense code, or in a holding account nobody revisits. |
| 2 · Clarify | The uncertainty is written in a sentence a non-accountant can read: what arrived, from where, and why it cannot be settled. | “Unidentified” or “query” — a label carrying no information, actionable by nobody but its author. |
| 3 · Gather evidence | A specific artefact is requested from a specific place: a remittance, a supplier invoice, a bank narrative, an answer from whoever authorised the payment. | The item joins a general list and waits for somebody to notice it. |
| 4 · Resolve | The item is allocated on the strength of that evidence, and the evidence is attached to the entry it supports. | The item is cleared at month-end because it is old, not because it is understood. |
| 5 · Preserve | The exception and its resolution stay readable afterwards: what it was, what settled it, when, and on whose answer. | The exception vanishes on closing, and next month the same transaction type raises the same question again. |
What a good exception actually says.
An exception is a piece of writing, and most are written badly. The difference is rarely diligence. It is that a good exception is written for the person who has to act on it, and a poor one is written by somebody clearing their own list.
| A weak exception | A good exception | |
|---|---|---|
| What it says | Unidentified receipt — query | Receipt of 12,400 on 14 May, bank narrative “PROJ TRF”. Matches no single open invoice for that customer; closest combination is short by 600. |
| Who owns it | Unassigned, or “finance” | Named. Held by whoever keeps the books until the remittance arrives; the account owner is asked only if it does not. |
| What it is waiting on | Nothing stated | A remittance advice, or the customer confirming which invoices the payment covers. |
| When it comes back | Whenever somebody opens the list | Requested 16 May, next review 20 May, raised with the owner if still open before the period is closed. |
| On resolution | Cleared | Allocated against the named invoices, remittance attached to the entry, exception closed with the reason recorded. |
A practical filter: if the exception cannot be understood by a colleague returning from two weeks’ leave, it is not an exception. It is a reminder to the person who wrote it.
A confident wrong entry costs more than an open question.
The instinct to clear the list is strong and mostly wrong. An open question is uncomfortable and visible. A guess is comfortable and invisible, and the invisibility is the entire cost.
- It stops looking like a question. Once posted, a guessed entry is indistinguishable from a verified one. Nothing marks it for a second look, so it never gets one.
- It travels. The figure moves into the month’s reported numbers, into any tax or filing position that depends on them, and into whatever decision was taken on the strength of the report.
- It surfaces late, or through somebody else. The discovery point is usually a year-end review or a question from outside, by which time the context that would have settled it in one message is gone and the people involved have moved on.
- It teaches. A matching rule written on the basis of a guess applies that guess automatically to every similar transaction that follows, quietly and at scale.
- It costs more to unwind than it ever cost to resolve. A correction after a period has been reported on touches a figure somebody has already relied on, which turns a two-minute question into a conversation.
The comparison worth making is not “open item versus clean ledger”. It is “an open item you can see versus a wrong one you cannot”. A set of books carrying twelve named exceptions is in better condition than one carrying none and forty quiet guesses.
The transactions that genuinely cannot be matched.
Most bank lines match themselves. The residue is small, repetitive and worth naming, because each type has a different resolution path and a different owner.
- Money in from a payer nobody recognises. A trading name that differs from the customer name, a payment from a parent company, or a client paying through a third party.
- A card or account charge nobody recognises. An opaque descriptor, a renewal from a service signed up to by somebody who has since left, or a fee applied under a new schedule.
- A payment out with no bill behind it. A supplier paid on a quote, a deposit, or a purchase made personally and reimbursed through the account.
- A transfer between the business’s own accounts where only one side is visible, which reads as income until the other side appears.
- A refund, rebate or reversal with no original. The credit is real and the transaction it relates to may sit in a period that is already closed.
- A personal transaction through the business account. Ordinary in owner-led businesses and entirely resolvable — but only by the owner.
- A possible duplicate. Two identical amounts to the same party days apart, which is either a genuine repeat or a payment made twice. Guessing either way is expensive in a different direction.
Three of those can only be answered by the business. That is not a failure on the provider’s part and it should not be presented as one. The correct response is a specific question to a specific person — not a month held hostage, and not a quiet decision.
Five things to settle before an exception exists.
Most arguments about unmatched items are really arguments about a rule nobody set. Deciding these once removes the judgement call every time:
- The default when certainty runs out. Hold, not post. Said out loud once, it stops being a matter of temperament.
- Where exceptions live, and how you see them. One list, visible to you while items are open — not a paragraph at the end of a monthly email.
- Who may decide a match is good enough, and on what evidence: a remittance, a bank narrative, a written confirmation, an approval.
- How long an item may sit without an owner. Anything unowned is not being worked on, whichever list it appears in.
- What happens to items still open when the period closes. They should be reported with the accounts, not swept into them.
None of this needs a particular system. It needs somebody to have decided what happens when the software runs out of certainty, and to have written it down where you can read it.
Where At Par fits — and the limits.
At Par’s bookkeeping work is organised around this standard rather than around a ledger that looks clean. Transactions that cannot be settled on evidence are held, described in language you can read, given an owner and a date, and kept visible to you while they are open instead of summarised after the fact. When one is resolved, the evidence stays attached to the entry it supports.
That is part of bookkeeping and month-end close, and it applies whether your records sit in QuickBooks or Xero — the file stays yours either way. Where the books have fallen far enough behind that the residue is the majority, that is catch-up work first. The broader standard this belongs to is set out in what an outsourced accounting provider should own.
Asked by owners who have found something odd in their ledger.
How should an unmatched bank transaction be handled? +
Hold it rather than post it. Record that the cash moved, mark the classification unresolved, and write one sentence saying what arrived, from where, and why it cannot be settled. Name who has to act and what specific evidence would end it — a remittance, an invoice, a confirmation from whoever authorised it. Give it a review date. When the evidence arrives, allocate it and attach the evidence to the entry, then keep the resolution readable so the same question does not have to be answered twice.
Is it acceptable to post an unidentified payment to miscellaneous expenses? +
No. Miscellaneous is a classification, and applying it to something unidentified converts a question into a statement. The entry then looks settled, is never reviewed again, and flows into the reported figures and any tax position resting on them. An explicitly unresolved holding position is the honest alternative: the cash stays recorded, the uncertainty stays visible, and the item stays on a list somebody is accountable for clearing.
What is a suspense account, and is it bad practice to use one? +
A suspense account is a temporary holding position for an amount that has occurred but cannot yet be classified. Using one is normal and often correct. What makes it bad practice is leaving it unattended — entries with no description, no owner and no review date, and a balance that grows quietly month after month. A suspense account should behave like a short queue with a name against every line, not a place where unresolved items go to be forgotten.
Who should resolve an unmatched transaction — the provider or the business? +
It depends on where the missing information lives. A provider can chase a remittance advice, read a bank narrative, search for a matching invoice and check a supplier account. Only the business can confirm what an unrecognised payment to a new supplier was for, whether a transaction was personal, or what was agreed verbally with a customer. The workable split is that the provider does all the retrieval and asks one specific question when only the business holds the answer.
How quickly should unmatched bank items be cleared? +
Fast enough that the context still exists. There is no universal deadline, but the practical test is whether the item can still be explained by the people involved — memories of a transfer fade within weeks and the person who authorised it may not be reachable later. A weekly sweep keeps items resolvable; a monthly one usually means resolving them from documents alone. Nothing should reach the close of a period without either a resolution or an explicit note that it is open.
Can bank feed automation match every transaction automatically? +
No. Automated matching handles the predictable majority — recurring suppliers, familiar amounts, clean references — and that is genuinely valuable. It cannot resolve a payment with no reference, a receipt from an unfamiliar payer, a charge nobody recognises, or a transaction whose meaning exists only in a conversation. That residue is small and disproportionately important, and how it is treated is the difference between a ledger that is tidy and one that is right.
What should a good exception actually say? +
Enough that somebody else can act on it without a conversation. What arrived or left, when, and how it reads on the statement. Why it cannot be settled, in a sentence a non-accountant can follow. Who is holding it, and whether the next move belongs to the provider or the business. What specific evidence would end it. When it will be looked at again. And once it is resolved, what settled it — so the same question does not have to be answered from scratch the next time the same kind of transaction appears.
Does an unmatched transaction mean somebody made a mistake? +
Usually not. Most originate outside the business: a customer paying with no remittance, a bank narrative carrying no useful reference, a supplier charging under a trading name that differs from the contract, a payment processor netting fees before payout. Treating exceptions as failures is precisely what causes them to be hidden. They are a normal output of any real set of books, and the useful question is how they are handled rather than how many there are.
Send us one month of transactions. We’ll show you the residue.
One bank statement and whatever documents you have. We will come back with what matched cleanly, what could not be settled on the evidence available, and the specific question each unresolved item needs answered.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Review our exceptionsWe use your details only to prepare for and hold this call. No spam, ever.
Reviewed by an ACCA on the At Par team · Last updated 29 July 2026 · This page sets out an operating standard any provider can be held to, not a description of a particular system. See what we actually do.