Quicken Unable to Verify the Financial Institution: Why QFX Imports Fail

Last updated August 2026.

Quick answer: Quicken shows "Quicken is currently unable to verify the financial institution information for this download" when it cannot match the QFX file you are importing to a bank on Intuit's Web Connect list. Two things cause it: the institution has not paid Intuit's licensing fee (so the INTU.BID branding tag inside the file means nothing to Quicken), or your Quicken subscription has expired, which blocks even files you downloaded successfully months ago. The file itself is almost never corrupt. The transactions are sitting right there in plain text, and there are four practical ways to get them into your books.

What the error actually means

A .qfx file is an OFX file with two Intuit tags added. One of them, INTU.BID, is a branding ID: a number that tells Quicken which financial institution issued the file. Before Quicken imports anything, it reads that number and checks it against its own list of institutions that have a current Web Connect arrangement with Intuit.

When the number is missing, unrecognized, or attached to an institution whose arrangement has lapsed, Quicken stops. It does not parse the transactions, it does not warn you about a specific line, it just declines the whole file. That is why the message says nothing about the data: Quicken never got that far.

This is a licensing check, not a data-integrity check. Banks pay Intuit a fee to issue Web Connect files, and this error is the enforcement mechanism. Understanding that saves a lot of time, because most people start by re-downloading the file, which cannot help.

Why does this happen if the file came from my bank?

Because plenty of institutions produce OFX-family files without being licensed for Quicken specifically. A credit union might export a perfectly valid .ofx that a dozen other finance apps read without complaint, then Quicken refuses it. Smaller banks, newer fintech accounts, and business-only platforms fall into this gap constantly.

The other common version: the bank was licensed, you downloaded QFX files for years, and then it stopped working. That usually means the arrangement changed on Intuit's side or the bank moved to a different connection method, not that anything is wrong on your end.

Does an expired Quicken subscription cause this error?

Yes, and this catches people out because the message points at the bank rather than at the subscription. When a Quicken subscription lapses, the same verification error appears on QFX files, including ones you already downloaded and saved to your own machine. Nothing about those files changed. Quicken simply stops honoring the import.

Check your subscription status first, since it is the fastest thing to rule out. If it has expired and you plan to renew anyway, renewing restores the import. If you were leaving Quicken regardless, that answers a different question: you now need those saved files in a format that does not depend on a subscription at all.

How do I fix the Quicken unable to verify financial institution error?

There are four routes, in the order most people should try them.

1. Confirm the subscription is active. Thirty seconds, and it explains a surprising share of cases, especially when the import used to work.

2. Check whether your bank actually supports Web Connect. In Quicken, look for the institution in the add-account search. If it is not there, or it only offers Express Web Connect rather than Web Connect, then QFX import was never going to work for that account and no amount of retrying changes it.

3. Import a QIF file instead. QIF predates the licensing layer and carries no branding check, so Quicken accepts it from anywhere. The tradeoff on Quicken for Windows is that QIF import is limited to cash, asset, and liability accounts, which rules it out for a lot of checking-account work.

4. Build the file from the statement instead of the download. This is the route that works regardless of what your bank has arranged with Intuit, because a PDF statement carries no branding check at all. Convert it into a spreadsheet you can work in directly, or into a QBO or OFX file if the transactions need to land in accounting software. The Quicken bank statement converter page sets out which formats Quicken accepts and where each falls short, and the walkthrough is in our guide to importing bank statements into Quicken.

Can I edit the QFX file to fix it?

You can open a .qfx in any text editor, and forum threads will tell you to paste in a different INTU.BID value. Be careful with that advice. You are guessing at an identifier belonging to another institution, and a wrong value either fails the same check or imports the transactions under a bank that is not yours, which quietly corrupts the account mapping in your file.

Editing is also fragile as a habit. Every future download needs the same manual surgery, and one missed edit puts bad data in the register. If you are going to touch the file at all, it is worth understanding how the OFX structure works first, so you know what each tag does before changing it.

Is this the same as the QuickBooks version of the error?

It is the same mechanism in a different product. QuickBooks reads .qbo files that carry their own Intuit branding values and shows a near-identical complaint when they do not check out. If you landed here but your file is actually a .qbo, the fix is different in the details, and we cover it separately in QuickBooks unable to verify the financial institution.

Worth knowing: the two formats are not interchangeable. A .qfx will not import into QuickBooks and a .qbo will not import into Quicken, even though both are OFX underneath. Each product checks for its own branding and rejects the other. If your books are moving from one to the other, converting Quicken files into a QuickBooks Web Connect file is a cleaner path than fighting either importer.

What if I just need the transactions, not Quicken?

This is where a lot of people end up, particularly during a cleanup or a year-end scramble. The QFX file is not the goal; the transactions are. Once they are in a spreadsheet you can categorize them, total them, hand them to an accountant, or import them somewhere that does not have a branding list.

A .qfx is readable enough to work with because every field inside it is labeled: the date sits in DTPOSTED, the amount in TRNAMT, the description in NAME. Our reference on the QFX file format maps each tag to the spreadsheet column it belongs in, so you know what you are looking at. The more reliable route, and the one that also covers periods the download never reached, is to skip the .qfx and run the statement PDF through the main bank statement converter instead, which returns Excel, CSV, QBO, or OFX.

How to avoid this next time

If the account is with an institution Quicken does not recognize, stop fighting the QFX route and standardize on the statement. PDF statements are available for roughly seven years at most US banks, they do not depend on any licensing arrangement, and they keep working after an account closes, which is exactly when downloads stop being offered.

For accounts where Web Connect does work, download the QFX promptly rather than saving it for later. Files sitting in a folder are the ones that break when a subscription lapses or an arrangement ends, and by then the bank may no longer offer that period as a download at all.

The short version

The error is Quicken failing a licensing check on the INTU.BID tag, not a problem with your transactions. Rule out an expired subscription first, then confirm the bank supports Web Connect at all. If it does not, editing the file is a bad habit and re-downloading is pointless. Convert the statement or the .qfx directly into the format you actually need, and the data stops depending on whether two companies have a current agreement.