How to Convert an MT940 File to QuickBooks (QBO or CSV)

Last updated July 2026.

QuickBooks cannot read an MT940 file directly. Neither QuickBooks Online nor QuickBooks Desktop accepts the SWIFT MT940 text format, so the reliable path is to convert the MT940 into a file QuickBooks does accept: a QBO (Web Connect) file for a near one-click import, or a mapped CSV with Date, Description, and Amount columns. Convert first, then import through the Banking screen.

MT940 is the end-of-day SWIFT account statement most common with European and multinational banks and corporate treasury feeds. QuickBooks was built around US bank download formats (QBO, QFX, OFX, and CSV), so it has no idea what to do with the tag-based MT940 structure. Below is exactly how to bridge the two, for both QuickBooks Online and Desktop.

Which file formats QuickBooks actually accepts

Before converting, it helps to know your two realistic targets. QBO is the fastest and cleanest; CSV is the most flexible when a QBO file is not an option.

Step 1: Convert the MT940 file

Upload the .mt940 or .sta text file to the MT940 to Excel converter. It parses the :61: transaction lines and :86: descriptions, keeps the value date, amount, and debit or credit sign, and lets you export either a QuickBooks-ready QBO file or a clean CSV. If your books already run in QuickBooks, the QuickBooks bank statement converter is the same engine aimed straight at that import.

Two rules make the rest of the process painless: pick one account per file (QuickBooks imports into a single register at a time), and use QBO output when you can, because it carries a bank ID and account number so QuickBooks can match and de-duplicate transactions on its own.

Step 2: Import into QuickBooks Online

Once you have a QBO or CSV file, the import lives under Banking (or Transactions).

Importing a QBO file

Go to Banking > Link account > Upload from file, choose the QBO file, pick the QuickBooks account to import into, and confirm. QuickBooks reads the dates, amounts, and descriptions automatically and drops the transactions into For Review, where you accept or categorize them.

Importing a CSV file

Choose Upload from file, select your CSV, then map the columns: set Date, Description, and Amount (or separate Debit and Credit columns if you split them). Confirm the date format matches your file (MM/DD/YYYY for US files), pick the account, and finish. The transactions land in For Review the same way.

Step 3: Import into QuickBooks Desktop

QuickBooks Desktop imports a QBO file through File > Utilities > Import > Web Connect Files. Select the converted QBO file, choose the account, and Desktop matches the transactions against the register. For CSV in Desktop you generally need a mapping add-on, so a QBO file is the smoother route on Desktop specifically.

How to avoid duplicate transactions

Duplicates happen when a date range overlaps a period you already imported. QBO files are duplicate-aware because they carry a transaction ID, so QuickBooks flags repeats. With CSV there is no such ID, so import clean, non-overlapping date ranges and review the first and last few rows before accepting. If duplicates slip in, exclude them from the For Review tab rather than deleting posted transactions. Our guide on stopping duplicate transactions when importing covers the edge cases.

Can I convert QBO back to MT940?

Sometimes a treasury system or a European ERP wants the statement in MT940 rather than the other way around. That is the reverse conversion: it takes the QBO or CSV transactions and rebuilds the SWIFT :20:, :25:, :60:, :61:, :86:, and :62: tag structure. It is a niche need, but if a bank portal or cash-management tool is asking for MT940 specifically, keep the original statement and convert from that source rather than round-tripping through QuickBooks, which drops the SWIFT metadata.

Why not just paste the MT940 into Excel first?

You can open an MT940 file in a text editor, but it is a tag-based flat file, not columns. The transaction amount, sign, value date, and narrative are spread across :61: and :86: tags on different lines, so a raw paste into Excel gives you one long column of SWIFT codes, not a usable ledger. Converting parses those tags into real Date, Description, and Amount fields. If you only need the spreadsheet and not the QuickBooks import, the same tool exports straight to Excel, and once the rows are clean you can pair the statement data with automated receipt and expense capture so card spend is coded alongside the bank feed.

MT940 to QuickBooks, start to finish

The whole workflow is three steps: convert the MT940 to QBO or CSV, upload it under Banking, then review and categorize. Use QBO output whenever you can for duplicate-safe matching, keep one account per file, and import non-overlapping date ranges. For the format background, see how to read an MT940 file and MT940 vs MT942. When you are ready, the bank statement converter handles MT940, PDF, and every other format from one upload.