02007D0007 — FR — 21.11.2021 — 013.002

Ce texte constitue seulement un outil de documentation et n’a aucun effet juridique. Les institutions de l'Union déclinent toute responsabilité quant à son contenu. Les versions faisant foi des actes concernés, y compris leurs préambules, sont celles qui ont été publiées au Journal officiel de l’Union européenne et sont disponibles sur EUR-Lex. Ces textes officiels peuvent être consultés directement en cliquant sur les liens qui figurent dans ce document

►B DÉCISION DE LA BANQUE CENTRALE EUROPÉENNE du 24 juillet 2007 relative aux modalités de TARGET2-BCE (BCE/2007/7) (2007/601/CE) (JO L 237 du 8.9.2007, p. 71)

Modifiée par:





Rectifiée par:









▼B

DÉCISION DE LA BANQUE CENTRALE EUROPÉENNE

du 24 juillet 2007

relative aux modalités de TARGET2-BCE

(BCE/2007/7)

(2007/601/CE)







Article premier

Champ d'application

1. TARGET2-BCE pourra seulement: a) procéder au traitement des propres paiements de la BCE; b) procéder au traitement des paiements des clients de la BCE, et ▼M11 c) fournir des services de règlement à des entités gérant des systèmes exogènes, y compris des entités établies hors de l'EEE, à condition que ces entités soient soumises à la surveillance d'une autorité compétente, qu'elles respectent les exigences de surveillance relatives à la localisation des infrastructures offrant des services en euros, telles que modifiées périodiquement et publiées sur le site internet de la BCE ( 1 ), et que leur accès à TARGET2-BCE ait été approuvé par le conseil des gouverneurs.

▼M3

2. La BCE peut uniquement accepter comme clients des banques centrales et des organisations européennes et internationales, et en vertu d’une décision ad hoc du conseil des gouverneurs, les administrations centrales des États membres de l’Union européenne ou les organismes publics désignés par ces administrations centrales pour les représenter.

▼B

Article 2

Crédit intrajournalier

1. La BCE peut uniquement octroyer des crédits intrajournaliers à des clients qui sont des organisations européennes ou internationales sous forme de découverts sur le(s) compte(s) de ces clients. Les découverts ne dépassent, à aucun moment de la journée, le montant déterminé dans l'accord passé avec le client pour chacun des comptes. Un crédit intrajournalier accordé par la BCE reste limité à la journée en question sans pouvoir être prolongé pour devenir un crédit à vingt-quatre heures.

▼M11

2. Tout octroi de crédit intrajournalier par la BCE respecte les règles sur l'octroi de crédit intrajournalier exposées à l'annexe III de l'orientation BCE/2012/27 ( 2 ).

Article 3

Modalités de TARGET2-BCE

Les modalités d'ouverture et de fonctionnement d'un compte MP dans TARGET2-BCE sont exposées à l'annexe I de la présente décision. Les modalités d'ouverture et de fonctionnement d'un compte espèces dédié T2S (DCA T2S) dans TARGET2-BCE sont exposées à l'annexe II de la présente décision. Les modalités d'ouverture et de fonctionnement d'un compte espèces dédié TIPS (DCA TIPS) dans TARGET2-BCE sont exposées à l'annexe III de la présente décision.

▼M10

Article 3 bis

Rémunération des fonds de garantie

1. On entend par «fonds de garantie», des fonds fournis par des participants à un système exogène, qui sont utilisés dans le cas où, pour un motif quelconque, un ou plusieurs participants n'honorent pas leurs obligations de paiement dans le système exogène.

2. Les fonds de garantie sont rémunérés au taux de la facilité de dépôt.

▼B

Article 4

Entrée en vigueur

1. La présente décision entre en vigueur le 19 mai 2008.

2. La décision BCE/1999/NP3 du 16 mars 1999 concernant le mécanisme de paiement de la Banque centrale européenne et la décision BCE/2003/NP2 du 28 janvier 2003 modifiant la décision BCE/1999/NP3 concernant le mécanisme de paiement de la Banque centrale européenne sont abrogées à compter de la date d'entrée en vigueur de la présente décision et les références aux décisions BCE/1999/NP3 et BCE/2003/NP2 s'entendent comme faites à la présente décision.









▼M8

ANNEX I

TERMS AND CONDITIONS FOR THE OPENING AND OPERATION OF A PM ACCOUNT IN TARGET2-ECB

▼B

TITLE I

GENERAL PROVISIONS

Article 1

Definitions

For the purposes of these Terms and Conditions (hereinafter the ‘Conditions’), the following definitions apply:

▼M4

— ►M11 ◄ ‘addressable BIC holder’ means an entity which: (a) holds a Business Identifier Code (BIC); (b) is not recognised as an indirect participant in the PM; and (c) is a correspondent or customer of a PM account holder or a branch of a direct or indirect participant in the PM, and is able to submit payment orders to and receive payments from a TARGET2 component system via the PM account holder,

▼M2

— ►M11 ◄ ‘ancillary system’ means a system managed by an entity that is subject to supervision and/or oversight by a competent authority and complies with the oversight requirements for the location of infrastructures offering services in euro, as amended from time to time and published on the ECB's website ( 3 ), in which payments and/or financial instruments are exchanged and/or cleared or recorded with (a) the monetary obligations settled in TARGET2 and/or (b) funds held in TARGET2, in accordance with Guideline ECB/2012/27 ( 4 ) and a bilateral arrangement between the ancillary system and the relevant Eurosystem CB,

▼B

— ‘ancillary system central bank (ASCB)’ means the Eurosystem CB with which the relevant AS has a bilateral arrangement for the settlement of AS payment instructions in the PM,

— ‘Ancillary System Interface (ASI)’ means the technical device allowing an AS to use a range of special, predefined services for the submission and settlement of AS payment instructions,

▼M8

— ►M11 ◄ ‘available liquidity’ means a credit balance on a participant's PM account and, if applicable, any intraday credit line granted by the relevant euro area NCB in relation to such account but not yet drawn upon, or, if applicable, decreased by the amount of any processed reservations of liquidity on the PM account,

▼M2 —————

▼M4

— ‘Business Identifier Code (BIC)’ means a code as defined by ISO Standard No 9362,

▼M8

— ‘branch’ means a branch within the meaning of point (17) of Article 4(1) of Regulation (EU) No 575/2013 of the European Parliament and of the Council ( 5 ),

▼B

— ►M11 ◄ ‘business day’ or ‘TARGET2 business day’ means any day on which TARGET2 is open for the settlement of payment orders, as set out in Appendix V,

— ‘capacity opinion’ means a participant-specific opinion that contains an assessment of a participant's legal capacity to enter into and carry out its obligations under these Conditions,

— ‘central banks (CBs)’ means the Eurosystem CBs and the connected CBs,

— ‘connected CB’ means a national central bank (NCB), other than a Eurosystem CB, which is connected to TARGET2 pursuant to a specific agreement,

▼M12 —————

▼M12

— ‘Contingency Solution’ means the SSP functionality that processes very critical and critical payments in contingency,

▼M8

— ‘credit institution’ means either: (a) a credit institution within the meaning of point (1) of Article 4(1) of Regulation (EU) No 575/2013 and Section 2(1) no 2 and Section 2(6) no 2 of the (Kreditwesengesetz) KWG, that is subject to supervision by a competent authority; or (b) another credit institution within the meaning of Article 123(2) of the Treaty that is subject to scrutiny of a standard comparable to supervision by a competent authority,

▼B

— ‘credit instruction’ means a payment instruction submitted by an AS and addressed to the ASCB to debit one of the accounts kept and/or managed by the AS in the PM, and to credit a settlement bank's PM account or sub-account by the amount specified therein,

— ‘credit transfer order’ means an instruction by a payer to make funds available to a payee by means of a book entry on a PM account,

— ‘debit instruction’ means a payment instruction addressed to the SCB and submitted by an AS to debit a settlement bank's PM account or sub-account by the amount specified therein, on the basis of a debit mandate, and to credit either one of the AS's accounts in the PM or another settlement bank's PM account or sub-account,

▼M9

— ‘direct debit authorisation’ means a general instruction by a payer to its CB entitling and obliging that CB to debit the payer's account upon receipt of a valid direct debit instruction from a payee,

▼B

— ‘direct debit instruction’ means an instruction from a payee submitted to its CB pursuant to which the CB of the payer debits the payer's account by the amount specified in the instruction, on the basis of a direct debit authorization,

— ‘debit mandate’ means an authorisation by a settlement bank in the form provided by the Eurosystem CBs in the static data forms addressed to both its AS and its SCB, entitling the AS to submit debit instructions, and instructing the SCB to debit the settlement bank's PM account or sub-account as a result of debit instructions,

▼M7

— ‘deposit facility’ means a Eurosystem standing facility which counterparties may use to make overnight deposits with an NCB at a pre-specified deposit rate,

— ‘deposit facility rate’ means the interest rate applicable to the deposit facility,

▼M8

— ►M11 ◄ ‘T2S Dedicated Cash Account (T2S DCA)’ means an account held by a T2S DCA holder, opened in TARGET2-ECB, and used for cash payments in relation to securities settlement in T2S,

▼B

— ‘entry disposition’ means a payment processing phase during which TARGET2-ECB attempts to settle a payment order which has been accepted pursuant to Article 12, by means of specific procedures, as described in Article 18,

▼M6

— ‘euro area NCB’ means the national central bank (NCB) of a Member State whose currency is the euro,

▼M6

— ‘Eurosystem CB’ means the ECB or a euro area NCB,

▼M8

— ‘event of default’ means any impending or existing event, the occurrence of which may threaten the performance by a participant of its obligations under these Conditions or any other rules applying to the relationship between that participant and the ECB or any other CB, including: ▼M11 (a) where the participant no longer meets the access criteria laid down in Article 4 or the requirements laid down in Article 6(1)(a); ▼M8 (b) the opening of insolvency proceedings in relation to the participant; (c) the submission of an application relating to the proceedings referred to in point (b); (d) the issue by the participant of a written declaration of its inability to pay all or any part of its debts or to meet its obligations arising in relation to intraday credit; (e) the entry of the participant into a voluntary general agreement or arrangement with its creditors; (f) where the participant is, or is deemed by its CB to be, insolvent or unable to pay its debts; ▼M11 (g) where the participant's credit balance on its PM account, T2S DCA or TIPS DCA, or all or a substantial part of the participant's assets are subject to a freezing order, attachment, seizure or any other procedure that is intended to protect the public interest or the rights of the participant's creditors; ▼M8 (h) where participation of the participant in another TARGET2 component system and/or in an ancillary system has been suspended or terminated; (i) where any material representation or pre-contractual statement made by the participant or which is implied to have been made by the participant under the applicable law is incorrect or untrue; (j) the assignment of all or a substantial part of the participant's assets,

▼M12

— ‘Information and Control Module (ICM)’ means the SSP module that allows PM account holders to obtain online information and gives them the possibility to submit liquidity transfer orders, manage liquidity and, if applicable, initiate backup payment orders or payment orders to the Contingency Solution in a contingency,

▼B

— ►M11 ◄ ‘ICM broadcast message’ means information made simultaneously available to all or a selected group of PM account holders via the ICM,

— ►M11 ◄ ‘indirect participant’ means a credit institution established in the European Union or the European Economic Area (EEA), which has entered into an agreement with a PM account holder to submit payment orders and receive payments via such PM account holder's PM account, and which has been recognised by a TARGET2 component system as an indirect participant,

— ‘insolvency proceedings’ means insolvency proceedings within the meaning of Article 2(j) of the Settlement Finality Directive,

▼M13

— ‘instant payment order’ means, in line with the European Payments Council's SEPA Instant Credit Transfer (SCT Inst) scheme, a payment instruction which can be executed 24 hours a day any calendar day of the year, with immediate or close to immediate processing and notification to the payer and includes (a) the TIPS DCA to TIPS DCA instant payment orders, (b) TIPS DCA to TIPS AS technical account instant payment orders, (c) TIPS AS technical account to TIPS DCA instant payment orders and (d) TIPS AS technical account to TIPS AS technical account instant payment orders,

▼B

— ‘instructing participant’ means a TARGET2 participant that has initiated a payment order,

— ‘intraday credit’ means credit extended for a period of less than one business day,

▼M11

— ‘Linked PM account’ means the PM account with which a TIPS DCA is associated for the purpose of liquidity management and payment of TIPS fees,

▼B

— ‘liquidity transfer order’ means a payment order, the main purpose of which is to transfer liquidity between different accounts of the same participant,

— ‘marginal lending facility’ means a Eurosystem standing facility which counterparties may use to receive overnight credit from a Eurosystem CB at the pre-specified marginal lending rate,

— ‘marginal lending rate’ means the interest rate applicable to the marginal lending facility,

— ►M11 ◄ can access the relevant TARGET2 component system by submitting payment orders and/or receiving payments directly to and from the TARGET2 component system; this facility authorises these entities to submit their payment orders through the direct participant's PM account without that participant's involvement, ‘multi-addressee access’ means the facility by which branches or credit institutionsestablished in the Union or the EEAcan access the relevant TARGET2 component system by submitting payment orders and/or receiving payments directly to and from the TARGET2 component system; this facility authorises these entities to submit their payment orders through the direct participant's PM account without that participant's involvement,

▼M8

— ►M11 ◄ is linked and on which any remaining balance must be automatically repatriated from the ►M11 ◄ at the end of the day, ‘Main PM account’ means the PM account to which aT2S DCAis linked and on which any remaining balance must be automatically repatriated from theT2S DCAat the end of the day,

▼B

— ►M11 ◄ ’ means the undertaking appointed by the ECB's Governing Council to provide computerised network connections for the purpose of submitting payment messages in TARGET2, TARGET2 network service provider’ means the undertaking appointed by the ECB's Governing Council to provide computerised network connections for the purpose of submitting payment messages in TARGET2,

— ►M11 ◄ ‘non-settled payment order’ means a payment order that is not settled on the same-business day as that on which it is accepted,

▼M8

— ►M11 ◄ ‘participant’ [or ‘direct participant’] means an entity that holds at least one PM account (PM account holder) and/or one T2S Dedicated Cash Account (T2S DCA holder) and/or one TIPS Dedicated Cash Account (TIPS DCA holder) with a Eurosystem CB,

▼B

— ‘Participant Interface (PI)’ means the technical device allowing direct participants to submit and settle payment orders via the services offered in the PM,

▼M5

— ‘payee’, except where used in Article 33, means a TARGET2 participant whose PM account will be credited as a result of a payment order being settled,

— ‘payer’, except where used in Article 33, means a TARGET2 participant whose PM account will be debited as a result of a payment order being settled,

▼B

— ‘payment instruction’ or ‘AS payment instruction’ means a credit instruction or a debit instruction,

▼M8

— ►M11 ◄ ‘payment order’ means a credit transfer order, a liquidity transfer order, a direct debit instruction, a PM to T2S DCA liquidity transfer order or a PM to TIPS DCA liquidity transfer order,

▼B

— ‘Payments Module (PM)’ means an SSP module in which payments of TARGET2 participants are settled on PM accounts,

— ‘PM account’ means an account held by a TARGET2 participant in the PM with a CB which is necessary for such TARGET2 participant to: (a) submit payment orders or receive payments via TARGET2; and (b) settle such payments with such CB,

▼M11

— ‘positive recall answer’ means, in line with the SCT Inst scheme, a payment order initiated by the receiver of a recall request, in response to a recall request, for the benefit of the sender of that recall request,

▼M4

— ‘public sector body’ means an entity within the ‘public sector’, the latter term as defined in Article 3 of Council Regulation (EC) No 3603/93 of 13 December 1993 specifying definitions for the application of the prohibitions referred to in Articles 104 and 104b(1) of the Treaty ( 6 ),

▼M11

— ‘PM to TIPS DCA liquidity transfer order’ means the instruction to transfer a specified amount of funds from a PM account to a TIPS DCA,

▼M8

— ►M11 ◄ ‘PM to T2S DCA liquidity transfer order’ means the instruction to transfer a specified amount of funds from a PM account to a T2S DCA,

▼M11

— ‘recall request’ means, in line with the SCT Inst scheme, a message from a TIPS DCA holder requesting reimbursement of a settled instant payment order,

▼B

— ‘settlement bank’ means a participant whose PM account or sub-account is used to settle AS payment instructions,

— ‘settlement central bank (SCB)’ means a Eurosystem CB holding a settlement bank's PM account,

— ‘Settlement Finality Directive’ means Directive 98/26/EC of the European Parliament and of the Council of 19 May 1998 on settlement finality in payment and securities settlement systems ( 7 );

— ►M11 ◄ , ‘Single Shared Platform (SSP)’ means the single technical platform infrastructure provided by theSSP-providing NCBs

— ►M11 ◄ ’ means the Deutsche Bundesbank, the Banque de France and the Banca d'Italia in their capacity as the CBs building and operating the SSP for the Eurosystem's benefit, SSP-providing NCBs’ means the Deutsche Bundesbank, the Banque de France and the Banca d'Italia in their capacity as the CBs building and operating the SSP for the Eurosystem's benefit,

— ‘static data collection form’ means a form developed by the ECB for the purpose of registering applicants for TARGET2-ECB services and registering any changes in relation to the provision of such services,

— ‘suspension’ means the temporary freezing of the rights and obligations of a participant for a period of time to be determined by the ECB,

▼M11

— ‘TARGET Instant Payment Settlement (TIPS) service’ means the settlement in central bank money of instant payment orders on the TIPS Platform,

▼B

— ‘TARGET2-ECB’ means the TARGET2 component system of the ECB,

— ‘TARGET2’ means the entirety resulting from all TARGET2 component systems of the CBs,

— ‘TARGET2 component system’ means any of the CBs' real-time gross settlement (RTGS) systems that form part of TARGET2,

— ►M11 ◄ customers grouped for the purpose of their use of the relevant services and products of the ►M11 ◄ when accessing the PM, ‘TARGET2 CUG’ means a subset of theTARGET2 network service provider'scustomers grouped for the purpose of their use of the relevant services and products of theTARGET2 network service providerwhen accessing the PM,

— ‘TARGET2 participant’ means any participant in any TARGET2 component system,

▼M11

— ‘TARGET2-Securities (T2S)’ or ‘T2S Platform’ means the set of hardware, software and other technical infrastructure components through which the Eurosystem provides the services to CSDs and Eurosystem CBs that allow core, neutral and borderless settlement of securities transactions on a delivery-versus-payment basis in central bank money,

▼M2

— ►M11 ◄ in TARGET2-ECB, ‘technical malfunction of TARGET2’ means any difficulty, defect or failure in the technical infrastructure and/or the computer systems used by TARGET2-ECB, or any other event that makes it impossible to execute and complete thesame business-day processing of paymentsin TARGET2-ECB,

▼M11

— ‘TIPS Dedicated Cash Account (TIPS DCA)’ means an account held by a TIPS DCA holder, opened in TARGET2-ECB, and used for the provision of instant payment services to its customers,

— ‘TIPS DCA to PM liquidity transfer order’ means the instruction to transfer a specified amount of funds from a TIPS DCA to a PM account,

▼M13 —————

▼M11

— ‘TIPS Platform’ means the single technical platform infrastructure provided by the TIPS Platform-providing NCBs,

— ‘TIPS Platform-providing NCBs’ means the Deutsche Bundesbank, the Banco de España, the Banque de France and the Banca d'Italia in their capacity as the CBs building and operating the TIPS Platform for the Eurosystem's benefit,

▼M4

— ‘User Detailed Functional Specifications (UDFS)’ means the most up-to-date version of the UDFS, which is the technical documentation that details how a participant interacts with TARGET2,

▼M13

— ‘European Payments Council's SEPA Instant Credit Transfer (SCT Inst) scheme’ or ‘SCT Inst scheme’ means an automated, open standards scheme providing a set of interbank rules to be complied with by SCT Inst participants, allowing payment services providers in SEPA to offer an automated, SEPA-wide euro instant credit transfer product,

— ‘TIPS ancillary system technical account (TIPS AS technical account)’ means an account held by an ancillary system or a CB on an ancillary system's behalf in the CB’s TARGET2 component system for use by the ancillary system for the purpose of settling instant payments in its own books,

— ‘TIPS DCA to TIPS AS technical account liquidity transfer order’ means the instruction to transfer a specified amount of funds from a TIPS DCA to a TIPS AS technical account to fund the TIPS DCA holder’s position (or the position of another participant of the ancillary system) in the books of the ancillary system,

— ‘TIPS AS technical account to TIPS DCA liquidity transfer order’ means the instruction to transfer a specified amount of funds from a TIPS AS technical account to a TIPS DCA to defund the TIPS DCA holder’s position (or the position of another participant of the ancillary system) in the books of the ancillary system,

— ‘reachable party’ means an entity which: (a) holds a BIC; (b) is designated as a reachable party by a TIPS DCA holder or by an ancillary system; (c) is a correspondent, customer or branch of a TIPS DCA holder or a participant of an ancillary system, or a correspondent, customer, or branch of a participant of an ancillary system; and (d) is addressable through the TIPS Platform and is able to submit instant payment orders and receive instant payment orders either via the TIPS DCA holder or the ancillary system or, if so authorised by the TIPS DCA holder or by the ancillary system, directly.

▼M8

Article 1a

Scope

The present Conditions govern the relationship between the ECB and its PM account holder as far the opening and the operation of the PM account is concerned.

▼B

Article 2

Appendices

1. The following Appendices form an integral part of these Conditions: Appendix I : Technical specifications for the processing of payment orders Appendix II : TARGET2 compensation scheme Appendix III : Terms of reference for capacity and country opinions Appendix IV : Business continuity and contingency procedures Appendix V : Operating schedule Appendix VI : Fee schedule and invoicing ▼M13 Appendix VII : Requirements regarding information security management and business continuity management ▼B

2. In the event of any conflict or inconsistency between the content of any appendix and the content of any other provision in these Conditions, the latter shall prevail.

▼M11

Article 3

General description of TARGET2

1. TARGET2 provides real-time gross settlement for payments in euro, with settlement in central bank money across PM accounts, T2S DCAs for the purpose of securities transactions and TIPS DCAs for the purpose of instant payments.

2. The following transactions are processed in TARGET2-ECB: (a) transactions directly resulting from or made in connection with Eurosystem monetary policy operations; (b) settlement of the euro leg of foreign exchange operations involving the Eurosystem; (c) settlement of euro transfers resulting from transactions in cross-border large-value netting systems; (d) settlement of euro transfers resulting from transactions in euro retail payment systems of systemic importance; (e) settlement of the cash leg of securities transactions; (f) T2S DCA to T2S DCA liquidity transfer orders, T2S DCA to PM liquidity transfer orders and PM to T2S DCA liquidity transfer orders; (fa) instant payment orders; (fb) positive recall answers; ▼M13 (fc) TIPS DCA to PM liquidity transfer orders and PM to TIPS DCA liquidity transfer orders; ▼M13 (fd) TIPS DCA to TIPS AS technical account liquidity transfer orders and TIPS AS technical account to TIPS DCA liquidity transfer orders; and ▼M11 (g) any other transactions in euro addressed to TARGET2 participants.

▼M13

3. TARGET2 provides real-time gross settlement for payments in euro, with settlement in central bank money across PM accounts, T2S DCAs and TIPS DCAs. TARGET2 is established and functions on the basis of the SSP through which payment orders are submitted and processed and through which payments are ultimately received in the same technical manner. As far as the technical operation of the T2S DCAs is concerned, TARGET2 is technically established and functions on the basis of the T2S Platform. As far as the technical operation of the TIPS DCAs and TIPS AS technical accounts is concerned, TARGET2 is technically established and functions on the basis of the TIPS Platform.

▼M11

4. The ECB is the provider of services under these Conditions. Acts and omissions of the SSP-providing NCBs shall be considered acts and omissions of the ECB, for which it shall assume liability in accordance with Article 25 below. Participation pursuant to these Conditions shall not create a contractual relationship between PM account holders and the SSP-providing NCBs when any of the latter acts in that capacity. Instructions, messages or information which a PM account holder receives from, or sends to, the SSP in relation to the services provided under these Conditions are deemed to be received from, or sent to, the ECB.

5. TARGET2 is legally structured as a multiplicity of payment systems composed of all the TARGET2 component systems, which are designated as ‘systems’ under the national laws implementing the Settlement Finality Directive. TARGET2-ECB is designated as a ‘system’ under § 1(16) of the KWG.

6. Participation in TARGET2 takes effect via participation in a TARGET2 component system. These Conditions describe the mutual rights and obligations of PM account holders in TARGET2-ECB and the ECB. The rules on the processing of payment orders under these Conditions (Title IV and Appendix I) refer to all payment orders submitted or payments received by any PM account holder.

7. No intraday credit is provided to participants in TARGET2-ECB.

▼B







TITLE II

PARTICIPATION

▼M2

Article 4

Access criteria

Entities managing ancillary systems (including entities established outside the EEA) and acting in that capacity, whose access to TARGET2-ECB has been approved by the Governing Council, shall be the only entities that are eligible for participation in TARGET2-ECB.

▼M13

Article 5

Participants directs

PM account holders in TARGET2-ECB are direct participants and shall comply with the requirements set out in Article 8(1) and (2). They shall have at least one PM account with the ECB. PM account holders that have adhered to the SCT Inst scheme by signing the SEPA Instant Credit Transfer Adherence Agreement shall be and shall remain reachable in the TIPS Platform at all times, either as a TIPS DCA holder or as a reachable party via a TIPS DCA holder.

▼B

Article 6

Application procedure

1. To join TARGET2-ECB, applicant participants shall fulfil the following technical and legal requirements: (a) install, manage, operate and monitor and ensure the security of the necessary IT infrastructure to connect to ►M11 the SSP ◄ and submit payment orders to it. In doing so, applicant participants may involve third parties, but retain sole liability. In particular, applicant participants shall enter into an agreement with the ►M11 TARGET2 network service provider ◄ to obtain the necessary connection and admissions, in accordance with the technical specifications in Appendix I; (b) have passed the tests required by the ECB; (c) provide a capacity opinion in the form specified in Appendix III, unless the information and representations to be provided in such capacity opinion have already been obtained by the ECB in another context; and (d) for entities established outside the EEA, provide a country opinion in the form specified in Appendix III, unless the information and representations to be provided in such country opinion have already been obtained by the ECB in another context.

2. Applicants shall apply in writing to the ECB, as a minimum enclosing the following documents/information: (a) completed static data collection forms as provided by the ECB, (b) the capacity opinion, if required by the ECB, and (c) the country opinion, if required by the ECB.

3. The ECB may also request any additional information it deems necessary to decide on the application to participate.

4. The ECB shall reject the application to participate if: (a) access criteria referred to in Article 4 are not met; (b) one or more of the participation criteria referred to in paragraph 1 are not met; and/or ▼M5 (c) in the ECB’s assessment, such participation would endanger the overall stability, soundness and safety of TARGET2-ECB or of any other TARGET2 component system, would jeopardise the ECB’s performance of its tasks as described in the Statute of the European System of Central Banks and of the European Central Bank, or poses risks on the grounds of prudence. ▼B

5. The ECB shall communicate its decision on the application to participate to the applicant within one month of the ECB's receipt of the application to participate. Where the ECB requests additional information pursuant to paragraph 3, the decision shall be communicated within one month of the ECB's receipt of this information from the applicant. Any rejection decision shall contain reasons for the rejection.

Article 7

TARGET2 directory

1. The TARGET2 directory is the database of BICs used for the routing of payment orders addressed to: (a) TARGET2 participants and their branches with multi-addressee access; (b) indirect participants of TARGET2, including those with multi-addressee access; and (c) addressable BIC holders of TARGET2. It shall be updated weekly.

▼M2

2. Unless otherwise requested by the participant, its BIC(s) shall be published in the TARGET2 directory.

▼B

3. Participants may only distribute the TARGET2 directory to their branches and entities with multi-addressee access.

4. Entities specified in paragraph 1(b) and (c) shall only use their BIC in relation to one direct participant.

▼M2

5. Participants acknowledge that the ECB and other CBs may publish participants’ names and BICs.

▼B







TITLE III

OBLIGATIONS OF THE PARTIES

Article 8

Obligations of the ECB and the participants

1. The ECB shall offer the services described in Title IV. Save where otherwise provided in these Conditions or required by law, the ECB shall use all reasonable means within its power to perform its obligations under these Conditions, without guaranteeing a result.

2. Participants shall pay to the ECB the fees laid down in Appendix VI.

3. Participants shall ensure that they are connected to TARGET2-ECB on business days, in accordance with the operating schedule in Appendix V.

4. The participant represents and warrants to the ECB that the performance of its obligations under these Conditions does not breach any law, regulation or by-law applicable to it or any agreement by which it is bound.

Article 9

Cooperation and information exchange

1. In performing their obligations and exercising their rights under these Conditions, the ECB and participants shall cooperate closely to ensure the stability, soundness and safety of TARGET2-ECB. They shall provide each other with any information or documents relevant for the performance of their respective obligations and the exercise of their respective rights under these Conditions, without prejudice to any banking secrecy obligations.

2. The ECB shall establish and maintain a system support desk to assist participants in relation to difficulties arising in connection with system operations.

3. ►M11 ◄ The T2IS may be used to obtain information on any event affecting the normal operation of TARGET2. Up-to-date information on the SSP's operational status shall be available on the TARGET2 Information System (T2IS) on a dedicated webpage on the ECB's website.The T2IS may be used to obtain information on any event affecting the normal operation of TARGET2.

4. The ECB may either communicate messages to participants by means of an ICM broadcast or by any other means of communication.

▼M11

4a. The holder of the Linked PM account shall be responsible for informing in a timely manner its TIPS DCA holders of any relevant ICM broadcast message, including those related to the suspension or termination of any TIPS DCA holder's participation in TARGET2-ECB.

▼B

5. Participants are responsible for the timely update of existing static data collection forms and the submission of new static data collection forms to the ECB. Participants are responsible for verifying the accuracy of information relating to them that is entered into TARGET2-ECB by the ECB.

6. ►M11 ◄ any information relating to participants which the ►M11 ◄ may need in their role as service administrators, in accordance with the contract entered into with the ►M11 ◄ . The ECB shall be deemed to be authorised to communicate to theSSP-providing NCBsany information relating to participants which theSSP-providing NCBsmay need in their role as service administrators, in accordance with the contract entered into with theTARGET2 network service provider

7. Participants shall inform the ECB about any change in their legal capacity and relevant legislative changes affecting issues covered by the country opinion relating to them.

▼M12

8. Participants shall immediately inform the ECB if an event of default occurs in relation to themselves or if they are subject to crisis prevention measures or crisis management measures within the meaning of Directive 2014/59/EU of the European Parliament and of the Council ( 8 ) or any other equivalent applicable legislation.

▼B







TITLE IV

MANAGEMENT OF PM ACCOUNTS AND PROCESSING OF PAYMENT ORDERS

Article 10

Opening and management of PM accounts

▼M2

1. The ECB shall open and operate at least one PM account for each participant. Upon request by a participant acting as a settlement bank, the ECB shall open one or more sub-accounts in TARGET2-ECB to be used for dedicating liquidity.

▼B

2. No debit balance shall be allowed on PM accounts.

▼M7

3. PM accounts and their sub-accounts shall be remunerated either at zero per cent or the deposit facility rate, whichever is lower.

▼B

4. Participants shall use the ICM to obtain information on their liquidity position. The ECB shall provide a daily statement of accounts to any participant that has opted for such service.

▼M11

5. A PM account holder accepting its PM account to be designated as the Main PM account shall be bound by any invoices related to the opening and operation of each T2S DCA linked to that PM account, as set out in Appendix VI to this Annex, including any penalties levied in accordance with paragraph 9(d) of Annex IIIa, regardless of the content of, or any non-compliance with, the contractual or other arrangements between that PM account holder and the T2S DCA holder.

▼M8

6. ►M11 ◄ to which the PM account is linked. A Main PM account holder shall be bound by any invoices, as set out in Appendix VI to this Annex, for the linkage to eachT2S DCAto which the PM account is linked.

▼M11

7. A PM account holder accepting its PM account to be designated as the Linked PM account shall be bound by any invoices related to the opening and operation of each TIPS DCA linked to that PM account, as set out in Appendix VI to this Annex, regardless of the content of, or any non-compliance with, the contractual or other arrangements between that PM account holder and the TIPS DCA holder. A Linked PM account may be linked to a maximum of 10 TIPS DCAs.

8. The holder of a Linked PM account shall have an overview of the liquidity available on the TIPS DCAs linked to that PM account and ensure the TIPS DCA holders are aware of their responsibility to manage that liquidity.

▼M8

Article 11

Types of payment orders

The following are classified as payment orders for the purposes of TARGET2:

(a) credit transfer orders;

(b) direct debit instructions carried out under a direct debit authorisation;

▼M11

(c) liquidity transfer orders;

(d) PM to T2S DCA liquidity transfer orders; and

▼M11

(e) PM to TIPS DCA liquidity transfer orders.

▼B

Article 12

Acceptance and rejection of payment orders

1. Payment orders submitted by participants are deemed accepted by the ECB if: (a) the payment message complies with the rules established by the ►M11 TARGET2 network service provider ◄ ; (b) the payment message complies with the formatting rules and conditions of TARGET2-ECB and passes the double-entry check described in Appendix I; and (c) in cases where a payer or a payee has been suspended, the suspended participant's CB's explicit consent has been obtained.

2. The ECB shall immediately reject any payment order that does not fulfil the conditions laid down in paragraph 1. The ECB shall inform the participant of any rejection of a payment order, as specified in Appendix I.

▼M11

3. The SSP attaches its timestamp for the processing of payment orders in the sequence of their receipt.

▼M2

Article 13

Priority rules

1. Instructing participants shall designate every payment order as one of the following: (a) normal payment order (priority class 2); (b) urgent payment order (priority class 1); or (c) highly urgent payment order (priority class 0).

If a payment order does not indicate the priority, it shall be treated as a normal payment order.

▼M11

2. Highly urgent payment orders may only be designated by: (a) CBs; and (b) participants, in cases of payments to and from CLS Bank International, with the exception of payments related to the CLS CCP service and, at the discretion of the Governing Council, the CLSNow service, and liquidity transfers in relation to ancillary system settlement using the ASI.

All payment instructions submitted by an ancillary system through the ASI to debit or credit the participants' PM accounts and all PM to T2S DCA liquidity transfer orders and PM to TIPS DCA liquidity transfer orders submitted shall be deemed to be highly urgent payment orders.

▼M2

3. Liquidity transfer orders initiated via the ICM are urgent payment orders.

4. In the case of urgent and normal payment orders, the payer may change the priority via the ICM with immediate effect. It shall not be possible to change the priority of a highly urgent payment order.

▼B

Article 14

Liquidity limits

1. A participant may limit the use of available liquidity for payment orders in relation to other TARGET2 participants, except any of the CBs, by setting bilateral or multilateral limits. Such limits may only be set in relation to normal payment orders.

2. By setting a bilateral limit, a participant instructs the ECB that an accepted payment order shall not be settled if the sum of its outgoing normal payment orders to another TARGET2 participant's PM account minus the sum of all incoming urgent and normal payments from such TARGET2 participant's PM account would exceed this bilateral limit.

3. A participant may set a multilateral limit for any relationship that is not subject to a bilateral limit. A multilateral limit may only be set if the participant has set at least one bilateral limit. If a participant sets a multilateral limit, it instructs the ECB that an accepted payment order shall not be settled if the sum of its outgoing normal payment orders to all TARGET2 participants' PM accounts in relation to which no bilateral limit has been set, minus the sum of all incoming urgent and normal payments from such PM accounts would exceed this multilateral limit.

4. The minimum amount of any of the limits shall be EUR 1 million. A bilateral or a multilateral limit with an amount of zero shall be treated as if no limit has been set. Limits between zero and EUR 1 million are not possible.

5. Limits may be changed in real time with immediate effect or with effect from the next business day via the ICM. If a limit is changed to zero, it shall not be possible to change it again on the same business day. The setting of a new bilateral or multilateral limit shall only be effective from the next business day.

Article 15

Liquidity reservation facilities

1. Participants may reserve liquidity for highly urgent or urgent payment orders via the ICM.

2. By requesting to reserve a certain amount of liquidity for highly urgent payment orders, a participant instructs the ECB only to settle urgent and normal payment orders if there is available liquidity after the amount reserved for highly urgent payment orders has been deducted.

3. By requesting to reserve a certain amount of liquidity for urgent payment orders, a participant instructs the ECB only to settle normal payment orders if there is available liquidity after the amount reserved for urgent and highly urgent payment orders has been deducted.

▼M2

4. After receipt of the reservation request the ECB shall check whether the amount of liquidity on the participant’s PM account is sufficient for the reservation. If this is not the case, only the liquidity available on the PM account shall be reserved. The rest of the requested liquidity shall be reserved if additional liquidity becomes available.

▼B

5. The level of the liquidity reservation may be changed. Participants may make a request via the ICM to reserve new amounts with immediate effect or with effect from the next business day.

▼M2

Article 15a

Standing instructions for liquidity reservation and dedication of liquidity

1. Participants may predefine the default amount of liquidity reserved for highly urgent or urgent payment orders via the ICM. Such standing instruction or a change to such instruction shall take effect from the next business day.

2. Participants may predefine via the ICM the default amount of liquidity set aside for ancillary system settlement. Such standing instruction or a change to such instruction shall take effect from the next business day. Participants shall be deemed to have instructed the ECB to dedicate liquidity on their behalf if the relevant ancillary system so requests.

▼B

Article 16

Predetermined settlement times

1. Instructing participants may predetermine the settlement time of the payment orders within a business day by using the Earliest Debit Time Indicator or the Latest Debit Time Indicator.

2. When the Earliest Debit Time Indicator is used, the accepted payment order is stored and only entered into the entry disposition at the indicated time.

3. When the Latest Debit Time Indicator is used, the accepted payment order shall be returned as non-settled if it cannot be settled by the indicated debit time. 15 minutes prior to the defined debit time, the instructing participant shall be sent an automatic notification via the ICM. Instructing participant may also use the Latest Debit Time Indicator solely as a warning indicator. In such cases, the payment order concerned shall not be returned.

4. Instructing participants can change the Earliest Debit Time Indicator and the Latest Debit Time Indicator via the ICM.

5. Further technical details are contained in Appendix I.

Article 17

Payment orders submitted in advance

1. Payment orders may be submitted up to five business days before the specified settlement date (warehoused payment orders).

2. Warehoused payment orders shall be accepted and entered into the entry disposition on the date specified by the instructing participant at the start of daytime processing, as referred to in Appendix V. They shall be placed in front of payment orders of the same priority.

3. Articles 13(3), 20(2) and 23(1)(a) shall apply mutatis mutandis to warehoused payment orders.

Article 18

Settlement of payment orders in the entry disposition

1. Unless instructing participants have indicated the settlement time in the manner described in Article 16, accepted payment orders shall be settled immediately or at the latest by the end of the business day on which they were accepted, provided that sufficient funds are available on the payer's PM account and taking into account any liquidity limits and liquidity reservations as referred to in Articles 14 and 15.

2. Funding may be provided by: (a) the available liquidity on the PM account; or (b) incoming payments from other TARGET2 participants, subject to the applicable optimisation procedures.

3. For highly urgent payment orders the ‘first in, first out’ (FIFO) principle shall apply. This means that highly urgent payment orders shall be settled in chronological order. Urgent and normal payment orders shall not be settled for as long as highly urgent payment orders are queued.

4. For urgent payment orders the FIFO principle shall also apply. Normal payment orders shall not be settled if urgent and highly urgent payment orders are queued.

5. By derogation from paragraphs 3 and 4, payment orders with a lower priority (or of the same priority but accepted later) may be settled before payment orders with a higher priority (or of the same priority which were accepted earlier), if the payment orders with a lower priority would net out with payments to be received and result on balance in a liquidity increase for the payer.

6. Normal payment orders shall be settled in accordance with the FIFO by-passing principle. This means that they may be settled immediately (independently of other queued normal payments accepted at an earlier time) and may therefore breach the FIFO principle, provided that sufficient funds are available.

7. Further details on the settlement of payment orders in the entry disposition are contained in Appendix I.

▼M2

Article 19

Settlement and return of queued payment orders

1. Payment orders that are not settled immediately in the entry disposition shall be placed in the queues in accordance with the priority to which they were designated by the relevant participant, as referred to in Article 13.

2. To optimise the settlement of queued payment orders, the ECB may use the optimisation procedures described in Appendix I.

3. Except for highly urgent payment orders, the payer may change the queue position of payment orders in a queue (i.e. reorder them) via the ICM. Payment orders may be moved either to the front or to the end of the respective queue with immediate effect at any time during daytime processing, as referred to in Appendix V.

4. At the request of a payer, the ECB may decide to change the queue position of a highly urgent payment order (except for highly urgent payment orders in the context of settlement procedures 5 and 6) provided that this change would not affect the smooth settlement by ancillary systems in TARGET2 or would not otherwise give rise to systemic risk.

5. Liquidity transfer orders initiated in the ICM shall be immediately returned as non-settled if there is insufficient liquidity. Other payment orders shall be returned as non-settled if they cannot be settled by the cut-off times for the relevant message type, as specified in Appendix V.

▼B

Article 20

Entry of payment orders into the system and their irrevocability

▼M6

1. For the purposes of the first sentence of Article 3(1) of the Settlement Finality Directive and the third sentence of § 116, § 96(2), § 82 and § 340(3) of the German Insolvency Code ( Insolvenzordnung ) and the last sentence of § 46(2) of the KWG, payment orders are deemed entered into TARGET2-ECB at the moment that the relevant participant’s PM account is debited.

▼B

2. Payment orders may be revoked until they are entered into TARGET2-ECB in accordance with paragraph 1. Payment orders that are included in an algorithm, as referred to in Appendix I, may not be revoked during the period that the algorithm is running.







TITLE V

SECURITY REQUIREMENTS AND CONTINGENCY ISSUES

▼M12

Article 21

Business continuity and contingency procedures

1. In the event of an abnormal external event or any other event which affects the operation of the SSP, the business continuity and contingency procedures described in Appendix IV shall apply.

2. The Eurosystem provides a Contingency Solution if the events described in paragraph 1 occur. Connection to and use of the Contingency Solution shall be mandatory for participants considered by the ECB to be critical. Other participants may, on request, connect to the Contingency Solution.

▼M13

Article 22

Security Requirements and Control Procedures

1. Participants shall implement adequate security controls to protect their systems from unauthorised access and use. Participants shall be exclusively responsible for the adequate protection of the confidentiality, integrity and availability of their systems.

2. Participants shall inform the ECB of any security-related incidents in their technical infrastructure and, where appropriate, security-related incidents that occur in the technical infrastructure of the third party providers. The ECB may request further information about the incident and, if necessary, request that the participant take appropriate measures to prevent a recurrence of such an event.

3. The ECB may impose additional security requirements, in particular with regard to cybersecurity or the prevention of fraud, on all participants and/or on participants that are considered critical by the ECB.

4. Participants shall provide the ECB with: (i) permanent access to their attestation of adherence to their chosen network service provider’s endpoint security requirements, and (ii) on an annual basis the TARGET2 self-certification statement as published on the ECB’s website in English.

4a. The ECB shall assess the participant’s self-certification statement(s) on the participants level of compliance with each of the requirements set out in the TARGET2 self-certification requirements. These requirements are listed in Appendix VII, which in addition to the other Appendices listed in Article 2(1), shall form an integral part of these Conditions.

4b. The participant’s level of compliance with the requirements of the TARGET2 self-certification shall be categorised as follows, in increasing order of severity: “full compliance”; “minor non-compliance”; or “major non-compliance”. The following criteria apply: full compliance is reached where participants satisfy 100% of the requirements; minor non-compliance is where a participant satisfies less than 100% but at least 66% of the requirements and major non-compliance where a participant satisfies less than 66% of the requirements. If a participant demonstrates that a specific requirement is not applicable to it, it shall be considered as compliant with the respective requirement for the purposes of the categorisation. A participant which fails to reach “full compliance” shall submit an action plan demonstrating how it intends to reach full compliance. The ECB shall inform the relevant supervisory authorities of the status of such participant’s compliance.

4c. If the participant refuses to grant permanent access to its attestation of adherence to their chosen NSPs endpoint security requirements or does not provide the TARGET2 self-certification the participant’s level of compliance shall be categorised as “major non-compliance”.

4d. The ECB shall reassess compliance of participants on an annual basis.

4e. The ECB may impose the following measures of redress on participants whose level of compliance was assessed as minor or major non-compliance, in increasing order of severity: (i) enhanced monitoring: the participant shall provide the ECB with a monthly report, signed by a senior executive, on their progress in addressing the non-compliance. The participant shall additionally incur a monthly penalty charge for each affected account equal to its monthly fee as set out in paragraph 1 of Appendix VI excluding the transaction fees. This measure of redress may be imposed in the event the participant receives a second consecutive assessment of minor non-compliance or an assessment of major non-compliance; (ii) suspension: participation in TARGET2-ECB may be suspended in the circumstances described in Article 28(2)(b) and (c) of this Annex. By way of derogation from Article 28 of this Annex, the participant shall be given three months’ notice of such suspension. The participant shall incur a monthly penalty charge for each suspended account of double its monthly fee as set out in paragraph 1 of Appendix VI, excluding the transaction fees. This measure of redress may be imposed in the event the participant receives a second consecutive assessment of major non-compliance; (iii) termination: participation in TARGET2-ECB may be terminated in the circumstances described in Article 28(2)(b) and (c) of this Annex. By way of derogation from Article 28 of this Annex, the participant shall be given three months’ notice of such termination. The participant shall incur an additional penalty charge of EUR 1000 for each terminated account. This measure of redress may be imposed if the participant has not addressed the major non-compliance to the satisfaction of the ECB following three months of suspension.

▼B







TITLE VI

THE INFORMATION AND CONTROL MODULE

Article 23

Use of the ICM

1. The ICM: (a) allows participants to access information relating to their accounts and to manage liquidity; ▼M11 (b) may be used to initiate liquidity transfer orders, TIPS DCA to PM liquidity transfer orders, PM to TIPS DCA liquidity transfer orders, PM to T2S DCA liquidity transfer orders and, when the ICM is used in combination with the T2S value added services, T2S DCA to PM liquidity transfer orders; and ▼M12 (c) allows participants to initiate backup liquidity redistribution and backup contingency payments or payment orders to the Contingency Solution in the event of a failure of the participant’s payment infrastructure. ▼B

2. Further technical details relating to the ICM are contained in Appendix I.







TITLE VII

COMPENSATION, LIABILITY REGIME AND EVIDENCE

Article 24

Compensation scheme

If a payment order cannot be settled on the same business day on which it was accepted due to a technical malfunction of TARGET2, the ECB shall offer to compensate the direct participants concerned in accordance with the special procedure laid down in Appendix II.

Article 25

Liability regime

1. In performing their obligations pursuant to these Conditions, the ECB and the participants shall be bound by a general duty of reasonable care in relation to each other.

2. The ECB shall be liable to its participants in cases of fraud (including but not limited to wilful misconduct) or gross negligence, for any loss arising out of the operation of TARGET2-ECB. In cases of ordinary negligence, the ECB's liability shall be limited to the participant's direct loss, i.e. the amount of the transaction in question and/or the loss of interest thereon, excluding any consequential loss.

3. The ECB is not liable for any loss that results from any malfunction or failure in the technical infrastructure (including but not limited to the ECB's computer infrastructure, programmes, data, applications or networks), if such malfunction or failure arises in spite of the ECB having adopted those measures that are reasonably necessary to protect such infrastructure against malfunction or failure, and to resolve the consequences of such malfunction or failure (the latter including but not limited to initiating and completing the business continuity and contingency procedures referred to in Appendix IV).

4. The ECB shall not be liable: (a) to the extent that the loss is caused by the participant; or (b) if the loss arises out of external events beyond the ECB's reasonable control (force majeure).

▼M11

5. Notwithstanding Sections 675(u), 675(v), 675(x), 675(y), 675(z), 676(a), 676(c) of the German Civil Code ( Bürgerliches Gesetzbuch ), paragraphs 1 to 4 shall apply to the extent that the ECB's liability can be excluded.

▼B

6. The ECB and the participants shall take all reasonable and practicable steps to mitigate any damage or loss referred to in this Article.

7. ►M11 ◄ shall not be considered as third parties. In performing some or all of its obligations under these Conditions, the ECB may commission third parties in its own name, particularly telecommunications or other network providers or other entities, if this is necessary to meet the ECB's obligations or is standard market practice. The ECB's obligation shall be limited to the due selection and commissioning of any such third parties and the ECB's liability shall be limited accordingly. For the purposes of this paragraph, theSSP-providing NCBsshall not be considered as third parties.

Article 26

Evidence

1. ►M11 ◄ . Unless otherwise provided in these Conditions, all payment and payment processing-related messages in relation to TARGET2, such as confirmations of debits or credits, or statement messages, between the ECB and participants shall be made through theTARGET2 network service provider

2. ►M11 ◄ shall be accepted as a means of evidence of the payments processed through the ECB. The saved or printed version of the original message of the ►M11 ◄ shall be accepted as a means of evidence, regardless of the form of the original message. Electronic or written records of the messages retained by the ECB or by theTARGET2 network service providershall be accepted as a means of evidence of the payments processed through the ECB. The saved or printed version of the original message of theTARGET2 network service providershall be accepted as a means of evidence, regardless of the form of the original message.

3. ►M11 ◄ fails, the participant shall use the alternative means of transmission of messages laid down in Appendix IV. In such cases, the saved or printed version of the message produced by the ECB shall have the same evidential value as the original message, regardless of its form. If a participant's connection to theTARGET2 network service providerfails, the participant shall use the alternative means of transmission of messages laid down in Appendix IV. In such cases, the saved or printed version of the message produced by the ECB shall have the same evidential value as the original message, regardless of its form.

4. The ECB shall keep complete records of payment orders submitted and payments received by participants for a period of 10 years from the time at which such payment orders are submitted and payments are received.

5. The ECB's own books and records (whether kept on paper, microfilm, microfiche, by electronic or magnetic recording, in any other mechanically reproducible form or otherwise) shall be accepted as a means of evidence of any obligations of the participants and of any facts and events that the parties rely on.







TITLE VIII

TERMINATION OF PARTICIPATION AND CLOSURE OF ACCOUNTS

Article 27

Duration and ordinary termination of participation

1. Without prejudice to Article 28, participation in TARGET2-ECB is for an indefinite period of time.

2. A participant may terminate its participation in TARGET2-ECB at any time giving 14 business days' notice thereof, unless it agrees a shorter notice period with the ECB.

3. The ECB may terminate a participant's participation in TARGET2-ECB at any time giving three months' notice thereof, unless it agrees a different notice period with that participant.

4. On termination of participation, the confidentiality duties laid down in Article 32 remain in force for a period of five years starting on the date of termination.

5. On termination of participation, the PM accounts of the participant concerned shall be closed in accordance with Article 29.

Article 28

Suspension and extraordinary termination of participation

1. A participant's participation in TARGET2-ECB shall be immediately terminated without prior notice or suspended if one of the following events of default occurs: (a) the opening of insolvency proceedings; and/or (b) the participant no longer meets the access criteria laid down in Article 4.

▼M11

For the purposes of this paragraph, the taking of crisis prevention measures or crisis management measures within the meaning of Directive 2014/59/EU of the European Parliament and of the Council ( 9 ) against a PM account holder shall not automatically qualify as the opening of insolvency proceedings.

▼B

2. The ECB may terminate without prior notice or suspend the participant's participation in TARGET2-ECB if: (a) one or more events of default (other than those referred to in paragraph 1) occur; (b) the participant is in material breach of these Conditions; (c) the participant fails to carry out any material obligation to the ECB; (d) the participant is excluded from, or otherwise ceases to be a member of, a TARGET2 CUG; ►M4 ————— ◄ ▼M5 (e) any other participant-related event occurs which, in the ECB’s assessment, would threaten the overall stability, soundness and safety of TARGET2-ECB or of any other TARGET2 component system, which would jeopardise the ECB’s performance of its tasks as described in the Statute of the European System of Central Banks and of the European Central Bank, or poses risks on the grounds of prudence; ▼M11 (f) the ECB suspends, limits or terminates the participant's access to intraday credit pursuant to paragraph 12 of Annex III to Guideline ECB/2012/27. ▼B

3. In exercising its discretion under paragraph 2, the ECB shall take into account, inter alia, the seriousness of the event of default or events mentioned in subparagraphs (a) to (c).

4. ►M9 (a) In the event that the ECB suspends or terminates a PM account holder's participation in TARGET2-ECB under paragraph 1 or 2, the ECB shall immediately inform, by means of an ICM broadcast message or a T2S broadcast message, that PM account holder, other CBs and PM account holders and ►M11 T2S DCA holders ◄ in all of the TARGET2 component systems of such suspension or termination. Such message shall be deemed to have been issued by the home CB of the PM account holder and ►M11 T2S DCA holder ◄ that receives the message. ◄ ▼M9 ————— ▼B (c) Once such an ICM broadcast message has been received by the participants, the latter shall be deemed informed of the termination/suspension of a participant's participation in TARGET2-ECB or another TARGET2 component system. The participants shall bear any losses arising from the submission of a payment order to participants whose participation has been suspended or terminated if such payment order was entered into TARGET2-ECB after receipt of the ICM broadcast message.

5. Upon termination of a participant's participation, TARGET2-ECB shall not accept any new payment orders from such participant. Payment orders in the queue, warehoused payment orders or new payment orders in favour of such participant shall be returned.

▼M10

6. If a PM account holder is suspended from TARGET2-ECB on grounds other than those specified in paragraph 1(a), all of its incoming payments and outgoing payment orders shall be stored and only entered into the entry disposition after they have been explicitly accepted by the suspended PM account holder's CB.

▼M10

7. If a PM account holder is suspended from TARGET2-ECB on the grounds specified in paragraph 1(a), any outgoing payment orders from that PM account holder shall only be processed on the instructions of its representatives, including those appointed by a competent authority or a court, such as the PM account holder's insolvency administrator, or pursuant to an enforceable decision of a competent authority or a court providing instructions as to how the payments are to be processed. All incoming payments shall be processed in accordance with paragraph 6.

▼B

Article 29

Closure of PM accounts

1. Participants may close their PM accounts at any time provided they give the ECB 14 business days' notice thereof.

2. On termination of participation, pursuant to either Article 27 or 28, the ECB shall close the PM accounts of the participant concerned, after having: (a) settled or returned any queued payment orders; and (b) made use of its rights of pledge and set-off under Article 30.







TITLE IX

FINAL PROVISIONS

Article 30

The ECB's rights of pledge and set-off

1. The ECB shall have a pledge over the participant's existing and future credit balances on its PM accounts, thereby collateralising any current and future claims arising out of the legal relationship between the parties.

2. On the occurrence of: (a) an event of default referred to in Article 28(1); or (b) any other event of default or event referred to in Article 28(2) that has led to the termination or suspension of the participant's participation in TARGET2-ECB notwithstanding the commencement of any insolvency proceedings in respect of a participant and notwithstanding any assignment, judicial or other attachment or other disposition of or in respect of the participant's rights, all obligations of the participant shall be automatically and immediately accelerated, without prior notice and without the need for any prior approval of any authority, so as to be immediately due. In addition, the mutual obligations of the participant and the ECB shall automatically be set off against each other, and the party owing the higher amount shall pay to the other the difference.

3. The ECB shall promptly give the participant notice of any set-off pursuant to paragraph 2 after such set-off has taken place.

4. The ECB may without prior notice debit any participant's PM account by any amount which the participant owes the ECB resulting from the legal relationship between the participant and the ECB.

Article 31

Security rights in relation to funds on sub-accounts

1. The ECB shall have a pledge over the balance on a participant's sub-account opened for the settlement of AS-related payment instructions under the arrangements between the relevant ancillary system and its CB. Such balance shall collateralise the participant's obligation referred to in paragraph 7 towards the ECB in relation to such settlement.

▼M2

2. The ECB shall freeze the balance on the sub-account of the participant upon communication by the ancillary system (via a ‘start-of-cycle’ message). Where applicable, the ECB shall thereafter increase or reduce the frozen balance by crediting or debiting cross-system settlement payments to or from the sub-account or crediting liquidity transfers to the sub-account or crediting liquidity transfers to the sub-account. Such freezing shall expire upon communication by the ancillary system (via an ‘end-of-cycle’ message).

3. By confirming the freezing of the balance on the participant’s sub-account, the ECB guarantees to the ancillary system payment up to the amount of this particular balance. By confirming, where applicable, the increase or reduction of the frozen balance upon crediting or debiting cross-system settlement payments to or from the sub-account or crediting liquidity transfers to the sub-account, the guarantee is automatically increased or reduced in the amount of the payment. Without prejudice to the abovementioned increase or reduction of the guarantee, the guarantee shall be irrevocable, unconditional and payable on first demand. If the ECB is not the ancillary system’s CB, the ECB shall be deemed instructed to issue the abovementioned guarantee to the ancillary system’s CB.

▼B

4. In the absence of any insolvency proceedings in relation to the participant, the AS-related payment instructions for the squaring of the participant's settlement obligation shall be settled without drawing on the guarantee and without recourse to the security right over the balance on the participant's sub-account.

5. In the event of the participant's insolvency, the AS-related payment instruction for the squaring of the participant's settlement obligation shall be a first demand for payment under the guarantee; the debiting of the instructed amount from the participant's sub-account (and crediting of the AS's technical account) shall therefore equally involve the discharge of the guarantee obligation by the ECB and a realisation of its collateral right over the balance on the participant's sub-account.

6. The guarantee shall expire upon communication by the ancillary system that the settlement has been completed (via an ‘end-of-cycle’ message).

7. The participant shall be obliged to reimburse to the ECB any payment made by the latter under such guarantee.

Article 32

Confidentiality

▼M9

1. The ECB shall keep confidential all sensitive or secret information, including when such information relates to payment, technical or organisational information belonging to the participant, participants from the same group or the participant's customers, unless the participant or its customer has given its written consent to disclose.

▼M11

1a. By derogation from paragraph 1, the participant agrees that information on any action taken under Article 28 shall not be considered as confidential.

▼M11

2. By derogation from paragraph 1, the participant agrees that the ECB may disclose payment, technical or organisational information regarding the participant, participants from the same group or the participant's customers obtained in the course of the operation of TARGET2-ECB to: (a) other CBs or third parties that are involved in the operation of TARGET2-ECB, to the extent that this is necessary for the efficient functioning of TARGET2 or the monitoring of the participant's or its group's exposure; (b) other CBs in order to carry out the analyses necessary for market operations, monetary policy functions, financial stability or financial integration; or ▼M12 (c) supervisory, resolution and oversight authorities of Member States and the Union, including CBs, to the extent that this is necessary for the performance of their public tasks, and provided in all such cases that the disclosure is not in conflict with the applicable law. ▼M11

The ECB shall not be liable for the financial and commercial consequences of such disclosure.

▼M10

3. By derogation from paragraph 1 and provided that this does not make it possible, whether directly or indirectly, to identify the participant or the participant's customers, the ECB may use, disclose or publish payment information regarding the participant or the participant's customers for statistical, historical, scientific or other purposes in the exercise of its public functions or of functions of other public entities to which the information is disclosed.

▼B

4. Information relating to the operation of TARGET2-ECB to which participants have had access, may only be used for the purposes laid down in these Conditions. Participants shall keep such information confidential, unless the ECB has explicitly given its written consent to disclose. Participants shall ensure that any third parties to whom they outsource, delegate or subcontract tasks which have or may have an impact on the performance of their obligations under these Conditions are bound by the confidentiality requirements in this Article.

5. ►M11 ◄ . The ECB shall be authorised, in order to settle payment orders, to process and transfer the necessary data to theTARGET2 network service provider

Article 33

▼M5

Data protection, prevention of money laundering, administrative or restrictive measures and related issues

▼M13

1. Participants shall be deemed to be aware of, shall comply with, and shall be able to demonstrate that compliance to the relevant competent authorities with all obligations on them relating to legislation on data protection. They shall be deemed to be aware of, and shall comply with all obligations on them relating to legislation on prevention of money laundering and the financing of terrorism, proliferation-sensitive nuclear activities and the development of nuclear weapons delivery systems, in particular in terms of implementing appropriate measures concerning any payments debited or credited on their PM accounts. Participants shall ensure that they are informed about the TARGET2 network service provider’s data retrieval policy prior to entering into the contractual relationship with the TARGET2 network service provider.

▼B

2. Participants shall be deemed to have authorised the ECB to obtain any information relating to them from any financial or supervisory authority or trade body, whether national or foreign, if such information is necessary for the participant's participation in TARGET2-ECB.

▼M5

3. ►M6 Participants, when acting as the payment service provider of a payer or payee, shall comply with all requirements resulting from administrative or restrictive measures imposed pursuant to Articles 75 or 215 of the Treaty on the Functioning of the European Union to which they are subject, including with respect to notification and/or the obtaining of consent from a competent authority in relation to the processing of transactions. In addition: ◄ (a) when the ECB is the payment service provider of a participant that is a payer: (i) the participant shall make the required notification or obtain consent on behalf of the central bank that is primarily required to make notification or obtain consent, and shall provide the ECB with evidence of having made a notification or having received consent; and ▼M11 (ii) the participant shall not enter any payment order for the transfer of funds to an account held by an entity different than the participant, into TARGET2 until it has obtained confirmation from the ECB that the required notification has been made or the consent has been obtained by or on behalf of the payment service provider of the payee; ▼M5 (b) when the ECB is a payment service provider of a participant that is a payee, the participant shall make the required notification or obtain consent on behalf of the central bank that is primarily required to make notification or obtain consent, and shall provide the ECB with evidence of having made a notification or having received consent.

For the purposes of this paragraph, the terms ‘payment service provider’, ‘payer’ and ‘payee’ shall have the meanings given to them in the applicable administrative or restrictive measures.

▼B

Article 34

Notices

1. ►M11 ◄ . ►M11 ◄ Notices to the participant shall be sent to it at the address, fax number or its ►M4 ◄ address as the participant may from time to time notify to the ECB. Except where otherwise provided for in these Conditions, all notices required or permitted pursuant to these Conditions shall be sent by registered post, facsimile or otherwise in writing or by an authenticated message through theTARGET2 network service providerNotices to the ECB shall be submitted to the European Central Bank, Director-General of the ECB's Directorate-General Payment Systems and Market Infrastructure, Sonnemannstrasse 22, 60314 Frankfurt am Main, Germany or to the BIC address of the ECB: ECBFDEFF.Notices to the participant shall be sent to it at the address, fax number or itsBICaddress as the participant may from time to time notify to the ECB.

2. To prove that a notice has been sent, it shall be sufficient to prove that the notice was delivered to the relevant address or that the envelope containing such notice was properly addressed and posted.

3. All notices shall be given in English.

4. Participants shall be bound by all forms and documents of the ECB that the participants have filled in and/or signed, including but not limited to static data collection forms, as referred to in Article 6(2)(a), and information provided under Article 9(5), which were submitted in compliance with paragraphs 1 and 2 and which the ECB reasonably believes to have received from the participants, their employees or agents.

Article 35

Contractual relationship with ►M11 TARGET2 network service provider ◄

1. ►M11 ◄ is SWIFT. Each participant shall enter into a separate agreement with SWIFT regarding the services to be provided by SWIFT in relation to the participant's use of TARGET2-ECB. The legal relationship between a participant and SWIFT shall be exclusively governed by SWIFT's terms and conditions. For the purposes of these Conditions, theTARGET2 network service provideris SWIFT. Each participant shall enter into a separate agreement with SWIFT regarding the services to be provided by SWIFT in relation to the participant's use of TARGET2-ECB. The legal relationship between a participant and SWIFT shall be exclusively governed by SWIFT's terms and conditions.

2. ►M11 ◄ acting as the SWIFT service administrator for the SSP. Admission and exclusion of a participant to or from a TARGET2 CUG shall take effect once communicated to SWIFT by the SWIFT service administrator. Each participant shall also participate in a TARGET2 CUG, as specified by theSSP-providing NCBsacting as the SWIFT service administrator for the SSP. Admission and exclusion of a participant to or from a TARGET2 CUG shall take effect once communicated to SWIFT by the SWIFT service administrator.

3. Participants shall comply with the TARGET2 SWIFT Service Profile, as made available by the ECB.

4. The services to be provided by SWIFT shall not form part of the services to be performed by the ECB in respect of TARGET2.

5. The ECB shall not be liable for any acts, errors or omissions of SWIFT (including its directors, staff and subcontractors) as provider of SWIFT services, or for any acts, errors or omissions of network providers selected by participants to gain access to the SWIFT network.

Article 36

Amendment procedure

The ECB may at any time unilaterally amend these Conditions, ►M11 including the Appendices ◄ . Amendments to these Conditions, ►M11 including the Appendices ◄ , shall be announced by means of communication in writing to the participants. Amendments shall be deemed to have been accepted unless the participant expressly objects within 14 days of being informed of such amendments. In the event that a participant objects to the amendment, the ECB is entitled immediately to terminate that participant's participation in TARGET2-ECB and close any of its PM accounts.

Article 37

Third party rights

1. Any rights, interests, obligations, responsibilities and claims arising from or relating to these Conditions shall not be transferred, pledged or assigned by participants to any third party without the ECB's written consent.

2. These Conditions do not create any rights in favour of or obligations in relation to any entity other than the ECB and participants in TARGET2-ECB.

Article 38

Governing law, jurisdiction and place of performance

1. The bilateral relationship between the ECB and participants in TARGET2-ECB shall be governed by the law of the Federal Republic of Germany.

▼M4

2. Without prejudice to the competence of the Court of Justice of the European Union, any dispute arising from a matter relating to the relationship referred to in paragraph 1 falls under the exclusive competence of the courts of Frankfurt am Main.

▼B

3. The place of performance concerning the legal relationship between the ECB and the participants shall be Frankfurt am Main, Federal Republic of Germany.

Article 39

Severability

If any provision in these Conditions is or becomes invalid, this shall not prejudice the applicability of all the other provisions of these Conditions.

▼M13

Article 39a

Transitional provisions

1. Once the TARGET system is operational and TARGET2 has ceased operation, PM account balances shall be transferred to the account holder’s corresponding successor accounts in the TARGET system.

2. The requirement that PM account holders, indirect Participants and addressable BIC holders adhering to the SCT Inst scheme be reachable in the TIPS Platform pursuant to Article 5 shall apply as of 25 February 2022.

▼B

Article 40

Entry into force and binding nature

1. These Conditions become effective from 19 May 2008, unless the ECB communicates another date of entry into force to the participants.

▼M8

2. By requesting a PM account in TARGET2-ECB, applicant participants automatically agree to these Conditions between themselves and in relation to the ECB.

▼B









Appendix I

TECHNICAL SPECIFICATIONS FOR THE PROCESSING OF PAYMENT ORDERS

In addition to the terms and conditions of TARGET2-ECB, the following rules shall apply to the processing of payment orders:

1. Technical requirements for participation in TARGET2-ECB regarding infrastructure, network and formats

(1) TARGET2 uses SWIFT services for the exchange of messages. Each participant therefore needs a connection to SWIFT’s Secure IP Network. Each participant’s PM account shall be identified by an eight- or 11-digit SWIFT BIC. Furthermore, each participant shall pass a series of tests to prove its technical and operational competence before it may participate in TARGET2-ECB.

(2) For the submission of payment orders and the exchange of payment messages in the PM the SWIFTNet FIN Y-copy service shall be used. A dedicated SWIFT Closed User Group (CUG) shall be set up for this purpose. Payment orders within such TARGET2 CUG shall be directly addressed to the receiving TARGET2 participant by entering its BIC in the header of the SWIFTNet FIN message.

(3) For the information and control services the following SWIFTNet services may be used: (a) SWIFTNet InterAct; (b) SWIFTNet FileAct; and/or (c) SWIFTNet Browse.

(4) The security of the message exchange between participants shall rely exclusively on SWIFT’s Public Key Infrastructure (PKI) service. Information on the PKI service is available in the documentation provided by SWIFT.

(5) The ‘bilateral relationship management’ service provided by SWIFT’s Relationship Management Application (RMA) shall only be used with the central destination BIC of the SSP and not for payment messages between TARGET2 participants.

2. Payment message types

(1) The following SWIFTNet FIN/SWIFT system message types are processed: ▼M2



Message Type Type of use Description MT 103 Mandatory Customer payment MT 103+ Mandatory Customer payment (Straight Through Processing) MT 202 Mandatory Bank-to-bank payment ▼M12 MT 202COV Mandatory Cover payment ▼M2 MT 204 Optional Direct debit payment MT 011 Optional Delivery notification MT 012 Optional Sender notification MT 019 Mandatory Abort notification ▼M4 MT 900 Optional Confirmation of Debit/Credit line change MT 910 Optional Confirmation of Credit/Credit line change MT 940/950 Optional (Customer) Statement Message ▼B

(2) When they register with TARGET2-ECB, direct participants shall declare which optional message types they will use, with the exception of MT 011 and MT 012 messages in relation to which direct participants shall decide from time to time whether or not to receive them with reference to specific messages.

(3) Participants shall comply with the SWIFT message structure and field specifications, as defined in the SWIFT documentation and under the restrictions set out for TARGET2, as described in Chapter 9.1.2.2 of the User Detailed Functional Specifications (UDFS), Book 1.

(4) Field contents shall be validated at the level of TARGET2-ECB in accordance with the UDFS requirements. Participants may agree among each other on specific rules regarding the field contents. However, in TARGET2-ECB there shall be no specific checks as to whether participants comply with any such rules.

▼M2

(5) MT 202COV messages shall be used for making cover payments, i.e. payments made by correspondent banks to settle (cover) credit transfer messages which are submitted to a customer’s bank by other, more direct means. Customer details contained in MT 202COV shall not be displayed in the ICM.

▼B

3. Double-entry check

(1) All payment orders shall pass a double-entry check, the aim of which is to reject payment orders that have been submitted more than once by mistake.

(2) The following fields of the SWIFT message types shall be checked:



Details Part of the SWIFT message Field Sender Basic Header LT Address Message Type Application Header Message Type Receiver Application Header Destination Address Transaction Reference Number (TRN) Text Block :20 Related Reference Text Block :21 Value Date Text Block :32 Amount Text Block :32

(3) If all the fields described in subparagraph 2 in relation to a newly submitted payment order are identical to those in relation to a payment order that has already been accepted, the newly submitted payment order shall be returned.

4. Error codes

If a payment order is rejected, the instructing participant shall receive an abort notification (MT 019) indicating the reason for the rejection by using error codes. The error codes are defined in Chapter 9.4.2 of the UDFS.

5. Predetermined settlement times

(1) For payment orders using the Earliest Debit Time Indicator, the codeword ‘/FROTIME/’shall be used.

(2) For payment orders using the Latest Debit Time Indicator, two options shall be available. (a) Codeword ‘/REJTIME/’: if the payment order cannot be settled by the indicated debit time, the payment order shall be returned. (b) Codeword ‘/TILTIME/’: if the payment order cannot be settled by the indicated debit time, the payment order shall not be returned but shall be kept in the relevant queue. Under both options, if a payment order with a Latest Debit Time Indicator is not settled 15 minutes prior to the time indicated therein, a notification shall automatically be sent via the ICM.

(3) If the codeword ‘/CLSTIME/’ is used, the payment shall be treated in the same way as a payment order referred to in subparagraph 2(b).

6. Settlement of payment orders in the entry disposition

(1) Offsetting checks and, if appropriate, extended offsetting checks (both terms as defined in paragraphs 2 and 3) shall be carried out on payment orders entered into the entry disposition to provide quick, liquidity-saving gross settlement of payment orders.

(2) An offsetting check shall determine whether the payee’s payment orders that are at the front of the highly urgent or, if inapplicable, the urgent queue are available to be offset against the payer’s payment order (hereinafter ‘offsetting payment orders’). If an offsetting payment order does not provide sufficient funds for the respective payer’s payment order in the entry disposition, it shall be determined whether there is sufficient available liquidity on the payer’s PM account.

(3) If the offsetting check fails, the ECB may apply an extended offsetting check. An extended offsetting check determines whether offsetting payment orders are available in any of the payee’s queues regardless of when they joined the queue. However, if in the queue of the payee there are higher priority payment orders addressed to other TARGET2 participants, the FIFO principle may only be breached if settling such an offsetting payment order would result in a liquidity increase for the payee.

7. Settlement of payment orders in the queue

(1) The treatment of payment orders placed in queues depends on the priority class to which it was designated by the instructing participant.

(2) Payment orders in the highly urgent and urgent queues shall be settled by using the offsetting checks described in paragraph 6, starting with the payment order at the front of the queue in cases where there is an increase in liquidity or there is an intervention at queue level (change of queue position, settlement time or priority, or revocation of the payment order).

(3) Payments orders in the normal queue shall be settled on a continuous basis including all highly urgent and urgent payment orders that have not yet been settled. Different optimisation mechanisms (algorithms) are used. If an algorithm is successful, the included payment orders will be settled; if an algorithm fails, the included payment orders will remain in the queue. Three algorithms (1 to 3) shall be applied to offset payment flows. By means of Algorithm 4, settlement procedure 5 (as defined in Chapter 2.8.1 of the UDFS) shall be available for the settlement of payment instructions of ancillary systems. To optimise the settlement of highly urgent ancillary system transactions on participants’ sub-accounts, a special algorithm (Algorithm 5) shall be used. (a) Under Algorithm 1 (‘all-or-nothing’) the ECB shall, both for each relationship in respect of which a bilateral limit has been set and also for the total sum of relationships for which a multilateral limit has been set: (i) calculate the overall liquidity position of each TARGET2 participant’s PM account by establishing whether the aggregate of all outgoing and incoming payment orders pending in the queue is negative or positive and, if it is negative, check whether it exceeds that participant’s available liquidity (the overall liquidity position shall constitute the ‘total liquidity position’); and (ii) check whether limits and reservations set by each TARGET2 participant in relation to each relevant PM account are respected. If the outcome of these calculations and checks is positive for each relevant PM account, the ECB and other CBs involved shall settle all payments simultaneously on the PM accounts of the TARGET2 participants concerned. (b) Under Algorithm 2 (‘partial’) the ECB shall: (i) calculate and check the liquidity positions, limits and reservations of each relevant PM account as under Algorithm 1; and (ii) if the total liquidity position of one or more relevant PM accounts is negative, extract single payment orders until the total liquidity position of each relevant PM account is positive. Thereafter, the ECB and the other CBs involved shall, provided there are sufficient funds, settle all remaining payments (except the extracted payment orders) simultaneously on the PM accounts of the TARGET2 participants concerned. When extracting payment orders, the ECB shall start from the TARGET2 participant’s PM account with the highest negative total liquidity position and from the payment order at the end of the queue with the lowest priority. The selection process shall only run for a short time, to be determined by the ECB at its discretion. (c) Under Algorithm 3 (‘multiple’) the ECB shall: (i) compare pairs of TARGET2 participants’ PM accounts to determine whether queued payment orders can be settled within the available liquidity of the two TARGET2 participants’ PM accounts concerned and within the limits set by them (by starting from the pair of PM accounts with the smallest difference between the payment orders addressed to each other), and the CB(s) involved shall book those payments simultaneously on the two TARGET2 participants’ PM accounts; and (ii) if, in relation to a pair of PM accounts as described under point (i), liquidity is insufficient to fund the bilateral position, extract single payment orders until there is sufficient liquidity. In this case the CB(s) involved shall settle the remaining payments, except the extracted ones, simultaneously on the two TARGET2 participants’ PM accounts. After performing the checks specified under subparagraphs (i) to (ii), the ECB shall check the multilateral settlement positions (between a participant’s PM account and other TARGET2 participants’ PM accounts in relation to which a multilateral limit has been set). For this purpose, the procedure described under subparagraphs (i) to (ii) shall apply mutatis mutandis. (d) Under Algorithm 4 (‘partial plus ancillary system settlement’) the ECB shall follow the same procedure as for Algorithm 2, but without extracting payment orders in relation to the settlement of an ancillary system (which settles on a simultaneous multilateral basis). (e) Under Algorithm 5 (‘ancillary system settlement via sub-accounts’) the ECB shall follow the same procedure as for Algorithm 1, subject to the modification that the ECB shall start Algorithm 5 via the Ancillary System Interface and shall only check whether sufficient funds are available on participants’ sub-accounts. Moreover, no limits and reservations shall be taken into account. Algorithm 5 shall also run during night-time settlement.

(4) Payment orders entered into the entry disposition after the start of any of algorithms 1 to 4 may nevertheless be settled immediately in the entry disposition if the positions and limits of the TARGET2 participants’ PM accounts concerned are compatible with both the settlement of these payment orders and the settlement of payment orders in the current optimisation procedure. However, two algorithms shall not run simultaneously.

(5) During daytime processing the algorithms shall run sequentially. As long as there is no pending simultaneous multilateral settlement of an ancillary system, the sequence shall be as follows: (a) algorithm 1, (b) if algorithm 1 fails, then algorithm 2, (c) if algorithm 2 fails, then algorithm 3, or if algorithm 2 succeeds, repeat algorithm 1. When simultaneous multilateral settlement (‘procedure 5’) in relation to an ancillary system is pending, Algorithm 4 shall run.

(6) The algorithms shall run flexibly by setting a pre-defined time lag between the application of different algorithms to ensure a minimum interval between the running of two algorithms. The time sequence shall be automatically controlled. Manual intervention shall be possible.

(7) While included in a running algorithm, a payment order shall not be reordered (change of the position in a queue) or revoked. Requests for reordering or revocation of a payment order shall be queued until the algorithm is complete. If the payment order concerned is settled while the algorithm is running, any request to reorder or revoke shall be rejected. If the payment order is not settled, the participant’s requests shall be taken into account immediately.

8. Use of the ICM

(1) The ICM may be used for obtaining information and managing liquidity. SWIFT’s Secure IP Network (SIPN) shall be the underlying technical communications network for exchanging information and running control measures.

(2) With the exception of warehoused payment orders and static data information, only data in relation to the current business day shall be available via the ICM. The screens shall be offered in English only.

(3) Information shall be provided in ‘pull’ mode, which means that each participant has to ask to be provided with information.

(4) The following modes shall be available for using the ICM: (a) Application-to-application mode (A2A) In A2A, information and messages are transferred between the PM and the participant’s internal application. The participant therefore has to ensure that an appropriate application is available for the exchange of XML messages (requests and responses) with the ICM via a standardised interface. Further details are contained in the ICM User Handbook and in Book 4 of the UDFS. ▼M13 (b) User-to-application mode (U2A) U2A permits direct communication between a participant and the ICM. The information is displayed in a browser running on a PC system (SWIFT Alliance WebStation or another interface, as may be required by SWIFT). For U2A access the IT infrastructure has to be able to support cookies. Further details are described in the ICM User Handbook.

▼M2

(5) Each participant shall have at least one SWIFT Alliance WebStation, or another interface, as may be required by SWIFT, to have access to the ICM via U2A.

▼B

(6) Access rights to the ICM shall be granted by using SWIFT’s ‘Role Based Access Control’. The SWIFT ‘Non Repudiation of Emission’ (NRE) service, which may be used by participants, allows the recipient of an XML message to prove that such message has not been altered.

(7) ►M12 If a participant has technical problems and is unable to submit any payment order, it may generate preformatted backup liquidity redistribution and backup contingency payments by using the ICM. The ECB shall open such functionality upon request of the participant. ◄

(8) Participants may also use the ICM to transfer liquidity: (a) from their PM account to their account outside the PM; (b) between the PM account and the participant’s sub-accounts; and ▼M11 (c) from the PM account to the technical account managed by the ancillary system using settlement procedure 6 real-time; (d) by means of a PM to T2S DCA liquidity transfer order or, when the ICM is used in combination with the T2S value added services, a T2S DCA to PM liquidity transfer order; and ▼M11 (e) by means of a PM to TIPS DCA liquidity transfer order or a TIPS DCA to PM liquidity transfer order. ▼B

9. The UDFS and the ICM User Handbook

Further details and examples explaining the above rules are contained in the UDFS and the ICM User Handbook, as amended from time to time and published on the ECB’s website in English.









Appendix II

TARGET2 COMPENSATION SCHEME

1. General principles

(a) If there is a technical malfunction of TARGET2, direct participants may submit claims for compensation in accordance with the TARGET2 compensation scheme laid down in this Appendix.

(b) Unless otherwise decided by the ECB's Governing Council, the TARGET2 compensation scheme shall not apply if the technical malfunction of TARGET2 arises out of external events beyond the reasonable control of the CBs concerned or as a result of acts or omissions by third parties.

(c) Compensation under the TARGET2 compensation scheme shall be the only compensation procedure offered in the event of a technical malfunction of TARGET2. Participants may, however, use other legal means to claim for losses. If a participant accepts a compensation offer under the TARGET2 compensation scheme, this shall constitute the participant's irrevocable agreement that it thereby waives all claims in relation to the payment orders concerning which it accepts compensation (including any claims for consequential loss) it may have against any CB, and that the receipt by it of the corresponding compensation payment constitutes full and final settlement of all such claims. The participant shall indemnify the CBs concerned, up to a maximum of the amount received under the TARGET2 compensation scheme, in respect of any further claims which are raised by any other participant or any other third party in relation to the payment order or payment concerned.

(d) The making of a compensation offer shall not constitute an admission of liability by the ECB or any other CB in respect of a technical malfunction of TA