Skip to main content

Securities & Position Reconciliation

Securities, positions and custody reconciliation in one place.

Reconcile custody positions, trades, corporate actions and cash-vs-position across custodians, prime brokers and internal books — with AI-assisted root-cause suggestions and evidence for every position.

MT535 · MT536
Custody statement formats
Trade · Settlement
Date-aware position matching
3-way
Custodian · broker · internal book
For Middle OfficeFor Custody OpsFor Fund AccountingFor Prime Brokerage Ops

The problem

The reconciliation problems this solves

Multi-custodian fragmentation

Different SWIFT MT535/MT536 dialects, custodian-specific extensions and inconsistent identifiers (ISIN, CUSIP, SEDOL, internal).

Corporate actions

Elective events, DR conversions and stock splits create transient breaks that need lifecycle-aware matching.

Trade date vs settlement date

T/S-date reconciliation across pending, failed and partially-settled trades needs stateful position rollforward.

Cash-vs-position integrity

Position moves must reconcile back to cash movements to catch booking errors before NAV strike.

Capabilities

What ReconIQ does for this use case

Position lifecycle matching

Stateful reconciliation across trade date, settlement date, pending and failed states with rollforward semantics.

Corp-actions aware AI

Agentic triage recognises DR/ADR splits, mergers and elective events, proposing resolutions with source evidence.

Identifier crosswalk

Built-in ISIN/CUSIP/SEDOL/ticker crosswalk with tenant overrides for internal instrument masters.

Cash-vs-position

Two-legged reconciliation ties position changes to their cash counterparts for booking-error detection.

NAV-ready dashboards

Sign-off dashboards with ageing, exposure and unmatched trend, exportable to fund accounting sign-off packs.

Custodian isolation

Multi-custodian tenants use row-level isolation so ops teams only see the books they are entitled to.

Data sources supported

  • SWIFT MT535 (holdings), MT536 (statement of transactions), MT537 (pending), MT548 (settlement status)
  • ISO 20022 semt.002, semt.003, semt.017
  • Custodian & prime broker files (State Street, BNY Mellon, Northern Trust, JPM, Citi, GS PB)
  • Trading system extracts (Charles River, BlackRock Aladdin, Bloomberg AIM)
  • Corp-actions vendor feeds (Bloomberg CACS, Refinitiv, ICE)
  • Internal instrument & entity masters

What this gives you

Lifecycle-aware
Matching across pending, failed and settled states
Cross-checked
Cash movements tied back to position changes
Sign-off ready
Ageing and exposure views for fund accounting review
Isolated
Custodian books separated by row-level access controls

Designed with reference to the frameworks that matter here

Controls are designed with reference to these frameworks and regimes. See Security & Compliance for the full picture.

SEC 17a-13AIFMD Annex IVUCITSMiFID II RTS 22DORASOC 2 Type II (target)

ReconIQ does not hold SOC 2 or ISO 27001 certification. Entries marked “(target)” or “(aligned)” describe design references and roadmap targets, not certifications we have earned.

Questions

Frequently asked

Can ReconIQ reconcile shadow-NAV against fund accounting?+

Yes. ReconIQ supports tri-party reconciliation — custody, prime broker and fund accountant — with configurable tolerance and materiality per book.

How are failed trades handled?+

Failed trades are flagged as stateful breaks tied to the parent trade lifecycle; ageing SLAs, escalation and buy-in workflows are configurable per tenant.

Do you support ISO 20022 semt.* messages?+

Yes, alongside MT5xx. ReconIQ maintains both models in the canonical schema so you can run mixed-custodian populations without dual-book pipelines.

See it on your data.

Try the live demo, or book a session to walk a securities & position reconciliation workflow end to end.