ZagTrader

camt: Cash Management

camt.050 Liquidity Credit Transfer

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

camt.050 is the ISO 20022 LiquidityCreditTransfer message in the Cash Management business area (camt). The latest version is camt.050.001.07, and 3 versions are in the repository.

Message
LiquidityCreditTransfer
Latest version
camt.050.001.07
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.050 is for

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

It is used to request a transfer of funds between two accounts belonging to the same member or the same group of accounts, and being held at the transaction administrator.

At any time during the operating hours of the system, and to perform the appropriate liquidity management, the member can request the transaction administrator to execute the transfer of funds between two accounts that the transaction administrator maintains for the member. For instance, this may be an action resulting from a Get/Return Account pair of messages.

The LiquidityCreditTransfer message can be used when the transactions to/from the member are unbalanced in value for the business day, or to unlock pending transactions at the end of day.

The member can request the transfer by identifying the accounts stored at the transaction administrator:

- If the accounts involved in the requested transfer are known without doubt to the transaction administrator, it is possible to indicate only the type of the account to be credited.

- If, on the contrary, more clarity is desired, it is possible to identify the accounts from and to which the funds should be transferred.

Note that transfers are processed only when the balance in the account to be debited is sufficient to pass the liquidity transfer instruction and remain positive. Based on the criteria received within the LiquidityCreditTransfer message, the transaction administrator will execute or reject the requested transfer.

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

camt.050 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.050.001.07latestRegisteredLatest version set
camt.050.001.06RegisteredPrevious version set
camt.050.001.05RegisteredArchive

camt.050 message structure

The building blocks of camt.050.001.07 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]
    • LqdtyCdtTrf LiquidityCreditTransfer [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.

      • LqdtyCdtTrf Liquidity Credit Transfer [1..1]LiquidityCreditTransfer4

        Details of the liquidity credit transfer.

        • LqdtyTrfId Liquidity Transfer Identification [0..1]PaymentIdentification8

          Used to uniquely identify the liquidity transfer.

          • InstrId Instruction Identification [0..1]Max35Text
          • EndToEndId End To End Identification [1..1]Max35Text
          • TxId Transaction Identification [0..1]Max35Text
          • UETR UETR [0..1]UUIDv4Identifier
        • Cdtr Creditor [0..1]BranchAndFinancialInstitutionIdentification8

          Owner of the account to be credited.

          • FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
          • BrnchId Branch Identification [0..1]BranchData5
        • CdtrAcct Creditor Account [0..1]CashAccount40

          Account to be credited as a result of a transfer of liquidity.

          • Id Identification [0..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • TrfdAmt Transferred Amount [1..1]Amount2Choice (choice)

          Amount of money that the transaction administrator transfers from one account to another.

          • AmtWthtCcy Amount Without Currency [1..1]ImpliedCurrencyAndAmount
          • AmtWthCcy Amount With Currency [1..1]ActiveCurrencyAndAmount
        • Dbtr Debtor [0..1]BranchAndFinancialInstitutionIdentification8

          Owner of the account to be debited.

          • FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
          • BrnchId Branch Identification [0..1]BranchData5
        • DbtrAcct Debtor Account [0..1]CashAccount40

          Account to be debited as a result of a transfer of liquidity.

          • Id Identification [0..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • SttlmDt Settlement Date [0..1]ISODate

          Date on which the amount of money ceases to be available to the agent that owes it and when the amount of money becomes available to the agent to...

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

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

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