Decision of the European Central Bank of 24 July 2007 concerning the terms and conditions of TARGET2-ECB (ECB/2007/7) (2007/601/EC)

[F1 [F2 PARAMETERS OF THE T2S DEDICATED CASH ACCOUNTS — TECHNICAL SPECIFICATIONS] U.K.

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 U.K.

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

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

(3) For the submission of liquidity transfer orders in the [F2 T2S 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 following information: U.K.

(a)

in the case of liquidity transfers between two [F2 T2S DCAs] , the unique 34 character account numbers of both the sending and the receiving [F2 T2S DCA holder] ; or

(b)

in the case of liquidity transfers from a [F2 T2S DCA] to a PM account, the unique 34 character account number of the sending [F2 T2S 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 [F2 T2S 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. U.K.

(5) [F2 T2S 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. U.K.

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

2. Message types U.K.

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
(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)	IntraBalanceMovementModificationRequestStatusAdvice
(camt.074)	IntraBalanceMovementCancellationRequest
(camt.075)	IntraBalanceMovementCancellationRequestStatusAdvice
(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 U.K.

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

(2) The following parameters shall be checked: U.K.

• Order Reference (End to End Id);

• Debit and Credit Account ( [F2 T2S DCA] or PM account); and

• instructed Amount.

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

4. Error codes U.K.

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

5. Settlement triggers U.K.

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

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

• 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/VldtyPrd/ToDt/ ’ . U.K.

6. Settlement of liquidity transfer orders U.K.

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 U.K.

(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 [F2 T2S DCA holders] : U.K.

(a)

Application-to-application mode (A2A)

In A2A, information and messages are transferred between the T2S Platform and the [F2 T2S DCA holder's] internal application. The [F2 T2S 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 [F2 T2S 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. U.K.

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

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

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

(6) If a [F2 T2S 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 T2S DCA holder] . U.K.

8. Relevant documentation U.K.

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

Textual Amendments

F1 Inserted by Decision (EU) 2015/929 of the European Central Bank of 26 May 2015 amending Decision ECB/2007/7 concerning the terms and conditions of TARGET2-ECB (ECB/2015/22).

F2 Substituted by Decision (EU) 2018/1625 of the European Central Bank of 8 October 2018 amending Decision ECB/2007/7 concerning the terms and conditions of TARGET2-ECB (ECB/2018/24).