Guide · Breaks
Reconciliation breaks: why they recur, and how to stop them.
Most teams know how many breaks they have. Few know why they happen, which is why the same breaks come back every day.
A reconciliation break is an item in one source that has no matching item in the other, or matches with a difference. Breaks are normal; breaks that age without an owner, or recur every day for the same reason, are the problem.
Classify every break
| Class | Example | Usual fix |
|---|---|---|
| Timing | Posted today in one system, tomorrow in the other | Usually clears; watch the age |
| Missing entry | In the bank statement, not in the ledger | Post the entry, with approval |
| Duplicate | Posted twice in one system | Reverse one, with approval |
| Amount difference | Charges, rounding or FX | Tolerance rule or charge entry |
| Reference mismatch | Same transaction, different narration | Fuzzy narration rule |
| Genuine error or dispute | Wrong account or customer dispute | Investigate and escalate |
Age and own every break
- Record when each break first appeared.
- Give it an owner: a team or a person, not “recon”.
- Set escalation points by age and amount under your policy.
- Report open breaks by age bucket every day, not only at month-end.
Turn recurring breaks into rules
If the same kind of break appears every day, for example a bank charge, a predictable narration difference or a one-day timing lag, it is a missing rule. Write the rule, have a checker approve it, version it and watch whether the break stops. Read about UPI reconciliation for one high-volume example.
How AutoRecon does it
AutoRecon is built for finance, operations and treasury teams at banks, NBFCs and payment companies. Switch, network, core, GL, bank and MT950 statements and ERP files are loaded as they land and mapped to one schema, with bad rows rejected and the reason given. UPI and IMPS, cards, NEFT/RTGS, nostro and vendor recons are matched daily on rules you write: exact, tolerance and fuzzy narration matching. Each break is classified, aged and given an owner; recurring breaks become a suggested rule, which takes effect only after maker-checker. The daily close is approved by maker and checker, and MIS, board packs and regulatory returns are drafted with every number traced to the query that produced it. It is read-only by default and writes nothing to your core unless you open the path.
Questions
What is a reconciliation break?
An item in one source with no matching item in the other, or one that matches with a difference, such as a missing entry, a duplicate or an amount mismatch.
How should reconciliation breaks be managed?
Classify each break, record when it appeared, give it an owner, escalate by age and amount, and report open breaks by age daily.
Why do the same reconciliation breaks recur?
Usually because a predictable difference, such as a charge, timing lag or narration format, has no matching rule. Writing and approving the rule stops it.
See it on your own data. AutoRecon — Close the day before it starts. Book a 30-minute working session with an engineer.