LedgerBridge

What Is INTU.BID and How to Find Yours

If QuickBooks just told you your bank file is "not recognized" or "cannot be read," there's a good chance the problem is a tiny tag buried near the top of the file: INTU.BID. It's the Intuit Bank Identifier, a small number that tells QuickBooks and Quicken which financial institution a Web Connect (.qbo) or OFX file came from. Get it wrong, leave it blank, or pair it with a mismatched FID, and Intuit's importer refuses the file before it ever looks at your transactions.

This guide explains exactly what INTU.BID is, where it lives inside the OFX 1.0.2 / SGML format, how to find the correct value for your bank, and the step-by-step fix for the most common import failures. If you're starting from a raw bank CSV or Excel export, LedgerBridge can build a properly structured QBO/QFX/OFX file for you in the browser, so you can set the right identifiers without hand-editing SGML.

What INTU.BID actually is (and where it lives in the file)

INTU.BID stands for "Intuit Bank ID." It's a numeric identifier that Intuit assigns to financial institutions participating in the Web Connect / Direct Connect program. When you import a .qbo file, QuickBooks uses INTU.BID (together with the FID and ORG) to decide whether the file came from a recognized institution. If the value doesn't resolve to a known FI, QuickBooks rejects the file rather than importing partial data.

A .qbo file is really an OFX file. QBO files for QuickBooks Desktop use OFX version 1.0.2, which is SGML-based, not XML. That means the file opens with a plain-text header of key:value pairs, followed by SGML tags where leaf elements don't need closing tags. Opening a .qbo in a text editor (rename it to .txt first if needed) shows you exactly what's inside.

A typical OFX 1.0.2 header and sign-on block looks like this:

  • OFXHEADER:100
  • DATA:OFXSGML
  • VERSION:102
  • SECURITY:NONE
  • ENCODING:USASCII
  • CHARSET:1252
  • COMPRESSION:NONE
  • OLDFILEUID:NONE
  • NEWFILEUID:NONE
  • <OFX> ... <SIGNONMSGSRSV1><SONRS> ... <FI><ORG>My Bank</ORG><FID>1234</FID></FI> ... <INTU.BID>1234</INTU.BID> ...

INTU.BID vs FID vs ORG vs BANKID: don't confuse them

These four identifiers are easy to mix up, and mismatches between them are the number-one cause of "file not recognized" errors. Each does a distinct job, and QuickBooks cross-checks them.

Knowing which is which makes troubleshooting far faster. Here's the breakdown of the identifiers you'll see in a QBO/OFX file:

  • INTU.BID - the Intuit-assigned bank ID. This is the value Intuit's importer looks up. It usually matches the FID, but not always.
  • FID - the Financial Institution ID, inside the <FI> block. Combined with ORG, it identifies the institution to OFX clients.
  • ORG - the organization name string inside the <FI> block (e.g., "B1", "Chase", or the bank's OFX org name). It must match what Intuit expects for that FID.
  • BANKID - the bank routing number (ABA number) inside each account's <BANKACCTFROM>. This is your real routing number and is unrelated to INTU.BID.
  • ACCTID - your account number, also in <BANKACCTFROM>. This determines which QuickBooks account the transactions match to.

How to find the correct INTU.BID for your bank

There are three reliable ways to get the right value. Start with whichever matches what you already have on hand.

Method 1 - copy it from a known-good file. If your bank offers Web Connect downloads, log in and download an official .qbo directly from your bank's site. Open it in a text editor and read the INTU.BID, FID, and ORG values. Reuse those exact values in any file you generate yourself. This is the most authoritative source because it's what Intuit already accepts for your institution.

Method 2 - look it up in a public OFX directory. OFX Home (ofxhome.com) is a community-maintained database that lists OFX connection details for thousands of institutions, including the FID and ORG. Search for your bank by name; the FID listed there is almost always the value you want for both FID and INTU.BID. Treat it as a strong starting point and verify against a real download when you can.

Method 3 - contact your bank or check QuickBooks. Some banks publish their FID/INTU.BID in their online-banking help pages, and Intuit's own financial-institution directory (used during the bank-feed setup wizard) lists supported institutions. If your bank isn't in Intuit's list at all, no INTU.BID will work for a Web Connect import, and you'll need to use a converter that produces a generic but well-formed file.

If you don't have a known-good file and lookups are ambiguous, drop your CSV or Excel export into the LedgerBridge converter. It builds a valid OFX 1.0.2 structure and lets you set the INTU.BID, FID, and ORG to the values you confirmed, so you skip the error-prone hand-editing of SGML tags.

Step-by-step: fix a "file not recognized" import error

When QuickBooks Desktop refuses a .qbo file, work through these steps in order. Most failures are fixed by the time you reach step 4.

After correcting the identifiers, import through the standard path. In QuickBooks Desktop, go to File > Utilities > Import > Web Connect Files, browse to your .qbo, and choose either an existing QuickBooks account or create a new one when prompted.

  • Confirm the file is genuinely OFX/QBO: header should read OFXHEADER:100, DATA:OFXSGML, VERSION:102. A wrong VERSION line is a common rejection cause.
  • Check that INTU.BID is present and non-blank, and that it matches the FID (or your bank's known value). A missing or mismatched INTU.BID is the classic trigger for "file not recognized."
  • Verify ORG matches the FID for your institution. An FID with the wrong ORG string will be refused even if the number is correct.
  • Make sure BANKID (routing number) and ACCTID (account number) are filled in and correct so the transactions match the right register.
  • Re-import via File > Utilities > Import > Web Connect Files. If you previously imported the same file, QuickBooks may report transactions as already imported (see FITID below) rather than failing.

FITID and duplicate transactions

Every transaction in an OFX file carries a FITID (Financial Institution Transaction ID), a unique string within an account. QuickBooks and Quicken use FITID to deduplicate: if you import a file containing a FITID it has already seen for that account, it skips the transaction instead of creating a duplicate. This is why re-importing an overlapping date range is usually safe.

Problems appear when FITIDs aren't stable or unique. If a converter regenerates FITIDs each time, or two different transactions share an ID, you can get either duplicate entries or silently dropped transactions. A good converter derives FITID deterministically from transaction data (date, amount, and a sequence or reference) so the same source row always produces the same FITID. LedgerBridge generates stable, unique FITIDs from your CSV, which keeps re-imports clean and avoids both duplicates and skipped rows.

QuickBooks Online vs Desktop: a different import path

The INTU.BID and Web Connect mechanics above are primarily a QuickBooks Desktop story. QuickBooks Online handles uploaded files differently and is generally more forgiving about the INTU.BID value, but it has its own constraints worth knowing before you generate a file.

Keep these QuickBooks Online behaviors in mind when preparing a file:

  • Upload path: in QBO, go to Transactions > Bank transactions, select the account, then Link account / Upload from file, and choose your .qbo, .qfx, .ofx, or .csv.
  • File-size and row limits: QBO restricts how much you can upload at once (commonly cited around a few thousand transactions and a file-size cap). For large histories, split the file by date range into smaller batches.
  • Date range: very old transactions or wide ranges can be trimmed; import recent ranges first and work backward if needed.
  • Account matching: QBO matches uploaded transactions to the selected account, so you don't rely on INTU.BID the way Desktop does. A clean, well-formed OFX/QBO from LedgerBridge imports into both, and you can split large CSVs into compliant batches before uploading.

Convert your CSV now →

Frequently asked questions

Is INTU.BID the same as my bank's routing number?

No. INTU.BID is an Intuit-assigned bank identifier used by QuickBooks/Quicken to recognize the institution. Your routing number is the BANKID field inside the account block (<BANKACCTFROM>). They are unrelated values and serve different purposes, so don't substitute one for the other.

Where exactly is INTU.BID in a .qbo file?

It's in the sign-on section near the top, inside <SIGNONMSGSRSV1><SONRS>, usually right after the <FI><ORG>...</ORG><FID>...</FID></FI> block, written as <INTU.BID>1234</INTU.BID>. Rename the file to .txt (or open it in a code editor) to view it, since .qbo is plain SGML text.

Why does QuickBooks say my file is "not recognized" even though it has transactions?

QuickBooks Desktop validates the file's identity before reading transactions. A missing, blank, or mismatched INTU.BID, an FID that doesn't match its ORG, or a wrong OFX VERSION line will all cause rejection regardless of how good the transaction data is. Fix the header and identifiers first, then re-import.

What happens if I use the wrong INTU.BID?

In QuickBooks Desktop, an unrecognized INTU.BID typically causes the import to fail outright. If the value resolves to a different institution, you may also be prompted to set up the wrong bank feed. Use a value copied from a real download from your bank, or one confirmed via an OFX directory like OFX Home.

Do I need INTU.BID for QuickBooks Online?

QuickBooks Online is more forgiving and matches uploaded files to the account you select, so it usually doesn't reject files over the INTU.BID value the way Desktop does. A well-formed OFX/QBO file still imports more cleanly, and for large histories you should split the file to stay under QBO's per-upload limits.

Can I just edit the INTU.BID by hand?

You can, but OFX 1.0.2 is SGML and a single malformed tag breaks the whole file. It's safer to start from a valid file. If you're converting a bank CSV or Excel export, LedgerBridge builds the correct OFX structure in your browser and lets you set INTU.BID, FID, and ORG, with stable FITIDs so re-imports don't create duplicates.

Related guides

Not affiliated with Intuit/QuickBooks/Quicken/Xero. LedgerBridge is a file-conversion utility, not financial advice.