Reconciliation

Overview

Reconciliation compares independent records of financial activity to confirm that obligations, transactions, balances, fees, settlement movements, and accounting entries are complete and consistent. Differences are identified, investigated, corrected, approved, and retained as auditable exceptions rather than hidden through forced balancing.

For Reconciliation, reconciliation begins with independent source records and a clearly defined cutoff. For Reconciliation, systems normalize identifiers, currencies, dates, and signs, then match one-to-one, one-to-many, or many-to-one relationships. The source-of-truth record should preserve source record, counterpart record, matching rule, cutoff, amount, currency or asset, exception reason, and resolution evidence for Reconciliation, including the handoff to Reconciliation Exception . For Reconciliation, the most consequential risks are 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. The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence.

Reconciliation should remain distinct from Reconciliation Exception and Reconciliation Engine, 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, this point supports the definition’s focus on reconciliation compares independent records of financial activity to confirm that obligations, transactions, balances, fees, settlement movements, and accounting.

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, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released.