Convert PDF Bank Statement to CAMT.053 (ISO 20022)

Free PDF to CAMT.053 converter for finance and treasury teams on ISO 20022. The output is a valid camt.053.001.02 BankToCustomerStatement XML document — the format SEPA banks already deliver and that SAP S/4HANA, Oracle Cloud, Workday, and treasury platforms ingest natively.

See How It Works
Free first conversion 1,000+ banks supported Files deleted in 24h

How to convert a PDF bank statement to CAMT.053

  1. Download your bank statement as a PDF from your online banking portal.
  2. Drop the PDF into the upload box above (or click to browse). Files up to 25 MB are supported.
  3. Wait 10–30 seconds while our OCR + AI engine reads the layout and extracts every transaction.
  4. Download the XML file. The first conversion every 24 hours is free.

Why CAMT.053?

ISO 20022 is the XML successor to SWIFT MT messages. SEPA banks deliver CAMT.053 by default; SAP S/4HANA's Bank Statement Manager and most modern treasury platforms read it natively. If your downstream system expects CAMT.053 and your bank only delivers a PDF copy, this export bridges the gap.

  • Valid camt.053.001.02 XML — passes ISO 20022 schema validation
  • Header metadata (account, owner, servicer/bank, statement period) plus opening (OPBD) and closing (CLBD) balances
  • One <Ntry> element per transaction with ISO date, amount, currency, credit/debit indicator, and remittance information
  • Each entry carries an EndToEndId so downstream systems can dedupe across imports
  • Drop into SAP S/4HANA Bank Statement Manager, Oracle Cloud Cash Management, Workday Banking, Kyriba, or any ISO 20022 ingester

What gets extracted from your statement

  • Transaction date (normalised to YYYY-MM-DD)
  • Description, payee, and reference where available
  • Debit and credit amounts in separate, signed columns
  • Running balance, where the statement shows one
  • Statement period, opening balance, and closing balance
  • Account holder name and account number (header only)

Convert CAMT.053 for any bank

Our parser is bank-agnostic — it reads the layout of your statement directly rather than relying on a hand-written template per bank. That's how we support 1,000+ banks worldwide. Common ones below:

ChaseBank of AmericaWells FargoCitibankCapital OneU.S. BankPNC BankTruistAmerican ExpressDiscoverHSBCBarclaysView all 1,000+ →

CAMT.053 conversion FAQ

What CAMT version do you emit?

camt.053.001.02 — the most widely deployed version in SEPA and the one SAP S/4HANA reads by default. Newer versions (.04, .08) are backwards-compatible at the data level for our use case.

Will SAP S/4HANA accept this XML?

Yes. The Bank Statement Manager's CAMT.053 import reads the file as-is. The namespace declaration (urn:iso:std:iso:20022:tech:xsd:camt.053.001.02) is what SAP keys off to route the file.

What's the difference between CAMT.053 and MT940?

Same data, different syntax. MT940 is text with SWIFT block tags (:60F:, :61:, etc.). CAMT.053 is XML and follows ISO 20022. Modern systems prefer CAMT; older SAP installs still want MT940. We emit both — pick whichever your downstream expects.

Need a different format?

Try a free conversion