Solutions · Clearing members

Clearing and post-trade platform for clearing members

Client segregation, margin and collateral, settlement, custody and the general ledger in one system, connected to your CCP, depository and custodians.

Book a demo See resources and guides

In short

ZagTrader gives clearing members one post-trade system for client segregation, margin and collateral, settlement, custody, corporate actions and the general ledger. Post-trade processing for Tabadul Hub's cross-border exchange hub runs on ZagTrader technology.

Settlement: DVP, RVP and FOP, T+0 to T+N
Segregation: Omnibus, individual and gross omnibus
Messaging: SWIFT ISO 15022, ISO 20022 capable

What clearing members get

The six things post-trade teams ask about first.

Client segregation

Omnibus, individually segregated and gross omnibus accounts, with margin tracked per client and entity.

See custody

Margin and collateral

Margin rules by client, product and market, automated margin calls, and haircuts marked to market daily.

See margin

Settlement across markets

DVP, RVP and FOP per market and custodian, early- and final-cut instructions, holiday-aware T+N dates.

See settlement

SWIFT and reconciliation

Instructions, statuses and allegements over SWIFT, with daily custodian and client-money reconciliation.

See SWIFT Suite

Corporate actions

Dividends, splits, rights and mergers from the depository feed, checked by a second user before posting.

See corporate actions

Ledger and audit

Clearing events, fees and adjustments post to an auditable chart of accounts, with every action logged.

See finance

Full capability detail

Clearing, margin, settlement and the ledger on one system, with every action audit-ready.

Capability	What you get
Trade capture	Trades ingested in real time over FIX or API from exchanges, brokers or internal platforms, then normalized, validated and stored for downstream workflows.
Client segregation	Omnibus, individually segregated and gross omnibus segregated structures across multiple clearing account set-ups, with client-level segregation, margin tracked per entity, and client assets reconciled and reported automatically.
Margin workflow	Initial, variation and additional margin on configurable rules by client, product and market, automated from calculation to call issuance and settlement.
Collateral	Collateral movements monitored on live dashboards, with real-time position tracking.
Settlement and custody	Gross and net, DVP and FOP settlement across multi-asset trades, with integrated custody, real-time reconciliation and integration with CSDs and market venues.
Corporate actions	Entitlements, redemptions and adjustments tied to held positions, synchronized with validation and workflow routing; dividends, stock splits, mergers and other events processed automatically.
Sub-ledger and general ledger	Clearing events, fees and adjustments posted automatically to a fully auditable chart of accounts.
Audit and compliance	Built-in controls for CSD compliance, trade-fail tracking and financial reporting, with full event logging and multi-user authorization, across asset classes and jurisdictions.

Free tool, no sign-up

Try the free MT/MX Parser

Decode MT and ISO 20022 messages with our free parser. Paste a status advice to see every field explained, or look up a settlement status or transaction type code.

Every MT block, field, sequence and qualifier decoded in plain English
ISO 20022 XML shown as a tree, with the MT message that does the same job
Status, reason and event codes explained, with what to do next
Runs in your browser: nothing you paste is uploaded

Look up

Free to use, no sign-up. Available publicly until further notice.

Open the parser See what it does

Reference page for MT548 Settlement Status and Processing Advice, explaining when the message is used, its category, its 17 sequences and 83 fields, and its ISO 20022 equivalents sese.024 and sese.025

Who it's for

General and direct clearing members
Brokers that clear their own trades
Custodian banks acting as clearing agents

What it solves

Margin calculated in spreadsheets
Client segregation tracked outside the ledger
CCP and depository breaks found late

Built on the ZagTrader platform

Settlement & Post-Trade Margin & Leverage Custody & Back Office SWIFT Suite

Frequently asked questions

Which segregation models are supported?

Omnibus, individually segregated and gross omnibus segregated structures, with client assets kept separate and reconciled automatically.

How do trades come in?

Over FIX or API from exchanges, brokers or internal platforms. Trades are normalised and validated before they reach margin, settlement and the ledger.

How do you connect to custodians and depositories?

Through SWIFT messaging (full ISO 15022, with ISO 20022 format capability) on any service bureau, plus SFTP, email or API where a market uses them.

What controls are built in?

Maker-checker approval, multi-user authorisation, trade-fail tracking and a full event log across clearing, settlement and the ledger.

How do we track each trade from execution to settlement?

Each trade is captured in real time over FIX or API, normalised and validated, then carried through margin, settlement and the ledger as one record. Settlement shows per-leg status with rejection and trade-fail tracking, and SWIFT status messages and allegements update it as custodians and depositories respond. Clearing events, fees and adjustments post to the general ledger as they happen, and every event is logged.

Can it manage different settlement cycles across markets and asset classes?

Yes. Settlement cycles are set per market, from T+0 to T+N, with holiday-aware dating and end-of-day processing. DVP, RVP and FOP settlement run per market and custodian, gross or net, across multi-asset trades, and FX trades settling in a different currency are handled.

How are breaks and failed trades caught?

Trade fails are tracked inside the clearing workflow, and custodians, brokers, holdings and client money are reconciled every day. Items are auto-matched by ISIN, quantity, price and reference, and exceptions are flagged for the operations team.