Flow of the explanation in this lesson.
Customer Reporting and the SEPA 2024 Transition to 2019 Messages
What you will learn
Your objective. By the end of this lesson, you will be able to explain customer reporting and the SEPA 2024 transition to 2019 messages. Customer reporting in SEPA uses the camt family, and each message has a distinct job.
Why it matters. The migration work behind a message version change is larger than it looks, and a business analyst should plan for it explicitly.
Chapter objective: Message flows, exchange periods and the 2024 transition
Key learning points
- Customer reporting in SEPA
- Account view from three messages
- Structured party addresses
- Version 09
- Migration work behind a message version
Key terms
Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.
Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.
ISO 20022: An international standard for financial messaging that defines XML message formats for payments, securities and trade.
Payment flow diagram showing Customer Reporting and the SEPA 2024 Transition to 2019 Messages.
Practise this lesson
Exercise
Read the camt family 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 customer reporting and the SEPA 2024 transition to 2019 messages?
Takeaway and next step
What to remember
For the 2024 transition, most banks ran a period of dual acceptance, then closed the old version, and they kept a help desk ready for customers whose files failed validation in the first weeks after the change.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "Exceptions and Investigations: camt.056, camt.029 and pacs.004 Returns".
Transcript and full text
Show transcript
Customer reporting in SEPA uses the camt family, and each message has a distinct job. The camt.052.001.08 Bank to Customer Account Report gives intraday balance and transaction information, so a treasurer can see the EUR 48,250 debit during the day it happens. The camt.053.001.08 Bank to Customer Statement gives the end of day statement, with the full list of entries, balances, and references for reconciliation. The camt.054.001.08 Bank to Customer Debit Credit Notification reports a single debit or credit as it happens, which is useful for a supplier waiting for a specific payment. Together, these three messages give the customer a complete view of its account without a phone call to the bank. The SEPA 2024 transition moved the SCT and SDD schemes to the 2019 version of the ISO 20022 messages, and the change took effect in November 2023 for most participants, with the full migration completed during 2024. The 2019 versions brought structured addresses, richer remittance information, and clearer identification of the ultimate debtor and ultimate creditor. For a payment like the EUR 48,250 from Loire Components to Rhine Metals, the 2019 messages carry the full postal address of both parties in structured fields, rather than in free text lines that systems cannot parse reliably. The transition also aligned SEPA messages with the global ISO 20022 migration, so a payment could move between SEPA and other networks with fewer conversions. The focus of the transition for customer initiation was pain.001.001.09, which replaced pain.001.001.03 as the standard version for SEPA payments. Version 09 carries the structured address fields, the ultimate debtor and ultimate creditor elements, and the updated service level and purpose codes that the 2019 definitions require. A corporate that still sent pain.001.001.03 after the migration date would have its files rejected, or would have its payments processed with missing data that could fail downstream screening. Banks had to update their validation rules, their mapping tables, and their customer onboarding guides, and they had to test the new version with their largest corporate customers before the cutover date. The migration work behind a message version change is larger than it looks, and a business analyst should plan for it explicitly. The bank must update its message schemas, change its validation rules, remap fields that moved or changed format, update its customer documentation, and run parallel testing with corporates and with the clearing system. It must also decide how to handle the cutover, whether to accept both versions for a short period or to switch on a single date. For the 2024 transition, most banks ran a period of dual acceptance, then closed the old version, and they kept a help desk ready for customers whose files failed validation in the first weeks after the change. Worked example with numbers: on the day the EUR 48,250 payment is debited, the Loire Components treasurer checks the camt.052.001.08 intraday report and sees the debit of EUR 48,250 with the value date, the end to end identification and the Rhine Metals name, so the treasurer knows the payment has left the account before the end of the day. The next morning the treasurer downloads the camt.053.001.08 statement, which shows the opening balance, the EUR 48,250 debit, the closing balance, and every other transaction for the day, and reconciles the statement against the company ledger by matching the end to end identification. If the statement shows a debit the treasurer does not recognise, the treasurer raises a query with the bank the same day Failure and recovery: customer reporting fails when the statement is late, when a transaction is missing, or when the message version is wrong. If the bank sends a camt.053 in version 02 to a customer system that expects version 08, the customer cannot read the statement, and the reconciliation fails. The recovery is a corrected statement in the right version, but the treasurer has lost a day, and the month end close may slip. If a transaction is missing from the statement, the treasurer must ask the bank for a camt.052 intraday report to find it, and the bank must explain why it was omitted. A bank must therefore test its statement generation with every customer system version it supports, because a statement that cannot be read is a statement that has not been delivered. For a business analyst, product owner or subject matter expert, the reporting requirement must state which camt messages the bank sends, camt.052 for intraday, camt.053 for end of day, and camt.054 for debit and credit notifications, and must state the version of each one. The requirement must also state the 2019 message versions, pain.001.001.09, pacs.008.001.08 and camt.053.001.08, because the SEPA 2024 transition moved the schemes to those versions, and a customer system that still expects the 2009 versions will fail. The test pack must include a statement with a missing transaction, one in the wrong version, and a reconciliation that breaks. Source: EPC SCT Rulebook 2025; ISO 20022 camt.053.001.08 last reviewed 7 November 2026.
Customer reporting in SEPA uses the camt family, and each message has a distinct job. The camt.052.001.08 Bank to Customer Account Report gives intraday balance and transaction information, so a treasurer can see the EUR 48,250 debit during the day it happens. The camt.053.001.08 Bank to Customer Statement gives the end of day statement, with the full list of entries, balances, and references for reconciliation. The camt.054.001.08 Bank to Customer Debit Credit Notification reports a single debit or credit as it happens, which is useful for a supplier waiting for a specific payment. Together, these three messages give the customer a complete view of its account without a phone call to the bank.
The SEPA 2024 transition moved the SCT and SDD schemes to the 2019 version of the ISO 20022 messages, and the change took effect in November 2023 for most participants, with the full migration completed during 2024. The 2019 versions brought structured addresses, richer remittance information, and clearer identification of the ultimate debtor and ultimate creditor. For a payment like the EUR 48,250 from Loire Components to Rhine Metals, the 2019 messages carry the full postal address of both parties in structured fields, rather than in free text lines that systems cannot parse reliably. The transition also aligned SEPA messages with the global ISO 20022 migration, so a payment could move between SEPA and other networks with fewer conversions.
The focus of the transition for customer initiation was pain.001.001.09, which replaced pain.001.001.03 as the standard version for SEPA payments. Version 09 carries the structured address fields, the ultimate debtor and ultimate creditor elements, and the updated service level and purpose codes that the 2019 definitions require. A corporate that still sent pain.001.001.03 after the migration date would have its files rejected, or would have its payments processed with missing data that could fail downstream screening. Banks had to update their validation rules, their mapping tables, and their customer onboarding guides, and they had to test the new version with their largest corporate customers before the cutover date.
The migration work behind a message version change is larger than it looks, and a business analyst should plan for it explicitly. The bank must update its message schemas, change its validation rules, remap fields that moved or changed format, update its customer documentation, and run parallel testing with corporates and with the clearing system. It must also decide how to handle the cutover, whether to accept both versions for a short period or to switch on a single date. For the 2024 transition, most banks ran a period of dual acceptance, then closed the old version, and they kept a help desk ready for customers whose files failed validation in the first weeks after the change.
Worked example with numbers: on the day the EUR 48,250 payment is debited, the Loire Components treasurer checks the camt.052.001.08 intraday report and sees the debit of EUR 48,250 with the value date, the end to end identification and the Rhine Metals name, so the treasurer knows the payment has left the account before the end of the day. The next morning the treasurer downloads the camt.053.001.08 statement, which shows the opening balance, the EUR 48,250 debit, the closing balance, and every other transaction for the day, and reconciles the statement against the company ledger by matching the end to end identification. If the statement shows a debit the treasurer does not recognise, the treasurer raises a query with the bank the same day
Failure and recovery: customer reporting fails when the statement is late, when a transaction is missing, or when the message version is wrong. If the bank sends a camt.053 in version 02 to a customer system that expects version 08, the customer cannot read the statement, and the reconciliation fails. The recovery is a corrected statement in the right version, but the treasurer has lost a day, and the month end close may slip. If a transaction is missing from the statement, the treasurer must ask the bank for a camt.052 intraday report to find it, and the bank must explain why it was omitted. A bank must therefore test its statement generation with every customer system version it supports, because a statement that cannot be read is a statement that has not been delivered.
For a business analyst, product owner or subject matter expert, the reporting requirement must state which camt messages the bank sends, camt.052 for intraday, camt.053 for end of day, and camt.054 for debit and credit notifications, and must state the version of each one. The requirement must also state the 2019 message versions, pain.001.001.09, pacs.008.001.08 and camt.053.001.08, because the SEPA 2024 transition moved the schemes to those versions, and a customer system that still expects the 2009 versions will fail. The test pack must include a statement with a missing transaction, one in the wrong version, and a reconciliation that breaks. Source: EPC SCT Rulebook 2025; ISO 20022 camt.053.001.08 last reviewed 7 November 2026.
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.