sese.029 — Securities Settlement Information Notification
Non-status operational information during the settlement cycle. Late SSI change, market suspension, cut-off window change, extraordinary event — sese.029 is the informative channel from CSD to custodians, alongside status messages.
Purpose and place in the flow
sese.029 informs the parties of a settlement instruction of an event that changes the operational conditions without changing the legal status of the transaction. Three big families:
- SSI (Standard Settlement Instructions) change — a sub-custodian changes, a new intermediate party is added, a bank address is updated.
- Market information — listing suspension, instrument halt, shortened cut-off window, exceptional public holiday impacting settlement.
- Extraordinary event — urgent corporate action (tender offer, forced buyback), CSD system outages, liquidity constraints.
sese.029 is not a status (use sese.024) nor a modification (use sese.030/031): it's an enriching information broadcast to let the custodian adapt its downstream treatment, without restarting matching.
XML structure
- TxIdDtls — Transaction ID Details.
- NtfctnTp — Notification Type (SSIC = SSI change, MKTI = market info, EXCT = exceptional event).
- FinInstrmId — ISIN.
- SttlmDt — impacted settlement date.
- UpdtdSttlmInf — Updated Settlement Information: new field values (parties, accounts, places…).
- AddtlInf — explanatory narrative.
Key fields
TxIdDtls/AcctOwnrTxIdandAcctSvcrTxId— bilateral identifiers.NtfctnTp/Cd— notification type.UpdtdSttlmInf— the modified fields (typicallyDlvrgSttlmPtiesorRcvgSttlmPties).AddtlInf/Inf— plain-language narrative for the custodian.
XML example
DTCC informs BNP Paribas that a sub-custodian (Pty2) on the 14 May sese.023 transaction has changed: Citi is replaced by BNY Mellon, effective 16 May. The 15 May settlement target is unchanged, but BNP must update its ledgers before settlement:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:sese.029.001.06">
<SctiesSttlmInfNtfctn>
<TxIdDtls>
<AcctOwnrTxId>BNPP-SETT-20260514-001</AcctOwnrTxId>
<AcctSvcrTxId>DTCC-7894561230</AcctSvcrTxId>
</TxIdDtls>
<NtfctnTp>
<Cd>SSIC</Cd>
</NtfctnTp>
<FinInstrmId>
<ISIN>US0378331005</ISIN>
</FinInstrmId>
<SttlmDt>
<Dt>
<Dt>2026-05-15</Dt>
</Dt>
</SttlmDt>
<UpdtdSttlmInf>
<DlvrgSttlmPties>
<Dpstry>
<Id>
<AnyBIC>
<AnyBIC>DTCYUS33</AnyBIC>
</AnyBIC>
</Id>
</Dpstry>
<Pty1>
<Id>
<AnyBIC>
<AnyBIC>BNPAFRPP</AnyBIC>
</AnyBIC>
</Id>
</Pty1>
<Pty2>
<Id>
<AnyBIC>
<AnyBIC>BNYMUS3N</AnyBIC>
</AnyBIC>
</Id>
<AddtlInf>NEW SUB-CUSTODIAN — REPLACES CITIUS33 EFFECTIVE 20260516</AddtlInf>
</Pty2>
</DlvrgSttlmPties>
</UpdtdSttlmInf>
<AddtlInf>
<Inf>SSI UPDATE — SUB-CUSTODIAN CHANGED FROM CITI TO BNY MELLON FOR THIS TRADE</Inf>
</AddtlInf>
</SctiesSttlmInfNtfctn>
</Document> NtfctnTp/Cd = SSIC— SSI change.UpdtdSttlmInf/DlvrgSttlmPties/Pty2— new sub-custodian BIC (BNYMUS3N).AddtlInf/Inf— clear narrative explaining the change and its timing.
Common pitfalls
- sese.029 / sese.030 confusion — sese.029 informs; sese.030 requests modification. Do not mix: a sese.029 with no action on the custodian side requires no response.
- Empty UpdtdSttlmInf — if the message is informative without a modified field, omit UpdtdSttlmInf and use AddtlInf only.
- Unknown NtfctnTp — using a non-standard notification code (outside SSIC/MKTI/EXCT) triggers ETL rejects. Always check the XSD version for added codes.
- Timing too late — a sese.029 sent after settlement target loses operational value. The CSD should handle those cases as post-mortem via sese.026 or accounting correction.
- No narrative — a sese.029 with UpdtdSttlmInf but no AddtlInf forces the custodian to guess the change context. Always document.