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.
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.
| Version | Registration status | Published in |
|---|---|---|
| camt.050.001.07latest | Registered | Latest version set |
| camt.050.001.06 | Registered | Previous version set |
| camt.050.001.05 | Registered | Archive |
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]LqdtyCdtTrfLiquidityCreditTransfer [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.
LqdtyCdtTrfLiquidity Credit Transfer [1..1]LiquidityCreditTransfer4Details of the liquidity credit transfer.
LqdtyTrfIdLiquidity Transfer Identification [0..1]PaymentIdentification8Used to uniquely identify the liquidity transfer.
InstrIdInstruction Identification [0..1]Max35TextEndToEndIdEnd To End Identification [1..1]Max35TextTxIdTransaction Identification [0..1]Max35TextUETRUETR [0..1]UUIDv4Identifier
CdtrCreditor [0..1]BranchAndFinancialInstitutionIdentification8Owner of the account to be credited.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
CdtrAcctCreditor Account [0..1]CashAccount40Account to be credited as a result of a transfer of liquidity.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
TrfdAmtTransferred Amount [1..1]Amount2Choice (choice)Amount of money that the transaction administrator transfers from one account to another.
AmtWthtCcyAmount Without Currency [1..1]ImpliedCurrencyAndAmountAmtWthCcyAmount With Currency [1..1]ActiveCurrencyAndAmount
DbtrDebtor [0..1]BranchAndFinancialInstitutionIdentification8Owner of the account to be debited.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
DbtrAcctDebtor Account [0..1]CashAccount40Account to be debited as a result of a transfer of liquidity.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
SttlmDtSettlement Date [0..1]ISODateDate 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...
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.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.