How to Import a Bank Statement into Quicken (CSV to QFX)

Why you can't import a CSV directly

When you download a statement from your bank's website you usually get a CSV or Excel file. Quicken Desktop (Windows and Mac) has no built-in CSV importer for transactions, it expects a financial-data format. The closest match to what Quicken actually wants is QFX, Intuit's flavor of OFX used for "Web Connect" imports. A QFX file carries the same rows your CSV does (date, amount, payee, memo) but wrapped in tags Quicken understands, with a header that identifies your account.

So the workflow is two quick steps: convert CSV → QFX, then import the QFX. QBO Maker's converter does the first step in your browser, nothing is uploaded, and outputs a Quicken-ready .QFX. See CSV to QFX for the conversion details.

Step 1: Convert your CSV to a .QFX file

1. Open your bank statement CSV or Excel file and confirm it has a header row with at least a date, amount, and description/payee column.
2. Go to the converter and drop the file in.
3. Map the columns if prompted, pick which column is the date, which is the amount (or separate debit/credit columns), and which is the description.
4. Choose QFX (Quicken) as the output format.
5. Download the generated .qfx file. The whole conversion happens locally in your browser.

If your dates look wrong after import, that's almost always a date-format mismatch in the source file, MM/DD/YYYY vs DD/MM/YYYY. Fix it in the converter's date setting and re-export before importing.

Step 2: Import the .QFX into Quicken

On Quicken for Windows:

1. Open the account register you want the transactions to land in (or create the account first).
2. Click File → File Import → Web Connect File (.QFX).
3. Browse to your converted .qfx file and select it.
4. When prompted, choose "Link to an existing account" and pick the right Quicken account, or create a new one. Linking is what prevents duplicate or orphaned accounts.
5. Review the transactions in the register and accept them.

On Quicken for Mac: use File → Import → Bank or Brokerage File (OFX, QFX), then select the file and choose the destination account the same way.

Quicken matches incoming transactions against what's already in the register, so re-importing an overlapping date range usually won't create duplicates, but it's still smart to convert only the new statement period.

Fixing "unable to verify the financial institution"

This is the most common QFX import error. Quicken validates the bank identifiers in the file header, the <FID> (financial institution ID) and <INTU.BID> tags, against its online services. If those don't match a recognized institution, the import is blocked.

Two reliable fixes:

• Use a recognized FID. Many users edit the file in a plain-text editor (Notepad / TextEdit) and set the <FID> and <INTU.BID> to a known-good value, then import the edited copy. You can still name the Quicken account after your real bank.
• Re-generate a clean header. A well-formed QFX from the converter includes a valid header structure, which avoids the malformed-file version of this error. If you still hit verification trouble, it's a bank-recognition issue, not a corrupt file.

Fixing OL-220 / OL-221 and other import errors

The OL-220 through OL-226 family of errors almost always points to a problem in the QFX header, a missing tag, a bad date, or an encoding issue. Checklist:

• Open the file in a text editor and confirm the header block is intact and the transaction tags (<STMTTRN>) are properly closed.
• Check the amounts. Debits must be negative and credits positive; a stray currency symbol or thousands-separator can break parsing. Clean these in your CSV before converting.
• Confirm one account per file. A QFX should describe a single account. If your CSV mixed two accounts, split it and convert each separately.
• Try a small test batch. Convert just 5-10 rows first to confirm the mapping is right before doing the full statement.

Want to sanity-check the structure before importing? Run the output through the file validator to catch header and tag problems early.

QFX vs QIF vs OFX in Quicken

Quicken accepts a few formats and they behave differently:

• QFX (Web Connect), the modern, preferred import; Quicken validates the institution and matches transactions intelligently. Best choice for current Quicken versions.
• QIF, an older text format. Recent Quicken for Windows restricts QIF imports to certain account types (like cash and asset accounts), so it's no longer reliable for bank/checking imports.
• OFX, the open standard QFX is based on; some Quicken builds accept it via the same import dialog. If you use other software too, see CSV to OFX.

For Quicken specifically, QFX is the safest pick. If you're also moving data into QuickBooks, you'd convert to QBO instead, see importing CSV into QuickBooks Online.

Frequently asked questions

Related