Settlement services - Greece - BOGS


Pre-matching service

The table below summarises CBL and CBF/LuxCSD's pre-matching service for external settlement instructions, as well as the pre-matching method and start time in the market. For details of CBL and LuxCSD's pre-matching services, see Pre-matching services for external settlement instructions.

The hold and release feature available in T2S will be used by CBL, CBF and LuxCSD for the pre-matching of settlement instructions in T2S.

Service offered

Method employed

(local time)

All securities

CBF and LuxCSD

The T2S hold/release process allows for a released transaction to be set back to hold as long as it has not settled. Instructions that were sent on “Hold” can be released via a corresponding MT540 – MT543 “NEWM”. The status of a CBF/LuxCSD instruction can be changed via a modification (MT530) until its final settlement. In parallel to the instruction hold flag set by the CBF/LuxCSD customers (“Party hold”)  T2S provides hold information from the counterparty (“counterparty hold”) itself. Hence, the following values can be reported to CBF/LuxCSD customers:

  • “PREA” for Party hold;
  • “PRCY” for Counterparty hold.

Automated through T2S

On receipt of instructions


CBL releases pre-matching instructions (PREA) only outside the provisioning period to CBF for matching purposes only. As soon as the start of the provisioning period is reached and provided the provisioning of cash and securities is successful, the settlement instruction (NEWM) will be released to CBF for further processing and settlement in T2S. Once the instruction is released to CBF, it cannot be set back on hold again.

Automated through T2S

On receipt of instructions

Local pre-matching, which is market practice for instructions starts, subject to counterparty availability, on receipt of instructions and continues until Settlement Date (SD).

Partial release (CBF and LuxCSD)

The table below summarises the CBF and LuxCSD T2S Partial Release service for external settlement instructions. This T2S functionality enables the partial release of the quantity specified in a pending securities settlement instruction and can be initiated with the “Hold / Release functionality” by specifying the quantity to be released. A partial release request can also be cancelled.

Service offered

Method employed

(local time)

All securities

CBF and LuxCSD

T2S will execute the request within all defined Partial Settlement windows during the day and the night-time processing.


Partial Release via “Teilfreigabe” and transaction KVAS (Auftragsabwicklung – Settlement Dienst) for the release of an instruction (function code “FA” + “T” (stands for Teilfreigabe)).


The Partial Release request can be instructed via MT530 (:22F::SETT//YPRE + :36B: in sequence C with the security quantity) using Xact via SWIFT or Xact File Transfer.

Xact Web Portal

To create a Partial Release, the option “Creation Partial Release” accessible via list view and detailed view in Xact Settlement screen on existing “On Hold” instructions should be used.

Automated through T2S

On receipt of the delivery instructions in an “On Hold” status.


Not available

Automated through T2S

On receipt of the delivery instructions in an “On Hold” status.

Matching service

Matching is mandatory for all transactions settling in T2S. In addition to the mandatory matching criteria in T2S the following fields, if present, may be matching criteria.

Additional matching field

The following additional matching fields are initially not mandatory but when one of the counterparties provides a value for them in its instruction, matching values must be provided by the other counterparty.

  • Opt-out indicator;
  • CUM/EX indicator (not available in BOGS and must not be used by customers with counterparties that are ICPs and access T2S via BOGS).

Optional matching field

The following optional matching fields must match when provided by both counterparties:

  • Common reference;
  • Client of delivering/receiving CSD participant;
  • Securities account of the delivering/receiving CSD participant.

Note: Clearstream recommends to agree on the usage of a common reference (:20C::COMM) and the T2S Security Account number (SAC) with the counterparty in BOGS. Both fields are “optional” matching criteria in T2S and avoid cross-matching if populated in the Settlement instructions of both parties.


T2S will send allegement messages depending on the information indicated in the counterparty’s instruction. The allegements will contain additional and optional matching criteria as described above. These can be used to correctly format instructions to ensure matching if the matching instrucion has not yet been sent to Clearstream Banking or LuxCSD.

All securities


When the counterparty of the CBF customer instructs first, an allegement instruction will be generated by T2S. T2S will send the allegement message (sese.028) to CBF or to the DCP, without prior validation whether the ISIN is eligible in the counterparty CSD, which in this case is CBF.

Receipt domestic instructions are automatically generated, if the passive matching flag is set on the receiving main account or sub-account. In addition, the generation follows the rules below:

  • For domestic transactions, if the delivering party is an ICP or DCP customer and the recipient is a passive matching participant (ICP/DCP), CBF generates the receipt instruction based on the delivery instruction sent to CBF (ICP) or based on the copy of the DCP instruction (sese.023) received from T2S;
  • For cross-border transactions where the deliverer is a foreign CSD customer and the recipient is a CBF customer (ICP/DCP), the receipt instruction is generated based on the allegement received from T2S;
  • Allegements are not generated for “Already matched” instructions.


CBL may receive counterparty instructions alleged to its account at CBF and will report them to customers, provided that the customer’s CBL account is present in the allegement and the customer has subscribed to allegement messages.


If a counterparty's settlement instruction does not match after the first matching attempt, the customer is informed through an allegement message after a predefined period of time (T2S standard service).

Identification of CSDs in T2S

In T2S, all CSDs will be identified by their BIC11. CBL, CBF and LuxCSD customers are required to use the following BIC11 as Place of Settlement for domestic instructions with counterparties in BOGS:



Bank of Greece System


Identification of the counterparty in T2S

In T2S, CSD participants are identified exclusively by the combination of their Home CSD (for example, PSET DAKVDEFFXXX) and their BIC11.

Counterparty identification


4712000a (counterparty CSD account in CBF) or alternatively BNGRGRAASSS (BIC11 of the counterparty CSD)b and the T2S Party BIC11 of the CSD participant.

The counterparty CSD BIC is used by CBF to address the CSD where the counterparty is set up as T2S Party. This counterparty's CSD is reflected in CASCADE with a counterparty CSD account. The counterparty CSD BIC must be used in cross-border instructions with T2S In-CSDs. 


Home CSD BIC11 and the T2S Party BIC11 of the CSD participant.

When a CBL customer uses a BIC8 to identify the Receiving/Delivering Agent, CBL shall be entitled to modify the BIC8 provided and the settlement instructions will be then processed by default with a BIC11 by adding the default XXX suffix to comply with T2S settlement rules. Accordingly, such customers remain liable for any settlement fails that the use of the BIC8 may cause and the customers furthermore agree to indemnify CBL against losses, liabilities, damages, penalties, expenses and all other costs on any kind suffered by CBL as a result of the customer not complying with the above requirement.


Home CSD BIC11 and the T2S Party BIC11 of the CSD participant.

a. The counterparty CSD account can only be used in the CBF Legacy connectivity.

b. BIC11 of other T2S IN-CSDs possible if the technical configuration in T2S is available.

Note: Cross-border settlement between CSDs in T2S is only possible, if the corresponding technical configuration in T2S for cross-border links has been established by the CSDs linked to each other.

Procedures for domestic counterparties 


CBL depository – CBF

Place of settlement


Delivering/Receiving Agent



Not to be instructed. If instructed, it must be the valid CBL SAC:
BOGS: DAKV7201105


BIC11 of the CBL customer.

a. Although the safekeeping account of Party 1 (REAG/DEAG) is an optional matching field in T2S, if  present on one instruction 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).


Place of settlement


Delivering/Receiving Agent

T2S Party BIC11 CBF participant.


Place of settlement


Delivering/Receiving Agent

T2S Party BIC11 LuxCSD participant.

Partial settlement

When counterparties access T2S as an ICP via BOGS the default set up will be No Partial Settlement (NPAR) but counterparties can still instruct partial settlement instructions (PART) and BOGS will send them to T2S. NPAR is mandatory for CCBM transactions in BOGS.

In T2S, partial settlement for eligible instructions is allowed at the last night-time settlement cycle in sequence ‘X’; and within the real-time settlement period:

  • At 08:00 CET, 10:00 CET, 12:00 CET, 14:00 CET and 15:30 CET.
  • 30 minutes prior to the against payment cut-off time (between 15:30 CET and 16:00 CET).

Within these windows, all transactions that are pending due to lack of securities and hold a positive partial settlement indicator are included in the partial settlement processing.

Whether partial settlement will be applied depends on the partial settlement indicator set within the instruction or on the customer account setup. A settlement Instruction will settle partially, if both Counterparties instruct with the Field :22F::PARQ.

Partial settlement applies only when full settlement is not possible due to lack of securities. T2S will perform partial settlement according to the available position after analysing the partial settlement indicator in the instruction. Settlement instructions are submitted for a full settlement attempt before being submitted for a partial settlement attempt, if permitted by instruction indicators or customer account setup.

Partial settlement is applicable to domestic and cross-border instructions and is not allowed for PFoD instructions. Additionally, partial settlement is not applied if instructions are linked to any other settlement instruction with link type “Before”, “After”, “With” or via pool reference. Partial settlement is not applied if the transaction undergoes a process where a CoSD Hold is used. The unsettled remaining part of a partially settled settlement instruction can be cancelled.


CBF customers can define within the instruction whether partial settlement is to be applied by setting a partial settlement indicator. In addition, they can set a flag on account level (CBF 7-digit account number) that defines the default value to be set to those instructions where the partial settlement indicator is not filled. The flag is maintained within CBF’s static account database and defines which partial settlement indicator is to be assigned to an instruction as default value (NPAR, PART). The flag applies to delivery and receipt instructions.


As customer delivery instructions are always fully provisioned before being sent to the domestic market, no partial settlement can be performed. For receipts, the partial settlement can take place if the counterparty is short of securities and the instructions are received by T2S within the times set above.

When CBL customers access T2S via CBF, the default set up will be Partial Settlement. Customers that do not wish their transactions to settle partially must provide the No Partial Settlement indicator (NPAR) in their instruction.


LuxCSD customers can define within the instruction whether partial settlement is to be applied or not by setting a partial settlement indicator.

Allowed countervalue difference

The following T2S cash tolerances will apply to instructions (against payment instructions in EUR only):

  • EUR 2 for transactions with an amount equal to or less than EUR 100,000; and
  • EUR 25 for transactions with an amount greater than EUR 100,000.

In the event of a discrepancy within the limits, the cash amount of the delivering party will prevail.

For non-EUR currencies, the T2S cash tolerances apply to against payment instructions in foreign currencies between CBL and CBF participants (not applicable to LuxCSD).

Bridge settlement (CBL only)

CBL customers can settle BOGS T2S- eligible securities via the Bridge. This service is not available for CBF and LuxCSD customers.

Back-to-back processing (Transaction Linking)

Back-to-back processing is available for transactions in BOGS T2S eligible securities.


Unmatched instructions can be cancelled unilaterally, at any time, by the party who placed the instruction or until cancelled by T2S.

Matched instructions must be cancelled by both counterparties.

Recycling rules

Unmatched instructions will be recycled for 20 business days (starting from the initial settlement date), after which they will be cancelled.

Unmatched cancellation requests will be recycled for 20 business days (starting from the date of receipt).

Matched, but not settled instructions will be cancelled by T2S after 60 business days (starting from the date of receipt or on the day the last modification was sent for the instruction).


In accordance with BOGS rules, matched instructions that are not settled by the seventh business day after the intended SD at the latest will be subject to a forced tender initiated by the Bank of Greece. The forced tender is conducted by the Bank of Greece through a buy/sell back trade in HDAT. Should the forced tender be unsuccessful, the Bank of Greece initiates a buy-in.

Customers are requested to ensure timely provisioning and release of their instructions (for example, instructions with status "on hold"). Any costs and charges incurred by CBF, CBL or LuxCSD as a result of the forced tender and buy/sell back trade or buy-in will be charged to the instructing customer.

Buy-in process

If after the forced tender not all short positions have been covered, BOGS will invite directly all participants to cover them (buy-in). The process is executed in accordance with BOGS Operating Regulation.

Upon successful buy-in, BOGS will inform Clearstream as failing participant of the results of the buy-in. 

Clearstream will be required to input matching instruction in order to match the buy-in transaction. These instructions will be input and executed directly from failing customers’ accounts. Customers must ensure that their cash account is provisioned with sufficient cash balance to settle the buy-in in order to avoid cash penalties resulting from Settlement Discipline Regime which would be applied to failing instruction.

Settlement Discipline Regime cash penalties

Penalties will be calculated and applied on matched settlement instructions that fail to settle, in full or in part, on and after their intended settlement date (ISD), if both the settlement instruction and the relevant financial instrument are subject to cash penalties.

Instruments subject to cash penalties

Any financial instrument listed in the Financial Instruments Reference Data System (FIRDS) database maintained by ESMA will be subject to cash penalties. However, cash penalties will not apply to shares listed in the Short Selling Regulation (SSR) exemption listed in the Short Selling Regulation (SSR) exemption list.

New issues settlement

Transactions in new issues are settled on the day on which the distribution occurs in the Greek Market. For confirmation times, please refer to Settlement times.