Insights on Crypto Payments, Infrastructure, and Operations

Two-Way Reconciliation

Pronunciation: too way rek-un-sil-ee-AY-shun

Also known as: Two-Source Reconciliation, Two-Way Matching

Definition

Two-Way Reconciliation is reconciliation that compares two record sets and classifies records as matched, unmatched, duplicated, or outside tolerance. It compares two sources and cannot independently validate which source is correct when both disagree. 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

Two-Way Reconciliation is reconciliation that compares two record sets and classifies records as matched, unmatched, duplicated, or outside tolerance. It compares two sources and cannot independently validate which source is correct when both disagree. Two-Way Reconciliation is closely connected to Three-Source Reconciliation , Reconciliation Rule Set , and Reconciliation Match Rate .

The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. For Two-Way Reconciliation, this point supports the definition’s focus on reconciliation that compares two record sets and classifies records as matched, unmatched, duplicated, or outside tolerance.

Two-Way Reconciliation should remain distinct from Three-Source Reconciliation, Reconciliation Rule Set, and Reconciliation Match Rate, 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 Two-Way Reconciliation, this point supports the definition’s focus on reconciliation that compares two record sets and classifies records as matched, unmatched, duplicated, or outside tolerance.

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 Two-Way Reconciliation, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Two-Way Reconciliation should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Two-Way Reconciliation should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.

Operational reporting for Two-Way Reconciliation should separate completed, pending, failed, retried, manually adjusted, and unresolved records so aggregate totals do not hide uncertain outcomes. A production review of Two-Way Reconciliation should compare external provider or network evidence with internal state and accounting records before the organization releases irreversible follow-on action.

Key Takeaway

Two-Way Reconciliation should be defined with explicit scope, authoritative evidence, accountable ownership, controlled exception handling, and measurable production safeguards.

Sources

  1. ISO 20022 Universal Financial Industry Message Scheme — ISO 20022 Registration Authority (2026-08-03)
  2. CPMI Glossary — Bank for International Settlements (2026-08-03)
  3. Principles for Financial Market Infrastructures — CPMI-IOSCO (2026-08-03)