Convert a SWIFT MT940 statement into a QuickBooks Web Connect (.qbo) or .ofx file. Free, no signup, no size limit.
.sta, .mt940, .txt
MT940 is a SWIFT text format built from tagged fields — :25: account, :60F:
opening balance, :61: statement lines, :86: free-text descriptions that often
wrap onto unlabelled continuation lines, and :62F: closing balance. QuickBooks has no MT940
importer; it expects OFX SGML in a .qbo wrapper with a valid financial institution ID. Banks
in Europe and Asia that still issue MT940 statements leave QuickBooks users to convert manually — or with
this tool, automatically.
Two MT940 quirks matter for a clean import: amounts use a decimal comma
(1200,50), which this converter normalises to a decimal point before it ever reaches the OFX
builder, and the debit/credit mark in :61: (C, D, plus reversal
codes RC/RD) is translated into the negative-for-debit sign OFX expects.
:61:2507150715D1200,50NDDTREF67890//BANKREF002 :86:DIRECT DEBIT INSURANCE CONTINUATION LINE FOR INSURANCE
becomes an OFX <STMTTRN> with TRNAMT>-1200.50,
DTPOSTED>20250715, a FITID built from BANKREF002, and the full description —
including the continuation line — in <MEMO>.
No. Everything, including OFX/QBO generation, runs in your browser. There is no server component — verify with your browser's network tab, or use the page fully offline.
Yes — many banks still deliver MT940 alongside newer CAMT.053 XML, and MT940-only banks are still common outside the EU, so converting straight to QBO/OFX remains the fastest path into QuickBooks.
Reversal credit/debit marks are treated the same as their non-reversal counterparts for sign purposes, so a reversed debit still posts as a positive amount in the OFX output.
Almost always the <INTU.BID> value. Try the .ofx download instead; it carries the same transactions without the financial-institution check that QuickBooks Desktop enforces.