What INTU.BID actually is
QBO is Intuit's flavor of the OFX file format. Inside every QBO file is a block of tags describing the bank, the account, and the transactions. Two of those tags matter most for import: INTU.BID and INTU.USERID.
INTU.BID stands for Intuit Bank ID. It is a numeric code that identifies the financial institution to Intuit's servers. Every bank that Intuit has onboarded for Web Connect has its own BID. QuickBooks uses it to confirm that the file came from a bank it recognizes.
INTU.USERID is a secondary field tied to your login or account context. It is usually less of a blocker than the BID, but a malformed value can still cause a rejection.
Why QuickBooks rejects the file
When you import a QBO file, QuickBooks Desktop does not just read the transactions. It validates the INTU.BID against a list of institutions it knows about. If the BID is missing, blank, set to a placeholder, or belongs to a bank that is not enabled for your QuickBooks version, you get an error such as unsupported financial institution or an invalid file message.
This trips up converted files most often. When a statement is turned into a QBO from a PDF, the converter has to supply a BID. If it uses a generic or nonexistent number, QuickBooks refuses it. The transactions themselves may be perfectly formatted, but the gatekeeper check fails first.
This is a QuickBooks Desktop behavior. QuickBooks Online does not accept QBO Web Connect files at all for manual upload in the same way, so if you are on QBO you should use CSV instead.
How to fix an unsupported bank error
The most reliable fix is to use a valid INTU.BID that matches your actual bank. If you have ever downloaded a real Web Connect file directly from your bank, open it in a plain text editor and note the INTU.BID value. You can reuse that same number in your converted file so QuickBooks recognizes the institution.
If you cannot find your bank's BID, a common workaround is to import as CSV instead of QBO. QuickBooks Desktop supports CSV import for bank transactions with a mapping step for date, description, and amount. This bypasses the INTU.BID check entirely. QuickBooks Online also supports CSV upload under the banking or transactions area, so CSV is the safer route there.
If you do edit a QBO file by hand, only change the INTU.BID and INTU.USERID values and leave the transaction tags alone. Save it as plain text with the .qbo extension. A single broken tag or a smart quote from a word processor will invalidate the whole file, so use a basic text editor, not a rich document editor.
Choosing the right format for your setup
If you are on QuickBooks Desktop and want the cleaner reconciliation experience that Web Connect gives, aim for a QBO with a correct INTU.BID for your bank. That keeps matching and duplicate detection working the way Intuit intends.
If you just need the transactions in and do not want to chase down a bank ID, CSV is the pragmatic choice on both Desktop and Online. You lose some automatic matching niceties but gain a format that will not be rejected over a hidden code.
When you convert statements with Statement to Sheets, you can export to CSV for a no-friction import, or to QBO when you need Web Connect. Setting the right INTU.BID for your institution is what makes the difference between a smooth import and the unsupported bank error.