Almost every QBO import failure comes down to one line in the file that most people have never heard of, and that no error message ever mentions by name.
What the tag is
INTU.BID is a numeric identifier for a financial institution, assigned by Intuit to institutions that have signed up for Web Connect or Direct Connect. It is usually expanded as Intuit Bank ID; Intuit’s own partner documentation calls it a Branding ID. Either way it means the same thing: this file came from an institution Intuit has an arrangement with. It appears near the top of every .qbo and .qfx file, inside the sign-on response.
<SIGNONMSGSRSV1>
<SONRS>
<STATUS><CODE>0<SEVERITY>INFO</STATUS>
<DTSERVER>20260401120000
<LANGUAGE>ENG
<FI>
<ORG>Example Bank institution name
<FID>10898 OFX institution ID
</FI>
<INTU.BID>10898 Intuit’s ID: the one that is checked
</SONRS>
</SIGNONMSGSRSV1>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 was set up with, and the import fails. Quicken does exactly the same with .qfx files, against its own list.
A converter that asks you for the number rather than inventing one is doing the only correct thing available to it, because there is no way to derive a bank’s ID from a statement.
INTU.BID, FID and BANKID are three different things
A Web Connect file carries several numbers that look like they might identify the bank, and mixing them up is a common way to build a file that fails.
| Tag | What it is | Checked by QuickBooks? |
|---|---|---|
| <INTU.BID> | Intuit’s ID for the institution, from its Web Connect list | Yes, this is the check |
| <FID> inside <FI> | The institution ID in standard OFX; often the same digits as INTU.BID, not always | Not as the gate |
| <ORG> inside <FI> | The institution’s name or short code | Displayed, not validated |
| <BANKID> inside <BANKACCTFROM> | Routing number or sort code for the account | No |
| <ACCTID> | Your account number | Used to link the file to an account |
The routing number printed on your cheques is a BANKID, not an INTU.BID, and pasting it into the INTU.BID tag is one of the more common mistakes in hand-built files. The two are unrelated numbering schemes run by different organisations.
Why the errors never mention it
The failures surface as OL-301, OL-249, “this file is not from a QuickBooks-supported financial institution”, or in Quicken as a message that the financial institution cannot be verified. All of them 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.
| What you see | Likely cause |
|---|---|
| OL-301 or “not from a supported financial institution” | Tag missing, mistyped, or a number Intuit does not list |
| Quicken: unable to verify the financial institution | A QuickBooks ID in a .qfx, or a bank with no Quicken ID |
| The account is missing from the import drop-down in Desktop | The account is already linked to a different institution or connection |
| Imported into a brand-new account instead of yours | The file’s institution or account number does not match the existing link |
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. For Quicken, download a .qfx instead, because the number is often different.
- 2Open it in a plain text editor, such as Notepad or TextEdit in plain-text mode. Do not open it in QuickBooks or a word processor.
- 3Find the line beginning <INTU.BID>. The digits after it are your bank’s ID for that product.
- 4Write it down alongside the product it belongs to. It does not change often, and this is the only awkward step in the whole process.
Do not borrow a number
A BID from a forum post for a bank with a similar name will either be rejected or, worse, accepted, associating your QuickBooks account with an institution that is not yours. Banks that merged or operate several brands frequently have separate IDs, so a plausible-looking wrong number is still a wrong number.
Why a converter cannot work it out
The number is not printed on your statement, is not derivable from your account number or routing 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.
Guessing is worse than it sounds. A tool that writes one hard-coded ID into every file produces files that import for one bank and fail for the rest, or import for everyone under the wrong institution. Neither is visible until something downstream breaks.
When there is no number to find
Plenty of banks are not enrolled in Web Connect at all, particularly outside the United States, along with many smaller credit unions and most card issuers outside North America. For those, no valid QBO can exist and no amount of troubleshooting will produce one.
- QuickBooks Online will import a three- or four-column CSV, or a plain OFX, with no bank ID. Import each period once and check the date range, because the CSV route carries no transaction IDs.
- QuickBooks Desktop will take IIF, which writes into the register directly and needs no institution.
- Quicken will take QIF, subject to the account-type limits of your version.
- Everything that is not Intuit, including Xero, Sage, MYOB, Wave and Zoho Books, reads plain OFX, which has no such tag.
Why the list exists at all
Web Connect is a programme institutions contract into, not a standard anyone may implement. A bank joins, gets an identifier, and its customers can download files that QuickBooks and Quicken 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 something happened to the bank, or to your copy of QuickBooks, rather than to your file.
- The bank left the programme, or moved to a different online banking 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, which is common after an acquisition and easy to miss because the branding does not change.
- Your QuickBooks Desktop version reached the end of its support. Intuit switches off online banking services for discontinued versions, and that includes importing Web Connect files, so a perfectly good .qbo stops importing on the cut-off date.
For the first three, download a fresh .qbo from the bank today and read the number out of that one, rather than reusing what you saved. For the last, the file is fine and the software is the problem: upgrade, or use IIF.