Securities, positions and custody reconciliation at institutional scale.
Reconcile custody positions, trades, corporate actions and cash-vs-position across custodians, prime brokers and internal books — with agentic root-cause analysis and full T+1 evidence.
The reconciliation problems this solves
Different SWIFT MT535/MT536 dialects, custodian-specific extensions and inconsistent identifiers (ISIN, CUSIP, SEDOL, internal).
Elective events, DR conversions and stock splits create transient breaks that need lifecycle-aware matching.
T/S-date reconciliation across pending, failed and partially-settled trades needs stateful position rollforward.
Position moves must reconcile back to cash movements to catch booking errors before NAV strike.
What FVI does for this use case
Stateful reconciliation across trade date, settlement date, pending and failed states with rollforward semantics.
Agentic triage recognises DR/ADR splits, mergers and elective events, proposing resolutions with source evidence.
Built-in ISIN/CUSIP/SEDOL/ticker crosswalk with tenant overrides for internal instrument masters.
Two-legged reconciliation ties position changes to their cash counterparts for booking-error detection.
Sign-off dashboards with ageing, exposure and unmatched trend, exportable to fund accounting sign-off packs.
Multi-custodian tenants use row-level isolation so ops teams only see the books they are entitled to.
- 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
Aligned to the regulations that matter here
Controls designed against the frameworks Tier-1 buyers require. See Security & Compliance for the full matrix.
Frequently asked
Can FVI reconcile shadow-NAV against fund accounting?+
Yes. FVI 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. FVI maintains both models in the canonical schema so you can run mixed-custodian populations without dual-book pipelines.
See it on your data
30 minutes with a solutions engineer, walking a real securities & position reconciliation workflow end-to-end.