Revolut MT940
Revolut MT940 statements can look valid while simple formatters still miss structured :86: fields, original amounts, FX rates, or card details. MT940 Toolkit shows those values in readable columns before you export CSV or split MT940 packages.
Revolut can split transfer data across MT940 fields differently than classic banks. A simple formatter may show only part of the description or miss the counterparty account, original amount, or FX rate. MT940 Toolkit detects that file shape and shows the values in reviewable columns.
Review the transaction table first: contractor, contractor account, description, operation code, currency, original amount, FX rate, and card data when the file contains it. Export is useful only after that check.
After validation, download CSV for spreadsheets or prepare MT940 packages split by account and month. CSV is one output, but the main value is a readable preview before handing data off.
The standard flow runs in the browser. Statement content, account numbers, transfer descriptions, and amounts do not need to be uploaded to a server for parsing and preparation.
Yes. An LT IBAN is not the user benefit by itself. It is one signal that the file may come from Revolut and need a different field mapping. In the interface, the important part is whether you can review the counterparty account, description, amounts, and FX rate before export.
Some Revolut data lives in structured narrative fields, for example :86: sections separated with ^ markers or slash fields such as /OCMT/ and /RATE/. Plain text-to-CSV converters may not parse them.
When the file contains /OCMT/ and /RATE/, the tool exposes original amount, original currency, and FX rate as transaction data and in CSV export.
Not in the standard flow. The file is read and parsed locally in the browser.