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

What OL-301 actually means

OL-301 is a QuickBooks Desktop Bank Feeds error. The OL- prefix marks the online banking family, and Intuit’s own troubleshooting article groups OL-301 with OL-332, OL-334, OL-392 and OL-393, putting them down to communication problems between QuickBooks and the bank, or to a problem in the company file. QuickBooks Online does not use OL- codes; if you are in Online, skip to the section on it below.

The message assumes a live connection, but it fires just as readily when you import a Web Connect (.qbo) file by hand with no connection involved. In that case it means QuickBooks read the file and something inside it did not match what QuickBooks expected of a file from that institution — most often the INTU.BID tag, sometimes the account the file is being pushed into.

First: were you downloading or importing?

The same code covers two different situations, and the first five minutes go better if you know which one you are in.

The 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.
• An account — often an inactive one you have forgotten about — still has online banking switched on and is confusing the connection. Intuit lists this one explicitly.
• The bank changed how it connects (Direct Connect to Web Connect, or the reverse), or has a pending security notice you have to acknowledge on its website before anything else will work.
• The file is structurally malformed — a truncated download, or an editor that saved it with the wrong line endings or encoding.
• QuickBooks itself is out of date: an old release, TLS 1.2 switched off in Windows Internet Options, or a Desktop version past its support date.

How to confirm the cause in two minutes

A .qbo file is plain text. Right-click it, choose Open with, and pick Notepad (Windows) or TextEdit (Mac) — anything that will not reformat it. You are looking for a handful of tags near the top and one at the bottom:

OFXHEADER:100
<ORG>Your Bank<FID>1234
<INTU.BID>01234
<ACCTID>000123456789
<ACCTTYPE>CHECKING
...
</OFX>

1. 1The first line begins OFXHEADER: — if it does not, this is not a Web Connect file, whatever its extension says.
2. 2INTU.BID is present and is a number. Missing, empty, or a value like 00000 points straight at Fix 1.
3. 3ACCTID is the account number the file claims. Compare it with the number stored on the QuickBooks account.
4. 4ACCTTYPE says CHECKING, SAVINGS or CREDITLINE, or the file uses a credit-card block instead of a bank one. It has to agree with the account type in your chart of accounts.
5. 5The last line is </OFX>. If the file stops mid-transaction, the download was interrupted.

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 and read the number after the tag:

<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

If the bank ID looks right, make sure the file is what it claims to be before you touch anything in QuickBooks.

1. 1Confirm the extension is .qbo. Intuit is explicit that Desktop only opens downloaded transactions in that format; a .qfx or .ofx renamed to .qbo usually carries the wrong ID for QuickBooks.
2. 2Confirm the 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. 3Look for stray content at the top. Some banks serve the file through a portal that returns an HTML error page when the session has expired; the extension is still .qbo and the contents are a web page.
4. 4Download it again rather than editing it. A fresh file from the bank rules out a damaged copy in one step.

Fix 3: reset the account’s bank feed (Desktop)

If the BID is right and the file is intact, the mismatch is probably at the QuickBooks end. An account set up against one institution will not accept a file carrying another’s ID, and an inactive account with online banking still switched on can upset the connection for the others. These steps follow Intuit’s own article:

1. 1Back up the company file (File → Back Up Company → Create Local Backup).
2. 2Open the Chart of Accounts (Lists → Chart of Accounts) and tick Include Inactive at the bottom.
3. 3Look for any account with a lightning-bolt icon, which means online services are on. Deal with inactive accounts first.
4. 4For each one, select it, open Edit Account → Bank Feed Settings → Deactivate All Online Services, and confirm.
5. 5Close and reopen the company file, then import again with File → Utilities → Import → Web Connect Files. Choose Use an existing QuickBooks account and pick the right one when asked.

Fix 4: when it really is the connection

If OL-301 appeared on a Direct Connect download rather than a file import, Intuit’s troubleshooting order is roughly this:

1. 1Sign in to your bank’s website in a browser and clear any security notice, new terms or password prompt waiting for you.
2. 2Update QuickBooks (Help → Update QuickBooks Desktop), then restart it.
3. 3In Windows, open Internet Options → Advanced and make sure Use TLS 1.2 is ticked. Restart the computer.
4. 4Test in a new company file (File → New Company → Express Start), set up Bank Feeds for the same account and download. If it fails there too, the problem is with the bank connection, and only the bank can fix it.
5. 5If it works in the test file, the problem is in your company file — turn the account’s bank feed off and back on, or use Intuit’s create-and-merge procedure on the account.

Check your Desktop version before anything else

Intuit retires connected services for each QuickBooks Desktop release roughly three years after launch, on 31 May. QuickBooks Desktop 2023, for example, lost bank feeds, payroll and live support after 31 May 2026. A discontinued version still opens your company file, but online banking stops, and users on retired versions commonly report Web Connect imports failing with OL- errors or the "unable to verify" message. If you are on a retired release, no amount of work on the file will help; IIF import, which writes to the register without any bank involvement, is the usual workaround.

If you are using QuickBooks Online

QuickBooks Online does not show OL-301. A bad Web Connect file there produces messages such as "The uploaded file isn’t a valid Web Connect file". The upload lives under Bank transactions → Link account → Upload from file, and Intuit’s current limits are files of 350 KB or less and up to 1,000 transactions per upload, in QBO, QFX or CSV format.

Intuit has also added PDF and image statement uploads in the same place, for English-language statements, with the transactions extracted automatically. That route sidesteps the bank ID entirely. Note that a PDF dropped elsewhere in QuickBooks Online — on the general upload area — may be filed as a receipt rather than read as a statement.

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- or four-column CSV without any bank ID. You lose the per-transaction IDs that stop re-imports duplicating, which is a real loss — but a working import 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 rarely changes, 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.
• Turn off online services on an account before you make it inactive, so it cannot interfere later.
• Keep QuickBooks Desktop updated, and note the date your version loses online services.