Choose an MT940 file
Open a UTF-8 .mt940, .940 or .sta export from your bank, up to 2 MB.
Inspect an MT940 statement and export an Excel workbook with transaction rows and statement-level account and balance information.
The workbook keeps monetary values and identifiers as text cells to avoid rounding and accidental spreadsheet formulas.
Choose a file, then use Download Excel to save the result.
Also with this file: View statement · Download CSV · Download JSON
Open a UTF-8 .mt940, .940 or .sta export from your bank, up to 2 MB.
Inspect accounts, balances and transaction rows before exporting.
Save transactions as CSV, a two-sheet Excel workbook or the normalized JSON model.
Read transaction and balance fields without searching through MT940 tags.
Move exact decimal strings and references into CSV or Excel for your own checks.
Use normalized JSON as a starting point for a local data workflow.
The details that matter before you use MT940 Viewer.
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.
No. Opening and closing balances are displayed as supplied, without inferring missing transactions or certifying bank totals.
Amounts are exact decimal strings. Credit and debit are separate fields; the exporter never converts money through floating point.
CSV contains transaction rows. Excel includes transaction and statement sheets. JSON preserves the complete normalized statement model.
Excel cells are written as text. Formula-like CSV cells receive a leading apostrophe; JSON retains raw semantic values.
No. Parsing and exports run in the browser. File contents, filenames and account details are excluded from analytics.
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.