A useful reconciliation exception log describes the question that remains, not just the amount that fails to match. Give every item an identifier, a source reference, an owner, and a next action. That turns “the reconciliation is off” into work someone can complete.
Give the item enough context
An amount on its own is rarely unique. Record the account, cut-off date, transaction date, source report, and any payment or ledger reference. Link to the original evidence instead of pasting sensitive account data into a general-purpose message thread.
Separate what is known from what is suspected. “Deposit missing from bank statement” is a finding only after checking the relevant statement period. “Possible deposit timing difference” is a hypothesis that still requires evidence.
Example of an actionable entry
| Field | Illustrative entry |
|---|---|
| Exception ID | REC-014 |
| Comparison | Adjusted bank versus trust books |
| Amount | $430 |
| Observation | Ledger receipt appears in June export |
| Evidence needed | Deposit detail and next statement activity |
| Owner | Assigned reconciliation contact |
| Next action | Match receipt reference to deposit support |
| Status | Investigating; no correction posted |
This entry tells the next person where to look. It does not assume that $430 should be added to or removed from either balance.
Use statuses that change the work
“Open” can hide several different situations. Useful statuses include awaiting source, awaiting explanation, ready for approved correction, and resolved with evidence. Keep the date of the latest action so an old item is not mistaken for a new discovery.
When an item is resolved, record the explanation and supporting reference. If a correction was authorized, link the approved change and the revised report. Deleting the row erases the very trail that makes the log valuable.
Review the age and the next step
At the review meeting, focus on items that lack an owner, have no clear action, or have remained unchanged. A large list of “checking” statuses is a sign that the work needs a more specific handoff.
Keep an unresolved item visible in the month-end package. A comparison should not be described as fully explained while an unsupported adjustment is doing the balancing.
The DaxSync reconciliation service starts by defining the report population and the exception trail, so the conversation can move beyond a single unexplained total.
Sources and further reading
- IRS: choosing and maintaining business records
- Intuit: reviewing a first reconciliation and opening balance
Source links provide background. The workflow and illustrative examples above are original educational material.