Upload your MT940 (.sta or .mt940) bank statement file and get a clean CSV with all transactions — ready for Excel, Python, data analysis, or accounting software import.
MT940 is the SWIFT standard for electronic bank statements. Banks and ERP systems use MT940 to exchange structured transaction data in a machine-readable format. An MT940 file is a plain-text document where each data element is identified by a tag (like :61: for transactions or :86: for narrative descriptions).
The challenge with MT940 files is that they cannot be opened directly in Excel, imported into most cloud accounting tools, or processed by standard CSV-based pipelines. Converting MT940 to CSV is the first step to making the data usable for analysis, reporting, or import into accounting software that does not natively support MT940.
Before converting, it helps to understand what is in an MT940 file. Here is a typical snippet:
The converter reads each :61: tag for transaction data and each :86: tag for the description, then maps them into clean CSV rows.
The CSV produced from your MT940 file contains these columns:
| CSV Column | Source MT940 Tag | Description |
|---|---|---|
| Date | :61: (first date field) | Transaction date (YYYYMMDD → formatted) |
| Value Date | :61: (second date field) | Value / clearing date |
| Description | :86: | Transaction narrative / description |
| Reference | :61: (reference field) | Transaction reference number |
| Type Code | :61: (SWIFT type code) | e.g. NTRN, PMNT, XFER |
| Debit | :61: (D = debit) | Money out (blank if credit) |
| Credit | :61: (C = credit) | Money in (blank if debit) |
| Balance | Calculated from :60F:/:62F: | Running balance after each transaction |
| Currency | :25: / :60F: | ISO currency code (EUR, GBP, USD, INR, etc.) |
Many businesses are moving from SAP or Oracle (which use MT940 for bank feeds) to cloud accounting tools like Xero, QuickBooks Online, or Zoho Books. These cloud tools accept CSV bank import but not MT940. Converting your MT940 archives to CSV lets you migrate historical transaction data without losing any records.
Python, R, SQL, and virtually every data processing tool works natively with CSV via pandas, readr, or standard SQL COPY commands. MT940 requires a dedicated parser. Converting to CSV removes that dependency and makes bank statement data immediately usable in any analytical pipeline.
If your ERP exports MT940 files for treasury reporting but your CFO wants an Excel dashboard, converting MT940 to CSV (then opening in Excel) is the fastest path. No SAP report configuration required — just download the .sta file, convert, and open in Excel.
MT940 archives are the official bank statement record for ERP-based businesses. Converting to CSV for specific periods makes it easy to share with auditors who work in Excel, or to load into audit software that accepts tabular data.
| Feature | MT940 | CSV |
|---|---|---|
| Human readable | Partially (structured text) | Yes (any text editor) |
| Excel compatible | No (needs parsing) | Yes (open directly) |
| Python/pandas compatible | Needs mt940 library | Yes (pd.read_csv) |
| SAP / Oracle import | Yes (native format) | Limited (needs mapping) |
| QuickBooks / Xero import | No | Yes |
| Universal compatibility | Low | Very High |
Export from your ERP (SAP, Oracle) or download from your bank's portal as .sta
Upload the .sta or .mt940 file — choose CSV as the output format
Get a clean CSV with all transactions, ready for Excel or your data pipeline