Convert QIF to CSV in seconds. Turn any Quicken .qif export into a clean CSV or Excel file with the dates, payees, and amounts already parsed and reconciled.
No account needed for your first conversions. We never store your bank login.
A QIF file is plain text, so you can open it in a text editor, but you cannot open it as a spreadsheet. The transactions inside are stored as tagged lines (D for date, T for amount, P for payee) rather than rows and columns, so Excel shows you one long column of tags instead of a ledger. A QIF to CSV converter reads those tags and rebuilds them as real rows: one transaction per line, with date, payee, memo, and amount in their own columns. Upload your .qif above and you get the CSV back in a few seconds, along with an Excel (.xlsx) copy and a QuickBooks-ready .qbo file from the same conversion.
Last updated July 2026. This page covers converting QIF to CSV and to Excel for analysis, cleanup, and bookkeeping handoff. If your goal is to get the transactions into QuickBooks rather than into a spreadsheet, use the QIF to QBO converter instead, which writes a Web Connect file QuickBooks imports as a bank feed.
The conversion is checked before you download it. The converter sums every transaction it parsed out of the QIF and compares that total against the file itself, so a QIF whose splits or apostrophe-style years would normally be misread does not quietly produce a CSV that is short a few hundred dollars. You see the parsed rows and the reconciled total on screen before you export anything.
Built for the QIF files Quicken and finance tools actually export, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, payee, and amount are read straight from the QIF tags, so there is nothing to map and no layout to match.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, apostrophe years, currency symbols, and split lines in a QIF are cleaned up and summed before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a .qif export from Quicken, your bank, or another finance tool. Any QIF type works.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
The exported CSV contains one row per transaction with a Date column, a Description or Payee column, and an Amount column, which is the three-column layout QuickBooks, Xero, and most accounting tools expect on import. Memo and category data from the QIF are carried through as additional columns when the source file contains them, and split transactions are summed to a single signed amount.
Upload the .qif file to the converter at the top of this page, wait a few seconds while the QIF tags are parsed, review the transactions and the reconciled total on screen, then download the CSV. There is no column mapping step and no template to configure, because the converter reads the QIF tags directly rather than guessing at a layout. Excel and QBO copies of the same data are available from the same download screen.
Not usefully. Excel will open a .qif file as plain text, but because QIF stores each field on its own tagged line rather than in columns, you get a single column of values like D01/15/2026 and T-42.19 instead of a transaction table. Rebuilding that into rows by hand means reading the tag structure yourself, which is exactly the work a QIF to CSV converter does for you.
Each line in a QIF file starts with a single-letter tag that says what the value is. The table below covers the tags that carry the transaction data a converter needs to rebuild your rows.
| QIF tag | Meaning | Example line | CSV column it becomes |
|---|---|---|---|
| D | Date of the transaction | D01/15/2026 | Date |
| T (or U) | Amount, negative for money out | T-42.19 | Amount |
| P | Payee | PShell Oil 4412 | Description / Payee |
| M | Memo | MFuel, client visit | Memo |
| L | Category or transfer account | LAuto:Fuel | Category |
| S / $ | Split category and split amount | SAuto:Fuel then $-42.19 | Summed into Amount |
| ^ | End of the transaction record | ^ | Ends the row |
QIF has no date-format declaration, so 03/04/2026 is March 4 to a US-formatted file and April 3 to a European one, and the reader has to guess. Quicken also writes two-digit years with an apostrophe, as in D01/15'26. The converter looks across every date in your file to work out which format is actually in use before it writes a single row, which is why the CSV comes out with dates that survive an import instead of dates silently shifted by nine months.
Yes. Batch upload takes a set of .qif files in one go and converts each one separately, with its own reconciliation check and its own CSV, Excel, and QBO exports. This is the normal path for catch-up bookkeeping, where a client hands over a year or more of exports at once. See the bulk QIF converter for how batch runs are priced and handled.
Go to CSV when a human needs to look at the data: reviewing a client's history, cleaning up payee names, splitting a file by date range, or handing transactions to someone who works in Excel. Go straight to QBO when the destination is QuickBooks, because a Web Connect file lands in the banking review queue as a native bank feed, keeps the signs and the transaction structure intact, and skips the three-column CSV rules QuickBooks Online enforces on manual uploads.
It should not, and this converter checks that it did not. Amounts are read from the QIF T tags exactly as written, splits are summed rather than dropped, and the total of every parsed transaction is matched against the source file before export. If the two do not agree, the converter tells you instead of handing you a clean-looking CSV with missing rows.
Upload a QIF export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
