Convert MT940 files to Excel
Upload the MT940 file from your bank (.sta, .mt940 or .txt) and get an Excel workbook or CSV with one row per transaction: each :61: line decoded into a date and a signed amount, each :86: field turned into a readable payee and purpose, and every statement checked against its own opening and closing balance.
Drop your statement here
PDF, scans and phone photos, or CSV, Excel, OFX, QIF, CAMT and MT940 exports
See the result before you payAny bank, any language
Updated October 28, 2026
Step by step
- 1
Download the MT940 file
In your business online banking, export the account transactions or statements as MT940 (sometimes called SWIFT or STA format). One file can cover many days and several accounts.
- 2
Upload it
Drop one or many files. Each account and currency becomes its own statement, and the daily statements in a file are joined into one period.
- 3
Export
Choose Excel or CSV, or a file for QuickBooks, Xero, OFX or QIF. Combine several files into one export, optionally limited to a date range.
What is an MT940 file?
MT940 is the SWIFT Customer Statement Message: an end-of-day account statement in a plain-text format of numbered tags. It was designed for banks to send account statements to their customers' systems, and it became the standard way to feed statements into treasury and accounting software.
Today banks offer MT940 mainly to business customers — as a download in business online banking, through EBICS or host-to-host connections, or over the Swift network. It is especially common in Germany, the Netherlands and Poland, where many accounting programs import it. A file usually has the extension .sta, .mt940 or .txt and often contains one statement per day, sometimes for several accounts.
Reading the :61: statement line
The :61: line packs a whole transaction into one string with no separators. The example 2609140914D89,90NDDTNONREF breaks down like this:
| Part | Example | Meaning |
|---|---|---|
| Value date (YYMMDD) | 260914 | 14 September 2026 |
| Entry date (MMDD, optional) | 0914 | Booked on 14 September |
| Debit/credit mark | D | D debit, C credit; RD and RC mark reversals |
| Amount | 89,90 | 89.90, always unsigned, comma as decimal separator |
| Transaction type | NDDT | N plus a 3-character code, e.g. NTRF transfer, NDDT direct debit, NCHK cheque |
| Reference for the account owner | NONREF | Your reference, or NONREF when there is none |
Watch out for three things: amounts carry no sign, so the direction depends entirely on the D/C mark; the year has two digits and the entry date none, so at the turn of the year it has to be inferred; and an optional bank reference can follow after //, with supplementary details on a second line.
The :86: field: who paid whom, and why
:86: holds up to six lines of 65 characters describing the transaction above it. Its layout is not fixed by SWIFT, so every bank fills it a little differently — often the name of the other party, the payment purpose and a few references run together.
German banks use a structured layout: a three-digit transaction code followed by numbered subfields. ?00 holds the booking text (for example LASTSCHRIFT or GUTSCHRIFT), ?20–?29 and ?60–?63 the purpose, ?30 and ?31 the other party's bank code or BIC and account or IBAN, and ?32–?33 their name. Inside the purpose, SEPA keywords such as EREF+ (end-to-end reference), MREF+ (mandate reference) and SVWZ+ (purpose text) mark the parts.
When we read :86:, the name and the purpose are pulled out, the keyword prefixes are dropped and lines that were cut mid-word at 27 characters are rejoined. The AI then gives each transaction a clean payee name and a category.
How to open an MT940 file in Excel
MT940 is plain text, so Notepad or any text editor will open it — but Excel has no MT940 import. Opened directly, the file lands as one tag per row, with transactions spread over several lines, amounts as text with a comma and the sign hidden in a letter. Parsing that with text formulas breaks on the first :86: that wraps to a new line.
Converting gives you a normal table: one row per transaction with a real date, a signed amount (money out negative), the payee, the full description and a category. The Excel file also has a Summary sheet with totals by category and month — see bank statement to Excel for the layout — and the CSV export uses comma or semicolon format with the date format you choose.
MT940 vs MT942 vs CAMT.053
Three formats are easy to mix up when you pick a download option:
| Format | What it is | Balances | Use it for |
|---|---|---|---|
| MT940 | SWIFT end-of-day customer statement | Opening and closing booked balance | Bookkeeping and reconciliation |
| MT942 | SWIFT interim transaction report, sent during the day | No booked opening or closing balance | Intraday cash monitoring, not month-end books |
| CAMT.053 | ISO 20022 XML end-of-day statement, the successor of MT940 | Opening and closing booked balance | Bookkeeping, with richer structured details |
For bookkeeping, download the end-of-day statement — MT940 or, if your bank offers it, CAMT.053. An interim report can still change before the day closes, and without booked balances it can't be checked.
Is MT940 being discontinued?
Not overnight. Swift moved cross-border payment instructions from MT to ISO 20022 when the coexistence period ended in November 2025. Statement and reporting messages such as MT940, MT942 and MT950 were not switched off then: they remain on the Swift network until Swift sets an end date, while banks and their customers move to the ISO 20022 equivalents. Their ISO 20022 equivalents are camt.053 for statements, camt.052 for intraday reports and camt.054 for debit and credit notifications. Details are on Swift's ISO 20022 standards page.
An MT940 file you download from online banking doesn't travel over the Swift network at all, so whether you can keep downloading it is your bank's decision. Many banks offer MT940 and CAMT side by side; if yours does, CAMT.053 is the future-proof choice. Either way, both convert to the same Excel file.
Several accounts and a year of daily statements
An MT940 export often contains one statement per day and sometimes several accounts. We group the statements by account (:25:) and currency. The days of one account join into a single statement that runs from the first opening balance (:60F:) to the last closing balance (:62F:), and every transaction in between must add up: opening balance plus money in minus money out equals the closing balance. If it doesn't — a missing day, for example — you see that before exporting.
Upload a year of files at once and export them as one workbook, or straight into accounting software. Accountants and bookkeepers use this to catch up a client's books, and it is the starting point for a bank reconciliation in Excel.
Questions
What is an MT940 file?
A SWIFT end-of-day bank statement in plain text. Tagged lines hold the account (:25:), opening balance (:60F:), one :61: line plus an :86: description per transaction, and the closing balance (:62F:).
How do I open an MT940 file in Excel?
Excel can't read MT940 directly; it shows the raw tags. Convert the file instead and you get one row per transaction with a date, a signed amount, payee and category.
What is the difference between MT940, MT942 and CAMT.053?
MT940 is the end-of-day statement, MT942 an interim report during the day without booked balances, and CAMT.053 the ISO 20022 XML successor of MT940.
Is MT940 being discontinued?
Swift kept MT940 on its network after the November 2025 payments migration, with no end date set yet, and banks are moving customers to CAMT.053. Whether your bank keeps offering MT940 downloads is up to the bank.
Which file extensions work?
.sta, .mt940 and .txt files are all read by their content, not their name. If your bank zips the files, unzip them before uploading.
Does converting an MT940 file use pages?
No. MT940, CAMT, CSV, Excel, OFX and QIF files use no pages, but you need a plan or a page pack to upload them. See pricing.
Keep reading
- Convert CAMT.053 files to ExcelConvert camt.053 bank statement XML to Excel or CSV: one row per entry with signed amounts, payee and category, checked against the file's balances.
- Convert bank statements to ExcelConvert any bank statement PDF, scan or photo to Excel in seconds. Every transaction categorized and checked against your balances. See it before you pay.
- Convert a bank statement to CSVConvert a bank statement PDF, scan or photo to CSV: one clean row per transaction, categorized and balance-checked. Comma or semicolon, any date format.
- Bank statement conversion for accountants and bookkeepersTurn a client's year of PDF statements, scans and photos into balance-checked transactions and import files for QuickBooks, Xero or Excel.
- How to do a bank reconciliation in ExcelHow to do a bank reconciliation in Excel: the step-by-step method, a template layout, the formulas to match transactions and a worked example.
Your next statement takes seconds.
See what we find on your statement before you pay.