convertbank.onlineOpen Converter →
swift · mt940 · mt942

MT940 / MT942 → CSV or Excel

SWIFT bank statements parsed into a clean spreadsheet — :61: transactions, :86: remittance, :60F/:62F balances, all preserved. Built for treasury, AR/AP, and ERP integration teams.

Open the converter Migrating to ISO 20022? CAMT.053 →
Browser-side
MT940 never leaves your machine. GDPR / BaFin friendly.
Field-tag aware
Parses :20: :25: :28C: :60F: :61: :86: :62F: :64: :65: tags correctly.
Multi-account
Mixed-account MT940 batches split into one CSV per IBAN.

CSV output columns

One row per :61: transaction, one column per field — drop straight into Excel, SAP, Oracle, NetSuite, or DATEV.

Statement ref (:20:)
Account IBAN (:25:)
Sequence (:28C:)
Opening balance (:60F:)
Value date
Entry date
Debit/Credit mark
Amount
Currency
Transaction type (S/N/F)
SWIFT code
Customer reference
Bank reference
GVC code
Remittance text (:86:)
Counterparty name
Counterparty IBAN
Counterparty BIC
Closing balance (:62F:)
Available balance (:64:)

Why MT940 is still everywhere

ERP bank reconciliation
SAP FF.5, Oracle Cash Management, and Microsoft Dynamics still consume MT940 as a primary statement format.
Multi-bank treasury
Corporates pulling statements from 20+ banks use MT940 as the lowest common denominator before normalising to one CSV.
DATEV & German bookkeeping
DATEV's bank-statement import pipeline is MT940-native — converting to CSV lets you audit before posting.
Migration to ISO 20022
Mid-migration to CAMT.053? Run both formats through this site to verify the new feed matches the old.

FAQ

What is an MT940 file?+

MT940 is the legacy SWIFT 'Customer Statement Message' — a flat-text bank statement format with field tags like :20:, :25:, :60F:, :61:, :86:, and :62F:. It's still widely used by European corporate treasury, even as banks roll out the modern ISO 20022 CAMT.053 replacement.

What's the difference between MT940 and MT942?+

MT940 is the end-of-day statement; MT942 is the interim/intraday version sent multiple times per day for treasury cash positioning. Both share the same field-tag structure and both parse with this tool.

Does it parse :86: remittance and structured info?+

Yes. The :86: narrative field — including German GVC codes, structured SEPA ?20-?29 subfields, and free-text remittance — maps to dedicated CSV columns so you don't lose payment context.

Will it work with bank-specific dialects?+

Yes. Deutsche Bank, Commerzbank, ING, Rabobank, ABN AMRO, BNP Paribas, UniCredit, KBC, Erste, and most cooperative-bank MT940 variants all parse. Bank-specific :86: subfield conventions are detected automatically.

Is my MT940 file uploaded?+

No. Parsing runs entirely in your browser — the MT940 never leaves your device. Important for treasury teams under GDPR, BaFin, or internal data-residency policy.