BankStatementToExcel.com

Convert PDF Bank Statement to MT940 (SWIFT)

Export extracted statement data as an MT940 block-4 body in a .sta file. Check account metadata, fixed references, generic transaction codes, and narrative limits against your destination’s requirements before importing.

See How It Works
2 free pages a day 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 while the converter extracts the statement. Processing time depends on the document.
  4. Open More formats and select MT940. Your first 2 pages each day are free.

Why MT940?

Some ERP and treasury workflows require tagged MT940 data. A PDF-derived file provides a starting point when an electronic bank statement is unavailable, but bank-specific fields and importer rules may require adaptation.

  • Tags for account, opening balance, transactions, and closing balance
  • C/D direction markers and comma decimal amounts
  • Transaction narratives retained up to the exporter’s length limit
  • Download through More formats alongside a review workbook
  • Guide documents fixed references, missing-field defaults, and strict-importer limitations

What gets extracted from your statement

  • Transaction date (normalised to YYYY-MM-DD)
  • Transaction description; available details depend on the source PDF
  • Debit and credit amounts; Excel and CSV use separate columns, while QBO uses signed transaction amounts
  • 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:

MT940 conversion FAQ

Is import into SAP or another ERP guaranteed?

No. Acceptance depends on the configured MT940 variant, account mapping, reference rules, and field constraints. Test or preview the import before posting.

Why does the download end in .sta?

That is the filename extension used for this exporter’s MT940 text body. Renaming it does not change its content or make it match another import specification.

Which fields need particular attention?

The statement reference and sequence are fixed, transaction code is NMSC, and transaction reference is NONREF. Missing balances default to zero and long narratives are truncated without continuation-line wrapping.