camt: Cash Management
camt.007 Modify Transaction
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
camt.007 is the ISO 20022 ModifyTransaction message in the Cash Management business area (camt). The latest version is camt.007.001.10, and 5 versions are in the repository.
- Message
- ModifyTransaction
- Latest version
- camt.007.001.10
- Submitting organisation
- Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What camt.007 is for
The ModifyTransaction message is sent by a member to the transaction administrator.
It is used to request one modification in one payment instruction held at the transaction administrator and sent by the member, debiting or crediting its account at the transaction administrator.
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.
For this reason, at any time during the operating hours of the system, the member can request modifications to the features of transient transactions.
The member will submit a message requesting modifications in one or more of the following criteria:
- instruction given, related to the processing of the transaction
- type of payment instructed
- priority of payment period in which the payment instruction should be processed (processing validity time)
The ModifyTransaction message will contain the new values that the member wants to see applied to the features of the transaction identified in the message.
Based on the criteria received within the ModifyTransaction message, the transaction administrator will execute or reject the requested modifications.
camt.007 versions
Every version published in the e-Repository, newest first. Variant 001 and 002 are listed together: a variant other than 001 is a restricted form of the same message with its own schema.
| Version | Registration status | Published in |
|---|---|---|
| camt.007.002.03 | Registered | Archive |
| camt.007.002.01 | Registered | Archive |
| camt.007.001.10latest | Registered | Latest version set |
| camt.007.001.09 | Registered | Previous version set |
| camt.007.001.08 | Registered | Archive |
camt.007 message structure
The building blocks of camt.007.001.10 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]ModfyTxModifyTransaction [1..1]MsgHdrMessage Header [1..1]MessageHeader1Common business identification for the message.
MsgIdMessage Identification [1..1]Max35TextPoint to point reference, as assigned by the sender, to unambiguously identify the message.
CreDtTmCreation Date Time [0..1]ISODateTimeDate and time at which the message was created.
ModModification [1..*]TransactionModification7Identifies the list of modifications to be executed.
PmtIdPayment Identification [1..1]PaymentIdentification8Choice (choice)Reference to the instruction related to the payment for which a modification is requested.
TxIdTransaction Identification [1..1]Max35TextUETRUETR [1..1]UUIDv4IdentifierQIdQueue Identification [1..1]QueueTransactionIdentification1LngBizIdLong Business Identification [1..1]LongPaymentIdentification4ShrtBizIdShort Business Identification [1..1]ShortPaymentIdentification4PrtryIdProprietary Identification [1..1]Max70Text
NewPmtValSetNew Payment Value Set [1..1]PaymentInstruction33New payment values.
InstrInstruction [0..1]Instruction1CodeTpType [0..1]PaymentType4Choice (choice)PrtyPriority [0..1]Priority1Choice (choice)PrcgVldtyTmProcessing Validity Time [0..1]DateTimePeriod1Choice (choice)
SplmtryDataSupplementary Data [0..*]SupplementaryData1Additional information that cannot be captured in the structured elements and/or any other specific block.
PlcAndNmPlace And Name [0..1]Max350TextUnambiguous reference to the location where the supplementary data must be inserted in the message instance.
EnvlpEnvelope [1..1]SupplementaryDataEnvelope1Technical element wrapping the supplementary data.
Have a camt.007 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.007
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.007 questions
- What is the latest version of camt.007?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.007.001.10.
- What is the root element of camt.007?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.007.001.10, and its message element is ModfyTx (ModifyTransaction).
- Is there an MT equivalent of camt.007?
- 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.