camt.054

camt.054 is the identifier of the ISO 20022 message called Bank-to-Customer Debit/Credit Notification. A bank uses it to inform an account holder that one or more specific debits or credits have been, or will be, booked to the account. Unlike a statement, it does not need to report balances; it focuses on the details of particular transactions, such as an incoming customer payment, an outgoing batch of supplier payments or a set of direct debit collections.

The message is part of the cash management family of ISO 20022, together with the end-of-day statement camt.053 and the intraday account report camt.052. It corresponds to the SWIFT MT messages MT900, confirmation of debit, and MT910, confirmation of credit, but carries far richer data. Corporate treasury teams, payment service providers and banks use it to update receivables and payables quickly and to reconcile payments in detail.

A camt.054 message follows the same building blocks as other camt reports. A group header identifies the message and its creation time. One or more notification blocks each refer to an account and contain entries. Each entry gives the amount, currency, credit or debit indicator, status (for example booked or pending), booking and value dates and a bank transaction code. The entry details then list the underlying transactions, with references such as the end-to-end identification set by the payer, the names and accounts of the debtor and creditor, purpose codes, charges and structured or unstructured remittance information.

Because the entry details can hold many transactions, camt.054 is often used to break down a single batch booking. A bank may show one total credit of a day's collections on the account statement, while sending a camt.054 that lists every individual payment in that total.

• Receivables matching. Companies use incoming credit notifications to apply customer payments to open invoices, often by payment reference matching on structured references. This can update accounts receivable during the day rather than waiting for the statement.
• Batch details. Banks send camt.054 to explain bulk bookings, such as payroll runs, supplier payment files and direct debit collections, including returns and rejections.
• Direct debit reporting. Creditors collecting through SEPA Direct Debit and similar schemes receive notifications showing which collections were paid and which were returned.
• Virtual accounts. Firms using virtual IBANs receive notifications identifying which virtual account each payment arrived in, which simplifies identifying the payer.
• Real-time alerts. With instant payment systems, some banks send a camt.054 for each incoming payment within seconds, giving businesses a near-real-time payment confirmation that can trigger release of goods or credit to a customer account.

The three messages complement one another. camt.053 is the official statement for a period, with balances and every booking. camt.052 reports account activity and balances during the day, for monitoring cash positions. camt.054 notifies specific movements and can be sent as soon as they occur, or as a supporting detail file. Some banks put full details in the statement; others keep the statement short and send details only in camt.054. Customers therefore need to agree with each bank which combination they will receive and how the messages link, typically through shared entry references.

As with other ISO 20022 messages, several versions of camt.054 exist, and national or industry guidelines say which elements are mandatory and how codes are used. In Switzerland, for example, camt.054 has been widely used to report details of incoming payments, including those made with structured payment references. Banks deliver camt.054 through SWIFT, host-to-host links, the EBICS protocol, online banking or APIs. Accounting and treasury management systems must be configured to read the chosen version, match entries to statements and avoid double counting when the same booking appears in both a notification and a statement.

camt.054 gives companies timely, detailed and structured information, which reduces manual work in bank reconciliation and speeds up cash application. It also supports better cash management by showing payments as they happen. The main limitations are practical. Banks differ in how they use the message and how quickly they send it, remittance data is only as good as what the payer provided, and firms working with many banks must handle multiple formats and versions. Translating notifications into older formats can also lose information, so businesses that switch from MT900 and MT910 often update their systems to use the full MX message content directly.

• ISO 20022