Skip to main content
ZagTrader
Reconciliation for Multi-Asset Operations: What to Look For hero background
Back to Resources
Buyer's Guide
Post-Trade

Reconciliation for Multi-Asset Operations: What to Look For

Positions, cash and trades across custodians, brokers, depositories and banks, for every entity and currency.

Short answer: a reconciliation platform for multi-asset operations should match positions, cash and trades against every custodian, broker, depository and bank each day, by ISIN, quantity, price and reference, and turn whatever does not match into a flagged, aged exception. It should work across legal entities and currencies from one book, so the internal records being reconciled already agree with each other.

Reconciliation is where operations teams find out whether the books are right. In a multi-asset business the work multiplies: equities at one custodian, bonds at another, funds with a transfer agent, cash at several banks, sometimes digital assets in wallets, all across several entities and currencies. This guide sets out what a reconciliation capability should cover, what to ask vendors and how ZagTrader handles it.

What Needs Reconciling

  • Positions: holdings per account, per instrument, per custodian and depository, settled and unsettled.
  • Cash: balances and movements at each bank and custodian, per currency.
  • Trades: executions against broker and venue confirmations, and settlement instructions against the trades they came from.
  • Client money: the total of individual client balances against the omnibus account that holds them.
  • Internal integrity: every executed trade has its ledger entry, and the sub-ledgers agree with the general ledger.

Matching Rules

Matching should be automatic for the clean majority, so people spend their time on breaks. Look for matching keys you can set per counterparty: ISIN, quantity, price, account and trade reference, with tolerances where a counterparty rounds differently. A good engine also understands timing. A trade executed yesterday and not yet settled at the depository is not a break, and it should not appear as one.

Exceptions and Ageing

  • Every unmatched item is flagged with its difference in quantity, price or amount.
  • Exceptions are aged, so a break open for three days is treated differently from one found this morning.
  • Break reports go to the reconciliation team automatically after each run.
  • Excluding an item from reconciliation needs a second person's approval.

Multiple Legal Entities and Currencies

Global asset managers and banking groups reconcile across several legal entities, each with its own custodians, bank accounts and reporting currency. Ask whether entities share one ledger with separate books, whether each journal keeps its original currency and rate, and whether group consolidation removes inter-company balances. If each entity runs on a separate system, every inter-company movement becomes another reconciliation.

Straight-Through Processing

Custody banks get most value from reconciliation that is part of the settlement flow rather than a separate step at the end of the day. Settlement instructions go out, confirmations come back and are matched to the instruction automatically, statements of holdings and transactions are compared to internal positions, and only exceptions need a person.

Data Aggregation Across Custodians

Each custodian and bank sends data in its own layout. The platform should accept SWIFT statements (MT535 holdings, MT536 transactions, MT537 pending, MT940 and MT950 cash), Excel and XML files and drop copy, with a template per counterparty so a new custodian is a configuration task. Holdings held at several custodians should roll up into one book, so the firm sees one position per client and instrument.

Controls and Audit

  • Every reconciliation run is recorded, so auditors can see what was compared and when.
  • Role-based access decides who can run, review and clear items.
  • Corrections post as reversals with both entries kept, never as deletions.
  • Closed periods stay closed, so a reconciled month cannot change behind you.

Questions to Ask a Vendor

  • Show a break end to end: a custodian statement that disagrees with the book, from file import to flagged exception.
  • How is a new custodian added? Configuration of a statement template, or a development project?
  • How are unsettled trades treated? Do they show as breaks against the depository on the trade date?
  • What is the internal side of the comparison? The same ledger that trading and settlement post to, or a copy loaded overnight?
  • How are entities and currencies handled? One ledger, separate books, and consolidation with inter-company eliminations?
  • Who can hide an unmatched item? Is a second approval enforced by the system?
  • Which message types are supported? Name the SWIFT statements and file formats you accept today.

How ZagTrader Handles It

ZagTrader runs reconciliation on the same platform as trading, settlement, custody and the general ledger, so the internal side of every comparison is the live book of record. The platform carries $500B+ in client assets for 100+ institutions.

  • Daily reconciliation: custodian and broker reconciliation from Excel, XML, SWIFT or drop copy; holdings at local and international custodians; and aggregate client money across omnibus and individual accounts, described on Settlement.
  • Matching: auto-matching by ISIN, quantity, price and reference, with exceptions flagged and aging alerts and escalation. Statement layouts are configured per custodian, and break reports are emailed to the reconciliation team.
  • Depository timing: depository holdings are compared with settled positions plus unsettled trades grouped by age, so trades the depository has not registered yet do not show as breaks.
  • STP: SWIFT Suite generates instructions, matches inbound confirmations against them automatically, and reconciles MT535, MT536 and MT537 statements against internal positions. Settlement instructions are also reconciled against trades, with quantity and price differences recorded.
  • Cash: bank statements, custodian holdings and custodian cash are matched daily, unmatched items become a worklist, and hiding an unmatched item needs a second approval. Client funding by virtual IBAN is matched and posted automatically.
  • Entities and currencies: several offices run on one double-entry ledger, each closing its own periods, with group consolidation that eliminates inter-company sales. Each journal keeps its currency and the rate at posting.
  • Aggregation: holdings and cash are reconciled daily against each custodian, so positions held at several custodians roll up into one book. ZagTrader Investment Office consolidates every custody account into one view in a base currency.
  • Integrity and audit: an alert for executed trades with no journal, a nightly consistency report, every reconciliation run written to the audit trail, and corrections by reversal, never deletion.

Related: see Custody & Back Office, Finance & Accounting and ZagTrader for Custodians. For asset managers running several entities, see ZagTrader for Asset Managers. For the settlement flow that reconciliation checks, read DVP Settlement and the Move to ISO 20022.

See a Break Found and Flagged

Watch a custodian statement reconciled against the live book, with exceptions flagged for your team.