You can import financial transactions into Quicken from a comma-separated values (.CSV) file. This feature is useful when you need to add historical data, manage accounts manually, or bring in transactions from a financial institution that isn’t supported for download.
Unlike Web Connect (.QFX) imports, CSV imports do not check for or match existing transactions. Every transaction in the file is added to the register, even if an identical transaction already exists.
Supported account types
The banking CSV import supports banking, cash, credit card, other asset, and other liability accounts. Investment transactions use a separate import path and a different file format. To import those, see Import investment transactions from a .CSV file.
Before you begin
The .CSV file must follow a strict format. The file must include all required columns, in the correct order, even if some columns have no data. A header row is optional, but if you include one, it must follow the same column order.
Required file format
The file must contain the first seven comma-separated columns in exactly this order. The last three columns are optional, but if you use them, they must appear in this order:
-
Date *
-
Payee *
-
FI Payee
-
Amount *
-
Debit/Credit
-
Category
-
Account *
-
Tag
-
Memo
-
Chknum
Columns marked with * must contain data in each row. The other columns may be blank, but each column position must be present in the file.
Formatting rules
Each value in the file must follow these rules:
-
Date values use the mm/dd/yyyy format. Leading zeros are optional for single-digit months and days. For example, 5/31/2025.
-
Amount values may include commas. For example, 5400 and 5,400 are both valid.
-
The FI Payee column provides backward compatibility with CSV files exported from Mint. Quicken ignores it during import, but the column must be present.
-
The Debit/Credit column also provides Mint compatibility. Leave this column blank and use a signed value in the Amount column instead. A positive amount, such as +5,400, increases net worth. A negative amount, such as -5400, decreases it. If the amount has no sign, Quicken treats it as positive.
-
If a field contains a comma, enclose the field in double quotes. For example, “Office Supplies, Inc.”
-
Use the format Category:Subcategory for subcategories.
-
Use the format tag1:tag2 for multiple tags.
-
Do not add, remove, or reorder columns.
Import the file
To import a properly formatted .CSV file:
-
Open your Quicken data file.
-
Select File > File Import > Banking Transactions > From (.CSV) File.
Note: You can also select Create Sample File for extra guidance. -
In the Import transactions from .CSV file window, review the format requirements.
-
Select Choose .CSV File to Import….
-
Browse to your file and select it.
-
Select OK.
If the file does not meet the required structure, an error message explains what to fix.
When account names don’t match
If the file contains transactions for an account that doesn’t exist in your data file, the Account does not exist in Quicken window opens. Choose one of these options for that account:
-
Ignore transactions from this account skips the account’s transactions.
-
Add transaction to the existing account imports the transactions into an account you select from the list.
-
Add transaction to a new account of type creates an account of the type you select and imports the transactions into it. The available types are Banking, Cash, Other Asset, Credit Card, and Other Liability.
Continue the import after you choose an option.
After the import
When the import completes, Quicken displays a summary that shows:
-
The number of transactions imported
-
Any new accounts created
-
Any tags added
To update the balance of a new or existing manual account:
-
Open the account register.
-
Select the gear icon.
-
Choose Update Balance.
Additional notes
Keep these limits in mind when you import:
-
CSV import does not detect or create transfer transactions, even if the Category field contains a bracketed account name such as [Checking].
-
Reimporting the same file creates duplicates. Review your register after each import to confirm the results.
-
Use a plain-text editor or spreadsheet tool that supports UTF-8 encoding to prepare your file.