QuickBooks error OL-301: what causes it, and how to fix it

What OL-301 actually means

The OL- prefix marks an Online Banking error, and QuickBooks uses that family for anything that goes wrong while it is talking to — or reading a file from — a financial institution. That framing is the problem: the message assumes a live connection, and the error fires just as readily when you are importing a file by hand with no connection involved at all.

In practice, OL-301 means QuickBooks read the file, and something inside it did not match what QuickBooks expected of a Web Connect file from that institution. Nine times in ten, the something is the INTU.BID tag.

The four causes, in order of likelihood

• The INTU.BID is wrong, or missing. Overwhelmingly the most common cause when the file came from a converter rather than from the bank.
• The BID is valid but belongs to a different institution than the account in QuickBooks is set up for. QuickBooks refuses to mix them.
• The file is structurally malformed — a truncated download, or an editor that saved it with the wrong line endings or encoding.
• The account in QuickBooks is set up for a different connection method than the file implies, most often after a bank migration changed the institution behind an existing account.

Fix 1: get the right bank ID

The reliable source for your bank’s INTU.BID is a .qbo file the bank itself issued. If you have ever downloaded one from your online banking, open it in a plain text editor — Notepad, TextEdit, anything that will not reformat it — and look for a line near the top:

<INTU.BID>01234

That number is what any file you import for that account has to carry. Do not use a BID you found in a forum post for a bank with a similar name — banks that merged, or that operate under several brands, frequently have separate IDs, and a plausible-looking wrong number produces the same OL-301 as an obviously wrong one.

If you have never downloaded a .qbo from the bank, ask them. The support line for business banking will usually know what Web Connect is; the retail line often will not.

Fix 2: check the file is intact

A .qbo file is text. Open it and confirm three things before blaming the BID.

1. 1The first line begins OFXHEADER: — if the file starts with anything else, it is not a Web Connect file, whatever its extension says.
2. 2The file ends with a closing </OFX> tag. A download interrupted partway through will not, and QuickBooks reports the result as OL-301 rather than as a truncated file.
3. 3There is no stray content at the top. Some banks serve the file through a portal that prepends an HTML error page when the session has expired; the extension is still .qbo and the contents are a web page.

Fix 3: match the account, not just the file

If the BID is right and the file is intact, the mismatch may be at the QuickBooks end. An account set up against one institution will not accept a file carrying another’s ID, and QuickBooks does not tell you that is what happened.

1. 1Open the Chart of Accounts and find the bank account you are importing into.
2. 2Deactivate its online banking setup — in Desktop, Edit Account → Bank Feed Settings → Deactivate All Online Services.
3. 3Import the file again. QuickBooks will ask which account it belongs to rather than assuming.

When to stop fighting it and use another format

If your bank is not enrolled in Web Connect at all, there is no valid BID to find, and no amount of troubleshooting will produce one. That is common outside the United States, and it is the point at which QBO stops being the right format.

QuickBooks Online will import a three-column CSV without any bank ID. You lose the banking feed’s duplicate detection, which is a real loss — but a working import without duplicate detection beats an import that never happens. QuickBooks Desktop will take IIF, which writes into the register directly and needs no BID either.

How to not see it again

• Save your bank’s INTU.BID somewhere you will find it. It does not change, and looking it up once is the whole of the problem.
• Keep one bank-issued .qbo file as a reference, even after you have imported it.
• When a converter asks for the BID rather than guessing one, give it the real number. A tool that guesses is a tool that produces this error silently.