iso 20022 · sepa

CAMT.053 → CSV or Excel

ISO 20022 XML bank statements parsed into a clean, ERP-ready spreadsheet. SEPA remittance, IBAN, BIC, and BkTxCd codes preserved. 100% browser-side — built for European treasury and finance teams.

GDPR-safe
Parser runs in your browser. No upload, no logs, no server.
Multi-statement merge
Drop a month of daily CAMT.053 files — one consolidated CSV out.
ERP-shaped output
Columns map to SAP FF.5, Oracle Cash Mgmt, NetSuite Bank Feeds.

Supported banks

Every major European bank that issues ISO 20022 CAMT messages.

Deutsche Bank
Commerzbank
BNP Paribas
Société Générale
Credit Agricole
ING
Rabobank
ABN AMRO
UBS
Credit Suisse
PostFinance
Santander
BBVA
CaixaBank
UniCredit
Intesa Sanpaolo
KBC
Belfius
Erste Group
Raiffeisen
Nordea
DNB
SEB
Handelsbanken

CAMT.053 vs MT940 vs CAMT.052

CAMT.053
End-of-day statement. Replaces MT940 under ISO 20022. Full structured remittance, multi-currency, multi-account.
CAMT.052
Intraday report. Same XML shape as CAMT.053 but issued multiple times per day for treasury cash positioning.
CAMT.054
Debit/credit notification. Single-transaction or batch confirmation — used for direct debit and SEPA collections reconciliation.

See the glossary for a full breakdown of ISO 20022 message types.

FAQ

What is CAMT.053?+

CAMT.053 is the ISO 20022 'Bank to Customer Statement' XML message used across SEPA and most European banks (Deutsche Bank, BNP Paribas, ING, UBS, Credit Suisse, Santander, UniCredit). It replaces legacy MT940 and contains end-of-day balances plus full transaction detail with structured remittance information.

Which CAMT messages are supported?+

CAMT.053 (end-of-day statement), CAMT.052 (intraday report), and CAMT.054 (debit/credit notification). All ISO 20022 versions from v2 through v10 parse, including bank-specific variants from Deutsche Bank, BNP Paribas, ING, Rabobank, KBC, UBS, Credit Suisse, Erste, Raiffeisen, and BBVA.

Does it preserve SEPA remittance fields?+

Yes. Structured creditor reference (ISO 11649 RF), unstructured remittance info, end-to-end ID, transaction ID, BIC, IBAN, and BkTxCd domain/family/subfamily codes all map to dedicated CSV columns.

Will my XML touch a server?+

No. The parser runs entirely in your browser — bank-statement data never leaves your device. Important for finance teams under GDPR, BaFin, FINMA, or internal data-residency rules.

Can I convert CAMT.053 for SAP, Oracle, or NetSuite import?+

Yes. The CSV is shaped for ERP bank reconciliation modules — one row per BkTxnDtls entry, ISO date format, EUR/CHF/GBP/USD amounts with sign, full IBAN/BIC. Drop into SAP FF.5, Oracle Cash Management, or NetSuite Bank Feeds.