QIF Format

PDF to QIF ConverterWhat your bank dropped, Quicken still accepts

For two decades, Quicken users opened a download from their bank and the file slid into the register. Then the QIF link disappeared from most online banking portals — replaced by Web Connect, replaced by CSV, replaced by nothing at all. We rebuild that link in your browser. Drop a statement PDF and head back to Quicken with a .qif that imports the way QIF always has.

Why Use Our PDF to QIF Converter Tool?

Every transaction, exactly as it appeared

Posted, pending, FX duplicates, fees, interest, reversals — every line of the statement appears in the QIF, with the same description text and amounts your bank printed.

Date format you tell us, not the one your computer guesses

Pick MM/DD/YYYY (US) or DD/MM/YYYY (UK / AU / EU) before download. Quicken's biggest QIF import failure mode — locale mismatch — is just gone.

Joint and multi-account statements stay separated

Family checking + savings + a credit card on one PDF? You get one QIF with proper !Account blocks, ready to be mapped to three Quicken ledgers at import time.

Three steps from PDF to QIF

1

Pull the statement from your bank

Most banks still publish PDF statements even after dropping QIF. Download yours — or use a phone photo / scan if it's a paper statement. Password-protected PDFs work; multi-page statements get stitched.

2

Upload the PDF

Drop the PDF onto the area above, or click to browse. Accepts PDF, PNG, JPG, JPEG up to 10MB.

3

Choose your locale, then download

MM/DD/YYYY for US Quicken installs, DD/MM/YYYY for UK/AU/EU. Click Download to save the .qif. In Quicken: File → Import → QIF, then map each account.

How banks dropped QIF for Quicken

Banks phased out QIF to push you onto Web Connect

Major US banks dropped QIF export to nudge users into the QFX/QBO ecosystem Intuit licenses. Quicken still imports QIF perfectly — only the supply got cut.

Quicken can't parse PDFs at all

PDF is a print format. Quicken needs structured fields. Hand-keying a 60-line statement defeats the entire reason you bought Quicken in the first place.

Locale-mismatched dates corrupt your reconciliation silently

A US-formatted QIF imported into UK Quicken parses 03/04/2026 as April 3, not March 4. The transactions land — just on the wrong days. Reconciliation never matches.

Multi-account statements get flattened by most converters

Joint statements and small-business multi-account exports come back from cheaper converters as one undifferentiated stream. You then sort by hand inside Quicken.

Who uses PDF to QIF for Quicken

Quicken Loyalists Locked Out by Their Bank

You've been on Quicken since the dial-up era. Your bank quietly dropped the QIF download last upgrade. This puts the workflow back exactly where it was.

GnuCash Users Importing From PDFs

GnuCash imports QIF natively but won't touch a PDF. Bridge the gap without paying for a converter subscription.

Moneydance, Banktivity, AceMoney

Personal-finance apps outside Quicken still rely on QIF as their primary import format. Same workflow, same output, no app-specific tools needed.

Tax-Time Backfills

A January with twelve missing months of statements doesn't have to mean retyping. Convert each PDF to QIF, import in sequence.

Closing Out a Fintech Account

When a fintech only ships PDFs and you're about to lose access, a QIF gives you a permanent ledger entry inside Quicken before the door closes.

Bookkeepers With Quicken Clients

Different banks per client, all sending PDFs. Standardize on QIF imports, drop the per-bank guesswork.

Frequently Asked Questions — PDF to QIF Converter

QWill Quicken actually accept the QIF without errors?

Yes. The output is standards-conformant: !Type:Bank or !Type:CCard header, T fields with signed amounts, dates in your chosen locale. The locale toggle eliminates the most common QIF import failure.

QDoes this work outside Quicken — GnuCash, Moneydance, AceMoney?

Yes. The QIF spec hasn't changed since the 1990s. Every QIF-importing application from that era forward — including GnuCash, Moneydance, AceMoney, Banktivity — accepts this output.

QMy statement has checking and savings on one PDF. What happens?

Each account section is extracted separately. The QIF has one !Account block per account so Quicken prompts you to map each to a destination ledger at import time.

QAre pending transactions included or filtered out?

Included. We don't edit your data. Pending rows arrive in the QIF with [Pending] in the memo field so you can decide whether to reconcile them or wait.

QMy bank prints German / Spanish / Japanese / Hindi headers. Does that work?

Yes. The extractor reads transaction tables in any language, then normalizes dates and amounts before generating the QIF. Output is always Quicken-readable regardless of source language.

QIs my statement data stored anywhere?

The PDF is processed in memory, never written to disk, deleted immediately on response. The QIF is generated and downloaded directly to your machine. No persistent storage at any point.

QCredit card statements too?

Yes. Credit accounts get a !Type:CCard header, charges are negative, payments are positive — what Quicken expects for a credit-card register.

Other Conversion Formats

Drop your PDF, get a QIF

Two decades of QIF imports, restored. Drop your PDF, pick your locale, download a .qif file Quicken accepts on the first try. Free for the first 2 pages.