Quicken Import CSV: How to Import CSV Transactions Into Quicken for Windows and Mac

TL;DR: Yes, Quicken can import a CSV, but only a strictly formatted one, and the two desktop versions want different things. Quicken for Windows uses File, then File Import, then Banking Transactions, then From (.CSV) File, and expects dates as mm/dd/yyyy. Quicken for Mac imports through File, then Import, then Mint.com File (CSV), and always creates a brand new account named after the file. Neither version matches against transactions already in your register, so reimporting the same CSV duplicates every row. If your source is a bank statement rather than a spreadsheet you maintain, a QFX import is the better route, because Web Connect files do match duplicates and land in the account you choose.

Can Quicken import CSV files?

Yes. Both Quicken Classic for Windows and Quicken Classic for Mac accept a CSV, but each one requires an exact column layout and neither is forgiving about it. A spreadsheet exported from your bank will almost never import as-is, because the column names and their order have to match what Quicken expects, not what your bank chose to call things. The import is also one-directional and unmatched: Quicken adds what is in the file and does not check whether those transactions are already there.

That last point is the one that causes the most damage, and it is worth stating plainly before you try anything. Quicken's own documentation for the Windows CSV import says that CSV imports do not match existing transactions, that reimporting the same file will create duplicates, and that every transaction in the file is added to the register even if an identical transaction already exists. There is no undo that cleanly separates the imported rows from the ones that were already there.

What format does a Quicken CSV import need?

On Windows the columns must appear in this order: Date, Payee, FI Payee, Amount, Debit/Credit, Category, Account, Tag, Memo, Chknum. The first seven are required and the last three are optional, but the headers themselves all need to be present. Dates follow mm/dd/yyyy, which is the US convention, and leading zeros on single-digit months and days are optional. A positive amount increases net worth and a negative amount decreases it, so a card charge belongs in the file as a negative number.

On Mac the expected headers are Date, Amount, Account, Category, Payee, Notes, Debit/Credit and FI Payee. Date, Amount and Account must contain values; the rest can be blank but the columns still have to exist in the file. The Amount column takes signed numbers and must not contain dollar signs or thousands separators. The Debit/Credit column has to say debit or credit in lower case, because Quicken uses it to decide whether a row reads as income or expense. FI Payee is carried for backward compatibility with the old Mint CSV layout and is not imported at all.

Notice that the Windows and Mac date rules do not agree. Windows wants month first, Mac accepts day first. A file built for one and fed to the other will either fail outright or, worse, import with the day and month swapped on every transaction dated on or before the twelfth of a month. That silent version is the one that costs an afternoon to unpick, so check a handful of imported dates against the source before you trust the batch.

Why is my Quicken CSV import not working?

Almost every failed CSV import comes down to the file not matching the expected layout exactly. Quicken validates the header row and the column order before it reads any data, so a file with the right information under the wrong headings is rejected the same way an empty file would be. Work through the causes below in order, because the cheap ones account for most cases.

Is CSV or QFX better for importing bank transactions into Quicken?

For a bank or credit card statement, QFX is better in almost every respect, and it is not close. A QFX is a Web Connect file, which is the same thing Quicken receives when it downloads from your bank directly. It carries a unique identifier on every transaction, which is what lets Quicken recognize a transaction it has already seen and offer to match rather than duplicate it. It also imports into an account you select instead of manufacturing a new one. CSV has none of that machinery.

The practical rule that follows: use CSV when the spreadsheet is the original record and you are loading it once, and use QFX when the original record is a statement from a financial institution. Most people asking how to import a CSV into Quicken are in the second group. They started with a PDF statement, converted it to a spreadsheet because that felt like the obvious intermediate step, and then hit the import wall. Going from the statement straight to a QFX file Quicken imports skips the wall entirely, and the convert a bank statement to Quicken walkthrough covers the import screen by screen. If you specifically need categories and splits to survive the import, QIF is the format that carries them.

How do I import a CSV into Quicken for Mac?

Choose the File menu, then Import, then Mint.com File (CSV), and select your file. The name is a leftover from the Mint import path and does not mean the file has to come from Mint, but the column layout it expects is the old Mint one. The single most important thing to know before you click import is that Quicken for Mac always creates a new account named after the imported file. It will not merge the rows into an account you already have, no matter what the Account column says.

That behavior makes CSV a poor fit for topping up an existing Mac account with missing transactions, which is the most common reason people want it. If that is your situation, importing a QFX into the existing account is the route that actually does what you want. Investment transactions are a hard stop either way, since they cannot be imported through the Mac CSV path at all.

Can Quicken Simplifi import a CSV?

Simplifi is a separate product from Quicken Classic and handles manual imports through its own web app rather than the desktop menus described above, so the column layouts on this page do not apply to it. If you are on Simplifi, check its current import documentation rather than assuming the Classic behavior carries over, because the two products have diverged considerably and the file requirements are not the same.

Where the CSV came from usually matters more than the import

It is worth stepping back and asking why there is a CSV in the middle of this at all. If you keep a working spreadsheet of transactions, the CSV is your real record and importing it once is entirely reasonable. If the CSV is something you generated from a bank statement on the way to Quicken, it is an extra step that strips out the transaction identifiers Quicken uses to avoid duplicates, and you are paying for that convenience with manual cleanup later.

There is a third case: building the spreadsheet by hand from a pile of paperwork. If you are typing figures off receipts and supplier invoices rather than exporting from a bank, that is a different extraction problem, and pulling the line items off those documents automatically will save far more time than any choice of import format. For bank and card activity, the statement is the authoritative source and converting it directly is both faster and safer.

One more thing about gaps. People frequently reach for a CSV import because a bank feed stopped and they are trying to patch the hole by hand. A restored connection resumes from the current date rather than backfilling what it missed, so the gap does not close on its own. The Quicken not downloading transactions guide covers why feeds break and how to fill the missing period properly, and there are bank-specific walkthroughs for the accounts that fail most often, including American Express not downloading to Quicken, where the fix is a reauthorization rather than a file import at all.

Before you import anything

Back up the Quicken file first. This is not generic caution: because CSV import performs no matching, a mistaken import is genuinely hard to reverse by hand, and restoring a backup is the only clean way out. Take the backup, import a short test file of five or ten rows, check the dates and the signs in the register, and only then run the full file.

If you want to understand what a QFX or OFX actually contains and why the identifiers inside it make duplicate matching possible, the OFX file format reference walks through the transaction and balance blocks that Quicken reads on import.