Custody Reconciliation
The daily comparison of a firm's internal position records against the custodian's statement of holdings, identifying breaks for investigation and regulatory documentation.
Definition
Custody reconciliation — also called custodian reconciliation or position reconciliation — is the process of comparing a firm's internal books against the custodian's official statement of positions and cash balances. The custodian holds legal title to the assets on behalf of the firm and its clients. Their record is the authoritative settled position. Any difference between the internal record and the custodian statement represents either a legitimate timing difference or a genuine discrepancy requiring investigation.
Unresolved custody breaks are both an operational risk and a regulatory concern, creating direct exposure to inaccurate NAV calculation and unreliable client reporting. With the industry move toward T+0, the overnight reconciliation window has effectively vanished. Firms now require intraday or continuous custodian reconciliation to prevent settlement failures from cascading into the next trading session.
How it works
Custody reconciliation runs at least once per day, typically after the custodian publishes its end-of-day statement. The firm's operations system compares each position line — instrument by instrument, account by account — against the custodian's reported holdings. Cash balances are reconciled separately in each currency.
The expected output is a zero-break report — meaning every internal position matches the custodian statement within accepted tolerances. Firms typically define tolerance thresholds by dollar value or share count; differences below the threshold are recorded but not escalated. In practice, timing differences are normal. A trade that settled at the custodian after the statement cutoff will show as a break until the next reconciliation cycle. These are classified as timing breaks and age out automatically once the settlement posts.
Genuine breaks — where the difference cannot be explained by settlement timing — require investigation. Common causes include:
- Custodian processing errors
- Corporate action discrepancies, such as a dividend applied at a different amount or a stock split processed at a different ratio than the internal system recorded
- Failed settlements not properly reflected internally
- Data entry errors in the internal system
Each cause has a different resolution path and urgency level. In digital asset contexts, where settlement is often atomic, the reconciliation question shifts from whether a trade settled to whether the internal ledger correctly reflects the current wallet state. Devancore treats the blockchain as a real-time custodian feed, reducing time-to-detection for discrepancies from 24 hours to minutes.
For digital asset positions held at a qualified custodian or on-chain, the reconciliation source shifts from a SWIFT MT535 statement to an on-chain ledger query or custodian API feed. The operational risk controls and the control objective remain identical: confirm that what the firm believes it holds matches what the custodian or ledger confirms as settled and safekept.
Regulators treat custodian reconciliation as a fundamental control. SEC Rule 17a-3 requires broker-dealers to maintain accurate records of positions held at each custodian. SEC Rule 17a-13 mandates periodic securities counts and comparisons against custodian records. Firm-level supervisory procedures under FINRA Rule 3110 govern the frequency, documentation, and escalation requirements for reconciliation breaks. Examiners look for evidence that reconciliation runs daily, that breaks are investigated promptly, and that resolution is documented.
In Devancore™
Devancore transforms custody reconciliation from a retrospective batch process into a continuous control. By unifying SWIFT MT535 parsing with real-time API feeds and on-chain ledger queries, the platform provides a living view of position integrity across both traditional securities and digital asset holdings — applying the same operational risk framework to both rails.
Breaks are automatically aged and prioritized by risk. A principal value discrepancy at a custodian is flagged significantly higher than a one-day timing break on an equity trade. Ops Copilot surfaces contextual explanation for common break types — including corporate action misalignments and failed settlement reflections — reducing investigation time for back-office teams without requiring manual triage of every open item.
The source of each reconciliation run is recorded explicitly: SWIFT MT535 statements, DTCC files, custodian APIs, and on-chain ledger queries are all supported as named external sources. Each break carries internal and external position values, a calculated difference, a cause classification, and a resolution timestamp. Compliance teams have documented evidence of daily reconciliation diligence without a separate reporting system.