Convert a CAMT.053 ISO 20022 Statement to CSV

What a CAMT.053 file is

CAMT.053 is the ISO 20022 message a bank sends its corporate clients as an end-of-day account statement, the Bank-to-Customer Statement. It is the modern XML replacement for the older SWIFT MT940, mandatory across the SEPA zone and spreading globally as banks migrate to ISO 20022. Instead of tagged text, it uses structured XML with named, nested elements, which is excellent for machine processing and unreadable at a glance. Corporate treasury and shared-service teams receive these files daily, often covering several accounts at once, and the first step to actually working with the data is flattening that XML into a CSV.

The XML structure: Stmt and Ntry

A CAMT.053 file is organized as a hierarchy. Each Stmt element is one account for one reporting period, carrying the account identification such as the IBAN, the opening and closing balances, and a set of entries; a single file can hold several Stmt blocks when a company gets a consolidated statement. Inside each statement, every Ntry is one booking, and it names its parts explicitly: an Amt that is always a positive amount with a currency, a CdtDbtInd that says CRDT for money received or DBIT for money sent, booking and value dates, a bank transaction code in BkTxCd, and nested transaction details in NtryDtls carrying the counterparty and the remittance information in RmtInf.

Flattening the entries into CSV rows

Converting a CAMT.053 to CSV turns that tree into a table. The usual output is one row per Ntry, with the amount, the credit or debit direction, the dates, the transaction code, and the remittance reference in their own columns, and the account and balances from the parent Stmt carried down so each row is self-describing. Where a single entry batches several underlying transactions, the details can be expanded to one row per TxDtls instead, so nothing is hidden inside a summary booking. The result is an ordinary CSV you can sort, filter, and total, or load into a system that does not read ISO 20022 XML.

CAMT.053 vs MT940 and BAI2

All three are bank statement formats, but they carry data very differently. MT940 is SWIFT's legacy format, built on fixed-width tagged fields like :61: for a transaction and :86: for its narrative. BAI2 is a US cash-management standard organized by two-digit record type codes. CAMT.053, by contrast, is hierarchical XML with named elements, so the amount direction is stated outright in CdtDbtInd rather than inferred, and the remittance data lives in a dedicated RmtInf element rather than a free-text narrative. That explicit structure is why ISO 20022 is displacing the older formats, and it flattens cleanly into CSV columns.

Reconciliation and privacy

The named fields are what make CAMT.053 strong for reconciliation once they are in a table. Because the remittance information is structured, a converted CSV lets you match a receipt to the invoice it settles, and sorting by the bank transaction code isolates a class of activity in one step. That is the same value an ERP or treasury system gets from ingesting the XML directly, delivered as a spreadsheet for review or for a system that cannot parse it. Because the file holds real corporate account activity across possibly many accounts, it is processed to build the CSV and then deleted automatically, with nothing retained on a server afterward.

Frequently Asked Questions