ZagTrader

camt: Cash Management

camt.012 Delete Limit

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

camt.012 is the ISO 20022 DeleteLimit message in the Cash Management business area (camt). The latest version is camt.012.001.08, and 2 versions are in the repository.

Message
DeleteLimit
Latest version
camt.012.001.08
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.012 is for

The DeleteLimit message is sent by a member to the transaction administrator.

It is used to request the deletion of one particular, several or all limits set by the member and managed by the transaction administrator.

The DeleteLimit message may delete several types of current limits (risk or liquidity management limit), based on a multiple requests.

The member will submit a DeleteLimit message identifying which limit(s) it wants to delete (current limit risk/liquidity limit concepts have been merged) based on following criteria:

- type of limit(s) (current/default)

- value of the limit(s) (default and/or current limit(s))

- identification of the counterparty (bilateral limit)

Based on the criteria received within the DeleteLimit message, the transaction administrator will execute or reject the requested modifications.

The transaction administrator may send a Receipt message as a reply to the DeleteLimit request.

To verify the outcome of the request, the member may submit a GetLimit message with the appropriate search criteria.

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

camt.012 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.012.001.08latestRegisteredLatest version set
camt.012.001.07RegisteredPrevious version set

camt.012 message structure

The building blocks of camt.012.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]
    • DelLmt DeleteLimit [1..1]
      • MsgHdr Message Header [1..1]MessageHeader1

        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.

      • LmtDtls Limit Details [1..1]LimitStructure3Choice (choice)

        Identifies one particular limit set by the member and managed by the transaction administrator.

        • CurLmtId Current Limit Identification [1..1]LimitIdentification8

          Identification of the current limit.

          • SysId System Identification [0..1]SystemIdentification2Choice (choice)
          • BilLmtCtrPtyId Bilateral Limit Counterparty Identification [0..1]BranchAndFinancialInstitutionIdentification8
          • Tp Type [1..1]LimitType1Choice (choice)
          • AcctOwnr Account Owner [0..1]BranchAndFinancialInstitutionIdentification8
          • AcctId Account Identification [0..1]AccountIdentification4Choice (choice)
        • AllCurLmts All Current Limits [1..1]LimitIdentification9

          Identification of the current limit.

          • SysId System Identification [0..1]SystemIdentification2Choice (choice)
          • Tp Type [1..1]LimitType1Choice (choice)
          • AcctOwnr Account Owner [0..1]BranchAndFinancialInstitutionIdentification8
          • AcctId Account Identification [0..1]AccountIdentification4Choice (choice)
      • 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.012 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.012

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

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