A single cross-border payment can generate records in half a dozen systems: the originating institution, one or more intermediaries, a clearing scheme, a correspondent's ledger and the receiving institution. Each records the payment in its own format, at its own moment, with its own reference. Reconciliation is the work of proving that all of these describe the same event — and the work grows faster than the volume.

Why one payment becomes many records

  • Different formats. ISO 20022 messages, scheme files and internal ledgers describe the same payment differently.
  • Different timing. Debits, settlements and credits happen at different moments, so an intraday view is always partly incomplete.
  • Deductions in transit. Intermediary fees change the amount received, so the outgoing and incoming figures do not match by design.
  • Broken references. When a reference is truncated or transformed, matching becomes manual.
  • Multiple hops. Each additional institution adds another place a record can diverge.

What good reconciliation looks like

The strongest prompt to reconcile is a ledger that records attribution. If every operation can be traced to a principal, an agent and the policy version under which it was authorised, then matching becomes a matter of comparing structured facts rather than reconstructing intent. Signed, verifiable documents and per-unit reporting reduce the ambiguity further, because the record of what was agreed travels with the payment rather than being reassembled afterwards.

Reducing hops helps too. A payment that settles internally between participants, rather than travelling through external rails, produces fewer records and no in-transit deductions to explain. Netting has a similar effect: offsetting flows that cancel internally never generate the external records that would need matching.

The operational point

Reconciliation is usually treated as a back-office cost. It is better understood as a signal of design quality. A payment path that produces many divergent records is telling you something about the architecture, not just about the team matching them.

In short

  • One payment produces records in several systems, in several formats.
  • Timing gaps and in-transit deductions break simple matching.
  • Traceable attribution to principal, agent and policy makes matching structural.
  • Fewer hops mean fewer records to reconcile.
  • Reconciliation load is a signal of design quality.

For the treasury and CFO view of operations, see /business/.