Trade Reconciliation
The systematic comparison of internal trade and position records against external sources to identify breaks and resolve them before they become settlement failures.
Definition
Trade reconciliation in securities operations is the systematic comparison of a firm's internal trade and position records against external sources — broker confirms, custodian statements, clearinghouse reports, and SWIFT settlement status messages — to identify discrepancies and resolve them within the settlement window. The objective is to ensure that the firm's system of record accurately reflects what has actually traded, settled, and is held in custody.
Reconciliation is the primary control that validates data integrity across the system of record. Without regular automated reconciliation against external sources, internal records can diverge from actual positions without detection — through booking errors, missed settlements, corporate action misprocessing, or data feed failures. Automated reconciliation systems eliminate the manual comparison step, matching records field by field and surfacing only exceptions that require human review; this automation is what makes reconciliation operationally viable at T+1 scale.
In a T+1 settlement environment, breaks discovered at end-of-day on trade date leave less than 24 hours before the settlement date. SEC Rule 15c6-2 (SEC Release No. 34-96930, February 2023) requires broker-dealers to establish written policies and procedures reasonably designed to achieve same-day affirmation of institutional trades — and intraday reconciliation is the operational mechanism that makes that requirement achievable. Running comparisons against broker execution reports and intermediate custodian data throughout trade date, rather than in overnight batch, gives operations teams enough time to investigate and resolve breaks before settlement instructions must be generated. Unresolved breaks increase the risk of settlement failure, which in the US carries consequences including mark-to-market charges, Reg SHO close-out obligations, and potential buy-in exposure; in Europe, CSDR's cash penalty regime applies daily charges on unsettled transactions.
SEC Rule 17a-3 requires broker-dealers to create records of positions and trades. Reconciliation against custodian statements and clearinghouse reports is the operational discipline that ensures those records accurately reflect actual holdings — not merely that records were created.
How it works
Reconciliation runs on a defined schedule — intraday and end-of-day for firms with significant volume, overnight batch for lower-volume operations — comparing internal records against external statements. Each comparison produces either a match or a break. The reconciliation process feeds directly into exception management: each break becomes a work item that must be classified, assigned, and resolved.
The three primary reconciliation types in securities operations have distinct data sources and failure modes:
Position reconciliation compares the firm's internal position records against custodian statements and SWIFT MT536 securities statement messages. A position break means the firm's record shows a different quantity held than the custodian confirms. Position breaks may reflect unsettled trades, failed deliveries, corporate action processing differences, or booking errors. For long positions, an overstated internal record creates false compliance headroom — the firm believes it holds more than it does. For short positions, an understated record understates exposure.
Cash reconciliation compares internal cash balances against bank or custodian cash statements. Cash breaks arise from timing differences in payment processing, unsettled trade cash legs, fee or interest discrepancies, or bank errors. Cash reconciliation software automates this comparison, applying configurable tolerances and automatically matching items with offsetting amounts across accounts. Cash reconciliation is operationally distinct from position reconciliation because the tolerance and urgency differ: a small position break may be investigated over multiple days; a cash break above a threshold often requires same-day resolution to avoid overdraft or margin call exposure.
Trade reconciliation in the narrow sense compares internal trade records — what the firm captured as executed — against broker confirms, clearinghouse reports, and SWIFT MT548 settlement instruction status messages. Trade breaks at this level typically reflect execution reporting failures, allocation mismatches, or FIX message processing errors. Trade reconciliation breaks that are not resolved before settlement instruction generation materially increase the risk of settlement failure, since the settlement instruction cannot be generated from an unresolved trade record.
Breaks are categorized by cause to determine the resolution path: timing differences that will resolve automatically by the next reconciliation run; data entry or booking errors requiring correction entries with audit trail; allocation mismatches requiring buy-side resubmission; and genuine counterparty disputes requiring direct contact and potentially escalation. A break that is miscategorized — treated as a timing difference when it is actually a booking error — will not resolve and will age toward the settlement date undetected. Break aging is operationally significant: each passing reconciliation run without resolution reduces the time available to investigate before the settlement cutoff, and aged breaks that reach the settlement date unresolved are a primary driver of settlement fail rates.
Digital asset reconciliation has different mechanics from traditional reconciliation. Internal records are compared against on-chain state rather than custodian statements: a block explorer query or node API call returns the confirmed balance for a wallet address at a given block height. On-chain reconciliation must account for finality timing — a transaction that appears confirmed may not have reached the finality threshold for the network — and for chain reorganizations that can alter confirmed balances on probabilistic finality networks. For custodied digital assets, reconciliation against the custodian's reported holdings follows the same mechanics as traditional custody reconciliation, with the additional dimension that the custodian's record can itself be verified against on-chain state.
In Devancore™
Devancore runs reconciliation automatically across position, cash, and trade record types — comparing internal records against custodian statements, broker confirms, and clearinghouse reports on a configurable schedule. Every reconciliation run is logged with its type, external source, as-of date, and result counts: matched records, breaks identified, and breaks carried forward from prior runs. The reconciliation log satisfies the record creation requirements of SEC Rule 17a-3; its retention in WORM-compliant storage satisfies the retention requirements of SEC Rule 17a-4.
Each break is surfaced as an exception with cause classification, monetary value, and priority level based on settlement date proximity. The distinction between reconciliation and break management is explicit in the workflow: reconciliation detects and classifies; break management resolves. A break created by the reconciliation run is assigned to the break management queue, where it follows the full exception lifecycle — investigation, counterparty contact if required, correction entry, and closure — with every step logged for audit.
For digital asset positions, Devancore reconciles internal records against on-chain state, querying confirmed balances at the current finality threshold for each network. Transactions pending finality are tracked separately from confirmed positions, preventing premature position updates that would need to be reversed if finality is not achieved. The on-chain transaction hash serves as the external source reference for digital asset reconciliation breaks, providing independently verifiable evidence of the on-chain state at the time of comparison.