Instruction specifications – Swift ISO 20022 DCP mode – CEU – Direct link to SIX SIS – Switzerland
Reference
In the following tables M=Mandatory; O=Optional.
sese.023 (Securities Settlement Transaction Instruction) DELI with FREE
Settlement in SECOM | |||
M | Safekeeping SAC | Security account in T2S | |
O | Common trade reference - <Cmonld> | COMM a | |
M | Trade date - <TradDt> | Trade Date | |
M | Receiving depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA | |
M | Receiving P1 - <AnyBIC> | BIC of Participant in SECOMb | |
O | Receiving P1 - <SfkpgAcct/ID> | BPID code c | |
O | Receiving P2 – <AnyBIC> | Beneficiary's BIC in SECOM | |
O | Receiving P2 - <SfkpgAcct/ID> | Beneficiary Party's account | |
sese.023 (Securities Settlement Transaction Instruction) DELI with APMT and CRDT
Settlement in SECOM | ||
M | Safekeeping SAC | Security account in T2S |
O | Common trade reference - <Cmonld> | COMM a |
M | Trade date - <TradDt> | Trade Date |
M | Receiving depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA |
M | Receiving P1 - <AnyBIC> | BIC of Participant in SECOM b |
O | Receiving P1 - <SfkpgAcct/ID> | BPID code c |
O | Receiving P2 – <AnyBIC> | Beneficiary's BIC in SECOM |
O | Receiving P2 - <SfkpgAcct/ID> | Beneficiary Party's account |
M | Settlement amount - <SttlmAM\AM> | Cash amount (in CHF) |
--------------------------------------
a. The Common Reference may be populated based on market practices and in coordination with local counterparties.
b. If Party 1 Safekeeping Account is populated, it must be populated with BPID code.
If Party 1 BIC and Party 1 Safekeeping Account are populated, Counterparty's BIC will not be forwarded to the depository. Only the BPID code will be forwarded to the depository (:95R::REAG or DEAG/SCOM/BPID code)
If Party 1 BIC is populated without Safekeeping Account, then Counterparty's BIC will be forwarded to the depository.(:95P::REAG or DEAG//Counterparty's BIC)
c. BPID code = Business Partner Identification. Format is ccxxxxxx (where cc is the ISO country code) and this identifies the counterparty account at SIS.
sese.023 (Securities Settlement Transaction Instruction) RECE with FREE
Settlement in SECOM | |||
M | Safekeeping SAC | Security account in T2S | |
O | Common trade reference - <Cmonld> | COMM a | |
M | Trade date - <TradDt> | Trade Date | |
M | Delivering depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA | |
M | Delivering P1 - <AnyBIC> | BIC of Participant in SECOM b | |
O | Delivering P1 - <SfkpgAcct/ID> | BPID code c | |
O | Delivereing P2 – <AnyBIC> | Ordering Party's BIC in SECOM | |
O | Delivering P2 - <SfkpgAcct/ID> | Ordering Party's account | |
sese.023 (Securities Settlement Transaction Instruction) RECE with APMT and CRDT
Settlement in SECOM | ||
M | Safekeeping SAC | Security account in T2S |
O | Common trade reference - <Cmonld> | COMM a |
M | Trade date - <TradDt> | Trade Date |
M | Delivering depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA |
M | Delivering P1 - <AnyBIC> | BIC of Participant in SECOM b |
O | Delivering P1 - <SfkpgAcct/ID> | BPID code c |
O | Delivering P2 – <AnyBIC> | Ordering Party's BIC in SECOM |
O | Delivering P2 - <SfkpgAcct/ID> | Ordering Party's account |
M | Settlement amount - <SttlmAM\AM> | Cash amount (in CHF) |
-----------------------------------
a. The Common Reference may be populated based on market practices and in coordination with local counterparties.
b. If Party 1 Safekeeping Account is populated, it must be populated with BPID code.
If Party 1 BIC and Party 1 Safekeeping Account are populated, Counterparty's BIC will not be forwarded to the depository. Only the BPID code will be forwarded to the depository (:95R::REAG or DEAG/SCOM/BPID code)
If Party 1 BIC is populated without Safekeeping Account, then Counterparty's BIC will be forwarded to the depository.(:95P::REAG or DEAG//Counterparty's BIC)
c. BPID code = Business Partner Identification. Format is ccxxxxxx (where cc is the ISO country code) and this identifies the counterparty account at SIS.
sese.023 (Securities Settlement Transaction Instruction) DELI with FREE
Settlement in T2S (FoP only) | |||
M | Safekeeping SAC | Security account in T2S | |
O | Common trade reference - <Cmonld> | COMM a | |
M | Trade date - <TradDt> | Trade Date | |
M | Additional Transaction Type <FinInstrmAttrbts/FinInstrmAttrAddtlDtlss> | /POSTYP/TS | |
M | Receiving depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA e, f | |
M | Receiving P1 - <AnyBIC> | Counterparty's BIC d, h | |
O | Receiving P2 - <AnyBIC> | Beneficiary BIC if different from Party 1 OR <RcvgSttlmPties/Pty2/Id/PrtryId/Id>Beneficiary’s proprietary code, if different from Party 1<Issr> SCOM | |
O | Receiving P2 - <SfkpgAcct/ID> | Beneficiary Party's account | |
sese.023 (Securities Settlement Transaction Instruction) RECE with FREE
Settlement in T2S (FoP only) | |||
M | Safekeeping SAC | Security account in T2S | |
O | Common trade reference - <Cmonld> | COMM a | |
M | Trade date - <TradDt> | Trade Date | |
M | Additional Transaction Type <FinInstrmAttrbts/FinInstrmAttrAddtlDtlss> | /POSTYP/TS | |
M | Delivering depository BIC - <Dpstry/Id/AnyBIC> | INSECHZZSGA e, f | |
M | Delivering P1 - <AnyBIC> | Counterparty's BIC d, h | |
O | Delivering P2 - <AnyBIC> | Beneficiary BIC if different from Party 1 OR <DlvrgSttlmPties/Pty2/Id/PrtryId/Id>Ordering party’s proprietary code, if different from Party 1<Issr> SCOM | |
O | Delivering P2 - <SfkpgAcct/ID> | Ordering Party's account | |
------------------------------------
a. The Common Reference may be populated based on market practices and in coordination with local counterparties.
b. If Party 1 Safekeeping Account is populated, it must be populated with BPID code.
If Party 1 BIC and Party 1 Safekeeping Account are populated, Counterparty's BIC will not be forwarded to the depository. Only the BPID code will be forwarded to the depository (:95R::REAG/SCOM/BPID code)
If Party 1 BIC is populated without Safekeeping Account, then Counterparty's BIC will be forwarded to the depository.(:95P::REAG//Counterparty's BIC)
c. BIPID code = Business Partner Identification. Format is ccxxxxxx (where cc is the ISO country code) and this identifies the counterparty account at SIS.
Unified for New Opportunities April 2026 Clearstream Europe AG Page 57 of 82
d. If a client uses a BIC8, Clearstream Banking shall be entitled to modify the BIC8 by adding the default XXX suffix to comply with T2S settlement rules. Accordingly, such clients remain liable for any settlement fails that the use of the BIC8 may cause.
e. In the PSET field, clients are required to use BIC11. If a client uses a BIC8, such instructions will be rejected. This is a temporary limitation that should be solved shortly to apply the same rule as described in the footnote (d).
f. For cross-border transactions, the Place of Settlement must contain the BIC of the counterparty’s CSD.
If Party 1 BIC and Party 1 Safekeeping Account are populated, Counterparty's BIC will not be forwarded to the depository. Only the CUID number will be forwarded to the depository (:95R::REAG/CDSL/CUID number)
g. If Party 1 BIC is populated without Safekeeping Account, then Counterparty's BIC will be forwarded to the depository.(:95P::REAG//Counterparty's BIC)
If the counterparty is a financial institution or a bank, the account must be provided. The absence of the account in such cases may lead to settlement delays.
It is recommended to include the receiving account number to ensure that the receiving participant can recognise the delivery and settlement failure can be avoided.
h. Providing a safekeeping account in this party is not allowed
