Reconciliation Rule
Pronunciation: rek-un-sil-ee-AY-shun rool
Also known as: Reconciliation Rule Process, Reconciliation Rule Control
Definition
Reconciliation Rule is a documented condition that determines how records are matched, classified, tolerated, or routed to exception handling. It is one governed decision condition, while a rule set combines multiple conditions and priorities. In production, the definition should identify scope, authoritative records, ownership, state or timing rules, and the controls used when evidence conflicts. It matters because inconsistent interpretation can create duplicate processing, misstated balances, delayed settlement, or unresolved operational exceptions. Teams should also document measurable outcomes and review the definition whenever providers, rails, accounting rules, or system architecture change.
Overview
Reconciliation Rule is a documented condition that determines how records are matched, classified, tolerated, or routed to exception handling. It is one governed decision condition, while a rule set combines multiple conditions and priorities. Reconciliation Rule is closely connected to Reconciliation Rule Set , Reconciliation Match Key , and Reconciliation Tolerance .
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 Rule, this point supports the definition’s focus on documented condition that determines how records are matched, classified, tolerated, or routed to exception handling.
Reconciliation Rule should remain distinct from Reconciliation Rule Set, Reconciliation Match Key, and Reconciliation Tolerance, 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 Rule, this point supports the definition’s focus on documented condition that determines how records are matched, classified, tolerated, or routed to exception handling.
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 Rule, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Reconciliation Rule should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Reconciliation Rule should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.
Operational reporting for Reconciliation Rule should separate completed, pending, failed, retried, manually adjusted, and unresolved records so aggregate totals do not hide uncertain outcomes. A production review of Reconciliation Rule should compare external provider or network evidence with internal state and accounting records before the organization releases irreversible follow-on action.
Key Takeaway
Reconciliation Rule should be defined with explicit scope, authoritative evidence, accountable ownership, controlled exception handling, and measurable production safeguards.
Sources
- ISO 20022 Universal Financial Industry Message Scheme — ISO 20022 Registration Authority (2026-08-03)
- CPMI Glossary — Bank for International Settlements (2026-08-03)
- Principles for Financial Market Infrastructures — CPMI-IOSCO (2026-08-03)