What is INTU.BID, and why does QuickBooks check it?

What the tag is

INTU.BID stands for Intuit Bank ID. It is a numeric identifier for a financial institution, assigned by Intuit to banks participating in Web Connect, and it appears near the top of every .qbo and .qfx file.

<INTU.BID>01234

On import, QuickBooks reads that number and looks it up. Present and recognised, the file proceeds. Absent, unrecognised, or belonging to a different institution than the account expects, and the import fails.

Why the errors never mention it

The failures surface as OL-301, OL-249, or "this file is not from a QuickBooks-supported financial institution". All three describe a connection or a supported-bank problem, and none names the tag. So people phone their bank, where support has no idea what is being asked, and the actual cause — five digits in a text file — goes unmentioned for the length of the call.

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 — anything that will not reformat it.
3. 3Find the line beginning <INTU.BID>. The digits after it are your bank’s ID.
4. 4Write it down. It does not change, and this is the only awkward step in the whole process.

Why a converter cannot work it out

The number is not printed on your statement, is not derivable from your account number, and is not published as a list anywhere reliable. A converter turning a PDF into a QBO has three options: leave the tag out, guess, or ask you. The first two produce exactly the errors above, which is why being asked for a number you have never heard of is a good sign rather than a bad one.

When there is no number to find

Plenty of banks are not enrolled in Web Connect at all, particularly outside the United States. For those, no valid QBO can exist and no amount of troubleshooting will produce one.

• QuickBooks Online will import a three-column CSV with no bank ID. You lose duplicate detection, so import each period exactly once.
• QuickBooks Desktop will take IIF, which writes into the register directly and needs no institution.
• Everything that is not QuickBooks — Xero, Sage, MYOB, Wave — reads plain OFX, which has no such tag.

Why the list exists at all

Web Connect is a programme banks participate in, not a standard anyone may implement. A bank joins, gets an identifier, and its customers can download files that QuickBooks will accept. The tag is how Intuit tells a participating institution’s file from anyone else’s.

That explains the behaviour that otherwise makes no sense. The transactions in a rejected file are perfectly readable and QuickBooks refuses them anyway; the same data in a plain OFX imports into Xero without a murmur. Nothing technical is missing — the file simply cannot prove it came from a participant.

It also explains why the identifier changes hands. Banks join and leave, merge, and rebrand, and the number follows the arrangement rather than the brand on your card.

When a number that worked stops working

A BID that imported fine last year and fails now usually means one of three things happened to the bank rather than to your file.

• It left the programme, or moved to a different aggregation provider, and the old identifier retired with the arrangement.
• It merged. The surviving institution has its own identifier, and statements from either side of the merger may now need different ones.
• Your account itself migrated to a new institution within a group — common after an acquisition, and easy to miss because the branding does not change.

In all three cases the fix is the same: download a fresh .qbo from the bank today and read the number out of that one, rather than reusing what you saved.