Articles / Learning brief
The camt family: cash management and reporting
Your notes
In simple terms / 01
What this means in plain language
The camt (cash management) family reports on accounts and handles payment investigations. It includes intraday reports, end-of-day statements, entry notifications, and the cancellation-request and resolution messages used to recall payments and answer those requests.
The camt (cash management) family of ISO 20022 (International Organization for Standardization standard 20022) messages does two jobs: it tells account holders what has happened on their accounts, and it carries the questions and answers when a payment needs to be investigated or recalled. On the reporting side, camt.052 is an account report used during the day, camt.053 is the definitive end-of-day statement, and camt.054 notifies the holder of individual debit or credit entries in detail. On the investigation side, camt.056 is a request to cancel or recall a payment already sent, and camt.029 is the reply that resolves it, accepting or rejecting the request with a reason. Together these messages let a business see its cash position, reconcile incoming and outgoing payments against its own records, and follow the formal process for correcting a payment made in error. The reporting messages are structured, so entries can be matched by machine rather than read by eye.
Complete lesson / 02
Understand the full idea, step by step
Two very different jobs share one four-letter code. Every morning a business reads a bank statement to reconcile — routine, expected. Now and then someone has to ask a bank to undo a payment that already went out — an exception, handled carefully. In ISO 20022 both live in the same family: camt.
camt — cash management — an ISO 20022 business area
The camt family is broader than its name suggests. It carries the messages a bank uses to report on accounts, and the messages used to investigate and correct payments. Both concern the state of money in an account: one describes what has settled, the other asks to change something that has settled or is in flight. Reading the reporting messages is a daily rhythm; sending an investigation message is an exception that follows a defined process with time limits.
| Message | Name | Answers |
|---|---|---|
| camt.052 | Bank-to-Customer Account Report | What is happening now — an interim, provisional view during the day |
| camt.053 | Bank-to-Customer Statement | What finally happened today — the definitive end-of-day record |
| camt.054 | Bank-to-Customer Debit/Credit Notification | What makes up this entry — itemised detail, often splitting a bulk booking |
Why reporting sits here at all
Each reporting message carries structured entry information — amount, value date, counterparty, and structured remittance — so reconciliation software can match a credit to an outstanding invoice without a person reading narrative text. Because camt.053 is authoritative, most reconciliation treats it as the source of truth and uses camt.052 for earlier visibility and camt.054 for itemised breakdown. Choosing the right one is mostly a question of whether you need speed, finality, or detail.
The investigation pair: camt.056 and camt.029
When a payment must be undone, camt gives a formal exchange rather than an informal note. camt.056 is a Financial Institution to Financial Institution Payment Cancellation Request: the sending bank asks the receiving bank to cancel or return a payment, quoting the original references and a reason such as a duplicate or a technical error. camt.029, the Resolution of Investigation, is the reply that closes the request — reporting whether it was accepted or rejected, and why.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
This is Maya's request going out from Bank Alfa: it names the original payment by its references and states a reason. It asks Nordbank to act — it does not, and cannot, reverse the credit itself.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
And this is the answer coming back: the resolution that closes the case, telling Bank Alfa whether the cancellation was accepted or refused. Only now does Maya know the outcome.
WHAT IF — The sending bank needs a payment cancelled or returned after it has left
What happens: A camt.056 goes to the receiving bank as a request, not a command; the receiving bank checks whether the funds are still available and whether the beneficiary agrees to release them, then replies with a camt.029.
How it is handled: Funds are only returned through this traceable, auditable exchange. The receiving bank confirms what could be returned; time limits apply and reason codes come from a shared external list so both sides read them the same way. The exchange is the control working as intended — not a workaround around it.
STRICTLY SPEAKING
Strictly speaking, a recall cannot force a return. If the beneficiary has already been paid and does not agree, or the money is gone, the receiving bank may reject the request with a reason code. The exact time limits and reason values are set by the scheme and the current external code list, so a recall is best understood as a disciplined request whose success is never guaranteed.
FOR NOW, REMEMBER
- camt spans two jobs: reporting on accounts, and investigating or correcting payments.
- camt.052 is the interim report, camt.053 the definitive end-of-day statement, camt.054 the itemised notification.
- camt.056 requests a cancellation or return; camt.029 resolves it — accepted or rejected, with a reason.
- A recall is a request, not a command: funds return only through a traceable exchange, and may not return at all.
TRY IT YOURSELF
Maya sends a camt.056 to recall the duplicate EUR 12,400.00. An hour later a camt.029 comes back with a rejection: the beneficiary was already paid and will not agree to release the funds. What is the correct reading?
camt.053 lets software match a credit to an invoice without a person reading text — but only if the payment carried the right reference in the right place. That is structured remittance information.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
camt.052, camt.053, and camt.054 provide intraday reports, end-of-day statements, and detailed entry notifications respectively.
- 02
The camt.056 cancellation request and the camt.029 resolution form a matched pair for recalling a payment and answering that request.
- 03
Structured reporting lets a business reconcile payments and monitor its cash position by machine rather than by hand.
Practical use cases / 04
Where you would use this
A corporate treasury imports camt.053 end-of-day statements to reconcile the previous day's booked entries against its ledger.
An operations team monitors camt.052 intraday reports to track available balances before releasing large outgoing payments.
A payments investigations desk sends a camt.056 to recall a misdirected transfer and reads the camt.029 reply to learn whether funds were returned.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional company, Alder Freight Ltd, receives a camt.053 end-of-day statement from its bank, a fictional institution called Meridian Trust. The statement lists a closing booked balance of EUR 512,340.75 and 3 credit entries, one of which is a customer payment of EUR 18,900.00 carrying structured remittance that matches invoice INV-4471 automatically. Later that week Alder Freight discovers it paid a supplier twice, so Meridian Trust sends a camt.056 cancellation request for the duplicate of EUR 6,250.00. The receiving bank replies with a camt.029 resolution marked as accepted, and the EUR 6,250.00 is returned within 4 business days.
Evidence & review / 07
Evidence & review
ISO 20022 camt family generally; recall time limits and permitted reason codes are set by the applicable scheme and current external code list.
What this brief simplifies: Names the most common reporting and investigation messages rather than the full camt catalogue; scenario amounts are illustrative.
Sources for this brief3
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt.052/053/054, camt.056, camt.029 definitions
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority · Cancellation and resolution reason codes
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.