In addition to the Harmonised Conditions, the following rules shall apply to the processing of cash transfer orders:
Each participant shall pass a series of tests to prove its technical and operational competence before it may participate in TARGET-[insert CB/country reference].
Each participant’s account shall be identified by a unique account number of up to 34 characters made up of five sections as follows:
[For sub-accounts this section must start with the 3-character AS code as defined by the central bank.]
Name | No. of Characters | Content
Account type | 1 |
M = MCA
R = RTGS DCA
C = T2S DCA
I = TIPS DCA
T = RTGS AS Technical account
U = Sub-account
A = TIPS AS Technical account
G = AS Guarantee funds account
D = Overnight deposit account
X = Contingency Account
Country Code of Central Bank | 2 | ISO Country code : 3166-1
Currency code | 3 | EUR
BIC | 11 | Account holder BIC
Account name | Max. 17 | Free text
Each participant shall comply with the message structure and field specifications, as defined in Part 3 of the relevant User Detailed Functional Specifications (UDFS).
Business application headers shall be attached to all message types processed on MCAs, RTGS DCAs (including sub-accounts) RTGS AS technical accounts, AS guarantee fund accounts and T2S DCAs as follows:
Message Type | Description
head.001 | Business application header
head.002 | Business file header
The following message types are processed on MCAs:
Message Type | Description
Administration (admi) |
admi.004 | SystemEventNotification
admi.005 | ReportQueryRequest
admi.007 | ReceiptAcknowledgement
Cash Management (camt) |
camt.003 | GetAccount
camt.004 | ReturnAccount
camt.005 | GetTransaction
camt.006 | ReturnTransaction
camt.018 | GetBusinessDayInformation
camt.019 | ReturnBusinessDayInformation
camt.025 | Receipt
camt.046 | GetReservation
camt.047 | ReturnReservation
camt.048 | ModifyReservation
camt.049 | DeleteReservation
camt.050 | LiquidityCreditTransfer
camt.053 | BankToCustomerStatement
camt.054 | BankToCustomerDebitCreditNotification
Payments clearing and Settlement (pacs) |
pacs.009 | FinancialInstitutionCreditTransfer
pacs.010 | FinancialInstitutionDirectDebit
The following message types are processed on RTGS DCAs, and where relevant on the RTGS AS technical accounts and AS guarantee funds accounts:
Administration (admi) |
admi.004 | SystemEventNotification
admi.005 | ReportQueryRequest
admi.007 | ReceiptAcknowledgement
Cash Management (camt) |
camt.003 | GetAccount
camt.004 | ReturnAccount
camt.005 | GetTransaction
camt.006 | ReturnTransaction
camt.007 | ModifyTransaction
camt.009 | GetLimit
camt.010 | ReturnLimit
camt.011 | ModifyLimit
camt.012 | DeleteLimit
camt.018 | GetBusinessDayInformation
camt.019 | ReturnBusinessDayInformation
camt.021 | ReturnGeneralBusinessInformation
camt.025 | Receipt
camt.029 | ResolutionOfInvestigation
camt.046 | GetReservation
camt.047 | ReturnReservation
camt.048 | ModifyReservation
camt.049 | DeleteReservation
camt.050 | LiquidityCreditTransfer
camt.053 | BankToCustomerStatement
camt.054 | BankToCustomerDebitCreditNotification
camt.056 | FIToFIPaymentCancellationRequest
Payments Clearing and Settlement (pacs) |
pacs.002 | PaymentStatusReport
pacs.004 | PaymentReturn
pacs.008 | CustomerCreditTransfer
pacs.009 | FinancialInstitutionCreditTransfer
pacs.010 | FinancialInstitutionDirectDebit
Payments Initiation (pain) |
pain.998 | ASInitiationStatus
pain.998 | ASTransferNotice
pain.998 | ASTransferInitiation
The following message types are processed on T2S DCAs:
Message Type | Description
Administration (admi) |
admi.005 | ReportQueryRequest
admi.006 | ResendRequestSystemEventNotification
admi.007 | ReceiptAcknowledgement
Cash Management (camt) |
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
The following message types are processed on TIPS DCAs and TIPS AS technical accounts:
Message Type | Description
Payments Clearing and Settlement (pacs) |
pacs.002 | FIToFIPayment Status Report
pacs.004 | PaymentReturn
pacs.008 | FIToFICustomerCreditTransfer
pacs.028 | FIToFIPaymentStatusRequest
Cash Management (camt) |
camt.003 | GetAccount
camt.004 | ReturnAccount
camt.011 | ModifyLimit
camt.019 | ReturnBusinessDayInformation
camt.025 | Receipt
camt.027 | ClaimNonReceipt
camt.029 | ResolutionOfInvestigation
camt.050 | LiquidityCreditTransfer
camt.052 | BankToCustomerAccountReport
camt.053 | BankToCustomerStatement
camt.054 | BankToCustomerDebitCreditNotification
camt.056 | FIToFIPaymentCancellationRequest
acmt.010 | AccountRequestAcknowledgement
acmt.011 | AccountRequestRejection
acmt.015 | AccountExcludedMandateMaintenanceRequest
admi.004 | SystemEventNotification
Reference data (reda) |
reda.016 | PartyStatusAdviceV01
reda.022 | PartyModificationRequestV01
The following additional message subtypes are used for instant payment orders according to the OCTs Inst scheme:
Message Type | Description
pacs.002.001.03 | FIToFIPayment Status Report
pacs.008.001.08 | FIToFICustomerCreditTransfer
pacs.028.001.03 | FIToFIPaymentStatusRequest
Messages related to instant payment orders according to the OCTs Inst scheme will be identified with the suffix XCY in the message exchange protocol.
All cash transfer orders shall pass a double-entry check, the aim of which is to reject orders that have been submitted more than once (duplicated cash transfer orders). Details can be found in Part I, Section 3 of the relevant UDFS.
Validation of messages is carried out according to High Value Payments Plus (HVPS+) guidelines on message validations specified by the ISO 20022 standard, and TARGET-specific validations. The detailed validation rules and error codes are described in the respective parts of the UDFS as follows:
for MCAs, in Chapter 14 of the CLM UDFS;
for RTGS DCAs, in Chapter 13 of the RTGS UDFS;
for T2S DCAs, in Chapter 4.1 of the T2S UDFS.
If an instant payment order or a positive recall answer is rejected for any reason, the TIPS DCA holder shall receive a payment status report (pacs.002), as described in Chapter 4.2 of the TIPS UDFS. If a liquidity transfer order is rejected for any reason, the TIPS DCA holder shall receive a rejection (camt.025), as described in Chapter 1.6 of the TIPS UDFS.
For payment orders using the Earliest Debit Time Indicator, the message element ‘/FromTime/’ shall be used.
For payment orders using the Latest Debit Time Indicator, two options shall be available.
Message element ‘RejectTime’: if the payment order cannot be settled by the indicated debit time, the cash transfer order shall be rejected.
Message element ‘TillTime’: if the payment order cannot be settled by the indicated debit time, the cash transfer order shall not be rejected but shall be kept in the relevant queue.
Under both options, if a payment order with a Latest Debit Time Indicator is not settled 15 minutes prior to the time indicated therein, a notification shall automatically be sent via the GUI.
For immediate liquidity transfer orders, no specific XML tag is required;
Predefined liquidity transfer orders and standing liquidity transfer orders may be triggered by a specific time or event on the day of settlement:
for settlement at a specific time, the XML tag ‘Time(/ExctnTp/Tm/)’ shall be used,
for settlement upon occurrence of a specific event, the XML tag ‘(EventType/ExctnTp/Evt/)’ shall be used.
the validity period for standing liquidity transfer orders shall be set by the following XML tags: ‘FromDate/VldtyPrd/FrDt/’ and ‘ToDate/VldtyPrd/ToDt/’.
Offsetting checks and, if appropriate, extended offsetting checks (both terms as defined in subparagraphs a) and b) shall be carried out on cash transfer orders to facilitate the smooth settlement.
An offsetting check shall determine whether the payee’s cash transfer orders that are at the front of the queue for cash transfer orders with the priority ‘urgent’ or, if inapplicable, ’high’ are available to be offset against the payer’s cash transfer order (hereinafter ‘offsetting cash transfer orders’). If an offsetting cash transfer order does not provide sufficient funds for the respective payer’s cash transfer order it shall be determined whether there is sufficient available liquidity on the payer’s RTGS DCA.
If the offsetting check fails, the [insert name of CB] may apply an extended offsetting check. An extended offsetting check determines whether offsetting cash transfer orders are available in any of the payee’s queues regardless of when they joined the queue. However, if in the queue of the payee there are higher priority cash transfer orders addressed to other participants, the FIFO principle may only be breached if settling such an offsetting cash transfer order would result in a liquidity increase for the payee.
Four algorithms shall be applied to facilitate the smooth settlement of payment flows. Further information is available in the RTGS UDFS Part 2.
Under the ‘partial optimisation’ algorithm the [insert name of CB] shall:
calculate and check the liquidity positions, limits and reservations of each relevant RTGS DCA; and
if the total liquidity position of one or more relevant RTGS DCA is negative, extract single payment orders until the total liquidity position of each relevant RTGS DCA is positive.
Thereafter, the [insert name of CB] and the other CBs involved shall, provided there are sufficient funds, settle the relevant remaining cash transfer orders (except the extracted payment orders described in point (ii)) simultaneously on the RTGS DCAs of the participants concerned.
When extracting payment orders, the [insert name of CB] shall start from the participant’s RTGS DCA with the highest negative total liquidity position and from the payment order at the end of the queue with the lowest priority. The selection process shall only run for a short time, to be determined by the [insert name of CB] at its discretion.
Under the ‘multiple optimisation’ algorithm the [insert name of CB] shall:
compare pairs of participants’ RTGS DCAs to determine whether queued payment orders can be settled within the available liquidity of the two participants’ RTGS DCAs concerned and within the limits set by them (by starting from the pair of RTGS DCAs with the smallest difference between the payment orders addressed to each other), and the CBs involved shall book those payments simultaneously on the two participants’ RTGS DCAs; and
if, in relation to a pair of RTGS DCAs as described in point (i), liquidity is insufficient to fund the bilateral position, extract single payment orders until there is sufficient liquidity. In this case the CBs involved shall settle the remaining payments, except the extracted ones, simultaneously on the two participants’ RTGS DCAs.
After performing the checks specified in points (i) to (ii), the [insert name of CB] shall check the multilateral settlement positions (between a participant’s RTGS DCA and other participants’ RTGS DCAs in relation to which a multilateral limit has been set). For this purpose, the procedure described under subparagraphs (i) to (ii) shall apply mutatis mutandis.
Under the algorithm ‘partial optimisation with AS’ which supports settlement procedure B, the [insert name of CB] shall follow the same procedure as for the partial optimisation algorithm, but without extracting AS transfer orders (for an AS which settles on a simultaneous multilateral basis i.e. RTGS AS settlement procedure B).
The algorithm ‘optimisation on sub-accounts’ is used to optimise the settlement of urgent priority AS transfer orders on participants’ sub-accounts. When using this algorithm the [insert name of CB] shall calculate the total liquidity position of each participant’s sub-account by establishing whether the aggregate of all outgoing and incoming AS transfer orders pending in the queue is negative or positive. If the outcome of these calculations and checks is positive for each relevant sub-account, the [insert name of CB] and other CBs involved shall settle all cash transfers simultaneously on the sub-accounts of the participants concerned. If the outcome of these calculations and checks is negative no settlement shall take place. Furthermore, this algorithm does not take account of any limits or reservations. For each settlement bank the total position is calculated and, if the positions for all settlement banks are covered, all transactions shall be settled. Transactions which are not covered are returned to the queue.
Cash transfer orders entered after the multiple optimisation algorithm, the partial optimisation algorithm or the partial optimisation with AS algorithm has started may nevertheless be settled immediately if the positions and limits of the participants’ RTGS DCAs concerned are compatible with both the settlement of these orders and the settlement of cash transfer orders in the current optimisation procedure.
The partial optimisation algorithm and the multiple optimisation algorithm shall be run sequentially in that order. They shall not be run if RTGS AS settlement procedure B is running.
The algorithms shall run flexibly by setting a pre-defined time lag between the application of different algorithms to ensure a minimum interval between the running of two algorithms. The time sequence shall be automatically controlled. Manual intervention shall be possible.
While included in a running algorithm, a payment order shall not be reordered (change of the position in a queue) or revoked. Requests for reordering or revocation of a payment order shall be queued until the algorithm is complete. If the payment order concerned is settled while the algorithm is running, any request to reorder or revoke shall be rejected. If the payment order is not settled, the participant’s requests shall be taken into account immediately.
Participants shall connect to TARGET using one of the following modes.
The user to application (U2A) mode: in the U2A mode, participants connect via a GUI which allows users to perform business functions based on their respective access rights. It allows users to enter and maintain business data as well as to retrieve business information. The relevant User Handbook (UHB) provides exhaustive information on each of the business functions that the respective GUI provides.
The application to application (A2A) mode: in A2A mode software applications communicate with TARGET by exchanging single messages and files based on their respective access rights and message subscription and routing configuration. The A2A communication relies on XML messages, using the ISO 20022 standard where applicable, for both inbound and outbound communication.
The modes of connection are described in further detail in the ESMIG UDFS.
Further details and examples explaining the above rules are contained in the respective UDFS and the User Handbooks for each service, as amended from time to time and published on [insert as necessary the [insert name of CB]’s website and] the ECB’s website in English.