← Glossary

Devancore Post-Trade Glossary

Custody Reconciliation

Custody reconciliation is the daily match of internal positions and cash to the custodian statement: timing versus genuine breaks, owners, aging, and the evidence that holdings are actually safekept.

Definition

Custody reconciliation is the daily test of whether internal positions and cash still equal what the custodian reports as safekept. The custodian statement is the settled vault file. The internal snapshot is what the firm believes it holds. A difference is either a timing item that should clear on the next statement or a genuine break that needs an owner before anyone treats the stock record as clean.

This page is the statement match. The sibling page, custody accounting reconciliation, is the vault-to-ledger join: trade-date books, accruals, fees, FX, and location control accounts. Quantity can match the statement while the accounting books still cannot close. Do not collapse those two controls into one queue.

Statement-match records

Statement-match records

The run is useful when each internal line can be tied to a custodian line, a cutoff, and a break class.

Record area What the run holds Control question
Holdings statement Settled quantity by instrument, account, and location as of the custodian as-of time Does the vault file show what is safekept at that cutoff?
Internal position Stock record or position blotter quantity, account, and identifier used for the match Is the internal line the same security and account as the statement line?
Cash by currency Custody-bank or custodian cash versus internal cash for each currency Does cash match on the same as-of, or is it mixed with another value date?
Pending and fails Trades not yet on the statement, fails to receive or deliver, and in-transfer items Is this break still inside the settlement window, or has it aged past expected settlement?
Break class Match, timing, genuine, and the reason code assigned at detection Will this item age out, or does it need an owner today?
Evidence Run timestamp, source file, delta, owner, aging, and close Can a reviewer replay why the line was accepted, aged, or corrected?

Trade reconciliation compares events. Custody reconciliation compares resulting state. A blotter can be clean and the vault still wrong: a split applied at a different ratio, a fail that never hit the stock record, an identifier mapped to the wrong instrument, or a settle that posted after the statement cutoff.

Cash is a separate match, not a footnote on the position run. Each currency has its own as-of. Mixing local custody cash with base-currency books is an accounting problem; mixing two value dates inside the statement match is a custody problem.

US broker-dealers use this run as operating evidence that position records stay current. Rule 17a-3 requires accurate records of securities held. Rule 17a-13 requires a quarterly examination, count, and comparison, including items not in physical possession. Daily statement matching is what keeps that quarterly work from becoming the first time a location break is seen. Supervisory procedures under FINRA Rule 3110 typically require that breaks are run, owned, and documented. The recon log is evidence. It is not a substitute for the count or for counsel's view of those rules.

How it works

The workflow is match, classify, age, correct. Take the custodian holdings and cash. Take the internal snapshot. Name the cutoff. Match by identifier, account, and location. Split timing from genuine. Assign owners. Keep the run.

Daily statement-match control points

Daily statement-match control points

A timing item that is never reclassified becomes a genuine break that nobody owned.

Step Data required Failure mode
Take cutoff Statement as-of time and internal snapshot at the same clock A settle after the statement looks like a missing position
Match holdings Identifier, account, location, and quantity Netting across accounts hides a long and a short that should both break
Match cash Currency, value date, and custody-bank balance Cash is compared in base currency while the statement is local
Classify Pending settlements, known fails, and unexplained quantity or cash A booking error is labeled timing and sits until the next cycle
Age and assign Open days, materiality, owner, and next action Aged genuine breaks have no owner when the quarterly count arrives
Correct and evidence Adjustment, maker-checker, and the statement line The position is forced to match with no retained reason

Source systems include custodian holdings statements, often delivered as SWIFT MT535 or an equivalent API file, cash statements, internal stock record or position blotter, pending settlement and fail files, and identifier maps. For digital asset holdings at a qualified custodian or on-chain, the external source may be a custodian API or a ledger query. The control objective does not change: internal quantity and cash must still explain the safekeeping source at a named as-of.

Timing breaks are expected around cutoff. A trade that settles after the statement should appear on the next run. Timing that does not clear on the following statement is no longer timing. Genuine breaks need a reason at detection: booking error, corporate-action quantity, fail not reflected, identifier mismatch, or custodian processing difference. Each reason has a different owner.

Tolerance is a policy, not a hiding place. A share or cash delta below threshold still belongs on the run. If it is never recorded, aging cannot start.

When the statement match is clean, the accounting join can still be open. That handoff is custody accounting reconciliation: expected trade-date versus settlement-date gaps, accruals versus receipts, and difference-account postings. This page stops at whether the vault file and the internal position and cash snapshot agree.

In Devancore™

Devancore supports custody reconciliation as a post-trade operating-record layer around custodian statements, internal snapshots, break class, aging, and run evidence. It can help teams keep statement lineage, timing versus genuine state, and owners visible.

Devancore does not act as a custodian, qualified custodian, or examining authority. It does not safekeep assets, produce the official stock record, or determine that a daily recon or quarterly count was complete. Those functions remain with the appointed custodian and the firm's responsible parties. The product boundary is the controlled operating copy of the statement match that books-and-records already depend on.

In a Devancore-style workflow, a holdings statement, cash statement, internal snapshot, break, aging change, or correction enters as a source event. The record is mapped to instrument, account, currency, delta, owner, and workflow state. Matched, timing, genuine, aged, corrected, or unexplained remains visible with timestamp, reason, and source reference.

That structure is what operations actually use. The custodian may know the vault. The stock record may know the internal quantity. The operating question is whether the break between them is classified before the next statement, the next count, or the next close.

Conversational finance depends on the same chain. A user can ask which genuine breaks have no owner, which timing items survived a second statement, which cash currencies broke at the last cutoff, or which identifiers do not join the holdings file. The answer should resolve to statements, lines, owners, and evidence.