The securities settlement lifecycle, message by message

From trade to settled position

Settlement is the part of a trade that happens after the price is agreed. A broker, an asset manager or a custodian’s client has bought or sold securities; now the securities must move from the seller’s account to the buyer’s account and the cash must move the other way. Both moves happen in the books of a central securities depository (CSD), or of an international CSD for eurobonds, usually on a fixed settlement date such as trade date plus one or two business days.

Upstream of settlement, and outside this guide, sit execution, allocation and confirmation: the broker confirms the trade to the investment manager, the manager allocates it across funds or accounts, and both sides agree the economics. In the Swift MT world these trade confirmations use messages such as MT515 and MT518; many firms agree them over FIX instead, with allocations (35=J) and confirmations (35=AK), as explained in from FIX execution to settlement on the ZagTrader FIX Parser. Whatever the channel, the agreed trade is what each side’s settlement instruction must copy exactly.

From the moment the instruction is sent, the lifecycle has five stages: instruction, acknowledgement and validation by the custodian, matching with the counterparty’s instruction at the CSD, settlement on or after the settlement date, and reporting in statements. Each stage has its own message, and every message refers back to the account owner’s original reference so the whole chain can be traced.

Who sends what to whom

The table follows one trade from the account owner’s point of view: an asset manager or broker (the account owner) holds its securities with a custodian (the account servicer), which is a participant of the CSD directly or through a sub-custodian. The same pattern repeats one level down between the custodian and the CSD.

Step 1: choose the right instruction and fill it completely

The four instruction types are the same message with two switches: direction (receive or deliver) and payment (free of payment or against payment). Pick the one that matches what you will do at the CSD, not what you did on the exchange: a sale is a delivery, a purchase is a receipt. In sese.023 the two switches are explicit elements, SttlmTpAndAddtlParams/SctiesMvmntTp (RECE or DELI) and SttlmTpAndAddtlParams/Pmt (APMT or FREE).

Every instruction carries the same backbone. Sequence A (GENL) has your reference in :20C::SEME// and the function in 23G (NEWM for a new instruction, CANC to cancel one). Sequence B (TRADDET) has the settlement date :98A::SETT//, usually the trade date :98A::TRAD//, the deal price and the ISIN in 35B. Sequence C (FIAC) has the quantity :36B::SETT// and your safekeeping account :97A::SAFE//. Sequence E (SETDET) has the transaction type :22F::SETR//, one SETPRTY block per settlement party and, for against-payment trades, the settlement amount :19A::SETT// in an AMT block.

The transaction type tells everyone what kind of movement this is: TRAD for a normal trade, REPU and RVPO for repo legs, SECL and SECB for securities lending, COLI and COLO for collateral, OWNI and OWNE for transfers between your own accounts.

• Settlement parties are built as a chain from the CSD outwards: :95P::PSET// is the place of settlement (the CSD); on the other side, the receiving agent REAG (for a delivery) or the delivering agent DEAG (for a receipt) is the counterparty’s CSD participant, followed where the market requires it by the custodian and the buyer or seller.
• Many CSDs match on the counterparty participant’s account as well, so give :97A::SAFE// inside the REAG or DEAG block when your counterparty supplied it.
• Instruct early. Most custodians publish a deadline before the CSD cut-off, and an instruction that matches late may attract a late matching penalty in markets that apply them.

{1:F01FUNDLULLAXXX0000000000}{2:I543CUSTAEADXXXXN}{4:
:16R:GENL
:20C::SEME//FL26102000017
:23G:NEWM
:98C::PREP//20261020153000
:16S:GENL
:16R:TRADDET
:98A::SETT//20261022
:98A::TRAD//20261020
:90B::DEAL//ACTU/AED12,5
:35B:ISIN AEZAGT000016
ZAGTRADER TEST HOLDING PJSC
:16S:TRADDET
:16R:FIAC
:36B::SETT//UNIT/10000,
:97A::SAFE//ZAG-SAFE-0001
:16S:FIAC
:16R:SETDET
:22F::SETR//TRAD
:16R:SETPRTY
:95P::REAG//BRKRAEADXXX
:97A::SAFE//BRK-0042
:16S:SETPRTY
:16R:SETPRTY
:95P::PSET//CSDXAEADXXX
:16S:SETPRTY
:16R:AMT
:19A::SETT//AED125000,
:16S:AMT
:16S:SETDET
-}

Step 2: matching at the CSD

Matching is the CSD comparing your instruction with your counterparty’s. A delivery from the seller’s participant and a receipt by the buyer’s participant must agree on a list of matching fields before either can settle. If one side has not instructed, the CSD has nothing to match against; if both have instructed but one field differs, the two instructions stay unmatched.

The usual matching fields are: direction (one delivery, one receipt), ISIN, quantity, settlement date, trade date, payment type (free or against payment), settlement amount and currency, the delivering and receiving participants and their accounts, and the place of settlement. Some markets add optional fields that only count when both sides fill them. For the settlement amount many CSDs allow a small tolerance: in T2S, for example, the ECB documents a tolerance of EUR 2 for amounts up to EUR 100,000 and EUR 25 above that.

Your custodian relays the result in an MT548: :25D::MTCH//MACH when the instructions agree, or :25D::MTCH//NMAT with a reason in :24B::NMAT//. The reason tells you which field disagrees: CMIS (no counterparty instruction found), DDAT (settlement date), DTRD (trade date), DQUA (quantity), DSEC (security), DMON (settlement amount), DELN (direction), DEPT (place of settlement) or ICAG (counterparty agent). When your counterparty instructs against you and you have not, you may instead receive a settlement allegement (MT578 in ISO 15022, sese.028 in ISO 20022): treat it as a request to check your own booking.

• Compare your instruction field by field with the counterparty’s trade confirmation, not with your own order.
• Never cancel and re-send while the counterparty is also correcting: agree who amends first, or you will both chase a moving target.
• A full checklist of unmatched causes is in why a settlement instruction is unmatched.

{1:F01CUSTAEADAXXX0000000000}{2:I548FUNDLULLXXXXN}{4:
:16R:GENL
:20C::SEME//CA26102100231
:23G:INST
:98C::PREP//20261021091500
:16R:LINK
:13A::LINK//543
:20C::RELA//FL26102000017
:16S:LINK
:16R:STAT
:25D::MTCH//NMAT
:16R:REAS
:24B::NMAT//DMON
:70D::REAS//COUNTERPARTY SETTLEMENT AMOUNT
AED125500,00
:16S:REAS
:16S:STAT
:16S:GENL
:16R:SETTRAN
:35B:ISIN AEZAGT000016
:36B::SETT//UNIT/10000,
:19A::SETT//AED125000,
:97A::SAFE//ZAG-SAFE-0001
:22F::SETR//TRAD
:22H::REDE//DELI
:22H::PAYM//APMT
:98A::SETT//20261022
:98A::TRAD//20261020
:16R:SETPRTY
:95P::REAG//BRKRAEADXXX
:16S:SETPRTY
:16R:SETPRTY
:95P::PSET//CSDXAEADXXX
:16S:SETPRTY
:16S:SETTRAN
-}

Step 3: read the status advices

An MT548 carries one or more status blocks. The qualifier of 25D says which process the status belongs to: IPRC is the custodian’s processing of your instruction, MTCH is matching, SETT is settlement and CPRC is a cancellation request. A reason block (24B) explains the status, and :70D::REAS// may add free text. The link block always quotes your SEME in :20C::RELA//, which is how your system finds the instruction.

The same information travels in sese.024, but each status has its own element instead of a qualifier, as the table shows.

• Reasons under PEND and PENF say whose problem it is: LACK and MONY are yours (not enough securities or cash), CLAC and CMON are the counterparty’s, PREA means your instruction is on hold, BOTH that both are.
• A status advice describes one instruction at one moment. Your custodian may also report all open items at once in an MT537 statement of pending transactions.
• More on the most frequent pending reason: PEND with LACK.

Step 4: settlement and confirmation

On the settlement date the CSD moves securities and, for DVP, cash at the same time. The custodian then sends the confirmation that mirrors your instruction: MT544 for an MT540, MT545 for an MT541, MT546 for an MT542 and MT547 for an MT543. In ISO 20022 all four are sese.025.

A confirmation repeats the trade but reports what actually happened: the effective settlement date in :98A::ESET//, the quantity settled in :36B::ESTT// and, for against-payment trades, the cash settled in :19A::ESTT//. Book from these values, not from the instruction. If only part of the quantity could be delivered and the market allows partial settlement, the confirmation says so in :22F::PARS// with PAIN (more to come) or PARC (no further settlement will take place), and the rest stays pending.

A confirmation can be withdrawn: a custodian that confirmed by mistake, or on a contractual basis before the real movement failed, sends the same message type with function 23G:RVSL. Watch for reversals when you reconcile, because they undo a posting you have already booked.

{1:F01CUSTAEADAXXX0000000000}{2:I547FUNDLULLXXXXN}{4:
:16R:GENL
:20C::SEME//CC26102200415
:23G:NEWM
:98C::PREP//20261022143000
:16R:LINK
:13A::LINK//543
:20C::RELA//FL26102000017
:16S:LINK
:16S:GENL
:16R:TRADDET
:98A::TRAD//20261020
:98A::ESET//20261022
:90B::DEAL//ACTU/AED12,5
:35B:ISIN AEZAGT000016
ZAGTRADER TEST HOLDING PJSC
:16S:TRADDET
:16R:FIAC
:36B::ESTT//UNIT/10000,
:97A::SAFE//ZAG-SAFE-0001
:16S:FIAC
:16R:SETDET
:22F::SETR//TRAD
:16R:SETPRTY
:95P::REAG//BRKRAEADXXX
:16S:SETPRTY
:16R:SETPRTY
:95P::PSET//CSDXAEADXXX
:16S:SETPRTY
:16R:AMT
:19A::ESTT//AED125000,
:16S:AMT
:16S:SETDET
-}

Step 5: statements and reconciliation

Individual messages tell you about one instruction; statements tell you about the account. The custodian sends an MT535 statement of holdings (semt.002) with the position per security, an MT536 statement of transactions (semt.017) with every movement that settled in a period, and an MT537 statement of pending transactions (semt.018) with everything still open and its status.

Reconcile in that order: movements first (each settled confirmation should appear in the MT536), then positions (opening position plus movements equals the MT535 balance), then open items (every instruction you consider live should be in the MT537 with the same status you hold). Differences are breaks to investigate the same day. The step-by-step method is in the guide to reading a custody statement.

When settlement fails

A matched trade that does not settle on its date is a settlement fail. The most common causes are lack of securities (the seller’s own purchase has not settled yet, or the securities are on loan or pledged), lack of cash or credit, an instruction on hold, and a late or unmatched counterparty. Each shows up as a reason under PEND or PENF in the MT548.

In the European Union, the CSD Regulation applies cash penalties to failing participants for each business day of the fail, and ESMA notes that the penalty mechanism has applied since 1 February 2022. CSDs calculate and report these penalties to their participants, who pass them on to clients. Even outside the EU, persistent fails cost money: borrowing fees, buy-in risk, claims for lost income on corporate actions and broken client trust.

1. Read the reason code in the latest MT548 and decide whose action it needs.
2. For LACK: check pending receipts, recalls of lent securities and blocked balances; consider borrowing or a partial delivery where the market allows it.
3. For MONY: arrange funding or credit before the next settlement cycle.
4. For CLAC or CMON: contact the counterparty with the CSD references and agree a new expected date.
5. Record the expected settlement date (:98A::EXSE// when the custodian sends it) and chase daily until the confirmation arrives.

Daily checklist for settlement teams

• Every trade booked today has an instruction sent, and every instruction has an acknowledgement (PACK) by the custodian’s next status run.
• Every instruction due in the next settlement cycle is matched; NMAT items are worked with the counterparty before the cut-off.
• Every instruction due today is either confirmed (MT544 to MT547) or explained by a PEND or PENF reason.
• Settled quantities and amounts are booked from the confirmation, and cash postings agree with the cash statement.
• The MT537 open items equal your own open items; the MT535 positions equal your positions.
• Copy every reference exactly: your SEME comes back in :20C::RELA// in every status, confirmation and statement line.

Questions

What is the difference between MT541 and MT543?

MT541 is a receipt against payment: you receive securities and pay cash, as a buyer. MT543 is a delivery against payment: you deliver securities and receive cash, as a seller. Their confirmations are MT545 and MT547.

Which ISO 20022 message replaces MT540 to MT543?

One message, sese.023 Securities Settlement Transaction Instruction. The direction and payment type become two elements: SctiesMvmntTp (RECE or DELI) and Pmt (APMT or FREE). Status advices move to sese.024 and confirmations to sese.025.

What does NMAT mean in an MT548?

The CSD has not matched your instruction with the counterparty’s. The reason under :24B::NMAT// tells you why, for example CMIS (no counterparty instruction) or DMON (settlement amounts differ). See unmatched instructions.

What is the difference between PEND and PENF?

PEND means the matched instruction has not settled yet but can still settle on its intended date. PENF means it is failing: the intended date has passed or can no longer be met. Both come with a reason code.

How do I cancel a settlement instruction?

Send the same message type with 23G:CANC and the reference of the original in :20C::PREV// in a linkage block. The custodian answers with an MT548 cancellation status. Once matched, many CSDs need both parties to cancel.

Are MT540 to MT548 still used after November 2025?

Yes. Securities messages (category 5) were not part of the November 2025 payments deadline and remain in use on FIN alongside their ISO 20022 equivalents. See ISO 20022 migration for securities and payments.

Messages in this guide

• MT540Receive Free
• MT541Receive Against Payment
• MT542Deliver Free
• MT543Deliver Against Payment
• MT544Receive Free Confirmation
• MT545Receive Against Payment Confirmation
• MT546Deliver Free Confirmation
• MT547Deliver Against Payment Confirmation
• MT548Settlement Status and Processing Advice
• MT535Statement of Holdings
• MT536Statement of Transactions
• MT537Statement of Pending Transactions
• sese.023Securities Settlement Transaction Instruction
• sese.024Securities Settlement Transaction Status Advice
• sese.025Securities Settlement Transaction Confirmation
• semt.002Securities Balance Custody Report
• semt.017Securities Transaction Posting Report

Read next

• Triage table for unsettled trades: status, reason, who acts and where the fix is.
• Header, account, holdings, balances, prices, transactions and pending items, and how to reconcile them.
• Securities messages stay on ISO 15022 alongside ISO 20022 after the November 2025 payments switch; the MT to MX map.
• Announcement, entitlement, instruction, status, payment and reversal with MT564-568 and seev messages.
• Unmatched instruction (NMAT)
• PEND LACK (lack of securities)
• Failing settlement (PENF)
• Rejected instruction (REJT)
• MT535 reconciliation breaks