What is QIF Format?

The Quicken Interchange Format was introduced by Intuit alongside Quicken 3.0 for DOS in the early 1990s. At the time, personal finance software needed a simple way to import bank transactions that users downloaded from early online banking services or received on floppy disks from their financial institutions.

QIF became the de facto standard for personal finance data exchange throughout the 1990s. Microsoft Money adopted QIF import support, and most personal finance applications of the era could read and write QIF files. The format was simple enough that developers could implement parsers in a few dozen lines of code.

In 2005, Intuit officially deprecated QIF in favor of QFX (Quicken Financial Exchange), a proprietary variant of the OFX standard. Intuit removed the ability to import QIF files from Quicken 2005 and later versions for downloaded transactions, though manual QIF import remained available. The motivation was partly security — QIF files have no integrity verification — and partly commercial, as QFX requires banks to license Intuit's Web Connect service.

Despite the deprecation, QIF remains relevant in 2026. Millions of users have legacy QIF archives from decades of Quicken use. Open-source applications like GnuCash still support QIF import. And data migration between personal finance tools often involves QIF as an intermediate format.

A QIF file is plain text encoded in ASCII. It consists of a header line declaring the account type, followed by individual transaction records separated by the caret character (^). Each field within a transaction is identified by a single-character prefix at the start of the line.

The amount field (T) uses a signed value: negative for withdrawals (debits) and positive for deposits (credits). Dates follow the American MM/DD/YYYY convention, though some European exports use DD/MM/YYYY — a common source of parsing errors when exchanging QIF files across regions.

QIF supports multiple account types through the !Type: header: Bank for checking/savings, CCard for credit cards, Invest for investment accounts, and Oth A / Oth L for other assets and liabilities.

Since QIF is plain text, you can open any QIF file in a text editor like Notepad, VS Code, or TextEdit to inspect its contents. You will see the raw transaction records with their D/T/P/M prefixes.

To actually use the data, you need software that understands the QIF structure. Quicken can import QIF files through File > File Import > QIF File. GnuCash supports QIF import through File > Import > Import QIF.

For Excel or Google Sheets analysis, you need to convert QIF to a tabular format first. FinanceConvert's QIF to CSV converter parses the D/T/P/M records and produces a clean spreadsheet with Date, Description, Amount, and Memo columns. You can also convert to Excel (XLSX) for native date formatting and currency cells.

Date format ambiguity. QIF does not specify whether dates use MM/DD/YYYY (American) or DD/MM/YYYY (European) formatting. A date like D03/04/2026 could mean March 4 or April 3 depending on the source software. This is the most common source of QIF import errors and often requires manual verification of the first few records.

No duplicate detection. Unlike OFX and QFX, QIF transactions have no unique identifier (FITID). If you import the same QIF file twice, your accounting software will create duplicate entries. Always verify your import against existing records.

Missing balance data. QIF does not carry running balance information. When you import QIF transactions, the reconciliation process must rely on comparing totals against your bank statement rather than validating individual running balances.

Character encoding. QIF was designed for ASCII text. Extended characters (accented letters, non-Latin scripts) may not transfer correctly between applications. If your bank descriptions contain special characters, verify the output after conversion.

Split transactions. QIF supports split transactions (dividing one payment into multiple categories) using the S/$ prefix combination, but many importers and converters — including most online tools — flatten splits into a single line. If your QIF file uses splits extensively, verify that the total amounts are preserved after conversion.