Reconciliation exception management is the process that takes each flagged item, such as an unmatched line, a duplicate or a gap, from the moment it is raised to a documented resolution. It has five parts: triage by type and size, an owner, a deadline, evidence for the fix, and a report of what is still open at period close.
What counts as a reconciliation exception?
A reconciliation exception is any item the reconciliation cannot explain on its own: a line with no partner, a difference between two figures that should agree, a possible duplicate, or a gap in a sequence. It is a question that needs an answer, not necessarily an error. Many exceptions turn out to be timing.
Common exception types
- Unmatched items. A statement line with no ledger entry, or the reverse.
- Amount differences. A pair that matches on reference but differs on value.
- Possible duplicates. Same payee, same amount, close dates.
- Sequence gaps. A check number missing from an otherwise continuous run.
- Footing failures. A statement whose opening balance plus activity does not equal its closing balance.
- Stale reconciling items. A timing item that has not cleared within the expected period.
What is not an exception
An outstanding check written two days before month end is a normal reconciling item, not an exception. Treating every timing item as an exception floods the list and trains people to skim it. Set rules that keep expected timing items on the reconciliation and raise them as exceptions only when they pass an age limit.
Triaging flagged reconciliation exceptions by type and size
Triage means sorting flagged reconciliation exceptions so the ones that can do the most harm are handled first. Sort by type before size: a footing failure or a possible duplicate outranks a small unmatched line, because it can hide many other errors or represent money already lost.
A triage order
- Footing failures. If a statement does not foot, every match built on it is suspect. Fix the statement first.
- Possible duplicates over a size limit. Money may have left twice. Recovery gets harder each week.
- Sequence gaps on checks. A missing check number can mean a lost, stolen or unrecorded check.
- Unmatched items over a size limit. Large items with no partner may be unrecorded transactions.
- Amount differences. Often fees or keying slips, but each needs a cause.
- Small unmatched items. Usually timing or minor errors. Batch them for one review session.
The size limit is your choice. Pick it from the account's normal activity, and record it so the order is the same each month.
When the matching itself caused the exception
Some exceptions exist because a matching rule was too strict or too loose. A long list of unmatched items with near-identical amounts often points to a date window that is too narrow. How transaction matching software sets date windows and tolerances explains how to tell a rule problem from a data problem.
Assigning an owner and a deadline to each reconciliation exception
Every reconciliation exception needs one named owner and a date by which it must be resolved or escalated. An exception owned by "the team" is owned by nobody. A deadline turns an open item into a commitment and makes ageing visible.
Who owns what
The owner is the person best placed to find the cause, not always the preparer. A missing vendor payment belongs with payables. An unrecorded deposit belongs with whoever applies cash receipts. A bank error belongs with the person who holds the bank relationship. The preparer's job is to route it and follow up.
Setting deadlines
Deadlines work best when tied to the close calendar rather than set item by item. A sample policy:
- Footing failures and duplicates over the size limit: resolved before the reconciliation is signed.
- Other items over the size limit: resolved within five business days.
- Small items: resolved by the next month's reconciliation.
- Anything past its deadline: escalated to the controller with a note on why.
These are examples. A busy institution with daily reconciliations will need shorter windows. Reconciliation software for credit unions covers the volume and timing pressures in that setting.
Handing an exception to someone outside finance
Many exceptions can only be answered by someone outside the finance team: a branch manager who took a cash deposit, a project lead who approved a vendor, an office manager who holds the check stock. Those people do not read the reconciliation, so the request has to stand alone. Give them the amount, the date, the bank line as printed and one plain question, such as "Was this 875.00 deposit from a customer, and which one?" Record when the request went out and when the answer came back. If the answer never comes, the deadline still applies, and the exception escalates on the same terms as any other.
Changing an owner mid-month
Exceptions sometimes need a new owner when the first one finds the cause sits elsewhere. Reassigning is fine, but the register should keep the history: who held it, for how long, and why it moved. An exception that has passed through four owners in a month is itself a signal that nobody understands the process that produced it.
What evidence closes a reconciliation exception?
A reconciliation exception closes when the owner records its cause, the action taken and a document that shows it. The evidence should let a reviewer who was not involved confirm the resolution without asking anyone. A note saying "resolved" with no attachment is a claim, not evidence.
Evidence by exception type
- Unrecorded transaction: the journal entry that records it, plus the bank line or source document.
- Duplicate confirmed: the refund request or the bank's credit, with the original and duplicate lines.
- Duplicate rejected: the two invoices or receipts that prove two real purchases.
- Missing check number: the voided check, a register entry showing it was spoiled, or its later clearing.
- Bank error: the bank's written confirmation and the date of its correction.
The exception register
A register is the list that holds all of this in one place. The rows below are examples.
| ID | Type | Amount | Owner | Deadline | Status | Closing evidence |
|---|---|---|---|---|---|---|
| E-01 | Possible duplicate | 1,240.00 | Payables lead | Before sign-off | Closed | Vendor credit memo, both statement lines |
| E-02 | Check number gap, #3318 | (none) | Preparer | 5 business days | Closed | Void entry in check register |
| E-03 | Unmatched deposit | 875.00 | Cash applications | 5 business days | Open | Awaiting remittance from customer |
| E-04 | Amount difference | 12.50 | Preparer | Next reconciliation | Closed | Bank fee schedule, fee journal entry |
| E-05 | Footing failure, page 3 | 300.00 | Preparer | Before sign-off | Closed | Missing line restored from bank PDF |
PreciseBankFlow produces the statement side of a register like this. Each difference, duplicate and check number gap is listed with the source lines that support it, and the report exports to Excel or PDF for review and sign-off. Owners and deadlines are set in your own close process.
Reporting open reconciliation exceptions at period close
At period close, the open reconciliation exceptions should be reported in one list showing each item's amount, age, owner and the reason it is still open. That report tells the controller what risk is being carried into the next period, and it tells an auditor the reconciliation is honest about its loose ends.
What the close report shows
- Count and total of open exceptions, by account and by type.
- Age bands, such as under 30, 31 to 90 and over 90 days.
- Each item past its deadline, with its escalation note.
- Exceptions closed during the period, so trends are visible.
Trends worth acting on
The same kind of exception on the same account every month is not a reconciliation problem. It is a process problem upstream. A recurring unmatched fee may need a standing journal. Recurring duplicates from one vendor may need a payables control. For balance sheet accounts beyond cash, the same reporting belongs inside the wider close, as covered in what general ledger reconciliation software should do.
Trust accounts deserve a stricter standard. An open exception in a client trust account may mean one client's money is short, so many firms resolve every trust exception before the reconciliation is signed. Trust accounting software for law firms covers the controls that setting expects.
Exception management mistake: clearing reconciliation exceptions in bulk
Clearing reconciliation exceptions in bulk, by selecting a page of items and approving them together, turns the control into a formality. It is fast on the day and costly later, because one real error is approved along with forty harmless timing items, and the approval record says a person reviewed something they did not read.
Bulk clearing usually starts for good reasons. The list is long, most items are small, and the close is late. The fix is to shorten the list, not to stop reading it. Tighten the rules that raise timing items as exceptions. Batch small items into a single reviewed entry with its own support. Keep the high-risk types, such as duplicates and footing failures, out of any bulk action at all.
If a tool allows bulk approval, check that it records each item individually, with the approver's name, so the register still shows one decision per exception. To see how a statement-level exception report looks on your own files, request early access to PreciseBankFlow.