The Four Types of Reconciliation in a Bank

Reconciliation is the process of comparing two sets of records and identifying differences. In a capital markets context, this means comparing the bank's internal records against an external source of truth — a custodian's statement, a counterparty's position report, a CCP's portfolio — and investigating any differences that arise. Differences are called breaks.

Reconciliation is not glamorous, but it is one of the most important control disciplines in a markets business. A bank that does not reconcile its positions daily does not know whether its trades have settled, whether its P&L is accurate, or whether its regulatory reports are correct. The four main types of reconciliation serve different purposes and use different data sources — but all are essential.

Position reconciliation compares the trades and positions held in the front-office trading system against those in the back-office settlement system. These two systems maintain separate records of what has been traded, and discrepancies between them are a primary source of error.

Front-office systems (such as MUREX or a proprietary trading system) record trades as they are done — capturing the economics, booking the risk, generating the P&L. Back-office systems process those same trades for confirmation, settlement, and lifecycle management. In a perfectly integrated architecture, the two systems would always agree. In practice, they often do not, because:

• A trade was booked in the front-office system but not correctly fed to the back-office system (interface failure)
• A trade was amended in the back office (for example, to fix a settlement instruction error) but the amendment was not reflected in the front-office system
• A lifecycle event (option exercise, coupon payment) was processed in one system but not the other
• A novation or assignment was processed differently across the two systems

Position reconciliation breaks between front and back office are particularly dangerous because they mean the bank's risk and P&L calculations (which use front-office data) may be based on a different set of trades than the settlement obligations (which use back-office data). A large break — a trade that exists in the back office but not the front office — could mean a significant market risk position is not being managed.

Materiality thresholds. Not every break requires immediate escalation. Banks set materiality thresholds — typically defined by notional amount, market value, or DV01 — below which a break can be investigated and resolved on a normal timeline. Breaks above the threshold require immediate escalation to senior management and, in some cases, to the risk function.

Nostro reconciliation compares the bank's internal records of what should be in each of its correspondent bank accounts against the statements provided by those correspondent banks. As described elsewhere, a nostro account is the bank's account held at a correspondent in another currency or jurisdiction.

The bank maintains its own records of what should be in each nostro account: debits from outgoing payments, credits from incoming payments and securities settlements. The correspondent bank sends a statement (typically via SWIFT MT940 or MT950) showing the same account from their perspective. The reconciliation matches each item on the internal records against the corresponding item on the correspondent's statement.

Nostro breaks arise when:

• A payment was sent by the bank but has not yet appeared on the correspondent's statement (timing difference)
• The correspondent received a credit that the bank did not expect (unidentified credit — potentially a payment from a counterparty that was not correctly recorded)
• A payment was instructed with the wrong value date, causing a one-day timing break
• The bank sent duplicate payments (operational error requiring urgent reversal)

Nostro reconciliation must be completed every business day. Aged nostro breaks — items that have been outstanding for more than a few days — attract regulatory scrutiny and must be escalated. An unidentified credit sitting in a nostro account for 30 days is a significant concern for both auditors and regulators, as it may indicate a fraud or an uncorrected operational error.

P&L reconciliation compares the daily profit and loss calculated by the trading desk's own systems against the independently calculated P&L produced by the Product Control team. This is a critical control — it ensures that the P&L being reported to senior management and used for remuneration purposes is independently verified.

The trading desk produces its own P&L in real time throughout the day. Product Control produces an independent P&L after the market close, using independently sourced prices (not the prices in the trading system) and a complete accounting of all trades. The two P&Ls should agree — but frequently there are differences.

P&L breaks between the trading system and Product Control arise from:

• Pricing differences: the trading system and Product Control use different market data (different curves, different volatility surfaces). These are expected to be small for liquid instruments but can be large for complex or illiquid instruments.
• Trade population differences: a trade is in one system but not the other — typically caused by a booking error or an interface failure.
• Methodology differences: the trading system uses one pricing model; Product Control uses a slightly different one. These differences are documented as known model differences and must be reviewed regularly.
• Reserves and adjustments: Product Control applies reserves (bid-offer, model uncertainty, liquidity) that the trading system does not reflect. The P&L reconciliation must account for these.

P&L reconciliation is one of Product Control's core responsibilities. Material, unexplained differences must be investigated before the P&L can be signed off — and the sign-off process is typically time-pressured, as the P&L must be reported to management before the start of the next trading day.

Regulatory reconciliation compares the trades and positions reported to regulators (trade repositories, regulatory capital reports) against the internal records. This type of reconciliation has grown enormously in importance since the G20 commitments after the 2008 crisis mandated trade reporting for OTC derivatives.

Under EMIR (Europe) and Dodd-Frank (United States), every OTC derivative must be reported to a trade repository — Unavista, DTCC, or similar. The data reported must accurately reflect the trades on the bank's books. Regulatory reconciliation compares the population of trades in the trade repository against the internal position records and identifies:

• Trades that are in the internal records but not reported (reporting failure)
• Trades that are reported but no longer in the internal records (stale reports requiring cancellation)
• Trades where the reported terms differ from the internal terms (data quality issues)

Regulatory reconciliation failures can result in significant fines. The FCA has fined multiple banks for persistent EMIR reporting failures where regulatory reconciliation controls were inadequate. The CFTC in the United States has taken similar action under Dodd-Frank.

Regulatory reconciliation also extends to capital reporting: comparing the exposures used in RWA (risk-weighted asset) calculations against the actual trade population, and verifying that netting sets and collateral arrangements are correctly reflected in the capital models.