How to import a PDF bank or credit card statement into Quicken

Can Quicken import a PDF bank statement?

No. Quicken’s Windows support article on importing data says plainly that Quicken cannot import Excel, QuickBooks, PDF or OFX files, and the Mac CSV article lists PDF among the files it can’t take either. To import a PDF bank statement into Quicken, the PDF has to become a QFX (Web Connect) file, a QIF file or a CSV in Quicken’s own column layout first, or the transactions have to be typed in.

Before converting anything, check the bank’s website. If it offers a Quicken (QFX) download covering the dates on your statement, that file is the cleanest route there is, and no PDF is involved at all.

Every route from a PDF statement to Quicken, compared

The routes differ in three ways that matter more than the file extension: which edition of Quicken accepts them, whether Quicken can recognise a transaction it already has, and whether you can pick the account the transactions land in.

Read across the duplicates column before you import a PDF statement into Quicken by any of these routes. QFX is the only route where Quicken itself protects you from importing the same transaction twice. With QIF and CSV that protection is yours to provide, which is manageable if you plan the dates first and import each file exactly once.

First choice: a QFX (Web Connect) file from your bank

Web Connect is Quicken’s name for a QFX file you download from the bank’s website yourself. Quicken’s help recommends Direct Connect or Express Web Connect where the bank supports them, and Web Connect where it doesn’t; for a PDF statement you are trying to replace, Web Connect is the one that matters, because you choose the date range.

1. 1Back up the Quicken data file. Both the Windows and Mac help pages make this the first step.
2. 2On the bank’s website, find the download or export option and choose Quicken, Web Connect or QFX as the format. Avoid “QuickBooks” (QBO) and plain “OFX” if a Quicken option exists.
3. 3Set the start and end dates to the statement period. Quicken’s Windows help advises a start date of the day of, or the day after, the last transaction already recorded in Quicken.
4. 4On Windows, open the account in Quicken, click the gear icon and choose Import transactions from Bank website, then drop in the file. This ties the import to the account you are looking at. File → File Import works too; the menu item is labelled “Web Connect (.QFX) File” on Quicken’s troubleshooting page and “Quicken Transfer Format (.QFX) File” on its import page, so look for the .QFX entry.
5. 5On a Mac, choose File → Import → Bank or Brokerage File (OFX, QFX), select the file, and pick the account on the Choose Your Accounts screen.
6. 6Review the transactions in the register, or in the downloaded transactions list if you accept them manually, before reconciling.

Convert the PDF to QFX for Quicken

When the bank’s download doesn’t reach the period, or the account is closed, converting the PDF to QFX gives you the nearest thing to a bank download: Quicken imports it through the same Web Connect path and applies the same duplicate check. It is the right route for a checking, savings or card account you want to keep using in Quicken, because the transactions arrive as bank data rather than as typed entries.

Two cautions belong up front. Quicken’s Web Connect troubleshooting page says Quicken does not support QFX files created by third-party conversion software, PDF-to-QFX included, and its support team won’t help if one fails to open. And a QFX file names its bank: Quicken checks that identifier against Intuit’s list of institutions that offer Web Connect, so a converted file only goes in if it carries your own bank’s current identifier and the bank still offers Web Connect. If your bank has left Web Connect, use QIF or CSV instead.

What a converted QFX file needs to get right, whichever tool writes it:

• The bank identifier (INTU.BID) your bank itself uses. A number borrowed from another bank misdescribes the data and can tie the account to the wrong institution.
• The account number and the account type: checking, savings or credit card. The type decides how Quicken signs and labels the transactions.
• A transaction ID (FITID) on every row that stays the same if you convert the statement again. IDs built from a timestamp change each run, and every re-import then duplicates.
• Signs from your side of the account. On a card, charges, fees and interest are negative and payments and refunds positive, even though the PDF prints purchases as positive numbers.
• Full dates. Card statements often print 03/14 with no year; the year has to come from the statement period, which matters when a statement spans December and January.
• Totals that agree with the PDF. If the converted rows don’t add up to the statement’s closing balance, a row was missed or misread, and it is far easier to catch before import than after.

If a converted or downloaded QFX file is refused, the message tells you which check failed. That diagnosis is covered step by step in our separate guide to QFX files not importing into Quicken, so it isn’t repeated here.

QIF and Quicken’s CSV layout on Windows

Neither format carries a bank identifier, so neither depends on the bank still supporting Quicken. That makes them the usual answer for a bank that has left Web Connect, for closed accounts and for old history. Neither checks for duplicates.

QIF goes in through File → File Import → QIF File, into an account you pick from the QIF Import window’s dropdown, so the account should exist before you start. Be aware that Quicken’s own pages disagree on which accounts QIF can reach: the current help article says any account type can now be imported using QIF, while the support article on importing data (updated June 2026) still says QIF isn’t available for checking, savings or credit card accounts. If your release won’t offer the account in the dropdown, use CSV.

CSV import for banking transactions is the newer route, and it still exists as of October 2026: File → File Import → Banking Transactions → From (.CSV) File. The window that opens shows the format rules and offers Create Sample File, which is the safest template to start from. The columns are fixed in count and order.

Date,Payee,FI Payee,Amount,Debit/Credit,Category,Account,Tag,Memo,Chknum
03/02/2026,Riverside Grocery,,-84.17,,Groceries,Jane Doe Checking,,,
03/05/2026,Acme Payroll,,2150.00,,Salary,Jane Doe Checking,,,
03/09/2026,Corner Fuel,,-42.50,,Auto:Fuel,Jane Doe Visa,,,
03/20/2026,Payment Thank You,,300.00,,,Jane Doe Visa,,,

Notice the card rows. The fuel charge is negative and the payment positive, because a charge lowers your net worth, which is exactly the opposite of how the PDF prints it. Quicken’s help adds two limits worth knowing: CSV import does not detect or create transfers, so a card payment from checking arrives as two unrelated transactions until you link them, and a manual account may need Update Balance (from the register’s gear icon) afterwards.

Importing on a Mac, and a note on Simplifi

Quicken Classic for Mac has fewer doors, and the labels don’t say what they do. As of October 2026 these are the options for a statement’s worth of transactions:

• QFX: File → Import → Bank or Brokerage File (OFX, QFX). This is the only Mac route that imports into an account you already have. Despite the OFX in the label, plan on a QFX carrying your bank’s identifier: Quicken’s help describes this path for Web Connect (QFX) files, and Quicken checks the bank named in the file.
• CSV: File → Import → Mint.com File (CSV). Quicken’s Mac article says any CSV in its format can be imported this way, but the import always creates a new account named after the file, and the transactions can’t be linked to an existing account. The Debit/Credit column must say “debit” or “credit” in lower case, amounts are signed with no dollar signs or commas, and investment transactions aren’t supported.
• QIF: only when starting a new data file (File → New, then the option to start from a QIF exported from another application). Quicken’s Mac article states that incremental QIF import isn’t supported.
• Manual entry, which works in any account, including ones set up for download.

In practice, a Mac user who wants a PDF’s transactions in an existing account needs a QFX file, from the bank or converted. CSV suits a closed account you are happy to keep as its own register.

Quicken Simplifi is a separate product. Its help says CSV is the only file format it supports for transaction imports, that imports only work in the web app, one account at a time, with dates as M/D/YY and a minus sign on expenses, and that each set of transactions can only be imported once. So a PDF statement reaches Simplifi as a CSV, not as a QFX.

Getting history older than the bank’s download offers

This is the most common reason anyone needs to import a PDF bank statement into Quicken. A new Quicken account pulls the bank’s first download, typically 90 days or so, and the year before that exists only as monthly statement PDFs.

1. 1Find the date of the oldest transaction Quicken downloaded. Everything you add must end the day before it.
2. 2Ask the bank’s site for a Web Connect file covering the older months first. Quicken’s support page says many banks offer older history this way, sometimes a month at a time.
3. 3For the months the bank won’t download, take the statement PDFs and convert them to QFX (Windows or Mac) or to Quicken’s CSV layout (Windows).
4. 4Import the oldest month first and work forward, one statement per import, checking each before the next.
5. 5Correct the account’s opening balance. An account set up from a download usually starts with an opening balance as of the day downloads began, so earlier transactions would otherwise be counted on top of it. Change it to the opening balance printed on the oldest statement you imported, dated that statement’s start date.

That last step is the one people miss, and it is why a history import can look complete while the account balance is wrong by thousands. Once the opening balance is the oldest statement’s opening balance, the register should agree with every closing balance after it.

Matching the right account and avoiding duplicates

A clean file in the wrong register is worse than no import, because it changes two balances. Each route decides the account differently:

Duplicates come from overlap: the same dates arriving twice, from a second import or from the bank’s live download. Quicken recognises a QFX transaction it already has by its FITID, but nothing recognises a repeated QIF or CSV row, and Quicken’s Windows CSV help says outright that reimporting the same file will create duplicates. The habits that prevent it:

• Back up before every import, so a mistake is a restore rather than an afternoon of deleting rows.
• Pick a cut-over date. Files cover only the dates before the first downloaded transaction; the bank’s connection covers everything after it. Quicken’s Mac help gives the same advice: don’t duplicate dates that already exist in the account.
• One statement per import, and keep a short note of which statements are in. It turns “did I already import March?” into a lookup.
• If a QFX does duplicate, convert the same statement twice and compare the FITIDs. If they differ, the converter is the cause, and every future re-import will duplicate too.
• Where duplicates do appear, delete one of each. Quicken’s Windows help says exactly that, and a restore from the backup is quicker when there are many.

Checking the balance after you import a PDF bank statement into Quicken

An import that finished without an error has only proved the file was readable. Reconciling against the statement proves the transactions are complete. Do it per statement, straight after each import.

1. 1Open the account, click the gear (Account Actions) icon and choose Reconcile. If offered a choice, pick Paper Statement, because you are reconciling to the PDF, not the bank’s online balance.
2. 2Compare the opening balance Quicken shows with the statement’s opening balance, and enter the statement’s ending balance and date.
3. 3Add any service charge or interest the statement shows that isn’t already in the register.
4. 4Check off each transaction that appears on the statement.
5. 5Click Done when the difference in the lower-right corner is zero.

A quick arithmetic check first saves time. Say Jane Doe’s March statement shows an opening balance of $1,240.55, deposits of $2,150.00 and withdrawals of $1,318.42, for a closing balance of $2,072.13. If the imported March transactions don’t net to plus $831.58, the difference is a missing, doubled or reversed row, and its size usually points at it: a difference of exactly twice one amount is a sign flipped the wrong way.

When manual entry is the better answer

For a statement with a dozen transactions, typing them into the register is often quicker than any conversion, and it has no format to get wrong. Quicken’s Mac help notes you can enter transactions manually even in accounts set up for download, and on both platforms Quicken’s help describes matching a manually entered transaction to the downloaded one when it arrives, so it isn’t added twice.

• Type them in: one or two short statements, a cash account, or a single missing month.
• Bank’s QFX: any period the bank still lets you download, on either platform.
• Converted QFX: longer history for an account you keep using, especially on a Mac.
• CSV or QIF on Windows: banks that have left Web Connect, closed accounts, and bulk history you are importing once.

Whichever route you take, the finish is the same: the right account, each date imported once, and a reconciled balance that matches the closing balance on the PDF.