What Is a QIF File?

The short answer

A .qif file is a Quicken Interchange Format file: a plain-text list of transactions, readable in any text editor. Each line begins with a single letter saying what the rest of the line is: D for date, T for amount, P for payee. A lone caret ^ marks the end of one transaction and the start of the next.

It is the oldest format still in general use for moving transactions between accounting programs, and the simplest. That simplicity is both why it survived and why it is limited: a QIF states no balance, names no bank, and gives no transaction a unique identifier.

QIF describes movements only. If you need a file that also states a closing balance, or one that names the institution the statement came from, the format cannot express either. See the comparison below.

What a QIF file looks like inside

Open one in a text editor and you will see something close to this. Nothing is compressed or encoded, so what is on screen is the whole file:

!Type:Bank
D01/05/2026
T-24.50
PCOFFEE SHOP
MMorning coffee
^

That is one transaction: a header naming the kind of account, four fields, and a caret closing the entry. Every field is on its own line, which is the single most important thing to know about the format. It is why a QIF cannot be read as a table, and why one transaction occupies six lines rather than one.

Codes are case-sensitive and always the first character of the line. Anything a reader does not recognise is skipped rather than treated as an error, which is why files written by different programs remain broadly readable by each other.

The header lines, and why they matter

A line beginning with ! does not describe a transaction. It says how the lines beneath it should be read. This is the part of the format most often got wrong, because the same letter means different things in different sections.

Under !Type:Bank, a T line is an amount. Under !Account, a T line is an account type, the word Bank or CCard. A reader that ignores the headers and treats every T as money will turn a list of accounts into a list of transactions, and it will do so without reporting an error.

Splits, and why a QIF can look doubled

A split transaction is one payment filed under more than one category, such as a supermarket trip that was partly groceries and partly household. In a QIF the entry states its total on the T line, and then lists the parts on S, E and $ lines beneath it.

The parts add up to the total. They are a categorisation of money that has already been counted, not additional money moving. Add the $ lines to the T line and you report the payment twice, which is the single most common way a QIF is converted wrongly.

This is the exact opposite of the trap in an IIF file, where every transaction genuinely appears twice as a pair of counter-entries and reading only one side is correct. Two formats, two rules, and swapping them breaks both.

How QIF dates work

Quicken writes dates in a dialect nothing else uses, and it accounts for most of the confusion around the format. Two habits in particular:

• An apostrophe introduces a year in the 2000s. 12/31'05 is the last day of 2005. A slash with a two-digit year, as in 12/31/99, is the older style.
• Fields are padded to a fixed width with spaces. The fifth of January can appear as 1/ 5'26, spaces and all, which trips any reader that assumes the date has no whitespace in it.
• Day and month order is not stated anywhere. 05/01/2026 is 5 January to a file written in the UK and 1 May to one written in the US, and nothing in the file says which.

That last point is worth dwelling on, because it fails quietly. A file full of dates where the first number is 12 or less will parse under either reading. It then produces a statement that is entirely wrong about when things happened, without a single error being raised.

QIF, QFX, QBO and OFX are not the same thing

The names look like variants of one another and the formats are not related. QIF stands alone; the other three are the same underlying document with different extensions.

So a .qfx and a .qbo are near-identical files with different names on the end, and a .qif shares nothing with either beyond describing transactions. If a program asks for one specifically, the extension is not something to rename your way out of. Read more about what a QBO file is or the OFX family on their converter pages.

How to open a QIF file

Any text editor will show you the contents: Notepad, TextEdit, VS Code, anything at all. There is nothing proprietary about the bytes, and reading one is the quickest way to check that a file holds what you expect before doing anything else with it.

What does not work is renaming it to .csv and opening it in a spreadsheet. A QIF is one field per line rather than one transaction per line, so a spreadsheet gives you a single tall column with every transaction spread down it. It is not a table and cannot be coerced into one by renaming.

To get a QIF into a spreadsheet, or into a program that wants a different format, it has to be converted. That means reading the codes, grouping the lines between carets, and handling the splits and the date dialect described above.

What a QIF cannot tell you

Knowing the format's limits is most of knowing when to use it. A QIF carries no closing balance, so nothing in the file can confirm that the transactions in it are all of them. If a page of a statement was missed on the way in, the file is perfectly valid and simply shorter.

It names no institution, which is a privacy advantage and an interoperability problem at once: nothing identifies the bank or the account, and nothing can. And it gives no transaction a unique identifier, so a program reading the same QIF twice has no way to recognise that it has seen those transactions before.

None of this makes the format useless. It makes it a transport format for transactions and nothing more, which is exactly what it was designed as, and why almost every accounting program can still produce one.

Frequently asked questions

Can I open a QIF file in Excel? You can open it as text, but it will not be a table. A QIF puts one field on each line rather than one transaction on each line, so a spreadsheet shows a single tall column with every transaction stretched down it. Renaming the file to .csv does not change that. The shape of the data is the problem, not the extension.

Is a QIF the same as a QFX? No, and they are not variants of one another. A QIF is a plain line-based list with no balance and no institution named. A QFX is an OFX document, tagged and structured, that states a closing balance and carries an Intuit identifier naming the bank. They share a vendor and very little else.

Why does my QIF have far more lines than transactions? Because each transaction occupies several lines, one per field, plus a caret to close it. A four-field transaction is five lines. If a transaction is split across categories it will have more lines again, for the parts. Those parts add up to the total the entry has already stated, rather than adding to it.

Does a QIF file contain my account number? No. There is no field for one. A QIF holds dates, amounts, payees, memos, reference numbers and categories, and nothing identifying the account or the institution. An !Account block, where present, carries a name you chose and a type, not a number.

Why do the dates in my QIF look like 12/31'05? That is Quicken's shorthand for a year in the 2000s: an apostrophe where you would expect a slash. It also pads fields out to a fixed width, so the fifth of January can appear as 1/ 5'26. Both are valid QIF and both trip readers that expect an ordinary date.