Tento dokument slúži čisto na potrebu dokumentácie a inštitúcie nenesú nijakú zodpovednosť za jeho obsah

►B ROZHODNUTIE EURÓPSKEJ CENTRÁLNEJ BANKY z 24. júla 2007

o podmienkach TARGET 2-ECB (ECB/2007/7) (2007/601/ES)

(Ú. v. EÚ L 237, 8.9.2007, s. 71)

Zmenené a doplnené:

Úradný vestník

Č.								Strana Dátum
►M1	Rozhodnutie Európskej centrálnej banky ECB/2009/13 z 9. júna 2009						L 151	39	16.6.2009
►M2	Rozhodnutie Európskej centrálnej banky ECB/2009/22 zo 6. októbra 2009						L 274	38	20.10.2009
►M3	Rozhodnutie Európskej centrálnej banky ECB/2010/4 z 10. mája 2010						L 119	24	13.5.2010
►M4	Rozhodnutie Európskej novembra 2010	centrálnej	banky	ECB/2010/19	z	2.	L 290	53	6.11.2010
►M5	Rozhodnutie Európskej novembra 2011	centrálnej	banky	ECB/2011/19	z	15.	L 303	44	22.11.2011
►M6	Rozhodnutie Európskej decembra 2012	centrálnej	banky	ECB/2012/31	z	11.	L 13	8	17.1.2013
►M7	Rozhodnutie Európskej júna 2014	centrálnej	banky	ECB/2014/27	zo	16.	L 192	68	1.7.2014
►M8	Rozhodnutie Európskej mája 2015	centrálnej	banky	ECB/2015/22	z	26.	L 155	1	19.6.2015

ROZHODNUTIE EURÓPSKEJ CENTRÁLNEJ BANKY

z 24. júla 2007

o podmienkach TARGET 2-ECB (ECB/2007/7) (2007/601/ES)

VÝKONNÁ RADA EURÓPSKEJ CENTRÁLNEJ BANKY,

so zreteľom na Zmluvu o založení Európskeho spoločenstva, a najmä na jej článok 105 ods. 2 štvrtú zarážku,

so zreteľom na Štatút Európskeho systému centrálnych bánk a Európskej centrálnej banky, a najmä na jeho články 11.6, 17, 22 a 23,

keďže:

(1) Jednotná menová politika vyžaduje také platobné systémy, prostredníctvom ktorých možno uskutočňovať operácie menovej politiky medzi národnými centrálnymi bankami a úverovými inštitúciami včasným a bezpečným spôsobom, a ktoré posilňujú jednotnosť peňažného trhu v rámci eurozóny.

(2) Pôvodný Transeurópsky automatizovaný expresný systém hrubého zúčtovania platieb v reálnom čase (ďalej len „TARGET“) sa nahrádza systémom TARGET2, ktorého základným znakom je jednotná technická platforma s názvom Jednotná spoločná platforma (ďalej len „SSP“). TARGET2 bude aj naďalej plniť tie isté základné ciele ako TARGET, pričom bude poskytovať spoľahlivý a efektívny mechanizmus na zúčtovanie platieb v eurách, ktorý funguje na základe SSP.

(3) Rada guvernérov prijala usmernenie ECB/2007/2 z 26. apríla 2007 o Transeurópskom automatizovanom expresnom systéme hrubého zúčtovania platieb v reálnom čase (TARGET2) (1).

(4) Európska centrálna banka (ďalej len „ECB“) sa bude zúčastňovať na TARGET2 s cieľom spracovávať svoje vlastné platby a platby svojich klientov v TARGET2 a poskytovať prostredníctvom TARGET2 zúčtovacie služby organizáciám vykonávajúcim klíring a zúčtovanie, vrátane subjektov, ktoré sú usadené mimo Európskeho hospodárskeho priestoru (ďalej len „EHP“) za pred pokladu, že podliehajú dohľadu príslušného orgánu a ich prístup do TARGET2-ECB bol schválený Radou guvernérov.

(5) Klientmi ECB môžu byť len centrálne banky a európske a medzi národné organizácie.

(6) V súlade s týmto rozhodnutím môže ECB poskytnúť vnútrodenný úver len klientom, ktorí sú európskymi alebo medzinárodnými organizáciami.

(1) Pozri stranu 1 tohto úradného vestníka.

(7) Rada guvernérov rozhodla, že pravidlá systémov, ktoré sú súčasťou TARGET2, budú v čo najväčšej možnej miere zosúla dené a že sa zverejnia,

ROZHODLA TAKTO:

Článok 1

Rozsah pôsobnosti

1. TARGET2-ECB môže len:

a) spracovávať vlastné platby ECB;

b) spracovávať platby klientov ECB a

▼M2

c) poskytovať zúčtovacie služby subjektom spravujúcim pridružené systémy vrátane subjektov, ktoré sú usadené mimo EHP za pred pokladu, že podliehajú dohľadu príslušného orgánu, spĺňajú požia davky v oblasti dohľadu, ktoré sa týkajú umiestnenia infraštruktúr na poskytovanie služieb v eurách tak, ako sú tieto požiadavky priebežne menené a dopĺňané a uverejňované na internetových stránkach ECB (1), a ich prístup do TARGET2-ECB bol schválený Radou guvernérov.

▼M3

2. Klientmi ECB môžu byť len centrálne banky, európske a medziná

rodné organizácie, a ak o tom rozhodne ad hoc Rada guvernérov, ústredné vlády členských štátov Európskej únie alebo verejnoprávne subjekty ustanovené týmito ústrednými vládami za ich zástupcov.

▼B

Článok 2

Vnútrodenný úver

1. ECB môže poskytnúť vnútrodenný úver len klientom, ktorí sú európskymi alebo medzinárodnými organizáciami formou prečerpaní na účte alebo účtoch takýchto klientov. Prečerpania nesmú kedykoľvek

(1) ►M8 Súčasná politika Eurosystému v oblasti umiestnenia infraštruktúr je ustanovená v nasledujúcich dokumentoch, ktoré sú dostupné na internetových stránkach ECB na xxx.xxx.xxxxxx.xx: a) Policy statement on euro payment and settlement systems located outside the euro area z 3. novembra 1998, b) The Eurosystem's policy line with regard to consolidation in central coun terparty clearing z 27. septembra 2001, c) The Eurosystem policy principles on the location and operation of infrastructures settling in euro-denominated payment transactions z 19. júla 2007, d) The Eurosystem policy principles on the location and operation of infrastructures settling euro-denominated payment transactions: specification of ‘legally and operationally located in the euro area’ z 20. novembra 2008, e) The Eurosystem oversight policy framework z júla 2011, v zmysle rozsudku zo 4. marca 2015, Spojené kráľovstvo proti Európskej centrálnej banke, T-496/11, ECLI:EU:T:2015:

496. ◄

počas dňa prekročiť sumu vymedzenú v dohode s klientom pre každý z týchto účtov. Vnútrodenný úver poskytnutý ECB sa obmedzí na pred metný deň a nie je možné ho predĺžiť na jednodňový úver.

▼M8

▼B

2. Akékoľvek poskytnutie vnútrodenného úveru zo strany ECB sa uskutoční v súlade s pravidlami o poskytovaní vnútrodenného úveru, ktoré sú ustanovené v prílohe III k usmerneniu ECB/2007/2.

Článok 3

Podmienky TARGET2-ECB

Podmienky otvorenia a vedenia účtu PM v TARGET2-ECB sú ustano vené v prílohe I k tomuto rozhodnutiu. Podmienky otvorenia a vedenia účelového peňažného účtu v TARGET2-ECB sú ustanovené v prílohe II k tomuto rozhodnutiu.

Článok 4

Nadobudnutie účinnosti

1. Toto rozhodnutie nadobúda účinnosť 19. mája 2008.

2. Rozhodnutie ECB/1999/NP3 zo 16. marca 1999 o platobnom mechanizme Európskej centrálnej banky a rozhodnutie ECB/2003/NP2 z 28. januára 2003, ktorým sa mení a dopĺňa rozhodnutie ECB/ 1999/NP3 o platobnom mechanizme Európskej centrálnej banky sa zrušujú s účinnosťou od dátumu nadobudnutia účinnosti tohto rozhod nutia a odkazy na rozhodnutie ECB/1999/NP3 a rozhodnutie ECB/ 2003/NP2 sa považujú za odkazy na toto rozhodnutie.

▼M8

▼B

ANNEX I

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

TITLE I

GENERAL PROVISIONS

Article 1

Definitions

▼M4

▼M2

▼B

▼M8

▼M2

▼M4

▼M8

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

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

— ‘ancillary system (AS)’ 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 website (1), in which payments and/or financial instruments are exchanged and/or cleared while the resulting monetary obligations are settled in TARGET2 in accor dance with Guideline ECB/2007/2 and a bilateral arrangement between the ancillary system and the relevant CB,

— ‘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,

— ‘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,

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

— ‘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 Coun cil (2),

(1) ►M8 The Eurosystem's current policy for the location of infrastructure is set out in the following statements, which are all available on the ECB's website at www.ecb.euro xx.xx: (a) the Policy statement on euro payment and settlement systems located outside the euro area of 3 November 1998; (b) The Eurosystem's policy line with regard to consolidation in central counterparty clearing of 27 September 2001; (c) The Eurosystem policy principles on the location and operation of infrastructures settling in euro-deno minated payment transactions of 19 July 2007; (d) The Eurosystem policy principles on the location and operation of infrastructures settling euro-denominated payment transac tions: specification of ‘legally and operationally located in the euro area’ of 20 November 2008; (e) The Eurosystem oversight policy framework of July 2011, subject to the judgment of 4 March 2015, United Kingdom v European Central Bank, T-496/11,

ECLI:EU:T:2015:496. ◄

(2) Regulation (EU) No 575/2013 of the European Parliament and of the Council of 26 June 2013 on prudential requirements for credit institutions and investment firms and amen ding Regulation (EU) No 648/2012 (OJ L 176, 27.6.2013, p. 1).

▼B

▼M8

▼B

▼M7

▼M8

▼B

▼M6

▼M8

— ‘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 asse ssment of a participant's legal capacity to enter into and carry out its obli gations 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 Euro system CB, which is connected to TARGET2 pursuant to a specific agree ment,

— ‘Contingency Module’ means the SSP module enabling the processing of critical and very critical payments in contingency situations,

— ‘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,

— ‘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 x xxxxx to make funds avai lable 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,

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

— ‘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 authoriza tion,

— ‘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 instruc ting the SCB to debit the settlement bank's PM account or sub-account as a result of debit instructions,

— ‘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,

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

— ‘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,

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

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

— ‘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:

▼M8

▼B

▼M8

▼B

(a) where the participant no longer meets the access criteria laid down in Article 4 or the requirements laid down in Article 8(1)(a)(i);

(b) the opening of insolvency proceedings in relation to the participant;

(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 arran gement with its creditors;

(f) where the participant is, or is deemed by its CB to be, insolvent or unable to pay its debts;

(g) where the participant's credit balance on its PM account or 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;

(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;

— ‘Information and Control Module (ICM)’ means the SSP module that allows participants to obtain on-line information and gives them the possibility to submit liquidity transfer orders, manage liquidity and initiate backup payment orders in contingency situations,

— ‘ICM broadcast message’ means information made simultaneously available to all or a selected group of TARGET2 participants via the ICM,

— ‘indirect participant’ means a credit institution established in the European Economic Area (EEA), which has entered into an agreement with a direct participant to submit payment orders and receive payments via such direct participant'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,

— ‘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,

— ‘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 coun terparties 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,

— ‘multi-addressee access’ means the facility by which branches or credit insti tutions established in the EEA 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,

— ‘Main PM account’ means the PM account to which a DCA is linked and on which any remaining balance must be automatically repatriated from the DCA at the end of the day,

— ‘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,

▼M8

▼B

▼M5

▼B

▼M8

▼B

▼M4

▼M8

▼B

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

— ‘participant’ [or ‘direct participant’] means an entity that holds at least one PM account (PM account holder) and/or one Dedicated Cash Account (DCA holder) with the ECB,

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

— ‘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,

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

— ‘payment order’ means a credit transfer order, a liquidity transfer order, a direct debit instruction or a PM to DCA liquidity transfer order,

— ‘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,

— ‘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 prohibi tions referred to in Articles 104 and 104b(1) of the Treaty (1),

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

— ‘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 (2);

— ‘Single Shared Platform (SSP)’ means the single technical platform infra structure provided by the SSP-providing CBs,

— ‘SSP-providing CBs’ 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,

— ‘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 settle ment (RTGS) systems that form part of TARGET2,

(1) OJ L 332, 31.12.1993, p. 1.

(2) OJ L 166, 11.6.1998, p. 45.

▼M2

▼M4

▼M8

▼B

— ‘TARGET2 CUG’ means a subset of the network service provider's custo mers grouped for the purpose of their use of the relevant services and products of the network service provider when accessing the PM,

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

— ‘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 the same-day processing of payments in TARGET2-ECB,

— ‘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.

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.

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

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.

Article 3

General description of TARGET2-ECB and TARGET2

▼M8

1. TARGET2 provides real-time gross settlement for payments in euro, with settlement in central bank money across PM accounts and DCAs.

2. The following payment orders are processed in TARGET2-ECB:

(a) payment orders directly resulting from or made in connection with Euro system monetary policy operations;

(b) settlement of the euro leg of foreign exchange operations involving the Eurosystem;

(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) PM to DCA liquidity transfer orders; and

(g) any other payment orders in euro addressed to TARGET2 participants.

3. TARGET2 is established and functions on the basis of the SSP. The Euro system specifies the SSP's technical configuration and features. The SSP services are provided by the SSP-providing CBs for the benefit of the Eurosystem CBs, pursuant to separate agreements.

4. The ECB is the provider of services under these Conditions. Acts and omissions of the SSP-providing CBs 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 relati onship between participants and the SSP-providing CBs when the latter act in that capacity. Instructions, messages or information which a participant 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 participants in TARGET2-ECB and the ECB. The rules on the processing of payment orders (Title IV) refer to all payment orders submitted or payments received by any TARGET2 participant.

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

▼M2

▼B

TITLE II

PARTICIPATION

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.

Article 5

Direct participants

Direct participants in TARGET2-ECB shall comply with the requirements set out in Article 6(1) and (2). They shall have at least one PM account with the ECB.

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 TARGET2-ECB 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 agree ment with the network service provider to obtain the necessary connection and admissions, in accordance with the technical specifications in Appendix I; and

(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

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 parti cipate. 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

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 parti cipants’ names and BICs.

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 other wise provided in these Conditions or required by law, the ECB shall use all reasonable means within its power to perform its obligations under these Condi tions, 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 stabi lity, soundness and safety of TARGET2-ECB. They shall provide each other with any information or documents relevant for the performance of their respec tive 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 operati ons.

3. Up-to-date information on the SSP's operational status shall be available on the TARGET2 Information System (T2IS). 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.

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 rela ting to them that is entered into TARGET2-ECB by the ECB.

6. The ECB shall be deemed to be authorised to communicate to the SSP- providing CBs any information relating to participants which the SSP-providing CBs may need in their role as service administrators, in accordance with the contract entered into with the 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.

8. Participants shall immediately inform the ECB if an event of default occurs in relation to them.

TITLE IV

MANAGEMENT OF PM ACCOUNTS AND PROCESSING OF PAYMENT ORDERS

Article 10

Opening and management of PM accounts

▼M2

▼B

▼M7

▼B

▼M8

▼B

1. The ECB shall open and operate at least one PM account for each parti cipant. 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.

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

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

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.

5. A PM account holder accepting its PM account to be designated as the Main PM account defined in Annex II shall be bound by any invoices related to the opening and operation of each Dedicated Cash Account 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 Xxxxx XXXx, regardless of the content of, or any non-compliance with, the contractual or other arrangements between that PM account holder and the DCA holder.

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

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;

(d) PM to DCA liquidity transfer orders.

Article 12

Acceptance and rejection of payment orders

▼M2

1. Payment orders submitted by participants are deemed accepted by the ECB if:

(a) the payment message complies with the rules established by the 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 x xxxxx 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.

3. The SSP determines the timestamp for the processing of payment orders on the basis of the time when it receives and accepts the payment order.

▼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

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

2. Highly urgent payment orders may only be designated by:

(a) CBs; and

(b) participants, in cases of payments to and from CLS International Bank and liquidity transfers in relation to ancillary system settlement using the Xxxxxx xxxx System Interface.

▼M8

All payment instructions submitted by an ancillary system through the ASI to debit or credit the participants' PM accounts and all PM to 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 bila teral 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 reser vation. 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 ware housed 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 imme diately 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 appli cable 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 (indepen dently 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.

▼M2

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 x xxxxx, 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 algo rithm, 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

Article 21

Business continuity and contingency procedures

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.

Article 22

Security requirements

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 avai lability 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 on all participants and/or on participants that are considered critical by the ECB.

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;

(b) may be used to initiate liquidity transfer orders; and

(c) allows participants to initiate backup lump sum and backup contingency payments in the event of a failure of the participant's payment infrastructure.

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 conse quential 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).

▼M6

5. Notwithstanding Sections 675(u), 675(v), 675(x), 675y 675z, 676a, 676c 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.

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. In performing some or all of its obligations under these Conditions, the ECB may commission third parties in its own name, particularly telecommuni cations 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 para graph, the SSP-providing CBs shall not be considered as third parties.

Article 26

Evidence

1. 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 the network service provider.

2. Electronic or written records of the messages retained by the ECB or by the network service provider 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 network service provider shall be accepted as a means of evidence, regardless of the form of the original message.

3. If a participant's connection to the network service provider fails, the parti cipant 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 repro ducible 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 termi nated 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.

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;

(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;

(f) the ECB suspends, limits or terminates the participant’s access to intraday credit pursuant to paragraph 12 of Annex III to Guideline ECB/2007/2.

▼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. (a) In the event that the ECB suspends or terminates a participant's parti cipation in TARGET2-ECB under paragraph 1 or 2, the ECB shall immediately inform that participant, other CBs and the other partici pants of such suspension or termination by means of an ICM broadcast message.

(c) Once such an ICM broadcast message has been received by the parti cipants, the latter shall be deemed informed of the termination/suspen sion 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.

6. If a participant is suspended from TARGET2-ECB, all 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 participant's CB.

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 relati onship 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).

▼M2

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 settle ment 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 instruc tion 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

1. The ECB shall keep confidential all sensitive or secret information, inclu ding when such information relates to payment, technical or organisational infor mation belonging to the participant or the participant's customers, unless the participant or its customer has given its written consent to disclose.

▼M8

2. By derogation from paragraph 1, the participant agrees that the ECB may disclose payment, technical or organisational information regarding the partici pant, participants from the same group or the participant's customers obtained in the course of the operation of TARGET2-ECB to 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, or to supervisory and oversight authorities of Member States and the Union to the extent that this is necessary for the perfor mance of their public tasks, and provided in all such cases that the disclosure is not in conflict with the applicable law. The ECB shall not be liable for the financial and commercial consequences of such disclosure.

▼B

3. By derogation from paragraph 1 and provided this does not make it possible, whether directly or indirectly, to identify the participant or the partici pant'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 whom the information is disclosed.

4. Information relating to the operation of TARGET2-ECB to which partici pants 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. The ECB shall be authorised, in order to settle payment orders, to process and transfer the necessary data to the network service provider.

▼M5

Article 33

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

▼M4

1. Participants shall be deemed to be aware of, and shall comply with, all obligations on them relating to legislation on data protection, prevention of money laundering, the financing of terrorism, proliferation-sensitive nuclear acti vities 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 also acquaint themselves with the network service provider’s data retrieval policy prior to entering into the contractual relationship with the 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 x xxxxx 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 x xxxxx:

(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

(ii) the participant shall not enter any credit transfer order into TARGET2 until it has obtained confirmation from the ECB that the required noti fication has been made or the consent has been obtained by or on behalf of the payment service provider of the payee;

(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 admini strative or restrictive measures.

Article 34

Notices

1. 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 the network service provider. Notices to the ECB shall be submitted to Director General of the ECB's Directorate General Payment Systems and Market Infra structure, Xxxxxxxxxxxxx 00, X-00000 Xxxxxxxxx xx Xxxx, Xxxxxxx or to the

►M4 BIC ◄ address of the ECB: XXXXXXXX. Notices to the participant shall be sent to it at the address, fax number or its ►M4 BIC ◄ address 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 network service provider

1. For the purposes of these Conditions, the network service provider 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 XXXXX'x terms and conditions.

2. Each participant shall also participate in a TARGET2 CUG, as specified by the SSP-providing CBs 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.

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, including its Appendices. Amendments to these Conditions, including its Appendices, shall be announced by means of communication in writing to the participants. Amend ments 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

▼M4

▼B

▼M8

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

2. Without prejudice to the competence of the Court of Justice of the Euro pean 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.

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 preju dice the applicability of all the other provisions of these Conditions.

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.

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

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 XXXXX’x 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

(4) The security of the message exchange between participants shall rely exclusively on SWIFT’s Public Key Infrastructure (PKI) service. Infor mation 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 proces sed:

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
MT 202COV	Mandatory	Cover payments
MT 204	Optional	Direct debit payment
MT 011	Optional	Delivery notification
MT 012	Optional	Sender notification
MT 019	Mandatory	Abort notification
MT 900	Optional	Confirmation of Debit/Credit line change

▼M2

▼M4

Message Type	Type of use	Description
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. Xxxxx ver, 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 xxxxx 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	Message Type
	Header
Receiver	Application	Destination
	Header	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.

▼B

5. Predetermined settlement times

(1) For payment orders using the Earliest Debit Time Indicator, the code word ‘/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 Indi cator is not settled 15 minutes prior to the time indicated therein, a noti fication 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 (herei nafter ‘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.

▼B

(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 parti cipant’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 reserva tions 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.

(i) compare pairs of TARGET2 participants’ PM accounts to deter mine 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).

▼B

(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 simulta neously.

(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,

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 infor mation, only data in relation to the current business day shall be avai lable 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.

▼M2

▼B

▼M8

▼B

(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 and JavaScript. Further details are described in the ICM User Handbook.

(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.

(6) Access rights to the ICM shall be granted by using XXXXX’x ‘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) If a participant has technical problems and is unable to submit any payment order, it may generate preformatted backup lump sum 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;

(d) by means of a PM to DCA liquidity transfer order.

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.

▼B

▼M2

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 malfunc tion 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 malfunc tion 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 TARGET2.

2. Conditions for compensation offers

(a) X xxxxx may submit a claim for an administration fee and interest compensation if, due to a technical malfunction of TARGET2, a payment order was not settled on the business day on which it was accepted;

▼B

(b) A payee may submit a claim for an administration fee if due to a technical malfunction of TARGET2 it did not receive a payment that it was expec ting to receive on a particular business day. The payee may also submit a claim for interest compensation if one or more of the following condi tions are met:

(i) in the case of participants that have access to the marginal lending facility: due to a technical malfunction of TARGET2, a payee had recourse to the marginal lending facility; and/or

(ii) in the case of all participants: it was technically impossible to have recourse to the money market or such refinancing was impossible on other, objectively reasonable grounds.

3. Calculation of compensation

(a) With respect to a compensation offer for x xxxxx:

(i) the administration fee shall be EUR 50 for the first non-settled payment order, EUR 25 for each of the next four such payment orders and EUR 12,50 for each further such payment order. The administration fee shall be calculated separately in relation to each payee;

▼B

(ii) interest compensation shall be determined by applying a reference rate to be fixed from day to day. This reference rate shall be the lower of the euro overnight index average (EONIA) rate and the marginal lending rate. The reference rate shall be applied to the amount of the payment order not settled as a result of the technical malfunction of TARGET2 for each day in the period from the date of the actual or, in relation to payment orders referred to in para graph 2(a)(ii), intended submission of the payment order until the date on which the payment order was or could have been succe ssfully settled. Any proceeds made by placing funds resulting from non-settled payment orders on deposit with the Eurosystem shall be deducted from the amount of any compensation; and

(iii) no interest compensation shall be payable if and in so far as funds resulting from non-settled payment orders were placed in the market or used to fulfil minimum reserve requirements.

(b) With respect to a compensation offer for a payee:

(ii) the method set out in subparagraph (a)(ii) for calculating interest compensation shall apply except that interest compensation shall be payable at a rate equal to the difference between the marginal lending rate and the reference rate, and shall be calculated on the amount of any recourse to the marginal lending facility occurring as a result of the technical malfunction of TARGET2.

4. Procedural rules

(a) A claim for compensation shall be submitted on the claim form available on the website of the ECB in English (see xxx.xxx.xxx). Payers shall submit a separate claim form in respect of each payee and payees shall submit a separate claim form in respect of each payer. Sufficient addi tional information and documents shall be provided to support the infor mation indicated in the claim form. Only one claim may be submitted in relation to a specific payment or payment order.

(b) Within four weeks of a technical malfunction of TARGET2, participants shall submit their claim form(s) to the ECB. Any additional information and evidence requested by the ECB shall be supplied within two weeks of such request being made.

(c) Unless otherwise decided by the ECB's Governing Council and commu nicated to the participants, all received claims shall be assessed no later than 14 weeks after the technical malfunction of TARGET2 occurs.

(d) The ECB shall communicate the result of the assessment referred to in subparagraph (c) to the relevant participants. If the assessment entails a compensation offer, the participants concerned shall, within four weeks of the communication of such offer, either accept or reject it, in respect of each payment or payment order comprised within each claim, by signing a standard letter of acceptance (in the form available on the website of the ECB (see xxx.xxx.xxx). If such letter has not been received by the ECB within four weeks, the participants concerned shall be deemed to have rejected the compensation offer.

(e) The ECB shall make compensation payments on receipt of a participant's letter of acceptance of compensation. No interest shall be payable on any compensation payment.

▼B

Appendix III

TERMS OF REFERENCE FOR CAPACITY AND COUNTRY OPINIONS

Terms of reference for capacity opinions for participants in TARGET2

The European Central Bank Xxxxxxxxxxxxx 00

D-60311 Frankfurt am Main Germany

Participation in TARGET2-ECB

[location], [date] Dear Sir or Madam,

We have been asked to provide this Opinion as [in-house or external] legal advisers to [specify name of Participant or branch of Participant] in respect of issues arising under the laws of [jurisdiction in which the Participant is establis hed; hereinafter the ‘jurisdiction’] in connection with the participation of [specify name of Participant] (hereinafter the ‘Participant’) in TARGET2-ECB (herei nafter the ‘System’).

This Opinion is confined to the laws of [jurisdiction] as they exist as on the date of this Opinion. We have made no investigation of the laws of any other juris diction as a basis for this Opinion, and do not express or imply any opinion in this regard. Each of the statements and opinions presented below applies with equal accuracy and validity under the laws of [jurisdiction], whether or not the Participant acts through its head office or one or more branches established inside or outside of [jurisdiction] in submitting payment orders and receiving payments.

I. DOCUMENTS EXAMINED

For the purposes of this Opinion, we have examined:

(1) a certified copy of the [specify relevant constitutional document(s)] of the Participant such as is/are in effect on the date hereof;

(2) [if applicable] an extract from the [specify relevant company register] and [if applicable] [register of credit institutions or analogous register];

(3) [to the extent applicable] a copy of the Participant's licence or other proof of authorisation to provide banking, investment, funds transfer or other financial services in [jurisdiction];

(4) [if applicable] a copy of a resolution adopted by the board of directors or the relevant governing body of the Participant on [insert date], [insert year], evidencing the Participant's agreement to adhere to the System Documents, as defined below; and

(5) [specify all powers of attorney and other documents constituting or evidencing the requisite power of the person or persons signing the relevant System Documents (as defined below) on behalf of the Parti cipant];

and all other documents relating to the Participant's constitution, powers, and authorisations necessary or appropriate for the provision of this Opinion (hereinafter the ‘Participant Documents’).

▼B

For the purposes of this Opinion, we have also examined:

(1) the terms and conditions of TARGET2-ECB dated [insert date] (herei nafter the ‘Rules’); and

(2) […].

The Rules and the […] shall be referred to hereinafter as the ‘System Documents’ (and collectively with the Participant Documents as the ‘Docu ments’).

II. ASSUMPTIONS

For the purposes of this Opinion we have assumed in relation to the Docu ments that:

(1) the System Documents with which we have been provided are originals or true copies;

(2) the terms of the System Documents and the rights and obligations created by them are valid and legally binding under the laws of the Federal Republic of Germany by which they are expressed to be xxxxxx xxx, and the choice of the laws of the Federal Republic of Germany to govern the System Documents is recognised by the laws of the Federal Republic of Germany;

(3) the Participant Documents are within the capacity and power of and have been validly authorised, adopted or executed and, where necessary, deli vered by the relevant parties; and

(4) the Participant Documents are binding on the parties to which they are addressed, and there has been no breach of any of their terms.

III. OPINIONS REGARDING THE PARTICIPANT

A. The Participant is a corporation duly established and registered or other wise duly incorporated or organised under the laws of [jurisdiction].

B. The Participant has all the requisite corporate powers to execute and perform the rights and obligations under the System Documents to which it is party.

C. The adoption or execution and the performance by the Participant of the rights and obligations under the System Documents to which the Parti cipant is party will not in any way breach any provision of the laws or regulations of [jurisdiction] applicable to the Participant or the Participant Documents.

D. No additional authorisations, approvals, consents, filings, registrations, notarisations or other certifications of or with any court or governmental, judicial or public authority that is competent in [jurisdiction] are required by the Participant in connection with the adoption, validity or enforcea bility of any of the System Documents or the execution or performance of the rights and obligations thereunder.

E. The Participant has taken all necessary corporate action and other steps necessary under the laws of [jurisdiction] to ensure that its obligations under the System Documents are legal, valid and binding

This Opinion is stated as of its date and is addressed solely to the ECB and the [Participant]. No other persons may rely on this Opinion, and the contents of this Opinion may not be disclosed to persons other than its intended recipients and their legal counsel without our prior written consent, with the exception of the national central banks of the European System of Central Banks [and [the national central bank/relevant regulatory authorities] of [jurisdiction]].

Yours faithfully,

[signature]

▼B

Terms of reference for country opinions for non-EEA participants in TARGET2

The European Central Bank Xxxxxxxxxxxxx 00

D-60311 Frankfurt am Main Germany

TARGET2-ECB

[location], [date] Dear Sir or Madam,

We have been asked as [external] legal advisers to [specify name of Participant or branch of Participant] (the Participant) in respect of issues arising under the laws of [jurisdiction in which the Participant is established; hereinafter the ‘juris diction’] to provide this Opinion under the laws of [jurisdiction] in connection with the participation of the Participant in a system which is a component of TARGET2 (hereinafter the ‘System’). References herein to the laws of [jurisdic tion] include all applicable regulations of [jurisdiction]. We express an opinion herein under the law of [jurisdiction], with particular regard to the Participant established outside the Federal Republic of Germany in relation to rights and obligations arising from participation in the System, as presented in the System Documents defined below.

This Opinion is confined to the laws of [jurisdiction] as they exist on the date of this Opinion. We have made no investigation of the laws of any other jurisdiction as a basis for this Opinion, and do not express or imply any opinion in this regard. We have assumed that there is nothing in the laws of another jurisdiction which affects this Opinion.

1. DOCUMENTS EXAMINED

For the purposes of this Opinion, we have examined the documents listed below and such other documents as we have deemed necessary or appro priate:

(1) the terms and conditions of TARGET2-ECB dated [insert date] (herei nafter the ‘Rules’); and

(2) any other document governing the System and/or the relationship between the Participant and other participants in the System, and between the participants in the System and the ECB.

The Rules and the […] shall be referred to hereinafter as the ‘System Documents’.

2. ASSUMPTIONS

For the purposes of this Opinion we have assumed in relation to the System Documents that:

(1) the System Documents are within the capacity and power of and have been validly authorised, adopted or executed and, where necessary, delivered by the relevant parties;

(2) the terms of the System Documents and the rights and obligations created by them are valid and legally binding under the laws of the Federal Republic of Germany, by which they are expressed to be xxxxxx xxx, and the choice of the laws of the Federal Republic of Germany to govern the System Documents is recognised by the laws of the Federal Republic of Germany;

▼B

(3) the participants in the System through which any payment orders are sent or payments are received, or through which any rights or obliga tions under the System Documents are executed or performed, are licensed to provide funds transfer services, in all relevant jurisdictions; and

(4) the documents submitted to us in copy or as specimens conform to the originals.

3. OPINION

Based on and subject to the foregoing, and subject in each case to the points set out below, we are of the opinion that:

3.1. Country-specific legal aspects [to the extent applicable]

The following characteristics of the legislation of [jurisdiction] are consistent with and in no way set aside the obligations of the Partici pant arising out of the System Documents: [list of country-specific legal aspects].

3.2. General insolvency issues

3.2.a Types of insolvency proceedings

The only types of insolvency proceedings (including composition or rehabilitation) — which, for the purpose of this Opinion, shall include all proceedings in respect of the Participant's assets or any branch it may have in [jurisdiction] — to which the Participant may become subject in [jurisdiction], are the following: [list proceedings in original language and English translation] (together collectively referred to as ‘Insolvency Proceedings’).

In addition to Insolvency Proceedings, the Participant, any of its assets, or any branch it may have in [jurisdiction] may become subject in [jurisdiction] to [list any applicable moratorium, recei vership, or any other proceedings as a result of which payments to and/or from the Participant may be suspended, or limitations can be imposed in relation to such payments, or similar procee dings in original language and English translation] (hereinafter collectively referred to as ‘Proceedings’).

3.2.b Insolvency treaties

[jurisdiction] or certain political subdivisions within [jurisdiction], as specified, is/are party to the following insolvency treaties: [specify, if applicable which have or may have an impact on this Opinion].

3.3. Enforceability of System Documents

Subject to the points set out below, all provisions of the System Docu ments will be binding and enforceable in accordance with their terms under the laws of [jurisdiction], in particular in the event of the opening of any Insolvency Proceedings or Proceedings with respect to the Parti cipant.

In particular, we are of the opinion that:

3.3.a Processing of payment orders

The provisions on processing of payment orders [list of sections] of the Rules are valid and enforceable. In particular, all payment orders processed pursuant to such sections will be valid, binding and will be enforceable under the laws of [jurisdiction]. The provision of the Rules which specifies the precise point in time at which payment orders submitted by the Participant to the System become enforceable and irrevocable (Article 20 of the Rules) is valid, binding and enforceable under the laws of [juris diction].

▼B

3.3.b Authority of the ECB to perform its functions

The opening of Insolvency Proceedings or Proceedings in respect of the Participant will not affect the authority and powers of the ECB arising out of the System Documents. [Specify [to the extent applicable] that: the same opinion is also applicable in respect of any other entity which provides the Participants with services directly and necessarily required for participating in the System (e.g. network service provider)].

3.3.c Remedies in the event of default

[Where applicable to the Participant, the provisions contained in Article 30 of the Rules regarding accelerated performance of claims which have not yet matured, the set-off of claims for using the deposits of the Participant, the enforcement of a pledge, suspension and termination of participation, claims for default interest, and termination of agreements and transactions (Articles 27-31 of the Rules) are valid and enforceable under the laws of [jurisdiction].]

3.3.d Suspension and termination

Where applicable to the Participant, the provisions contained in Articles 27 and 28 of the Rules (in respect of suspension and termination of the Participant's participation in the System on the opening of Insolvency Proceedings or Proceedings or other events of default, as defined in the System Documents, or if the Parti cipant represents any kind of systemic risk or has serious opera tional problems) are valid and enforceable under the laws of [jurisdiction].

3.3.e Assignment of rights and obligations

The rights and obligations of the Participant cannot be assigned, altered or otherwise transferred by the Participant to third parties without the prior written consent of the ECB.

3.3.f Choice of governing law and jurisdiction

The provisions contained in Articles 34 and 38 of the Rules, and in particular in respect of the governing law, the resolution of a dispute, competent courts, and service of process are valid and enforceable under the laws of [jurisdiction].

3.4. Voidable preferences

We are of the opinion that no obligation arising out of the System Documents, the performance thereof, or compliance therewith prior to the opening of any Insolvency Proceedings or Proceedings in respect of the Participant may be set aside in any such proceedings as a preference, voidable transaction or otherwise under the laws of [jurisdiction].

In particular, and without limitation to the foregoing, we express this opinion in respect of any payment orders submitted by any participant in the System. In particular, we are of the opinion that the provisions of Article 20 of the Rules establishing the enforceability and irrevocability of payment orders will be valid and enforceable and that a payment order submitted by any participant and processed pursuant to Title IV of the Rules may not be set aside in any Insolvency Proceedings or Proceedings as a preference, voidable transaction or otherwise under the laws of [jurisdiction].

▼B

▼M2

3.5. Attachment

If a creditor of the Participant seeks an attachment order (including any freezing order, order for seizure or any other public or private law procedure that is intended to protect the public interest or the rights of the Participant's creditors) — hereinafter referred to as an ‘Atta chment’ — under the laws of [jurisdiction] from a court or governmen tal, judicial or public authority that is competent in [jurisdiction], we are of the opinion that [insert the analysis and discussion].

3.6. Collateral [if applicable]

3.6.a Assignment of rights or deposit of assets for collateral purposes, pledge and/or repo

Assignments for collateral purposes will be valid and enforceable under the laws of [jurisdiction]. Specifically, the creation and enforcement of a pledge or repo under the Rules will be valid and enforceable under the laws of [jurisdiction].

▼B

3.6.b Priority of assignees’, pledgees’ or repo purchasers’ interest over that of other claimants

In the event of Insolvency Proceedings or Proceedings in respect of the Participant, the rights or assets assigned for collateral purposes, or pledged by the Participant in favour of the ECB or other participants in the System, will rank in priority of payment above the claims of all other creditors of the Participant and will not be subject to priority or preferential creditors.

3.6.c Enforcing title to security

Even in the event of Insolvency Proceedings or Proceedings in respect of the Participant, other participants in the System and the ECB as pledgees will still be free to enforce and collect the Participant's rights or assets through the action of the ECB pursuant to the Rules.

3.6.d Form and registration requirements

There are no form requirements for the assignment for collateral purposes of, or the creation and enforcement of a pledge or repo over the Participant's rights or assets and it is not necessary for the assignment for collateral purposes, pledge or repo, as appli cable, or any particulars of such assignment, pledge or repo, as applicable, to be registered or filed with any court or governmen tal, judicial or public authority that is competent in [jurisdiction].

3.7. Branches [to the extent applicable]

3.7.a Opinion applies to action through branches

Each of the statements and opinions presented above with regard to the Participant applies with equal accuracy and validity under the laws of [jurisdiction] in situations where the Participant acts through its one or more of its branches established outside [juris diction].

3.7.b Conformity with law

Neither the execution and performance of the rights and obliga tions under the System Documents nor the submission, transmis sion or receipt of payment orders by a branch of the Participant will in any respect breach the laws of [jurisdiction].

▼B

3.7.c Required authorisations

Neither the execution and performance of the rights and obliga tions under the System Documents nor the submission, transmis sion or receipt of payment orders by a branch of a Participant will require any additional authorisations, approvals, consents, filings, registrations, notarisations or other certifications of or with any court or governmental, judicial or public authority that is compe tent in [jurisdiction].

Yours faithfully,

[signature]

▼B

▼M2

Appendix IV

BUSINESS CONTINUITY AND CONTINGENCY PROCEDURE

1. General provisions

(a) This Appendix sets out the arrangements between the ECB and partici pants, or ancillary systems, if one or more components of the SSP or the telecommunications network fail or are affected by an abnormal external event, or if the failure affects any participant or ancillary system.

(b) All references to specific times in this Appendix are to the local time at the seat of the ECB, i.e. Central European Time (CET) (1).

▼B

2. Measures of business continuity and contingency processing

(a) In the event that an abnormal external event occurs and/or there is a failure of the SSP or the telecommunications network which affects the normal operation of TARGET2, the ECB shall be entitled to adopt business continuity and contingency processing measures.

(b) The following main business continuity and contingency processing measures shall be available in TARGET2:

(i) relocating the operation of the SSP to an alternative site;

(ii) changing the SSP's operating hours; and

(iii) initiating contingency processing of very critical and critical payments, as defined in paragraph 6(c) and (d) respectively.

(c) In relation to business continuity and contingency processing measures, the ECB shall have full discretion regarding whether and which measures are adopted to settle payment orders.

3. Incident communication

(a) Information about the failure of the SSP and/or an abnormal external event shall be communicated to participants through the domestic communication channels, the ICM and T2IS. In particular, communica tions to participants shall include the following information:

(i) a description of the event;

(ii) the anticipated delay in processing (if known);

(iii) information on the measures already taken; and

(iv) the advice to participants.

(b) In addition, the ECB may notify participants of any other existing or anticipated event which has the potential to affect the normal operation of TARGET2.

4. Relocation the operation of the SSP to an alternative site

(a) In the event that any of the events referred to in paragraph 2(a) occurs, the operation of the SSP may be relocated to an alternative site, either within the same region or in another region.

(b) In the event that the operation of the SSP is relocated to another region, the participants shall use best efforts to reconcile their positions up to the point of the failure or the occurrence of the abnormal external event and provide to the ECB all relevant information in this respect.

5. Change of operating hours

(a) The daytime processing of TARGET2 may be extended or the opening time of a new business day may be delayed. During any extended operating time of TARGET2, payment orders shall be processed in accordance with the terms and conditions of TARGET2-ECB, subject to the modifications contained in this Appendix.

(1) CET takes into account the change to Central European Summer Time.

▼B

▼M8

▼B

(b) Daytime processing may be extended and the closing time thereby delayed if an SSP failure has occurred during the day but has been resolved before 18.00. Such a closing time delay shall in normal circu mstances not exceed two hours and shall be announced as early as possible to participants. If such a delay is announced before 16.50, the minimum period of one hour between the cut-off time for customer and interbank payment orders shall remain in place. Once such a delay is announced it may not be withdrawn.

(c) The closing time shall be delayed in cases where an SSP failure has occurred before 18:00 and has not been resolved by 18.00. The ECB shall immediately communicate the delay of closing time to participants.

(d) Upon recovery of the SSP, the following steps shall take place:

(i) The ECB shall seek to settle all queued payments within one hour; this time is reduced to 30 minutes in the event that the SSP failure occurs at 17.30 or later (in cases where the SSP failure was ongoing at 18.00).

(ii) Participants' final balances shall be established within one hour; this time shall be reduced to 30 minutes in the event that the SSP failure occurs at 17.30 or later, in cases where the SSP failure was ongoing at 18.00.

(iii) At the cut-off time for interbank payments, the end-of-day proces sing, including recourse to the Eurosystem standing facilities shall take place.

(e) Ancillary systems that require liquidity in the early morning need to have established means to cope with cases where the daytime processing cannot be started in time due to an SSP failure on the previous day.

6. Contingency processing

(a) If it deems it necessary to do so, the ECB shall initiate the contingency processing of payment orders in the Contingency Module of the SSP. In such cases, only a minimum service level shall be provided to partici pants. The ECB shall inform its participants of the start of contingency processing by means of any available means of communication.

(b) In contingency processing, payment orders shall be processed manually by the ECB.

(c) The following payments shall be considered as ‘very critical’ and the ECB shall use best efforts to process them in contingency situations:

(i) CLS Bank International-related payments;

(ii) end-of-day settlement of EURO1; and

(iii) central counterparty margin calls.

(d) The following types of payments shall be considered ’critical‘ and the ECB may decide to initiate contingency processing in relation to them:

(i) payments in relation to the real-time settlement of interfaced secu rities settlement systems;

(ii) additional payments, if required to avoid systemic risk; and

(iii) DCA to PM liquidity transfer orders.

(e) Participants shall submit payment orders for contingency processing and information to payees shall be provided through encrypted and authen ticated e-mail, as well as via authenticated fax. Information concerning account balances and debit and credit entries may be obtained via the ECB.

(f) Payment orders that have already been submitted to TARGET2-ECB, but are queued, may also undergo contingency processing. In such cases the ECB shall endeavour to avoid the double processing of payment orders, but the participants shall bear the risk of such double processing if it occurred.

▼B

(g) For contingency processing of payment orders, participants shall provide additional collateral. During contingency processing, incoming contin gency payments may be used to fund outgoing contingency payments. For the purposes of contingency processing, participants' available liqui dity may not be taken into account by the ECB.

7. Failures linked to participants or ancillary systems

(a) In the event that a participant has a problem that prevents it from settling payments in TARGET2 it shall be its responsibility to resolve the problem. In particular, a participant may use in-house solutions or the ICM functionality, i.e. backup lump sum payments and backup contin gency payments (CLS, EURO1, STEP2 pre-fund).

(b) If a participant decides to use the ICM functionality for making backup lump sum payments, the ECB shall, if the participant so requests, open this functionality via the ICM. If the participant so requests, the ECB shall transmit an ICM broadcast message to inform other participants about the participant's use of backup lump sum payments. The partici pant shall be responsible for sending such backup lump sum payments exclusively to other participants with which it has bilaterally agreed on the use of such payments and for any further steps in relation to such payments.

(c) If the measures referred to in subparagraph (a) are exhausted or if they are inefficient, the participant may request support from the ECB.

(d) In the event that a failure affects an ancillary system, that ancillary system shall be responsible for resolving the failure. If the ancillary system so requests, the ECB may act on its behalf. The ECB shall have discretion to decide what support it gives to the ancillary system, including during the night-time operations of the ancillary system. The following contingency measures may be taken:

(i) the ancillary system initiates clean payments (i.e. payments that are not linked to the underlying transaction) via the Participant Inter face;

(ii) the ECB creates and/or processes XML instructions/files on behalf of the ancillary system; and/or

(iii) the ECB makes clean payments on behalf of the ancillary system.

(e) The detailed contingency measures with respect to ancillary systems shall be contained in the bilateral arrangements between the ECB and the relevant ancillary system.

8. Other provisions

(a) In the event that certain data are unavailable because one of the events referred to in paragraph 3(a) has occurred, the ECB is entitled to start or continue processing payment orders and/or operate TARGET2-ECB on the basis of the last available data, as determined by the ECB. If so requested by the ECB, participants and ancillary systems shall resubmit their FileAct/Interact messages or take any other action deemed appro priate by the ECB.

(b) In the event of a failure of the ECB, some or all of its technical functions in relation to TARGET2-ECB may be performed by other Eurosystem CBs.

(c) The ECB may require that the participants participate in regular or ad hoc testing of business continuity and contingency processing measures, training or any other preventive arrangements, as deemed necessary by the ECB. Any costs incurred by the participants as a result of such testing or other arrangements shall be borne solely by the participants.

▼M2

Appendix V

OPERATING SCHEDULE

1. TARGET2 is open on all days, except Saturdays, Sundays, New Year’s Day, Good Friday and Easter Monday (according to the calendar applicable at the seat of the ECB), 1 May, Christmas Day and 26 December.

2. The reference time for the system is the local time at the seat of the ECB, i.e. CET.

3. The current business day is opened during the evening of the previous business day and operates to the following schedule:

Time	Description
6.45-7.00	Business window to prepare daytime operations (*)
7.00-18.00	Daytime processing
17.00	Cut-off time for customer payments (i.e. payments where the originator and/or the beneficiary of a payment is not a direct or indirect participant as identified in the system by the use of an MT 103 or MT 103 + message)
18.00	Cut-off time for interbank payments (i.e. payments other than customer payments)
18.00-18.45 (**)	End-of-day processing
18.15 (**)	General cut-off time for the use of standing facilities
(Shortly after) 18.30 (***)	Data for the update of accounting systems are available to CBs
18.45-19.30 (***)	Start-of-day processing (new business day)
19.00 (*)-19.30 ()	Provision account	of	liquidity	on	the	PM
19.30 (***)	‘Start-of-procedure’ message and settlement of the standing orders to transfer liquidity from the PM accounts to the sub-account(s)/mirror account (ancillary system-related settlement)
19.30 (***)-22.00	Execution of additional liquidity trans fers via the ICM before the ancillary system sends the ‘start-of-cycle’ message; settlement period of night- time ancillary system operations (only for ancillary system settlement proce dure 6)
22.00-1.00	Technical maintenance period

▼M2

▼M4

Time

Description

1.00 - 7.00

Settlement procedure of night-time ancillary system operations (only for ancillary system settlement procedure 6)

(*) Daytime operations means daytime processing and end-of-day processing.

(**) Ends 15 minutes later on the last day of the Eurosystem reserve maintenance period.

(***) Starts 15 minutes later on the last day of the Eurosystem reserve maintenance period.

▼M2

4. The ICM is available for liquidity transfers from 19.30 (1) until 18.00 the next day, except during the technical maintenance period from 22.00 until 1.00.

5. The operating hours may be changed in the event that business continuity measures are adopted in accordance with paragraph 5 of Appendix IV.

(1) Starts 15 minutes later on the last day of the Eurosystem reserve maintenance period.

▼M8

Appendix VI

FEE SCHEDULE AND INVOICING

Fees for direct participants

1. The monthly fee for the processing of payment orders in TARGET2-ECB for direct participants, depending on which option the direct participant has chosen, shall be either:

(a) EUR 150 per PM account plus a flat fee per transaction (debit entry) of EUR 0,80; or

(b) EUR 1 875 per PM account plus a fee per transaction (debit entry) determined as follows, based on the volume of transactions (number of processed items) per month:

Band	From	To	Price
1	1	10 000	EUR 0,60
2	10 001	25 000	EUR 0,50
3	25 001	50 000	EUR 0,40
4	50 001	100 000	EUR 0,20
5	Above 100 000	—	EUR 0,125

Liquidity transfers between a participant's PM account and its sub-accounts shall not be subject to a charge.

PM to DCA liquidity transfer orders sent from a participant's PM account and DCA to PM liquidity transfer orders received on a participant's PM account shall be charged according to the pricing option (a) or (b) above chosen for that PM account.

2. The monthly fee for multi-addressee access shall be EUR 80 for each 8-digit BIC address other than the BIC of the direct participant's account.

3. There shall be an additional monthly fee for direct participants who do not wish the BIC of their account to be published in the TARGET2 directory of EUR 30 per account.

4. The monthly fee for each registration by a direct participant of an indirect participant in the TARGET2 directory shall be EUR 20.

5. The one-time fee for each registration in the TARGET2 directory of an addressable BIC holder, for branches of direct and indirect participants, branches of correspondents and addressable BIC holders that are members of the same group, as defined in Article 1, shall be EUR 5.

6. The monthly fee for each registration in the TARGET2 directory of an addressable BIC holder for a correspondent shall be EUR 5.

7. The monthly fee for direct participants subscribing to the TARGET2 value- added services for T2S shall be EUR 50 for those participants which have opted for option (a) in paragraph 1 above, and EUR 625 for those partici pants which have opted for option (b) in paragraph 1 above.

Fees for liquidity pooling

8. For the Consolidated Account Information (CAI) mode, the monthly fee shall be EUR 100 for each account included in the group.

9. For the Aggregated Liquidity (AL) mode, the monthly fee shall be EUR 200 for each account included in the AL group. If the AL group uses the CAI mode, accounts not included in the AL mode shall pay the CAI monthly fee of EUR 100 per account.

10. For both the AL mode and the CAI mode, the degressive transaction fee structure set out in the table in paragraph 1(b) shall apply to all payments by the participants in the group, as if these payments were sent from one participant's account.

▼M8

11. The monthly fee of EUR 1 875 referred to in paragraph 1(b) shall be paid by the relevant group manager, and the monthly fee of EUR 150 referred to in paragraph 1(a) shall be paid by all other members of the group. If an AL group is part of a CAI group, and the AL group manager is the same as the CAI group manager, the monthly fee of EUR 1 875 shall only be paid once. If the AL group is a part of a CAI group and the CAI group manager is different from the AL group manager, then the CAI group manager shall pay an additional monthly fee of EUR 1 875. In such cases the invoice for the total fees for all the accounts in the CAI group (including the AL group accounts) shall be sent to the CAI group manager.

Fees for Main PM account holders

12. In addition to the fees set out above in this Appendix, a monthly fee of EUR

250 for each linked DCA shall be charged to Main PM account holders.

13. The Main PM account holders shall be charged the following fees for T2S services connected with the linked DCA(s). These items shall be billed separately.

Tariff items	Price	Explanation
Settlement services
DCA to DCA liquidity transfer orders	9 eurocent	per transfer
Intra-balance movement (i.e. blocking, unblocking, reservation of liquidity etc)	6 eurocent	per transaction
Information services
A2A reports	0,4 eurocent	Per business item in any A2A report generated
A2A queries	0,7 eurocent	Per queried business item in any A2A query genera ted
U2A queries	10 eurocent	Per executed search func tion
Messages bundled into a file	0,4 eurocent	Per message in a file
Transmissions	1,2 eurocent	Per transmission

Invoicing

14. In the case of direct participants, the following invoicing rules apply. The direct participant (the AL group or CAI group manager in the event that the AL or CAI modes are used) shall receive the relevant invoices for the previous month specifying the fees to be paid, no later than on the fifth business day of the following month. Payment shall be made at the latest on the tenth working day of that month to the account specified by the ECB and shall be debited from that participant's PM account.

▼M8

ANNEX II

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

TITLE I

GENERAL PROVISIONS

Article 1

Definitions

For the purposes of these Harmonised Conditions (hereinafter the ‘Conditions’) the following definitions apply:

— ‘Auto-collateralisation’ means intraday credit granted by the euro area national central bank (NCB) in central bank money triggered when a DCA holder has insufficient funds to settle securities transactions, whereby such intraday credit is collateralised either with the securities being purchased (collateral on flow), or with securities held by the DCA holder in favour of the euro area NCB (collateral on stock),

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

— ‘Immediate liquidity transfer order’ means an instruction to make a DCA to PM liquidity transfer order, a PM to DCA liquidity transfer order or a DCA to DCA liquidity transfer order in real-time upon the receipt of the said instruction,

— ‘Predefined liquidity transfer order’ means an instruction to transfer a speci fied amount of funds from a DCA to a PM account to be executed only once at a defined time or event,

— ‘Liquidity adjustment’ means the authorisation given by the DCA holder, to its participating CSD or the ECB by special contractual arrangement duly documented and registered in the Static Data to initiate liquidity transfers between a DCA and a PM Account, or between two DCAs,

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

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

— ‘DCA to DCA liquidity transfer order’ means the instruction to transfer a specified amount of funds from (i) a DCA to a DCA linked to the same Main PM account; or (ii) from a DCA to a DCA held by the same legal entity,

— ‘Main PM account’ means the PM Account to which a DCA is linked and on which any remaining balance will be automatically repatriated at end-of-day,

— ‘Standing liquidity transfer order’ means an instruction to transfer a specified amount of cash or ‘all cash’ available in the T2S DCA from a DCA to a PM account to be executed repetitively at a defined time or event in the T2S processing cycle until the order is deleted or the validity period expires,

— ‘Static Data’ means the set of business objects, specific to a DCA holder or central bank, in T2S and owned respectively by that DCA holder or central bank, that T2S requires to process the transactional data related to that DCA holder or central bank,

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

— ‘ISO country code’ means a code as defined by ISO Standard No 3166-1,

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

▼M8

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

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

— ‘connected NCB’ means an NCB, other than a Eurosystem CB, which is connected to TARGET2 pursuant to a specific agreement,

— ‘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 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 compa rable to supervision by a competent authority,

— ‘euro area NCB’ means the NCB of a Member State whose currency is the euro,

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

(a) where the participant no longer meets the access criteria laid down in Article 5 or the requirements laid down in Article 6(1)(a)(i);

(b) the opening of insolvency proceedings in relation to the participant;

(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 arran gement with its creditors;

(f) where the participant is, or is deemed by its CB to be, insolvent or unable to pay its debts;

(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,

— ‘insolvency proceedings’ means insolvency proceedings within the meaning of Article 2(j) of Directive 98/26/EC,

— ‘TARGET2 network service provider’ means a provider of computerised network connections appointed by the ECB's Governing Council for the purpose of submitting payment messages in TARGET2,

▼M8

— ‘T2S network service provider’ means an undertaking that has concluded a licence agreement with the Eurosystem to provide connectivity services in the context of T2S,

— ‘payee’, except where used in Article 28 of these Conditions, means a TARGET2 participant whose DCA will be credited as a result of a payment order being settled,

— ‘payer’, except where used in Article 28 of these Conditions, means a TARGET2 participant whose DCA will be debited as a result of a payment order being settled,

— ‘payment order’ means a DCA to PM liquidity transfer order, a PM to DCA liquidity transfer order or a DCA to DCA liquidity transfer order,

— ‘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 Eurosystem 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 Eurosystem CB,

— ‘Single Shared Platform (SSP)’ means the single technical platform infra structure provided by the SSP-providing NCBs,

— ‘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 participating CSDs and Eurosystem CBs that allow core, neutral and borderless settlement of securities transac tions on a delivery-versus-payment basis in central bank money,

— ‘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,

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

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

— ‘T2S GUI’ means module on the T2S Platform which allows DCA holders to obtain on-line information and gives them the possibility to submit payment orders,

— ‘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 settle ment (RTGS) systems that form part of TARGET2,

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

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

— ‘technical malfunction of TARGET2’ means any difficulty, defect or failure in the technical infrastructure and/or the computer systems used by TARGET2-ECB including the SSP or T2S Platform, or any other event that makes it impossible to execute and complete the same-day processing of payments in TARGET2-ECB,

▼M8

— ‘available liquidity’ means the credit balance on the DCA decreased by the amount of any processed reservations of liquidity or blocking of funds,

— ‘participating Central Securities Depository’ or ‘participating CSD’ means a CSD that has signed the T2S Framework Agreement,

— ‘A2A’ or ‘Application-to-application’ means a connectivity mode allowing the DCA holder to exchange information with the software application of the T2S Platform,

— ‘U2A’ or ‘User-to-application’ means a connectivity mode allowing the DCA holder to exchange information with software applications on the T2S Plat form through a graphical user interface,

— ‘T2S Distinguished Name’ or ‘T2S DN’ means the network address for the T2S Platform which must be included in all messages intended for the system,

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

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

— ‘real-time gross settlement’ means the processing and settlement of payment orders on a transaction by transaction basis in real-time.

Article 2

Scope

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

Article 3

Appendices

1. The following Appendices form an integral part of these Conditions: Appendix I: Parameters of the dedicated cash accounts — Technical specifi

cations;

Appendix II: TARGET2 compensation scheme in relation to the opening and the operation of the DCA;

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.

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.

Article 4

General description of T2S and TARGET2

1. TARGET2 provides real-time gross settlement for payments in euro, with settlement in central bank money across PM accounts and DCAs. By virtue of Guideline ECB/2012/27 (1)., TARGET2 also provides real-time gross settlement services in respect of T2S transactions for DCA holders having ensured a link with a securities account at a participating CSD. Such services are provided on the T2S Platform, enabling the exchange of standardised messages in respect of the transfers from and to the DCAs opened on the books of the relevant euro area NCB in TARGET2.

(1) Guideline ECB/2012/27 of 5 December 2012 on a Trans-European Automated Real- time Gross settlement Express Transfer system (TARGET2) (OJ L 30, 30.1.2013, p. 1).

▼M8

2. The following transactions are processed in TARGET2-ECB:

(a) payment orders directly resulting from or made in connection with Euro system monetary policy operations;

(b) settlement of the euro leg of foreign exchange operations involving the Eurosystem;

(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) DCA to DCA liquidity transfer orders, DCA to PM liquidity transfer orders and PM to DCA liquidity transfer orders; and

(g) any other payment orders in euro addressed to TARGET2 participants.

3. TARGET2 provides real-time gross settlement for payments in euro, with settlement in central bank money across PM accounts and DCAs. TARGET2 is established and functions on the basis of the SSP through which all 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 Dedicated Cash Accounts on T2S is concerned, TARGET2 is technically esta blished and functions on the basis of the T2S Platform. The ECB is the provider of services under these Conditions. Acts and omissions of the SSP-providing NCBs and the 4CBs shall be considered acts and omissions of the ECB, for which it shall assume liability in accordance with Article 21 below. Participation pursuant to these Conditions shall not create a contractual relationship between participants and SSP-providing NCBs or the 4CBs when any of the latter act in that capacity. Instructions, messages or information which a participant receives from, or sends to, the SSP or T2S Platform in relation to the services provided under these Conditions are deemed to be received from, or sent to, the ECB.

4. 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 Directive 98/26/EC. TARGET2-ECB is designated as a ‘system’ under the national laws implemen ting Directive 98/26/EC. TARGET2-ECB is designated as a system under Section 1(16) of the KWG.

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

TITLE II

PARTICIPATION

Article 5

Access criteria

Article 6

Application procedure

1. In order for the ECB to open a DCA for an entity, such entity must comply with the access criteria of Article 5 and shall:

(a) fulfil the following technical requirements:

▼M8

(i) install, manage, operate and monitor and ensure the security of the necessary IT infrastructure to provide a technical connection to the SSP and/or the T2S Platform and submit payment orders to it. In doing so, applicant participants may involve third parties, but retain sole liability. In particular, when connecting directly to the T2S Platform, applicant DCA holders shall enter into an agreement with a T2S network service provider to obtain the necessary connection and admissions, in accordance with the technical specifications in Appendix I; and

(ii) have passed the certification testing and obtained the authorisation required by the ECB; and

(b) fulfil the following legal requirements:

(i) 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

(ii) for entities established outside the EEA, acting through a branch esta blished in 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. Entities wishing to open a DCA 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

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 open a DCA if:

(a) the access criteria referred to in Article 5 are not met;

(b) one or more of the participation criteria referred to in paragraph 1 are not met; and/or

(c) in the ECB's assessment, opening a DCA would endanger the overall stabi lity, soundness and safety of TARGET2-ECB or of any other TARGET2 component system, or 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.

5. The ECB shall communicate its decision on the application to open a DCA to the applicant within one month of the ECB's receipt thereof. 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

DCA holders

DCA holders in TARGET2-ECB shall comply with the requirements set out in Article 6. They shall have at least one DCA with the ECB.

Article 8

Links between securities accounts and DCAs

1. A DCA holder may request the ECB to link its DCA to one or more securities account(s) held on its own behalf or on behalf of its clients which hold securities accounts in one or more participating CSD.

▼M8

2. DCA holders linking their DCA to securities account(s) on behalf of clients as set out in paragraph 1 are responsible for establishing and maintaining the list of linked securities accounts and, where relevant, the set-up of the client-colla teralisation feature.

3. As a result of the request under paragraph 1, the DCA holder is deemed to have given a mandate to the CSD where such linked securities accounts are maintained to debit the DCA with the amounts resulting from securities transac tions taking place on these securities accounts.

4. Paragraph 3 shall apply regardless of any agreements the DCA holder has with the CSD and/or the securities account holders.

TITLE III

OBLIGATIONS OF THE PARTIES

Article 9

Obligations of the ECB and the DCA holders

1. The ECB shall open upon request of the DCA holder and operate one or more DCA(s) denominated in euro. 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. The fees for DCA services are laid down in Appendix VI. The holder of the Main PM account to which the DCA is linked is liable for paying these fees.

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

4. The DCA holder 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.

5. DCA holders shall ensure that the liquidity in the DCA during the day is properly managed. This obligation shall include but is not limited to obtaining regular information on their liquidity position. The ECB shall provide a daily statement of accounts to any DCA holder that has opted for such service on the T2S Platform provided that the DCA holder is connected to the T2S Platform via a T2S network service provider.

Article 10

Cooperation and information exchange

1. In performing their obligations and exercising their rights under these Conditions, the ECB and DCA holders 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 DCA holders in relation to difficulties arising in connection with system operations.

3. Up-to-date information on the operational status of the TARGET2 platform and the T2S Platform shall be available on the TARGET2 Information System (T2IS) and the TARGET2-Securities Information System respectively. The T2IS and the TARGET2 Securities Information System may be used to obtain infor mation on any event affecting the normal operation of the respective platforms.

4. The ECB may either communicate messages to DCA holders by means of broadcast messages or by any other means of communication. DCA holders may collect information via the ICM, to the extent they also hold a PM account, or otherwise via the T2S GUI.

▼M8

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

6. The ECB shall be deemed to be authorised to communicate to the SSP- providing NCBs or the 4CBs any information relating to DCA holders which the former may need in their role as service administrators, in accordance with the contract entered into with the TARGET2 network service provider and/or the T2S network service provider.

7. DCA holders 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.

8. DCA holders shall inform the ECB of:

(a) any new holder of a securities account linked to the DCA pursuant to Article 8(1), which they accept; and

(b) any changes related to the holders of securities accounts listed in point (a).

9. DCA holders shall immediately inform the ECB if an event of default occurs in relation to themselves.

Article 11

Designation, suspension or termination of the Main PM account

1. The DCA holder shall designate a Main PM account to which the DCA is linked. The Main PM account may be held in a TARGET2 component system other than TARGET2-ECB and may belong to a different legal entity from the DCA holder.

2. A participant using internet based access cannot be designated as a Main PM account holder.

3. If the holder of the Main PM account and the holder of the DCA are different legal entities and in the event that the participation of that designated Main PM account holder is suspended or terminated, the ECB and the DCA holder shall take all reasonable and practicable steps to mitigate any ensuing damage or loss. The DCA holder shall take all necessary steps to designate a new Main PM account without undue delay which will then be liable for any outstan ding invoices. On the day of the suspension or termination of the Main PM account holder and until a new Main PM account holder has been designated, any funds remaining on the DCA at the end of the day shall be moved to an account of the ECB. These funds will be subject to the remuneration conditions of Article 10(3) of Annex I to this Decision.

4. The ECB shall not be liable for any losses incurred by the DCA holder as a consequence of the suspension or termination of the Main PM account holder's participation.

TITLE IV

OPENING AND MANAGEMENT OF THE DCA AND PROCESSING OF OPERATIONS

Article 12

Opening and management of the DCA

1. The ECB shall open and operate at least one DCA for each DCA holder. A DCA shall be identified by means of a unique 34 character account number which will be structured as follows.

▼M8

	Name	Format	Content
Part A	Account type	1 char. exactly	‘C’ for cash account
	Country code of the central bank	2 char. exactly	ISO country code 3166-1
	Currency code	3 char. exactly	EUR
Part B	Account holder	11 char. exactly	BIC Code
Part C	Sub-classification of the account	Up to 17 char.	Free text (alphanu meric) to be provided by the DCA holder

2. No debit balance shall be allowed on DCAs.

3. The DCA shall not hold any funds overnight. At the beginning and end of a business day, there shall be a zero balance on the DCAs. DCA holders shall be deemed to have instructed the ECB to transfer any remaining balance at the end of a business day as defined in Appendix V to the Main PM account referred to in Article 11(1).

4. The DCA shall only be used within the period between the T2S start-of-day and T2S end-of-day as defined in the T2S User Detailed Functional Specifica tions (UDFS).

5. DCAs shall be interest free.

Article 13

Operations that may be carried out through the DCA

Subject to the DCA holder designating the necessary securities account(s), the DCA holder may carry out the following operations through the DCA either on its own behalf or on behalf of its customers:

(a) DCA to PM liquidity transfer orders;

(b) DCA to DCA liquidity transfer orders;

(d) cash transfers between the DCA and the DCA of the ECB in the particular context of paragraphs 8 and 9 of Annex IIIa to Guideline ECB/2012/27.

Article 14

Acceptance and rejection of payment orders

1. Payment orders submitted by DCA holders are deemed accepted by the ECB if:

(a) the payment message complies with the rules established by the T2S 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 x xxxxx 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 DCA holder of any rejection of a payment order, as specified in Appendix I.

3. The T2S Platform determines the timestamp for the processing of payment orders on the basis of the time when it receives and accepts the payment order.

▼M8

Article 15

Reservation and blocking of liquidity

1. Participants may reserve or block liquidity on their DCA. This does not constitute a settlement guarantee in favour of any third party.

2. By requesting to reserve or block an amount of liquidity, a participant instructs the ECB to decrease the available liquidity by this amount.

3. A reservation request is an instruction by which, if the available liquidity is equal to or higher than the amount to be reserved, the reservation is processed. If the available liquidity is lower, it is reserved and the shortfall may be met by incoming liquidity until the full amount of the reservation is available.

4. A blocking request is an instruction by which, if the available liquidity is equal to or higher than the amount to be blocked, the blocking request is processed. If the available liquidity is lower, no amount is blocked and the blocking request is resubmitted, until the full amount of the blocking request can be met by available liquidity.

5. The participant may at any time during the business day on which a request to reserve or block liquidity has been processed, instruct the ECB to cancel the reservation or blocking. Partial cancelation shall not be permitted.

6. All requests for reservation or blocking of liquidity under this article shall expire at the end of the business day.

Article 16

Moment of entry, moment of irrevocability

1. For the purposes of the first sentence of Article 3(1) and Article 5 of Directive 98/26/EC, and the third sentence of Section 116, Section 96(2), Section 82 and Section 340(3) of the German Insolvency Code (Insolvenzordnung) and the last sentence of Section 46(2) of the KWG, DCA to DCA liquidity transfer orders or DCA to PM liquidity transfer orders are deemed entered into TARGET2-ECB and are irrevocable at the moment that the relevant DCA holder's DCA is debited. PM to DCA liquidity transfer orders are governed by the Harmonised Conditions for the Opening and Operation of a PM account in TARGET2 applicable to the TARGET2 component system from which they originate.

2. For the purposes of the first sentence of Article 3(1) and Article 5 of Directive 98/26/EC, and the third sentence of Section 116, Section 96(2), Section 82 and Section 340(3) of the German Insolvency Code (Insolvenzordnung) and the last sentence of Section 46(2) of the KWG, and for all transactions settling on DCAs and which are subject to matching of two separate transfer orders, such transfer orders are deemed entered into TARGET2-ECB and are irrevocable at the moment that the relevant DCA holder's DCA is debited.

3. The rules provided for in paragraph 2 shall be replaced by the rules below two weeks after the Governing Council of the ECB has determined that an agreement has been signed between the Eurosystem CBs and the Connected NCBs, on the one hand, and all CSDs participating in T2S at the date of such agreement, on the other hand, on the provision of information and liability.

(a) For all transactions settling on DCAs and which are subject to matching of two separate transfer orders, such transfer orders are deemed entered into TARGET2-ECB at the moment at which they have been declared compliant with the technical rules of T2S by the T2S Platform and irrevocable at the moment the transaction has been given the status ‘matched’ on the T2S Platform; or

(b) As an exception to point (a), for transactions involving one participating CSD having a separate matching component where transfer orders are sent directly to that participating CSD to be matched in its separate matching component, transfer orders are deemed entered into TARGET2-ECB at the moment at which they have been declared compliant with the technical rules

▼M8

of T2S by that participating CSD and irrevocable from the moment the transaction has been given the status ‘matched’ on the T2S Platform. A list of CSDs for which this point (b) applies is available on the website of the ECB.

TITLE V

SECURITY REQUIREMENTS, CONTINGENCY ISSUES AND USER INTERFACES

Article 17

Business continuity and contingency procedures

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

Article 18

Security requirements

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

2. DCA holders 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 request that the DCA holders take appropriate measures to prevent a recurrence of such an event.

3. The ECB may impose additional security requirements on all DCA holders and/or on DCA holders that are considered critical by the ECB.

Article 19

User interfaces

1. The DCA holder, or the Main PM account holder acting on its behalf, shall use either one or both of the following means to access that DCA:

(a) direct connection to the T2S Platform in either U2A or A2A modes; or

(b) the TARGET2 ICM in combination with TARGET2 value-added services for T2S.

2. A direct connection to the T2S Platform allows DCA holders:

(a) to access and, when applicable, amend information relating to their accounts;

(b) to manage liquidity and to initiate liquidity transfer orders from the DCAs.

3. The TARGET2 ICM in combination with TARGET2 value-added services for T2S allows the holder of the Main PM account:

(a) to access information relating to their accounts;

(b) to manage liquidity and to initiate liquidity transfer orders to and from the DCAs.

Further technical details relating to the TARGET2 ICM are contained in [insert national provisions implementing Appendix I to Annex II to the Guideline].

TITLE VI

COMPENSATION, LIABILITY REGIME AND EVIDENCE

Article 20

Compensation scheme

In the event that funds remain overnight on a DCA due to a technical malfunc tion of either the SSP or the T2S Platform, the ECB shall offer to compensate the participants concerned in accordance with the special procedure laid down in Appendix II.

▼M8

Article 21

Liability regime

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

2. The ECB shall be liable to its DCA holders 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 DCA holder's direct loss, i.e. the amount of the transaction in question and/or the loss of interest thereon, excluding any conse quential loss.

4. The ECB shall not be liable:

(a) to the extent that the loss is caused by the DCA holder; or

(b) if the loss arises out of external events beyond the ECB's reasonable control

(force majeure).

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

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

Article 22

Evidence

1. Unless otherwise provided in these Conditions, all payment and payment processing-related messages in relation to the DCAs, such as confirmations of debits or credits, or statement messages, between the ECB and the DCA holders shall be made through the T2S network service provider.

2. Electronic or written records of the messages retained by the ECB or by the T2S network service provider 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 T2S network service provider shall be accepted as a means of evidence, regardless of the form of the original message.

3. If a DCA holder's connection to the T2S network service provider fails, the DCA holder shall use an alternative means of transmission of messages agreed with the ECB. 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.

▼M8

4. The ECB shall keep complete records of payment orders submitted and payments received by DCA holders for a period of 10 years from the time at which such payment orders are submitted and payments are received, provided that such complete records shall cover a minimum of five years for any DCA holder in TARGET2 that is subject to continuous vigilance pursuant to restrictive measures adopted by the Council of the European Union or Member States, or more if required by specific regulations.

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

TITLE VII

TERMINATION AND CLOSURE OF DCAS

Article 23

Duration and ordinary termination of DCAs

1. Without prejudice to Article 24, a DCA in TARGET2-ECB is opened for an indefinite period of time.

2. A DCA holder may terminate its DCA 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 DCA holder's DCA in TARGET2-ECB at any time giving three months' notice thereof, unless it agrees a different notice period with that DCA holder.

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

5. On termination of the DCA, it shall be closed in accordance with Article 25.

Article 24

Suspension and extraordinary termination of participation

1. A DCA holder'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 DCA holder no longer meets the access criteria laid down in Article 5.

2. The ECB may terminate without prior notice or suspend the DCA holder's participation in TARGET2-ECB if:

(a) one or more events of default (other than those referred to in paragraph 1) occur;

(b) the DCA holder is in material breach of these Conditions;

(d) the DCA holder is excluded from, or otherwise ceases to be a member of, a T2S Closed Group of Users (CGU); and/or

(e) any other event related to the DCA holder occurs which, in the ECB's assessment, would threaten the overall stability, soundness and safety of TARGET2-E CB reference or of any other TARGET2 component system, or 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.

▼M8

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 points (a) to (c).

4. (a) In the event that the ECB suspends or terminates a DCA holder's participation in TARGET2-ECB under paragraph 1 or 2, the ECB shall immediately inform that DCA holder, other CBs and the other participants of such suspension or termination by means of an ICM broadcast message or a T2S broadcast message depending on which technical option provided for in Article 19 the DCA holder uses.

(b) In the event that the ECB is informed by another CB of a suspension or termination of a participant in another TARGET2 component system, the ECB shall immediately inform its participants of such suspension or termination by means of an ICM broadcast message or of a T2S broadcast message depending on which technical option provided for in Article 19 the DCA holder uses.

(c) Once such an ICM broadcast message (in the case of PM account holders) or T2S broadcast message (in the case of DCA holders) has been received by the participants, such participants shall be deemed informed of the termination/suspension of a DCA holder'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 or of the T2S broadcast message depending on which technical option provided for in Article 19 the DCA holder uses.

5. Upon termination of a DCA holder's participation, TARGET2-ECB shall not accept any new payment orders to or from that DCA holder.

6. If a DCA holder is suspended from TARGET2-ECB, all its incoming and outgoing payment orders shall only be presented for settlement after they have been explicitly accepted by the suspended DCA holder's CB.

Article 25

Closure of DCAs

1. DCA holders may request the ECB to close their DCAs at any time provided they give the ECB 14 business days' notice thereof.

2. On termination of participation, pursuant to either Article 23 or 24, the ECB shall close the DCA of the DCA holder concerned, after having settled or returned any unsettled payment orders and made use of its rights of pledge and set-off under Article 26.

TITLE VIII

FINAL PROVISIONS

Article 26

The ECB's rights of pledge and set-off

1. The ECB shall have a pledge over the DCA holder's existing and future credit balances on its DCAs, 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 24(1); or

(b) any other event of default or event referred to in Article 24(2) that has led to the termination or suspension of the DCA holder's participation, notwith standing the commencement of any insolvency proceedings in respect of a DCA holder and notwithstanding any assignment, judicial or other atta chment or other disposition of or in respect of the DCA holder's rights;

▼M8

all obligations of the DCA holder shall be automatically and immediately acce lerated, 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 DCA holder 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 DCA holder notice of any set-off pursuant to paragraph 4 after such set-off has taken place.

4. The ECB may without prior notice debit any DCA holder's DCA by any amount which the DCA holder owes the ECB resulting from the legal relati onship between the DCA holder and the ECB.

Article 27

Confidentiality

1. The ECB shall keep confidential all sensitive or secret information, inclu ding when such information relates to payment, technical or organisational infor mation belonging to the DCA holder or the DCA holder's customers, unless the DCA holder or its customer has given its written consent to disclose.

2. By derogation from paragraph 1, the DCA holder agrees that the ECB may disclose payment order, technical or organisational information regarding the DCA holder, other DCAs held by DCA holders of the same group, or the DCA holder's customers obtained in the course of the operation of TARGET2- ECB to 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 DCA holder's or its group's exposure, or to supervisory and oversight authorities of Member States and the Union 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. The ECB shall not be liable for the financial and commercial consequences of such disclosure.

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

4. Information relating to the operation of TARGET2-ECB to which DCA holders have had access, may only be used for the purposes laid down in these Conditions. DCA holders shall keep such information confidential, unless the ECB has explicitly given its written consent to disclose. DCA holders 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. The ECB shall be authorised, in order to settle payment orders, to process and transfer the necessary data to the T2S network service provider.

Article 28

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

1. DCA holders shall be deemed to be aware of, and shall comply with, all obligations on them relating to legislation on data protection, 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 payment orders debited or credited on their DCAs. Prior to entering into the contractual relati onship with its T2S network service provider, DCA holders shall acquaint them selves with its data retrieval policy.

▼M8

2. DCA holders 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 DCA holders' participation in TARGET2-ECB.

3. DCA holders, when acting as the payment service provider of x xxxxx or payee, shall comply with all requirements resulting from administrative or restric tive measures imposed pursuant to Articles 75 or 215 of the Treaty 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 DCA holder that is x xxxxx:

(i) the DCA holder 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;

(ii) the DCA holder shall not enter any DCA to PM liquidity transfer order or DCA to DCA liquidity transfer order 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;

(b) when the ECB is a payment service provider of a DCA holder that is a payee, the DCA holder 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 ascribed to them in the applicable admini strative or restrictive measures.

Article 29

Notices

1. 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 the T2S network service provider. Notices to the ECB shall be submitted to the Director-General of the ECB's Directorate-General Payment Systems and Market Infrastructure, Xxxxxxxxxxxxxxxx 00, 00000 Xxxxxxxxx xx Xxxx, Xxxxxxx, or to the BIC address of the ECB. Notices to the DCA holder shall be sent to it at the address, fax number or its BIC address as the DCA holder may from time to time notify to the ECB.

3. All notices shall be given in English.

4. DCA holders shall be bound by all forms and documents of the ECB that the DCA holders 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 10(5), which were submitted in compliance with paragraphs 1 and

2 and which the ECB reasonably believes to have received from the DCA holders, their employees or agents.

Article 30

Contractual relationship with T2S network service provider

1. Each DCA holder may enter into a separate agreement with a T2S network service provider regarding the services to be provided in relation to the DCA holder's use of the DCA. The legal relationship between a DCA holder and the T2S network service provider shall be exclusively governed by the terms and conditions of their separate agreement.

▼M8

2. The services to be provided by the T2S network service provider shall not form part of the services to be performed by the ECB in respect of TARGET2.

3. The ECB shall not be liable for any acts, errors or omissions of the T2S network service provider (including its directors, staff and subcontractors), or for any acts, errors or omissions of third parties selected by DCA holders to gain access to the T2S network service provider's network.

Article 31

Amendment procedure

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

Article 32

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 DCA holders 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 DCA holders in TARGET2-ECB.

Article 33

Governing law, jurisdiction and place of performance

1. The bilateral relationship between the ECB and DCA holders in TARGET2-ECB shall be governed by German law.

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

Article 34

Severability

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

Article 35

Entry into force and binding nature

1. These Conditions become effective from 22 June 2015.

2. By requesting a DCA in TARGET2-ECB, applying entities automatically agree to these Conditions between themselves and in relation to the ECB.

▼M8

Appendix I

PARAMETERS OF THE DEDICATED CASH ACCOUNTS — TECHNICAL SPECIFICATIONS

In addition to the Conditions, the following rules shall apply to the interaction with the T2S Platform:

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

(1) T2S uses the services of a T2S network service provider for the exchange of messages. Each DCA holder using a direct connection shall have a connection to at least one T2S network service provider's secure IP network.

(2) Each DCA holder shall pass a series of tests to prove its technical and operational competence before it may participate in TARGET2-ECB.

(3) For the submission of liquidity transfer orders in the DCA the services of the T2S network service providers shall be used. Liquidity transfer orders shall be directly addressed to the T2S DN and must contain the follo wing information:

(a) in the case of liquidity transfers between two DCAs, the unique 34 character account numbers of both the sending and the receiving DCA holder; or

(b) in the case of liquidity transfers from a DCA to a PM account, the unique 34 character account number of the sending DCA holder and the account number of the receiving PM account.

(4) For the exchange of information with the T2S Platform either A2A or U2A modes may be used. The security of the message exchange between DCA and the T2S Platform shall rely on the Public Key Infrastructure (PKI) service offered by a T2S network service provider. Information on the PKI service is available in the documentation provided by such T2S network service provider.

(5) DCA holders shall comply with the ISO20022 message structure and field specifications. All messages shall include a Business Application Header (BAH). Message structure, field specifications and BAHs are defined in the ISO documentation, under the restrictions set out for T2S, as described in Chapter 3.3.3 Cash Management (camt) of the T2S UDFS.

(6) Field contents shall be validated at the level of the T2S Platform in accordance with the T2S UDFS requirements.

2. Message types

The following system message types are processed, subject to subscription:

Message Type	Description
(camt.003)	GetAccount
(camt.004)	ReturnAccount
(camt.005)	GetTransaction
(camt.006)	ReturnTransaction
(camt.009)	GetLimit
(camt.010)	ReturnLimit
(camt.011)	ModifyLimit

▼M8

Message Type	Description
(camt.012)	DeleteLimit
(camt.018)	GetBusinessDayInformation
(camt.019)	ReturnBusinessDayInformation
(camt.024)	ModifyStandingOrder
(camt.025)	Receipt
(camt.050)	LiquidityCreditTransfer
(camt.051)	LiquidityDebitTransfer
(camt.052)	BankToCustomerAccountReport
(camt.053)	BankToCustomerStatement
(camt.054)	BankToCustomerDebitCreditNotification
(camt.064)	LimitUtilisationJournalQuery
(camt.065)	LimitUtilisationJournalReport
(camt.066)	IntraBalanceMovementInstruction
(camt.067)	IntraBalanceMovementStatusAdvice
(camt.068)	IntraBalanceMovementConfirmation
(camt.069)	GetStandingOrder
(camt.070)	ReturnStandingOrder
(camt.071)	DeleteStandingOrder
(camt.072)	IntraBalanceMovementModificationRequest
(camt.073)	IntraBalanceMovementModificationRequest- StatusAdvice
(camt.074)	IntraBalanceMovementCancellationRequest
(camt.075)	IntraBalanceMovementCancellationRequest- StatusAdvice
(camt.078)	IntraBalanceMovementQuery
(camt.079)	IntraBalanceMovementQueryResponse
(camt.080)	IntraBalanceModificationQuery
(camt.081)	IntraBalanceModificationReport
(camt.082)	IntraBalanceCancellationQuery
(camt.083)	IntraBalanceCancellationReport
(camt.084)	IntraBalanceMovementPostingReport
(camt.085)	IntraBalanceMovementPendingReport

3. Double-entry check

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

(2) The following parameters shall be checked:

— Order Reference (End to End Id);

▼M8

— Debit and Credit Account (DCA or PM account); and

— instructed Xxxxxx.

(3) If all the fields described in point (2) in a newly submitted liquidity transfer order are identical to those in a liquidity transfer order which has been accepted but not yet settled or a liquidity transfer order that has been settled within the past three business days, the newly submitted liquidity transfer order shall be rejected.

4. Error codes

If a liquidity transfer order is rejected on grounds of non-compliance with the fields in paragraph 3(2), the DCA holder shall receive a status advice message [camt.025], as described in Chapter 4.1 of the T2S UDFS.

5. Settlement triggers

(1) For immediate liquidity transfer orders, no specific XML tag is required;

(2) Predefined liquidity transfer orders and standing liquidity transfer orders may be triggered by a specific time or event on the day of settlement:

— for settlement at a specific time, the XML tag ‘Time(/ExctnTp/Tm/)’ shall be used;

— for settlement upon occurrence of a specific event, the XML tag ‘(EventType/ExctnTp/Evt/)’ shall be used.

(3) The validity period for standing liquidity transfer orders shall be set by the following XML tags: ‘FromDate/VldtyPrd/FrDt/’ and ‘ToDate/Vldty Prd/XxXx/’.

6. Settlement of liquidity transfer orders

Liquidity transfer orders are not recycled, queued or offset.

The different statuses for liquidity transfer orders are described in Chapter

1.6.4 of the T2S UDFS.

7. Use of the U2A and A2A mode

(1) The U2A and A2A modes may be used for obtaining information and managing liquidity. The T2S network service providers' networks shall be the underlying technical communications networks for exchanging information and running control measures. The following modes shall be available for use by DCA holders:

(a) Application-to-application mode (A2A)

In A2A, information and messages are transferred between the T2S Platform and the DCA holder's internal application. The DCA holder therefore has to ensure that an appropriate application is available for the exchange of XML messages (requests and responses).

(b) User-to-application mode (U2A)

U2A permits direct communication between a DCA holder and the T2S GUI. The information is displayed in a browser running on a PC system. For U2A access the IT infrastructure has to be able to support cookies and JavaScript. Further details are described in the T2S User Handbook.

(2) Static data shall be available to view in U2A mode. The screens shall be offered in English only.

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

(4) Access rights to the U2A and A2A mode shall be granted by using T2S GUI.

(5) The ‘Non Repudiation of Origin’ (NRO) signature allows the recipient of a message to prove that such message has been issued and has not been altered.

▼M8

(6) If a DCA holder has technical problems and is unable to submit any liquidity transfer order, it may contact its central bank which will on a best efforts basis act on behalf of the DCA holder.

8. Relevant documentation

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

▼M8

Appendix II

TARGET2 COMPENSATION SCHEME IN RELATION TO THE OPENING AND THE OPERATION OF THE DCA

1. General principles

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

(c) Compensation under the TARGET2 compensation scheme shall be the only compensation procedure offered in the event of a technical malfunc tion of the TARGET2. DCA holders may, however, use other legal means to claim for losses. If a DCA holder accepts a compensation offer under the TARGET2 compensation scheme, this shall constitute the DCA holder's irrevocable agreement that it thereby waives all claims in relation to the payment orders concerning which it accepts compensation (inclu ding any claims for consequential loss) it may have against any CB, and that the receipt by it of the corresponding compensation payment consti tutes full and final settlement of all such claims. The DCA holder 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 the TARGET2.

2. Conditions for compensation offers

(a) X xxxxx may submit a claim for an administration fee and interest compensation if, due to a technical malfunction of TARGET2, a liquidity transfer order was not settled on the business day on which it was accep ted.

(b) A payee may submit a claim for an administration fee if, due to a technical malfunction of TARGET2, it did not receive a payment that it was expecting to receive on a particular business day. The payee may also submit a claim for interest compensation if one or more of the following conditions are met:

(i) in the case of participants that have access to the marginal lending facility: due to a technical malfunction of TARGET2, a payee had recourse to the marginal lending facility; and/or

(ii) in the case of all participants: it was technically impossible to have recourse to the money market or such refinancing was impossible on other, objectively reasonable grounds.

3. Calculation of compensation

(a) With respect to a compensation offer for x xxxxx:

▼M8

the date on which the payment order was or could have been succe ssfully settled. Any proceeds made by placing funds resulting from non-settled payment orders on deposit with the Eurosystem shall be deducted from the amount of any compensation; and

(iii) no interest compensation shall be payable if and in so far as funds resulting from non-settled payment orders were placed in the market or used to fulfil minimum reserve requirements.

(b) With respect to a compensation offer for a payee:

(i) the administration fee shall be EUR 50 for the first non-settled payment order, EUR 25 for each of the next four such payment orders and EUR 12,50 for each further such payment order. The admini stration fee shall be calculated separately in relation to each payer;

(ii) the method set out in point (a)(ii) for calculating interest compensa tion shall apply except that interest compensation shall be payable at a rate equal to the difference between the marginal lending rate and the reference rate, and shall be calculated on the amount of any recourse to the marginal lending facility occurring as a result of the technical malfunction of TARGET2.

4. Procedural rules

(b) Within four weeks of a technical malfunction of TARGET2, DCA holders shall submit their claim forms to the ECB. Any additional information and evidence requested by the ECB shall be supplied within two weeks of such request being made.

(c) The ECB shall review the claims and forward them to the ECB. Unless otherwise decided by the ECB's Governing Council and communicated to the DCA holders, all received claims shall be assessed no later than 14 weeks after the technical malfunction of TARGET2 occurs.

(d) The ECB shall communicate the result of the assessment referred to in point (c) to the relevant DCA holders. If the assessment entails a compen sation offer, the DCA holders concerned shall, within four weeks of the communication of such offer, either accept or reject it, in respect of each payment or payment order comprised within each claim, by signing a stan dard letter of acceptance (in the form available on the website of the ECB (see xxx.xxx.xxx). If such letter has not been received by the ECB within four weeks, the DCA holders concerned shall be deemed to have rejected the compensation offer.

(e) The ECB shall make compensation payments on receipt of a DCA holder's letter of acceptance of compensation. No interest shall be payable on any compensation payment.

▼M8

Appendix III

TERMS OF REFERENCE FOR CAPACITY AND COUNTRY OPINIONS

TERMS OF REFERENCE FOR CAPACITY OPINIONS FOR DCA HOLDERS IN TARGET2

The European Central Bank Xxxxxxxxxxxxxxxx 00

60314 Frankfurt am Main Germany

Participation in the [name of the system]

[location] [date]

Dear Sir or Madam,

We have been asked to provide this Opinion as [in-house or external] legal advisers to [specify name of DCA holder or branch of DCA holder] in respect of issues arising under the laws of [jurisdiction in which the DCA holder is established; hereinafter the ‘jurisdiction’] in connection with the participation of [specify name of DCA holder] (hereinafter the ‘DCA holder’) in the TARGET2-ECB (hereinafter the ‘System’).

This Opinion is confined to the laws of [jurisdiction] as they exist as on the date of this Opinion. We have made no investigation of the laws of any other juris diction as a basis for this Opinion, and do not express or imply any opinion in this regard. Each of the statements and opinions presented below applies with equal accuracy and validity under the laws of [jurisdiction], whether or not the DCA holder acts through its head office or one or more branches established inside or outside of [jurisdiction] in submitting liquidity transfer orders and receiving liquidity transfers.

I. DOCUMENTS EXAMINED

For the purposes of this Opinion, we have examined:

(1) a certified copy of the [specify relevant constitutional documents] of the DCA holder such as is/are in effect on the date hereof;

(2) [if applicable] an extract from the [specify relevant company register] and [if applicable] [register of credit institutions or analogous register];

(3) [to the extent applicable] a copy of the DCA holder's licence or other proof of authorisation to provide banking, investment, funds transfer or other financial services in [jurisdiction];

(4) [if applicable] a copy of a resolution adopted by the board of directors or the relevant governing body of the DCA holder on [insert date], [insert year], evidencing the DCA holder's agreement to adhere to the System Documents, as defined below; and

and all other documents relating to the DCA holder's constitution, powers, and authorisations necessary or appropriate for the provision of this Opinion (hereinafter the ‘DCA holder's Documents’).

For the purposes of this Opinion, we have also examined:

▼M8

(1) the terms and conditions for the Opening and Operation of a Dedicated Cash Account in TARGET2-ECB (hereinafter the ‘Rules’); and

(2) […].

The Rules and the […] shall be referred to hereinafter as the ‘System Docu ments’ (and collectively with the DCA holder's Documents as the ‘Docu ments’).

II. ASSUMPTIONS

For the purposes of this Opinion we have assumed in relation to the Docu ments that:

(1) the System Documents with which we have been provided are originals or true copies;

(2) the terms of the System Documents and the rights and obligations created by them are valid and legally binding under the laws of [insert reference to the Member State of the System] by which they are expressed to be governed, and the choice of the laws of [insert reference to the Member State of the System] to govern the System Documents is recognised by the laws of [insert reference to the Member State of the System];

(3) the DCA holder's Documents are within the capacity and power of and have been validly authorised, adopted or executed and, where necessary, delivered by the relevant parties; and

(4) the DCA holder's Documents are binding on the parties to which they are addressed, and there has been no breach of any of their terms.

III. OPINIONS REGARDING THE DCA HOLDER

A. The DCA holder is a corporation duly established and registered or otherwise duly incorporated or organised under the laws of [jurisdiction].

B. The DCA holder has all the requisite corporate powers to execute and perform the rights and obligations under the System Documents to which it is party.

C. The adoption or execution and the performance by the DCA holder of the rights and obligations under the System Documents to which the DCA holder is party will not in any way breach any provision of the laws or regulations of [jurisdiction] applicable to the DCA holder or the DCA holder Documents.

D. No additional authorisations, approvals, consents, filings, registrations, notarisations or other certifications of or with any court or governmental, judicial or public authority that is competent in [jurisdiction] are required by the DCA holder in connection with the adoption, validity or enfor ceability of any of the System Documents or the execution or perfor mance of the rights and obligations thereunder.

E. The DCA holder has taken all necessary corporate action and other steps necessary under the laws of [jurisdiction] to ensure that its obligations under the System Documents are legal, valid and binding.

This Opinion is stated as of its date and is addressed solely to the ECB and the DCA holder. No other persons may rely on this Opinion, and the contents of this Opinion may not be disclosed to persons other than its intended recipients and their legal counsel without our prior written consent, with the exception of the European Central Bank and the national central banks of the European System of Central Banks [and [the national central bank/relevant regulatory authorities] of [jurisdiction]].

Yours faithfully,

[signature]

▼M8

TERMS OF REFERENCE FOR COUNTRY OPINIONS FOR NON-EEA DCA HOLDERS IN TARGET2

The European Central Bank Xxxxxxxxxxxxxxxx 00

60314 Frankfurt am Main Germany

TARGET2-ECB

[location], [date]

Dear Sir or Madam,

We have been asked as [external] legal advisers to [specify name of DCA holder or branch of DCA holder] (the ‘DCA holder’) in respect of issues arising under the laws of [jurisdiction in which the DCA holder is established; hereinafter the ‘jurisdiction’] to provide this Opinion under the laws of [jurisdiction] in connec tion with the participation of the DCA holder in a system which is a component of TARGET2 (hereinafter the ‘System’). References herein to the laws of [juris diction] include all applicable regulations of [jurisdiction]. We express an opinion herein under the law of [jurisdiction], with particular regard to the DCA holder established outside [insert reference to the Member State of the System] in relation to rights and obligations arising from participation in the System, as presented in the System Documents defined below.

1. DOCUMENTS EXAMINED

For the purposes of this Opinion, we have examined the documents listed below and such other documents as we have deemed necessary or appro priate:

(1) the terms and conditions for the Opening and Operation of a Dedi cated Cash Account in TARGET2] for the System dated [insert date] (hereinafter the ‘Rules’); and

(2) any other document governing the System and/or the relationship between the DCA holder and other participants in the System, and between the participants in the System and the ECB.

The Rules and the [.] shall be referred to hereinafter as the ‘System Documents’.

2. ASSUMPTIONS

For the purposes of this Opinion we have assumed in relation to the System Documents that:

(1) the System Documents are within the capacity and power of and have been validly authorised, adopted or executed and, where necessary, delivered by the relevant parties;

(2) the terms of the System Documents and the rights and obligations created by them are valid and legally binding under the laws of [insert reference to the Member State of the System], by which they are expressed to be governed, and the choice of the laws of [insert reference to the Member State of the System] to govern the System Documents is recognised by the laws of [insert reference to the Member State of the System];

(3) the documents submitted to us in copy or as specimens conform to the originals.

▼M8

3. OPINION

Based on and subject to the foregoing, and subject in each case to the points set out below, we are of the opinion that:

3.1. Country-specific legal aspects [to the extent applicable]

The following characteristics of the legislation of [jurisdiction] are consis tent with and in no way set aside the obligations of the DCA holder arising out of the System Documents: [list of country-specific legal aspects].

3.2. General insolvency issues

3.2.a. Types of insolvency proceedings

The only types of insolvency proceedings (including composition or reha bilitation) which, for the purpose of this Opinion, shall include all procee dings in respect of the DCA holder's assets or any branch it may have in [jurisdiction] to which the DCA holder may become subject in [jurisdic tion], are the following: [list proceedings in original language and English translation] (together collectively referred to as ‘Insolvency Proceedings’).

In addition to Insolvency Proceedings, the DCA holder, any of its assets, or any branch it may have in [jurisdiction] may become subject in [juris diction] to [list any applicable moratorium, receivership, or any other proceedings as a result of which payment orders to and/or from the DCA holder may be suspended, or limitations can be imposed in relation to such payment orders, or similar proceedings in original language and English translation] (hereinafter collectively referred to as ‘Proceedings’).

3.2.b. Insolvency treaties

3.3. Enforceability of System Documents

In particular, we are of the opinion that:

3.3.a. Processing of liquidity transfer orders

The provisions on processing of liquidity transfer orders [list of sections] of the Rules are valid and enforceable. In particular, all liquidity transfer orders processed pursuant to such sections will be valid, binding and will be enforceable under the laws of [jurisdiction]. The provision of the Rules which specifies the precise point in time at which liquidity transfer orders become enforceable and irrevocable ([add section of the Rules]) is valid, binding and enforceable under the laws of [jurisdiction].

3.3.b. Authority of the ECB to perform its functions

The opening of Insolvency Proceedings or Proceedings in respect of the DCA holder will not affect the authority and powers of the ECB arising out of the System Documents. [Specify [to the extent applicable] that: the same opinion is also applicable in respect of any other entity which provides the DCA holders with services directly and necessarily required for participation in the System, e.g. network service providers].

3.3.c. Remedies in the event of default

[Where applicable to the DCA holder, the provisions contained in the Rules regarding accelerated performance of claims which have not yet matured, the set-off of claims for using the deposits of the DCA holder, the enforcement of a pledge, suspension and termination of participation,

▼M8

claims for default interest, and termination of agreements and transactions are valid and enforceable under the laws of [jurisdiction].]

3.3.d. Suspension and termination

Where applicable to the DCA holder, the provisions contained in the Rules (in respect of suspension and termination of the DCA holder's participation in the System on the opening of Insolvency Proceedings or Proceedings or other events of default, as defined in the System Docu ments, or if the DCA holder represents any kind of systemic risk or has serious operational problems) are valid and enforceable under the laws of [jurisdiction].

3.3.e. Assignment of rights and obligations

The rights and obligations of the DCA holder cannot be assigned, altered or otherwise transferred by the DCA holder to third parties without the prior written consent of the ECB.

3.3.f. Choice of governing law and jurisdiction

The provisions contained in the Rules, and in particular in respect of the governing law, the resolution of a dispute, competent courts, and service of process are valid and enforceable under the laws of [jurisdiction].

3.4. Voidable preferences

We are of the opinion that no obligation arising out of the System Docu ments, the performance thereof, or compliance therewith prior to the opening of any Insolvency Proceedings or Proceedings in respect of the DCA holder may be set aside in any such proceedings as a preference, voidable transaction or otherwise under the laws of [jurisdiction].

In particular, and without limitation to the foregoing, we express this opinion in respect of any transfer orders submitted by any participant in the System. In particular, we are of the opinion that the provisions of the Rules establishing the enforceability and irrevocability of transfer orders will be valid and enforceable and that a transfer order submitted by any participant and processed pursuant to the Rules may not be set aside in any Insolvency Proceedings or Proceedings as a preference, voidable transaction or otherwise under the laws of [jurisdiction].

3.5. Attachment

If a creditor of the DCA holder seeks an attachment order (including any freezing order, order for seizure or any other public or private law proce dure that is intended to protect the public interest or the rights of the DCA holder's creditors) — hereinafter referred to as an ‘Attachment’ — under the laws of [jurisdiction] from a court or governmental, judicial or public authority that is competent in [jurisdiction], we are of the opinion that [insert the analysis and discussion].

3.6. Collateral [if applicable]

3.6.a. Assignment of rights or deposit of assets for collateral purposes, pledge and/or repo

3.6.b. Priority of assignees', pledgees' or repo purchasers' interest over that of other claimants

In the event of Insolvency Proceedings or Proceedings in respect of the DCA holder, the rights or assets assigned for collateral purposes, or pledged by the DCA holder in favour of the ECB or other participants in the System, will rank in priority of payment above the claims of all other creditors of the DCA holder and will not be subject to priority or preferential creditors.

▼M8

3.6.c. Enforcing title to security

Even in the event of Insolvency Proceedings or Proceedings in respect of the DCA holder, other participants in the System and the ECB as [xxxxxx nees, pledgees or repo purchasers as applicable] will still be free to enforce and collect the DCA holder's rights or assets through the action of the ECB pursuant to the Rules.

3.6.d. Form and registration requirements

There are no form requirements for the assignment for collateral purposes of, or the creation and enforcement of a pledge or repo over the DCA holder's rights or assets and it is not necessary for the assignment for collateral purposes, pledge or repo, as applicable, or any particulars of such assignment, pledge or repo, as applicable, to be registered or filed with any court or governmental, judicial or public authority that is compe tent in [jurisdiction].

3.7. Branches [to the extent applicable]

3.7.a. Opinion applies to action through branches

Each of the statements and opinions presented above with regard to the DCA holder applies with equal accuracy and validity under the laws of [jurisdiction] in situations where the DCA holder acts through its one or more of its branches established outside [jurisdiction].

3.7.b. Conformity with law

Neither the execution and performance of the rights and obligations under the System Documents nor the submission, transmission or receipt of payment orders by a branch of the DCA holder will in any respect breach the laws of [jurisdiction].

3.7.c. Required authorisations

Neither the execution and performance of the rights and obligations under the System Documents nor the submission, transmission or receipt of payment orders by a branch of a DCA holder will require any additional authorisations, approvals, consents, filings, registrations, notarisations or other certifications of or with any court or governmental, judicial or public authority that is competent in [jurisdiction].

Yours faithfully,

[signature]

▼M8

Appendix IV

BUSINESS CONTINUITY AND CONTINGENCY PROCEDURES

1. General provisions

(a) This Appendix sets out the arrangements between the ECB and DCA holders, if one or more components of TARGET2 or a network service provider fail or are affected by an abnormal external event, or if the failure affects any DCA holder.

(b) All references to specific times in this Appendix are to the local time at the seat of the ECB, i.e. Central European Time (CET) (1).

2. Measures of business continuity

(a) In the event that an abnormal external event occurs and/or there is a failure of the SSP, the T2S Platform or a network service provider which affects the normal operation of TARGET2, the ECB shall be entitled to adopt business continuity measures.

(b) The following main business continuity and contingency measures shall be available for the SSP:

(i) relocating the operation of the SSP to an alternative site;

(ii) changing the SSP's operating hours; and

(iii) initiating contingency processing of very critical and critical payment orders, as defined in paragraph 6(c) and (d) of Appendix IV to Xxxxx XX.

(i) relocating the operation of the T2S Platform to an alternative site;

(ii) rescheduling events in the T2S Settlement day.

(d) In relation to business continuity processing measures, the ECB shall have full discretion regarding what measures are adopted.

3. Incident communication

(a) Information about a failure of the TARGET2 and/or an abnormal external event shall be communicated to DCA holders through the domestic communication channels, the ICM, the T2S GUI and the T2S-information system as defined in the T2S UDFS. In particular, communications to DCA holders shall include the following information:

(i) a description of the event;

(ii) the anticipated delay in processing (if known);

(iii) information on the measures already taken.

(b) In addition, the ECB may notify DCA holders of any other existing or anticipated event which has the potential to affect the normal operation of TARGET2.

4. Relocation of the operation of the SSP and/or T2S Platform to an alter native site

(a) In the event that any of the events referred to in paragraph 2(a) occurs, the operation of the SSP and/or the T2S Platform may be relocated to an alternative site, either within the same region or in another region.

(b) In the event that the operation of the T2S Platform is relocated to another region, the DCA holders shall (i) refrain from sending new instructions to the T2S Platform and (ii) at the request of the ECB perform a reconcilia tion and resubmit any instructions identified as missing submitted

(1) CET takes into account the change to Central European Summer Time.

▼M8

within a maximum of five minutes prior to the time of failure or the occurrence of the abnormal external event and provide the ECB with all relevant information in this respect.

5. Change of operating hours

(a) The daytime processing of TARGET2 may be extended or the opening time of a new business day may be delayed. During any extended opera ting time of TARGET2, payment orders shall be processed in accordance with this Appendix.

(b) TARGET2 daytime processing may be extended and the closing time thereby delayed, if a T2S Platform or SSP failure has occurred during the day but has been resolved before 18.00. Such a closing time delay shall in normal circumstances not exceed two hours and shall be announced as early as possible to DCA holders. Once such a delay is announced it may not be withdrawn.

6. Failures linked to DCA holders

(a) In the event that a DCA holder has a problem that prevents it from settling payment orders in TARGET2-ECB, it shall be its responsibility to resolve the problem.

(b) In the event that a DCA holder unexpectedly submits an abnormally high number of messages, which threaten the stability of the T2S Platform, and does not, upon request of the ECB, refrain from such behaviour without delay, the ECB may block from the T2S Platform all further messages submitted by such DCA holder.

7. Other provisions

(a) In the event of a failure of the ECB, some or all of its technical functions in relation to TARGET2-ECB may be performed by other Eurosystem CBs.

(b) The ECB may require that the DCA holders participate in regular or ad hoc testing of business continuity and contingency processing measures, training or any other preventive arrangements, as deemed necessary by the ECB. Any costs incurred by the DCA holders as a result of such testing or other arrangements shall be borne solely by the DCA holders.

▼M8

Appendix V

OPERATING SCHEDULE

1. TARGET2 is open on all days, except Saturdays, Sundays, New Year's Day, Good Friday and Easter Monday (according to the calendar applicable at the seat of the ECB), 1 May, 25 December and 26 December.

2. The reference time for the system is the local time at the seat of the ECB, i.e. CET (1).

3. The current business day is opened during the evening of the previous busi ness day and operates according to the schedule set out in the T2S Scope Defining Set of Documents.

4. The T2S Platform is available for U2A and A2A mode during the whole settlement day, except during the technical maintenance period from 03:00 until 05:00. During the technical maintenance period messages sent using the A2A mode will be queued. It will not be possible to submit messages via the U2A mode.

5. The operating hours may be changed in the event that business continuity measures are adopted in accordance with paragraph 2 of Appendix IV.

6. An overview of the operating hours and significant business events during the day is shown in the following table:

SSP schedule		T2S schedule (applicable to DCAs)
Time	Description	Time	Description
18:45 — 19:00 (1)	Start of day proces sing(sending of GL files shortly after 18:45)	18:45 — 20:00	Start of day: — Change of business date — Deadline for accep tance of CMS data feeds (19:00) — Preparation of the night time settle ment
			Night-time settlement:
			— First Night-time settlement cycle
19:00 — 19:30 (1)	Night-time settlement: provision of liquidity from SF to HAM and PM; from HAM to PM and from PM to DCA.	20:00 — 03:00	— Last Night-time settlement cycle (Sequence X includes the partial settlement of unsettled payment instructions eligible for partial settle ment and that have failed to settle due to a lack of securi ties; Sequence Y includes the reimbursement of multiple liquidity providers at the end of cycle)
	Night-time settlement (NTS1):
	— Start-of-procedure message;
19:30 (1) — 22:00	— Setting aside of liquidity on the basis of standing orders for the nig- ht-time processing

(1) CET takes into account the change to Central European Summer Time.

▼M8

SSP schedule		T2S schedule (applicable to DCAs)
Time	Description	Time	Description
	(ancillary system settlement procedure 6 and T2S)
22:00 — 01:00	Technical mainte xxxxx window (2)	03:00 — 05:00	Technical maintenance window (3)
01:00 — 06:45	Night-time processing (ancillary system settlement procedure 6 and T2S)	05:00 — 18:00	Day trade/Real-time settlement (4): — Real-time settlem- ent preparation (4) — Partial settlement windows at 14:00 and 15:45 (5) (for 15 minutes) — 16:00: DvP cut-off — 16:30: Automatic auto-collateralisa tion reimbursement, followed by the optional cash sweep — 17:40: Cut-off for Bilaterally agreed treasury manage ment operations (BATM) and central bank operations (CBO) cut-off — 17:45: inbound liquidity transfer cut-off Automated cash sweep after 17:45 — 18:00: FOP cut-off
06:45 — 07:00	Business window to prepare daylight operations
07:00 — 18:00	Day trade phase: — 17:00: Cut-off for customer payments — 17:45: Cut-off for liquidity transfers to DCAs — 18:00: Cut-off for interbank paymen- ts and incoming liquidity transfers from DCAs
18:00 — 18:45	— 18:15 (1): Cut-off for the use of stan ding facilities Data needed to update the accoun ting system is available for central banks, shortly after 18:30 — 18:40 (1): Cut-off for use of marginal lending (NCBs only) End-of-day proces sing	18:00 — 18:45	— End of T2S settle ment processing — Recycling and purging — End of day repor ting and statements

▼M8

Notes to table:

(1) Plus 15 minutes on the last day of the reserve maintenance period.

(2) Over a weekend or on a holiday, the technical window will last throughout the weekend or the holiday, i.e., from 22:00 on Friday until 1:00 on Monday or, in the case of a holiday, from 22:00 on the last business day until 1:00 on the next business day.

(3) Over a weekend or on a holiday, the technical window will last throughout the weekend or the holiday, i.e., from 03:00 a.m. on Saturday until 05:00 a.m. on Monday or, in the case of a holiday, from 03:00 a.m. on the holiday until 05:00 a.m. on the next business day.

(4) Real-time settlement preparation and real-time settlement may start before the maintenance window if the last night-time settlement cycle ends before 03:00 am.

(5) Each partial settlement window lasts for 15 minutes. The partial settlement applies to unsettled payment instructions eligible for partial settlement and that have failed to settle due to a lack of securities.

▼M8

Appendix VI

FEE SCHEDULE

Fees for T2S services.

The following fees for T2S services connected with DCAs shall be charged to the Main PM account holders:

Tariff items		Price	Explanation
Settlement services
DCA to DCA transfer orders	liquidity	9 eurocent	per	transfer
Intra-balance movement (i.e. blocking, unblocking, reser vation of liquidity etc.)		6 eurocent	per	transaction
Information services
A2A reports		0,4 eurocent	Per business item in any A2A report generated
A2A queries		0,7 eurocent	Per queried business item in any A2A query generated
U2A queries		10 eurocent	Per executed search function
Messages bundled into a file		0,4 eurocent	Per	message in a file
Transmissions		1,2 eurocent	Per	transmission

Document Metadata

Table of Contents

Free Standard Templates

Tento dokument slúži čisto na potrebu dokumentácie a inštitúcie nenesú nijakú zodpovednosť za jeho obsah

Document Metadata