1.   The following Appendices form an integral part of these Conditions:

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.

1.   TARGET is legally structured as a multiplicity of payment systems composed of all TARGET component systems, each of which is designated as a ‘system’ under the relevant national law implementing Directive 98/26/EC of the European Parleament and of the Council (1). TARGET-ECB is designated as a ‘system’ under § 1(16) of the Kreditwesengesetz (KWG).

2.   TARGET comprises payment systems in euro that settle in central bank money and provide central liquidity management services, real-time gross settlement for payments and services for AS settlement, and enable cash payments in relation to securities settlement and the settlement of instant payments.

3.   TARGET provides:

Each account in TARGET-ECB shall be identified by means of a unique account number made up of the elements described in Appendix I, paragraph 2.

1.   In order to become a participant in TARGET-ECB, an eligible entity as described in Article 4 shall fulfil the following requirements:

2.   Applicants shall apply to the ECB, as a minimum enclosing the following documents/information:

3.   Applicants which are already TARGET participants and apply for a new account as described in: (i) Part III (RTGS-DCA); (ii) Part IV (T2S DCA); (iii) Part V (TIPS DCA); (iv) Part VI (RTGS AS technical account); and/or (v) Part VII (TIPS AS technical account), shall comply with the provisions of paragraphs 1 and 2 to the extent relevant for the new account applied for.

4.   The ECB may also request any additional information it deems necessary to decide on an application to open a TARGET account.

5.   The ECB shall reject the application to participate if:

6.   The ECB shall communicate its decision on the application to become a participant in TARGET-ECBto the applicant participant within one month of the ECB’s receipt of the application. Where the ECB requests additional information pursuant to paragraph 4, 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.

1.   To the extent technically possible, a participant may give access to its TARGET accounts to one or more entities it designates, for the purposes of submitting cash transfer orders and performing other actions.

2.   Cash transfer orders submitted or funds received by the entities designated by a participant as referred to in paragraph 1 shall be deemed to have been submitted or received by that participant itself.

3.   The participant shall be bound by such cash transfer orders and any other action taken by the entity or entities referred to in paragraph 1, regardless of the content of, or any non-compliance with, the contractual or other arrangements between that participant and such entity.

1.   The ECB shall identify billable items according to Appendix VI and shall allocate each of them to the participant from which that billable item originates.

2.   Any fee payable in relation to a cash transfer order submitted by or cash transfer received by an AS, irrespective of whether it uses the RTGS AS settlement procedures or an RTGS DCA, shall be exclusively charged to that AS.

3.   Billable items generated by actions taken by the designated entities referred in Article 7, as well as by central banks acting on behalf of a participant, shall be allocated to the participant.

4.   The ECB shall issue separate invoices to the participant for the relevant services described in: (i) Part III (RTGS-DCA); (ii) Part IV (T2S DCA); (iii) Part V (TIPS DCA); (iv) Part VI (RTGS AS settlement procedures); and (v) Part VII (TIPS AS settlement procedure).

5.   The ECB shall settle each invoice by means of a direct debit of an MCA held by the participant, unless the participant has designated another participant in TARGET (which may be in TARGET-ECB or another component system) as a paying agent and instructed the ECB to debit the MCA of that paying agent. Such an instruction shall not release the participant from its obligation to pay each invoice.

6.   Where a paying agent has been designated, the participant will provide the ECB with evidence that the paying agent has agreed to act in that role.

7.   For the purposes of this Article, each AS shall be treated separately, even if two or more of them are operated by the same legal entity, and irrespective of whether or not the AS has been designated under Directive 98/26/EC. In the case of an AS that has not been designated under Directive 98/26/EC, it shall be identified as an AS by reference to the following criteria: (a) it is a formal arrangement, based on a contractual or legislative instrument, e.g. an agreement among the participants and the system operator; (b) it has multiple membership; (c) it has common rules and standardised arrangements; and (d) is for the purpose of clearing, netting and/or settlement of payments and/or securities between the participants.

1.   Upon the request of the participant the ECB shall create a billing group to allow its members to benefit from the degressive pricing applicable to RTGS DCAs. The billing group may only include RTGS DCA holders belonging to the same banking group, from one or more TARGET component systems.

2.   Upon the request of an RTGS DCA holder the ECB shall add that RTGS DCA holder to or delete it from a billing group which may be in TARGET-ECB or in any other TARGET component system. The RTGS DCA holder shall inform all other members of the billing group of such a request prior to making it.

3.   RTGS DCA holders included in a billing group shall be invoiced individually as set out in Article 8.

1.   The ECB shall offer the services described in Parts II, III, IV, V, VI and VII of these Conditions where a participant has opted for and been granted an account as referred to therein. 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 ECB is the provider of services pursuant to these Conditions. Acts and omissions of the Level 3 NCBs shall be considered as acts and omissions of the ECB, for which it shall assume liability in accordance with Article 21. Participation pursuant to these Conditions shall not create a contractual relationship between participants and the Level 3 NCBs when any of the latter acts in its capacity as a Level 3 NCB. Instructions, messages or information which a participant receives from, or sends to, TARGET in relation to the services provided under these Conditions shall be deemed to be received from, or sent to, ECB.

3.   The participant shall pay to the ECB fees in accordance with Article 8.

4.   The participant shall ensure that it is technically connected to TARGET-ECB in accordance with TARGET operating schedule set out in Appendix V. This obligation may be fulfilled through a designated entity referred to in Article 7.

5.   The participant shall represent and warrant 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.

6.   The participant shall pay any applicable stamp duties or other documentary taxes or duties, if applicable, as well as any other costs the participant incurs in opening, maintaining or closing its TARGET account.

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

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

3.   Up-to-date information on the operational status of each service shall be available on a TARGET Information System (TIS) on a dedicated webpage on the ECB’s website.

4.   The ECB may communicate system relevant messages to participants by means of a broadcast message or, if this means is not available, by any other appropriate means of communication.

5.   Participants shall update in a timely manner existing reference data collection forms and submit new reference data collection forms to the ECB. Participants shall verify the accuracy of information relating to them that is entered into TARGET-ECB by the ECB.

6.   The participant hereby authorises the ECB to communicate to the Level 3 NCBs any information relating to participants which the Level 3 NCBs may need, in accordance with the agreements between the Level 3 NCBs and the Eurosystem CBs governing the provision of the services to be provided by the Level 3 NCBs.

7.   Participants shall inform the ECB without undue delay about any change in their legal capacity and relevant legislative changes affecting issues covered by the country opinion as set out in the terms of reference given in Appendix III.

8.   The ECB may at any time request an update or renewal of the country or capacity opinions referred to in Article 5(1), points (d) and (e).

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

1.   MCAs, DCAs and sub-accounts shall either be remunerated at zero per cent or at the deposit facility rate, whichever is lower.

2.   Overnight balances held on a TIPS AS technical account or on an RTGS AS technical account for AS settlement procedure D, and guarantee funds, including those held on an AS guarantee fund account, shall be remunerated at the deposit facility rate.

1.   Participants shall monitor and manage the liquidity on their accounts in line with the TARGET operating schedule as set out in Appendix V and perform transaction-level reconciliation at least once a day. This obligation may be fulfilled through a designated entity referred to in Article 7.

2.   The participant shall make use of the tools provided by the ECB for the purpose of account reconciliation, in particular the daily statement of account which is made available to each participant. This obligation may be fulfilled through a designated entity referred to in Article 7.

3.   Participants shall immediately inform the ECB in the event that a mismatch occurs in relation to any of their accounts.

1.   The participant may set floor and ceiling amounts on its MCA or DCAs.

2.   The participant may choose to receive a notification if the floor or ceiling amount is breached. In addition, for MCAs or RTGS DCAs the participant may opt for the breach to trigger a rule-based liquidity transfer order.

3.   The settlement of a liquidity transfer order shall not trigger a check of whether the floor or ceiling amount has been breached.

1.   An MCA holder may create one or more account monitoring groups for the purpose of monitoring liquidity on several MCAs or DCAs and will become the leader party for any account monitoring group that it creates.

2.   A participant may add any of its MCAs or DCAs opened within TARGET-ECB or any other TARGET component system to one or more account monitoring groups and thereby become a member of that account monitoring group. A member of an account monitoring group may initiate the removal of its account from that account monitoring group at any time. A participant shall inform the leader party of an account monitoring group prior to adding an account to or removing an account from that account monitoring group.

3.   Only the leader party for an account monitoring group shall be able to view the balances of all accounts included in that account monitoring group.

4.   The leader party may delete the account monitoring group and shall inform the other members of the account monitoring group prior to such deletion.

1.   Cash transfer orders submitted by participants shall be deemed accepted by the ECB if:

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

1.   For the purposes of the first sentence of Articles 3(1) and 5 of Directive 98/26/EC and the third sentence of § 116, § 96(2), § 82 and § 340(3) of the Insolvenzordnung (German Insolvency Code) and the sixth sentence of § 46a(1) of the KWG:

2.   The provisions of paragraph 1 shall not affect any rules of AS that stipulate a moment of entry into the AS and/or irrevocability of transfer orders submitted to it at a point in time earlier than the moment of entry of the respective AS transfer orders in the relevant TARGET component system.

3.   Cash transfer orders included in an algorithm may not be revoked during the period that the algorithm is running.

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

2.   In exceptional circumstances the TARGET operating schedule may be changed, in which case participants will be informed by the ECB.

3.   In exceptional circumstances an AS may make a request to the ECB to modify the TARGET operating schedule.

4.   The Eurosystem provides a Contingency Solution for use if the events described in paragraph 1 occur. Connection to and use of the Contingency Solution shall be mandatory for participants considered by the ECB] to be critical and for participants that settle very critical transactions as set out in Appendix IV. Other participants may, on request, connect to the Contingency Solution.

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

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

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

4.   Participants shall provide the ECB with: (i) permanent access to their attestation of adherence to their chosen NSP’s endpoint security requirements; and (ii) on an annual basis the TARGET self-certification statement as required for the types of accounts that they hold and as published on the ECB’s website.

5.   The ECB shall assess the participant’s self-certification statement(s) on the participant’s level of compliance with each of the requirements set out in the TARGET selfcertification requirements. These requirements are listed in Appendix VII.

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

7.   If the participant refuses to grant permanent access to its attestation of adherence to its chosen NSPs endpoint security requirements or does not provide the TARGET self-certification, the participant’s level of compliance shall be categorised as ‘major non-compliance’.

8.   The ECB shall re-assess compliance of participants on an annual basis.

9.   The ECB may impose the following measures of redress on participants whose level of compliance was assessed as minor or major non-compliance, in increasing order of severity:

10.   Participants allowing access to their TARGET account by third parties as set out in Article 7 and participants having registered addressable BIC holders as set out in Part III, Article 2, shall address the risk stemming from allowing such access in accordance with the security requirements set out in paragraphs 1 to 9.

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 TARGET-ECB. In cases of ordinary negligence, the ECB’s liability shall be limited to the participant’s direct loss, i.e. the amount of the transaction in question and/or the loss of interest thereon, excluding any consequential loss.

3.   The ECB shall not be 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:

5.   Notwithstanding § § 676a, 676b, 676c, 676e and 676g of the Bürgerliches Gesetzbuch (German Civil Code), 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 telecommunications or other network providers or other entities, if this is necessary to meet the ECB’s obligations or is standard market practice. The ECB’s obligation shall be limited to the due selection and commissioning of any such third parties and the ECB’s liability shall be limited accordingly. For the purposes of this paragraph, the Level 3 NCBs shall not be considered as third parties.

1.   Unless otherwise provided in these Conditions, all cash transfer orders and related messages, such as confirmations of debits or credits, or statement messages, between the ECB and participants shall be made through the relevant NSP.

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

3.   If a participant’s connection to the NSP fails, the participant shall use the alternative means of transmission of messages as 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.

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

5.   The ECB’s own books and records 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.

1.   Without prejudice to Article 24, participation in TARGET-ECB shall be for an indefinite period of time.

2.   A participant may terminate any of the following at any time giving 14 business days’ notice thereof, unless it agrees a shorter notice period with the ECB:

3.   The ECB may terminate any of the following at any time giving three months’ notice thereof, unless it agrees a different notice period with the relevant participant:

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

5.   On termination of participation, the ECB shall close all TARGET accounts of the participant concerned in accordance with Article 25.

1.   A participant’s participation in TARGET-ECB shall be immediately terminated without prior notice or suspended if one of the following events of default occurs:

For the purposes of this paragraph, the taking of crisis prevention measures or crisis management measures within the meaning of Directive 2014/59/EU against a participant shall not automatically qualify as the opening of insolvency proceedings.

2.   The ECB may terminate without prior notice or suspend the participant’s participation in TARGET-ECB if:

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) of paragraph 2.

4.   In the event that the ECB suspends or terminates a participant’s participation in TARGET-ECB under paragraphs 1 or 2, the ECB shall without undue delay inform – by means of a broadcast message or, if that is not available, by any other appropriate means of communication – the respective participant, other CBs and participants in all of the TARGET component systems of such suspension or termination. Such message shall be deemed to have been issued by the home CB of the respective participant.

5.   Once a message issued under paragraph 4 has been received by the participants, they shall be deemed informed of the termination/suspension of a participant’s participation in TARGET-ECB or another TARGET component system. The participants shall bear any losses arising from the submission of a cash transfer order to participants whose participation has been suspended or terminated if such cash transfer order was entered into TARGET-ECB after receipt of the message.

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

2.   On the occurrence of:

3.   The ECB shall promptly give the participant 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 participant’s TARGET accounts by any amount which the participant owes the ECB resulting from the legal relationship between the participant and the ECB .

5.   The provisions of this Article shall not create any right, pledge, charge or claim or set-off in respect of the following TARGET accounts used by AS:

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

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

3.   By derogation from paragraph 1, the participant agrees that the ECB may disclose payment, technical or organisational information regarding the participant, participants from the same banking group or the participant's customers, obtained in the course of the operation of TARGET-ECB to:

and provided that in all such cases the disclosure is not in conflict with applicable law.

4.   The ECB shall not be liable for the financial and commercial consequences of disclosure made in accordance with paragraph 3.

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

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

7.   The ECB shall be authorised, in order to settle cash transfer orders, to process and transfer the necessary data to the NSP.

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

2.   Participants authorise 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 TARGET-ECB.

3.   Participants, when acting as the payment service provider of a payer or payee, shall comply with all requirements resulting from administrative or restrictive measures imposed pursuant to Article 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:

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

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 other electronic means if agreed bilaterally, or otherwise in writing. Notices to the ECB shall be submitted to the Director-General of the ECB's Directorate-General Payment Systems and Market Infrastructure, at the European Central Bank, Sonnemannstrasse 22, 60314 Frankfurt am Main, GERMANY or to the BIC address of the ECB, ‘ECBFDEFF’, or to the electronic means bilaterally agreed. Notices to the participant shall be sent to it at the address, facsimile number or other electronic means bilaterally agreedor its 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 sent either physically or by electronic means to the relevant addressee.

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 reference data collection forms, as referred to in Article 5(2), point (a), and information provided under Article 11(5), which were submitted in compliance with paragraphs 1 and 2 and which the ECB reasonably believes to have been received from the participants, their employees or agents.

1.   In order to send to or receive from TARGET instructions and messages, participants shall:

2.   The legal relationship between a participant and the NSP shall be exclusively governed by the terms and conditions of the contract concluded between them.

3.   The services to be provided by the NSP shall not form part of the services to be performed by the ECB in respect of TARGET.

4.   The ECB shall not be liable for any acts, errors or omissions of the NSP (including its directors, staff and subcontractors), or for any acts, errors or omissions of third parties selected by participants to gain access to the NSP’s network.

1.   Participants shall not transfer, pledge or assign any rights, interests, obligations, responsibilities or claims arising from or relating to these Conditions 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 TARGET-ECB.

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

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

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

1.   These Conditions become effective from 21 November 2022.

2.   By requesting to participate in TARGET- ECB, applicant participants automatically agree to these Conditions between themselves and in relation to the ECB.

1.   The ECB shall open and operate at least one MCA for each participant, except where the participant is an AS that only uses RTGS or TIPS AS settlement procedures, in which case the use of an MCA shall be at the discretion of the AS.

2.   The primary MCA designated by the participant shall be used for the following purposes:

3.   Any negative balance on a primary MCA shall not be lower than the credit line (if granted). There shall be no debit balance on an MCA that is not a primary MCA.

1.   On the request of an MCA holder the ECBshall allow an MCA held by that MCA holder to be co-managed by one of the following:

If the MCA holder holds more than one MCA, each MCA held may be co-managed by a different comanager. The co-manager shall have the same rights and privileges in relation to an MCA that it co-manages as it has in relation to its own MCA.

2.   The MCA holder shall provide the ECB with evidence of the consent of the co-manager to act in that capacity.

3.   An MCA holder acting as co-manager shall fulfil the obligations of the MCA holder of the co-managed MCA under Part I, Article 5(1), point (a), Part I, Article 10(4), and Part I, Article 30(1).

4.   The MCA holder of a co-managed MCA shall fulfil the obligations of a participant under Part I and Part II in respect of the co-managed MCA. In the event that the MCA holder does not have a direct technical connection to TARGET, Part I, Article 5(1), point (a), Part I, Article 10(4), and Part I Article 30(1) shall not apply.

5.   Part I, Article 7 shall apply to an MCA holder that designates an entity to act as co-manager of an MCA holder’s MCA pursuant to this Article.

6.   The MCA holder shall immediately notify the ECB if the co-manager ceases to act or the co-management arrangement between the MCA holder and the co-manager is terminated.

1.   On the request of an MCA holder the ECB shall create an MCA liquidity transfer group, for the purpose of enabling the processing of MCA-to-MCA liquidity transfer orders.

2.   On the request of an MCA holder the ECB shall add one of the MCA holder’s MCAs to or delete it from an existing MCA liquidity transfer group created in TARGET-ECB or another TARGET component system. The MCA holder shall inform all other MCA holders in that MCA liquidity transfer group before making such a request.

1.   The following transactions shall be processed via an MCA in TARGET-ECB:

1.   An MCA holder may submit a liquidity transfer order as one of the following:

1.   An MCA holder may specify a floor and/or a ceiling amount for its MCA.

2.   By setting a ceiling and opting for a rule-based liquidity transfer order, if, following the settlement of a payment order, the ceiling is breached, the MCA holder instructs the ECB to execute a rule-based liquidity transfer order that credits an RTGS DCA or another MCA within the same MCA liquidity transfer group designated by that MCA holder. The credited RTGS DCA or MCA may be in TARGET-ECB or another TARGET component system.

3.   By setting a floor and opting for a rule-based liquidity transfer order, if, following the settlement of a payment order, the floor is breached, a rule-based liquidity transfer order is initiated which debits an RTGS DCA or another MCA within the same MCA liquidity transfer group designated by that MCA holder. The debited RTGS DCA or MCA may be in TARGET-ECB or another TARGET component system. The holder of the RTGS DCA or MCA to be debited must authorise its account to be debited in this manner.

4.   An MCA holder may authorise its MCA to be debited in the event that a floor is breached in one or more specified RTGS DCAs or MCAs within the same liquidity transfer group in TARGET-ECB or another TARGET component system. By authorising its account to be debited, the MCA holder instructs the ECB to execute a rule-based liquidity transfer order that credits the RTGS DCA(s) or MCA(s) whenever the floor is breached.

5.   An MCA holder may authorise its MCA to be debited in the event that there is insufficient liquidity on an RTGS DCA designated for the purpose of automated liquidity transfer orders under Part III, Article 1(5) and (6) to settle urgent payment orders, AS transfer orders or high priority payment orders. By authorising its account to be debited, the MCA holder instructs the ECB to execute a rulebased liquidity transfer order that credits its RTGS DCA.

1.   Cash transfer orders, once accepted, shall settle immediately provided that there is available liquidity on the payer’s MCA.

2.   In the event that there are insufficient funds on an MCA to effect settlement, the relevant rule as set out in points (a) to (e) shall apply depending on the type of cash transfer order.

3.   All cash transfer orders in the queue shall be processed following the ‘first in, first out’ (FIFO) principle without prioritisation or reordering.

4.   Cash transfer orders in the queue at the end of the business day shall be rejected.

1.   An MCA holder may instruct the ECB to reserve a specified amount of liquidity on its MCA for the purpose of settling central bank operations or liquidity transfer orders to overnight deposit accounts using one of the following:

2.   In the event that the amount of unreserved liquidity is not sufficient to fulfil the current or standing liquidity reservation order, the ECB shall partially execute the reservation order. The ECB is instructed to execute further reservation orders until the outstanding amount to be reserved is reached. Pending reservation orders shall be rejected at the end of the business day.

3.   Central bank operations shall be settled using the liquidity reserved as set out in paragraph 1 and other cash transfer orders shall only be settled using liquidity available after the amount reserved has been deducted.

4.   Notwithstanding paragraph 3, in the event of insufficient unreserved liquidity on the MCA holder’s primary MCA for the purpose of decreasing the MCA holder’s line of intraday credit the ECBshall use the liquidity reserved.

1.   Upon termination of a participant’s participation in TARGET-ECB, the ECB shall not accept any new cash transfer orders from that participant. Cash transfer orders in the queue, warehoused cash transfer orders or new cash transfer orders in favour of that participant shall be rejected.

2.   If a participant is suspended from TARGET-ECB on grounds other than those specified in Part I, Article 24 (1), point (a), the ECB shall store all of that participant’s incoming and outgoing cash transfer orders on its MCA and only submit them for settlement after they have been explicitly accepted by the suspended participant’s CB.

3.   If a participant is suspended from TARGET-ECB on the grounds specified in Part I, Article 24(1), point (a), any outgoing cash transfer orders from that participant’s MCA shall only be processed on the instructions of its representatives, including those appointed by a competent authority or a court, such as the participant’s insolvency administrator, or pursuant to an enforceable decision of a competent authority or a court providing instructions as to how the cash transfer orders are to be processed. All incoming cash transfer orders shall be processed in accordance with paragraph 2.

1.   The ECB shall on the request of an MCA holder open and operate one or more RTGS DCAs, and one or more sub-accounts if required for use for AS settlement. If the MCA holder has adhered to the SCT Inst scheme by signing the SEPA Instant Credit Transfer Adherence Agreement, the RTGS DCA(s) (and any sub-accounts) shall not be opened or operated unless the MCA holder is and remains reachable at all times, either as a TIPS DCA holder or as a reachable party via a TIPS DCA holder.

2.   The ECB shall on the request of the holder of an account opened pursuant to paragraph 1 (RTGS DCA holder) add the RTGS DCA or its sub-account to a settlement bank account group for AS settlement. The RTGS DCA holder shall provide the ECB with any relevant documents, duly signed by that RTGS DCA holder and the AS.

3.   There shall be no debit balance on an RTGS DCA or its sub-accounts.

4.   Sub-accounts shall have a zero balance overnight.

5.   An RTGS DCA holder shall designate one of its RTGS DCAs in TARGET-ECB for the purpose of processing automated liquidity transfer orders. By such designation the RTGS DCA holder instructs the ECB to execute an automated liquidity transfer that credits the MCA in the event that there are insufficient funds on its primary MCA for the settlement of payment orders that are central bank operations.

6.   A participant holding two or more RTGS DCAs and two or more MCAs shall designate one of its RTGS DCAs in TARGET-ECB, which is not already designated to its primary MCA, for the purpose of processing automated liquidity transfer orders in the event that there are insufficient funds on one of its other MCAs for the settlement of payment orders that are central bank operations.

1.   RTGS DCA holders that are entities as set out in Part I, Article 4 may only register as an addressable BIC holder, any BIC that belongs to the same legal entity.

2.   An addressable BIC holder may submit cash transfer orders to and receive cash transfer orders via an RTGS DCA holder.

3.   An addressable BIC holder may not be registered by more than one RTGS DCA holder.

4.   Cash transfer orders submitted or cash transfers received by addressable BIC holders shall be deemed to have been submitted or received by the participant itself.

5.   The participant shall be bound by such cash transfer orders and any other action taken by the addressable BIC holders, regardless of the content of, or any non-compliance with, the contractual or other arrangements between that participant and such entity.

1.   On the request of an RTGS DCA holder the ECB shall create an RTGS liquidity transfer group, for the purpose of enabling the processing of RTGS DCA-to-RTGS DCA liquidity transfer orders.

2.   On the request of an RTGS DCA holder the ECB shall add one of the RTGS DCA holder’s RTGS DCAs to or delete it from an existing RTGS liquidity transfer group created in TARGET-ECB or another TARGET component system. The RTGS DCA holder shall inform all other RTGS DCA holders in that RTGS liquidity transfer group before making such a request.

1.   Payment orders to other RTGS DCAs and cash transfer orders to AS guarantee fund accounts shall be processed via an RTGS DCA in TARGET-ECB.

2.   Cash transfer orders related to RTGS AS settlement procedures shall be settled via an RTGS DCA or its sub-accounts in TARGET-ECB.

3.   The following transactions may be processed via an RTGS DCA or its sub-accounts in TARGET-ECB:

4.   Liquidity transfer orders to T2S DCAs may be processed via an RTGS DCA in TARGET-ECB.

1.   An RTGS DCA holder may submit a liquidity transfer order as one of the following:

2.   A standing liquidity transfer order may be input or modified by the RTGS DCA holder at any time during a business day and shall become effective as of the next business day.

3.   An immediate liquidity transfer order may be input by the RTGS DCA holder at any time during a business day. An immediate liquidity transfer order for processing in accordance with RTGS AS settlement procedures C or D may also be input by the relevant AS on behalf of the settlement bank.

1.   An RTGS DCA holder may specify a floor and/or a ceiling amount for its RTGS DCA.

2.   An RTGS DCA holder may authorise its RTGS DCA to be debited in the event that a floor is breached in one or more specified MCAs in TARGET-ECB or another TARGET component system. By authorising its RTGS DCA to be debited, the RTGS DCA holder instructs the ECB to execute a rule-based liquidity transfer order that credits the MCA(s) whenever the floor is breached.

3.   An RTGS DCA holder may authorise its MCA designated for the purpose of automated liquidity transfer orders under Article 1(5) and (6) to be debited in the event that there is insufficient liquidity on the RTGS DCA to settle urgent payment orders, AS transfer orders or high priority payment orders on its RTGS DCA.

1.   The order of priority for the processing of cash transfer orders, in descending level of urgency, shall be:

2.   The following orders shall automatically be assigned the priority ‘urgent’:

3.   All cash transfer orders not listed in paragraph 2 shall automatically be assigned the priority ‘normal’, except payment orders to which the RTGS DCA holder has at its discretion assigned the priority ‘high’.

1.   Cash transfer orders on RTGS DCAs shall be settled immediately they are accepted, or later as indicated by the RTGS DCA holder in accordance with Article 16 or Article 17, provided in all cases that:

2.   If any of the conditions set out in points (a) to (c) of paragraph 1 are not met in relation to a cash transfer order, the following shall apply.

3.   Cash transfer orders on RTGS DCAs, other than those orders referred to in paragraph 2 shall be queued and processed in accordance with the rules set out in Article 10.

1.   Cash transfer orders on RTGS DCAs that are queued in accordance with Article 9(3) shall be processed according to their priority. Subject to paragraph 2 to 5, the ‘first in, first out' (FIFO) principle shall apply within each category or subcategory of cash transfer orders priority as follows:

2.   The payer may change the priority of its cash transfer orders other than urgent cash transfer orders.

3.   The payer may change the position of its cash transfer orders in the queue. The payer may move such cash transfer orders either behind the automated liquidity transfer orders in the queue or to the end of the respective queue with immediate effect at any time during the settlement window for customer and interbank payments as specified in Appendix V.

4.   To optimise the settlement of queued cash transfer orders, the ECB may:

5.   Queued cash transfer orders shall be rejected if they cannot be settled by the cut-off times for the relevant message type as specified in Appendix V.

6.   The provisions regarding settlement of cash transfer orders as set out in Appendix I shall apply.

1.   An RTGS DCA holder may instruct the ECB to reserve a specified amount of liquidity on its RTGS DCA using one of the following:

2.   An RTGS DCA holder shall assign one of the following statuses to a current or standing liquidity reservation order:

3.   In the event that the amount of unreserved liquidity is not sufficient to fulfil the current or standing liquidity reservation order, the ECB shall partially execute the reservation order and is instructed to execute further reservation orders until the outstanding amount to be reserved is reached. Pending reservation orders shall be rejected at the end of the business day.

4.   By requesting the reservation of a specified amount of liquidity for usage for urgent cash transfer orders, the RTGS DCA holder instructs the ECB only to settle high priority and normal priority cash transfer orders if there is available liquidity after the amount reserved for usage for urgent cash transfer orders has been deducted.

5.   By requesting the reservation of a specified amount of liquidity for usage for high priority cash transfer orders, the RTGS DCA holder instructs the ECB only to settle normal priority cash transfer orders if there is available liquidity after the amount reserved for usage for urgent and high priority cash transfer orders has been deducted.

1.   An RTGS DCA holder may enter a recall request to request the return of a settled payment order.

2.   The recall request shall be forwarded to the payee of the settled payment order which may answer positively or negatively. A positive answer does not initiate a return of the funds.

1.   The RTGS directory is a list of BICs used for the purpose of routing information and comprises the BICs of:

2.   The RTGS directory shall be updated daily.

3.   Unless otherwise requested by an RTGS DCA holder, its BICs shall be published in the RTGS directory.

4.   RTGS DCA holders may only distribute the RTGS directory to their branches and entities with multiaddressee access.

5.   RTGS DCA holders acknowledge that the ECB and other CBs may publish RTGS DCA holders’ names and BICs. In addition, names and BICs of addressable BIC holders or entities with multi-addressee access may be published and RTGS DCA holders shall ensure that addressable BIC holders or entities with multi-addressee access have agreed to such publication.

1.   Upon termination of an RTGS DCA holder’s participation in TARGET-ECB, the ECB shall not accept any new cash transfer orders from that RTGS DCA holder. Cash transfer orders in the queue, warehoused cash transfer orders or new cash transfer orders in favour of that RTGS DCA holder shall be rejected.

2.   If an RTGS DCA holder’s participation in TARGET-ECB is suspended on grounds other than those specified in Part I, Article 25(1), point (a), the ECB shall store all of that RTGS DCA holder’s incoming and outgoing cash transfer orders on its RTGS DCA and only submit them for settlement after they have been explicitly accepted by the suspended RTGS DCA holder’s CB.

3.   If an RTGS DCA holder’s participation in TARGET-ECB is suspended on the grounds specified in Part I, Article 25(1), point (a), any outgoing cash transfer orders from that RTGS DCA holder’s RTGS DCA shall only be processed on the instructions of its representatives, including those appointed by a competent authority or a court, such as the RTGS DCA holder’s insolvency administrator, or pursuant to an enforceable decision of a competent authority or a court providing instructions as to how the cash transfer orders are to be processed. All incoming cash transfer orders shall be processed in accordance with paragraph 2.

1.   An RTGS DCA holder may limit the use of available liquidity for payment orders on its individual RTGS DCAs in relation to other RTGS DCAs, except any of the CBs, by specifying bilateral or multilateral limits. Such limits may only be defined in relation to normal priority payment orders.

2.   By specifying a bilateral limit, an RTGS DCA holder instructs the ECB that an accepted payment order shall not be settled if the sum of its outgoing normal priority payment orders to another RTGS DCA holder’s RTGS DCA minus the sum of all incoming urgent, high priority and normal priority payments from that RTGS DCA (the net bilateral position) would exceed this bilateral limit.

3.   An RTGS DCA holder may specify a multilateral limit for any relationship that is not subject to a bilateral limit. A multilateral limit may only be specified if the RTGS DCA holder has set at least one bilateral limit. If an RTGS DCA holder specifies a multilateral limit, it instructs the ECB that an accepted payment order shall not be settled if the sum of its outgoing normal priority payment orders to all RTGS DCA holders’ RTGS DCAs in relation to which no bilateral limit has been specified minus the sum of all incoming urgent, high priority and normal priority payments from those RTGS DCAs (the net multilateral position) would exceed this multilateral limit.

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

1.   An RTGS DCA holder may indicate the earliest time before which a payment order cannot settle or the latest time after which time the payment order will be rejected by using the earliest debit time indicator or the latest debit time indicator, respectively, or may indicate a time range during which the payment order will settle by using both indicators. An RTGS DCA holder may also use the latest debit time indicator solely as a warning indicator. In such cases, the payment order concerned shall not be rejected.

2.   In the event that 15 minutes prior to the indicated latest debit time the payment order has not been settled, the RTGS DCA holder concerned shall be notified accordingly.

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

2.   Warehoused payment orders shall be accepted and submitted for processing on the date specified by the RTGS DCA holder at the start of settlement window on that day for customer and interbank payments, as referred to in Appendix V. They shall be placed in front of payment orders of the same priority.

1.   An RTGS DCA holder (payer) may give its authorisation for another RTGS DCA holder (payee) in TARGET-ECB or in another TARGET component system to debit the payer’s RTGS DCA by direct debit.

2.   To enable such arrangement the payer shall provide a prior authorisation to the ECB entitling the ECB to debit the payer’s RTGS DCA upon receipt of a valid direct debit instruction.

3.   If a payee receives the authorisation as described in paragraph 1, it may submit direct debit instructions to debit the payer’s RTGS DCA by the amount specified in the instruction.

4.   An RTGS DCA holder that requests to be added to a settlement bank account group of an AS shall be deemed to have given authorisation to the ECB entitling the ECB to debit the RTGS DCA holder’s RTGS DCA and sub-account upon receipt of a valid direct debit instruction by that AS.

1.   The ECB shall have a pledge over the balance on an RTGS DCA holder’s sub-account opened under the arrangements between the relevant AS and its CB for the settlement of AS-related payment instructions in accordance with RTGS AS settlement procedure C. Such balance shall collateralise the RTGS DCA holder’s obligation referred to in paragraph 7 towards the ECB in relation to such settlement.

2.   Upon receipt by the ECB of a ‘start-of-cycle’ message, the ECB shall ensure that the balance on the sub-account of the RTGS DCA holder (including increases or reductions of that balance resulting from crediting or debiting cross-system settlement payments to or from the sub-account, or from crediting liquidity transfers to the sub-account) at the moment the AS starts a cycle can only be used for the settlement of AS transfer orders related to that settlement procedure C. Upon receipt by the ECB of an ‘end-of-cycle’ message the balance on the sub-account shall be available for the use of the RTGS DCA holder.

3.   By confirming the balance on the RTGS DCA holder’s sub-account, the ECB guarantees to the AS payment up to the amount of this particular balance. By confirming, where applicable, the increase or reduction of the 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 by the amount of the payment. Notwithstanding 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 AS’s CB, the ECB shall be deemed instructed to issue the abovementioned guarantee to the AS’s CB.

4.   In the absence of any insolvency proceedings in relation to the RTGS DCA holder, the AS transfer orders for the squaring of the RTGS DCA holder’s settlement obligation shall be settled without drawing on the guarantee and without recourse to the security right over the balance on the RTGS DCA holder’s sub-account.

5.   In the event of the RTGS DCA holder’s insolvency, the AS transfer orders for the squaring of the RTGS DCA holder’s settlement obligation shall be a first demand for payment under the guarantee; the debiting of the instructed amount from the RTGS DCA holder’s sub-account (and crediting of the AS’s RTGS AS 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 RTGS DCA holder’s sub-account.

6.   The guarantee shall expire upon receipt by the ECB of an ‘end-of-cycle’ message confirming that the settlement has been completed.

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

1.   The ECB shall on the request of an MCA holder open and operate one or more T2S DCAs.

2.   There shall be no debit balance on a T2S DCA.

3.   A T2S DCA holder shall designate one MCA for the purpose of processing liquidity transfer orders between T2S DCAs as referred to in Article 3(1), point (c). The designated MCA may be held in TARGET-ECB or another TARGET component system and may belong to a different participant.

1.   A T2S DCA holder may request the ECB to link its T2S 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 CSDs.

2.   T2S DCA holders linking their T2S 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-collateralisation feature.

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

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

1.   The following transactions shall be processed via a T2S DCA in TARGET-ECB:

2.   Corporate actions payments may be processed via a T2S DCA.

1.   Participants may reserve or block liquidity on their T2S DCAs. This does not constitute a settlement guarantee vis-à-vis 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 cancellation 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.

1.   A timestamp for the processing of liquidity transfer orders is allocated in the sequence of their receipt.

2.   All liquidity transfer orders submitted to TARGET-ECB shall be processed following the ‘first in, first out’ (FIFO) principle without prioritisation or reordering.

3.   After a liquidity transfer order to a TIPS DCA, an MCA, an RTGS DCA or a T2S DCA has been accepted as set out in Part I, Article 16, the TARGET-ECB shall check if sufficient funds are available on the payer’s T2S DCA to effect settlement. If sufficient funds are available, the liquidity transfer order shall be settled immediately. If sufficient funds are not available, the following shall apply:

1.   Upon termination of a T2S DCA holder’s participation in TARGET-ECB, the ECB shall not accept any new cash transfer orders from that T2S DCA holder.

2.   If a T2S DCA holder is suspended from TARGET-ECB on grounds other than those specified in Part I, Article 24(1), point (a) , the ECB shall store all of that participant’s incoming and outgoing cash transfer orders on its T2S DCA and only submit them for settlement after they have been explicitly accepted by the suspended T2S DCA holder’s CB.

3.   If a T2S DCA holder is suspended from TARGET- ECB on the grounds specified in Part I, Article 24(1), point (a), any outgoing cash transfer orders from that T2S holder’s T2S DCA shall only be processed on the instructions of its representatives, including those appointed by a competent authority or a court, such as the T2S DCA holder’s insolvency administrator, or pursuant to an enforceable decision of a competent authority or a court providing instructions as to how the cash transfer orders are to be processed. All incoming cash transfer orders shall be processed in accordance with paragraph 2.

1.   The ECB shall on the request of an MCA holder open and operate one or more TIPS DCAs.

2.   There shall be no debit balance on a TIPS DCA.

1.   A TIPS DCA holder may send messages:

2.   A TIPS DCA holder shall receive messages:

3.   Part I, Article 7 shall apply to a TIPS DCA holder that sends or receives messages via an instructing party as though that TIPS DCA holder sends or receives messages directly.

1.   A TIPS DCA holder may designate one or more reachable parties. Reachable parties shall have adhered to the SCT Inst scheme by signing the SEPA Instant Credit Transfer Adherence Agreement.

2.   A TIPS DCA holder shall provide evidence to the ECB of each designated reachable party’s adherence to the SCT Inst scheme.

3.   A TIPS DCA holder shall inform the ECB if any designated reachable party no longer adheres to the SCT Inst scheme and shall, without undue delay, take steps to prevent the reachable party from accessing the TIPS DCA.

4.   A TIPS DCA holder may allow its designated reachable parties access via one or more instructing parties.

5.   Part I, Article 7 shall apply to TIPS DCA holders that designate reachable parties.

6.   A TIPS DCA holder that has designated a reachable party shall ensure that at all times that reachable party is available for the purpose of receiving messages.

1.   The following transactions shall be processed via a TIPS DCA in TARGET-ECB:

1.   A timestamp for the processing of cash transfer orders is allocated in the sequence of their receipt.

2.   All cash transfer orders submitted to TARGET-ECB shall be processed following the ‘first in, first out’ (FIFO) principle without prioritisation or reordering.

3.   After an instant payment order has been accepted as set out in Part I, Article 16, TARGET-ECB shall check if sufficient funds are available on the payer’s TIPS DCA to effect settlement and the following shall apply:

4.   Funds reserved in accordance with paragraph 3(b) shall not be available for the settlement of subsequent cash transfer orders.

5.   Without prejudice to paragraph 3(b), the ECB shall reject an instant payment order if the amount of the instant payment order exceeds any applicable credit memorandum balance (CMB).

6.   After an immediate liquidity transfer order has been accepted as set out in Part I, Article 16, TARGET-ECB shall check if sufficient funds are available on the payer’s TIPS DCA. If sufficient funds are not available the liquidity transfer order shall be rejected.

7.   After a positive recall answer has been accepted as set out in Part I, Article 16, TARGET- ECB shall check if sufficient funds are available on the TIPS DCA to be debited. If sufficient funds are not available the positive recall answer shall be rejected. If sufficient funds are available the positive recall answer shall be settled immediately.

8.   Without prejudice to paragraph 7, TARGET-ECB shall reject positive recall answers if the amount of the positive recall answer exceeds any applicable CMB.

1.   A TIPS DCA holder may submit a recall request.

2.   The recall request shall be forwarded to the payee of the settled instant payment order which may answer with a positive or a negative recall answer.

1.   The TIPS directory is a list of BICs used for the purpose of routing information and comprises the BICs of:

2.   The TIPS directory shall be updated daily.

3.   TIPS DCA holders may only distribute the TIPS directory to their branches, their designated reachable parties and their instructing parties. Reachable parties may only distribute the TIPS directory to their branches.

4.   A specific BIC shall only appear once in the TIPS directory.

5.   TIPS DCA holders acknowledge that the ECB and other CBs may publish their names and BICs. In addition, the ECB and other CBs may publish names and BICs of reachable parties designated by TIPS DCA holders and TIPS DCA holders shall ensure that reachable parties have agreed to such publication.

1.   The central Mobile Proxy Lookup (MPL) repository contains the proxy – IBAN mapping table for the purposes of the MPL service.

2.   Each proxy may be linked to only one IBAN. An IBAN may be linked to one or multiple proxies.

3.   Part I, Article 27 shall apply to the data contained in the MPL repository.

1.   Upon termination of a TIPS DCA holder’s participation in TARGET-ECB, the ECB shall not accept any new cash transfer orders to or from that TIPS DCA holder.

2.   If a TIPS DCA holder’s participation in TARGET-ECB is suspended on grounds other than those specified in Part I, Article 24(1), point (a), the ECB shall:

3.   If a TIPS DCA holder’s participation in TARGET-ECB is suspended on the grounds specified in Part I, Article 24(1), point (a), the ECB shall reject all of its incoming and outgoing cash transfer orders.

4.   The ECB shall process instant payment orders of a TIPS DCA holder whose participation in TARGET-ECB has been suspended or terminated under Part I, Article 24(1) or (2) and in relation to which the ECB has reserved funds on a TIPS DCA pursuant to Article 6(3), point (b) prior to the suspension or termination.

1.   The ECB may on the request of an AS open and operate one or more RTGS AS technical accounts to support RTGS AS settlement procedures.

2.   There shall be no debit balance on an RTGS AS technical account.

3.   RTGS AS technical accounts shall not be published in the RTGS directory.

4.   The AS shall select at least one of the following settlement procedures for the purposes of processing AS transfer orders:

5.   The rules set out in Articles 3, 4, 5, 6 and 7 shall apply to RTGS AS settlement procedures A, B, C, D and E, respectively.

6.   The RTGS AS settlement procedures shall be operational during the times set out in Appendix V.

7.   The AS shall request the ECB to create a settlement bank account group.

8.   The AS shall only send AS transfer orders to accounts included in the settlement bank account group referred to in paragraph 7.

1.   The AS shall request a dedicated RTGS AS technical account to support the processing of AS transfer orders using settlement procedure A. The balance on such account shall be zero at the end of the day.

2.   The AS may request the opening of an AS guarantee fund account to support settlement in connection with the ‘settlement period’ service. The balances on the AS guarantee fund account shall be used to settle AS transfer orders in the event that there is insufficient available liquidity on a settlement bank's RTGS DCA. The AS guarantee fund account may be held by the ECB, the AS or an eligible participant. The AS guarantee fund account shall not be published in the RTGS directory.

3.   The AS shall submit AS transfer orders as a batch in a single file in which the sum of debits must balance the sum of credits.

4.   The ECB shall first attempt to settle AS transfer orders that debit the RTGS DCAs of settlement banks and crediting the AS's RTGS AS technical account. Only upon settlement of all such AS transfer orders (including possible funding of the RTGS AS technical account from the AS guarantee fund account) the ECB shall attempt to settle AS transfer orders that debit the RTGS AS technical account and that credit the RTGS DCAs of settlement banks.

5.   If an AS transfer order to debit a settlement bank's RTGS DCA is queued, the ECB shall inform the settlement bank by means of a broadcast message.

6.   If an AS guarantee fund account has been opened and a settlement bank has insufficient funds on its RTGS DCA, the AS may instruct the ECB to activate the guarantee fund mechanism by means of a request to debit the AS guarantee fund account and to credit the RTGS AS technical account. If the AS guarantee fund account does not have sufficient funds to complete settlement, the settlement process shall fail.

7.   If the settlement process fails for any reason, including as referred to in paragraph 6, the ECB shall reject all unsettled AS transfer orders in the single file referred to in paragraph 3 and shall reverse any AS transfer orders that have already been settled.

8.   The AS shall be notified on completion or failure of the settlement.

9.   The AS may opt for the following services:

1.   The AS shall request a dedicated RTGS AS technical account to support the processing of AS transfer orders using settlement procedure B. The balance on such account shall be zero at the end of day.

2.   The AS may request the opening of an AS guarantee fund account to support settlement in connection with the ‘settlement period’ service. The balances on the AS guarantee fund account shall be used to settle the AS transfer orders in the event that there is insufficient available liquidity on a settlement bank's RTGS DCA. The AS guarantee fund account may be held by the ECB, the AS or an eligible participant. The AS guarantee fund account shall not be published in the RTGS directory.

3.   The AS shall submit AS transfer orders as a batch in a single file in which the sum of debits must balance the sum of credits.

4.   Settlement procedure B operates on an ‘all-or-nothing’ basis. The ECB shall attempt to simultaneously settle all AS transfer orders that debit the RTGS DCAs of settlement banks and credit the AS’s RTGS AS technical account, and all AS transfer orders that debit the RTGS AS technical account and credit the RTGS DCAs of settlement banks. If one or more of the AS transfer orders cannot be settled, all AS transfer orders shall be queued and an optimisation algorithm shall be applied, and the settlement banks shall be informed.

5.   If an AS guarantee fund account has been opened and a settlement bank has insufficient funds on its RTGS DCA, the AS may instruct the ECB to activate the guarantee fund mechanism by means of a request to debit the AS guarantee fund account and to credit the RTGS AS technical account. If the AS guarantee fund account does not have sufficient funds to complete settlement, the settlement process shall fail.

6.   If the settlement process fails for any reason, including as referred to in paragraph 5, the ECB shall reject all unsettled AS transfer orders in the single file referred to in paragraph 3.

7.   The AS shall be notified on completion or failure of the settlement.

8.   The AS may opt for the following services:

1.   Settlement procedure C supports settlement using dedicated liquidity on sub-accounts. The AS shall request a dedicated RTGS AS technical account to support the processing of AS transfer orders using settlement procedure C. The balance on such account shall be zero at the end of the day. This RTGS AS technical account may also be used to support the processing of AS transfer orders using settlement procedure E.

2.   The AS shall ensure that each settlement bank opens at least one sub-account that is only to be used by the AS for the purposes of this settlement procedure.

3.   The ECB shall start a mandatory settlement procedure C automatically on each TARGET business day according to the schedule set out in Appendix V, that shall trigger the settlement of those standing liquidity transfer orders set up for mandatory settlement procedure C by debiting the RTGS DCAs of the settlement banks and crediting the sub-account referred to in paragraph 2.

4.   Settlement procedure C shall close by means of an end-of-procedure message, which may be sent by the AS at any time prior to the cut-off time for interbank payments as set out in Appendix V. If the AS does not send the end-of-procedure message by that cut-off time, the ECB shall close the procedure at that cut-off time.

5.   The closure of the mandatory settlement procedure C leads to an automatic transfer of liquidity from the sub-account referred to in paragraph 2 to the RTGS DCA.

6.   If the mandatory settlement procedure C is closed, the AS may start an optional procedure at any time before the cut-off time for interbank payments as set out in Appendix V, that shall trigger the settlement of those standing liquidity transfer orders set up for optional settlement procedure C by debiting the settlement bank’s RTGS DCA and crediting its RTGS sub-account. The AS may start and close one or several successive optional procedures before the cut-off time for interbank payments. The closure of an optional settlement procedure C leads to an automatic transfer of liquidity from the sub-account referred to in paragraph 2 to the RTGS DCA.

7.   The mandatory settlement procedure C and any subsequent optional settlement procedure C may consist of one or several cycles.

8.   The AS may, at any time after the start of a mandatory or optional settlement procedure C, start a cycle by means of a ‘start-of-cycle’ message. After the start of the cycle, liquidity transfers from the sub-account referred to in paragraph 2 may not be made until an ‘end-of-cycle’ message is sent by the AS. The balance can be changed during the cycle as a result of cross-system settlement payments or if a settlement bank transfers liquidity to its sub-account. The ECB shall notify the AS of the reduction or increase of liquidity on the sub-account as a result of cross-system settlement payments. If the AS so requests, the ECB shall also notify it of the increased liquidity on the sub-account as a result of liquidity transfer orders by the settlement bank.

9.   The AS may submit AS transfer orders as a batch in one or several files while the cycle is open. The cash transfer orders may be for any of the following transactions:

10.   The ECB shall immediately settle those AS transfer orders that can be settled. AS transfer orders that cannot be settled immediately shall be queued and an optimisation algorithm shall be applied. Any AS transfer orders which remain unsettled at the time the cycle is closed shall be rejected.

11.   The AS shall be notified at the latest by the end of the cycle of the status of the individual AS transfer orders.

1.   RTGS AS Settlement procedure D supports settlement with the use of pre-funding. The AS shall request a dedicated RTGS AS technical account to support the processing of AS transfer orders using settlement procedure D.

2.   The RTGS AS technical accounts shall only have a zero balance or a positive balance. Liquidity may remain on the RTGS AS technical account overnight whereupon it will be subject to remuneration as set out in Part I, Article 12(2).

3.   The ECB shall notify the AS of liquidity transfers debiting the RTGS DCAs of the settlement banks and crediting the RTGS AS technical account. These liquidity transfers may be made on each TARGET business day according to the schedule set out in Appendix V. The AS may input immediate liquidity transfer orders that debit the RTGS AS technical account and credit the RTGS DCAs of the settlement banks.

1.   RTGS AS Settlement procedure E supports bilateral settlement and the individual processing of AS transfer orders. The AS may use Settlement Procedure E without an RTGS AS technical account for bilateral settlement. The AS shall request an RTGS AS technical account to support the processing of AS transfer orders using settlement procedure E if it opts for the individual processing of AS transfer orders. The balance on this RTGS AS technical account shall be zero at the end of the day. This RTGS AS technical account may also be used for settlement procedure C.

2.   The AS may submit AS transfer orders as a batch in one or several files between:

The AS shall be responsible for ensuring the correct sequencing of AS transfer orders in the file to ensure smooth settlement.

3.   The ECB shall settle immediately those AS transfer orders that can be settled. AS transfer orders that cannot be settled immediately shall be queued. If an AS transfer order to debit a settlement bank's RTGS DCA is queued, the settlement bank shall be informed via a broadcast message.

4.   The AS may opt for the following services:

5.   The AS shall be notified of the status of the individual AS transfer orders submitted.

1.   The ‘information period’ service allows the AS to inform its settlement banks of the liquidity needed to ensure successful settlement. This optional service allows the AS to define a period before the start of the settlement of the AS transfer orders. During that period, and at the request of the settlement bank, the AS may revoke either single AS transfer orders (for RTGS AS settlement procedure E) or files (for RTGS AS settlement procedures A and B). The AS may also request the ECB to perform such revocation on its behalf.

2.   In the event that an AS, or the ECB on its behalf, revokes single AS transfer orders (for RTGS AS settlement Procedure E) or files (for RTGS AS settlement procedures A and B) during the ‘information period’, the processing of the AS transfer orders shall be cancelled.

3.   The ‘settlement period’ service allows the AS to define a period until which the settlement of the AS transfer orders can take place. This service is a prerequisite for the use of a guarantee fund account, and is optional for the use of AS technical accounts.

4.   During the ‘settlement period’ the AS, or the ECB on its behalf, may revoke either single AS transfer orders (for RTGS AS settlement procedure E) or files (for RTGS AS settlement procedures A and B) that do not have a final status and the following shall apply:

1.   Cross-system settlement allows an AS to credit the RTGS AS technical account of another AS or sub-account of a settlement bank of another AS and is available for AS using RTGS AS settlement procedure C or D.

2.   The ECB shall, on the request of the AS, allow cross-system settlement between that AS and another AS in TARGET-ECB or another TARGET component system. The requesting AS shall provide the ECB with the authorisation of the other AS.

3.   A cross-system settlement may only be initiated if the two AS have opened a settlement procedure. Furthermore, if the cross-system settlement is initiated by an AS using RTGS AS settlement procedure C, a settlement cycle must also be open for that AS.

4.   An AS using RTGS AS settlement procedure C in the context of cross-system settlement shall only submit AS transfer orders individually that debit the sub-account of one of its AS settlement banks. These AS transfer orders would credit the sub-account of the receiving AS settlement bank if that receiving AS is using RTGS AS settlement procedure C, or would credit the RTGS AS technical account of the receiving AS if that AS is using RTGS AS settlement procedure D.

5.   An AS using RTGS AS settlement procedure D in the context of cross-system settlement shall only submit AS transfer orders individually that debit its RTGS AS technical account. These AS transfer orders would credit the sub-account of the receiving AS settlement bank if that receiving AS is using RTGS AS settlement procedure C, or would credit the RTGS AS technical account of the receiving AS if that AS is using RTGS AS settlement procedure D. Both AS using cross-system settlement shall be notified via a broadcast message of the settlement or rejection of the AS transfer orders.

1.   The ECB may on the request of an AS that settles instant payments pursuant to the SCT Inst scheme or near instant payments in its own books, open and operate one or more TIPS AS technical accounts.

2.   There shall be no debit balance on a TIPS AS technical account.

3.   The ancillary system shall use a TIPS AS technical account to collect the necessary liquidity set aside by its clearing members to fund their positions.

4.   The ancillary system may opt to receive notifications of the crediting and debiting of its TIPS AS technical account. If the ancillary system opts for this service notification is provided immediately upon the debit or credit of the TIPS AS technical account.

5.   An ancillary system may send instant payment orders, and positive recall answers to any TIPS DCA holder or TIPS AS. A ancillary system shall receive and process instant payment orders, recall requests and positive recall answers from any TIPS DCA holder or TIPS AS.

1.   A TIPS AS technical account holder may send messages:

2.   A TIPS AS technical account holder shall receive messages:

Article 7 of Part I shall apply to a TIPS AS technical account holder that sends or receives messages via an instructing party as though that TIPS AS technical holder sends or receives messages directly.

1.   A timestamp for the processing of cash transfer orders is allocated in the sequence of their receipt.

2.   All cash transfer orders submitted to TARGET-ECB shall be processed following the ‘first in, first out’ (FIFO) principle without prioritisation or reordering.

3.   After an instant payment order has been accepted as set out in Part I, Article 17(1), the ECB shall check if sufficient funds are available on the payer’s TIPS AS technical account to effect settlement and the following shall apply:

4.   Funds reserved in accordance with paragraph 3(b) shall not be available for the settlement of subsequent cash transfer orders.

5.   Without prejudice to paragraph 3(b), the ECB shall reject an instant payment order if the amount of the instant payment order exceeds any applicable credit memorandum balance (CMB).

6.   After a liquidity transfer order from a TIPS AS technical account to a TIPS DCA has been accepted as set out in Part I, Article 17(1), the ECB shall check if sufficient funds are available on the payer’s TIPS AS technical account. If sufficient funds are not available the liquidity transfer order shall be rejected. If sufficient funds are available the liquidity transfer order shall be settled immediately.

7.   After a positive recall answer has been accepted as set out in Part I, Article 17, the ECB shall check if sufficient funds are available on the TIPS AS technical account to be debited. If sufficient funds are not available the positive recall answer shall be rejected. If sufficient funds are available the positive recall answer shall be settled immediately.

8.   Without prejudice to paragraph 7, the ECB shall reject positive recall answers if the amount of the positive recall answer exceeds any applicable CMB.

1.   A TIPS AS technical account holder may submit a recall request.

2.   The recall request shall be forwarded to the payee of the settled instant payment order which may answer with a positive or negative recall answer.

1.   A TIPS AS technical account holder may designate one or more reachable parties. Reachable parties shall have adhered to the SCT Inst scheme signing the SEPA Instant Credit Transfer Adherence Agreement.

2.   A TIPS AS technical account holder shall provide evidence to the ECB of each designated reachable party’s adherence to the SCT Inst scheme.

3.   A TIPS AS technical account holder shall inform the ECB if any designated reachable party no longer adheres to the SCT Inst scheme and shall, without undue delay, take steps to prevent the reachable party from accessing the TIPS AS technical account.

4.   A TIPS AS technical account holder may allow its designated reachable parties access via one or more instructing parties.

5.   Part I, Article 7 shall apply to an AS that has designated reachable parties.

6.   A TIPS AS technical account holder that has designated a reachable party shall ensure that reachable party is at all times available for the purpose of receiving messages.

1.   The following transactions shall be processed via a TIPS AS technical account in TARGET-ECB:

1.   The TIPS directory is a list of BICs used for the purpose of routing information and comprises the BICS of:

2.   The TIPS directory shall be updated daily.

3.   TIPS AS technical account holders may only distribute the TIPS directory to their designated reachable parties and their instructing parties. Reachable parties may only distribute the TIPS directory to their branches.

4.   A specific BIC shall only appear once in the TIPS directory.

5.   TIPS AS technical account holders acknowledge that the ECB and other CBs may publish names and BICs of reachable parties designated by the TIPS AS technical account holders and TIPS AS technical account holders shall ensure that reachable parties have agreed to such publication.

1.   The central Mobile Proxy Lookup (MPL) repository contains the proxy – IBAN mapping table for the purposes of the MPL service.

2.   Each proxy may be linked to only one IBAN. An IBAN may be linked to one or multiple proxies.

3.   Part I, Article 28 shall apply to the data contained in the MPL repository.

1.   Upon termination of a TIPS AS technical account holder’s participation in TARGET-ECB, the ECB shall not accept any new cash transfer orders to or from that TIPS AS technical account holder.

2.   If a TIPS AS technical account holders’ participation in TARGET-ECB is suspended on grounds other than those specified in Part I, Article 24(1), point (a), the ECB shall:

3.   If a TIPS AS Technical Account Holder’s participation in TARGET-ECB is suspended on the grounds specified in Part I, Article 24(1), point (a), the suspended TIPS AS technical account holder’s CB shall reject all of its incoming and outgoing sash transfer orders.

4.   The ECB shall process instant payment orders of a TIPS AS technical account holder whose participation in TARGET-ECB has been suspended or terminated under Part I, Article 24(1) or (2) and in relation to which the ECB has reserved funds on a TIPS AS technical account pursuant to Article 4(3), point (b) prior to the suspension or termination.