OL 301 QuickBooks Error: Fix the Bank Feed or Import QBO

OL-301 in QuickBooks Desktop means your bank's server answered the Bank Feeds request with an error instead of transactions. Usually something changed on the account: a new login or account number, a service the bank has not switched on, a notice waiting on the bank's website, or an old account still set up for online banking. Reset the connection and it normally clears. Until it does, you can import the transactions from a .qbo file, which does not use the connection at all.

Intuit files OL-301 together with OL-393 in one help article, and the fixes overlap. The reported wording of the message is close to this: "Your financial institution sent an error message. It might be because your account info changed or they haven't turned on a service, like online bill pay." Note what that sentence says. The bank sent the error, not QuickBooks. That shapes which fixes are worth your time.

OL-301 or OL-301-A?

Check the exact code first, because the search results mix two products. OL-301 with no letter is a QuickBooks Desktop Bank Feeds error. OL-301-A (and OL-393-A) come from Quicken, which uses the same OL numbering for its own connection errors. If you see the letter, you are in Quicken, and the Quicken route for statements is a QFX file; a tool built for converting bank statements for Quicken fits that case better than anything below. The rest of this guide is about QuickBooks Desktop, including Enterprise.

What causes QuickBooks error OL-301?

The causes quoted in Intuit threads and by the accountants who write about this code fall into two groups.

How do I fix error OL-301 in QuickBooks Desktop?

Back up the company file and sign in as Admin in single-user mode. Work down the list and stop when the download succeeds.

1. Sign in on the bank's website

This takes two minutes and solves more OL-301 cases than any QuickBooks setting. Sign in with the same credentials QuickBooks uses, accept any new terms, answer any identity check, and look for a setting that lists linked financial software or Direct Connect. Some banks require you to enable QuickBooks access separately, and some charge a monthly fee for Direct Connect on business accounts. If the bank's site shows nothing unusual, move on.

2. Run the test company check

Create a sample company with Express Start, add the same bank account through Bank Feeds, and try a download. This one test tells you whose problem it is. If the test company also fails, the problem is at the bank, and you need to call them with your Bank Feeds logs. If the test company connects, the problem is inside your company file, so continue with steps 3 to 5.

3. Deactivate and reactivate the account's online services

Open the Chart of Accounts, right-click the failing account, choose Edit Account, open Bank Feed Settings, and select Deactivate all online services. Save, then set the account up again from Banking, Bank Feeds, Set Up Bank Feed for an Account. You can reconnect with Direct Connect, or pick Web Connect and download .qbo files from the bank instead. Transactions already in the register stay where they are.

4. Switch off online banking on inactive accounts

In the Chart of Accounts, tick Include inactive. For every inactive bank or card account, edit it and deactivate its online services. A closed card that still has Direct Connect switched on can throw OL-301 for the whole bank session.

5. Repair the company file

If the test company works and steps 3 and 4 did not help, run File Doctor from the QuickBooks Tool Hub. Then repeat step 3.

6. Check your version is still supported

Open Help, About QuickBooks. Intuit supports each Desktop year for about three years; after the cut-off, Intuit turns off online banking for that version and no reset brings it back. Desktop 2023 reached that cut-off in 2026. If your version is past its date, skip ahead to the import section. Our page on discontinued QuickBooks Desktop versions lists what stops and what keeps working.

Can I import bank transactions while OL-301 is unresolved?

Yes. OL-301 blocks the live Direct Connect session, not file imports. A Web Connect file imported through File, Utilities, Import, Web Connect Files goes into the existing account with the same review screen as a download. When the connection returns, set the first download to start after the last imported date, or match any overlap in For review, and nothing is entered twice.

There are three places the file can come from:

• The bank's own QuickBooks download, when its website offers one for the months you need. Chase, for example, offers card activity as a .qbo file for about two years.
• The PDF statements, which every bank keeps and which reach further back than any download. Convert the PDF bank statement to a QuickBooks Desktop file, check the total against the statement balance, and import it the same afternoon.
• An IIF file, for a Desktop version where Web Connect has stopped as well. IIF is a local import that does not call any Intuit service.

For a credit card, the file has to declare a credit card account with purchases as charges. A file written as checking turns every purchase into a deposit, and you find out at reconciliation. The Chase credit card statement to QuickBooks converter and our other card pages write card accounts correctly, which matters because card feeds are where OL-301 shows up most after a card is replaced.

OL-301 compared with the codes around it

What does OL-301 cost you if you wait?

Bank-side OL-301 cases can take days or weeks, because the bank and Intuit each have to confirm the other's side. Meanwhile month-end still arrives. A business checking account with 100 transactions a month takes about an hour to key and check by hand. Converting the statement and importing it takes a few minutes plus a balance check, and the imported lines match cleanly against anything the feed brings down later.

On the Starter plan here, $49 a month covers 50 statements. For a firm with a few clients stuck on one bank, that is less than a single afternoon of data entry, and it removes the deadline pressure while the bank sorts out its side. If several banks are failing at once, the bank feed not working page covers closing the whole month from statements.

Frequently asked questions

What does "Your financial institution sent an error message" mean in QuickBooks?

It is the message reported with OL-301 and OL-393. The bank's server rejected the Bank Feeds request, usually because account details changed, a service is not activated, or a notice is waiting on the bank's website. Sign in at the bank first, then reset the account's online services in QuickBooks.

Is OL-301 a QuickBooks Online error?

No. OL-301 is a QuickBooks Desktop Bank Feeds code, including Enterprise. QuickBooks Online shows its own connection messages. The Online equivalent of the workaround is Transactions, Bank transactions, Link account, Upload from file, which accepts a .qbo file.

Why do I get OL-301 for only one bank?

Because the error comes from that bank's server. Other banks use their own connections, so they keep working. Run the test company check: if it fails there too, call the bank with your Bank Feeds logs and import a file for the gap.

Will importing a .qbo file duplicate transactions when the feed comes back?

It can, so check the first download. QuickBooks skips a line automatically only when its transaction ID matches one already imported, and the bank's IDs differ from those in a file converted from a statement. Start the feed after the last imported date, or match any line that appears twice in For review instead of adding it.

Does OL-301 affect credit card accounts?

Yes, and often right after the bank issues a new card number. Edit the account, deactivate online services, and set it up again with the new number. For the months in between, import the card statements as a credit card file so purchases post as charges.