QuickBooks error OL-301 is a reply from the bank's Direct Connect server during a QuickBooks Desktop download. It usually means your Desktop version is discontinued, or the bank's server returned a fault that its own IT staff must fix. Check your version first. If it is supported, import a Web Connect file from the bank while the bank investigates.
What QuickBooks error OL-301 says about the Direct Connect download
Error OL-301 comes from the server your bank runs for Direct Connect, the QuickBooks Desktop feature that downloads transactions straight from the bank. Intuit's support notes for financial institution partners describe it as a message from the OFX Direct Connect server, so the failure happens at the point where Desktop and the bank talk.
That matters for where you look. The error is not a problem with your company file, your chart of accounts or a file you imported. It appears when you press Send/Receive or update a connected account, and the bank's server sends back something Desktop cannot finish with.
Direct Connect and Web Connect
QuickBooks Desktop has two ways to bring bank transactions in. Intuit's page on downloading bank feed transactions in QuickBooks Desktop puts it simply: Direct Connect links your bank automatically, while Web Connect lets you import transactions from your bank's website. OL-301 belongs to Direct Connect. Web Connect uses a file you download yourself, which is why it is the fallback later in this post.
Two causes Intuit names
Intuit's partner notes list two reasons for OL-301:
- The QuickBooks Desktop version, Windows or Mac, is discontinued.
- The Direct Connect server returned "Error 2000", which the bank's IT staff have to investigate.
The first one you can check yourself in a minute. The second one only the bank can fix, but you can make the call faster and keep your books moving while you wait.
Is a discontinued QuickBooks Desktop version behind error OL-301?
A discontinued Desktop version is the cause to rule out first, because no bank-side fix will help. Intuit's QuickBooks Desktop service discontinuation policy says that once a version is discontinued, you can no longer download transactions or send online payments and transfers.
The same policy gives the current cutoff: QuickBooks Desktop 2023 is discontinued after May 31, 2026. If your company file opens in Desktop 2023 or earlier, OL-301 on a Direct Connect download is the expected result, not a fault.
How to check your version
Open QuickBooks Desktop and press F2. The Product Information window shows the product name and year at the top. Compare the year with Intuit's discontinuation page, because the cutoff moves forward each year.
What a discontinued version means for your options
Intuit's policy also says that uploading transactions is discontinued along with online banking. In practice, an unsupported version cannot be fixed with a setting change. Your choices are:
- Upgrade Desktop to a supported release, then set up Direct Connect again.
- Enter transactions by hand in the old version, which is workable for a low-volume account.
- Move the books to a supported product if you were planning to anyway.
Do not spend time disconnecting and reconnecting the account on a discontinued version. It cannot reconnect a service that has been switched off for that release.
OL-301 replies that start at the bank's OFX server
If your Desktop version is supported and OL-301 still appears, the fault is almost certainly at the bank. Intuit's partner notes say that when the Direct Connect server returns Error 2000, the financial institution's IT staff must investigate. You cannot repair a bank's server from your desk, but you can give the bank enough detail to act.
What to tell the bank
Call or message the bank's business or online banking support, not the general customer line, and ask for the team that handles QuickBooks Direct Connect. Have these ready:
- The full message, including the code OL-301.
- The account the error appears on, and whether other accounts at the same bank download normally.
- The date and time of your last successful download.
- Your Desktop product and year, from the F2 window.
A decision table for what you see
The table below sorts what you see into a likely cause and a next step. The examples are illustrative.
| What you see | Likely cause | Next step |
|---|---|---|
| OL-301 on every account, Desktop 2023 or earlier | Version discontinued | Upgrade, or enter by hand |
| OL-301 on every account at one bank, supported version | Bank's Direct Connect server | Contact the bank, use Web Connect meanwhile |
| OL-301 on one account only, others at the bank work | Account set up differently at the bank | Ask the bank whether that account still has Direct Connect enabled |
| A different OL code | A different fault | See the next section |
The third row is a judgment call. Banks sometimes change which accounts carry Direct Connect access, for example after converting an account to a new product. The bank is the only one who can confirm that.
Telling OL-301 apart from OL-222 and OL-393
OL errors look alike, but each one points to a different failure, so check the number before you follow a fix written for another. OL-301 is a reply from the bank's server. Other OL codes come from different points in the same download, and their fixes differ.
OL-222 appears when Desktop cannot finish a bank download. The post on QuickBooks error OL-222 and how to fix the bank download covers its causes in order and how to import a file in the meantime.
OL-393 is tied to the online bill payment side of Direct Connect. Intuit's partner notes say bill payments usually prompt OL-393, for example when payees are out of sync, and that a closed account included in the download request can also cause it. The guide to QuickBooks error OL-393 and what to check first walks through deactivating and reactivating the account.
A quick way to tell them apart is to look at what you were doing. If you were sending a bill payment, think OL-393 first. If you were only downloading transactions on a supported version, OL-301 points at the bank.
Can a Web Connect file get around error OL-301?
Yes, when the cause is the bank's Direct Connect server. Web Connect does not use that server at all. You sign in to the bank's website, download a QBO file for the dates you need, and import it into Desktop. Intuit's Desktop download page notes that Web Connect only works with .qbo files.
Steps to bring in a Web Connect file
Here is an example for a business that last downloaded on March 3 and hit OL-301 on March 10:
- Back up the company file first. Intuit's Desktop download page advises a backup before you start downloading.
- Sign in to the bank's website and find its download or export option.
- Choose the QuickBooks Web Connect or QBO format. A file called QFX or OFX is a Quicken or generic file and may not open.
- Set the date range from March 4 to March 10, the day after the last good download through today.
- In Desktop, go to File > Utilities > Import > Web Connect Files and pick the downloaded file.
- When asked, link it to the existing bank account in QuickBooks. Do not create a new one.
- Review the downloaded transactions in the Bank Feeds center and add or match them.
When the bank only offers a PDF
Some banks offer QBO files only to certain account types, or not at all. Business treasury accounts sometimes come with a cash management file such as BAI2 instead. The guide to the BAI2 file format for business bank files explains how to turn one into a file QuickBooks reads. If all you can get is a PDF statement, it can be converted to a QBO file. SimpleBankConvert is being built to do that, and accounts are not open yet, so the SimpleBankConvert homepage explains what it will produce.
When the Web Connect route around OL-301 backfires
The Web Connect fallback helps only when the Desktop version is supported and the fault sits at the bank. On a discontinued version, Intuit's policy says transaction uploads stop too, so a Web Connect file is not a way around an expired product. Overlapping date ranges cause the other common failure.
Duplicates when Direct Connect comes back
The usual mistake is overlap. Suppose you import a Web Connect file for March 4 to March 10, and the bank fixes its server on March 12. The next Direct Connect download may try to bring in the same days. Intuit's Desktop download page says you can't download transactions into the same company file more than once, so Desktop may skip lines it believes it already has, or you may end up matching the same deposit twice by hand. Before the first Direct Connect download after the fix, note the last date you imported by file, and compare the incoming lines against the register.
Files from the wrong account
Banks with several accounts sometimes export a Web Connect file for a different account than you meant. If Desktop asks you to link the file to an account and the suggested name looks wrong, cancel. Linking a savings file to checking puts every line in the wrong register.
Using Web Connect as a permanent replacement
Some banks take weeks to fix a Direct Connect fault, and some never do. Running on Web Connect files every week is fine, but pick a fixed day and a fixed date range rule, such as "the day after the last import through yesterday". Gaps and overlaps come from ad-hoc ranges, not from the file format.