Turn a SWIFT MT940 statement into a spreadsheet or an import ready OFX file. Upload the .sta, .940 or .mt940 your bank sends and download clean transactions with dates, signed amounts, tag 86 narrative, and opening and closing balances.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
An MT940 converter reads a SWIFT MT940 customer statement file and writes the transactions out as Excel, CSV or OFX so people and software can actually use them. Upload the .sta, .940 or .mt940 file your bank delivered and download a table with the value date, description from tag 86, signed amount, and the opening and closing balances from tags 60F and 62F. MT940 is a fixed SWIFT text format, so the parsing is deterministic: no guessing, no AI, the same file always produces the same rows.
MT940 is a machine to machine SWIFT format built for bank systems, not for people. Opened in a text editor it is a wall of colon delimited tags that nobody can reconcile against.
Everything lives inside tags like :61: and :86: on continuation lines, so there are no columns to sort, filter, or total the way finance work needs.
Renaming a .sta file to .csv does not help. The transaction data is packed into fixed width subfields, so Excel imports one useless column of raw text.
A single :61: line packs value date, entry date, debit or credit mark, amount, transaction type code, and bank reference into one run of characters with no separators.
MT940 marks direction with a C or D letter rather than a plus or minus, so a naive copy paste leaves every amount positive and every total wrong.
Tag 86 can run to six lines of 65 characters, and the counterparty name or invoice reference you need for reconciliation is split across them.
Quicken, MS Money, and plenty of accounting tools import OFX but have never read MT940, so the statement has to be translated before it can be loaded.
Upload the statement file, the parser walks the SWIFT tags in order, and you download the transactions as Excel, CSV or OFX.
Parses :20:, :25:, :28C:, :60F:, :61:, :86: and :62F: the way the MT940 specification defines them, rather than pattern matching lines of text.
Credit and debit marks in tag 61 are turned into properly signed amounts, so totals and reconciliation come out right in the spreadsheet.
Multi line narrative is stitched back into one readable description field, keeping the counterparty and reference text you reconcile against.
The 60F opening balance and 62F closing balance come through, so you can prove the extracted rows tie back to the statement.
MT940 has a fixed layout, so it is parsed by rule. There is nothing to interpret and the same file always yields the same transactions.
Take a workbook for analysis, a CSV for an ERP or bank import template, or an OFX for Quicken, MS Money, and accounting software.
No install, no SWIFT expertise, no credit card to start.
Drop in the statement your bank delivered. The usual extensions are .sta, .940, .mt940 and sometimes plain .txt.
Tip: If the file opens in Notepad and starts with :20:, it is an MT940.
Review the table of value dates, descriptions, signed amounts, and balances before you export anything.
Tip: Compare the closing balance against tag 62F on the statement.
Pick the output your next system wants and download it. OFX imports into Quicken and MS Money, CSV and Excel go anywhere.
Tip: Choose OFX when the destination is personal finance software.
Finance and treasury teams whose bank delivers SWIFT statements rather than a friendly download.
Companies receiving daily MT940 statements from a global bank who need the activity in a spreadsheet for cash positioning.
Teams loading historical bank activity into SAP, Oracle, or NetSuite who need MT940 flattened into an importable table first.
Anyone reconciling a subsidiary account where the only statement available from the bank is a SWIFT file.
Reviewers who receive an MT940 as source evidence and need the transactions in a sortable, totalable format.
MT940 is the SWIFT message type for an end of day customer statement. A bank generates one per account per day and it carries the opening balance, every posting for the period, and the closing balance. It is plain text made of tagged fields, and it usually arrives with a .sta, .940 or .mt940 extension. Because it is a bank to bank standard rather than a consumer download, the format assumes the receiving side is a treasury system, which is exactly why it needs converting before a human or a spreadsheet can use it.
Every MT940 is built from the same short list of tags in the same order. Knowing what each one holds makes it obvious where the converted columns come from.
| SWIFT tag | What it holds | Where it lands |
|---|---|---|
| :20: | Transaction reference for the statement message | Statement identifier |
| :25: | Account identification | Account number on the export |
| :28C: | Statement and sequence number | Statement number |
| :60F: | Opening balance with currency and date | Opening balance row |
| :61: | One transaction: value date, entry date, C or D mark, amount, type code, reference | Date and signed amount columns |
| :86: | Narrative for the transaction above, up to six lines | Description column |
| :62F: | Closing balance with currency and date | Closing balance row |
The right export depends entirely on what reads the file next. If a person is going to look at it, take Excel. If a system is going to load it, take CSV. If the destination is personal finance or older accounting software, take OFX, because that is the format those tools were built to import.
| Output | Best for | Keeps |
|---|---|---|
| Excel (XLSX) | Reconciliation, cash positioning, review by a person | Formatting, number types, multiple sheets |
| CSV | Loading into an ERP, a database, or a bank import template | Plain values, maximum compatibility |
| OFX | Quicken, MS Money, accounting software with an OFX import | Account structure and transaction typing |
Working with a different bank format? BAI2 is the American equivalent of MT940 and the BAI to OFX converter handles it, while the bank statement to OFX converter reads ordinary PDF statements.
Treasury teams rarely deal with only one statement format. MT940 is the SWIFT standard, BAI2 is what US banks tend to send for cash management, and OFX is what desktop finance software imports. They describe the same underlying activity in very different envelopes.
| Format | Origin | Typical use |
|---|---|---|
| MT940 | SWIFT message standard | End of day statements from global and correspondent banks |
| BAI2 | Bank Administration Institute | US cash management reporting, often intraday |
| OFX | Open Financial Exchange | Consumer and small business finance software imports |
| CAMT.053 | ISO 20022 XML | The modern successor banks are migrating statements toward |
Before you use converted data for anything that matters, run one check: take the opening balance from tag 60F, add the signed total of every converted transaction, and confirm it equals the closing balance in tag 62F. If it does, nothing was dropped or mis signed. That single reconciliation catches almost every conversion problem, and it takes one formula in the spreadsheet. If you need the resulting file inside Quicken afterward, converting a bank statement to Quicken walks through the import side.
Upload the .sta, .940 or .mt940 file to the converter above and download the XLSX. The parser reads the SWIFT tags, turns each :61: line into a dated row with a signed amount, joins the :86: narrative into a description, and carries the opening and closing balances through so the workbook ties back to the statement.
MT940 is the SWIFT message type for an end of day bank account statement. It is a plain text file of tagged fields carrying the opening balance, every transaction for the period, and the closing balance. Banks send it to corporate customers and treasury systems, typically with a .sta, .940 or .mt940 extension.
An MT940 opens in any text editor because it is plain text, but you will see raw SWIFT tags rather than readable transactions. To actually work with it, convert it to Excel or CSV first so the value dates, descriptions, and signed amounts sit in proper columns you can sort and total.
Tag 61 carries the transaction itself: value date, entry date, a C or D mark for credit or debit, the amount, a transaction type code, and a bank reference, all packed into one line. Tag 86 is the optional narrative that follows it, up to six lines of 65 characters holding the counterparty name and any payment reference.
Yes. Upload the MT940 and choose OFX as the output. Quicken and MS Money have never read SWIFT files, but they import OFX directly, so converting first is what gets the statement into your register. For Quicken specifically, the Web Connect QFX variant also works.
MT940 does not use plus and minus signs. Tag 61 marks direction with a C for credit or a D for debit immediately after the dates, so a copy paste that ignores that letter leaves every amount positive. A proper converter reads the mark and applies the sign, which is why converted totals reconcile and hand copied ones do not.
No. Both are bank statement file formats, but MT940 is the SWIFT standard used internationally while BAI2 comes from the Bank Administration Institute and is common for US cash management reporting. They carry similar information in completely different layouts, so a file has to be parsed according to its own specification.
Uploads are protected by 256-bit encryption in transit and you can delete the file at any time. Before sending any account data to an online tool, confirm it encrypts uploads, lets you control deletion, and publishes a retention policy you are comfortable with.
Send MT940 straight to a reconciling Excel workbook.
Turn a converted OFX file into a clean Excel workbook.
Convert the US BAI2 cash management format.
Convert an ordinary PDF statement to OFX.
Turn a PDF statement into clean CSV.
Get started converting bank statements to OFX.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
