Guides

How to Convert MT940 to CSV Online (SWIFT Bank Statement Guide)

To convert a SWIFT MT940 bank statement file (.sta, .mt940, or .txt) into a clean, spreadsheet-ready CSV or Microsoft Excel file without exposing sensitive financial records to cloud servers, parse the MT940 SWIFT fields directly inside your browser memory using the EasyExtract MT940 to CSV Converter. The tool analyzes :61: statement line transaction tokens (value date, entry date, debit/credit mark, currency, amount, transaction reference) and multi-line :86: transaction narratives entirely client-side using JavaScript, exporting a normalized UTF-8 CSV with zero network uploads.

Every business day, corporate treasury desks, accounting teams, external auditors, and ERP administrators download thousands of electronic bank account statements from corporate banking portals such as HSBCnet, BNP Paribas, Deutsche Bank, Barclays, and Citibank. In Europe, the United Kingdom, Asia-Pacific, and South Africa, the dominant standard for automated end-of-day customer statement reporting has long been the SWIFT MT940 (Message Type 940) Customer Statement Message.

However, when finance professionals attempt to open an MT940 file in standard desktop software, Microsoft Excel either fails to open it or dumps all raw telegraphic SWIFT lines into an unreadable, single column filled with cryptic colon tags like :20:, :25:, :60F:, :61:, and :86:. Consequently, accountants frequently resort to risky free online file converters, inadvertently transmitting proprietary enterprise cash flows, counterparty IBANs, customer names, and transaction values across unverified third-party cloud servers.

This technical guide explains the internal architecture of the SWIFT MT940 statement standard, details why traditional cloud conversion introduces catastrophic data security and compliance liabilities, and provides an end-to-end tutorial on parsing MT940 files into pristine Excel CSV spreadsheets completely inside your local browser.

What Is a SWIFT MT940 File and Why Is It Hard to Open?

The MT940 (Customer Statement Message) is an international financial messaging specification governed by the Society for Worldwide Interbank Financial Telecommunication (SWIFT) under the SWIFT Standards MT message category 9 (Cash Management and Customer Moves). It delivers balance information and itemized line transactions for an account held by a corporate customer at a financial institution.

Unlike modern delimited file formats such as CSV, TSV, or XML, an MT940 message is a sequential telegraphic text stream composed of rigid alphanumeric tags. Each field begins with a specific tag enclosed in colons (e.g., :tag:) followed by fixed or semi-fixed character patterns:

SWIFT Field Tag Field Designation Standard Data Format & Purpose
:20: Transaction Reference Number (TRN) Up to 16 characters uniquely identifying the statement generation session from the sending bank.
:25: Account Identification Up to 35 characters containing the account number or International Bank Account Number (IBAN) of the reporting account.
:28C: Statement Number / Sequence e.g., 00042/001 — Specifies the statement sequence number and sub-statement page index.
:60F: / :60M: Opening Balance (First or Intermediate) 1!a6!n3!a15d (Debit/Credit indicator, YYMMDD date, 3-letter ISO currency code, followed by opening balance amount).
:61: Statement Line (Transaction Item) Contains the transaction value date (YYMMDD), optional entry date (MMDD), Debit (D) / Credit (C) code, amount with comma decimal, transaction type code, customer reference, and bank reference.
:86: Information to Account Owner Multi-line narrative text (up to 6 lines of 65 characters) specifying counterparty details, invoice numbers, SEPA transfer references, and payment descriptions.
:62F: / :62M: Closing Balance (Final or Intermediate) Indicates the verified closing cleared funds balance, date, currency, and debit/credit status.

Because an MT940 statement groups individual transactions across multiple staggered lines—where every single transaction record is split between a structured :61: header and a multi-line unstructured :86: remittance block—native spreadsheet tools cannot parse the relational connection. Without a specialized semantic parser, Excel treats line breaks as separate disconnected rows, destroying the integrity of accounting ledgers.

Anatomy of the Crucial :61: Statement Line and :86: Narrative

To accurately convert an MT940 file into structured tabular data, a parser must decode the complex compound regex structure of SWIFT tag :61:. According to official SWIFT Standards documentation, field 61 follows this exacting schema:

:61:YYMMDD[MMDD]C|D|RC|RD[1!a]15d[1!a]3!c16x[//16x]
[34x]

Consider this real-world MT940 statement snippet:

:61:2611181118CR14500,50NTRFNONREF//INV-2026-9812
:86:SUPPLIER PAYMENT SEPA CT
ACME INDUSTRIAL SERVICES LTD
IBAN: DE89370400440532013000
EREF: INV-2026-9812 CUST ID 884102

Here is how our client-side extraction engine decomposes this data block into distinct spreadsheet columns:

  • Value Date (261118): Decoded into ISO date format 2026-11-18.
  • Entry Date (1118): Optional booking date November 18.
  • Debit/Credit Indicator (CR): Credit reversal / Credit indicator. In standard statements, C represents incoming funds, while D represents outgoing funds.
  • Transaction Amount (14500,50): European comma decimal notation normalized to standard floating-point representation (14500.50). Debits are automatically signed negative (-14500.50) for instant accounting reconciliation.
  • Transaction Type Code (NTRF): Non-SWIFT transfer indicator.
  • Reference Token (NONREF//INV-2026-9812): Parsed as invoice tracking number INV-2026-9812.
  • Narrative Body (:86:): Multi-line strings are stripped of internal carriage returns, sanitized, and concatenated into a cohesive narrative string: "SUPPLIER PAYMENT SEPA CT ACME INDUSTRIAL SERVICES LTD IBAN: DE89370400440532013000 EREF: INV-2026-9812 CUST ID 884102".

The Privacy Risk of Cloud-Based Bank Statement Converters

When searching for “convert MT940 to CSV” or “MT940 to Excel online”, Google displays dozens of generic document conversion websites. Unfortunately, nearly all legacy converters use server-side architecture. This workflow presents massive corporate vulnerabilities:

Security Dimension Generic Cloud Converters EasyExtract Client-Side Engine
Data Transmission Files are uploaded over public HTTP/HTTPS pipes to external cloud servers (AWS, GCP, DigitalOcean). Zero network transfer. Files remain strictly in client browser memory (RAM).
Banking Privacy Third-party server operators and database administrators can inspect raw account statements, corporate cash balances, and supplier details. 100% Private. Zero third-party access. Statements are never stored or logged.
Regulatory Compliance Severe violation risks under GDPR (Article 5 & 32), HIPAA, CCPA, and banking secrecy laws when uploading client financial statements. Full Compliance. Compliant by architecture since zero data crosses network boundaries.
Cost & Restrictions Free tier restricted to 1–2 files before locking behind \$29/month subscriptions or requiring email submission. 100% Free & Unlimited. Convert unlimited MT940 files with zero paywalls.

Step-by-Step: How to Convert MT940 to CSV in 3 Simple Steps

Using the free EasyExtract MT940 to CSV Converter, you can convert financial statement files into spreadsheets in seconds:

Step 1: Open the MT940 Converter

Open the free MT940 to CSV Converter on EasyExtract. No software installation, browser extensions, accounts, or API keys are required.

Step 2: Drop Your MT940 / .STA File

Drag and drop your electronic bank statement into the file dropzone, or click anywhere inside the box to choose a file from your hard drive (supports .mt940, .sta, .txt, and .940 file extensions). The client-side parser immediately reads the file into browser memory.

Step 3: Inspect Transactions & Download CSV

The parser immediately identifies all :61: statement entries, matches their :86: descriptions, and displays an interactive preview table showing:

  • Value Date: Normalized YYYY-MM-DD date format.
  • Debit/Credit: Clear transaction direction flag.
  • Amount: Decimal-adjusted transaction balance formatted for math functions.
  • Reference: Bank counterparty and transaction identifier.
  • Description: Full consolidated remittance message.

Click Download CSV to save an instant .csv spreadsheet formatted with RFC 4180 quotation escaping, or click Copy to Clipboard to paste the table directly into Microsoft Excel, Google Sheets, Xero, or Apple Numbers.

Importing Your Converted MT940 CSV into Accounting Software

Once you download your clean CSV file, you can immediately import your bank transactions into major accounting, bookkeeping, and ERP packages:

1. Microsoft Excel & Google Sheets

Simply double-click the downloaded mt940-transactions.csv file. Because the file is encoded in UTF-8 with standard comma separators and escaped quotes, Microsoft Excel opens it cleanly without splitting narratives across multiple rows.

2. Xero Cloud Accounting

Navigate to Accounting > Bank Accounts, locate your target account, select Manage Account > Import a Statement, and upload the CSV file. Map Value Date to Date, Amount to Amount, and Description to Payee/Description.

3. QuickBooks Online & Desktop

In QuickBooks Online, navigate to Bookkeeping > Transactions > Bank Transactions, click Upload Transactions, and select your converted CSV. Map the columns according to the 3-column (Date, Description, Amount) or 4-column format.

Frequently Asked Questions (FAQ)

What file extensions do MT940 bank statements use?

Banks typically provide MT940 files with the extensions .sta, .mt940, .940, or plain .txt. EasyExtract accepts any of these file types as long as the content follows the standard SWIFT MT940 structured format.

Can this tool parse European comma decimals?

Yes. SWIFT MT940 statements originating from Germany, France, the Netherlands, Italy, and Spain frequently represent numbers using comma decimals (e.g., 1.250,50 or 1250,50). EasyExtract automatically standardizes comma decimals into standard dot decimals (1250.50) so spreadsheets can calculate sums and averages immediately.

Does this tool support multi-statement MT940 files?

Yes. If your bank statement file contains multiple :20: statement batches or multiple days of transaction records concatenated into a single master file, our parser loops through the entire document, capturing every :61: transaction line in chronological order.

Are my banking statements uploaded or saved to any server?

No. EasyExtract runs 100% client-side inside your browser’s V8 JavaScript engine. Your bank statement never leaves your machine, making it completely compliant with corporate data protection standards, strict banking confidentiality, and NDAs.

Shah Abrar Ahmad - Founder & Lead Engineer
Lead Architect & Founder

Software architect and technical web engineer specializing in browser-based zero-knowledge file parsing, technical SEO, and data extraction security. Built EasyExtract to give users 100% private in-browser tools with zero cloud uploads.

Keep reading