QuickBooks Unable to Verify the Financial Institution: What It Means and How to Fix It

Last updated July 2026

Short answer: QuickBooks Desktop shows "QuickBooks is unable to verify the Financial Institution information for this download" when the bank identifier inside your QBO Web Connect file does not match an institution in Intuit's financial institution directory. Nothing is wrong with your transactions. The fix is to correct the <FID> and <BID> values in the file, or to generate the file with a converter that writes identifiers QuickBooks recognizes.

This is one of the most misdiagnosed errors in QuickBooks. People see the word "verify" and start re-checking their bank login, their account balance, or their internet connection. None of that is the problem. QuickBooks never even looked at your transactions. It rejected the file at the front door because of a few characters of metadata near the top.

What the error actually means

A Web Connect file, the kind that ends in .qbo, is not just a list of transactions. It is an OFX document that identifies which bank produced it. Two tags carry that identity: <FID>, the financial institution ID, and <BID>, the bank ID. Intuit maintains a directory of financial institutions, and every bank that supports Web Connect has an issued FID in it.

When you import a .qbo file, QuickBooks Desktop reads those tags and looks them up. If the value is missing, malformed, or belongs to no institution Intuit knows about, QuickBooks refuses the import and shows the verification message. It never reaches the transaction records, which is why the error appears instantly rather than after a pause.

So the mental model to keep: this error is about who the file says it came from, not about what is inside it.

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

Usually it did not come from your bank, at least not in the form QuickBooks expects. The common causes, roughly in order of how often they turn up:

The third row is the one that catches small businesses hardest. If you bank with a community bank or a credit union that never registered with Intuit, there is no correct FID to use, and no amount of re-downloading will produce one.

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

A .qbo file is plain text, so you can open and repair it. Work on a copy, not the original.

Step 1. Open the .qbo file in a plain text editor. Notepad on Windows or TextEdit on Mac both work. Do not use Word, which will add formatting.

Step 2. Near the top, find the block containing <FID> and <BID>. You will see something like <FID>10898</FID>. Those digits are the institution identifier.

Step 3. Replace the values with the correct FID and BID for your bank. Intuit's financial institution directory is where those come from, and many banks publish their own Web Connect identifiers in their QuickBooks setup instructions.

Step 4. Save the file, keeping the .qbo extension, and import it again through File, then Utilities, then Import, then Web Connect Files.

If you are on a version that offers it, importing in Classic mode sometimes bypasses the check entirely. That is a workaround rather than a fix, and it does not always appear.

What if my bank has no FID?

This is where the honest answer diverges from the optimistic one. If your institution is not in Intuit's directory, editing the file means picking an identifier that belongs to somebody else. QuickBooks will accept it, because it only checks that the value resolves. Your transactions will import correctly and your books will be right. It is a hack, and it is worth knowing that it is a hack: the file now claims to be from an institution it is not from.

The cleaner route for an unsupported bank is to skip Web Connect and import a CSV instead. QuickBooks Online accepts a CSV in either a three column layout of Date, Description, Amount, or a four column layout of Date, Description, Credit, Debit. You give up the automatic transaction matching that a QBO file brings, and in exchange you never touch a file identifier again. The tradeoff is covered in more depth on the QuickBooks bank statement converter page, which walks through when each format is the right call.

Is this the same as QuickBooks error 106?

No, and conflating them sends people down the wrong path for hours. The verification message is a QuickBooks Desktop problem with a file you are importing. The numbered errors are QuickBooks Online problems with a live bank feed connection. Different product, different subsystem, different fix.

If you landed here from a numbered error, the fix is on the connection, not the file. Start with what to do when the QuickBooks bank feed is not working.

Why not just avoid QBO files entirely?

You can, and for a lot of people that is the right answer. But a Web Connect file earns its keep in one specific situation: when the period you are importing overlaps transactions already sitting in the register. QuickBooks treats a .qbo as though it came straight from the bank, so it matches incoming transactions against existing ones rather than creating duplicates. Import the same period as a CSV and you get a second copy of every transaction, which someone then has to delete by hand.

That is the whole calculus. Fresh period with an empty register, CSV is simpler. Overlapping period, or an account you reconcile every month, QBO saves real time. Getting a valid QBO file out of a PDF statement is what a bank statement to QBO converter is for, and a converter that writes proper institution identifiers means you never see this error in the first place.

Does this affect QuickBooks Online?

Not in the same way. QuickBooks Online accepts uploaded QBO, QFX, and CSV files, and it can now take a PDF or image statement directly, extracting the transactions with AI as long as the upload is in English and 350 KB or less. The strict institution check that produces the verification message is a Desktop behavior around Web Connect imports. If you have hit this error, you are almost certainly on Desktop.

That difference matters when you are deciding where to do the work. Someone reconstructing a closed account's history on Desktop has to produce a valid .qbo. Someone on QuickBooks Online has more paths open, though the 350 KB cap rules out most scanned statements and plenty of ordinary ones.

A note on where the transactions come from

Most people who meet this error are importing history a bank feed cannot reach: an account that closed, a bank that never supported feeds, or a period older than the roughly 90 days QuickBooks backfills when you first connect. In every one of those cases the underlying record is a PDF statement sitting in a folder, and the question is only how to turn it into something QuickBooks accepts. Converting the statement into a valid QBO file solves the format problem and the identifier problem at once, since the converter writes the metadata QuickBooks checks.

If the destination is not QuickBooks at all, converting the same statement to a spreadsheet is the shorter path, and the same technique works for the vendor bills and brokerage reports that pile up alongside it when you need to pull a table out of a PDF into Excel.

The short version

The message is about file metadata, not about your bank, your login, or your transactions. QuickBooks Desktop read the FID inside your Web Connect file, failed to find it in Intuit's directory, and stopped. Fix the identifier in a text editor, use a converter that writes valid ones, or switch to a CSV import and accept that you lose automatic matching. And if you have only the PDF statement to work from, start at the bank statement converter and produce a file that imports on the first try.