Skip to main content
Skip to content
FREE TOOL — BROWSER-BASED

Convert MT940 Bank Statements to
QuickBooks QBO

Import SWIFT MT940 European bank statements into QuickBooks. Handles European date formats, comma decimals, and multi-currency transactions.

100% PrivateEuropean BanksMulti-Currency

FAQ

MT940 to
QuickBooks
Questions

Can't find what you're looking for? Reach out to our support team.

Contact Support

It converts SWIFT MT940 bank statement files into QuickBooks-compatible QBO (Web Connect) format. The tool parses MT940 tagged fields (:61: for transactions, :86: for descriptions, :25: for account info), converts European comma-decimal amounts to US format, reformats dates, and produces a standard OFX/QBO file that QuickBooks can import directly.

Understanding MT940 and Why You Need a QBO Converter

MT940 is the SWIFT standard for electronic bank account statements, formally known as “Customer Statement Message.” Developed by the Society for Worldwide Interbank Financial Telecommunication (SWIFT), the MT940 format has been the backbone of corporate banking in Europe and much of the international financial system for decades. It provides a structured, machine-readable representation of bank account activity using a tag-based format that encodes account identification, opening and closing balances, individual transactions, and narrative descriptions.

While MT940 is perfectly suited for European banking systems and treasury management platforms, it presents significant challenges when you need to import the data into QuickBooks — the dominant accounting software in North America. QuickBooks expects either CSV files with specific column formats or QBO (Web Connect) files that follow the OFX (Open Financial Exchange) specification. MT940 uses none of these conventions. The date formats are different (YYMMDD vs. YYYYMMDD), amounts use comma decimal separators instead of periods, and the overall document structure is completely incompatible with QuickBooks' import parsers.

How the MT940 Format Works

An MT940 file is organized into statement blocks, each beginning with a :20: tag (transaction reference number) and containing a series of tagged fields that describe the account's activity for a given period. The key tags include:

  • :25: — Account Identification — Contains the bank code and account number, often in IBAN format (e.g., NL91ABNA0417164300). This identifies which bank account the statement belongs to.
  • :60F: — Opening Balance — Shows the account balance at the start of the statement period. Includes a credit/debit indicator, date, currency code (ISO 4217), and the balance amount with comma decimal.
  • :61: — Statement Line — Each individual transaction. Encodes the value date (YYMMDD), an optional booking date (MMDD), credit/debit indicator (C, D, RC, RD), the transaction amount, a SWIFT transaction type code, and customer reference information.
  • :86: — Information to Account Owner — The narrative description that follows each :61: line. Contains free-text information about the transaction, such as the counterparty name, payment reference, or remittance information. Some banks use structured sub-fields separated by question marks.
  • :62F: — Closing Balance — The account balance at the end of the statement period. The difference between opening and closing balances should equal the sum of all transaction amounts.

European Banking and MT940 Adoption

MT940 is the default electronic statement format for the vast majority of European banks. If your business operates across borders — receiving payments from European customers, paying European suppliers, or maintaining bank accounts in the EU — you'll encounter MT940 files regularly. Major banks that provide MT940 statements include Deutsche Bank, ING, Rabobank, ABN AMRO, KBC, BNP Paribas, Commerzbank, UniCredit, Nordea, Danske Bank, SEB, and Handelsbanken, among many others.

Beyond Europe, MT940 is also used extensively in corporate banking across Asia, the Middle East, and Africa. Global companies with multi-country treasury operations often receive MT940 files from dozens of banks, making automated conversion to QuickBooks format essential for efficient bookkeeping.

Why Convert MT940 to QBO for US Accounting?

If you're using QuickBooks for your accounting and receive bank statements in MT940 format, manual data entry is impractical. The converter bridges this gap by transforming MT940 into QBO (Web Connect) format, which QuickBooks natively supports for bank transaction imports. Key benefits of converting to QBO include:

  • Native QuickBooks compatibility — QBO files import directly through QuickBooks' built-in Web Connect import feature. No manual column mapping or date reformatting required.
  • Transaction deduplication — Each transaction gets a unique FITID (Financial Transaction ID) generated from its content. QuickBooks uses this to prevent duplicate imports when you re-import updated statements.
  • Proper credit/debit classification — MT940 uses C (credit), D (debit), RC (reversal credit), and RD (reversal debit) indicators. The converter maps these to the appropriate OFX transaction types (CREDIT, DEBIT) that QuickBooks expects.
  • Preserved descriptions — The :86: narrative text is mapped to both the NAME and MEMO fields in the QBO output, ensuring you have full transaction details available for categorization and reconciliation in QuickBooks.

How the Converter Handles European Formats

The most common pain point when moving data between European and US accounting systems is format incompatibility. The MT940 to QBO converter addresses every format difference:

  • Comma decimal separators — European convention uses commas for decimal points (1.234,56 instead of 1,234.56). The parser converts all comma-decimal amounts to period-decimal format for the QBO output.
  • Two-digit year dates — MT940 uses YYMMDD format (260115 for January 15, 2026). The converter expands these to full 4-digit years and reformats to the YYYYMMDD format that OFX requires.
  • Booking date resolution — MT940 :61: lines include an optional 4-digit booking date (MMDD) that's relative to the value date's year. The converter handles year-boundary cases (e.g., booking in December with value date in January).
  • SWIFT envelope stripping — Some MT940 files arrive wrapped in SWIFT message envelopes ({1:...}{4:...-}). The parser automatically detects and strips these envelopes to access the statement content.
  • BOM handling — European banking systems frequently export files with a UTF-8 byte order mark (BOM) prefix. The parser strips this automatically so it doesn't interfere with tag detection.

Importing QBO Files into QuickBooks

After converting your MT940 file to QBO format, follow these steps to import into QuickBooks:

QuickBooks Online

  1. Log into QuickBooks Online and navigate to Banking from the left sidebar.
  2. Click Upload transactions (or “Link account” → “Upload from file” if this is your first import).
  3. Select the downloaded .qbo file from your computer.
  4. QuickBooks will display a preview of the imported transactions. Verify that dates and amounts look correct.
  5. Choose the QuickBooks account to import into (e.g., create an account named after your European bank).
  6. Click Import to complete the process. Transactions will appear in the “For Review” tab.

QuickBooks Desktop

  1. Open QuickBooks Desktop and go to FileUtilitiesImportWeb Connect Files.
  2. Browse to and select your converted .qbo file.
  3. QuickBooks will prompt you to select or create an account for the imported transactions.
  4. Click Continue to import. Transactions will appear in the bank register for review and categorization.

Tip: Create a dedicated account in QuickBooks for each European bank account (e.g., “Deutsche Bank EUR” or “ING Netherlands”). This makes reconciliation easier and keeps your European transactions organized separately from domestic accounts.

Multi-Currency Considerations

When importing European bank statements into QuickBooks, currency handling is an important consideration. The MT940 parser detects the currency code from the :60F: (opening balance) field and displays it in the tool's preview. Common currencies include EUR (Euro), GBP (British Pound), CHF (Swiss Franc), SEK (Swedish Krona), NOK (Norwegian Krone), and DKK (Danish Krone).

QuickBooks Online supports multi-currency accounting — when enabled, you can create bank accounts denominated in foreign currencies and import transactions in their original currency. QuickBooks Desktop has more limited multi-currency support, but you can still import the transactions and manually adjust exchange rates during reconciliation.

All transaction amounts in the QBO output are preserved exactly as they appear in the MT940 source file. The converter does not perform any currency conversion — amounts are imported at face value, and you handle exchange rate differences in QuickBooks as part of your normal reconciliation workflow.

Understanding SWIFT Transaction Type Codes

MT940 :61: lines include a SWIFT transaction type code that categorizes each transaction. Common codes include NMSC (miscellaneous), NTRF (transfer), NCHK (check), NDDT (direct debit), NSTO (standing order), and NINT (interest). The converter includes these codes in the MEMO field of the QBO output so you can use them for categorization in QuickBooks.

The converter maps C (credit) and RC (reversal credit) transactions as positive amounts (inflows), and D (debit) and RD (reversal debit) transactions as negative amounts (outflows). This standard mapping ensures that your QuickBooks bank register correctly reflects the direction of each transaction.

Related Free Accounting Tools

The MT940 to QBO Converter is part of our complete suite of free QuickBooks conversion tools: