What you are seeing
QuickBooks is unable to verify the Financial Institution information for this download. Please try again later.
This message sends people to their bank, where support has no idea what QuickBooks is asking about. The bank is rarely the problem. QuickBooks is not saying your institution is unsupported; it is saying it does not recognise the identifier inside this particular file.
Two wordings, one check
QuickBooks Desktop shows this problem in a couple of forms, depending on version and on how far it got into the file. Both come from the same lookup.
QuickBooks is unable to verify the Financial Institution information for this download.
The file you have selected is not from a QuickBooks-supported financial institution.Once you know which identifier your bank uses, you can produce a QBO file with the correct identifier in it from any PDF statement, which is the whole of the fix.
What QuickBooks is checking
QuickBooks maintains a list of financial institutions enrolled for Web Connect, each with a numeric Intuit Bank ID. When you import a .qbo file, it reads the INTU.BID tag, looks the number up, and refuses the file if the number is not on the list. Desktop keeps a local copy of that list, refreshed when QuickBooks updates — which is why an out-of-date installation can reject a bank that a current one accepts.
So the message means "the number in this file is not one I know". Your bank may be perfectly well supported — the file just does not say so correctly.
The causes, in order of likelihood
| Cause | How to tell | Fix |
|---|---|---|
| Missing or placeholder INTU.BID | Tag absent, empty, or all zeros | Supply the bank’s real BID |
| Number taken from a QFX file | The file was made by renaming or editing a Quicken download | Use the BID from a bank-issued .qbo |
| QuickBooks out of date or retired | Help → About shows an old release, or the version is past its support date | Update, or move to IIF |
| Region mismatch | A US bank’s file going into Canadian QuickBooks, or the reverse | Use the edition that matches the bank |
| Damaged or non-QBO file | No OFXHEADER line, or no closing </OFX> | Download it again |
| Bank not enrolled for Web Connect | The bank offers no .qbo download at all | Use CSV (Online) or IIF (Desktop) |
Why converters cause this so often
A converter turning a PDF into a .qbo has to put something in the INTU.BID tag, and it has no way to know your bank’s number. Tools handle that in one of three ways, and two of them produce this error.
- Leave the tag out. QuickBooks rejects the file outright.
- Guess, or use a generic placeholder. QuickBooks rejects the number, and the failure looks like a problem with your bank rather than with the guess.
- Ask you for it. The only approach that can be right, and the reason a converter asking for a number you have never heard of is a good sign rather than a bad one.
How to check the file yourself
- 1Right-click the .qbo and open it with Notepad (Windows) or TextEdit (Mac).
- 2Check the first line begins OFXHEADER: — anything else means the file is not Web Connect at all.
- 3Search for INTU.BID. Note the digits after it, and the FID and ORG values in the sign-on block just above.
- 4Scroll to the end and confirm the file closes with </OFX>.
- 5Compare the BID with one from a .qbo your bank issued itself. If they differ, that is the error.
Finding your bank’s number
- 1Download a .qbo file directly from your online banking, if the option exists — it may be labelled Web Connect, QuickBooks, or simply .QBO.
- 2Open it in a plain text editor.
- 3Find the line beginning <INTU.BID>. The digits after it are your bank’s ID.
- 4Keep it. It rarely changes, and this is the only awkward step.
If your bank offers no Web Connect download at all, there is no number to find, and that is genuinely the "unsupported institution" case the message describes. It is common outside the US, and banks do withdraw support: Bank of America, for example, ended its OFX-based download services, including Quicken Web Connect files, on 30 September 2025, which is a reminder to check what your bank offers today rather than what it offered when the account was set up.
Fixes inside QuickBooks Desktop
If the file’s BID is right and the message persists, the remaining causes are on the QuickBooks side.
- 1Update QuickBooks (Help → Update QuickBooks Desktop) so its institution list is current, then restart.
- 2Check your version. Each Desktop release loses online services about three years after launch, on 31 May — Desktop 2023 lost them after 31 May 2026 — and imports on retired versions commonly fail with this message.
- 3If you use the Advanced bank feeds mode, try switching to Classic: Banking → Bank Feeds → Change Bank Feeds Mode → Classic (Register) Mode, then import again. Community answers report this helping.
- 4If the account is already connected to a bank feed, Deactivate All Online Services on it (Edit Account → Bank Feed Settings), back up, and import with File → Utilities → Import → Web Connect Files.
The three ways out
- Supply the real BID and re-import. Best outcome: you keep Web Connect’s transaction IDs and the duplicate protection that comes with them.
- Use CSV instead, in QuickBooks Online. It takes a three- or four-column CSV with no bank ID at all, up to 350 KB and 1,000 transactions per file. You lose ID-based duplicate matching, so import each period exactly once. Online now also accepts English-language PDF or image statements under Bank transactions → Link account → Upload from file.
- Use IIF, on Desktop only. It writes straight into the register and needs no institution at all — which also means no duplicate detection, so the same caution applies.
What not to do
Do not use a BID belonging to a different bank because it happens to be accepted. The workaround circulates widely — usually as "change the number to 3000" or another big bank’s ID — and QuickBooks will take the file. The account is then associated with an institution that is not yours. What follows is a bank feed that behaves strangely for reasons nobody will connect back to this decision months later.
QBO and QFX have separate identifiers
A bank enrolled for both QuickBooks and Quicken usually has two different Intuit IDs — one for each product. Taking the number out of a QFX file and putting it in a QBO produces a valid-looking file that QuickBooks refuses, and the message is this one.
Read the BID out of a file of the same kind as the one you are building. If you only have a QFX and you need a QBO, the number in it is not the number you want.
What to actually ask your bank
Bank support staff generally do not recognise "INTU.BID". They do recognise the product names, so ask in those terms:
- "Do you support Web Connect for QuickBooks?" — if no, there is no ID and QBO is not available for this bank at all.
- "Can I download my statement in .QBO format from online banking?" — this is the same question in the words the website uses.
- "What is your Intuit Financial Institution ID?" — the business banking team sometimes knows this outright.
If all three draw a blank, treat the bank as unsupported for Web Connect and move to CSV or IIF. That is a real answer, not a failure to find the right person.
After you fix it
The first successful import associates the QuickBooks account with that institution. From then on, files carrying a different BID will be refused for this account even if they are otherwise valid — which is correct behaviour, and worth knowing before you wonder why a second bank’s file will not go in.
One account, one institution. Separate accounts for separate banks, always.