Nostro reconciliation
Matching what your ledgers say happened against what your correspondents say happened — and chasing every unexplained break until it is explained.
L0 Explain simply
An everyday analogy: you keep a diary of everything you spend, and once a month you sit down with the bank statement and tick items off against each other. Ticked lines are boring — boring is success. The interesting lines are the ones only in the diary (you thought you paid; did you?) or only on the statement (what is this charge?). A bank does exactly this, except the 'diary' is its own ledgers, the statements come from every bank where it holds an account, and the exercise runs every single day. Reconciliation is that tick-and-chase discipline — and the untickable leftovers, called breaks, are where errors, lost payments, and occasionally fraud first show themselves.
L1 Core concepts
Reconciliation compares what your ledgers expected against what actually happened, using independent evidence. The flagship case is nostro reconciliation: your ledger holds a shadow of each account you keep at other banks; the servicing bank sends statements — classically an end-of-day MT940, with intraday confirmations such as the MT910 — and a matching process pairs statement lines with expected ledger entries. Whatever fails to pair is a break: money that arrived unannounced, payments sent but not showing, amounts that differ. Break causes are usually mundane — timing across midnight, fees deducted en route, references truncated or reformatted, duplicates from a resend — but every break must be explained, because the rare non-mundane cause is exactly what the control exists to catch.
L2 Practitioner view
Practitioner reality is matching rules and break management. Engines match in passes: exact on reference, then amount-and-date within tolerance, then heuristics, then a human. Automation rates vary widely between institutions — reference quality from correspondents is the usual ceiling, since a servicing bank that truncates or rewrites references defeats exact matching at the source. Breaks get typed (ours-not-theirs, theirs-not-ours, amount difference), aged, owned, and escalated; unexplained items land in suspense with the clock running. One-to-many matching is the subtle skill: a single settlement line at a CSM can represent thousands of underlying payments netted together, so the engine must match a batch total against its members. Month-end attestation — a named person signing that each account reconciles — turns the daily grind into a formal control.
L3 Technical details
Two structural points complete the picture. First, segregation: reconciliation must be performed by people and systems independent of those executing payments, because its value as a control is exactly its independence — an engine team marking its own homework detects nothing. Second, the data plumbing: statement lines carry the servicing bank's reference, value date, and entry codes, and matching quality depends on those surviving the journey, which is why reference discipline upstream pays off here. Instant rails shift the rhythm from end-of-day batch toward continuous reconciliation against real-time confirmations and ISO 20022 statement equivalents, and settlement accounts at market infrastructures need the same treatment as commercial nostros. Institutions differ in tooling and team placement; the independence principle and the aging discipline are the constants.
Sources & standards1
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 9 — MT940 and MT910
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
Sources for this topic2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 9 — MT940 and MT910
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Matching passes, break categories, and attestation practices are described as a composite of common approaches; real reconciliation platforms, automation rates, and control frameworks vary substantially between institutions.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L3 — Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.