Direct answer
MT940 is a SWIFT customer statement. Excel cannot parse :61: and :86: tags into a cash book. F20 FinanceOps is a fit if you want a free MT940-to-CSV/Excel conversion with an opening-versus-closing check, then bank reconciliation. StatementBridge is a fit if you need MT940 to camt.053, OFX or CODA for European packages. Univik describes an offline Windows converter with batch folders. BankXLSX lists MT940 among formats on its site but is centred on PDF OCR. There is no SWIFT-issued official converter.
MT940 has been the workhorse customer statement for decades. Banks still send .sta, .swi, .mt940 and .txt files. The message carries an opening balance, tagged statement lines, narrative, and a closing balance. It does not carry BAI2-style control-total trailers. The check that matters is arithmetic: opening plus net movement against the closing the message states.
Converters fail in boring ways. They mishandle continuation lines on :61:. They treat one bank's :86: dialect as unstructured junk. They write UTF-8 without a BOM and a European ERP then splits amounts on commas. 'Best' means the tool whose failure modes you can see.
What an MT940 converter should expose
Tags at minimum: :20: reference, :25: account, :28C: statement number, :60F:/:60M: opening, :61: line, :86: narrative, :62F:/:62M: closing. Reversals (RD/RC) should not silently look like new money. Multi-statement files with several :20: blocks should not collapse into one account.
Bank dialects differ. StatementBridge's official page documents ING structured :86:, ABN AMRO envelopes, Rabobank field order, Triodos sparse narratives. A converter that only knows one bank will look 'accurate' until the second bank feed arrives.
F20 FinanceOps
F20 reads SWIFT MT940 into one row per transaction through the same parse-then-validate pipeline as BAI2. The closing-balance check is opening plus net against the message. Download CSV or XLSX. No account, no charge, file not stored. Next steps on the same site: statement quality, then bank-to-cash-book matching.
F20 does not emit camt.053 XML, OFX, QBO or CODA. If your ERP still wants MT940-shaped import after conversion, you may want a specialist. If you want rows you can filter and a recon against a cash book, F20 is built for that.
StatementBridge
Official page: upload .sta/.940/.mt940/.txt, review transactions, export camt.053, Excel/CSV, OFX or CODA. Compatibility copy names Exact Online, Twinfield, AFAS, Visma, SnelStart, e-Boekhouden, Yuki, Unit4, AccountView. That is a European accountant's converter, not a US BAI2 shop's converter.
We did not verify StatementBridge pricing on 8 September 2026. Treat price as NOT VERIFIED until you read their checkout.
Univik
Univik describes 100% offline conversion, all standard MT940 tags, Excel, CSV, PDF, OFX, QIF, QBO, batch folders. Offline matters for teams that will not put a statement on someone else's server. F20 processes in memory and does not store the file, but it is still a web request. Those are different threat models. We have not tested Univik's parser.
BankXLSX and open-source parsers
BankXLSX lists MT940 on its marketing surface. Its centre of gravity remains PDF OCR. If MT940 is your only format, paying for OCR capacity you will not use is optional.
Libraries such as x940 exist for engineers who want JSON/CSV/camt.053 from a script. That is the Python article's job. A controller who does not want a runtime should not be sent to PyPI as if it were a product.
Comparison table
Sourced where noted. Gaps marked.
| Job | F20 | StatementBridge | Univik |
|---|---|---|---|
| MT940 to CSV/Excel | Yes | Yes | Yes (vendor claim) |
| Opening/closing check | Yes | Review step described | Validation claimed; not tested |
| MT940 to camt.053 | No | Yes | Not the headline |
| Offline / no server | In-memory, not stored; still a web tool | Web upload described | Claims 100% offline |
| Price | No charge | NOT VERIFIED | NOT VERIFIED |
Pricing and privacy
F20: no charge; files not stored. StatementBridge and Univik: re-read their sites. Do not assume 'converter' means 'free' or 'local'.
If policy forbids any third-party processing, Univik's offline claim or an in-house library is the conversation. F20's legal page is still a third party processing the bytes in memory, even though it does not keep them.
Methodology
Official pages dated 8 September 2026. No bake-off. Learn what MT940 is on /learn/bank-files/what-is-mt940. Pairwise format compare: /compare/formats/mt940-vs-camt053.
Where F20 FinanceOps is a better fit
- You want MT940 as rows, a closing-balance check, and a free reconciliation step next.
- You do not need camt.053, CODA or QBO out of the converter.
- You are willing to use a web tool that does not store the file.
Where another MT940 converter is a better fit
- You must produce camt.053, OFX or CODA for a named EU package: StatementBridge documents those outputs.
- Policy requires a desktop converter with no network: Univik describes that.
- Your only statements are scanned PDFs: BankXLSX or Nanonets, not an MT940 parser.
- You are writing a pipeline: use a library, not a UI. See Python vs reconciliation software.
FAQ
Interbank rails have been moving to ISO 20022. Bank-to-corporate MT940 files still arrive. If your bank sent .sta, you still need a converter. We do not treat retirement headlines as 'this file no longer exists'.
If the accounting system wants XML parties and structured remittance, ask for camt.053. If it still has an MT940 importer, keep MT940. F20 converts both to rows.
Best fit for free rows plus recon. Not best for camt.053 emission or offline Windows batch, based on what those vendors publish.
Yes. Synthetic MT940 on the tool page and /samples/mt940. Not customer data.
It parses statement lines into rows and checks balances. Exotic bank-specific subfields may land in narrative. If a dialect matters to posting, inspect the rows before you import.
Sources
- F20 FinanceOps policies — F20 FinanceOps. Verified. Uploaded files are processed in memory and dropped when the response is sent. There is no charge to run a tool. Output is not professional advice.
- MT940 Converter | StatementBridge — StatementBridge. Verified. StatementBridge converts MT940 to camt.053, CSV, Excel, OFX and CODA, aimed at Dutch and European accounting packages.
- MT940 Converter | Univik — Univik. Vendor claim. Univik describes an offline Windows MT940 converter to Excel, CSV, OFX, QIF and QBO. F20 has not independently tested it.
- Bank Statement Converter: PDF Bank Statements to Excel & CSV — BankXLSX. Verified. BankXLSX converts PDF bank statements to Excel, CSV, JSON, or QuickBooks QBO, including scanned statements.
Convert MT940 to CSV or Excel — If the bank already sent camt.053, use that converter instead of round-tripping.