Why nostro breaks are different
- Two calendars. Your value date and the correspondent's posting date are not the same thing, and a one day difference is normal rather than wrong.
- Their rate source. An FX leg priced on the correspondent's rate will not match your ledger to the cent, and the difference is a variance to post, not an error to investigate.
- Their charges. Fees deducted at source mean the amount that arrives is not the amount that was sent.
- Their references. Field 86 narrative and reference formatting differ per correspondent, sometimes per branch.
- Real exposure. An unreconciled nostro position is intraday liquidity you cannot see and cannot use.
A nostro control that holds
Step 01
Ingest both sides daily
camt.053 or MT940 from each correspondent, plus the internal nostro ledger export, on the same schedule and with duplicate file detection.
Step 02
Match per account, per correspondent
Tolerances configured for that relationship: the value date window their cut-off requires, the amount tolerance their rate source justifies, the reference normalization their format needs.
Step 03
Classify what is left
FX rate source, timing, charges, duplicates, partial settlement, missing reference. Each with an owner and an age from the value date.
Step 04
Prove it
The position, the open items, the approvals and the rule versions, exportable per account and period for treasury, audit and the correspondent conversation.
The sample in the resolver is a nostro break
The default dataset in the Reconciliation Break Resolver is a correspondent statement against an internal nostro ledger, with an FX rate source difference, a duplicate posting, a partial settlement and a charge that was never accrued. Move the value date window to zero and a timing break appears, exactly as it would on a real account with a correspondent in another time zone.
Intraday, not just end of day
End of day statements tell you what already happened. MT942 and camt.054 let a break be visible during the day, which is when a funding decision can still be made about it. The same matching runs more often, against pending items, with the end of day statement confirming or contradicting the intraday picture.
The mirror, and how it should be maintained
The internal side of a nostro reconciliation is the mirror of the correspondent's account, and how it is kept determines how much of the daily work is real. A mirror updated when a payment is instructed differs from the statement by everything instructed and not yet settled, which is a predictable and explainable population. A mirror updated when settlement is assumed differs by everything the assumption got wrong, which is not predictable at all.
The discipline that removes most of the noise is recording state rather than existence. Instructed, confirmed by the correspondent, and appearing on a statement are three different states of the same item. A reconciliation that can distinguish them converts most timing differences into expected items and leaves only the genuine breaks in the queue.
Tolerances per correspondent, not per bank
A single global value date window is either too tight for the distant correspondents or too loose for the near ones, and in practice it is usually both at once on different accounts. The same applies to amount tolerance, where an account that carries FX legs justifies a percentage tolerance that would be indefensible on a domestic account with no conversion.
| Relationship characteristic | Sensible tolerance shape | What it must not absorb |
|---|---|---|
| Distant time zone, late cut-off | Wider value date window, amount exact | A payment that never settled |
| FX conversion by the correspondent | Small percentage on amount | A partial settlement |
| Charges deducted at source | Charges modelled, amount exact | An unexpected fee that was never agreed |
| Low volume, high value | Exact on everything, manual review | Anything at all |
Charges, which produce more small breaks than anything else
Three shapes recur. A per item charge deducted from the amount, so what arrives is less than what was sent. A lifting fee taken by an intermediary in the middle of the chain, with the same effect. And a periodic charge posted separately, monthly or quarterly, appearing on the statement with nothing in the ledger to meet it. None of the three is correctly handled by a wider amount tolerance.
The correct handling is to predict the first two from the charge bearer instruction and the correspondent agreement, so the expected settlement amount is already the net figure, and to accrue the third so that a matching posting exists. A charge that surfaces as a break every day is an accrual decision that has not been made, and it will keep surfacing until it is.
The liquidity argument that funds the work
The control case for nostro reconciliation is accuracy, and it is usually not what gets the project funded. The commercial case is liquidity. An unreconciled balance is cash the bank is holding because it cannot yet prove it can use it, and a buffer held against uncertainty is a buffer that costs money every day it exists.
That reframing matters because it changes who sponsors the work. A treasury desk working from a reconciled intraday position funds to a real number rather than to a cautious one, and the difference between those two numbers, across a set of correspondent accounts, is usually larger than the cost of the reconciliation. It is also a number the treasury team can estimate themselves, which is a better basis for a business case than any figure a vendor could offer.
What automation actually removes from the nostro desk
It does not remove judgement, and it should not. What it removes is the part of the day spent reassembling the same picture before any judgement can be applied: pulling statements from several mailboxes and portals, normalizing four reference formats by hand, keying both sides into a workbook, and re-deriving yesterday's open items because the workbook was overwritten. That work is identical every morning, which is precisely what makes it worth handing to a machine.
| Step in the nostro day | Worked by hand | Automated |
|---|---|---|
| Collect both sides | Mailboxes, portals, manual download, no duplicate check | Scheduled ingestion per correspondent with duplicate file detection |
| Normalize references | Find and replace in a workbook, per correspondent | Per relationship normalization rules, versioned and approved |
| Match | Sort, eyeball, highlight | Exact pass then tolerance pass, with the firing rule recorded |
| Work the residue | Email to treasury, reply in two days, decision unrecorded | Classified item, owning queue, age from value date, audit note |
| Prove it at quarter end | Rebuilt from inboxes and file shares | Filtered export of items, approvals and rule versions |
Where this sits next to the rest of the control framework
Nostro reconciliation is the deepest bank-specific case, but it runs on the same engine as everything else on this site. The general mechanics are described in bank reconciliation software, the settlement-side companion is payment reconciliation software, and the format questions that sit underneath all of it are covered in ISO 20022 payment automation. The process walk-through is in the nostro reconciliation process, and the controls a procurement review will ask about are on the security page.
Questions about nostro reconciliation
Do you connect to our correspondents directly?
The day one path is the statement file each correspondent already sends you, camt.053 or MT940, ingested on a schedule with duplicate detection. Where a direct channel exists it can be configured as a source, but nothing waits on that to start reconciling.
Can tolerances differ per correspondent?
Yes, and they should. A distant correspondent with a late cut-off needs a wider value date window than a domestic one, and an account carrying FX legs justifies a percentage amount tolerance that would be indefensible elsewhere. Each tolerance is set on the relationship and versioned.
How are FX rate source differences handled?
A leg priced on the correspondent rate will not match your ledger to the cent. That is classified as an FX rate source variance with the two amounts and the implied difference shown, and routed as a variance to post rather than as an item to investigate.
Does it cover intraday, or only end of day?
Both. MT942 and camt.054 intraday reporting can be ingested and matched against pending items during the day, with the end of day statement confirming or contradicting that picture. Intraday is where a funding decision can still be made.
Is this a compliance determination?
No. Bankautomation is operations software. Classifications and suggested actions are decision support. The reconciliation, the approvals and the institution's obligations remain with the institution.