camt.052 vs camt.053 vs camt.054: Which Bank Message Is Which

Banks that have moved to ISO 20022 deliver account information as XML files whose names start with camt, for "cash management". Three of them matter for most businesses: camt.052, camt.053 and camt.054. They share a vocabulary, which is why they are easy to confuse, but each answers a different question.

The three messages in one table

• camt.053, bank-to-customer statement. The account statement for a period, normally a day, produced after the books are closed. It holds opening and closing balances and every booked entry. It replaces the SWIFT MT940 text statement and is what accounting software usually imports.
• camt.052, bank-to-customer account report. An intraday report: what has been booked or is pending so far today. It replaces MT942. Its balances are interim, so they need not match the statement that follows.
• camt.054, bank-to-customer debit/credit notification. A notification about individual debits or credits, sent as they happen or in batches. It replaces MT900 and MT910 and is often used for incoming payments with a structured reference, for example Swiss QR-bill payments.

The structure they share

All three wrap a group header (GrpHdr: message ID, creation time, paging information) around one or more statements or reports, each with an account (Acct), optional balances (Bal) and entries (Ntry). An entry has an amount with currency, a credit or debit indicator (CdtDbtInd), a booking date and value date, a status, a bank transaction code (BkTxCd) and, inside NtryDtls/TxDtls, the details of the payments: references such as the end-to-end ID, the parties, and remittance information. When a bank books several payments together, the entry holds one total and several TxDtls blocks.

Versions: .02, .04 and .08

The last part of the name is the version. Versions .02 and .04 are older; .08 belongs to the 2019 version of ISO 20022 that Switzerland, for example, introduced in November 2022. The differences you notice when reading: banks are identified by BIC in older versions and BICFI in newer ones, an entry status is a text in older versions and a code element in newer ones, and a party sits in Dbtr/Nm in older versions and Dbtr/Pty/Nm in newer ones. The camt.053 Viewer & Excel/CSV Converter reads all three of them with these differences handled, and warns when it meets a version it has not been checked against.

What banks add

ISO 20022 is a framework. Each country or banking community publishes an implementation guide that restricts and fills in the message: which codes appear, how a structured reference is carried, which address forms are allowed. The Swiss, German and Nordic guides differ in details, so a field can mean something slightly different for your bank. When two banks' files look different, that is usually the reason, not an error.

Reading and checking a file

• Check the account, currency and period first. A statement for the wrong account or day is a surprisingly common reason for a failed import.
• Add the signed entry amounts to the opening balance. For a camt.053 the result should equal the closing balance; for a camt.052 or camt.054 it need not.
• Use the end-to-end ID and the structured reference to match payments with invoices, and look at batch entries through their individual payment details.
• Remember that a file with LastPgInd set to false is one page of several.

If you are producing payment files rather than reading statements, the pain.001 Payment File Checker covers the other direction, and the guide on pain.001 addresses explains one of the changes banks are asking for.