What is the latest version of camt.005?

The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.005.001.11.

What is the root element of camt.005?

The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.005.001.11, and its message element is GetTx (GetTransaction).

Is there an MT equivalent of camt.005?

No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

camt: Cash Management

camt.005 Get Transaction

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

camt.005 is the ISO 20022 GetTransaction message in the Cash Management business area (camt). The latest version is camt.005.001.11, and 4 versions are in the repository.

Message: GetTransaction
Latest version: camt.005.001.11
Submitting organisation: Swift
MT equivalent: None listed

In use: published in the current ISO 20022 catalogue.

What camt.005 is for

The GetTransaction message is sent by a member to the transaction administrator.
It is used to request information about payment instructions held at the transaction administrator. Payment instructions are either sent by the member, debiting or crediting its account at the transaction administrator or received by the transaction administrator, crediting or debiting the member's account.
Following normal business flows, transactions registered by the transaction administrator may be queued for later settlement (because of insufficient funds available, or because of risk or liquidity limits, etc.). A transaction may have a series of statuses. These can be transient (such as pending or related types) and final (such as rejected, revoked and/or settled).
Members of a system need to have information about the payments queue(s) and must have the ability to take action (that is, to cancel or modify the transaction(s) to be settled). Note, however, that actions by a member will always concern transactions in a transient status.
At any time during the operating hours of the system, the member can query the transaction administrator to get information about transactions, whatever their status.
These requests will concern either all transactions, all transactions with a particular status or a specific transaction.
The member can request information about transactions through a series of criteria, corresponding to the known information stored at the transaction administrator, based on the following elements:
- provenance or destination of the payment (payment to/payment from)
- transaction reference
- transfer value date
- payment instruction reference
- payment instruction status, as registered at the transaction administrator
- instructed amount and/or currency

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

camt.005 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.

Version	Registration status	Published in
camt.005.001.11latest	Registered	Latest version set
camt.005.001.10	Registered	Previous version set
camt.005.001.09	Registered	Archive
camt.005.001.08	Registered	Archive

camt.005 message structure

The building blocks of camt.005.001.11 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]
- GetTx GetTransaction [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
  - TxQryDef Transaction Query Definition [0..1]TransactionQuery8
    Defines the transaction query criteria.
    - QryTp Query Type [0..1]QueryType2Code
      Specifies the type of matching items to be returned in the response to the query.
    - TxCrit Transaction Criteria [0..1]TransactionCriteria8Choice (choice)
      Defines the payment transaction query criteria.
      - QryNm Query Name [1..1]Max35Text
      - NewCrit New Criteria [1..1]TransactionCriteria11
  - 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.005 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.005

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.005 questions

What is the latest version of camt.005?: The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.005.001.11.
What is the root element of camt.005?: The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.005.001.11, and its message element is GetTx (GetTransaction).
Is there an MT equivalent of camt.005?: 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.