ZagTrader

camt: Cash Management

camt.070 Return Standing Order

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

camt.070 is the ISO 20022 ReturnStandingOrder message in the Cash Management business area (camt). The latest version is camt.070.001.06, and 3 versions are in the repository.

Message
ReturnStandingOrder
Latest version
camt.070.001.06
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.070 is for

The ReturnStandingOrder message is sent by a transaction administrator to a member.

It is used to provide information on the details of one or more standing orders, based on specific request and return criteria.

in response to a request a on information on standing and predefined orders.

The ReturnStandingOrder message lists the standing order based on the following possible return criteria:

- Generic standing order details,

- Details of a specific predefined or standing liquidity transfer orders,

- Details on the set to which the standing order belongs to,

- List of all predefined and standing liquidity transfer standing orders and/or per set,

- Total amount of predefined and standing liquidity transfer orders defined in the system.

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

camt.070 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.070.001.06latestRegisteredLatest version set
camt.070.001.05RegisteredPrevious version set
camt.070.001.04RegisteredArchive

camt.070 message structure

The building blocks of camt.070.001.06 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]
    • RtrStgOrdr ReturnStandingOrder [1..1]
      • MsgHdr Message Header [1..1]MessageHeader6

        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.

        • OrgnlBizQry Original Business Query [0..1]OriginalBusinessQuery1

          Unique identification of the original query message.

          • MsgId Message Identification [1..1]Max35Text
          • MsgNmId Message Name Identification [0..1]Max35Text
          • CreDtTm Creation Date Time [0..1]ISODateTime
        • QryNm Query Name [0..1]Max35Text

          Recalls the criteria (search and return criteria) defined in a preceding query.

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

          Specific actions to be executed through the request.

          • Cd Code [1..1]StandingOrderQueryType1Code
          • Prtry Proprietary [1..1]GenericIdentification1
      • RptOrErr Report Or Error [1..1]StandingOrderOrError9Choice (choice)

        Reports on standing orders.

        • Rpt Report [1..*]StandingOrderReport3

          Reports either on the standing order or on a business error.

          • StgOrdrId Standing Order Identification [1..1]StandingOrderIdentification8
          • StgOrdrOrErr Standing Order Or Error [1..1]StandingOrderOrError10Choice (choice)
        • OprlErr Operational Error [1..*]ErrorHandling5

          Indicates that an operational error has been issued during the processing of the related request.

          • Err Error [1..1]ErrorHandling3Choice (choice)
          • 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.070 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.070

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

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