Quicken Will Not Import My QFX File: How to Fix It and What INTU.BID Does

TL;DR: Quicken refuses most QFX files because of a single tag called INTU.BID. It is an Intuit bank identifier that Quicken checks on import to confirm the financial institution has licensed the right to send files into Intuit software. If that value is missing, unrecognized, or belongs to a bank that is not licensed, the import fails no matter how valid the transaction data underneath it is. This is also why renaming a plain .ofx file to .qfx never works: renaming a file does not add a tag that was never inside it.

If you have spent an evening being told your file is not a valid Quicken file while looking at a file that is obviously fine, you have run into a licensing check rather than a data problem. Below is what the check does, the five things that actually cause a rejected import, and the route that works when your bank simply will not hand you a QFX.

Why Quicken will not import my QFX file

Because Quicken validates where the file came from before it looks at what is in it. A QFX file is Intuit's licensed flavor of the Open Financial Exchange format, and it carries Intuit specific tags that a standard OFX file does not have. The most important of those is INTU.BID. On import, Quicken reads that identifier and decides whether the file originated from an institution entitled to deliver Web Connect files. A file that fails that check is rejected before the transactions are ever parsed.

This catches people out because the failure looks like a corruption problem. The error text points at the file, so the natural response is to download it again, or open it in a text editor to look for damage. The data is usually perfect. The gate is upstream of the data.

What is INTU.BID?

INTU.BID is a numeric bank identifier that Intuit assigns to financial institutions, written into QFX files as a tag near the top of the document. Its job is verification: the value makes a connection back to Intuit and confirms that the institution has licensed the right to import those files into Intuit software. A related tag, INTU.USERID, may carry the account holder identifier. Neither tag exists in the base OFX specification, which is exactly what separates a QFX file from a plain OFX file.

Banks pay for that licensing, which is the uncomfortable commercial reality behind a lot of import failures. When a small bank or credit union stops paying, or never paid, its downloads stop working in Quicken even though the file format itself is unchanged. Nothing broke on your machine.

Why renaming an OFX file to .qfx does not work

A file extension is a label, not content. Renaming statement.ofx to statement.qfx changes what your operating system thinks the file is and changes nothing inside it. Quicken opens the renamed file, looks for INTU.BID, does not find it, and refuses the import. The same applies in reverse, and it applies to the QuickBooks .qbo variant too.

This is worth stating plainly because renaming is the single most common piece of advice circulating in forums, and it wastes a lot of time. If you need a QFX, you need a file generated as a QFX. The structural differences between these formats are covered in more detail in the OFX file format reference, which shows the header and tag hierarchy the variants share.

The five reasons a QFX import fails

Nearly every rejected import traces back to one of these.

Does Quicken import OFX files?

Not reliably, and you should plan on no. Quicken's import path is built around Web Connect, which means QFX. Plain OFX files lack the Intuit identifier that path checks for, so they are usually refused. Other finance software is less fussy: Microsoft Money, GnuCash, Moneydance and Banktivity all read standard OFX directly, and Xero accepts OFX for manual statement imports and recommends it where possible. Quicken is the outlier, not the rule.

How do I fix the file is not a valid Quicken file error?

Work through it in this order. First confirm you are using File, then File Import, then Web Connect File, because importing through the wrong menu produces the same message on a perfectly good file. Second, open the file in a text editor and look for INTU.BID near the top. If it is absent, you have an OFX file and no amount of retrying will change that. Third, if the tag is present but the import still fails, the identifier is likely not recognized, which is a licensing matter between your bank and Intuit that you cannot resolve from your desk. At that point, generating your own QFX from the statement is faster than any support queue.

Should I edit INTU.BID by hand?

You will find forum posts suggesting you open the file in a text editor and swap the FID and INTU.BID values for a number belonging to a licensed bank. It sometimes works. I would not recommend it as a habit. You are hand editing a financial file to impersonate a different institution, a single mistyped character invalidates the document, and the value you copy can stop working whenever Intuit changes its list. It also does nothing about the underlying problem if your file was malformed to begin with. Generating a correct file is less fragile and takes less time than the editing.

What if my bank does not offer a QFX download?

This is now the common case rather than the edge case. Many US banks have retired Direct Connect and some never licensed Web Connect at all, so the QFX download button people remember simply is not there anymore. Your statements are still available as PDFs, and they contain every transaction the download would have carried, usually reaching back seven years rather than the 90 days a feed typically offers.

Converting one is the practical route. Upload the PDF statement to the PDF to QFX converter and download a Web Connect file built to spec, including the LEDGERBAL balance block whose absence triggers the OL-221 family of parse errors. The convert bank statement to Quicken walkthrough covers the import screen by screen, and if you are seeing a specific code, the Quicken connection errors reference decodes what each one means. For software that takes standard OFX, the bank statement to OFX converter produces that instead.

How to import a QFX file into Quicken correctly

Once you have a valid file, the import itself is short:

1. In Quicken, choose File, then File Import, then Web Connect File. Do not use a generic import option.
2. Select the .qfx file.
3. When Quicken asks, link the transactions to the account that already exists in your file rather than letting it create a new one. Creating a new account is what splits a register's history in two.
4. Review the transactions Quicken flags as possible duplicates before accepting them.
5. Reconcile against the statement closing balance.

That last step is the one people skip. If the closing balance in Quicken matches the balance printed on the statement, nothing is missing and nothing has been counted twice. If it does not match, the difference is almost always a duplicate at the edge of a date range you imported twice. Teams handling this across dozens of accounts every month usually move it off the desktop entirely and let reconciliation software match the transactions automatically, but for a single household file the manual check takes two minutes and is worth doing every time.

Will importing a QFX create duplicate transactions?

Only if the file reuses transaction IDs. Each transaction carries a FITID, an identifier that must be unique within the account, and Quicken uses it to recognize entries it has already seen. A correctly generated file gives every transaction a distinct FITID, so overlapping a few days at either end of a date range is safe and is generally smarter than leaving a gap. Duplicates appear when a generator lazily reuses IDs, which is one more reason the source of the file matters.

Frequently asked questions

What is INTU.BID in a QFX file? It is an Intuit assigned bank identifier that Quicken checks during import to verify the financial institution has licensed the right to deliver files into Intuit software. It is not part of the base OFX specification, and its absence is the most common reason a QFX import is refused.

Can I just rename my OFX file to QFX? No. Renaming changes the label on the file and nothing inside it, so the INTU.BID tag Quicken looks for is still missing and the import still fails. You need a file generated as a QFX.

Why did my bank's QFX file suddenly stop importing? Usually because the licensing arrangement behind the identifier changed rather than anything on your computer. Banks retire Web Connect support on their own schedule, and when they do, previously working downloads stop being accepted with no warning.

Does Quicken accept OFX files? Generally no. Quicken's import path expects Web Connect QFX files. Microsoft Money, GnuCash, Moneydance, Banktivity and Xero all accept standard OFX, so the format is fine, it is Quicken that is restrictive.

How far back can I recover transactions this way? As far back as your bank keeps statements, which for most US banks is seven years. That is considerably further than a live feed reaches, which is typically 90 days and rarely more than 18 months.