ZagTrader

camt: Cash Management

camt.010 Return Limit

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

camt.010 is the ISO 20022 ReturnLimit message in the Cash Management business area (camt). The latest version is camt.010.001.09, and 2 versions are in the repository.

Message
ReturnLimit
Latest version
camt.010.001.09
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.010 is for

The ReturnLimit message is sent by the transaction administrator to a member of the system.

It is used to provide information on the details of one or more limits set by the member (or on behalf of the member) and managed by the transaction administrator.

The ReturnLimit message can be sent as a response to a related GetLimit message (pull mode) or initiated by the transaction administrator (push mode). The push of information can take place either at prearranged times or as a warning or alarm when a problem has occurred.

At any time during the operating hours of the system, the member can query the transaction administrator to get information about the limit(s) that the transaction administrator manages for the member.

The transaction administrator may also send a ReturnLimit message with pre-defined information at times previously agreed with the member or to warn the member about a particular problem that may have arisen and which needs attention.

The message from the transaction administrator can contain information on the following elements:

- type of risk and/or liquidity limit

- value of the limit(s) (default and/or current limit(s) for risk and/or liquidity management)

- identification of the system

- status of the limit(s) (default and/or current limit(s) for risk and/or liquidity management)

- point in time when the limit becomes effective

- identification of the counterparty

Additional information on the generic design of the Get/Return messages can be found in the section How to Use the Cash Management Messages.

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

camt.010 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.010.001.09latestRegisteredLatest version set
camt.010.001.08RegisteredPrevious version set

camt.010 message structure

The building blocks of camt.010.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]
    • RtrLmt ReturnLimit [1..1]
      • MsgHdr Message Header [1..1]MessageHeader7

        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
        • 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.

      • RptOrErr Report Or Error [1..1]LimitReportOrError5Choice (choice)

        Reports on limits.

        • BizRpt Business Report [1..1]Limits8

          Reports on limits.

          • CurLmt Current Limit [0..*]LimitReport8
          • DfltLmt Default Limit [0..*]LimitReport8
        • 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.010 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.010

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

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