Camt.052 vs Camt.053 vs Camt.054: What's the Difference?
A complete comparison of the three main ISO 20022 cash management report formats: camt.052 (intraday statement), camt.053 (end-of-day statement), and camt.054 (debit/credit notification). When to use each and how they relate to legacy MT formats.
Overview: The Three ISO 20022 Bank Reporting Messages
ISO 20022 defines three cash management messages for bank-to-customer reporting: camt.052 (BankToCustomerAccountReport), camt.053 (BankToCustomerStatement), and camt.054 (BankToCustomerDebitCreditNotification). These three messages collectively replace the legacy SWIFT MT format equivalents (MT940, MT942, MT900/MT910) and provide significantly richer transaction data for automated cash management and reconciliation.
The key distinction is timing and granularity. camt.052 provides intraday reports on an as-needed basis, allowing treasury teams to monitor cash positions throughout the business day. camt.053 is the formal end-of-day bank statement used for accounting and reconciliation. camt.054 provides immediate notifications of individual debit or credit events as they occur, enabling real-time processing.
All three messages share the same underlying XML structure and data model, making them easy to process with a common parser. The main difference is the message header type (ReportHeader vs StatementHeader vs NotificationHeader) and the conditions under which each is delivered by the bank.
Camt.052: Intraday Account Report
Camt.052 (BankToCustomerAccountReport) is an intraday report that can be requested by the customer or pushed by the bank at configured intervals throughout the business day. It provides the current balance and pending/posted transactions as of the request time, allowing treasury teams to track cash positions for same-day funding decisions.
Unlike camt.053, camt.052 is not a formal accounting statement — it may include pending transactions that have not yet settled. This is similar to the legacy MT942 (Interim Transaction Report) which provided intraday balance updates. camt.052 is particularly valuable for companies with high transaction volumes that need real-time visibility into their account positions for zero-balance sweeping or same-day payment decisions.
Banks deliver camt.052 via SWIFT, EBICS (common in Germany and France), or host-to-host connections. The frequency of delivery is typically configured in the banking system: common intervals are every 2 hours, at specific times (e.g., 09:00, 12:00, 16:00), or on-demand via API. Swift GPI and API-based banking increasingly use camt.052 equivalents for real-time balance enquiry.
Camt.053: End-of-Day Bank Statement
Camt.053 (BankToCustomerStatement) is the formal end-of-day bank statement and the most widely used of the three camt formats. It contains all transactions posted to the account during the day, with opening and closing balances, and is used as the primary source for bank reconciliation in ERP systems and accounting software.
Camt.053 replaces the legacy MT940 (Customer Account Statement). Like MT940, it provides opening balance, transactions, and closing balance. Unlike MT940, it carries structured data: full IBAN/BIC of counterparties, structured remittance information (invoice references, creditor references), purpose codes, and end-to-end transaction identifiers. This structured richness enables automated reconciliation that MT940 with its free-text fields cannot support.
ValidateFin's Camt.053 Viewer parses and displays camt.053 files from all major European banks. It supports camt.053 versions 002, 006, 008, and higher, including DK-profiled German bank files and BNP/SG French bank files. Export to CSV is available for direct import into accounting systems.
Camt.054: Debit/Credit Notification
Camt.054 (BankToCustomerDebitCreditNotification) provides immediate notification of individual debit or credit events as they are posted to the account. It is the ISO 20022 equivalent of the legacy MT900 (Confirmation of Debit) and MT910 (Confirmation of Credit) messages.
Camt.054 is particularly useful for accounts payable and accounts receivable teams that need to act immediately on incoming payments. Instead of waiting for the end-of-day camt.053 statement, a camt.054 notification is delivered as soon as a payment is posted, enabling immediate allocation of incoming funds to open invoices.
Banks typically deliver camt.054 via SWIFT or API push notifications. In practice, camt.054 adoption is less widespread than camt.053 — many banks focus on camt.053 as the primary reporting format and treat camt.054 as an optional service. However, with the growth of instant payments (SEPA Instant Credit Transfer, TARGET Instant Payment Settlement), camt.054 is becoming more important for real-time payment confirmation.
Validate Your Camt.053 Files with ValidateFin
ValidateFin's Camt.053 Viewer parses all versions of camt.053, displays transactions and balances, and exports to CSV. No files are uploaded — all processing is client-side in your browser.
Open Camt.053 ViewerFrequently Asked Questions
What is the difference between camt.052 and camt.053?
Camt.052 is an intraday report providing current balance and pending/posted transactions as of the request time — used for real-time cash positioning during the business day. Camt.053 is the formal end-of-day bank statement used for accounting and reconciliation — delivered once per day after close of business.
What replaces MT940 in ISO 20022?
Camt.053 (BankToCustomerStatement) replaces MT940. Both provide end-of-day account statements with opening balance, transactions, and closing balance. Camt.053 carries structured data (IBAN, remittance references, purpose codes) where MT940 had free-text fields.
What replaces MT942 in ISO 20022?
Camt.052 (BankToCustomerAccountReport) replaces MT942. Both provide intraday account balance updates. Camt.052 carries structured data and can be delivered more flexibly (on demand, at scheduled intervals, or pushed by the bank).
What replaces MT900 and MT910?
Camt.054 (BankToCustomerDebitCreditNotification) replaces MT900 (Confirmation of Debit) and MT910 (Confirmation of Credit). It provides immediate notification of individual debit or credit events as they are posted to the account.
Do I need all three camt formats?
Most companies only need camt.053 for daily reconciliation. Camt.052 is valuable if you manage same-day cash positions or zero-balance sweeping. Camt.054 is optional but increasingly useful for instant payment confirmation. Start with camt.053 and add camt.052/camt.054 as needed.
Can ValidateFin parse camt.052 and camt.054 files?
ValidateFin's Camt.053 Viewer is optimised for camt.053. Camt.052 and camt.054 share similar XML structures and may be viewable with the same tool. Full support for all three formats is on the development roadmap.
What is the MT940 migration deadline?
The SWIFT MT940 migration deadline for cross-border account reporting was November 2025. After this date, MT940 is no longer supported for cross-border SWIFT account statements. Domestic delivery may vary by bank and country — contact your bank for your specific migration timeline.
How do I get camt.053 from my bank?
Request camt.053 from your corporate banking team or through your bank's online portal. Major banks in Europe offer camt.053 via SWIFT FileAct, EBICS (common in Germany and France), or host-to-host file transfer. Some banks offer camt.053 download directly from their online banking interface.
What version of camt.053 should I use?
The version delivered depends on your bank. Common versions are camt.053.001.002 (widely used), camt.053.001.006, and camt.053.001.008 (newer versions with additional fields). ValidateFin supports all major versions. Check with your bank which version they deliver and ensure your ERP parser supports it.
How do I reconcile camt.053 in my ERP?
Most modern ERP systems (SAP, Oracle, Microsoft Dynamics, Exact) have built-in camt.053 import functionality. The structured data in camt.053 — particularly end-to-end references and structured remittance information — enables automated matching of bank transactions to open invoices. ValidateFin's CSV export can be used as an intermediate step if your ERP requires a different import format.