Skip to content
Bankautomation

Nostro account reconciliation, the daily process explained properly

Published 15 July 2026

9 min read

nostro account reconciliation

camt.053 · NOSTRO USD · value date 03 sep 2026

Nostro cash break, sample data

Match rate

75.0%

Breaks

4

At risk

$533.9k

Oldest

4d

Date ±1d
Amount

This console matches the first rows a side. It left out statement and ledger , so anything in them is not counted below. To run a full file, .

BRK-001

Aged 0d

$219,105.40

2026-09-03 · both sides

REF//FX/SPOT/7741 · INTERBANK FX DESK

Amount differs by 164.80 USD (0.075%)

Re-price the ledger leg on the correspondent rate source for the value date and post 164.80 USD to FX variance.

FX RATE SOURCE

→ Treasury Ops

BRK-002

Aged 4d

$187,650.00

2026-08-30 · ledger

PAY/90012/R · KESTREL LOGISTICS

Second ledger entry for 187,650.00 USD against REF//PAY/90012

Confirm the original entry REF//PAY/90012 cleared, then reverse this posting under maker-checker and note the reversal on the original item.

DUPLICATE POSTING

→ Finance

BRK-003

Aged 0d

$123,760.00

2026-09-03 · both sides

REF//TRF/554121 · HALCYON TRADING

Statement 61,880.00 vs ledger 123,760.00 (50% short)

Split the ledger posting and match the settled leg; leave the residual 61,880.00 USD open against the same reference.

PARTIAL SETTLEMENT

→ Payments Ops

BRK-004

Aged 0d

$3,410.00

2026-09-03 · statement

REF//CHG/Q3FEES · CORRESPONDENT CHARGES

On the statement, nothing in the ledger

Post 3,410.00 USD to the charges account for the period and add it to the standing accrual so it stops surfacing as a break.

FEE NOT ACCRUED

→ Finance

Everything matched under these tolerances.

Tighten the date or amount tolerance to see the breaks it was absorbing.

Correspondent statement

camt.053 · NOSTRO USD

Value date Reference Amount
2026-09-02 REF//NONREF/2026090301 1,284,500.00
2026-09-02 REF//INV/88231 96,400.00
2026-09-03 REF//TRF/554120 452,180.25
2026-09-03 REF//FX/SPOT/7741 218,940.60
2026-09-01 REF//SEPA/33421 74,220.00
2026-09-03 REF//CHG/Q3FEES 3,410.00
2026-09-03 REF//TRF/554121 61,880.00
2026-09-02 REF//PAY/90012 187,650.00
2026-09-02 REF//INV/88245 242,015.00
2026-09-03 REF//TRF/554133 18,905.50
2026-09-01 REF//PAY/90044 505,300.00
2026-09-03 REF//INV/88260 132,640.75

Internal nostro ledger

Core banking export

Value date Reference Amount
2026-09-02 NONREF/2026090301 1,284,500.00
2026-09-02 INV/88231 96,400.00
2026-09-03 TRF/554120 452,180.25
2026-09-03 FX/SPOT/7741 219,105.40
2026-08-31 SEPA/33421 74,220.00
2026-09-02 PAY/90012 187,650.00
2026-09-03 TRF/554121 123,760.00
2026-08-30 PAY/90012/R 187,650.00
2026-09-02 INV/88245 242,015.00
2026-09-03 TRF/554133 18,905.50
2026-09-01 PAY/90044 505,300.00
2026-09-03 INV/88260 132,640.75
Matched pairs are tinted on both sides. Breaks carry the brass left rule and appear in the worklist.

Sample data only. Matching runs in your browser; classification is written by the model when you press Run. Matching done in your browser. Writing classifications… Classifications written by the model on this run. Decision support, not a compliance determination. The classification model was unavailable, so the built-in rule classifier wrote these. Same matching, same numbers. This console classifies up to 12 runs a minute and this run went over, so the built-in rule classifier wrote these. Same matching, same numbers. Wait a minute for the model, or . The model wrote the first 8 classifications; the rule classifier wrote the remaining .

Open the full resolver

A nostro account is your account, held by another bank, denominated in their local currency. You keep a mirror of it in your own ledger. Nostro reconciliation is the daily proof that the two agree, and it is where a bank first discovers whether its payment operation is under control.

The two records

The correspondent sends a statement: what they posted to your account, in their sequence, on their value dates, priced on their rate source where currency conversion was involved. Your own systems produce the mirror: what you instructed and what you expected. The two are describing the same money and will differ every day for reasons that are entirely normal.

A day, in order

Step 01

Intraday view

MT942 or camt.052 and camt.054 messages arrive during the day. Matched against pending items they give an early picture, which is the only version of the picture that is still actionable for funding decisions.

Step 02

End of day statement

camt.053 or MT940 arrives after the correspondent cut-off. This is the authoritative external record for the value date.

Step 03

Match

Exact key match on normalized reference, amount and value date, then a tolerance pass for timing and rate source differences under approved rules.

Step 04

Work the breaks

What is left is classified, aged from the value date, routed to treasury, payments or finance, and worked with the evidence attached.

Step 05

Position and proof

The reconciled position feeds liquidity reporting, and the evidence for the day is complete before anyone goes home.

The six differences, and what each one means

FX rate source

Same reference, same value date, amounts a fraction of a percent apart. The correspondent priced the conversion on their source and you priced it on yours. This is a variance to post, not a mystery to investigate, and it should be a configured tolerance with an approved percentage rather than a daily judgement call.

Timing and value date

Same amount, different date. Cut-off times and time zones mean an item posted on your Tuesday lands on their Wednesday. Set the window per correspondent. A single global window is either too tight for the far correspondents or too loose for the near ones.

Charges not accrued

Correspondent fees, lifting fees and periodic charges are deducted at source. If the accrual does not expect them, the amount will never agree. Every one of these that surfaces daily is an accrual that should be fixed once.

Duplicate posting

A re-presented instruction or a replayed batch posts twice on one side. The reversal is a maker-checker action with a reason code, and the original item should carry a note that a duplicate was found against it.

Partial settlement

One side settled short. The correct handling is to split, match the settled leg and leave the residual open against the same reference, so the outstanding exposure stays visible instead of being absorbed by a wide amount tolerance.

Missing reference

Something exists on one side with nothing to tie it to. This is the class that becomes a correspondent investigation, and it is the class that shrinks most when structured payment data survives the chain.

Why the aging number is the one to watch

Break counts fluctuate with volume and mean little in isolation. Age does not. An item open for four days on a nostro account is either a genuine dispute with a correspondent or a decision nobody has been willing to make. Both are worth surfacing on the first screen, which is why the resolver in this site puts the oldest break in the header strip next to the value at risk.

Nostro, vostro and loro, settled once

The vocabulary causes more confusion than it should, and it is worth fixing in one paragraph. A nostro account is our money held in their books, usually in their currency. A vostro account is their money held in our books, usually in our currency. Loro is the same relationship described from a third party position and appears mostly in older documentation. The account is one account; the name depends on who is speaking.

Operationally the distinction matters because the reconciliation is different in shape. For a nostro, the external record is a statement you receive and cannot control, and the internal record is your mirror. For a vostro, you are the record keeper: you produce the statement, and the reconciliation is between your ledger and what the account holder believes. Breaks on a vostro tend to arrive as queries rather than as unmatched rows, and the evidence you need is the evidence you already hold.

The mirror is where most problems begin

The internal side of a nostro reconciliation is often called the mirror, and how it is maintained determines how much work the reconciliation is. If the mirror is updated when a payment is instructed, it will differ from the statement by everything that has been instructed and not yet settled, which is a normal and predictable population. If the mirror is updated when settlement is assumed, it will differ by everything the assumption got wrong, which is not predictable at all.

The useful discipline is that the mirror should record the state a payment is in, not just its existence. An item that is instructed, an item that is confirmed by the correspondent and an item that has appeared on a statement are three states, and a reconciliation that can distinguish them turns most timing differences into expected items rather than into breaks.

Intraday, and why it is a funding question

End of day reconciliation proves what happened. Intraday reconciliation supports a decision that can still be made. The distinction is the entire argument for reading camt.052 and camt.054, or MT942, rather than waiting for the statement.

MessageWhat it carriesWhat the desk can do with it
camt.052 or MT942 Intraday report of activity so far See the position developing and match against pending items
camt.054 debit and credit notification Individual entry level notification Confirm a specific expected item without waiting
camt.053 or MT940 End of day statement, authoritative Prove the day and close the reconciliation
camt.056 Cancellation request Tie a cancellation to the original before it becomes a mystery
pacs.002 Status report on an instruction Distinguish rejected from delayed, which changes the funding decision

Swipe the table sideways to read every column.

The funding argument is concrete. A treasury team that knows at eleven in the morning that a large expected receipt has not arrived can act. The same team learning it from a statement the next morning is describing history. Reconciliation timeliness on a nostro account is a liquidity capability before it is a control capability, and it is usually easier to fund on that basis.

Correspondent charges, in more detail than they usually get

Charges deserve their own section because they generate a disproportionate share of small breaks and because they are almost entirely predictable. There are three common shapes. A per item charge deducted from the amount, which makes what arrives smaller than what was sent. A lifting fee taken by an intermediary, which does the same thing in the middle of the chain. And a periodic charge posted separately, monthly or quarterly, which appears on the statement with nothing in the ledger to meet it.

Each has a correct handling and none of them is a wider amount tolerance. The per item and lifting charges should be predicted from the charge bearer instruction and the correspondent agreement, so the expected settlement amount is the net figure. The periodic charge should be accrued so that a posting exists to match. A charge that surfaces daily as a break is an accrual decision that has never been made, and it will keep surfacing until it is.

The correspondent conversation

Some breaks cannot be resolved internally, and the quality of the correspondent relationship decides how quickly they clear. Two habits make a large difference. The first is quoting a single identifier rather than describing a payment: a uetr or an end to end id turns a discussion into a lookup. The second is tracking investigations as items with an age, in the same worklist as everything else, rather than in an email folder. An investigation that is not aged is an investigation that closes when someone remembers it.

A practical review to run once a quarter: list open items by correspondent and by age. Concentrations are informative. One correspondent holding most of the aged population is either a data problem worth fixing or a relationship conversation worth having.

The liquidity argument

The control case for nostro reconciliation is accuracy. The commercial case is liquidity: unreconciled balances are cash you are holding because you cannot prove you can use it. Every day the reconciliation is timely, the treasury team is working with a real position instead of a cautious one.

Account structure, and a cost most banks under-examine

The number of nostro accounts a bank holds is a decision with a running cost, and it is frequently inherited rather than chosen. Each account carries a statement to ingest, a set of tolerances to maintain, a relationship to manage, charges to accrue and a balance that has to be funded. Consolidating currencies onto fewer correspondents reduces all of that, at the price of concentration and, sometimes, of losing a corridor where the remaining correspondent is weak.

The reconciliation view of the question is a useful input to it, because the data answers it directly. Rank accounts by break volume, by aged break value and by the proportion of items requiring an investigation. Accounts that are expensive to reconcile are usually expensive for structural reasons: a correspondent with poor reference handling, a corridor with heavy charge deductions, or a low volume relationship that nobody has time to keep clean. That ranking is a better basis for a rationalisation discussion than a balance sheet view alone.

What a good nostro control looks like on a Tuesday

  • Intraday reports are read and matched against pending items during the day, not stored for later.
  • The end of day statement arrives on a schedule and is ingested without a person pressing anything.
  • Exact match rate is high and stable, and the tolerance band is small, per correspondent, and approved.
  • Charges are accrued or predicted, so a fee difference is an expected item rather than an investigation.
  • Every open item has a classification, an owner and an age counted from the value date.
  • The oldest item is visible on the first screen anyone looks at, next to the value at risk.
  • Evidence for the day exists because the work was recorded, not because someone assembled it.

None of that requires heroics. It requires the data to arrive reliably, the tolerances to be decisions rather than habits, and the residue to be treated as work with an owner instead of as a report with a distribution list.

Product detail is on nostro reconciliation automation, and the sample dataset in the resolver is exactly this reconciliation, including an FX rate source break and a charge nobody accrued.

Get started

Put your first reconciliation on rails

Create an account, and we will email you how onboarding works and what a first source connection looks like. The Reconciliation Break Resolver is open to try right now, on sample data, without an account.

Run the demo

No card required to create an account. Sample data only in the demo. Bankautomation is operations software, not a regulated service.