How to Import Transactions into Quicken from a CSV File

TL;DR: Current versions of Quicken for Windows and Mac do not import a plain CSV of bank transactions. Quicken reads QFX (Web Connect), and Quicken for Windows also reads QIF for certain account types. To get a CSV into Quicken, convert it to QFX first: make sure your spreadsheet has a date column, a description or payee column, and an amount column, convert it, then open the resulting QFX in Quicken and assign it to the right account.

Can Quicken import a CSV file?

Not for bank transactions. Quicken's import formats are QFX, QIF for limited account types in the Windows version, and its own transfer files. A CSV of dated transactions has no account identifier, no format marker, and no field definitions, so Quicken has nothing to map it against. The workaround everyone ends up using is converting the CSV to QFX, the same format a Web Connect download produces.

There is one narrow exception worth knowing. Quicken can import certain CSV data that is not bank activity, such as security price history in some versions. That is a different feature from importing a register full of transactions, and it does not help if what you have is a bank export.

What columns does your CSV need?

Three at minimum: a date, a description or payee, and an amount. Everything else is optional. If your bank splits debits and credits into two columns rather than using one signed amount column, that works too as long as both are mapped. A running balance column is useful for checking the result but is not required for the import itself.

How to import CSV transactions into Quicken, step by step

1. Clean the spreadsheet. Delete header banners, subtotal rows, and any blank rows the bank export added. You want one row per transaction and a single header row at the top.
2. Check the amount sign. Debits should be negative. If your export shows every amount as a positive number with a separate type column, note that so you can map it correctly.
3. Convert the CSV to QFX. Upload the file to the CSV to QFX converter, confirm which columns hold the date, description, and amount, and download the QFX.
4. Open the QFX in Quicken. Use File, then Import, then Bank or Web Connect File, and pick the account the transactions belong to. Choosing the wrong account here is the mistake that costs the most time to undo.
5. Review before accepting. Quicken stages the imported transactions for review. Scan the dates and amounts, then accept them into the register.
6. Reconcile. Compare the ending balance in Quicken to the ending balance on your statement. If they match, the import was complete.

Why will Quicken not import my CSV directly?

Because a CSV carries no structure Quicken can trust. A QFX file states which financial institution it came from, which account it belongs to, what the statement period is, and what type each transaction is. A CSV is just text separated by commas, with no agreed meaning for any column, so Quicken has no safe way to decide what belongs where.

Older versions of Quicken accepted QIF imports much more freely, which is why long time users remember importing text files without trouble. Intuit and later Quicken Inc. tightened that over the years, partly to reduce corrupted data and partly to push users toward bank connections. QFX conversion is the modern equivalent of what QIF used to do.

Can I import an Excel file into Quicken?

Not directly, and the fix is the same as for CSV. Save or export the workbook as a CSV, or upload the .xlsx straight to a converter that reads it, then produce a QFX. Quicken never reads .xlsx natively in any version, so the workbook always has to become an account file first.

If your data starts as a PDF statement rather than a spreadsheet, skip the middle step entirely. The PDF to QFX converter reads the statement and produces the Quicken file in one pass, which avoids the transcription errors that creep in when you copy a PDF into Excel by hand. If you would rather keep a spreadsheet copy of the statement for your own records, converting the PDF statement into a clean workbook first is a reasonable way to do both.

How do I avoid duplicate transactions?

Import one date range at a time and know the last date already in the register. Quicken matches imported entries against existing ones by date, amount, and check number, and it is good but not perfect, especially when the payee text differs between a bank download and a converted file. Overlapping ranges are what create the duplicates.

Two extra habits help. Sort the register by date after each import and scan the overlap week rather than assuming the matching worked. And if you are backfilling a long history into an account that also has an active download connection, do the backfill first, then reconcile, then let the connection resume. Reversing that order is how a clean register turns messy.

What if the import fails or the amounts are wrong?

Almost every failed import comes down to one of four things: a date format Quicken cannot parse, unsigned amounts so everything imports as a deposit, a missing account identifier in the file, or stray non transaction rows the converter read as data. Work through them in that order and the second attempt usually succeeds.

Signs are the most common and the most damaging, because the file imports without any error and the balance is simply wrong. Check a handful of known debits in the Quicken register after importing. If a grocery purchase increased your balance, the sign mapping was inverted and you should reconvert rather than fix the register by hand. Our guide to fixing OFX import errors in Quicken covers the error codes in more detail.

Should you use QFX or QIF?

Use QFX. It works in both Quicken for Windows and Quicken for Mac, it carries account and institution details, and it is the format the bank download path uses, so Quicken's matching and review flow treat it as a first class import. QIF is only accepted for certain account types in the Windows version and is best kept for legacy situations where nothing else works.

If your destination is not Quicken at all, the choice changes. Plain OFX is the better output for MS Money, GnuCash, Moneydance, and most accounting software, and the CSV to OFX converter produces it from the same spreadsheet. Going the other direction, when you need Quicken data back out in a spreadsheet, the QFX to CSV converter handles it.

A note on how far back to go

Bank downloads typically reach back only 30 to 90 days, so a CSV or PDF is the only way to load a year or more of history. That is worth doing once, properly, rather than in monthly pieces: pull the full range from your bank's statement archive, convert it in one batch, import it, and reconcile against the final statement. A single reconciled import beats twelve partial ones you have to check individually.

Last updated July 2026.