How to Fix OFX and QFX Import Errors in Quicken

TL;DR: Most Quicken OFX and QFX import failures come down to five things: using the wrong import menu, a file missing the Quicken bank ID (so it needs to be a QFX, not a plain OFX), the wrong account being matched, an unsupported OFX version, or bad date and amount formatting. Import through File, File Import, Web Connect File, use a QFX for Quicken rather than a plain OFX, and confirm the account when prompted. Below is each error and its fix.

First, use the right import path

A surprising number of failed imports are not errors at all, just the wrong menu. Quicken imports account files through File, then File Import, then Web Connect File. If you try to open the file by double-clicking it, or use a different import option, Quicken may ignore it or throw a vague message. Start every import from the Web Connect File option and pick the account you want the transactions to land in.

Common Quicken import errors and how to fix them

1. The file is a plain OFX and Quicken wants QFX

Quicken is built around QFX, its Web Connect format, which is OFX with an added bank identifier (the INTU.BID field). A plain OFX with no bank ID often imports fine into MS Money but gets rejected or ignored by Quicken. The fix is to give Quicken a proper QFX. If you are converting a statement, a genuine Web Connect QFX can only come from your bank, so use the CSV route on the convert bank statement to Quicken page instead, which carries the transaction detail Quicken needs.

2. Quicken asks to link or create an account, and nothing matches

When you import, Quicken tries to match the file to an existing account. If it cannot, it prompts you to link or create one. Choose the account you actually want, not a new one, or you will split your history across two registers. If you keep creating stray accounts, delete the extras and re-import into the correct one.

3. Parse errors and wrong OFX version

OFX comes in an older 1.x (SGML) style and a newer 2.x (XML) style. Quicken generally expects the 1.x Web Connect structure, so a file authored as strict XML OFX can throw a parse error even though it looks valid. This is also why converted files are not the answer here: no third party can issue the QFX institution tag Quicken checks for. If you hand-edited the file, an unclosed tag or a stray character will also break the parse.

4. Dates or amounts land wrong

If transactions import on the wrong day or with flipped signs, the source data had ambiguous dates (month and day reversed) or split debit and credit columns that were not merged into one signed amount. This is common when the file was built from a messy CSV. Rebuild the file from a clean source so dates are normalized and each transaction has a single signed amount before you import, which is exactly what the convert bank statement to Quicken page walks through with the raw export.

5. Duplicate transactions after import

Quicken uses each transaction's unique ID (FITID) to detect duplicates. If the file has no IDs, or reuses the same ID, re-importing doubles up transactions. A bank issued QFX carries stable, unique IDs. A CSV import carries none and Quicken does not match it against existing transactions, so import each converted period only once.

When the bank will not give you a QFX at all

Often the real problem is upstream: your bank only offers a QFX for the last few months, or hides it behind a paid Direct Connect. If the download itself is failing rather than the import, our guide to Quicken connection errors covers the OL and CC codes banks throw during a sync. For older statements you are left with a PDF and no account file. In that case, convert the PDF directly. Upload it to a tool that will convert a bank statement to Quicken and download a CSV built from the statement, then import it through Quicken's Banking Transactions CSV import. This also works for scanned statements and photos, since OCR reads the pages before extracting the transactions.

Reconcile after the import

Once the transactions load, do not skip reconciliation. Match Quicken's ending balance to the statement's ending balance to confirm nothing dropped or duplicated during import. If the totals differ, the culprit is usually a duplicated batch or a few transactions that matched the wrong account. Once the numbers agree and everything is categorized, the reconciled data is also a clean starting point if you later need to turn it into a P&L and balance sheet for a review or a lender.

Frequently asked questions

Why does Quicken say my file is not a valid Web Connect file?

The file is either a plain OFX without the Quicken bank ID, an OFX in the wrong version, or has a structural error. Import the Web Connect (QFX) file your bank issued. If all you have is a statement, convert it to CSV and use File, then File Import, then Banking Transactions, then From (.CSV) File instead, because no converter can produce the identifier Quicken requires.

Can Quicken import an OFX file, or only QFX?

Quicken does not import plain OFX at all. It reads Web Connect (QFX), which includes the bank identifier Quicken uses to match the account, and that tag can only come from the bank. When you have no QFX, the supported route is Quicken's CSV import rather than another conversion.

Will re-importing fix wrong transactions without creating duplicates?

Yes, if the file has unique transaction IDs. Quicken uses those IDs to recognize transactions it already has, so a corrected file with stable IDs updates the register instead of doubling entries. Files with no IDs are the usual reason duplicates appear.

Does Quicken for Mac handle imports differently?

The menu labels differ slightly, but the process is the same: you import a Web Connect (QFX) file and point it at the right account. A valid QFX that works on Windows Quicken imports the same way on Quicken for Mac.