"This file is not from a QuickBooks-supported financial institution" — what it means

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.

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.

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.

Finding your bank’s number

1. 1Download a .qbo file directly from your online banking, if the option exists — it may be labelled Web Connect, QuickBooks, or simply .QBO.
2. 2Open it in a plain text editor.
3. 3Find the line beginning <INTU.BID>. The digits after it are your bank’s ID.
4. 4Keep it. It does not change, 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.

The three ways out

• Supply the real BID and re-import. Best outcome: you keep the banking feed and its duplicate detection.
• Use CSV instead. QuickBooks Online imports a three-column CSV with no bank ID at all. You lose duplicate matching, so import each period exactly once.
• 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. QuickBooks will take the file, and the account will be 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.