Transfer of securities from CBF to CBL - Portugal
Delivery instruction specifications in CBL
CreationOnline
Deliver Free
M | Trade Date | Trade date |
M | Place of Settlement | BIC |
Party | DAKVDEFFXXX | |
M | Receiving Agent | BIC |
Party | T2S Party BIC11 of CBF customera | |
Ob | Seller | BIC |
Party | BIC11 of CBFi customer |
Xact Web Portal
Deliver Free
M | Trade date | Trade date |
Receiving settlement parties | ||
M | Depository Format | BIC |
Depository Identifier | DAKVDEFFXXX | |
M | Party 1 Format | BIC |
Party 1 Identifier | T2S Party BIC11 of CBF customera | |
Ob | Delivering settlement parties | |
Depository Format | BIC | |
Depository Identifier | DAKVDEFFXXX | |
Party 1 Format | BIC | |
Party 1 Identifier | CEDELULLXXX | |
Party 2 Format | BIC | |
Party 2 Identifier | BIC11 of CBFi customer |
Xact via SWIFT and Xact File Transfer
MT542 Deliver Free
Seq | ||||
M | :98A: | :TRAD | //Trade date | B |
M | :97A: | :SAFE | //6 series account | C |
M | :95P: | :PSET | //DAKVDEFFXXX | E1 |
M | :95P: | :REAG | //T2S Party BIC11 of CBF customera | E1 |
Ob | :95P: | :SELL | //BIC11 of CBFi customer | E1 |
a. It is not recommended to add the T2S SAC (:97A::SAFE//DAKVXXXXXXX) of the REAG. If required, it must be used in the CBF receipt instruction as well to allow matching.
b. CBL will default the customer’s matching BIC when sending the instruction to T2S. Customers should therefore not instruct this field unless they wish to match on a different BIC.
Receipt instruction specifications in CBF
CASCADE- Receipt (KVEE/MI)
Receive Free
M | Gut-Kto | T2S PARTY BIC of CBF participant (alternative 4-digit account master or 7-digit account) |
M | Last-Kto | CEDELULLXXXa |
M | Schlusstag | Trade Date |
M | Lieferer-P2 - BIC | BIC11 CBL customerb |
CASCADE-PC
Receive Free
M | Credit account | T2S PARTY BIC of CBF participant (alternative 4-digit account master or 7-digit account) |
M | Debit account | CEDELULLXXXa |
M | Trade Date | Trade Date |
M | Seller-P2 – BIC | BIC11 CBL customerb |
SWIFT in ISO15022 format (ICP mode) – CASCADE via SWIFT connectivity
MT540 Receive Free
Seq | ||||
M | :98A: | :TRAD | //Trade date | B |
M | :97A: | :SAFE | //4-digit account master or 7 or 8-digit account in CBF | C |
M | :95P: | :PSET | //DAKVDEFFXXX | E1 |
M | :95P: | :DEAG | //CEDELULLXXXa | E1 |
M | :95P: | :SELL | //BIC11 of CBFi customerb | E1 |
SWIFT in ISO15022 format (ICP mode) – OneClearstream
MT540 Receive Free
Seq | ||||
M | :98A: | :TRAD | //Trade date | B |
M | :97A: | :SAFE | // 8-digit account in CBF | C |
M | :95P: | :PSET | //DAKVDEFFXXX | E1 |
M | :95P: | :DEAG | //CEDELULLXXXa | E1 |
M | :95P: | :SELL | //BIC11 of CBFi customerb | E1 |
SWIFT in ISO20022 format (DCP mode)
sese.023 Securities Settlement Transaction Instruction RECE with FREE
M | Trade date – <TradDt> <Dt> | Trade Date |
M | Safekeeping Account – <QtyAndAcctDtls> <SfkpgAcct> <Id> | Customer SAC |
Delivering Settlement Parties – <DlvrgSttlmPties> | ||
M | Depository – <Dpstry> <Id> <AnyBIC> | DAKVDEFFXXX |
M | Party 1 – <Pty1> <Id> <AnyBIC> | CEDELULLXXXa |
M | Party 2 – <Pty2> <Id> <AnyBIC> | BIC11 of CBFi customerb |
__________________________________
Xact Web Portal
Receive Free
M | Trade date | Trade date |
Delivering settlement parties | ||
M | Depository Format | BIC |
Depository Identifier | DAKVDEFFXXX | |
M | Party 1 Format | BIC |
Party 1 Identifier | CEDELULLXXXa | |
M | Party 2 Format | BIC |
Party 2 Identifier | BIC11 of CBFi customerb |
__________________________________
a. It is not recommended to add the T2S SAC (Party 1 Safekeeping account: DAKVXXXXXXX) of the Party 1 Identifier. If required, it must be used in the CBL delivery instruction as well to allow matching.
b. This must be the matching BIC linked to the CBFi 6-series account in CBL. If the customer wishes to match on a different BIC11, this field must also be present on the instruction on the 6-series account sent to CBL.