What is camt.053 (bank-to-customer statement)?
camt.053 is the ISO 20022 bank-to-customer statement: an XML message in which a bank reports the booked entries and the opening and closing balances of one account, usually at day end, so the customer's accounting can reconcile its ledger.
What is camt.053?
camt.053 is the name of an ISO 20022 message called BankToCustomerStatement. A bank sends it to an account holder to report the booked transactions and the balances of one account. The Swiss Payment Standards describe it as the booking-relevant message of the day-end family and list the MT940 customer statement as an example of an alternative format. In practice, it is the file a company downloads from its bank, or receives from it, to bring its ledger into line with the bank.
The Swiss implementation guidelines for the camt messages, published by SIX Interbank Clearing, cover three messages together: camt.052 for intraday account reports, camt.053 for statements, and camt.054 for debit and credit notifications. Version 2.3 of those guidelines, in effect from 14 November 2026, is based on schema version camt.053.001.08.
How is a camt.053 organised?
The message is built in levels. The group header (A-level) identifies the message. The statement (B-level) describes one account; in the Swiss guidelines there is one account per message. Each statement contains balances and entries, and each entry can contain transaction details.
| Level | Content | Notes from the Swiss guidelines |
|---|---|---|
| Statement | Statement identification, sequence number, account (IBAN), reporting period | The IBAN is the account, not the QR-IBAN |
| Balance | Opening booked (OPBD) and closing booked (CLBD) | Both are mandatory in camt.053; closing available and forward available may also appear |
| Entry | Amount and currency, credit or debit indicator, booking and value date, bank transaction code, entry reference | The entry currency equals the account currency |
| Transaction details | References, parties, remittance information, creditor reference information | Where a batch is resolved internally, each line forms one transaction detail |
How are batch bookings handled?
A bank may combine many payments into one booking, for example a salary file. The Swiss guidelines describe two ways to resolve such a batch. In the internal variant, the camt.053 shows the batch total as the entry and the lines as transaction details. In the external variant, the camt.053 shows only the total, and an entry can refer to a camt.054 message that holds the detail; only one camt.054 can be referenced per entry. Not every bank offers the external variant, which is why accounting software must read both forms or know which one its bank uses.
How do references travel into the statement?
An invoice issuer who uses a QR-bill puts a structured reference, either a QR reference or an ISO creditor reference, on the invoice. The payer’s payment order carries it in the creditor reference information. The Swiss guidelines state that the reference is then forwarded to the creditor, and the creditor’s bank reports it in the camt message. For QR-IBAN and creditor-reference entries, the entry reference also carries a value that depends on the batch booking logic of the bank, so the entry reference should be treated as a bank-defined field and not as a stable key.
Worked example (illustrative, synthetic numbers)
A company’s bank sends a camt.053 for one business day with the values below.
| Item | Value |
|---|---|
| Opening booked balance (OPBD) | CHF 41,250.00 |
| Entry 1: credit, QR reference of invoice 2026-0412 | CHF 4,860.00 |
| Entry 2: credit, QR reference of invoice 2026-0398 | CHF 1,200.00 |
| Entry 3: debit, supplier payment | CHF 3,415.50 |
| Closing booked balance (CLBD) | CHF 43,894.50 |
The reconciliation check is simple arithmetic: 41,250.00 plus 4,860.00 plus 1,200.00 minus 3,415.50 equals 43,894.50. If the check fails, the file is incomplete or was altered, or the import went wrong, and the ledger should not be updated until a person has found out which. A missing statement in the sequence shows up in a different check: the opening balance does not equal the previous closing balance.
What controls apply?
| Risk | Control | Owner |
|---|---|---|
| Statement imported twice | Use the statement identification and sequence number to detect a duplicate and refuse it | Accounting software |
| Gap in the statement sequence | Compare the opening balance with the previous closing balance before accepting | Bookkeeper |
| Balance does not tie to entries | Recompute opening plus entries and compare with the closing balance | Bookkeeper |
| Bank entry has no matching document | Route to a person with the reference and amount; do not book automatically | Finance lead |
| Tampered file | Obtain the file only through the bank’s authenticated channel and keep the original | Treasury |
| Wrong company account | Check the IBAN in the statement against the company’s registered accounts | Accounting software |
Does the format differ between banks?
The Swiss guidelines say that the Swiss messages comply with ISO 20022 but do not use it to its full extent, and that no separate XML schemas are published for the camt messages. Each bank also decides which options it offers, such as external batch resolution and intraday reports. A company that changes bank should expect to test the import with a sample file again.
How does Corebanq Accounting relate to camt.053?
Today, Corebanq Accounting imports camt.053 statement files and camt.054 notification files that the user uploads. It does not offer live bank feeds, EBICS connections or open banking connections. This page does not describe automatic matching of statement entries to invoices. See Corebanq Accounting for the current product scope.
Related terms
camt.054 reports single credits and debits. QR-bill explains the reference that arrives in the statement. pain.001 is the customer-to-bank payment initiation message, the other direction of the same ISO 20022 family. The note From QR-bill to camt.054 follows an invoice through to its bank entry.
Frequently asked questions
- What is the difference between camt.053 and camt.054?
- A camt.053 is a statement with opening and closing balances covering booked entries of one account. A camt.054 is a notification of individual credits or debits, and it has no balance element. In the Swiss guidelines, camt.054 also carries the detail of a batch booking that a camt.053 shows only as a total.
- Is camt.053 the replacement for the MT940 statement?
- The Swiss guidelines list MT940 Customer Statement Message as an example of an alternative message to the camt.053 account statement. The two serve the same booking-relevant purpose, with different formats.
- Does every bank deliver camt.053 in the same way?
- The messages follow ISO 20022, but the Swiss Payment Standards say that the Swiss messages comply with the ISO standard without using it to its full extent, and that no separate XML schemas are issued for the camt messages. Banks also differ in what they offer, for example in how batch bookings are broken down.
- What version of the schema do the Swiss guidelines use?
- Version 2.3 of the Swiss guidelines, in effect from 14 November 2026, refers to camt.053.001.08, the BankToCustomerStatementV08 message of ISO 20022. Banks differ in what they deliver, so check the version with the bank.
- How does a QR-bill payment appear in a camt.053?
- As an entry on the creditor's account. The structured reference of the QR-bill, either the QR reference or the ISO creditor reference, is forwarded in the creditor reference information of the transaction details. For a QR-IBAN, the statement shows the account, not the QR-IBAN.
Sources
- SIX Interbank Clearing: Swiss Implementation Guidelines for Customer-Bank Messages (Reports) camt.052 / camt.053 / camt.054, version 2.3, with effect from 14 November 2026
- ISO 20022: message definitions catalogue (BankToCustomerStatement)
- SIX Interbank Clearing: Swiss Implementation Guidelines for the QR-bill, version 2.4