Nostro Reconciliation: Full Guide for Cross-Border Payments
Your client paid you two weeks ago. Your bank says the payment is pending. The correspondent bank says it was processed. And somewhere between those two statements, there is a $4,000 gap nobody can explain.
This is what happens when nostro reconciliation breaks down.
If you export goods or services and receive international payments, this process affects how fast your money moves, whether your bank's records match reality, and whether you stay on the right side of RBI compliance.
TL;DR - Summary
- What it is: - Nostro reconciliation is the process of matching a bank's internal foreign currency records with official statements from its correspondent banks.
- Purpose: - Banks do this to maintain accuracy, catch discrepancies early, and manage liquidity across international accounts.
- Why it matters: - Unreconciled items slow cross-border payment settlements and delay confirmation for businesses awaiting funds.
- Business relevance: - For Indian exporters and freelancers, your bank's reconciliation efficiency directly affects how fast international payments arrive and get confirmed.
What is nostro reconciliation?
Internal Ledger
Bank's own record of expected transactionsExport payment from US client
$50,000Outward payment to Germany
−$12,000Fee posting — JPMorgan
−$25Interest credit
+$14matches
these
External Statement
Correspondent bank's report (SWIFT MT940)Inward credit received
$50,000Outward payment processed
−$12,000Correspondent fee deducted
−$25Entry not yet reflected
—✓ Matched — entry closed
Reference numbers, amounts and value dates all align
✗ Break — investigation required
Interest credit present in ledger but not yet on correspondent's statement
Nostro reconciliation is the process of matching a bank's internal mirror ledger of its foreign currency accounts against the actual statements received from correspondent banks abroad.
Every Indian bank maintains two records for each nostro account: its own internal ledger of expected transactions, and the official statement from the correspondent bank showing what actually happened.
How banks use nostro reconciliation daily
Here's how this works in practice:
Say Kotak Mahindra Bank in India needs to pay a US supplier $50,000 on behalf of an Indian manufacturing company. Kotak routes this through its USD nostro account held with JPMorgan Chase in New York. Kotak's internal system records a $50,000 debit from that nostro account on Monday.
By Tuesday, JPMorgan sends an account statement via SWIFT. Kotak's reconciliation team pulls both sets of records and starts matching them. If JPMorgan's statement shows the same $50,000 debit with a matching reference number and value date, the entry is closed cleanly.
But if JPMorgan's statement shows $49,975 because a $25 correspondent fee was deducted, that $25 gap shows up as an unmatched break. Someone has to investigate, identify it as a fee deduction, and record it correctly before the entry can be closed.
Key components of the reconciliation process
- Internal ledger: The bank's own record of every transaction expected to hit the nostro account, maintained in its core banking system
- External statement: The official account statement from the correspondent bank, typically delivered via SWIFT MT940 or MT950 messages
- Matching rules: Automated or manual criteria used to pair internal entries with external ones, based on reference numbers, amounts, value dates, and currency
- Exception items: Unmatched or partially matched entries that need manual investigation before the account can be considered fully reconciled
Why does nostro reconciliation matter for international payments?
When nostro records don't match, payments stall. Here's what that costs you:
Impact on payment settlement timelines
Unreconciled items hold up payment confirmation. Your bank won't officially confirm that funds have arrived until its internal records match what the correspondent bank is reporting. If there's a gap between those two records, someone has to investigate before anything can move forward.
For a business waiting on a $30,000 export payment to clear, that investigation period can stretch into days. Your EDPMS entry stays open, your eBRC isn't generated, and your cash flow takes a hit.
Ensuring transaction accuracy and compliance
Reconciliation is also how banks catch things that shouldn't have happened.
- Failed payments that were debited but never reached the beneficiary.
- Duplicate entries where the same transaction was posted twice.
- Unauthorized debits with no clear reference or purpose.
Each of these creates a discrepancy between the internal ledger and the external statement. The reconciliation process surfaces them so they can be corrected before they compound.
From a compliance standpoint, this matters too. RBI requires banks to maintain strong reconciliation, reporting, and internal control systems for all foreign currency accounts under FEMA. Clean reconciliation records are what an auditor or RBI inspector reviews when assessing a bank's foreign currency operations.
For exporters, this directly relates to whether your inward remittances are properly recorded and whether your documentation holds up during tax filing or a GST refund claim.
Managing bank liquidity and cash flow
Nostro accounts need to hold enough foreign currency to settle payments, but not too much. Excess funds sitting idle in a USD account in New York are earning nothing and tying up capital that could be put to work elsewhere.
Banks need to monitor the funds in their overseas accounts via daily debit and credit updates, and end-of-day statements. The operational work involved and the lack of visibility into available funds, resulting in overfunding the account, represent a significant portion of the cost of making cross-border payments.
Accurate reconciliation gives banks a clear picture of their actual nostro balances in real time. That visibility lets them:
- Fund the account appropriately
- Release payments confidently
- Avoid the twin problems of overfunding (excess idle capital)
- Underfunding (failed payments due to insufficient balance)
A well-managed nostro position means your bank can process inward remittances faster, without waiting to verify available balances.
Pro Tip
When your international payment takes longer than expected, it may be stuck in nostro reconciliation. Ask your bank for the SWIFT confirmation number and use it to track the funds' progress through the correspondent banking chain. Most AD banks can trace this within 24 to 48 hours.
How does the nostro reconciliation process work?
Hover over each step to expand
80–90% auto-matched · remainder flagged for review
Most breaks are timing differences — not errors
The reconciliation process follows a clear sequence, whether it's being done manually by a bank's operations team or handled by automated software.
1. Transaction identification and data extraction
Before anything can be matched, the bank needs both sets of records in one place.
The internal side comes from the bank's core banking system, which logs every transaction posted to the nostro account, including:
- Outward payments
- Incoming credits
- Fee postings
- Interest entries
The external side comes from the correspondent bank, usually in the form of a SWIFT MT940 or MT950 message.
MT940 is an end-of-day statement showing the full transaction history.
MT950 is a shorter balance confirmation.
Some correspondent banks now send data in ISO 20022 format, which carries richer transaction details and is gradually replacing older SWIFT message types.
Both sets of data are then pulled into the reconciliation system, cleaned up, and formatted consistently so they can be compared. That’s because different correspondent banks use different field structures, date formats, and reference number conventions.
2. Matching entries across systems
Once the data is in, the matching begins. Every debit and credit in the internal ledger gets compared against the corresponding entry in the correspondent's statement, using a combination of reference numbers, transaction amounts, value dates, and currency codes.
In automated systems, matching rules handle the bulk of this. Rules can also allow a small dollar tolerance to account for fee deductions mid-chain. Entries that meet the criteria get matched and closed automatically.
What doesn't meet the criteria, the system flags it for manual review. A reconciliation analyst then reviews each flagged item individually, assesses whether there's a logical explanation, and either matches it manually or escalates it for further investigation.
In high-volume banks processing thousands of international transactions daily, automated matching typically handles 80 to 90 percent of entries. The remaining 10 to 20 percent is where the real work happens.
3. Detecting and investigating discrepancies
Any entry that can't be matched becomes an exception item, also called a break. The reconciliation team has to determine the cause before the account can be considered clean.
The analyst traces the transaction through SWIFT, checks with the correspondent bank if needed, and determines whether the break is a timing issue that will self-resolve, an error requiring a correction entry, or something more serious that requires escalation.
Common Mistake
A reconciliation break doesn't always mean something went wrong. The majority of breaks are timing differences that resolve on their own within one to two business days. The problem is when they're left uninvestigated, because a benign timing gap looks identical to a genuine error until someone checks.
4. Resolving exceptions and confirming balances
Once every exception has been either matched, explained, or corrected, the reconciliation moves to its final stage.
The team confirms that the closing balance on the internal ledger matches the closing balance on the correspondent's statement for that period. If they match, the reconciliation is complete and signed off. If they don't, the remaining difference is investigated further before sign-off can happen.
The completed reconciliation becomes part of the bank's audit trail.
For Indian banks operating under FEMA, this documentation is reviewed by RBI inspectors during supervisory audits.
What are common challenges in nostro reconciliation?
The reality involves multiple time zones, inconsistent data formats, and transaction volumes that make manual oversight genuinely difficult.
Time zone and cut-off differences
Every correspondent bank has its own end-of-day cut-off. When your Indian bank sends a payment at 6 PM IST, whether that transaction lands on today's statement or tomorrow's depends entirely on the US correspondent's cut-off time.
The result: two records of the same transaction carry different value dates. The matching system flags it as an exception, even though nothing went wrong.
Data format and messaging inconsistencies
Different correspondent banks send statements in different formats. Some use SWIFT MT940, some use older proprietary formats, and some have moved to ISO 20022. Field names, reference number lengths, and date formats don't always line up, so automated matching fails to recognize entries that are actually the same transaction.
The ISO 20022 transition is intended to address this over time by standardizing the structure of payment data globally. But with banks at different stages of adoption, format inconsistency remains a live problem.
Manual processing and human error
When automated matching can't close an exception, a person steps in. Each exception can take anywhere from minutes to several hours, depending on its complexity. In a bank processing thousands of daily transactions, the exception queue alone can consume an entire operations team's bandwidth.
Liquidity and overfunding risks
Poor reconciliation creates a visibility problem. If a bank can't clearly see its actual nostro balance, it either funds the account conservatively and risks failed payments or funds it generously and ties up excess capital that sits idle abroad.
The lack of visibility into available funds, resulting in overfunding the account, results in a significant portion of the cost of making cross-border payments. For exporters, this shows up as slower payment confirmations, as banks work through backlogged reconciliations before they can verify actual balances.
Reconciliation delays often cascade. A single unresolved exception can delay confirmation of multiple related transactions. If your payment is part of a batch that includes an exception item, your confirmation waits too, even if your specific transaction matched cleanly.
What are the best practices for nostro reconciliation?
Implement automated reconciliation tools
Manual matching doesn't scale. Automated software matches transactions in real time and flags exceptions immediately. Modern tools use AI and machine learning to recognize recurring patterns, so a correspondent bank that consistently deducts a fixed fee no longer requires a manual exception.
Standardize data formats and messaging
Many breaks happen before matching even begins, at the data cleaning stage. Adopting ISO 20022 reduces friction by introducing richer, more structured payment data.
Establish clear exception handling procedures
Every exception needs an owner, a deadline, and a documented resolution. Clear escalation procedures define how long a break can stay open, who approves correction entries, and how resolutions get recorded for audit purposes.
Conduct regular audits and reviews
Reconciliation processes drift over time as correspondent banks change formats and transaction volumes grow. Periodic reviews of exception volumes and resolution timelines help catch inefficiencies before they become compliance gaps.
How is technology changing nostro reconciliation?
Distributed Ledger Technology
Real-time nostro visibility
Shared ledgers allow banks to see nostro balances and transaction status in real time — without waiting for end-of-day SWIFT statements. SWIFT tested this with 34 global banks.
Proof of conceptISO 20022 Messaging
Standardised payment data
Richer, structured payment data shrinks the manual exception queue. More precise matching rules mean fewer breaks from format mismatches between correspondent banks.
In adoptionAI and Machine Learning
Automated exception handling
AI identifies recurring exception patterns and builds resolution rules around them — reducing the manual queue to breaks that actually need human judgment.
Live at scaleDistributed ledger technology for real-time visibility
SWIFT led a proof of concept with 34 global transaction banks to explore whether distributed ledgers could help banks reconcile transactions and optimize nostro liquidity more efficiently in real time. The technology isn't mainstream yet, but the proof-of-concept showed enough promise that adoption conversations are ongoing
ISO 20022 and standardized payment messaging
ISO 20022 carries structured, detailed payment data that makes matching rules more precise and significantly shrinks the manual exception queue.
AI and machine learning for exception handling
AI automatically identifies recurring exception patterns and builds resolution rules around them, reducing the manual queue to exceptions that genuinely need human judgment. The manual queue shrinks to breaks that actually need a human.
As real-time reconciliation technology spreads, the gap between payment initiation and confirmation is shrinking, meaning faster settlement visibility for businesses receiving international payments.
How businesses can avoid payment delays from reconciliation issues
A few habits on your end can significantly cut the chances of your payment getting stuck:
- Provide complete payment references: Ask your client to include your invoice number in the payment description. Missing or vague references are one of the most common reasons a transaction can't be matched automatically.
- Use platforms with real-time tracking: Payment providers that show transaction status at each step give you visibility without having to chase your bank.
- Confirm correspondent banking routes: Ask your bank which correspondents are in the payment chain before sending or receiving a large payment. More hops mean more potential points of mismatch.
- Request SWIFT confirmation: For high-value payments, ask for a copy of the MT103. It shows the exact amount sent, deductions made, and reference details, which helps trace any breaks quickly.
Skydo removes this complexity entirely. With virtual accounts in USD, EUR, GBP, and more, plus real-time transaction tracking and transparent fees, you'll always know where your payment stands.
Your client pays locally, Skydo handles the correspondent banking behind the scenes, and every inward remittance comes with RBI-compliant documentation for FIRA and eBRC.
What is the difference between nostro and loro accounts?
A nostro account is your bank's foreign currency account held abroad. A loro account refers to a third bank's account in that same correspondent relationship, used mainly in complex trade finance arrangements.
Can small businesses be affected by nostro reconciliation delays?
How long does nostro reconciliation typically take?
Does automated reconciliation eliminate all discrepancies?
