ZagTrader

camt: Cash Management

camt.025 Receipt

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

camt.025 is the ISO 20022 Receipt message in the Cash Management business area (camt). The latest version is camt.025.001.09, and 5 versions are in the repository.

Message
Receipt
Latest version
camt.025.001.09
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.025 is for

The Receipt message is sent by a message recipient to the message sender. It is sent to acknowledge the receipt of one or multiple messages sent previously.

The Receipt message is an application receipt acknowledgement and conveys information about the processing of the original message(s).

The Receipt message is used when the exchange of messages takes place in an asynchronous manner.

This may happen, for instance, when an action is requested from the message sender (a deletion, modification or cancellation). The message sender will first acknowledge the request (with a Receipt message) and then execute it.

The message can contain information based on the following elements: reference of the message(s) it acknowledges, the status code (optional) and further explanation:

- reference of the message it acknowledges

- potentially, a status code and status reason information.

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

camt.025 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

VersionRegistration statusPublished in
camt.025.001.09latestRegisteredLatest version set
camt.025.001.08RegisteredPrevious version set
camt.025.001.07RegisteredArchive
camt.025.001.06RegisteredArchive
camt.025.001.05RegisteredArchive

camt.025 message structure

The building blocks of camt.025.001.09 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

  • Document [1..1]
    • Rct Receipt [1..1]
      • MsgHdr Message Header [1..1]MessageHeader9

        Common business identification for the message.

        • MsgId Message Identification [1..1]Max35Text

          Point to point reference, as assigned by the sender, to unambiguously identify the message.

        • CreDtTm Creation Date Time [0..1]ISODateTime

          Date and time at which the message was created.

        • ReqTp Request Type [0..1]RequestType4Choice (choice)

          Specific actions to be executed through the request.

          • PmtCtrl Payment Control [1..1]ExternalPaymentControlRequestType1Code
          • Enqry Enquiry [1..1]ExternalEnquiryRequestType1Code
          • Prtry Proprietary [1..1]GenericIdentification1
      • RctDtls Receipt Details [1..*]Receipt7

        Details of the receipt.

        • OrgnlMsgId Original Message Identification [1..1]OriginalMessageAndIssuer1

          Identification of the original request message.

          • MsgId Message Identification [1..1]Max35Text
          • MsgNmId Message Name Identification [0..1]Max35Text
          • OrgtrNm Originator Name [0..1]Max70Text
        • OrgnlPmtId Original Payment Identification [0..1]PaymentIdentification8Choice (choice)

          Identification of the original transaction identification, when the request for which the receipt is generated is a payment transaction.

          • TxId Transaction Identification [1..1]Max35Text
          • UETR UETR [1..1]UUIDv4Identifier
          • QId Queue Identification [1..1]QueueTransactionIdentification1
          • LngBizId Long Business Identification [1..1]LongPaymentIdentification4
          • ShrtBizId Short Business Identification [1..1]ShortPaymentIdentification4
          • PrtryId Proprietary Identification [1..1]Max70Text
        • ReqHdlg Request Handling [0..*]RequestHandling4

          Gives the status of the request.

          • Sts Status [1..1]RequestStatus1Choice (choice)
          • StsRsn Status Reason [0..1]StatusReasonInformation14
          • Desc Description [0..1]Max140Text
      • SplmtryData Supplementary Data [0..*]SupplementaryData1

        Additional information that cannot be captured in the structured elements and/or any other specific block.

        • PlcAndNm Place And Name [0..1]Max350Text

          Unambiguous reference to the location where the supplementary data must be inserted in the message instance.

        • Envlp Envelope [1..1]SupplementaryDataEnvelope1

          Technical element wrapping the supplementary data.

Have a camt.025 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

External code sets used in camt.025

These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.

camt.025 questions

What is the latest version of camt.025?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.025.001.09.
What is the root element of camt.025?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.025.001.09, and its message element is Rct (Receipt).
Is there an MT equivalent of camt.025?
No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.