Choose an MT940 file
Open a UTF-8 .mt940, .940 or .sta export from your bank, up to 2 MB.
Make bank statement data readable.
MT940 to JSON
Parse an MT940 statement into structured JSON preserving transaction dates, exact decimal strings, debit or credit direction, references and source remittance text.
Review the statement locally, then download the normalized model without spreadsheet-specific cell escaping.
MT940 ViewerYOUR WORKSPACE
Your task
Download JSON
Choose a file, then use Download JSON to save the result.
Also with this file: View statement · Download CSV · Download Excel
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Review the statement
Inspect accounts, balances and transaction rows before exporting.
Download the format you need
Save transactions as CSV, a two-sheet Excel workbook or the normalized JSON model.
Made for the everyday
A useful part of your workflow.
Bank export review
Read transaction and balance fields without searching through MT940 tags.
Spreadsheet preparation
Move exact decimal strings and references into CSV or Excel for your own checks.
Structured integration
Use normalized JSON as a starting point for a local data workflow.
Good to know
A few useful answers.
The details that matter before you use MT940 Viewer.
Which MT940 files are supported?
This version reads UTF-8 statements with standard :20:, :25:, :60F/:60M, :61:, :86: and :62F/:62M tags. Bank-specific :86: subfields remain plain text.
Are balances reconciled?
No. Opening and closing balances are displayed as supplied, without inferring missing transactions or certifying bank totals.
How are monetary values handled?
Amounts are exact decimal strings. Credit and debit are separate fields; the exporter never converts money through floating point.
What do the downloads contain?
CSV contains transaction rows. Excel includes transaction and statement sheets. JSON preserves the complete normalized statement model.
Can a spreadsheet run formulas from the export?
Excel cells are written as text. Formula-like CSV cells receive a leading apostrophe; JSON retains raw semantic values.
Does the file leave my device?
No. Parsing and exports run in the browser. File contents, filenames and account details are excluded from analytics.
What are the limits?
Files must be UTF-8 text up to 2 MB, with at most 50 statements and 10,000 transactions. Unsupported variants fail with a clear error.