Skip to main content
Skip to content
Back to MT940 to QBO Converter

What is MT940?

MT940 is a SWIFT message type used for end-of-day bank account statement reporting. It is the global standard for structured bank statements, widely used across Europe, Asia, and international banking systems.

Overview

MT940 stands for "Message Type 940" within the SWIFT (Society for Worldwide Interbank Financial Telecommunication) network. SWIFT assigns message type numbers to different categories of financial communication, and the 9xx series covers cash management and customer statements. MT940 specifically delivers end-of-day account statements from a bank to its corporate customers.

Unlike the XML-based formats common in US banking (OFX, QBO), MT940 uses a structured text format with tagged fields. Each field is identified by a colon-delimited tag number (like :20:, :25:, :61:), followed by the field data in a precisely defined format. This compact, text-based approach made MT940 efficient for transmission over the SWIFT network, where message size historically mattered.

MT940 has been the backbone of corporate treasury operations for decades. Companies use these statements to automate cash positioning, reconcile bank accounts, and feed transaction data into ERP systems like SAP and Oracle. A single MT940 file can contain all transactions for a given account on a given day, along with opening and closing balances.

While MT940 remains widely used, it is gradually being replaced by CAMT.053 (ISO 20022) as part of SWIFT's MT-to-MX migration program. The coexistence period means that businesses today often need to handle both formats. Converting MT940 to QBO format with PrimeConnect lets you bring these international bank statements into QuickBooks® without manual re-entry.

Key Features

SWIFT Standard

Defined and maintained by SWIFT as part of their FIN messaging framework. Used by 11,000+ financial institutions across 200+ countries for standardized statement delivery.

Structured Field Tags

Uses numbered tags (:20: for reference, :25: for account, :60F: for opening balance, :61: for transactions, :62F: for closing balance, :86: for details) ensuring consistent parsing.

Global Coverage

The dominant bank statement format in Europe, Asia-Pacific, Middle East, and Africa. Particularly entrenched in countries with strong corporate banking infrastructure like Germany, Netherlands, and Singapore.

Legacy Compatible

Text-based format that works with older systems and can be processed by virtually any programming language or ERP system without XML parsing libraries.

MT940 File Structure

An MT940 message consists of tagged fields, each prefixed with a colon and a tag number. The format is strict — each tag has a defined position and data format. Here is a simplified example:

:20:STMT20260215
:25:DEUTDEFF/DE89370400440532013000
:28C:00125/001
:60F:C260214EUR12500,00
:61:2602150215D89,50NTRFNONREF//BANK-REF-001
Electric Utility Payment
:86:020?00Electric Utility Co?20Monthly bill
?21Account 4456789?30COBADEFF?31DE123456
:61:2602150215C3200,00NTRFNONREF//BANK-REF-002
Payroll Deposit
:86:020?00Client Corp GmbH?20Invoice 2026-0042
?21Payment received?30COBADEFF?31DE987654
:62F:C260215EUR15610,50
:64:C260215EUR15610,50
:86:Total entries: 2  Debits: 1  Credits: 1

Key tags: :20: Transaction reference, :25: Account identification, :60F: Opening balance, :61: Statement line (transaction), :86: Information to account owner, :62F: Closing balance.

Understanding MT940 Fields

The :61: tag is the core of every MT940 statement — it represents a single transaction. The field packs date, amount, transaction type, and references into a compact string. For example, 2602150215D89,50NTRFNONREF means: value date February 15, 2026; entry date February 15; Debit; amount 89.50; transaction type NTRF (transfer); reference NONREF.

The :86: tag that follows each :61: line provides human-readable details about the transaction. Banks use sub-fields (prefixed with ?) to structure this information: ?20-?29 for remittance details, ?30 for the counterparty bank BIC, and ?31 for the counterparty account number.

Balance tags use a specific format: C or D (credit/debit), followed by the date in YYMMDD format, the currency code, and the amount with a comma as the decimal separator (European convention). The :60F: opening balance and :62F: closing balance must mathematically reconcile with the sum of all :61: transactions.

Compatible Systems

MT940 is natively supported by enterprise financial systems and can be converted for use with accounting software:

SAP ERP / S/4HANA

All editions

Oracle Financials

Cloud & on-premise

Microsoft Dynamics

365 Finance

Treasury Systems

Kyriba, GTreasury, etc.

Banking Portals

Most European banks

QuickBooks® (via QBO)

Convert with PrimeConnect

Note: SWIFT is migrating from MT (text-based) to MX (XML-based) message formats. MT940 is being replaced by CAMT.053 (ISO 20022). Both formats will coexist through the transition period, but new implementations should consider supporting CAMT.053 as well.

MT940 vs CAMT.053

Format

MT940 uses structured text with colon-delimited tags. CAMT.053 uses ISO 20022 XML with nested elements. XML provides richer data structures and is easier for modern systems to parse.

Data Richness

MT940's :86: field is limited to 6 lines of 65 characters. CAMT.053 offers structured remittance information with dedicated XML elements for creditor/debtor details, references, and purpose codes.

Character Set

MT940 is restricted to the SWIFT character set (Latin letters, digits, limited special characters). CAMT.053 supports full Unicode via XML encoding, handling international characters natively.

Ready to Convert?

Convert your MT940 bank statements to QBO format for QuickBooks® — free and instant.

Start Converting Free