Settlement services French Registered Securities - France
The following French registered securities are eligible for settlement:
Essentially Registered Securities - “Valeurs Essentiellement Nominatives” (VEN)
For these securities, registration with the issuer is mandatory. VEN securities are by default registered in the name of CBF (except for French residents or specified otherwise by the customers or counterparties).
Occasionally Registered Securities - “Valeurs Occasionnellement Nominatives” (VON)
These securities can exist in bearer or registered form. The bearer form can be settled whereas the registered form is excluded from any settlement activity, except when a portfolio transfer occurs without a change of beneficial owner; Registration is optional and at the discretion of the customer. In case of registration, it must be done in the name of the final beneficial owner (BO).
Loyalty Bonus Shares (LBS) - "Primes de fidélité" (PF) – (CBF and CBL only)
These securities are a subcategory of VON securities. In order to qualify for a loyalty bonus program, the securities must be registered in the name of the BO. They give the right to a loyalty bonus if the temporary LBS are held by the BO for a pre-defined amount of time (typically 2 years, sometimes 4 years). The temporary LBS (PF) and LBS ISINs cannot be settled. In order to sell them, they must first be converted into VON registered securities and then converted to bearer securities (2-step process). Any right to a loyalty bonus will be lost during this process. The registration activity is decoupled from settlement, but must occur in close proximity. If this is not respected, penalty fees will be levied by the market.
This table summarises which type of securities are eligible via which link:
Form | Eligibility CBL | Eligibility CBF | Eligibility LuxCSD | |
VEN | Registered | Direct link to CBF a for holding Euroclear France/T2S eligible securities | Direct link to Euroclear France a | Not eligible |
VON | Bearer and Registered | Direct link to CBF for holding Euroclear France/T2S eligible securities | Direct link to Euroclear France | Direct link to CBF for holding Euroclear France/T2S eligible securities (Bearer only) |
Loyalty bonus shares | Bearer and Registered | Direct operated link via BNP Paribas S.A. to Euroclear France | Direct link to Euroclear France | Not eligible |
a. CBF will access Euroclear France as investor CSD via LuxCSD.
Account structure
VEN
| CBF customers | No segregated or specific account is required to safekeep and settle VEN securities in CBF (existing main account in CASCADE can be used). |
| CBL customers | No segregated or specific account is required to safekeep and settle VEN securities in CBL (existing 5-digit customer account in Creation can be used). |
| LuxCSD customers | Service not available. |
VON in registered form, temporary LBS and final LBS (CBF and CBL only)
| CBF customers | Sub-account “xxxx203” is used to hold VON in registered form, temporary LBS and final LBS ISINs This sub-account belongs to account type 240/Konto Art 240 (Registered VON) and is configured for free of payment transactions only with TEILNAHME-DVP=N. Sub-accounts XXXX-203 are automatically opened when customers open a main account XXXX-000. The settlement of securities in registered form is not allowed. All securities in the registered account must be registered in the beneficial owner’s (BO) name. These securities are safekept in a sub-account where:
Positions held on the sub-account 203 can only be moved if deregistered or in the context of a portfolio migration with no change of BO. |
| CBL customers | A dedicated account (registered account) in CBL is required for holding French securities in registered form only. If a new registered account will be opened, customers holding VON in registered form must provide CBL with the list of beneficial owners. The Account Application form is available on the Clearstream website under Key Documents/ICSD/Account Opening Forms. The registered account will be linked to the customer’s existing account identified at account opening request as ‘’over linked account’’ . This account will be used to credit any security proceeds in bearer form deriving from corporate actions applicable to a position registered in the BO name. The settlement versus payment of securities in registered form is not allowed. All securities in the registered account must be registered in the BO name. These securities are safekept on this dedicated account where:
|
Securities Reference Data
VEN and VON in bearer or registered form, LBS (CBF, CBL only)
| CBF customers | The legal form of the French registered securities is displayed in WSS Online Plus in the field “Französische Namensaktien” with the following possible values:
And in Xact Web Portal as follows:
|
| CBL customers | The legal form and the sub category of instrument of the French Registered Securities is displayed in Xact Web Portal and Codelist in the field “Legal form” with the following possible values:
and the sub-category field with the following values:
|
| LuxCSD customers | Service not available. |
Settlement flows
Registration process
Clearstream Banking will handle the registration process for VEN, VON directly with Euroclear France (Issuance of BRN – “Bordereau de Référence Nominative”) on behalf of customers.
If registration fails with Euroclear France or the issuer, Clearstream Banking will inform customers accordingly, if action is required from customers. Receipt instructions will trigger a registration while delivery instructions will trigger a de-registration.
VEN
| CBF customers | Generally, all VENs will be registered in the name of CBF as a default. For an individual registration, registration or de-registration can be requested in the settlement instruction by populating either :70D::REGI of the MT54x or using CASCADE/CASCADE-PC. Registration or de-registration information is requested in the following cases:
For registration into a BO name, Clearstream Banking will block the position and transfer it to sub-account xxxx851. The blocked position will be reported via MT564 under “Blocked balance” (except for Drawing events). If a customer would like to sell their position or participate to a voluntary corporate action, they will first have to request the unblocking of such position to CBF via an MT599 sent for the attention of “Settlement OCB Cross Border”. |
| CBL customers | MT54x instructions (internal, external and Bridgea) will be enhanced with field :70D::REGI (Registration Details in Sequence E/ Sequence E1 Settlement Parties) to allow for registration under the BO name. For further information on the format, please see the instruction specifications. Field :70D::REGI is required for the following transactions:
For registration into a BO name, Clearstream Banking will block the position. If a customer would like to sell their position, they will first have to request the unblocking of the position to CBL via an MT599 sent for the attention of “Settlement OCB Cross Border”. The message should contain the following details:
|
| LuxCSD customers | Service not available. |
b. Bridge instructions are permitted however instructions containing registration details will be treated as follows in terms of registration handling.
No position registered in BO name will be transferred in Euroclear Bank books.
Clearstream will de-register the position in the name of the BO and re-register it in the name of Clearstream Banking AG.
It will be up to the counterparty in Euroclear Bank to ask for a re-registration if securities need to be held in the name of the BO.
If the position needs to be held in the BO name at Euroclear Bank, Clearstream will recommend to transfer the position via cross border instruction (Instruction specifications - France).
VON in registered form, LBS (CBF and CBL only)
| CBF customers | Conversion Such conversion may be requested by submitting a free of payment already matched instruction. This is required to request a conversion from bearer to registered form between the customer’s main account and the sub-account “xxxx203” and vice versa to de-register. Portfolio transfer A free of payment instruction (subject to matching) is required to request a portfolio transfer between sub-accounts xxxx-203 as long as there is no change of BO.
|
| CBL customers | Conversion
Portfolio transfer
|
| LuxCSD customers | Service not available. |
Registration details and format
VEN, VON in registered form, temporary and final LBS
| CBF and CBL customers | For any registration, the BO details are required under :70D::REGI (MT54x) or :70E::REGI (MT565). If a new BO has to be registered, full details are requested. If the BO is a known one, the minimum details are required. Settlement instructions :70D::REGI should be used to declare BO details; or CASCADE/CASCADE-PC. The line break at the end of a line (35th character) cannot be interpreted as a space. If a space is to be set at the beginning or the end of a line, the customer has to enter the space. All elements pertaining to the registration must be entered consecutively and the last element of the registration details must not finish with a slash (please see below example). Alternatively, an MT599 can be used only if the BO details exceed the capacity of field :70D::REGI. For a new BO, the following information is required
For existing BOs with an Issuer Identifier (ICER) already assigned, full details are not necessary. Minimum details must be provided and must contain the following information: Simple registration details (One BO assigned to one Issuer ID)
Example: :70D::REGI///HTYP 03/NAME Smith/FNAM John/ICER 13090 One slash should be entered to start the input of details. Then a space needs to be included between the qualifier (e.g. HTYP) and the information required, then a slash immediately after the information. This must be repeated until all elements pertinent to the registration are input. Note: All elements pertaining to the registration must be entered consecutively and the last element of the registration details must not finish with a slash. Complex registration details (Multiple BOs assigned to one Issuer ID)
Example: :70D::REGI///HTYP 03/NAME Smith/FNAM John/ICER 13090/HTYP 03/NAME Brown/FNAM James/HTYP 03/NAME Bond/FNAM Jack One slash should be entered to start the input of details. Then a space needs to be included between the qualifier (e.g. HTYP) and the information required, then a slash immediately after the information. This must be repeated until all elements pertinent to the registration are input. Note: All elements pertaining to the registration must be entered consecutively and the last element of the registration details must not finish with a slash. Corporate action instructions Field :70E::REGI must be used for registration details, the usage of minimum details is strongly recommended : For existing BOs with an Issuer Identifier (ICER) already assigned, full details are not necessary. Minimum details must be provided and must contain the following information: Simple registration details (One BO assigned to one Issuer ID):
Example: :70D::REGI///HTYP 03/NAME Smith/FNAM John/ICER 13090 One slash should be entered to start the input of details. Then a space needs to be included between the qualifier (e.g. HTYP) and the information required, then a slash immediately after the information. This must be repeated until all elements pertinent to the registration are input. Note: All elements pertaining to the registration must be entered consecutively and the last element of the registration details must not finish with a slash. Complex registration details (Multiple BOs assigned to one Issuer ID):
Example: :70D::REGI///HTYP 03/NAME Smith/FNAM John/ICER 13090/HTYP 03/NAME Brown/FNAM James/HTYP 03/NAME Bond/FNAM Jack One slash should be entered to start the input of details. Then a space needs to be included between the qualifier (e.g. HTYP) and the information required, then a slash immediately after the information. This must be repeated until all elements pertinent to the registration are input. All elements pertaining to the registration must be entered consecutively and the last element of the registration details must not finish with a slash. Note: For corporate action instructions sent via SWIFT, field :70E::INST can be used, but straight-through processing will not be possible and Clearstream will have to repair the instruction manually, incurring repair fees. For a new BO, the following information is required
Alternatively, an MT599 can be used only if the BO details exceed the capacity of field :70E::REGI. If an MT599 is sent because the BO details to be provided exceed the capacity of :70E::REGI or :70E::INST, in order to avoid rejection of the MT565, customers should input the following statement "Please refer to MT599". The details should be sent in the MT599 as follows:
Note: For corporate action instructions sent via SWIFT, field :70E::INST can be used, but straight-through processing will not be possible and Clearstream will have to repair the instruction manually, incurring repair fees. |
| LuxCSD customers | Service not available. |
a. Personal entity applies if the Holder Type values are different from 01, 02 and 07 (data are available in the new query "Registered Securities: Beneficial Owner Details" in Xact Web Portal).
Unblocking request content
VEN registered in BO name
CBF and CBL customers
Unblocking request for delivery settlement instruction via MT599 instructions or Message Exchange via Xact Web Portal will contain the following:
- Account number (CBL, CBF or CBFi 6-series account number);
- ISIN code;
- Quantity;
- Intended/Requested settlement date;
- Transaction reference number (Sender'Reference);
- Beneficial owner details (simple registration details);
- Holder Type;
- Surname or Corporate name;
- Forename or Corporate name (only for personal entity);
- Issuer Identifier.
For delivery instructions (DvP, DFoP) the related position will be unblocked by CBF based on the MT599.
For receipt instructions (RvP, RFoP) the related position will be blocked by CBF based on BO details available in MT54X
Registration details format table
Customers are reminded that all elements pertaining to the registration process of any Beneficial Owner details required for French Registered Securities are assumed to have been already checked through the Clearstream customer's usual KYC/AML procedure with their underlying customers.
Note: at issuer’s request, a registration may be subject to fulfillment of additional piece of information (see issuers’ verification rights section).
Field | Length and | Mandatory/ | Values | |
HTYP | Holder type | 2N | M (if registration information is provided) | 01 Company |
NAME | Surname or Corporate name | 32AN | M (if registration information is provided) | n/a |
FNAM | Forename or Corporate name (cont.) | 32AN | M (If Holder type <> 01 or 02 or 07) O (If Holder type = 01 or 02 or 07) | n/a |
ICER | Issuer Identifier | 23N | O | For example: 13090 In general, this field is optional. However, it must be filled in certain cases, such as:
|
MNAM | Maiden name or Corporate name (cont.) | 32AN | O | n/a |
WFNA | Woman’s forename or Corporate name (cont.) | 32AN | O | n/a |
NACO | Nationality code of the holder | 3AN | C | If this field is input, its value must conform to the ISO 3166 standard. This field is mandatory if identifier has not been implemented previously |
CDCO | Country code of the address | 3AN | C | If this field is populated, its value must conform to the ISO 3166 standard. In general, this field is optional. However, it must be input in certain cases. For example, it must be input if the identifier is not input |
BUID | Building | 32AN | O | n/a |
STRE | Street | 32AN | O | n/a |
ADIN | Additional address information | 32AN | O | n/a |
CDPO | Postal code | 5AN | O | If this field is populated, its value must conform to postal standards. |
CITY | City | 27AN | O | If this field is populated, its value must comply with postal standards. |
PSTT | Personal title | 32AN | O | n/a |
The above table is compiled based on information extracted from the ESES Data Dictionary.
Issuers’1 verification rights
As per market standards, an issuer may request that Clearstream Banking send some relevant documents, either before or after the registration of the BRN, to justify information pertaining to the registration’s details
The issuer can request it either for sampling purposes or for more complete information related to a change file.
The type of documents, qualified as relevant by the issuer, will be communicated to Clearstream Banking customers upon issuer’s request, and are to be received by Clearstream Banking from the concerned customers.
Clearstream Banking highly recommends its customers to ensure that all documentation, justifying the customer’s instruction, are collected upfront from its underlying customers. This will allow Clearstream Banking customers to comply with market standard and be ready to promptly share the documentation, in case of issuer’s request.
If the issuer requests to send relevant documents before registering the BRN
According to the French market standards, Clearstream Banking must respond to the issuer’s request based on its customers response, within 48 hours upon receipt of the request.
If the issuer does not receive the documents within the allowed timeframe, it may reject the file.
Note: Given the short market deadline, Clearstream Banking will inform its customers via MT599 based on issuer’s request and require its customers to respond within one business day upon Clearstream’s Banking's request is sent to the customers.
If the issuer requests to send relevant documents after a BRN is accepted
After accepting the BRN, the issuer has one calendar month to request relevant documents.
Clearstream Banking will duly inform its customers via MT599 based on the issuer’s request and require its customers to respond within four business days upon which Clearstream Banking's request is sent to the customers.
Exceptionally, an issuer might still request after the one month calendar period that Clearstream Banking send some relevant documents.
Important Note: Clearstream Banking customers are fully responsible for:
- Safekeeping and storing all original documents or copies certified by notaries and in accordance with customers market law.
- Responding to Clearstream Banking request in due to time to allow Clearstream Banking to respond to the issuers within the timeframe foreseen by the market.
Any delay or missing document may lead the issuer to reject the request if not accepted yet or reverse the original request, if already accepted.
It is further clarified that Clearstream Banking (CBL and CBF) shall not be liable to the customer for any loss, claim, liability, expense or damage arising from any action taken by Clearstream Banking in connection with the above procedures.
In the event where the customer fails to fulfil any of its obligations towards Clearstream Banking, in particular in relation to the delivery in due time of the requested documentation (including inaccuracy, incompleteness of the provided information to Clearstream Banking), Clearstream Banking shall not be held liable for any resulting loss, claim, liability, expense or damage suffered by the customer and/or any final beneficiaries and the customer undertakes to fully indemnify Clearstream Banking against any such loss, claim, damage, liability or expense imposed on or incurred by or asserted against Clearstream Banking.
Sending of supporting documents
Clearstream Banking customers must send the requested document or a copy certified by a notary translated in French and English or French and German.
This will be sent via post or email to Clearstream Banking:
Email: Your local responsible client support.
Postal address: Clearstream Banking AG, Settlement Services OCB FRS, EA.08.301, 60485 Frankfurt am Main, Germany
Additional services
Restriction code handling
At issuer books level, the set of information constituting the registration is made of several elements such as: issuer ID, name, surname, address, city, nationality and also a restriction code whenever applicable.
The restriction code indicates a status that restricts the rights of the securities holder.
There are three categories of restrictions on the market:
- Related to the holder's person;
- Related to a usufruct and bare ownership;
- Other restrictions.
There can be a combination of restrictions.
Restriction codes attached to the holder
Code | Legal status | Holder type | Surname/Corporate name |
Minors | |||
AJ | Natural guardianship (authority of both parents) Tutorship by nature (authority of one parent) | 03, 04, 05, 06 or 08 | of the tutor by nature |
AS | Special guardianship | 03, 04, 05, 06 or 08 | of the special guardian |
TT | Testamentary guardianship | 03, 04, 05, 06 or 08 | of the testamentary guardian |
TL | Statutory guardianship | 03, 04, 05, 06 or 08 | of the statutory guardian |
TD | Under a guardian appointed by the family council | 03, 04, 05, 06 or 08 | of the appointed guardian |
TX | Under more than one type of guardianship | 03, 04, 05, 06 or 08 | guardian of the estate but not of the person |
Wards of the state | Blank | Blank | |
TP | Trusteeship | 01, 02 or 07 | of the trustee |
ME | Emancipated minors | Blank | Blank |
Majors | |||
SJ | Under power of attorney | 01, 02, 03, 04, 05, 06, 07 or 08 | of the agent |
CU | Under curatorship | 03, 04, 05, 06 or 08 | of the curator |
CS | Under curatorship ad hoc | 03, 04, 05, 06 or 08 | of the curator ad hoc |
TN | Under natural guardianship (authority of both parents) | 03, 04, 05, 06 or 08 | of the natural guardian |
TA | Under a guardian appointed by the family council | 03, 04, 05, 06 or 08 | of the appointed guardian |
TJ | Under tutorship by nature (authority of one parent) | 03, 04, 05, 06 or 08 | of the tutor by nature |
TE | Under partial guardianship | 01, 02, 03, 04, 05, 06, 07 or 08 | of the partial guardian |
HF | Family empowerment | 01, 02, 03, 04, 05, 06, 07 or 08, blank | of the legal tutor |
Absence | |||
AB | Declared | blank | blank |
AP | Presumed | 01, 02 or 07 | of the provisional administrator |
Other | |||
RE | Bare trusteeship | 01, 02 or 07 | of the beneficiary |
Restriction codes attached to a usufruct and naked ownership
Code | Legal status | Holder type | Surname/Corporate name |
NP | Joint naked ownership(#) | 01, 02, 03, 04, 05, 06, 07 or 08 | of the naked owner |
UT | Full usufruct(#) | 01, 02, 03, 04, 05, 06, 07 or 08 | of the usufructuary |
UP | Partial usufruct(#) | 01, 02, 03, 04, 05, 06, 07 or 08 | of the usufructuary |
UC | Joint usufruct(#) | 01, 02, 03, 04, 05, 06, 07 or 08 | of the usufructuary |
UL | Usufruct for a term(#) | 01, 02, 03, 04, 05, 06, 07 or 08 | of the usufructuary |
UX | Usufruct on condition expressed | 01, 02, 03, 04, 05, 06, 07 or 08 | of the deceased |
US | Successive usufruct | 01, 02, 03, 04, 05, 06, 07 or 08 | of the second usufructuary |
UR | Remainder usufruct | 01, 02, 03, 04, 05, 06, 07 or 08 | of the second usufructuary |
(#) The "holder type" and "surname/corporate name" are optional
Restriction codes attached to other types of situation
Code | Legal status | Holder type | Surname/Corporate name |
Donation | |||
DR | Donor’s right of survivorship | blank | blank |
IA | Restraint on alienation | blank | blank |
Succession | |||
SV | Vacant | blank | blank |
SD | Escheat | blank | blank |
SN | Represented by a notary | 01, 02 or 07 | of the notary |
SP | Represented by a provisional administrator | 01, 02 or 07 | of the provisional administrator |
Other | |||
NT | Pledged securities | 01, 02 or 07 | of the creditor |
DT | blank | blank | |
SQ | Securities in a dowry estate | 01, 02 or 07 | of the receiver |
AD | Securities in receivership | blank | blank |
AV | Securities owned by an affiliated person | blank | blank |
DG | Employee stock ownership plan (Act 73-1196 27/12/73) | blank | blank |
PA | 3% stock dividend (Act 70-1322 of 31/12/70) | blank | blank |
SO | Profit-sharing plan (Order 86-1136 of 21/10/86) | blank | blank |
EC | Community exclusion | 01, 02, 03, 04, 05, 06, 07, 08, or blank | any |
SA | Free share plan Business | 01, 02, 03, 04, 05, 06, 07, 08, or blank | any |
BS | creator shares | 01, 02, 03, 04, 05, 06, 07, 08, or blank | any |
The three above tables are extracted from the ESES Data Dictionary.
If customers would like to apply, amend or delete an existing restriction code, an instruction via free format message (MT599 or Message exchange via Xact Web Portal) should be sent to the attention of OCB – FRS.
The instruction should contain the following:
- The account number (CBL, CBF or CBFi 6-series account number)
- The number of shares and ISIN;
- The defined BO details: /HTYP/NAME/FNAM/WFNA/MNAM/ICER/NACO/CDCO/STRE/CDPO/CITY;
- In addition, the instruction must contain the justification for adding, modifying or deleting a restriction code;
- Plus any additional information/documentation, translated in French for issuers and in English or German for Clearstream Banking Operations, in order to fulfill the issuer’s request (see further details under Issuers’ verifications rights).
Handling update on BO details at the customer’s request
Customers are required to qualify the reason of the re-registration request defined under a. to e. and submit the free format message to the attention of OCB - FRS:
- Inheritance with one or more heirs;
- Gifts with or without change of custodian account holder;
- From single BO to a jointly and/or BO or vice versa (for instance, because of marriage or divorce etc.);
- Personal data changes, such as title, address, name etc.;
- Consolidation of issuer ID’s for one and the same BO.
The instruction, being a SWIFT MT599 or message exchange Xact Web Portal, should contain the following details:
- Account number (CBL, CBF or CBFi 6-series account number);
- The defined details depending on the nature of the reregistration request with the following values: /HTYP/NAME/FNAM/WFNA/MNAM/ICER/NACO/CDCO/STRE/CDPO/CITY;
- Plus any additional information/documentation translated in French for the issuers and in English or German for Clearstream Banking Operations, in order to fulfill the issuer’s request (see further details in section Issuers’ verifications rights).
For Inheritance with one or more heirs’ cases
In addition, the instruction must contain:
- The number of shares and ISIN code, the issuer ID, holder type, full name and address of the deceased BO;
- The number of shares and ISIN code, issuer ID(s), holder type, full name(s) and address per heir BOs;
- The BO death date;
- The issuance date, the court and reference number of the inheritance document as well as the inheritance ratio for each heir name.
For gifts with or without change of custodian account holder cases
In addition, the instruction must contain:
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the donor;
- The number of shares and ISIN, issuer ID(s), holder type, full name(s) and address per done BOs.
From single BO to a jointly and/or BO or vice versa (for instance, because of marriage or divorce etc.) cases
In addition, the instruction must contain:
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the current BO data;
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the new BO data.
For personal data changes, such as title, address, name etc. cases
In addition, the instruction must contain:
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the current BO data;
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the new BO data.
For consolidation of issuer ID’s for one and the same BO cases
In addition, the instruction must contain:
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the current two or more issuer ID BO date;
- The number of shares and ISIN, the issuer ID, holder type, full name and address of the issuer ID BO data to be used going forward.
Reporting of beneficial owner details
When a customer sends a settlement instruction or a corporate action instruction being subject to registration or de-registration customers may check whether the registration or de-registration process has started.
All details related to the registration of each individual beneficial owner are available via a query in Xact Web Portal.
The query can be run under Settlement / Securities / Registered securities: beneficial owner details.
After the instruction has reached the status “settled”, customers can see if the Bordereau de Référence Nominative (BRN) has been created.
If the BRN has been created for release to ESES, there will be a new row stating “pending registration” or “pending de-registration”. However, the BRN could still be rejected by either ESES or the issuer. Acceptance or rejection handled at the issuer level may take up to several days if the BRN cannot be treated in STP mode on the issuer’s side.
Once the BRN is accepted, the position will become "Final BO Position".
If this row is not present, it means that the registration details are either incomplete or wrong and a BRN cannot be created by Clearstream.
Procedure for domestic counterparties
CBL
CBL depository – CBF | |
Place of settlement | DAKVDEFFXXX |
Delivering/Receiving Agent | CEDELULLXXX |
SAFEa of the DEAG/REAG | Not to be instructed. If instructed, it must be the valid CBL SAC: |
Buyer/Seller | BIC11 of the CBL customer |
a. Although the safekeeping account of Party 1 (REAG/DEAG) is an optional matching field in T2S, if it is present on one instruction only it will only match with instructions instructed by this account. As CBL does not forward its own SAC to the settlement parties, if the customer counterparty instructs the SAFE of REAG/DEAG it must match CBL's SAC in T2S exactly.
We encourage customers to ask their counterparties not to include the SAFE of the DEAG/REAG in their instructions (also called securities account of the delivering/receiving party).
b. In case of portfolio transfers (VEN registered in BO name), we recommend customers to agree with counterparties to ensure the BRN is issued by the delivering party with a transaction code TO.
CBF
Place of settlement | DAKVDEFFXXX |
Delivering/Receiving Agent | T2S Party BIC11 CBF participant |
LuxCSD (VON in Bearer form only)
Place of settlement | LUXCLULLXXX |
Delivering/Receiving Agent | T2S Party BIC11 LuxCSD participant |
------------------------------------------
1. Issuers are intended to be either directly the issuer of the security or the financial institution appointed by the issuer to process the registrations. Such institution will hold the function of “Teneur de registre” on the French market.