Trade reconciliation is the process of matching executed trades — as recorded by the investment manager — against confirmations received from brokers and settlement instructions acknowledged by custodians. It ensures every buy, sell, or transfer is accurately captured in all systems before settlement.
Why trade reconciliation matters
A trade that is recorded incorrectly — or not recorded at all — will eventually surface as a position break, a cash discrepancy, or a failed settlement. But by then, the cost of resolution is significantly higher: failed settlements carry financial penalties, counterparty relationships suffer, and regulatory reporting may already be wrong.
Trade reconciliation is the earliest point at which errors can be caught. Catching a break at trade date (T+0) gives the operations team a full settlement cycle to resolve it. Catching it after settlement means unwinding transactions, booking corrections, and potentially compensating counterparties.
The trade reconciliation process
The process operates on three data sources that must agree:
- Internal trade record — what the portfolio manager or trader executed, as captured in the order management system (OMS) or portfolio accounting system.
- Broker confirmation — the broker's record of the trade, typically received via FIX protocol, SWIFT MT515, or email confirmation.
- Custodian instruction acknowledgement — confirmation that the custodian has received and accepted the settlement instruction.
Step 1: Trade capture verification
Immediately after execution, verify that the trade is recorded in the internal system with the correct details: security, quantity, price, trade date, settlement date, counterparty, and commission. For block trades, verify that allocations to sub-accounts sum to the block total.
Step 2: Broker confirmation matching
Match the internal trade record against the broker's confirmation. Key fields to compare:
| Field | What to check | Common break cause |
|---|---|---|
| Security identifier | ISIN/CUSIP/SEDOL match | Wrong line selected in OMS |
| Quantity | Exact match (no tolerance) | Partial fill not updated |
| Price | Match within market tolerance | Average price vs. fill price confusion |
| Settlement date | Same value date | Holiday calendar mismatch |
| Counterparty | Correct broker/dealer ID | Executing broker vs. clearing broker confusion |
| Commission/fees | Within agreed schedule | Incorrect fee tier applied |
Step 3: Settlement instruction matching
Once the trade is confirmed with the broker, a settlement instruction is sent to the custodian. The custodian acknowledges receipt and confirms the instruction is matched with the counterparty's custodian. Breaks at this stage typically indicate SSI (Standard Settlement Instruction) errors or counterparty mismatches.
Step 4: Break investigation and resolution
Unmatched trades enter an exception queue. Each break requires investigation:
- Is the trade missing from the broker confirmation? (Possible: trade not executed, confirmation delayed, wrong account)
- Do the details disagree? (Possible: partial fill, price amendment, wrong settlement date)
- Is the custodian rejecting the instruction? (Possible: wrong SSI, insufficient holdings for a sell, account frozen)
Trade reconciliation in different contexts
Equity and fixed income
Standard securities follow well-established matching protocols. Most breaks are resolved by comparing trade tickets and confirmations field by field. The main challenge is volume — a large asset manager may execute thousands of trades daily.
OTC derivatives
OTC trades (swaps, forwards, options) are more complex. Confirmations are often negotiated documents rather than standardised messages. Matching requires comparing economic terms (notional, rate, maturity, payment dates) rather than simple quantity and price.
Block trades and allocations
A block trade executed for multiple accounts must be allocated correctly. The block-level confirmation from the broker must match the sum of allocations, and each allocation must be instructed to the custodian separately. Allocation errors are a frequent source of breaks.
The settlement compression problem
With most major markets now operating on T+1 settlement (the US moved to T+1 in May 2024, the EU is targeting 2027), the window for catching and resolving trade breaks has halved. Operations teams that previously had two business days to investigate now have one. This compression makes same-day trade reconciliation essential — breaks must be identified on trade date, not the day after.
Where agents fit
Trade matching itself is well-served by existing middleware (CTM, ALERT, TradeSuite). The persistent challenge is investigating and resolving the exceptions — the trades that do not auto-match. An agent can examine a trade break, check whether a partial fill explains the quantity difference, verify settlement dates against the correct holiday calendar, contact the broker's system for an updated confirmation, and either resolve or escalate with full context.
For firms looking for operational support with trade and position reconciliation, our virtual family office service handles the full reconciliation lifecycle — from data ingestion through break resolution.
Key terms
- Trade date (T)
- The date on which a trade is executed.
- Settlement date (T+n)
- The date on which securities and cash are exchanged. T+1 means one business day after trade date.
- Broker confirmation
- The broker's official record of a trade's terms, sent to the investment manager for verification.
- SSI (Standard Settlement Instructions)
- Pre-agreed instructions that tell the custodian where to deliver or receive securities and cash.
- Block trade
- A single large trade executed on behalf of multiple accounts, which must be allocated post-execution.
- Failed settlement
- A trade that does not settle on its intended settlement date, typically due to unresolved breaks or insufficient holdings.