Convert an OFX to a QFX With the Intuit Bank ID

OFX and QFX are almost the same file

Open an OFX and a QFX side by side and the transaction blocks look identical, because they are. QFX is Quicken's flavor of OFX: the same underlying statement data with a few Intuit-specific header fields added at the top, chiefly INTU.BID, along with ORG and FID. Nothing about the dates, amounts, or payees changes between the two. That is why converting OFX to QFX is a small, precise edit rather than a re-extraction; the transactions are already right, and only the header that identifies the bank to Quicken is missing.

Why Quicken rejects a plain OFX

Quicken will not import a plain OFX because it cannot verify which financial institution the file came from. The identifier it looks for is INTU.BID, the Intuit Bank ID, a licensed value from Intuit's institution directory. When it is missing or wrong, Quicken throws the OL-221 error, can't verify financial institution, and refuses the file. So an OFX that another tool or bank handed you can be perfectly valid and still bounce, purely because it lacks the Intuit header Quicken insists on.

What the conversion adds

Converting the OFX to QFX inserts the Intuit headers Quicken needs, INTU.BID, ORG, and FID, with a value Quicken recognizes for the institution, and saves the result with the .qfx extension. The statement body is left as it is, since it was never the problem. The result is a file that presents as a proper Quicken Web Connect download rather than a generic OFX, which is exactly what clears the OL-221 verification and lets the import proceed.

Importing the QFX via Web Connect

With the headers in place, you import the .qfx into Quicken through its Web Connect path, and Quicken reads the transactions into the account you point it at. Because the data was unchanged by the conversion, the amounts and dates match what the OFX always held; the QFX wrapper simply got it past the front door. If Quicken still balks, it is almost always the INTU.BID value, not the transactions, that needs to match the institution.

Accuracy and privacy

Since the conversion touches the headers and leaves the transactions intact, what you import matches the OFX exactly, and the file is reviewable before it goes into Quicken. The output is a standard QFX ready for Web Connect. Because the file holds real account activity, it is processed to add the headers and then deleted automatically, with nothing kept on a server afterward.

Frequently Asked Questions