Payments - Introduction / Learning brief
Reconciliation in payments
Your notes
In simple terms / 01
What this means in plain language
Explains how banks match internal ledgers against nostro statements and clearing reports to prove recorded money equals actual money, and how unmatched items, called breaks, are found, investigated, and cleared.
Reconciliation is the daily discipline of proving that what a bank's own records say happened matches what actually happened, using independent evidence. The flagship case is nostro reconciliation. A nostro account is an account a bank holds at another bank — “our account on your books” — and the bank keeps its own shadow record of it. Each day the servicing bank sends a statement of what really moved through the account, and a matching process pairs each statement line against the entry the bank expected. Lines that pair are, satisfyingly, boring. Lines that do not pair are called breaks: money that arrived unannounced, a payment sent but not showing, or an amount that differs. Most breaks have mundane causes — timing across midnight, a fee deducted along the way, a truncated reference, a duplicate from a resend — but each one must be explained, because the rare serious cause is exactly what the control exists to catch.
Complete lesson / 02
Understand the full idea, step by step
You keep a note of what you spent this month, then open your bank statement to check the two agree. Most lines match; one you cannot place. That small ritual — comparing your own record against an independent one, and chasing whatever does not line up — is exactly what a bank does at industrial scale, every day, over accounts worth far more than a monthly budget.
Reconciliation — matching recorded money against independently reported money
Reconciliation compares what a bank's ledger expected against what an independent source says actually happened, line by line, and treats anything that fails to pair as something to be explained. It is not tidying the books after the fact — it is the control that turns an assumption a payment completed into evidence that it did. The flagship case is nostro reconciliation: matching the bank's internal shadow of its correspondent account against the statement the correspondent itself sends.
Two records of the same account
Bank Alfa keeps its own running figure for the account it holds at Meridian Bank — its nostro, updated every time it thinks a payment moved. Meridian Bank, the bank that actually services the account, sends its own statement of what really hit it. Historically that arrived as an end-of-day MT940 customer statement, with intraday credits confirmed by messages such as the MT910; the ISO 20022 world carries the same information in camt statement and notification messages. Two records, one account. Reconciliation is the discipline of proving they say the same thing — and investigating every line where they do not.
Maya's break at a glance
- Account
- Bank Alfa's nostro at Meridian Bank
- Statement line
- Credit EUR 3,250.00, value date today
- Matching ledger entry
- None — the engine found nothing to pair it with
- Break type
- Statement item with no internal record
- Status
- Parked in suspense, clock running, owner Maya
From statement to cleared break
- SETTLEMENT
Meridian Bank's statement of the nostro arrives, listing every movement it recorded against the account.
- LEDGER
The matching engine runs its first pass: pair each statement line to a ledger entry on an exact reference match.
- LEDGER
Lines that miss go to looser passes — amount and value date within a small tolerance, then heuristics — until only genuinely unmatched items remain.
- LEDGER
The EUR 3,250.00 credit survives every pass unmatched and is flagged as a break, then parked in a suspense account with an aging clock.
- NOTIFICATION
Maya investigates, quoting the statement reference: she finds an incoming customer credit whose reference was truncated in transit, so auto-matching never saw it.
- LEDGER
She matches the credit to the waiting payment, applies it to the customer, and clears the break — then reports the truncation so the source can be fixed.
Break — a line that will not reconcile
A break is any item that reconciliation cannot pair. They come in three plain shapes: an entry in the bank's records with no matching statement line, a statement line with no matching internal entry (Maya's case), or a pair that matches on everything except the amount. Most breaks are ordinary — timing gaps, fees, truncated references, a duplicate from a resend — and each is still resolved on its own, because the entire point of the control is catching the rare item that is not ordinary.
COMMON CONFUSION
“If the statement and the ledger disagree, post an entry to make them match so the account reconciles today.”
Forcing an entry only hides the break; it does not explain it. Real money either moved or it did not, and reconciliation exists to find out which. An unexplained item is parked in suspense with the clock running and chased until its cause is known — a suspense balance that only grows is a control failure in slow motion.
STRICTLY SPEAKING
Strictly speaking, reconciliation only works when it is independent: performed by people and systems separate from those that execute the payments, because a team checking its own work catches nothing. Add an aging limit and a named owner on every break, plus a month-end attestation where someone signs that each account reconciles, and the daily grind becomes a formal, auditable control. Instant rails are also shifting the rhythm from an end-of-day batch toward continuous matching against real-time confirmations.
FOR NOW, REMEMBER
- Reconciliation matches the bank's own ledger against an independent record — classically a correspondent's nostro statement — and proves recorded money equals real money.
- Anything that will not pair is a break, in one of three shapes: only in the ledger, only on the statement, or matched but for a different amount.
- Breaks are parked in suspense with an aging clock and a named owner, and cleared by explanation — never by a plug entry that just makes the report balance.
- The control only has value if it is independent of the teams that make the payments.
TRY IT YOURSELF
Maya finds a EUR 3,250.00 credit on the Meridian Bank nostro statement with no matching entry in Bank Alfa's ledger. What is the sound next step?
A break that turns out to be a payment stuck, misdirected, or claimed missing does not close at the ledger — it becomes a case. Next: how operations teams triage exceptions and run investigations to the point where the money and the record finally agree.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Reconciliation proves recorded money equals actual money by matching internal ledgers against independent statements.
- 02
Unmatched items are called breaks, and every break must be explained even though most causes are mundane.
- 03
The control's value comes from its independence, so it must be run separately from the teams that execute payments.
Practical use cases / 04
Where you would use this
A reconciliation analyst investigates a break where an incoming credit has no matching expected entry.
An operations manager tracks the aging of open breaks and escalates any item past its limit.
A controller signs a month-end attestation confirming that each nostro account reconciles.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, expects a USD 250,000.00 incoming credit on its nostro account at another fictional bank, Northwind New York, valued 2026-05-12. The statement shows only USD 249,975.00. The matching engine cannot pair the two amounts exactly, so it raises a break of USD 25.00. An analyst reads the statement narrative, finds that an intermediary bank deducted a USD 25.00 charge in transit, records the fee against the expected entry, and clears the break. The account now reconciles, and the recurring fee becomes a note for whoever negotiates that correspondent relationship.
Evidence & review / 07
Evidence & review
Nostro and settlement-account reconciliation at correspondent and clearing/settlement mechanisms; specific tooling, team placement and automation levels vary by institution.
What this brief simplifies: Presents a single illustrative break and a linear matching sequence; production engines run many passes, handle one-to-many netted lines, and differ in message formats and thresholds.
Sources for this brief4
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
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.
- Official requirement
Principles for financial market infrastructures ↗ — CPMI and IOSCO (Bank for International Settlements) · Segregation of duties; reconciliation as an operational control
Published by the CPSS (now CPMI) and IOSCO; contains 24 principles plus responsibilities for authorities. This site uses it only for high-level concepts such as settlement finality.
- Scheme-specific rule
Swift Standards MT (annual standards releases) ↗ — Swift · MT940 statement message; MT910 confirmation of credit
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.
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt statement and notification message definitions
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.