Convert PDF Bank Statement to MT940 (SWIFT)

Free PDF to MT940 converter for finance teams running SAP, Oracle, NetSuite, or any ERP that consumes SWIFT bank-statement messages. Output follows the SWIFT Standards Release Guide: tag-based block format with :20:, :25:, :60F:, :61:/:86: per transaction, and :62F:.

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

How to convert a PDF bank statement to MT940

  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 MT940 file. The first conversion every 24 hours is free.

Why MT940?

MT940 is the lingua franca of corporate bank statements. Every major ERP and treasury system reads it. If your finance team's import job expects an MT940 file but your bank only delivers a PDF, you currently re-key the statement by hand. This export removes that step.

  • Valid MT940 body wrapped in block 4 ({4:…-}) — accepted by SAP FI bank-statement upload (transaction FF_5)
  • :60F: opening balance and :62F: closing balance with currency and value date
  • One :61:/:86: pair per transaction with credit/debit indicator, value date, amount, and full narrative
  • Comma decimal separator — SWIFT-conformant, won't be rejected by strict validators
  • Suitable for downstream tools that read MT940: SAP, Oracle, NetSuite, Workday, Coupa, Kyriba, Trovata

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 MT940 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+ →

MT940 conversion FAQ

Will SAP accept this MT940 file?

Yes. The output passes SAP's FF_5 / FF.5 import (Electronic Bank Statement). The file is wrapped in SWIFT block 4 and uses the standard tag set (:20:, :25:, :28C:, :60F:, :61:, :86:, :62F:).

Why is the amount written with a comma?

SWIFT MT messages use comma as the decimal separator (',' not '.') — this is mandated by the standard. Strict validators reject files with '.' as the decimal marker.

What if my statement spans multiple pages or accounts?

We emit one MT940 statement per uploaded PDF. If your bank delivers multi-account combined PDFs, each account becomes its own conversion — upload them separately or use batch mode.

Need a different format?

Try a free conversion