Skip to content

CAMT.053 to CSV & Excel

Turn ISO 20022 camt.053 XML bank statements into clean CSV, Excel, QuickBooks, Xero, OFX or QBO files without uploading banking data.

Drop CAMT.053 XML statements here

ISO 20022 camt.053 (.xml) files or a .zip bundle of daily statements. Read locally in this tab.

How to use CAMT.053 to CSV & Excel

  1. Drop your CAMT.053 XML or ZIP files. Drag one or more .xml bank statements or a .zip archive of daily statements into the DropZone (up to 25 MB per file).
  2. Inspect parsed transactions and balance checks. Review counterparty IBANs, remittance text, EndToEndId references, and the opening-to-closing balance verification summary.
  3. Adjust batch and date options. Keep Split batch bookings into individual transactions checked to expand <TxDtls> sub-entries, or toggle Export value date instead of booking date.
  4. Choose your output format and convert. Select CSV with SEPA columns, Excel (.xlsx), QuickBooks CSV, Xero CSV, OFX, or QBO, then click Convert transactions.

Everything you type stays in this browser on your device. Nothing is uploaded, and your saved details are never sent anywhere.

How ISO 20022 CAMT.053 XML maps to accounting exports

European and international banks issue camt.053 XML statements under the ISO 20022 BkToCstmrStmt schema to replace legacy flat-text feeds with structured IBAN, BIC, and remittance tags. As detailed in the European Central Bank SEPA and ISO 20022 Overview, standardized XML messaging lets treasury and bookkeeping systems exchange rich payment references across borders.

Because many European banks still offer legacy text downloads alongside XML, you can also convert legacy SWIFT MT940 bank statements to spreadsheets when working with .sta or .mt940 archives. On this page, a namespace-agnostic parser handles camt.053.001.02, .04, .08, and .10 as well as camt.052 account reports.

Export format (Save as) Target software Key columns or structure included
CSV with SEPA columns Excel, ERP, custom import Date, Debit, Credit, Counterparty, IBAN, BIC, EndToEndId, MandateId
Excel workbook (.xlsx) Microsoft Excel, LibreOffice Formatted spreadsheet with numeric amounts and dates
CSV for QuickBooks QuickBooks Online / Self-Employed Standard Date, Description, Amount layout
CSV for Xero Xero Bank Statement Import Date, Amount, Payee, Description, Reference columns
OFX Xero, Sage, Lexoffice, GnuCash Open Financial Exchange XML/SGML with CHECKING / SAVINGS / CREDITCARD
QBO QuickBooks Desktop Web Connect OFX 1.x wrapper with configurable Intuit bank ID (default 3000)

How does batch TxDtls unpacking and balance verification work?

When a bank groups multiple SEPA transfers or direct debits into one collective <Ntry> booking, enabling Split batch bookings into individual transactions expands each <TxDtls> child into its own row with individual counterparty IBANs and EndToEndId references. Simultaneously, the parser checks that opening balance plus credits minus debits equals the closing balance within 0.01.

Expanding collective SEPA batches into individual rows

Treasury and payroll runs often appear on a bank statement as a single lump-sum <Ntry> total containing dozens of <TxDtls> entries inside <NtryDtls>. Unpacking those child nodes saves hours of manual cross-referencing against outgoing payment batches.

If you generate outgoing SEPA payment batches yourself, you can use the SEPA pain.001 and pain.008 XML generator to build the original payment instructions. The CAMT.053 parser also extracts structured German/SEPA tags (EREF+, MREF+, SVWZ+, CRED+, ABWA+) from unstructured remittance text when present.

Reconciling OPBD opening and CLBD closing balances to 0.01

Per the W3C Extensible Markup Language (XML) 1.0 Specification, well-formed XML tags preserve exact nesting for <Bal> balance blocks (OPBD or PRCD opening, CLBD closing) and <RvslInd> reversal flags. Checking opening-to-closing math automatically catches truncated XML downloads or duplicate statement pages before you import them into a ledger.

In the sidebar summary, you will see total credits, total debits, and whether Balances verified passed across all loaded statements. If a bank statement omits opening or closing balance blocks, transactions still export normally without a false mismatch alert.

Exporting to Excel, QuickBooks, Xero, OFX, and QBO

Choosing the right output format depends on if you are auditing raw SEPA metadata in a spreadsheet or feeding an automated bank-reconciliation screen in accounting software. All six export modes run from the same parsed statement array in memory.

Choosing between CSV with SEPA columns, Excel, and QuickBooks/Xero CSV

Select CSV with SEPA columns (IBAN, BIC, EndToEndId) or Excel workbook (.xlsx) when you need full remittance narratives, mandate IDs, and bank references for audit trails. Choose CSV for QuickBooks or CSV for Xero when your accounting software expects strict 3-to-5-column bank upload templates formatted per IETF RFC 4180 Common Format for CSV Files.

Excel exports write native numeric cells for debit, credit, and running balance columns so pivot tables and SUM formulas work immediately without text-to-number conversion. Standard CSV exports quote fields containing commas or line breaks cleanly.

Configuring OFX account types and Intuit bank IDs for QBO

When OFX or QBO is selected, extra fields appear for Account type (Checking / current, Savings, or Credit card) and, for QBO, Intuit bank ID (default 3000). If you already have a bank CSV and only need an OFX wrapper, you can prepare universal OFX imports from existing CSV ledgers directly.

Troubleshooting pain.001 files, character encoding, and privacy

Statement imports occasionally fail because of a wrong XML message type, Excel character-set assumptions, or large multi-month ZIP bundles. Understanding how the parser handles each case prevents import errors.

Why payment initiation XML and large 25 MB archives behave differently

Uploading a pain.001 or pain.008 XML file triggers a clear warning because payment initiation schemas describe requested transfers rather than settled bank entries. Each uploaded .xml or .zip archive supports up to 25 MB, and the on-screen preview table displays the first 300 rows while exporting every transaction in the file.

Tip: When converting a full year of daily .xml statements inside a .zip archive, verify that the balance status reads Balances verified before importing into QuickBooks or Xero so missing day files are spotted immediately.

Formula-injection sanitization, UTF-8 BOM, and audit scope

All CSV exports prepend a UTF-8 Byte Order Mark per the Unicode UTF-8 Byte Order Mark (BOM) FAQ so European umlauts and accents open cleanly in Excel, and neutralize leading =, +, -, or @ characters to block spreadsheet formula injection. If you work with non-banking XML feeds, you can flatten generic XML feeds into CSV tables; for statutory bookkeeping, confirm imported figures against your bank’s official PDF statement.

Questions

Does this converter unpack collective batch entries in TxDtls?

Yes. When Split batch bookings into individual transactions is enabled, the parser inspects each <Ntry> for itemised <TxDtls> sub-entries that reconcile to the entry total. Each underlying payment expands onto its own row with its counterparty IBAN, name, and EndToEndId.

How does opening-to-closing balance verification work?

The parser reads the statement's opening booked balance (OPBD or PRCD) and closing booked balance (CLBD), adds every credit, and subtracts every debit while accounting for reversal indicators (<RvslInd>). If the result differs from the closing balance by more than 0.01, it flags a balance mismatch.

What is the difference between booking date and value date?

Booking date (<BookgDt>) is the date the bank posted the entry to your ledger, whereas value date (<ValDt>) is when funds become available for interest calculation. Most accounting software reconciles against booking date by default, though you can toggle Export value date instead of booking date.

Why does the converter reject a pain.001 XML file?

Files containing <CstmrCdtTrfInitn> (pain.001) or <CstmrDrctDbtInitn> (pain.008) are outgoing SEPA payment initiation orders you send to a bank, not completed bank statements. This converter parses incoming camt.053 and camt.052 statement reports.

Which Intuit bank ID should I use for QBO Web Connect exports?

The default Intuit bank ID is 3000, which QuickBooks Desktop accepts for generic QBO Web Connect imports when your European bank is not listed in Intuit's US directory. If your bank provides a specific INTU.BID code, enter it in the Intuit bank ID field.

Can I convert a ZIP archive of daily CAMT.053 XML statements at once?

Yes. Drop a .zip archive up to 25 MB containing multiple daily or monthly .xml statements, or add several files together. The converter extracts every statement locally, previews the first 300 rows, and exports all transactions into one combined file.

Updated