The Reconciliation Error Catalogue — 57 Ways Real Books Go Wrong
Terra Insight publishes the catalogue of 57 human-error patterns we test against — carelessness, knowledge gaps, misconfigured systems, gaps in the data, and missing or mistimed entries — plus the Detection Envelope: our written per-customer statement of what we catch, what we catch conditionally, and what no reconciliation on earth can structurally catch.
Reconciliation software is usually pitched as matching software. But matching clean data is easy. The real job is surviving the data finance teams actually produce — files touched by tired clerks at month-end, exported from systems configured years ago by someone who left, maintained by people who know their business but not every section of the Income-tax Act. And here is the reframe that changes the pitch: many of these errors are not noise the software must tolerate — they are exactly what reconciliation exists to find. A payment recorded twice, an entry posted to the wrong month, a receipt that bounced but was never reversed — finding these IS the product.
Terra Insight has built a catalogue of 57 error patterns in 5 families and manufactures each one deliberately into realistic Indian financial data before every release. A test only passes when the product surfaces the error as the right exception, with the right rupees attached. Silently absorbing an error, or worse letting an error improve the match rate, is an automatic failure. That test discipline is what earns Terra Insight the right to publish the Detection Envelope — the written per-customer statement of which patterns we catch, catch conditionally, and cannot structurally catch.
This cluster explains each of the 5 families in depth, walks every one of the 57 error patterns with Indian regulatory-context worked examples, and marks the patterns that no reconciliation on earth can structurally catch — the honest limits of the discipline. It pairs with the Reconciliation Process Design cluster (how to design controls to catch these), the Reconciliation Playbook cluster (the 20-day cadence to run those controls), and the anchor Detection Envelope page (the trust artefact your auditor sees).
The Carelessness Family: 16 Reconciliation Errors That Come From Working Late
The month-end-at-9pm class. Nobody is careless on purpose — but a duplicate row, a fat-finger zero, a trailing space on a GSTIN, and a return typed as a positive together produce the reconciliation working paper the controller cannot sign off. This family walks every one of the sixteen carelessness patterns with an Indian regulatory failure attached to each, and separates the ones prevention controls at the upload gate can catch outright from the one — counterparty near-misses — that no reconciliation on earth catches without human recognition.
The Data Gaps Family: 9 Reconciliation Errors That Are Invisible Until the Arithmetic Forces Them Out
What is missing is invisible by definition. A bank statement with a hole in the middle, a fifth current account nobody uploaded, a March file mis-slotted as April — the data-gap family produces exceptions that a match-rate metric cannot see, because the arithmetic completes on the subset that was supplied. This is the honest walkthrough of nine such gaps, the Indian regulatory failure each one produces, and the single member of the family that no reconciliation on earth can catch alone.
The Knowledge Gaps Family: 11 Reconciliation Errors Where a Wrong Belief Is Applied Consistently
Not carelessness — a wrong belief, applied consistently. This is the most dangerous of the 57 human-error families reconciliation must survive, because internally consistent files defeat every reconciliation ever built. Two of the eleven are structural misses: no reconciliation on earth can catch an error applied identically on both sides.
The Misconfigured Systems Family: 11 Reconciliation Errors Where the Software Was Set Up Wrong Years Ago
Nobody typed anything wrong. The software that produced the file was set up wrong — once, years ago, by a consultant who is no longer on the payroll. This is Family 3 of the 57 human errors reconciliation must survive — eleven configuration failures that produce internally consistent files carrying a systematic distortion, and the two members of this family that no downstream reconciliation can structurally catch.
The Missing and Mistimed Entries Family: 10 Reconciliation Errors That Are Why Reconciliation Exists
The other four families in the human-error catalogue describe how data goes wrong on its way to the reconciliation. This family describes what reconciliation exists to find — money in the bank not in the books, a bounce never reversed, a vendor paid twice, and one specific pattern where the bank shows a credit and a return on the same wire while the books certify money that bounced. Every practitioner has lived some version of the last one. That is why this article exists.
See what TransactIG catches — and what it honestly cannot
The Detection Envelope is not a marketing claim. It is a written per-customer report Terra Insight delivers before go-live, classifying every one of the 57 error patterns for your specific data shape. Your auditor gets that document. It is what 'prepared for the worst' means.