Clearing and Settlement Tracking Explained

Short answer: a clearing and settlement tracking system follows every trade from execution until the securities and cash have actually moved, and shows where it stands: instructed, matched, settled, partially settled or failed. It tracks the market side and the client side separately, ties every status to the message that set it, and flags a trade that will miss its settlement date while there is still time to fix it.

Execution takes milliseconds. Settlement takes one or more business days and involves brokers, custodians, clearing houses and central securities depositories (CSDs), each keeping its own record of the same trade. For the mechanics of DVP and ISO 20022, see our DVP settlement explainer.

The Chain From Execution to Settled

• Trade capture: the trade arrives from the exchange, an executing broker or the front office, over FIX, a drop copy or a file, and is validated before anything downstream uses it.
• Confirmation and allocation: institutional trades are confirmed with the counterparty and block trades are allocated to the underlying accounts. An allocation error found on trade date is a correction; found on settlement date, it is a fail.
• Clearing: a central counterparty (CCP) becomes buyer to every seller and seller to every buyer and nets obligations, so the member settles one net position per security. Off-exchange and many bond trades clear bilaterally, trade by trade.
• Instruction: each side instructs its custodian or the CSD to deliver or receive, against payment (DVP or RVP) or free of payment (FOP), using the standard settlement instructions (SSIs) for the account. Over SWIFT these are MT540 to MT543.
• Matching and status: the CSD or custodian matches both sides on ISIN, quantity, amount, date and counterparty, and reports status on MT548.
• Settlement: securities and cash move on the settlement date, confirmed by MT544 to MT547. Holdings move from pending to settled, cash from projected to actual, and the ledger entry is made.
• Reconciliation: positions and cash are compared every day with the custodian's statements of holdings, transactions and pending items (MT535, MT536 and MT537).

Status Per Leg, Not Per Trade

A client trade at a broker or custodian has two legs: one with the market and one with the client or the client's custodian. They can diverge. The market leg can settle while the client leg waits for cash, or a pre-funded client can be settled while the market leg is pending. One status per trade hides exactly that case. A tracking system should distinguish at least pending, matched, partially settled, settled, and failed with a reason: lack of securities, lack of cash, mismatched details or a blocked account.

Allegements and Fails

An allegement (MT578) means a counterparty has instructed against your account and the CSD cannot find your matching instruction. Either you missed or mis-booked the trade, or the counterparty is wrong. Allegements and instructions still unmatched near settlement date belong in a queue with an owner and an age, not in a shared mailbox.

A fail ties up cash and securities, can attract daily cash penalties in some markets and can end in a buy-in at the failing party's expense. Managing fails means:

• seeing likely fails before settlement date: unmatched instructions, short holdings and unfunded cash;
• recording a reason for every fail and ageing it day by day;
• controlling who may re-settle or roll back a failed trade, and recording who did;
• reporting fails by market, custodian and counterparty.

Settlement Cycles: T+1, T+2 and T+N Per Market

Each market sets its own cycle. The US, Canada and Mexico moved most securities to T+1 in 2024, the UK and the EU have set October 2027 for theirs, and many markets, including the Saudi Exchange, settle on T+2. A tracking system needs the cycle per market and instrument type, holiday calendars per market and currency, and a settlement date that is calculated, never typed. Shorter cycles leave less time to allocate, confirm and fund, so exceptions must surface on trade date.

Fixed Income and Cross-Border Settlement

Bond settlement amounts include accrued interest (or accrued profit on sukuk), so a wrong day count becomes a cash mismatch at matching. Many bonds settle at an international CSD rather than the local depository, so the place of settlement belongs in the SSI.

A foreign security usually settles at the issuer's home CSD through a sub-custodian, and cash may settle in a currency other than the account currency, which adds an FX leg with its own date. Cross-border tracking needs each market's cycle and calendar, the sub-custodian's cut-offs, the FX leg and a reconciliation per custodian, so positions held at several custodians roll up into one book.

What a Tracking System Must Show

• Every open trade with trade date, settlement date and status per leg, filtered by market, custodian, counterparty and client.
• The messages behind each status: instruction, status advices, confirmation and any allegement.
• Counts and values of pending, settled and failed trades across the whole filtered set.
• The ledger entry for every settled movement, a reversal for every rollback, and an audit trail of who did what.

Questions to Ask a Vendor

• Does it track the market leg and the client leg separately?
• Which SWIFT messages does it send and receive, and through which service bureau or file channel?
• How are settlement dates calculated per market, and from which holiday calendars?
• How are allegements and unmatched instructions routed, owned and aged?
• Who can re-settle a failed trade, and is that permission closed until granted?
• Does settlement post to the general ledger as it happens, or in an end-of-day batch?

How ZagTrader Handles It

ZagTrader runs trade capture, settlement, custody, reconciliation and the general ledger on one platform, so a trade's position, its settlement instruction, the cash it moves and its ledger entry are one record.

• Trade capture: trades arrive over FIX or API and are validated before they reach margin, settlement and the ledger.
• Instructions: DVP, RVP and FOP per market and custodian, from per-client, per-custodian SSIs, dispatched by SWIFT, SFTP, email or API. SWIFT covers MT540 to MT547, MT548 status and MT578 allegements over ISO 15022, with ISO 20022 (MX) format capability.
• Status per leg: each order's settlement status separates the market side from the client side, including partial settlement and market or client settlement failure, with per-leg status and rejection tracking. The settlement screen counts pending, settled and failed trades and their value across every matching trade. Settling an order in a failed status needs a dedicated permission that stays closed until an administrator grants it.
• Message oversight: SWIFT Suite matches inbound confirmations against outgoing instructions, routes exceptions to owned queues with escalation and flags stuck messages with aging indicators.
• Cycles and reconciliation: T+0, T+1, T+2 or T+N per market with holiday-aware dating, and FX trades settling in a different currency. Custodians, holdings and aggregate client money are reconciled daily, auto-matched by ISIN, quantity, price and reference, with exceptions flagged and aged.
• Ledger: trades, fees, commissions and VAT post to the general ledger as they happen, and a rollback posts reversal journals.
• Markets and cross-border: connectivity to CSDs, clearing houses and global and regional custodians, with multi-custodian settlement reconciliation for international clients. In Saudi Arabia the platform works with Edaa over ISO 15022 and settles DVP in line with Muqassa on T+2. Post-trade processing for Tabadul Hub's cross-border exchange hub runs on ZagTrader technology.
• Fixed income: bonds and sukuk on the same platform, with accrued interest, clean and dirty pricing, coupons and redemptions.

More than 100 institutions run on ZagTrader technology, with $500B+ in client assets on the platform.

Related: see Settlement & Post-Trade, SWIFT Suite, Custody & Back Office, ZagTrader for Custodians and ZagTrader for Clearing Members, and our guides to DVP settlement and ISO 20022 and cross-border trading in the GCC.