Insights on Crypto Payments, Infrastructure, and Operations

Reconciliation Break

Pronunciation: rek-un-sil-ee-AY-shun BRAYK

Definition

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 Break requires named ownership and auditable controls for matching evidence, cutoff control, and exception resolution. For Reconciliation Break, material operational risks include missing records, reused references, cutoff mismatches, duplicate matches, wrong currencies, hidden fees, unresolved suspense, forced balancing, partial refunds, late settlement changes, and corrections without approval evidence.

Overview

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.

The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. For Reconciliation Break, this point supports the definition’s focus on reconciliation break is a difference between records that should agree, such as a missing item, amount mismatch, duplicate.

Reconciliation Break should remain distinct from Reconciliation and Reconciliation Exception, because each can represent a different stage, record, control, or financial outcome.

Important failure modes include missing records, duplicate matches, timing differences, hidden fees, currency mismatches, stale files, and adjustments that force balances to agree without explaining the cause. For Reconciliation Break, this point supports the definition’s focus on reconciliation break is a difference between records that should agree, such as a missing item, amount mismatch, duplicate.

Controls should keep original source records immutable, use stable match keys, explain many-to-one or one-to-many relationships, and route unresolved differences to an aged exception queue. For Reconciliation Break, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Reconciliation Break should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Reconciliation Break should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.

Operational reporting for Reconciliation Break should separate completed, pending, failed, retried, manually adjusted, and unresolved records so aggregate totals do not hide uncertain outcomes. A production review of Reconciliation Break should compare external provider or network evidence with internal state and accounting records before the organization releases irreversible follow-on action. Support and finance teams should be able to trace Reconciliation Break from the original commercial or operational obligation through processing, exceptions, settlement, and the final ledger effect.

Key Takeaway

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. Its matching scope, cutoff, exceptions, and resolution evidence must be explicit.

Sources

  1. Principles for Financial Market Infrastructures — BIS CPMI-IOSCO (2026-08-01)
  2. Conceptual Framework for Financial Reporting — IFRS Foundation (2026-08-01)