How to convert a bank statement to QIF for Quicken (2026)

Quicken has moved most of its consumer accounts to QFX and Web Connect over the last decade, but QIF is still the format serious Quicken users reach for when a bank does not offer a direct feed. QIF is plain text, portable across every Quicken version back to the mid 1990s, and unlike QFX it does not require a bank ID or Intuit-signed feed. If you can convert your bank statement into a well-formed QIF file, you can import into Quicken Deluxe, Quicken Classic, and even Quicken for Mac without going through a live feed.

The catch is that Quicken is unforgiving about the file. A single stray character in the account header, a date in the wrong format, or a mismatched account type and the whole import silently drops rows or lands in the wrong ledger. This guide walks through what a QIF file is, the four practical ways to build one from a bank statement, the fields Quicken actually validates, and the workflow that keeps your categories intact after the import.

What a QIF file actually is

QIF (Quicken Interchange Format) is a line-oriented text format. Each transaction is a short block of lines prefixed by a single character: D for date, T for amount, P for payee, M for memo, L for category, and ^ to close the transaction. Before the first transaction, a header line declares the account type: !Type:Bank, !Type:CCard, !Type:Cash, !Type:Invst, and so on. Optionally you can prepend an !Account block that names the account so Quicken maps the transactions to the right ledger on import.

Because the format is plain text, you can open a QIF in any editor and see exactly what Quicken will read. That transparency is why accountants and long-time Quicken users prefer QIF over QFX for one-off imports: nothing is hidden, nothing is signed, and every line is inspectable.

The four real ways to get a QIF file

1. Direct QIF export from your bank

A handful of banks and credit unions still expose QIF as a download option, usually labelled “Quicken 2004 or earlier” or simply “QIF”. If you see it, use it. Most consumer banks in the US, UK, India, Australia, and UAE do not offer QIF anymore, so if the option is missing you have to build the file yourself.

2. Convert CSV to QIF with a converter

If your bank offers a CSV download, a CSV-to-QIF converter can wrap it in the right envelope. Any reliable converter has to handle four things: format each date as MM/DD'YYYY or DD/MM/YYYY to match the region Quicken is configured for, use the correct sign on T amounts (negative for outflows), pick the right !Type header for the account, and avoid duplicating transactions if you re-import overlapping periods. Skip any of these and the import either silently fails or lands rows in the wrong month.

3. Convert PDF to QIF

The hardest case. You have to extract structured transactions from an unstructured document first, then wrap them in the QIF envelope. Extraction is where generic converters fall over. Column boundaries drift, wrapped descriptions become extra rows, running-balance columns get confused with amount columns, and scanned statements need OCR before any of it can happen. The wrapping step is easy once extraction is right. Getting extraction right on a real bank PDF is the whole game.

4. Extract, categorize, then export with Karchu

The workflow we recommend splits the problem into two clean steps: parse and categorize with Karchu, then export the categorized transactions in a Quicken-friendly format. Karchu handles extraction from PDF (digital or scanned), CSV, or Excel, applies your rule-based categorization so every transaction lands in the right Quicken category, and exports a clean file ready for import. That way the transactions Quicken receives already carry the payee, memo, and category your rules assigned. The manual matching step inside Quicken shrinks to a handful of edge cases instead of every row.

The QIF fields that actually matter

If you are hand-building or reviewing a QIF file, focus on the lines Quicken validates.

!Type header. Must be the first non-blank line. !Type:Bank for checking and savings, !Type:CCard for credit cards, !Type:Cash for wallet, !Type:Invst for brokerage. The wrong header sends every transaction to the wrong ledger type.
D (date). Format depends on your Quicken region. US builds expect MM/DD'YYYY or M/D/YY. UK, India, Australia, and UAE builds expect DD/MM/YYYY. Get this wrong and Quicken either flips month and day or drops the row.
T (amount). Two-decimal precision, negative for outflows. No currency symbol, no thousands separator. Commas break the parser.
P (payee). Free text, up to about 40 characters. Longer strings are truncated silently.
M (memo). Free text. Use it for reference numbers or additional description your bank rules can match on.
L (category). Category name from your Quicken chart. If the category does not exist, Quicken creates it on import. Consistent naming keeps your reports clean.
N (check number). Only for check payments; leave off otherwise.
^ (end of transaction). A single caret on its own line closes the block. Missing carets are the number-one cause of “file not recognized” errors.

A minimal, working example

Here is what a two-transaction QIF looks like for a US checking account.

!Type:Bank
D07/22'2026
T-42.15
PWhole Foods Market
MGroceries
LGroceries
^
D07/23'2026
T2450.00
PACME Payroll
MDirect deposit
LSalary
^

That file imports cleanly into every recent Quicken build. Change the header to !Type:CCard for a credit card and flip the sign convention: on a credit card ledger, positive amounts are charges and negative amounts are payments to the card.

Why categorize before you import

Quicken will happily accept a QIF file with 300 uncategorized transactions and then leave you to open each one, pick a category, and save. That is the manual step most people were trying to escape by exporting a QIF file in the first place. Categorizing before the export means the L lines land in Quicken already populated. Doing the categorization inside Karchu, with a deterministic rule engine you can audit, means the same rules apply to next month’s statement automatically. The workflow gets faster over time instead of resetting every month.

Common QIF import errors and how to fix them

“File not recognized.” Nine times out of ten the !Type header is missing, mistyped, or a stray BOM sits at the start of the file. Save the file as UTF-8 without BOM (or ASCII) and confirm the header spelling.

Every transaction lands on the wrong date. Region mismatch between the QIF date format and Quicken’s locale. A US Quicken build reading DD/MM/YYYY will happily flip day and month for every row without warning.

Transactions imported to the wrong account. QIF does not carry a bank account number. Quicken assigns the transactions to whichever account you had selected when you clicked Import. Always select the target account first.

Duplicate transactions after import. Unlike QFX, QIF has no per-transaction unique ID. Quicken tries to match on date, amount, and payee, but if your source file changes the payee wording between imports (bank cleans up merchant names differently on newer statements) you get duplicates. Dedupe upstream: Karchu detects overlapping periods across queued files before export so no duplicates ever reach Quicken.

Signs flipped on a credit card. Credit-card QIF files use the opposite sign convention from bank QIF files. If your converter treats every account as a bank, credit-card charges land as inflows. Fix the sign convention or use the correct !Type header.

A concrete workflow for PDF statements to Quicken

Upload the PDF statement to Karchu. Digital and scanned PDFs both work; no separate OCR step is required.
Review the extracted transactions in the workspace. Karchu normalizes dates to ISO 8601 and keeps a consistent debit and credit split.
Let the rule engine categorize the transactions. Adjust or add rules to catch merchants specific to your accounts; the rules apply retroactively across every statement in the workspace.
Export the categorized transactions as CSV. Feed the CSV into any CSV-to-QIF converter, or use Karchu’s direct QIF export where available for your region.
In Quicken, open the target account, choose File > Import > QIF, select the file, and confirm the account and date range Quicken shows before accepting.

QIF vs QFX vs CSV, when to use which

QFX is the format Quicken prefers for live feeds. It carries a bank ID, an account number, and per-transaction unique IDs, so Quicken can dedupe reliably. It is also signed for Intuit-recognized banks, which is why generic tools cannot produce a QFX that Quicken accepts. If your bank offers QFX, use it and let Web Connect handle the sync.

QIF is the right choice for one-off imports from banks that do not offer a direct feed, historical imports covering years of statements, and any situation where you need to inspect the file before it hits your ledger. It works with every Quicken build.

CSV is the fallback when your converter cannot produce a valid QIF. Quicken accepts CSV via File > Import > Web Connect File in newer builds, but the column mapping is manual and categories do not carry over. If categories matter, produce a QIF.

Frequently asked

Can I convert a scanned PDF directly to QIF? Yes, but only if the tool doing the conversion runs OCR. Karchu’s pipeline handles scanned PDFs end to end. Generic PDF-to-QIF converters usually fail on scans.

Does Quicken for Mac accept QIF? Yes, though the import lives under a different menu (File > Import > QIF File). The file format is identical to the Windows build.

How do I import multiple months in one go? Concatenate the transaction blocks under a single !Type header and import as one file. Quicken deduplicates on date, amount, and payee, but see the duplicate section above for the edge cases.

Can I import investment transactions? Yes, with !Type:Invst and the investment-specific action codes (N for action, Y for security). This is a separate specification worth its own guide; for most bank-statement workflows you will only need !Type:Bank and !Type:CCard.

Bottom line

The best QIF file is the one you barely have to think about. If your bank offers a native QIF or QFX download, use it. If it does not, do not reach for a generic converter and then spend an hour categorizing inside Quicken. Do the categorization upstream where the rules are yours to keep, export a clean file, and let Quicken focus on what it is good at: being the ledger of record. Try Karchu free for 30 days and see how much of the workflow disappears when categorization stops being a monthly chore.