| Field | Meaning | Required |
|---|---|---|
GrpHdr | The header holding message identification, creation date and time and the instructing agent. It identifies the liquidity transfer for tracking and duplicate det | M |
DbtrAcct | The account from which liquidity is moved, identified by IBAN or other account identification. It tells the receiving system exactly which account to debit. A w | M |
CdtrAcct | The account to which liquidity is moved, identified by IBAN or other account identification. It tells the receiving system exactly which account to credit. The | M |
TrfdAmt | The amount and currency of the liquidity transfer, for example EUR 5,000,000.00. It is the amount moved between the two accounts. The amount must not exceed the | M |
ExctnDt | The date on which the liquidity transfer is executed. It is normally the same business day the instruction is sent. The date drives the value dating of both acc | M |
DbtrAgt | The bank holding the debtor account and instructing the transfer, identified by BIC. It is responsible for checking the source balance, applying the debit and s | M |
CdtrAgt | The bank holding the creditor account, identified by BIC. It receives the instruction, checks the destination account and applies the credit. In most camt.050 f | M |
Purp | The purpose of the liquidity transfer, using a coded value such as a funding transfer or a sweep. Purpose codes support treasury reporting and help the bank cla | O |
AddtlInf | Additional information about the transfer, such as the treasury instruction reference or a narrative description. It can carry the reference the treasury team u | O |
InstrId | The identification of the liquidity transfer instruction, assigned by the instructing treasury team. It lets the treasury system track the transfer through exec | M |
EndToEndId | The end to end identification for the transfer, which stays unchanged through the whole movement. It lets the treasury team and both account systems refer to th | O |
ChrgsInf | Charges applied to the liquidity transfer, when the bank charges for the internal movement. It can show the amount and bearer of the fee. Treasury uses it to re | O |
Meridian Bank treasury sends a camt.050 to move EUR 5,000,000.00 from its central euro account to its nostro account at Harbour Bank on 6 November 2026, funding the afternoon payment run. The source balance is sufficient, the destination is an internal nostro account, and both accounts update at once on execution.
Valid example from the message catalogue. Scheme rules: camt.050 is the base ISO 20022 liquidity transfer message, used mainly for internal treasury movements with no external scheme rulebook. CBPR+ does not define a liquidity scheme, so banks apply their
camt.050, camt.025 and camt.054, A2A and U2A Modes, TIPS DCA vs TIPS AS Technical Account
What you will learn
Your objective. By the end of this lesson, you will be able to explain camt.050, camt.025 and camt.054, a2a and u2a modes, TIPS DCA vs TIPS as technical account. The camt.050 Liquidity Credit Transfer message is the instruction that starts a liquidity transfer in TIPS.
Why it matters. The camt.025 is therefore the receipt that closes the instruction, and operations teams match every camt.050 to its camt.025 before they treat a liquidity transfer as complete.
Chapter objective: Learner explains TIPS instant payments and liquidity transfers, describes SCT Inst, Non-Euro and SIP flows, and distinguishes TIPS DCA, AS Technical Account and Transit Accounts. Learner uses real amounts, banks and message names to show how instant payments and liquidity transfers work.
Key learning points
- Camt.050 Liquidity Credit Transfer message
- Camt.025 Receipt message
- Camt.054 Bank to Customer Debit Credit Notification
- TIPS supports two modes of access
- TIPS DCA and the TIPS AS Technical
- Account type has its own
Key terms
Liquidity transfer: A movement of funds between accounts held by the same participant to manage liquidity, for example from a main cash account to a dedicated cash account.
Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
ISO 20022 XML explorer showing camt.050, camt.025 and camt.054, A2A and U2A Modes, TIPS DCA vs TIPS AS Technical Account.
Practise this lesson
Exercise
Read the camt.050 message described in this lesson and identify its key parts.
Use the message structure, fields and example in this lesson.
- What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.
Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.
Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.
Check your understanding
Practice question
Which of the following best describes camt.050, camt.025 and camt.054, a2a and u2a modes, TIPS DCA vs TIPS as technical account?
Takeaway and next step
What to remember
Each account type has its own rules, its own holder, and its own purpose, and the system enforces that separation.
Follow EUR 1 through every stage, from instruction to beneficiary credit, and note where it can stop.
Open the Payment Lifecycle Simulator →
Builds on "Liquidity Transfers in TIPS: The Deposit Model and the Three Basic Rules".
Transcript and full text
Show transcript
The camt.050 Liquidity Credit Transfer message is the instruction that starts a liquidity transfer in TIPS. When a bank wants to move EUR 1 million from its TARGET main cash account to its TIPS DCA, it sends a camt.050 with the source account, the destination account, the amount, and the currency. The camt.050 is the order, and it is the message that TIPS and TARGET validate before any money moves. A bank that sends a camt.050 with the wrong account number, the wrong currency, or an amount above its available balance will see the transfer rejected, and the rejection will be reported back so the bank can correct the instruction and try again. The camt.025 Receipt message is the confirmation that answers a camt.050, and it tells the instructing bank whether the liquidity transfer settled or was rejected. A camt.025 with a settled status confirms that the EUR 1 million has moved from the main cash account to the TIPS DCA, and the bank can now use that liquidity for instant payments. A camt.025 with a rejected status gives the reason code, such as insufficient funds, so the bank knows what went wrong. The camt.025 is therefore the receipt that closes the instruction, and operations teams match every camt.050 to its camt.025 before they treat a liquidity transfer as complete. The camt.054 Bank to Customer Debit Credit Notification is the notification that tells an account holder that its account has been debited or credited. After a liquidity transfer settles, TIPS sends a camt.054 to the holder of the debited account and to the holder of the credited account, so both sides can update their records. For example, after a EUR 500,000 transfer from a TARGET main cash account to a TIPS DCA, the bank receives a camt.054 for the debit to the main account and a camt.054 for the credit to the TIPS DCA. Those notifications feed the bank reconciliation, and they are the evidence that the liquidity position has changed. TIPS supports two modes of access, known as A2A and U2A, and the difference is about who sends the message. A2A means application to application, and it is the automated mode, where the bank system sends camt.050 messages directly to TIPS and receives camt.025 and camt.054 messages back without human intervention. U2A means user to application, and it is the manual mode, where a user logs into the TIPS graphical interface, types the liquidity transfer details into a screen, and submits the transfer by hand. Large banks use A2A for the thousands of transfers they send every day, while smaller banks and contingency operators use U2A for occasional transfers and for manual intervention when automation fails. The TIPS DCA and the TIPS AS Technical Account are two different account types, and confusing them causes errors. A TIPS DCA is a Dedicated Cash Account held by a TIPS participant, such as a bank, and it holds the liquidity that the participant uses to settle instant payments. A TIPS AS Technical Account is an account held by an ancillary system, such as a clearing house or a securities settlement system, and it is used for the technical settlement of that system transactions in TIPS. A bank cannot use a TIPS AS Technical Account as if it were its own TIPS DCA, and an ancillary system cannot use a TIPS DCA for its technical settlement. Each account type has its own rules, its own holder, and its own purpose, and the system enforces that separation.
The camt.050 Liquidity Credit Transfer message is the instruction that starts a liquidity transfer in TIPS. When a bank wants to move EUR 1 million from its TARGET main cash account to its TIPS DCA, it sends a camt.050 with the source account, the destination account, the amount, and the currency. The camt.050 is the order, and it is the message that TIPS and TARGET validate before any money moves. A bank that sends a camt.050 with the wrong account number, the wrong currency, or an amount above its available balance will see the transfer rejected, and the rejection will be reported back so the bank can correct the instruction and try again.
The camt.025 Receipt message is the confirmation that answers a camt.050, and it tells the instructing bank whether the liquidity transfer settled or was rejected. A camt.025 with a settled status confirms that the EUR 1 million has moved from the main cash account to the TIPS DCA, and the bank can now use that liquidity for instant payments. A camt.025 with a rejected status gives the reason code, such as insufficient funds, so the bank knows what went wrong. The camt.025 is therefore the receipt that closes the instruction, and operations teams match every camt.050 to its camt.025 before they treat a liquidity transfer as complete.
The camt.054 Bank to Customer Debit Credit Notification is the notification that tells an account holder that its account has been debited or credited. After a liquidity transfer settles, TIPS sends a camt.054 to the holder of the debited account and to the holder of the credited account, so both sides can update their records. For example, after a EUR 500,000 transfer from a TARGET main cash account to a TIPS DCA, the bank receives a camt.054 for the debit to the main account and a camt.054 for the credit to the TIPS DCA. Those notifications feed the bank reconciliation, and they are the evidence that the liquidity position has changed.
TIPS supports two modes of access, known as A2A and U2A, and the difference is about who sends the message. A2A means application to application, and it is the automated mode, where the bank system sends camt.050 messages directly to TIPS and receives camt.025 and camt.054 messages back without human intervention. U2A means user to application, and it is the manual mode, where a user logs into the TIPS graphical interface, types the liquidity transfer details into a screen, and submits the transfer by hand. Large banks use A2A for the thousands of transfers they send every day, while smaller banks and contingency operators use U2A for occasional transfers and for manual intervention when automation fails.
The TIPS DCA and the TIPS AS Technical Account are two different account types, and confusing them causes errors. A TIPS DCA is a Dedicated Cash Account held by a TIPS participant, such as a bank, and it holds the liquidity that the participant uses to settle instant payments. A TIPS AS Technical Account is an account held by an ancillary system, such as a clearing house or a securities settlement system, and it is used for the technical settlement of that system transactions in TIPS. A bank cannot use a TIPS AS Technical Account as if it were its own TIPS DCA, and an ancillary system cannot use a TIPS DCA for its technical settlement. Each account type has its own rules, its own holder, and its own purpose, and the system enforces that separation.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.