# Unable to Verify the Financial Institution Information

- Author: SimpleBankConvert (https://simplebankconvert.com)
- Published: 2026-10-17
- Category: Import errors
- Canonical: https://simplebankconvert.com/blog/unable-to-verify-the-financial-institution-information

> QuickBooks says unable to verify the financial institution information? Why the bank ID in your QBO file isn't recognized and how to fix the file.
When QuickBooks is unable to verify the financial institution information in a download, it can't match the bank named inside your .qbo file to a bank it knows. The usual causes are a bank ID that is missing or unrecognized, a bank that dropped Web Connect, or an outdated bank list in QuickBooks. Check the file's bank lines first.

## Where the financial institution verification message appears

The financial institution verification message comes from QuickBooks Desktop when you import a Web Connect file, the .qbo file a bank offers for QuickBooks. It stops the import before any transaction is read, so nothing lands in your register. It is not a QuickBooks Online bank feed error, and it does not mean your transactions are wrong.

Intuit lists the exact wording, "QuickBooks is unable to verify the Financial Institution information for this download", among the messages in its guide to [fixing Web Connect import errors in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-connectivity/fix-web-connect-import-errors/L8o5eQjO4_US_en_US). The same page groups it with "We can't read the file" and "Your data was not imported", and gives one shared set of fixes for all of them.

You will usually meet it in one of three situations:

- A file you downloaded from your bank's website, often after the bank changed something.
- A file you made yourself, by converting a CSV or PDF statement into .qbo.
- A file from a bank QuickBooks has never connected to before, such as a small credit union or a newly merged bank.

## The financial institution block inside a QBO file

A QBO file is an OFX file with a few Intuit additions, and the part QuickBooks checks here is the set of lines naming the bank. The open OFX standard has an FI block with an organization name and an institution ID. QuickBooks also expects an Intuit bank ID line, INTU.BID, that points at its own list of banks.

The [OFX 2.2 specification from the Financial Data Exchange](https://financialdataexchange.org/wp-content/uploads/2025/12/OFX-2.2.pdf) defines the FI block in its sign-on section: ORG is the organization that defines the institution's name space and FID is the institution's ID, unique within that ORG. The specification also allows private tags, which an organization names with its own prefix and a period, such as ABC.SOMETHING. INTU.BID follows that pattern.

Here is a cut-down excerpt with example values, annotated line by line:

```
<SONRS>
  <STATUS><CODE>0<SEVERITY>INFO</STATUS>
  <DTSERVER>20260331120000
  <LANGUAGE>ENG
  <FI>
    <ORG>EXAMPLEBANK          <- organization name (example)
    <FID>10898                <- institution ID (example)
  </FI>
  <INTU.BID>10898             <- Intuit bank ID QuickBooks looks up (example)
</SONRS>
...
<BANKACCTFROM>
  <BANKID>021000021           <- routing number (example)
  <ACCTID>000123456789        <- account number (example)
  <ACCTTYPE>CHECKING
</BANKACCTFROM>
```

The routing number and account number say which account the lines belong to. The FI lines and INTU.BID say which bank sent them. A file can have a perfect account block and still fail verification if the bank lines are empty or point at a number QuickBooks does not recognize. [The bank ID line that makes QBO files picky](/blog/qbo-files-explained#the-bank-id-line-that-makes-qbo-files-picky) has more on how that one line behaves.

## Why would a real bank's file fail financial institution verification?

A file straight from a real bank can fail financial institution verification when QuickBooks' local bank list is out of date, when the bank has stopped offering Web Connect, or when the bank changed the ID it writes into its files. None of these is a fault in your company file, and each has its own fix.

**The bank list on your computer is old.** QuickBooks Desktop keeps a directory of financial institutions in a file named fidir.txt. If the bank's entry changed after your copy was saved, a new file from that bank no longer matches.

**The bank no longer supports Web Connect.** Banks sometimes switch from Web Connect files to a direct connection, or drop QuickBooks downloads altogether. The download button may still exist and still produce a file that QuickBooks then refuses.

**The bank merged or renamed.** After a merger, files can start carrying the new bank's details while your QuickBooks account is still tied to the old one.

**You are not signed in.** Intuit's Web Connect guide notes that importing .qbo files requires signing in to your Intuit account inside QuickBooks Desktop. A signed-out session can produce import errors that look like a file problem.

## Intuit's fixes for the financial institution message, in order

Intuit's fixes for this message start with a fresh download and end with a test in a new company file. Work through them in order and import the file after each one, because most people are done by the second or third step. Back up your company file before you start.

1. **Download the file again, from the bank's website.** Intuit's Web Connect guide says to download the .qbo directly from the bank rather than from inside QuickBooks. If the fresh file imports, disconnect the account and set it up again so later downloads behave.
2. **Read the bank's notices.** Sign in to the bank's site and follow any message about QuickBooks. If the bank has stopped supporting Web Connect, the guide says to disconnect the account.
3. **Update the financial institutions directory.** Intuit's page on [updating the Financial Institutions Directory in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-feeds/update-financial-institutions-directory-quickbooks/L9CuK0RjS_US_en_US) gives an automatic route through the Bank Feeds Center and a manual one that swaps the fidir.txt file.
4. **Switch Bank Feeds to Classic mode.** The guide suggests Banking, Bank Feeds, Change Bank Feeds Mode, then Classic (Register mode), and importing again.
5. **Test in a new company file.** If the file imports into a blank test company, disconnect and reconnect the account in your real file. If it fails there too, the file is at fault, and the bank needs to look at it.

For a bank-made file that still fails after step 5, gather the bank log files Intuit mentions and call the bank. Say that QuickBooks can't verify the institution in its Web Connect file. That phrasing points the bank at the right team.

## Checking the INTU.BID bank ID in a converted file

A converted file, one you made from a CSV or PDF statement, fails financial institution verification most often because the converter left the INTU.BID line out, left it blank or filled it with a number QuickBooks does not know. Open a copy of the file in a plain text editor and look at the bank lines before anything else.

A short check, done on a copy:

1. Search for INTU.BID. If it is missing, the file has no Intuit bank ID at all.
2. If it is there, note the number. Compare it with a .qbo file you have imported successfully from the same bank, if you have one.
3. Look at the FI block. ORG and FID should be filled in, not empty tags.
4. Check that the account block matches the account you will import into: right account type, right account number.
5. Save as plain text with the .qbo extension, then import into a test company first.

The best fix for a converted file is to make it again with a tool that writes these lines properly, rather than patching them by hand each month. SimpleBankConvert is being built to produce QBO files from PDF statements for this reason; it is not open for accounts yet, and the [homepage](/) explains what it will do.

## When is changing the bank ID the wrong fix?

Changing the bank ID is the wrong fix when the real problem is on the bank's side, when the file came from your bank and your bank has dropped Web Connect, or when you would have to borrow another bank's ID. In those cases an edited file may import once and then cause trouble with the account connection later.

Leave the ID alone when:

- **The file came from the bank and stopped working overnight.** That points to a bank-side change. Update the directory and ask the bank before editing.
- **Your bank is not in Intuit's list at all.** Writing in another bank's number tells QuickBooks the file came from that other bank. The import may work, but the account ends up tied to the wrong institution.
- **The account is already connected to a bank feed.** Importing a file with different bank details into a connected account can conflict with the connection. Disconnect first, or import into an unconnected account.
- **You can't tell which number is right.** A guess that happens to pass is still a guess, and the next month's file may not.

In these cases, entering a short period by hand, or using a CSV in software that accepts one, is safer than forcing the file through.

## After the verified file imports: what to check next

Once the file gets past financial institution verification, QuickBooks can still skip lines or bring in nothing new. The next checks are the date range, transactions QuickBooks has seen before and the way certain lines, such as payroll, should be recorded once they are in.

Look at the import summary. If it says nothing new was found, QuickBooks matched every transaction ID to one it already holds. [Why a Web Connect file shows no new transactions](/blog/no-new-transactions-in-web-connect-file) explains how those IDs work and how to bring in the lines you actually need.

Then scan the new lines for anything that needs more than a category. A single payroll withdrawal from an outside provider, for example, usually covers wages and taxes together. [Recording payroll transactions from bank lines in QuickBooks Online](/blog/import-payroll-transactions-into-quickbooks-online) shows how to split one, and the same thinking applies in Desktop.

If the same statement is also headed into Xero, its import has different failure points. [Why a Xero bank statement import fails](/blog/xero-bank-statement-import-failed) covers those.