Import Bank Statements into Quicken: Files, Steps, Fixes

TL;DR Quicken imports transaction files, not PDFs. Depending on your edition and version, it can import Web Connect files (QFX) from your bank, QIF files in certain situations, and CSV files in newer versions. If you only have PDF statements, convert them to a transaction file first and check that the transactions add up to the statement's closing balance. Import one statement period at a time into the right account, watch for duplicates with any connected download, and reconcile against the statement afterwards.

Quicken has been around for a long time, and many people have years of history in it. That history is valuable, and keeping it complete is the reason people end up importing statements: a bank connection stopped working, an account was never connected, you're adding an older account, or you're filling in months before you started using Quicken.

Importing into Quicken is a little different from importing into small-business accounting software like QuickBooks or Xero. File format support depends on your edition (Windows or Mac) and version, and has changed over the years. This guide explains the general options and a reliable process, without claiming exact menu paths that may not match your screen. Check Quicken's own support pages for the specifics of your version.

Which file types Quicken works with

There are three file types you'll come across.

QFX (Web Connect)

QFX is Quicken's version of the OFX standard, and the format banks use when they offer a "Download to Quicken" or Web Connect option. A QFX file contains transactions with dates, amounts, payees and unique transaction IDs, plus information identifying the bank and account. Quicken reads it and matches it to an account.

QFX is usually the smoothest import. The unique IDs help Quicken avoid importing the same transaction twice. If your bank offers a QFX download for the dates you need, start there.

QIF

QIF is an older, plain-text format that Quicken has supported for decades. Over time, Quicken has restricted which account types and situations allow QIF imports, and the behaviour differs between Windows and Mac. It remains useful for moving data between Quicken files and for some account types. If you want to use QIF for bank transactions, check Quicken's current help for whether your version allows it for the account you're importing into.

CSV

CSV is the format most banks offer and most converters produce. Newer versions of Quicken have added CSV import, with column mapping, in at least some editions. If your version supports it, CSV is the most flexible choice because you can open and check the file in Excel before importing. If it doesn't, you'll need QFX or QIF.

Summary

Preparing a file from PDF statements

Banks often only keep transaction downloads for a limited period, while PDF statements go back further. For older months, PDFs may be all you have.

Converting them is a two-step job: extract the transactions, then shape them into a file Quicken accepts.

1. Extract. SheetStatement's PDF bank statement converter reads the statement, outputs one row per transaction with a real date and a signed amount, and checks the total against the statement's opening and closing balances. Download CSV or Excel.
2. Check. Opening balance plus the sum of transactions should equal the closing balance. The converter shows this; you can also use the balance checker.
3. Shape the file. For a CSV import, keep the columns Quicken's import screen will ask for: date, payee or description, and amount (or separate inflow and outflow columns). For a QFX or QIF import, use a tool or converter that produces those formats, and test it on a small file first.

The free plan covers 3 pages a month, which is enough to test the whole process on one statement before converting a backlog. Paid plans are $9, $19 or $39 a month.

A clean CSV

If your version imports CSV, a simple, consistent file reduces mapping problems:

Date,Payee,Amount,Memo
2026-02-02,GROCERY MARKET,-74.18,
2026-02-03,PAYROLL EMPLOYER,2210.00,
2026-02-05,ELECTRIC UTILITY,-96.40,Feb bill

Rules that help:

• One header row and nothing above it.
• One date format throughout. ISO dates (2026-02-02) avoid month and day confusion.
• Plain numbers with a minus sign for money out. No currency symbols or thousands separators.
• Save as CSV UTF-8.

Our bank statement CSV format explainer covers these rules in more detail.

Importing into Quicken: the general process

The exact steps depend on your version, but the shape of the process is the same.

1. Back up your Quicken file. Before any import, make a backup. If the import goes wrong, restoring is far quicker than cleaning up.
2. Confirm the account. Make sure the account you're importing into exists in Quicken and is the right type (checking, savings, credit card).
3. Start the import. Look for an import option in the File menu, and choose the file type you have.
4. Choose or link the account. Quicken asks which account the transactions belong to. For QFX files, it may try to match the account automatically based on the file's bank information; if it offers to create a new account, check carefully that you're not creating a duplicate of an existing one.
5. Map columns (CSV). If importing CSV, match the file's columns to Quicken's fields and confirm the date format.
6. Review downloaded transactions. Quicken usually places imported transactions in a review area, where you can accept them, match them to existing entries, or edit payees and categories.
7. Accept. Once you're satisfied, accept the transactions into the register.

Import one statement period at a time. It keeps each batch small enough to review and makes reconciliation straightforward.

Matching and avoiding duplicates

Duplicates are the most common problem after an import. They happen when:

• The account is also connected to automatic downloads, and the file covers dates the connection already downloaded.
• You entered transactions manually and then imported the same ones.
• The same file is imported twice, or two files overlap.

How to avoid them:

1. Know your cutoffs. If the account has automatic downloads, find the earliest downloaded transaction and only import dates before it.
2. Use matching. When Quicken shows imported transactions in review, it often suggests matching them to existing manual entries. Accept a match only when the date, amount and payee all agree.
3. Trim files to statement periods. Don't import downloads that overlap; trim each file so every transaction belongs to exactly one import.
4. Keep a note. In the account's notes or a separate document, record which periods were imported from files and which came from downloads.

If duplicates do appear, delete the extra copies, keeping the version that's matched, categorized or cleared. Always compare against the statement: two identical transactions on the same day can be legitimate.

Categorizing after import

Imported transactions often need categories. Quicken has category rules (sometimes called renaming rules or memorized payees, depending on version) that apply categories and clean payee names automatically for future imports.

A sensible approach:

1. Set up rules for recurring payees after the first import. Next month, they're categorized automatically.
2. Tag transfers. Payments to a credit card and moves between your own accounts should be recorded as transfers to the other account, not as spending.
3. Review the uncategorized ones. Use a placeholder category for anything you need to check.

If you prefer, categorize in a spreadsheet first, then use the spreadsheet as a guide while working in Quicken. Our guide to Excel formulas for categorizing bank transactions shows how.

Reconciling

After importing a statement period, reconcile the account in Quicken against the statement:

1. Start reconciliation for the account.
2. Enter the statement's ending date and ending balance (and, if asked, the opening balance).
3. Mark the transactions that appear on the statement.
4. Confirm the difference is zero.

If it isn't, look for:

• Missing transactions (an incomplete file or an import that skipped rows).
• Duplicates (overlap with downloads or a manual entry).
• Signs reversed (deposits recorded as payments, or the reverse).
• An opening balance that doesn't match the previous statement's closing balance.

Our guides to finding bank reconciliation discrepancies and opening balance mismatches cover each of these in detail. They're written in general terms and apply to Quicken as much as to any other software.

Credit cards

Import card statements into a credit card account. Card files are where sign confusion is most common: purchases should increase the balance owed, and payments reduce it. After importing, check a known purchase and a known payment. If they're reversed, delete the import (or restore your backup), flip the signs in the file and import again. The credit card statement converter keeps a consistent convention across card statements, which saves fixing each file.

Record the monthly card payment as a transfer between your checking and card accounts, not as an expense, so it isn't counted twice.

Filling in history before a start date

If you want to add months before you started using Quicken:

1. Check the account's opening balance in Quicken. It should match the balance on the statement just before the earliest month you're adding.
2. Import oldest first, one statement at a time.
3. Reconcile each month before moving on.
4. Adjust the opening balance if needed so the history connects. Be careful: changing an opening balance affects every later balance, so do it once, deliberately, and back up first.

A worked example

A retired couple have used Quicken for years. Their credit union's download stopped working for four months, and they want those months in Quicken before their tax preparer's appointment.

1. Back up. They back up the Quicken file.
2. Check the cutoff. The last downloaded transaction is on May 31; downloads resumed on October 1. They need June to September.
3. Get the statements. The credit union's online banking only offers transaction downloads for the last 90 days, so they download the June to September PDF statements.
4. Convert and check. Each statement converts to CSV, and each passes the balance check.
5. Import. Their version of Quicken supports CSV import. They import June, map date, payee and amount, and review: forty-two transactions, all as expected. They accept.
6. Reconcile June. Zero difference.
7. Repeat for July, August and September. In August, Quicken suggests matching two transactions to manual entries they had typed in when the download broke. Both match exactly and they accept the matches instead of creating duplicates.
8. Check the join. The September 30 balance in Quicken matches the September statement, and October's downloaded transactions follow on with no gap.

Their tax preparer gets reports for the full year from Quicken, with every month reconciled.

Troubleshooting

Quicken won't accept the file. Check the file type is one your version supports for that account type. For CSV, look for extra header rows, totals at the bottom, or inconsistent date formats.

QFX file is rejected or goes to the wrong account. QFX files carry bank identification. Files produced outside the bank may not match what Quicken expects. Check Quicken's support for your version, or use CSV if supported.

All transactions show as deposits (or payments). A sign or column mapping problem. Money out must be negative in a single amount column, or mapped to the outflow column.

Dates are wrong. The date format in the file doesn't match what was selected during import. Use ISO dates and re-import after removing the bad batch.

Duplicates appeared. The file overlapped with downloaded or manually entered transactions. Delete the extras and set a clear cutoff for future imports.

Reconciliation is off by a fixed amount. Look for a single missing or duplicated transaction of that amount, or one with its sign flipped (which shows as double the amount).

Keeping Quicken and the bank in sync

Once the gap is filled, the goal is to avoid another one. A few habits help.

Check the download status monthly. Automatic downloads sometimes stop without much warning: a bank changes its connection, a password changes, or a security prompt needs answering. A quick look at the date of the latest downloaded transaction for each account, once a month, catches a broken connection before it becomes a four-month gap.

Reconcile every month. Reconciling against the statement is the clearest signal that the register is complete. If a month won't reconcile, the problem is fresh and easy to trace.

Save statements as they arrive. Download each month's PDF into a folder named by account and year, even if you don't plan to use it. If a download ever fails, the statements you need are already on hand, and you won't depend on how far back the bank's website goes.

Keep one method per account per period. Mixing automatic downloads and file imports for the same dates is where duplicates come from. If you switch methods, note the date you switched.

Back up regularly. Quicken files hold years of history. Keep backups in more than one place, and make an extra one before any large import or cleanup.

Our month-end close checklist is written for small businesses, but the same monthly rhythm works well for household finances in Quicken.

Moving from Quicken to other software

Some people use statement imports as a way to move from Quicken to another tool, or the reverse. The converted statement files work for most destinations: CSV for spreadsheets and many apps, QBO for QuickBooks, Xero's CSV format for Xero. If you're switching, our guide to QBO vs IIF vs CSV explains which formats suit QuickBooks.

Convert statements for Quicken

If your missing months are only available as PDFs, upload them to SheetStatement, check that each one balances, and download a clean CSV ready to import. The free plan's 3 pages a month are enough to try one statement end to end.

FAQ

Can Quicken import a PDF bank statement?

No. Quicken imports transaction files. Convert the PDF to a transaction file first, check it against the statement's balances, then import.

What file formats can Quicken import?

Typically QFX (Web Connect) files from banks, QIF in certain situations, and CSV in newer versions. Support depends on your edition and version, so check Quicken's help for yours.

How do I avoid duplicate transactions when importing into Quicken?

Only import dates not already covered by automatic downloads or manual entries, accept matches during review when date, amount and payee agree, and keep a note of import cutoffs.

Should I back up before importing?

Yes. A backup lets you undo a bad import quickly, which is much easier than deleting transactions one by one.

How do I import credit card statements into Quicken?

Import into a credit card account, check that purchases increase the balance owed and payments reduce it, and record payments from checking as transfers.

Do I need to reconcile after importing?

It's strongly recommended. Reconciling each imported period against the statement confirms nothing is missing or duplicated.