Reconciliation Break

Overview

Understand the idea

A reconciliation break is a difference between records that should agree, such as a missing item, amount mismatch, duplicate, timing difference, currency error, fee variance, or unmatched settlement entry. It remains open until supported resolution and correcting evidence are recorded.

Reconciliation begins with independent source records and a clearly defined cutoff. Systems normalize identifiers, currencies, dates, and signs, then match one-to-one, one-to-many, or many-to-one relationships.

Unmatched and partially matched items enter exception queues rather than being forced together. Merchant and order views must explain how customer payments, provider fees, refunds, disputes, reserves, conversions, settlement, and ledger postings produce the final balance.

Reports should explain matched, unmatched, duplicated, reversed, pending, and aged items. Manual decisions need an owner, reason, evidence, approval, and final correcting entry that preserves the original transaction history.

What actually happens

A reconciliation break is a mismatch between financial records that should represent the same event or balance. A crypto payment may be confirmed on-chain but missing from an invoice ledger, recorded under the wrong asset, duplicated in a webhook table or converted at an unexplained rate. The break is an unresolved difference, not necessarily fraud; its importance is that accounting cannot yet demonstrate what happened.

Reconciliation starts from independent sources such as blockchain observations, provider payment records, orders, settlement statements and general-ledger postings. It normalizes dates, asset precision, identifiers and cutoffs, then matches one-to-one or one-to-many relationships. Unmatched records enter a categorized queue, with evidence and ownership. The resolution might be a timing adjustment, corrected journal entry, refund, missing fee record or provider investigation. The original evidence must remain intact so reviewers can reconstruct each decision.

Decisions and failure cases

Cutoff differences can create temporary breaks that resolve next day; missing transfers can indicate more serious problems. Set aging thresholds, escalation routes and materiality rules. Never automatically match two records based on amount alone when multiple same-value invoices exist.

Related concepts

Reconciliation, Reconciliation Exception, Settlement Reconciliation.

Further reading

NIST Digital Identity Guidelines.