To import a PDF bank statement into Quicken, first turn the PDF into a QFX file, because Quicken won't read the PDF. Then use Quicken's Web Connect import to bring the QFX into the matching account. Finish by comparing Quicken's balance on the statement's last day with the ending balance printed on the PDF.
Why Quicken turns away a PDF bank statement
Quicken turns away a PDF bank statement because a PDF is a printed page, not a data file. It shows text in positions on a page, with no tags saying which number is an amount and which is a date. Quicken's article on importing data into Quicken for Windows says plainly that Quicken can't import PDF files.
The same article lists other files Quicken for Windows refuses: Excel workbooks, QuickBooks files and OFX files. That last one surprises people, since QFX is built on the OFX standard. The difference is that a QFX carries extra details Quicken checks before it accepts the download. For the long version of that story, see whether Quicken will import an OFX file.
A PDF statement can still be the starting point. Every line you need is printed on it: dates, descriptions, amounts and a running balance on most layouts. The job is to move those values into a file Quicken understands, without retyping and without dropping a line.
Some PDF statements are harder than others. A statement downloaded from the bank's website usually holds real text that software can read. A scanned or photographed statement is a picture of text, and every digit has to be recognized first. Expect more checking with a scan.
Which file should a PDF statement become for Quicken?
A PDF statement should become a QFX file for Quicken. On Windows, QFX is the format Quicken imports through Web Connect for checking, savings and credit card accounts. QIF, the older text format, is often blocked for those account types, and Quicken's CSV import works but skips duplicate checks.
Here is how the options compare for a checking account:
| Target file | Will Quicken for Windows take it for checking? | Notes |
|---|---|---|
| QFX | Yes, through Web Connect | The normal route for bank lines |
| QIF | Often not | Quicken's import article says QIF isn't available for checking, savings or credit card accounts, though another Quicken article says newer releases allow it |
| OFX | No | Listed among the files Quicken can't import |
| CSV | Yes, with limits | A fixed ten-column layout, no duplicate matching and no transfers; see importing CSV into Quicken |
| No | The starting point, not the import file |
One warning applies to every converted QFX. Quicken's Web Connect troubleshooting page says Quicken does not support QFX files made by third-party conversion software, such as PDF-to-QFX tools, and cannot help if one fails to open. Many import anyway, but test one statement first, and keep the CSV route in reserve.
The QIF row catches people who read older advice. QIF used to be the standard way into Quicken, and many converters still offer it. If your target is an asset or liability account, QIF may still apply, and the guide to the limits of importing a QIF file into Quicken sorts out which accounts accept it.
Quicken for Mac works differently in places. Its import menus and messages are not the same as the Windows ones, so follow the walk-through for importing a QFX into Quicken for Mac if you are on a Mac.
What a PDF to QFX conversion has to write into the file
A PDF to QFX conversion has to write each statement line as a tagged transaction, add a unique ID to every line, and wrap the lot in a header naming the bank and account. If any of those parts is wrong, Quicken either refuses the file or files the lines in the wrong place.
The parts a converter must get right:
- Dates in one format. PDFs mix styles such as "Mar 4" and "03/04". QFX wants a single compact date for every line, and the year has to be right for statements that cross New Year.
- Signed amounts. Many statements print withdrawals and deposits in separate columns. The QFX needs one amount per line, with money going out shown as a negative number.
- A unique ID per line. The OFX 2.2 specification says each FITID must be unique within the account and exists so software can detect duplicate downloads. A converter should make IDs that stay the same if you convert the same statement twice.
- The bank and account header. The file names the account type and an account number, and a QFX also carries an Intuit bank ID.
- The ending balance. The file's closing balance should match the last printed balance on the statement.
The header is where QFX and QBO differ most. Both formats share the OFX base, and the transaction lines look nearly the same. The explainer on what QBO files are and how QuickBooks reads them shows the shared layout, which helps if you ever open a QFX in a text editor to see why it failed.
A quick sanity check after conversion takes one minute. Open the QFX in a text editor. Count the transaction blocks and compare the count with the statement. Scan the first and last dates. If both look right, import.
Importing the converted QFX into the matching Quicken account
Importing the converted QFX into Quicken for Windows runs through File, then File Import, then Web Connect File. Choose the file, then either name a new account or choose Link to attach the lines to an account you already keep. Linking to the right existing account is the step that decides where every transaction lands.
The steps, based on Quicken's import article:
- Back up your Quicken data file. A backup turns a bad import into a five-minute restore.
- In Quicken for Windows, open the File menu and choose File Import, then Web Connect File.
- Select the converted QFX and click OK.
- When Quicken asks where the transactions go, choose Link and pick the existing account that matches the statement. Create a new account only if you have never tracked this one in Quicken.
- Review the downloaded transactions Quicken shows you. Accept the ones that are new, and match any that you had already entered by hand.
- Run the balance check in the next section before you move on to the next statement.
Two habits keep this clean. Import statements in date order, oldest first, so each one starts where the last ended. And import each statement once. If you are unsure whether a month went in, check the register for its first and last lines before importing it again.
If Quicken shows an error during step 3 or step 4, the cause is usually the file's header or a mismatch with the chosen account. Fix the cause before trying again, so you don't end up with two partial imports of the same month.
Does the Quicken ending balance match the PDF statement?
The Quicken ending balance should match the PDF statement's ending balance on the statement's last day. If it does, every line went in once. If it doesn't, the gap tells you what to look for: one missing line, one doubled line, or a sign flipped between deposit and withdrawal.
A worked example
The figures below are example values for a March checking statement.
| Item | Example amount |
|---|---|
| Opening balance printed on the PDF | 4,210.55 |
| Deposits on the statement | 3,600.00 |
| Withdrawals on the statement | 2,948.17 |
| Ending balance printed on the PDF | 4,862.38 |
| Quicken balance on March 31 after import | 5,012.38 |
| Difference | 150.00 too high |
A difference of exactly 150.00 points to a single line. Search the March register for 150.00. If a 150.00 withdrawal is missing, the converter likely dropped a line, often one at the foot of a page. If a 75.00 withdrawal came in as a 75.00 deposit, the gap would be twice the amount, also 150.00, so check signs too.
When the opening balance is the problem
Sometimes every March line is right and the totals still miss. Then compare the opening figure. If Quicken's balance on the day before the statement starts differs from the opening balance printed on the PDF, the gap belongs to an earlier month. Fix that month first, then come back.
A Quicken reconcile against the statement is the formal version of this check. Do it once per statement, and the next month's import starts from a known good balance.
When typing a PDF statement into Quicken by hand is quicker
Typing a PDF statement into Quicken by hand is quicker when the statement has only a handful of lines. Five or ten transactions take minutes to enter, with no file to check and no header to fix. Conversion pays off once statements run long or arrive every month.
Manual entry also wins in a few awkward cases:
- A poor scan. If the page is blurred, tilted or covered in handwriting, the time spent fixing a conversion can exceed the time spent typing.
- A one-off old statement. A single statement from years ago, for one tax question, may not be worth setting up a process for.
- Mixed accounts on one PDF. Some banks print checking and savings on the same statement. Splitting that into two clean QFX files is fiddly, and short sections are easier to type.
Ask the bank first in every case. Many banks keep a Quicken download for recent months, and a bank-made QFX needs no conversion at all.
If your records live in QuickBooks or Xero instead of Quicken, the route changes. SimpleBankConvert is being built to turn PDF statements into CSV or QBO files for QuickBooks and Xero rather than QFX files for Quicken, and you can sign up to hear when it opens.