SD-12.4 — Trade Settlement

Business Domain: BD-12 Investment Operations & Servicing (Back office) · Applies: PUB

Purpose

Completes the exchange of securities and cash that finishes a trade — instructing the custodian or settlement agent, matching the instruction against the counterparty, and seeing the trade through to settled or, where it fails, through fail management. A trade is not done when it is executed and confirmed; it is done when securities and cash have actually changed hands, days later, through a different infrastructure. SD-12.4 is that final step. It exists as a distinct capability because settlement runs through custodians and central securities depositories, happens on a contractual date (T+1 in most major markets), and fails in ways execution does not — carrying cost, counterparty exposure and regulatory penalty. It is not confirmation — that is SD-12.3, which produces the matched trade SD-12.4 settles — and it is not custody oversight — that is SD-12.5. SD-12.4 processes the settlement event; SD-12.5 oversees the assets once settled.

Service Operations

Settlement instruction generation — create the settlement instruction for each confirmed, matched trade, at the per-portfolio allocation grain, carrying the standing settlement instruction detail.
Instruction transmission and matching — send the instruction to the custodian or settlement agent and match it against the counterparty’s instruction at the place of settlement.
DvP / RvP processing — process delivery-versus-payment and receive-versus-payment settlement, the simultaneous-leg mechanism that eliminates principal risk; handle free-of-payment transfers as the explicit exception.
Settlement monitoring — track each instruction through its status — instructed, matched, settled — against the contractual settlement date.
Fail management — identify failing settlements, diagnose the cause (lack of securities, lack of cash, unmatched, counterparty fail), and work them to resolution or buy-in.
Settlement-penalty processing — accrue and process the penalties a settlement-discipline regime imposes for a fail, and reconcile them against the counterparty.
Buy-in administration — where a fail persists beyond the permitted window, administer the buy-in that closes it out.

Inputs and outputs

Inputs: confirmed, matched trades from SD-12.3; standing settlement instructions; custodian and place-of-settlement detail; cash availability from SD-11.1.
Outputs: settled trades, fail status and settlement-penalty records — consumed by SD-12.1 Investment Book of Record (IBOR) and SD-12.2 ABOR (the settled position), SD-12.5 Custody & Safekeeping Oversight, SD-12.10 Reconciliation, SD-11.1 Cash Management (the cash leg), and SD-07.2 Credit & Counterparty Risk Management (settlement-counterparty exposure).

Entities

Consumes: E-05 Transaction (transaction_type = trade), PB-05 Allocation (settlement is at the allocation grain), E-03 Portfolio / Mandate, E-01 Legal Entity (custodian and counterparty roles); the SD-11.1 cash availability; the SD-12.3 confirmed, matched trades.
Owns: PB-06 Settlement Instruction — SD-12.4 is the authoritative source for the settlement instruction and its lifecycle, including the failing state and fail_reason.
Open question: the settlement-fail lifecycle — fail, penalty accrual, buy-in — as an explicit event sub-model, and the SSI as its own reference entity, are both flagged on PB-06.

Standards

ISO 20022 securities-settlement (sese) family — the settlement-instruction and settlement-status messages; and the legacy ISO 15022 MT54x messages (MT540–MT543).
CSDR (the EU Central Securities Depositories Regulation) — the settlement-discipline regime behind settlement-penalty and mandatory-buy-in processing.
T+1 settlement — the shortened settlement cycle adopted across major markets; it compresses the post-trade window and raises the operational stakes of every prior lifecycle stage.
DvP — the delivery-versus-payment principle that makes the securities and cash legs simultaneous.

Open extensions

The Service-Operation-level input/output contracts.
The settlement-fail lifecycle as an explicit event sub-model — the open question on PB-06.
Partial settlement, and the relationship between an instruction and its partial settlements.