Designed for finance exports
The parser recognises date, description, amount, debit/credit, memo, category, and transaction id fields, including headers like Narration or Withdrawal Amt. used by many banks.
Finance file converter
Convert SWIFT MT940 statement transactions into Quicken Interchange Format. Upload a file or paste its contents, check the parsed transactions, then download the QIF file.
1 · Source
2 · Result
Nothing converted yet
A sample MT940 file is loaded — press “Convert to QIF” to see how the output looks.
The parser recognises date, description, amount, debit/credit, memo, category, and transaction id fields, including headers like Narration or Withdrawal Amt. used by many banks.
Each conversion shows the parsed transactions with money in, money out, and date range, plus warnings about ambiguous dates or missing account details.
PDFs and text files are read by your browser and never sent to a server. Close the tab and the data is gone.
QIF (Quicken Interchange Format) is a plain-text format that Quicken and a number of older personal finance programs use to import transactions. Each transaction is a short block of single-letter lines: D for the date, T for the amount, P for the payee, M for the memo, and a caret (^) to end the block. Many current programs prefer OFX, so people who receive SWIFT MT940 statements sometimes need QIF only for an older program.
This MT940 to QIF Converter reads each :61: line and its :86: narrative, then writes a QIF file with a !Type:Bank header. The payee comes from the counterparty subfield when the bank provides one, the amount is signed, and the bank reference is written as an N line. The file is built in your browser.
A QIF bank file starts with !Type:Bank. Each transaction then has a date line (D), an amount line (T), a payee line (P), and optional lines for the number (N), memo (M) and category (L), followed by ^. The converter writes the dates as MM/DD/YYYY, which is the form most Quicken US installs expect.
The amount is written with a full stop and a minus sign for money out. The converter takes the amount from the :61: line and the payee from ?32 or ?33 when they exist. Without subfields, the narrative text becomes the payee, which can be long.
The converter first reads the MT940 transactions into rows with a date, a signed amount, a payee, a memo and a reference. It then writes each row as a QIF block, in the order the statement lists them.
Date lines are rewritten from ISO dates to MM/DD/YYYY, so the output does not depend on the date order you chose.
MT940 (trimmed)
:61:2605030503DN39,99NTRFNONREF//BK-1001
:86:?00TRANSFER?10000000?20INVOICE 4411?32CLOUD HOSTING LTDQIF
!Type:Bank
D05/03/2026
T-39.99
PCLOUD HOSTING LTD
NBK-1001
MINVOICE 4411
^Importing into the wrong account type. The file header is !Type:Bank, so pick a bank or cash account when Quicken asks for the account type.
Expecting balances. QIF transaction files do not carry opening or closing balances, so the account balance in Quicken will be the sum of the imported transactions.
Expecting every subfield to appear. Only the counterparty and the reference are written as payee and number. The purpose text goes to the memo when a counterparty exists.
Relying on categories. The converter does not write L (category) lines because MT940 has no category field.
Why does the QIF file use the caret symbol?
The caret (^) ends each transaction block. QIF readers use it to know where one transaction stops and the next begins.
Is QIF still supported by Quicken?
Quicken versions differ in which import formats they accept, so check your version’s import menu before relying on the file.
For more background on data formats and conversion workflows, read our format guides.