Finance & Accounting
Convert MT940 bank statement transactions to CSV
Upload an MT940, STA or TXT statement. The :61: transaction lines become CSV rows with date, amount and debit or credit. Other lines are not converted.
or drop it here
- STA / MT940 / TXT
- Up to 100,000 transactions
1 prepared source file · 32 bytes
- Transactions: 1
- Unparsed transactions: 0
statement.csv · unparsed-records.csv · findings.csv · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Getting MT940 transaction lines into a CSV you can check
What you upload
You upload a bank statement as an STA, MT940 or TXT file, with up to 100,000 transactions per job. The converter reads the :61: transaction lines and turns each one into a CSV row with date, amount and debit or credit. Other lines in the statement are not converted.
What comes back
The download holds statement.csv, unparsed-records.csv, findings.csv and manifest.json. Debits carry a negative amount and credits stay positive, and the original record text stays available so you can check any row. Lines the converter cannot read go to unparsed-records.csv. If the file holds no supported transactions, you are told so rather than given an empty CSV that looks like a clean run.
Bank formats and your records
There are no options to set. Banks write MT940 in slightly different ways, and only a narrow part of the format is read. Anything outside it is listed in the unparsed file with a finding, so you can see what was skipped. Compare the transaction count and the totals with your bank statement before you import the CSV into your accounts.
Questions before you run it
Which MT940 tags does the parser read?
It works on a conservative subset of the :61: transaction line. Tags outside that subset are not interpreted, and anything it cannot parse goes to unparsed-records.csv instead of being guessed at.
How are debit and credit amounts signed in the export?
Explicit debit markers are normalized so debits carry a negative amount in the CSV and credits stay positive. The original record text remains available for checking.
Will it read my bank's MT940 dialect?
Coverage is deliberately narrow. Records matching the supported subset convert cleanly, while dialect-specific tokens land in the unparsed export with a finding, so you can see what was skipped rather than receiving a short statement that looks complete.
What happens when the file contains no supported transactions?
The job says so. You get an explicit report that no supported transactions were found, not an empty CSV that reads like a clean run.
How big a statement can I convert, and which file extensions work?
Up to 100,000 transactions per job, from STA, MT940 or TXT files.