Position reconciliation is the process of comparing securities positions held at a custodian against the positions recorded in an investment book of record. It is the primary control that confirms you actually own what your records say you own.
Why position reconciliation matters
Every investment decision — from rebalancing to reporting — depends on accurate position data. If the positions in your portfolio accounting system do not match what the custodian holds, downstream processes break: NAV calculations are wrong, performance attribution is unreliable, compliance checks reference stale data, and investor reports contain errors.
Position breaks that go unresolved compound. A missed corporate action today becomes a persistent position discrepancy that distorts reporting for weeks until someone traces it back to the source. The longer a break persists, the harder it is to resolve.
The position reconciliation process, step by step
The process follows a consistent sequence regardless of whether it is performed manually, by an RPA bot, or by an AI agent:
- Data extraction. Pull the custodian's position statement (typically via SWIFT MT535, a file feed, or an API) and the internal book of record's position report for the same date.
- Normalisation. Map security identifiers (ISIN, CUSIP, SEDOL, internal IDs) to a common reference so the same security can be matched across sources. Normalise units (some custodians report in nominal value, others in shares).
- Matching. Compare each position line: security identifier, quantity, and (optionally) market value. Positions that agree within tolerance are marked as reconciled.
- Break identification. Positions that do not match — or appear in one source but not the other — are flagged as breaks. Each break is categorised by type (quantity mismatch, missing position, extra position).
- Investigation. For each break, determine the root cause. Common causes include unsettled trades, pending corporate actions, timing differences, or booking errors.
- Resolution. Adjust the incorrect record. If the custodian is correct, update the book of record. If the book of record is correct (rare, but possible with custodian processing delays), document and monitor until the custodian catches up.
- Sign-off. Once all breaks are resolved or documented with expected resolution dates, the reconciliation is signed off for that date.
Common causes of position breaks
Understanding why breaks occur helps teams prioritise investigation and build better preventive controls:
| Cause | Description | Typical resolution |
|---|---|---|
| Unsettled trades | Trade booked internally but not yet settled at custodian | Monitor until settlement date; escalate if overdue |
| Corporate actions | Stock split, merger, or dividend processed at different times | Apply the corporate action to the lagging system |
| Timing differences | Custodian statement cut-off differs from internal system | Align cut-off times or apply known timing adjustments |
| Manual entry errors | Wrong quantity or security entered in the book of record | Correct the entry; review input controls |
| Failed trades | Trade failed to settle but was not reversed internally | Cancel or rebook the trade in the internal system |
| Account mapping errors | Position booked to wrong sub-account or entity | Transfer the position to the correct account |
How position reconciliation is handled today
In most operations teams, position reconciliation follows one of three models:
Manual spreadsheet-based
The operations analyst downloads custodian files and internal reports, pastes them into a spreadsheet, and uses VLOOKUP or pivot tables to identify mismatches. Breaks are investigated by checking trade blotters, corporate action calendars, and settlement status. This approach works for small portfolios but does not scale — and it introduces human error at the matching stage.
Reconciliation software
Dedicated tools (Duco, Gresham Clareti, SmartStream, Broadridge) automate the matching step. They ingest data feeds, apply configurable matching rules, and surface exceptions. The operations team still investigates and resolves breaks manually, but the matching is faster and more reliable.
RPA-assisted
Robotic process automation bots handle the data extraction and loading steps — pulling files from custodian portals, reformatting them, and loading them into the reconciliation tool. This removes manual download steps but does not address break investigation or resolution.
Where agents fit
The matching step is largely solved by existing software. The unsolved problem is what happens after matching: investigating breaks, determining root causes, and deciding on the correct resolution. This is where most of the labour cost sits — and where AI agents can operate.
An agent can examine a position break, check whether there are unsettled trades that would explain the difference, look for recent corporate actions on that security, compare the break pattern against known timing differences, and either resolve the break or escalate it with a full reasoning trail. Every action is logged and auditable.
For family offices and fund managers looking for this kind of operational support, our virtual family office service handles position reconciliation as part of a broader operational engagement.
Key terms
- Book of record
- The authoritative internal system that tracks what the firm believes it holds.
- Custodian statement
- The external report from the custodian confirming what is actually held in their accounts.
- Break
- A discrepancy between two sources that requires investigation.
- Exception queue
- The list of unresolved breaks awaiting investigation.
- Tolerance
- An acceptable threshold for differences (e.g., rounding differences below 0.01 units may be auto-resolved).