camt.025 ISO 20022 message

camt.025 ISO 20022 message: Definition

camt.025 ISO 20022 message stands for “Receipt”. With this ISO 20022 XML message, a market infrastructure confirms to a participant that a previously sent request has been executed – or reports that the request has been rejected.

camt.025 ISO 20022 message: Scope

The camt.025 is not a payment message but an acknowledgement. It is deliberately generic and serves in the TARGET Services as the uniform response to very different requests from the participant: liquidity transfers, limit changes, reservations and modifications of queued payment orders. Which request is being answered follows from the reference returned and from the request type field; the status field carries the outcome, together with a reason code in the case of a rejection.

The camt.025 is thus the counterpart of the pacs.002 ISO 20022 message, which reports the status of a payment, and of the camt.029 ISO 20022 message, with which one bank informs another of the outcome of an investigation. Unlike those two, the camt.025 is not exchanged between two credit institutions but always between a participant and the market infrastructure that holds its account.

The following ISO 20022 messages are answered with a camt.025, among others:

• camt.050 ISO 20022 message – liquidity credit transfer
• camt.007 – modify transaction: change of priority or execution time of a queued payment
• camt.011 / camt.012 – modify limit and delete limit
• camt.048 / camt.049 – modify reservation and delete reservation
• camt.998 – central bank specific messages (e.g. administrative functions)

Payments are not answered with a camt.025 (response: pacs.002), nor are recalls in RTGS (response: camt.029). Pure queries such as camt.003 (account balance) are answered with the corresponding report message, e.g. camt.004.

camt.025 ISO 20022 message: Usage

General

The camt.025 closes every request dialogue between participant and market infrastructure. It contains no balances and no booking details – the bookings themselves are notified, depending on the message subscription, by the camt.054 ISO 20022 message and the camt.053 ISO 20022 message statement of account.

T2 (TARGET Services)

Receipt – camt.025.001.05

In T2, both central liquidity management (CLM) and the RTGS component use the camt.025 as the standard response in A2A communication. If a participant sends a camt.050 to move liquidity from the main cash account (MCA) to its RTGS account, CLM acknowledges execution with a positive camt.025; if funds are insufficient or the target account is unknown, a negative camt.025 with a reason code is returned. The same message confirms a changed limit (camt.011), the deletion of a limit (camt.012), a changed liquidity reservation (camt.048) or the re-prioritisation of a queued payment (camt.007).

For requests that cannot be executed immediately – for instance a reservation that only takes effect later – the first camt.025 confirms acceptance only; a second camt.025 later reports the outcome of the execution. The complete dialogue:

TIPS and T2S

TIPS and T2S also use the camt.025 to acknowledge liquidity transfers (camt.050) and further requests. In TIPS, every inbound and outbound liquidity transfer is answered with a camt.025, so that the participant immediately knows whether the funds on the TIPS DCA have been increased for incoming SCT Inst payments.

SWIFT MX

The camt.025 plays no role in SWIFT correspondent banking: it is a message between a participant and a market infrastructure, not between two banks. Status reports on payments are sent there via the pacs.002.

Sources for specifications

• ISO 20022 standard – Cash Management (camt)
• ECB – T2 CLM and RTGS User Detailed Functional Specifications (UDFS)
• ECB – TIPS User Detailed Functional Specifications
• Deutsche Bundesbank – TARGET Services