What CAMT.053 actually is
CAMT.053 stands for "Cash Management" message type 053, formally named BankToCustomerStatement. It is part of ISO 20022, the international standard for financial messaging maintained by the ISO organization and used across payments, securities, and cash reporting.
A CAMT.053 message is an end-of-day statement. It reports booked transactions and balances for a specific period after that period has closed. Because it is a final statement rather than a live feed, the balances and entries in it are considered settled.
The file itself is XML. Inside, you will find a document wrapper, one or more statements (Stmt), account identification, opening and closing balances, and a list of entries (Ntry). Each entry carries an amount, a credit or debit indicator, a booking date, a value date, and transaction details that can include counterparty names, references, and remittance information.
The CAMT family and related formats
CAMT.053 has siblings you may encounter. CAMT.052 (BankToCustomerAccountReport) is an intraday report, used during the day before the statement closes. CAMT.054 (BankToCustomerDebitCreditNotification) is a notification of individual credits or debits, often used for detailed reconciliation of collections.
Think of it this way: CAMT.052 is a preview during the day, CAMT.053 is the official end-of-day statement, and CAMT.054 provides transaction-level advices. Many banks offer all three depending on your service agreement.
These sit alongside older messaging standards. SWIFT MT940 and MT942 have long served the same statement and interim-report roles, and BAI2 is common in North America. ISO 20022 formats like CAMT are gradually replacing MT messages as banks migrate to the newer standard.
CAMT.053 versus MT940
MT940 is the legacy SWIFT statement format. It is compact, tag-based text rather than XML. Many accounting and ERP systems have supported MT940 for years, so it remains widely used even as ISO 20022 adoption grows.
CAMT.053 carries richer, more structured data than MT940. Fields that were crammed into free-text lines in MT940 have dedicated XML elements in CAMT, such as separate tags for counterparty details, references, and structured remittance information. This makes automated reconciliation more reliable.
The tradeoff is complexity. CAMT.053 files are larger and harder to read by eye, and different banks populate optional fields differently. Two valid CAMT.053 files from two banks can look quite different in which elements they use, so any tool reading them needs to handle that variation.
How to use a CAMT.053 file
First, check whether your accounting or treasury software imports CAMT.053 directly. Many bank-feed and ERP systems now accept it. If yours does, import the XML as provided and let the system map the entries to your accounts.
If your software cannot read CAMT.053, you will need to convert it. The typical goal is a CSV or Excel layout with columns for date, description, amount, and running balance, or a format your accounting tool accepts such as OFX, QFX, QBO, or QIF. Converting flattens the nested XML entries into rows you can review and import.
Before importing anything, reconcile the opening and closing balances in the file against your own records. Because CAMT.053 is an end-of-day statement, those balances should tie out exactly. Spot-check a few entries for correct dates and signs, since credit and debit handling is a common source of import errors.
Keep the original XML on file. Even after you convert it, the source CAMT.053 is your authoritative record, and you may need to reprocess it if a mapping was wrong the first time.