Settlement Reconciliation
Pronunciation: SET-uhl-munt rek-un-sil-ee-AY-shun
Definition
Settlement reconciliation compares expected settlement obligations and internal ledger entries with actual bank, provider, custodian, network, or blockchain records. It confirms completeness and accuracy and identifies items that did not settle as expected. Settlement Reconciliation requires named ownership and auditable controls for matching evidence, cutoff control, and exception resolution. The process starts with a defined settlement population, such as a cycle, batch, account, currency, or date.
Overview
Settlement reconciliation compares expected settlement obligations and internal ledger entries with actual bank, provider, custodian, network, or blockchain records. It confirms completeness and accuracy and identifies items that did not settle as expected. A reconciliation is not complete merely because the net total agrees.
The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. 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. 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.
Expected gross amounts, fees, reserves, refunds, adjustments, and net positions are compared with external statements and final account movements.
Exact matches can be cleared automatically, while one-to-many, timing, partial, duplicate, and unexplained differences should remain visible in an exception queue. For Settlement Reconciliation, the principal failure modes are incorrect obligations, liquidity shortfalls, participant default, wrong settlement assets, premature finality, and unreconciled movements.
Matching can use settlement IDs, transaction references, amounts, currencies or assets, dates, participants, and batch controls. Every eligible source transaction must be represented, and every external entry must be allocated or investigated. Resolutions should use reason codes, ownership, evidence, approval, and linked adjustments. For Settlement Reconciliation, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Settlement Reconciliation should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome.
Key Takeaway
Settlement reconciliation compares expected settlement obligations and internal ledger entries with actual bank, provider, custodian, network, or blockchain records. Its matching scope, cutoff, exceptions, and resolution evidence must be explicit.
Sources
- Principles for Financial Market Infrastructures — BIS CPMI-IOSCO (2026-08-01)
- A Glossary of Terms Used in Payments and Settlement Systems — Bank for International Settlements (2026-08-01)