# Import CSV into Quicken: What Works and What Doesn't

- Author: SimpleBankConvert (https://www.simplebankconvert.com)
- Published: 2026-04-13
- Updated: 2026-04-13
- Category: Quicken and other software
- Canonical: https://www.simplebankconvert.com/blog/import-csv-into-quicken

> How to import CSV into Quicken: which Quicken versions accept CSV, the column layout they want and when converting the CSV file to QFX is easier.
You can import CSV into Quicken for Windows through File, File Import, Banking Transactions, From (.CSV) File, as long as the file follows Quicken's fixed ten-column layout. The import does not check for duplicates or create transfers, so it suits one-off history. For regular monthly statements, a QFX file is usually the easier route.

## Which Quicken versions read a bank transaction CSV?

Current Quicken for Windows reads a bank transaction CSV. [Quicken's help article on importing transactions from a .CSV file](https://info.quicken.com/win/import-transactions-from-csv-file) gives the menu path and the column rules. The article covers Windows only and does not name a minimum release, so check your own File Import menu for a From (.CSV) File entry.

If the entry is missing, the most likely reason is an older copy of the program. Quicken's broader [guide to importing data into Quicken for Windows](https://www.quicken.com/support/how-do-i-import-data-quicken-windows) still contains a line saying CSV files can only be imported to update security prices, which reads like the older rule. Updating Quicken to the current release is the first thing to try before rebuilding the file in another format.

Quicken for Mac is a separate program with its own import screens. The Windows CSV rules below may not apply there, so Mac users should look at that program's own import menu before building a file. When the Mac version refuses a file, the usual fallback is a QFX download, which has its own steps in [importing a QFX file into Quicken for Mac](/blog/import-qfx-into-quicken-for-mac).

Quicken Simplifi, the web product, is a different program again, and nothing in this post describes its screens.

## The ten Quicken CSV columns, in order

The Quicken CSV layout has ten columns in a fixed order. The first seven must be present on every row, even when some are blank, and the last three are optional. Quicken's help says not to add, remove or reorder columns. A header row is allowed but must follow the same order.

| Position | Column | Required? | What goes in it |
| --- | --- | --- | --- |
| 1 | Date | Yes | The transaction date, month first |
| 2 | Payee | Yes | The name you want to see in the register |
| 3 | FI Payee | Position only | Ignored by Quicken, kept for older Mint exports |
| 4 | Amount | Yes | A signed number |
| 5 | Debit/Credit | Position only | Leave blank and use the sign on Amount |
| 6 | Category | Position only | A category name, or blank |
| 7 | Account | Yes | The Quicken account the line belongs to |
| 8 | Tag | Optional | One or more tags |
| 9 | Memo | Optional | Any note |
| 10 | Chknum | Optional | A check number |

Three of those columns trip people up. FI Payee and Debit/Credit look as if they should hold data, but Quicken wants them as empty placeholders. The Account column is required because a single CSV can carry lines for several accounts at once.

### What Quicken does with the Account column

When a row names an account that does not exist in your data file, Quicken asks what to do with it. The help article lists three choices: ignore those rows, add them to an existing account, or create a new account. Spelling the account name exactly as it appears in Quicken avoids the question altogether.

The import window also offers a Create Sample File button. Using that sample as your starting point is safer than typing a header row from memory, because it comes from your own copy of Quicken.

## Quicken CSV dates, signs and commas

Quicken CSV values follow four small rules. Dates use month, day, year, such as 5/31/2025. Amounts carry a minus for money out and nothing or a plus for money in. Any value containing a comma goes inside double quotes. Categories and tags use a colon to separate levels.

Most failed files break one of those four. Dates are the most common. A bank in the US exports month first, but a file saved on a computer set to a different region, or a spreadsheet that reformats dates on save, can turn 03/04/2026 into 4 March. Keep the date column as text before saving.

Signs come next. Quicken treats a positive amount as something that increases net worth and a negative one as something that decreases it. On a checking account, that means a deposit is positive and a payment is negative. On a credit card account, a purchase is negative and a payment to the card is positive. A statement that prints withdrawals and deposits in separate columns has to be merged into one signed column first.

Commas matter because CSV uses them to separate columns. A payee such as `Smith, Jones & Co` splits into two columns unless it is quoted. Amounts with thousands separators are allowed, but `"1,250.00"` then needs quotes too.

For subcategories, write `Utilities:Water`. For two tags on one line, write `Client A:Rental`. Save the file as plain text in UTF-8 so that accented payee names survive.

## What does a Quicken CSV import do with transfers and duplicates?

A Quicken CSV import does nothing with either. Quicken's help says CSV imports do not check for or match existing transactions, unlike Web Connect imports, so importing the same file twice gives you every line twice. It also says CSV import will not create transfers, even when the category names another account in brackets.

### Duplicates

Without matching, the only defence is the file itself. Before you import, find the date of the last transaction already in the Quicken account, and delete every row in the CSV on or before that date. After you import, compare the register's ending balance with the statement's closing balance. If the register is higher or lower by exactly the total of a block of lines, that block came in twice or not at all.

The same rule applies to files that overlap each other. A January file that runs to February 3 and a February file that starts on February 1 share three days. Trim one before importing either.

### Transfers

A payment from checking to a credit card is one transfer, but a CSV import records it as two unrelated lines, one in each account. After importing, turn one of the pair into a transfer to the other account and remove the leftover line, so the movement is recorded once. On a file with many transfers, that clean-up can take longer than the import saved.

## A worked Quicken CSV built from a PDF statement

A worked Quicken CSV starts with the statement lines, merges withdrawals and deposits into one signed amount, adds the account name to every row and leaves the placeholder columns empty. The example below uses a made-up April statement for a checking account named Household Checking.

The statement printed these four example lines:

| Date | Description | Withdrawals | Deposits |
| --- | --- | --- | --- |
| Apr 2 | PAYROLL ACME TOOLS | | 2,140.00 |
| Apr 5 | CITY WATER DEPT, AUTOPAY | 64.18 | |
| Apr 9 | CHECK 1187 | 300.00 | |
| Apr 12 | GROCERY MART #22 | 118.47 | |

Rebuilt for Quicken, with a header row, the file looks like this:

```
Date,Payee,FI Payee,Amount,Debit/Credit,Category,Account,Tag,Memo,Chknum
4/2/2026,Acme Tools Payroll,,"2,140.00",,Salary,Household Checking,,,
4/5/2026,"City Water Dept, Autopay",,-64.18,,Utilities:Water,Household Checking,,,
4/9/2026,Check 1187,,-300.00,,,Household Checking,,,1187
4/12/2026,Grocery Mart,,-118.47,,Groceries,Household Checking,,,
```

Notice the details. The deposit is positive and quoted because of its comma. The water payee is quoted for the same reason. The check row moves the number into Chknum and leaves Category blank, which Quicken allows. Every row has ten values, counting the empty ones.

### Getting from the PDF to the rows

Typing four lines is quick. Typing three hundred is not. If the statement is a digital PDF, a converter can produce the dated, signed rows, and you then move the columns into Quicken's order. [SimpleBankConvert](/get-started) is being built to turn a PDF statement into a CSV with consistent dates and a single signed amount column, laid out for QuickBooks and Xero, so you would reorder the columns before importing into Quicken. For the wider set of routes from a PDF, see [importing a PDF bank statement into Quicken](/blog/import-pdf-bank-statement-into-quicken).

### Checking the result

After importing, open the account register and check three things: the first and last dates match the statement period, the number of new lines matches the statement, and the balance matches the closing balance. If the balance is wrong, set it with the Update Balance option on the register's gear menu only after you know why it differs.

## When converting the CSV to QFX beats a Quicken CSV import

Converting to QFX beats a Quicken CSV import when you bring in statements every month, when the account has frequent transfers, or when your file carries no account name. A QFX file goes through Web Connect, which matches transactions already in Quicken and remembers which account each file belongs to.

The trade-off is that a QFX file is harder to inspect and harder to build. It needs a correct header, a bank identifier and a unique ID on every transaction. A CSV you can read and fix in any spreadsheet. That makes CSV the better choice for a single block of old history, such as two years of statements from a closed account, where duplicates are easy to rule out because nothing else covers those dates.

A practical rule follows from that:

- **One-off history, no overlap:** use CSV and check the balance afterwards.
- **Every month, same account:** use a QFX from the bank, or convert to QFX, knowing that Quicken's Web Connect troubleshooting page says it does not support QFX files made by conversion software.
- **Heavy transfers between accounts:** use QFX, or plan time for transfer clean-up.
- **File will not import either way:** check the header and dates before blaming the format.

That last point applies outside Quicken too. Files rejected by accounting software usually fail for the same few reasons, a bad date, a missing field, an unexpected header, and the checklist in [why QuickBooks rejects a converted QBO file](/blog/converted-qbo-file-rejected-by-quickbooks) is a useful model even when the program on the other end is Quicken.