camt: Cash Management
camt.024 Modify Standing Order
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
camt.024 is the ISO 20022 ModifyStandingOrder message in the Cash Management business area (camt). The latest version is camt.024.001.08, and 3 versions are in the repository.
- Message
- ModifyStandingOrder
- Latest version
- camt.024.001.08
- Submitting organisation
- Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What camt.024 is for
The ModifyStandingOrder message is sent by a member to the transaction administrator.
It is used to request a change in the features of a permanent order for the transfer of funds between two accounts belonging to the same member and being held at the transaction administrator.
There should be one standing order per (direct) member and per business day. The ModifyStandingOrder message must not be used to request a transfer of funds between accounts during the working day. The liquidity transfer messages must be used for this purpose. There is no need to have a standing order to empty the settlement account at the end of the day and transfer the funds to the current account. For liquidity savings purposes, systems will effect the necessary transfers automatically when and where relevant.
The ModifyStandingOrder message first identifies the standing order to be modified and then provide the details of the new standing order. The elements that can be modified are:
- amount
- account to be credited
- account to be debited
- account owner (for on behalf scenario)
- frequency of payment
- daytime or overnight processing
- dates when the standing order begins and ceases to be effective
Based on the criteria received within the ModifyStandingOrder message, the transaction administrator will execute or reject the requested modifications.
The transaction administrator may send a Receipt message as a reply to the Modify Standing Order request. To verify the outcome of the request, the member may submit a GetStandingOrder message with the appropriate search criteria.
camt.024 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.024.001.08latest | Registered | Latest version set |
| camt.024.001.07 | Registered | Previous version set |
| camt.024.001.06 | Registered | Archive |
camt.024 message structure
The building blocks of camt.024.001.08 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]ModfyStgOrdrModifyStandingOrder [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.
StgOrdrIdStanding Order Identification [1..1]StandingOrderIdentification8Identifies the standing order.
IdIdentification [0..1]Max35TextUnique and unambiguous identification for a standing order, as assigned by the account servicer or the account owner.
AcctAccount [1..1]CashAccount40Business relationship between two entities; one entity is the account owner, the other entity is the account servicer.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
AcctOwnrAccount Owner [0..1]BranchAndFinancialInstitutionIdentification8Party that legally owns the account.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
NewStgOrdrValSetNew Standing Order Value Set [1..1]StandingOrder10New set of values for the standing order.
AmtAmount [0..1]Amount2Choice (choice)Amount of money and currency to be transferred when a payment instruction is created as a result of a standing order.
AmtWthtCcyAmount Without Currency [1..1]ImpliedCurrencyAndAmountAmtWthCcyAmount With Currency [1..1]ActiveCurrencyAndAmount
CdtrCreditor [0..1]BranchAndFinancialInstitutionIdentification8Party to which an amount of money is due.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
CdtrAcctCreditor Account [0..1]CashAccount40Cash account credited from a standing order mechanism.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
DbtrDebtor [0..1]BranchAndFinancialInstitutionIdentification8Party that owes an amount of money to the (ultimate) creditor.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
DbtrAcctDebtor Account [0..1]CashAccount40Cash account debited from a standing order mechanism.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
ExctnTpExecution Type [0..1]ExecutionType1Choice (choice)Defines whether the standing order is executed through a time-based or an event-based trigger.
TmTime [1..1]ISOTimeEvtEvent [1..1]EventType1Choice (choice)
FrqcyFrequency [0..1]Frequency2CodeRegularity with which payment instructions are to be created and processed as a result of the standing order, such as daily, weekly, or monthly.
VldtyPrdValidity Period [0..1]DatePeriod2Choice (choice)Dates during which the standing order is in effect.
FrDtFrom Date [1..1]ISODateToDtTo Date [1..1]ISODateFrToDtFrom To Date [1..1]DatePeriod2
ZeroSweepIndZero Sweep Indicator [0..1]TrueFalseIndicatorIndicates whether the standing order is defined as a zero sweeping order.
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.024 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.024
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.024 questions
- What is the latest version of camt.024?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.024.001.08.
- What is the root element of camt.024?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.024.001.08, and its message element is ModfyStgOrdr (ModifyStandingOrder).
- Is there an MT equivalent of camt.024?
- 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.