Convert Bank Statements for Quicken — PDF to OFX or QIF

When you'd convert rather than download

Quicken's automatic feed covers the recent past for connected accounts, but there are gaps it can't fill:

• Older history. You're setting up a new file, or rebuilding one, and need months the download won't reach.
• A closed account. The account no longer connects, but you still want its transactions on file.
• An account you never linked. A rarely used savings or business account you'd rather not wire a live connection to.

In each case you have the statement PDFs already — they're the record — and converting them is quicker than typing the register out by hand.

OFX or QIF: which to use

For Quicken, OFX is the better file. It carries a unique transaction id on every line, so if you re-import the same file by mistake, Quicken recognizes the duplicates and doesn't double them up. QIF works too and is widely supported, but it has no such id, so you have to be careful not to import the same period twice.

The converter produces both from your PDF, so you can pick whichever your version of Quicken prefers.

From PDF to a Quicken import

1. Download the statement PDF from your bank — Chase, Bank of America, Wells Fargo and the rest keep several years online.
2. Convert it, choosing OFX (or QIF). Every transaction is read into a row first — date, description, amount — and the running balance is checked so nothing is missing.
3. In Quicken, go to File → Import and select the file.
4. Review the register. The lines land against the account with their dates and amounts, ready for you to categorize.

What the converter handles that a copy-paste won't

US statements from the big banks are sectioned — deposits, electronic withdrawals, checks — with a daily ending balance rather than a balance on every line. That layout doesn't map to a register at all if you just copy the text out; deposits and withdrawals get jumbled. The converter reads each section, marks every line as money in or out, and rebuilds one clean statement in date order, so what reaches Quicken has the right sign on every transaction.

It also reconciles the math before building the file — beginning balance, plus deposits, minus withdrawals, has to reach the ending balance — so a line that dropped out of the PDF is caught before it leaves your Quicken balance off.

Avoiding duplicate transactions

The most common Quicken import headache is doubling up: importing a period the feed already covered. Two habits prevent it:

• Use OFX where you can — its per-line id lets Quicken skip anything already in the register.
• Import only the gap — convert and import the months the download didn't cover, not overlapping ones.

If a duplicate does slip in, Quicken lets you delete it from the register; OFX simply makes it far less likely.

After the import: keeping the register clean

Once the lines are in your Quicken register, categorizing works the same as any transaction — and because the conversion keeps the payee or merchant on every line, Quicken's memorized-payee rules can do much of it for you. A card charge shows the vendor, a deposit shows the source, so recurring items get categorized automatically after you set them the first time. For a rebuilt file that turns a daunting backlog into a mostly hands-off pass, leaving only the one-offs to code by hand. When you're done, run Quicken's reconcile against the statement's closing balance — because the converted file was already checked to that balance, the two should agree on the first try, which is the quickest way to know the account is complete and correct.