QIF is from 1984, and it shows
QIF is not a table. Every transaction is spread over several lines, one field per line, with a single letter at the start of the line saying what the field is:
!Type:Bank
D01/05/2024 the date
T-45.20 the amount
PSHELL who you paid
MGAS STATION the memo
LAuto:Fuel the category
^ end of this transaction
Open that in Excel and you get one long column of exactly what you see above. This page reads the structure and gives you one row per transaction.
The part other converters don't tell you about
QIF never says which order the day and month are in, and never says whether a dot or a comma is the decimal mark. Both have to be worked out from the data, and sometimes the data does not settle it:
-
03/04/2024is the 3rd of April in most of the world and March 4th in the United States. The only proof is finding a date somewhere in the file where one part is above 12. If every date in your file has both parts at 12 or under, no such proof exists. -
1.234is one point two three four in the US and one thousand two hundred and thirty four in most of Europe. The proof is finding an amount where the digits after the mark are not exactly three.
This converter looks at the whole file at once for that evidence, and says on screen whether each one was proven or guessed before you download anything. Both mistakes are the dangerous kind: the whole file is wrong together, and the result looks completely normal.
Excel or CSV? It depends who reads the file
An .xlsx stores each cell's type, so amounts are numbers and
dates are real Excel dates. You can total a column or build a pivot table the moment it
opens, with no trip through Data → Text to Columns assigning formats by hand.
The page shows you the column total before you download, and that is the number
=SUM() will give you.
A CSV carries no type information — the program opening it has to
guess. It often guesses right; it guesses wrong when the decimal mark does not match the
reader's regional setting, when a value ended up in quotes, or when the date order is
ambiguous, and then =SUM() returns 0 and dates sort as text with nothing saying
so. The point is not that CSV always breaks — it is that you do not control
the guess. That is a real cost when a person is going to open the file and
add things up, which is what this page is for.
It is the better format when another program has to read the file, because you can
match the column separator, decimal mark and date format it expects — and an
.xlsx gives you no such control. If something has told you what it wants,
convert to CSV instead.
What comes across
- Date, amount, payee, memo and check number. Payee and memo stay in separate columns, because QIF keeps them apart.
- Category. The
Lfield, including nested ones likeAuto:Fuel. The class after a slash is dropped, since a spreadsheet column holds one value. - Transfers. A category written as
[Savings]means money moved to another of your own accounts. Those are counted separately so you can tell them from spending. - Account name and type, when the file has an
!Accountblock.
The one thing a spreadsheet can't carry
A split transaction, where one payment is divided across several categories, has no representation in a single row. Those come out as one line for the total with the Category cell blank. The totals stay right; the breakdown does not. The page lists exactly which transactions were affected rather than letting you find out during a reconciliation.
Questions
Which programs' QIF files does this read?
Quicken, GnuCash, Moneydance, YNAB 4, AceMoney, KMyMoney and Microsoft Money exports all
use the same field letters. Investment transactions (!Type:Invst) are a
different set of fields and are skipped, with a note on screen saying how many.
Why is 2024 showing as 1924?
Quicken writes two digit years, and uses an apostrophe rather than a slash to mean the
2000s: 01/05'24 is 2024 while 01/05/24 is 1924. Converters that
treat both the same put a century of your transactions in the wrong place. This one
handles the apostrophe. If you see a wrong century anyway, send us the file.
Some transactions are missing from the download.
The page tells you when that happens and how many, rather than quietly shortening the file. A transaction is left out when it has no readable date or no readable amount. If the count surprises you, the original is worth a look.
Is my file uploaded anywhere?
No. Every converter here runs in the browser, and each page ships a Content Security Policy
with connect-src 'none', so your browser refuses to let the page make any
network request. Watch the Network tab in developer tools while you convert and it stays
empty.
Related
- IIF to Excel converter QuickBooks Desktop files
- CSV to QIF converter the other direction
- IIF to QIF converter QuickBooks into Quicken
- Excel to QBO converter spreadsheet into QuickBooks