CAMT.053 to CSV Converter

What is a camt.053 file?

camt.053 — formally BankToCustomerStatement — is the ISO 20022 XML message banks use for end-of-day account statements. It's the modern replacement for SWIFT MT940 under the SEPA and ISO 20022 migration, and it nests like the standard it belongs to: a BkToCstmrStmt element wraps one or more Stmt blocks, each carrying the account, opening and closing balances, and an Ntry element per statement line. It's all plain-text XML, but at hundreds of tags per transaction it's not something you want to read by hand. For the full anatomy of the format, read What is a CAMT.053 file? in the Learn section.

Who gets camt.053 files?

Any business banking in the SEPA zone — and increasingly anywhere ISO 20022 has landed — receives camt.053 as the daily statement feed for treasury systems and ERPs. If your bank recently announced it's retiring MT940 exports, camt.053 is what replaces them; the two formats map field-for-field, and CAMT.053 vs MT940 walks through exactly what changes. Still receiving MT940 from another bank? The MT940 to CSV converter handles those the same way.

What ends up in your CSV

• Booking Date / Value Date: When the entry hit the books, and when it affects interest.
• Amount / Currency: Signed amounts — debits negative — preserving the file's own decimal precision.
• Status: BOOK for booked entries, PDNG for pending ones, with reversals flagged.
• Bank Transaction Code: The ISO domain/family/sub-family code as a dotted string ("PMNT.RCDT.ESCT"), or the bank's proprietary code.
• End-to-End Reference: The reference the payer supplied, carried unchanged through the whole payment chain.
• Counterparty / Counterparty IBAN: Who the money came from (credits) or went to (debits).
• Description: The unstructured remittance information (Ustrd) lines, joined.
• Statement: Which statement the row came from, for files carrying more than one.

The converter reads every statement in the file and flattens the XML to one row per transaction. Batch entries — one Ntry wrapping several TxDtls blocks — are unrolled so each underlying payment gets its own row rather than hiding inside a batch total.

How to convert camt.053 to CSV

1. Drop your camt.053 .xml file above. Parsing happens on your device — bank data is never uploaded.
2. Check the summary: account, statement and entry counts, currency, and the opening and closing balances.
3. Preview every transaction — signed amounts, counterparties, remittance info.
4. Export as CSV for Excel, or XLSX.

Troubleshooting camt.053 files

What's the difference between camt.052, camt.053, and camt.054?

They're sibling ISO 20022 cash management messages. camt.052 is the intraday account report — balances and movements during the day. camt.053 is the end-of-day statement — the complete, final record with opening and closing balances, replacing MT940. camt.054 is a debit/credit notification that reports individual movements (or batch details) as they happen. This converter reads camt.053; if you drop a camt.052 or camt.054 it will tell you.

Why does one statement entry produce several CSV rows?

camt.053 allows batch bookings: a single entry (Ntry) carries the total amount, and its entry details (NtryDtls) wrap one TxDtls block per underlying transaction — a payroll run debited as one entry can contain dozens of individual payments. This converter unrolls those to one row per transaction, each with its own amount, counterparty, and reference, so nothing hides inside a batch total.

How does camt.053 relate to MT940?

camt.053 is MT940's successor. Both are end-of-day bank statements, and banks under SEPA and the ISO 20022 migration are replacing MT940 with camt.053. The data maps across — MT940's :60F:/:62F: balances become Bal blocks, each :61: transaction line becomes an Ntry — but camt.053 carries far more structure: named counterparties with IBANs, end-to-end references, mandate IDs, and remittance info that isn't truncated to 65-character lines.

Is this camt.053 converter really free?

Yes — every file parses and previews free with no signup and no upload. Free exports include the first 100 rows; a one-time $19 license unlocks unlimited exports on every LegacyFile tool.