Map QIF Fields to QuickBooks: How QIF Tags Become Transactions
No account needed for your first conversions. We never store your bank login.
A QIF file does not use columns, so there is no Map columns screen to fight with. Quicken Interchange Format stores each transaction as a short block of tagged lines, and every line begins with a single letter that names what it holds: D for the date, T for the amount, P for the payee, M for a memo, L for the category, and N for a check or reference number. A line containing only a caret (^) marks the end of one transaction and the start of the next. Because the tags are named, a converter reads them directly and builds the transaction with no manual mapping, then hands QuickBooks a .qbo it imports as a bank feed.
Mapping CSV columns is where most failed spreadsheet imports start, but QIF removes that step entirely. The tags tell the converter exactly which value is the date and which is the amount, so you cannot point the wrong column at the Amount field or read a reference number as a payee. What still matters with QIF is that the tags themselves are clean: a well-formed date after D, a signed number after T with no currency symbol, and a caret on its own line between records. Get the tags right and every transaction lands in the right place.
| QIF tag | QuickBooks field | What it holds | Common mistake |
|---|---|---|---|
| D | Date | Transaction date, e.g. D01/04/2026 | DD/MM order or Quicken's apostrophe year (01/04'26) read wrong |
| T | Amount | Signed amount, e.g. T-125.40 | Currency symbols or commas left in the number |
| P | Description / Payee | Payee name, e.g. PCostco Wholesale | Putting a reference number here instead of the N tag |
| M | Memo | Extra note kept as the bank memo | Stuffing the payee into the memo and leaving P blank |
| L | Category | Quicken category, e.g. LGroceries | Expecting it to map to a QuickBooks chart account automatically |
| N | Check / Ref number | Check or reference, e.g. N1024 | Leaving the check number inside the payee text |
How does a QIF file store a transaction?
Each transaction is a set of tagged lines, one tag per line, ended by a caret on its own line. A single record might read D01/04/2026, then T-125.40, then PCostco Wholesale, then MCard purchase, then LGroceries, then N0512, then a line with just ^. The header line at the top of the file, such as !Type:Bank, tells the reader what kind of account these records belong to. There are no column headers and no fixed order beyond the leading tag on each line.
Do I have to map fields when I import a QIF?
No. Because QIF tags are named, the converter already knows the D line is the date, the T line is the amount, and the P line is the payee. There is no Map columns screen the way a CSV upload has, and no chance of pointing the wrong column at the wrong field. The converter reads the tags, builds each transaction, and writes a .qbo that QuickBooks imports straight into the bank feed.
Which QIF tags does the converter use?
The ones that carry transaction data: D for the date, T for the amount, P for the payee, M for the memo, L for the category, and N for the check or reference number. Split-transaction tags (S, E, and a $ sub-amount) are read when present so a split keeps its detail. Anything the QuickBooks bank feed does not need is read and set aside rather than forced into a field where it does not belong.
What is the difference between the T tag and a CSV Amount column?
The T tag is the amount, full stop, and its sign already says whether money went in or out: T-125.40 is a withdrawal and T250.00 is a deposit. A CSV might split that across Credit and Debit columns and force you to map both, which is where sign flips creep in. QIF carries a single signed amount per record, so the converter never has to guess which column means money out.
Why are my QIF amounts importing as zero or as text?
Usually the T line still has a currency symbol, a thousands comma, or parentheses around a negative, so the number does not parse cleanly. Write the amount after T as a plain signed decimal: T-1234.56, not T($1,234.56). Confirm each transaction has exactly one T line, and that the caret separators are in place so two records did not merge into one with two amounts.
How do QIF categories map to my QuickBooks chart of accounts?
They do not map automatically. The L tag holds a Quicken category name, which is not the same thing as a QuickBooks chart-of-accounts entry. The transactions still import correctly with their dates, payees, and amounts, but you categorize them inside QuickBooks during review, the same as any bank feed item. Treat the L value as a hint to speed up categorization, not as a posting account.
Can I map QIF fields in QuickBooks Desktop?
There is nothing to map. QuickBooks Desktop imports bank activity through a .qbo Web Connect file, and a .qbo carries each field already labeled, so Desktop reads the date, payee, and amount with no mapping screen at all. Convert your QIF to .qbo first, then import it under File, Utilities, Import, Web Connect Files. The whole point of the .qbo route is that the fields arrive pre-identified.
What date format should the D tag use?
For US QuickBooks accounts, write the D line as MM/DD/YYYY, for example D01/04/2026 for January 4. Quicken sometimes writes a two-digit year with an apostrophe, like D1/4'26, and the day-month order can be ambiguous when the day is 12 or lower. A good converter normalizes the D tag to an unambiguous date before it builds the .qbo, which removes the guesswork covered in the QuickBooks QIF import date format guide.
Do I have to delete extra QIF tags?
No. Tags the bank feed does not need, like the L category line or an A address line, are simply read and set aside, so they will not break the import. It is still worth confirming each record ends with a caret on its own line, since a missing ^ is the usual reason two transactions run together and one set of tags overwrites the other.
How do I avoid touching the tags at all?
Convert the QIF to a .qbo file instead. The converter reads the D, T, P, M, L, and N tags automatically, with no template to match and no mapping screen, then gives you a .qbo that QuickBooks imports as a bank feed. Use the converter at the top of this page, then import the downloaded file.
Can one QIF hold both deposits and withdrawals?
Yes, and it handles them with a single tag. Each transaction's T line carries a signed amount, so a deposit is positive and a withdrawal is negative within the same file. There are no separate money-in and money-out tags to keep straight, which is exactly why QIF avoids the column-swap mistakes that flip signs on a CSV import.
Once your tags are clean, send them to the right destination: the QIF to QuickBooks Online guide walks through the upload and bank-feed match, QIF to QuickBooks Desktop covers the .qbo Web Connect route, and the QIF to QBO converter handles the conversion itself. If the amounts came in backwards, the credit card QIF to QuickBooks page explains the sign flip, and the QuickBooks QIF import date format guide fixes date errors. You can also convert your QIF to QBO right here.
This guide assumes your transactions already sit in a QIF. If they are stuck in a PDF, export the PDF bank statement to a clean Excel or CSV file first, then reshape it into QIF so the tags line up. For vendor paperwork, you can convert any PDF table into an Excel spreadsheet or pull invoice data into Excel and CSV with the date, description, and amount fields already separated, which makes building a clean QIF far quicker.