Resolving QuickBooks Bank Feeds Errors OL-301 and OL-393
QuickBooks Desktop users encountering Bank Feeds errors OL-301 or OL-393 can resolve connection failures by refreshing account links, updating software, or repairing file damage.
QuickBooks Desktop users relying on Bank Feeds to download transactions sometimes run into connection failures flagged as Error OL-301 or Error OL-393. These codes appear when QuickBooks cannot complete an online-banking session — and because the underlying cause can sit in several different places, resolving the issue requires a process of elimination rather than a single fix.
Where the Problem Originates
The accepted community guidance identifies three possible sources for OL-301 and OL-393. The first is the bank’s own online-banking infrastructure. A temporary outage on the financial institution’s side, or a change to the way that bank routes its QuickBooks connections, will block the download before QuickBooks can do anything about it. The second is the Bank Feeds configuration inside QuickBooks itself — stale or corrupted connection data tied to a specific account. The third, and most serious, is structural damage within the company file that interferes with the routines QuickBooks uses to communicate with the bank.
Start With the Bank
The recommended diagnostic path works from the outside in. Before changing anything inside QuickBooks, check whether your bank is experiencing a known online-banking disruption or has recently switched connection methods. A bank-side change is one of the more frequent triggers for these errors, and if the bank is the culprit, no amount of troubleshooting inside QuickBooks will restore the feed until the bank resolves the issue on its end.
Update QuickBooks
Make sure QuickBooks Desktop is running the latest release. Intuit issues maintenance updates that often include refreshed bank-connection parameters, and running an older release can cause a previously working feed to fail. Updating is a quick step that eliminates version-related incompatibilities before you move on to deeper troubleshooting.
Deactivate and Reactivate Bank Feeds
If the bank’s service is operating normally and QuickBooks is current, the next step targets the connection data stored inside the program. Deactivate Bank Feeds for the affected account, then set the feed up again from scratch. This clears out stale online-banking information and forces QuickBooks to establish a fresh handshake with the financial institution. Community reports indicate this single step clears a large share of OL-301 and OL-393 cases.
When multiple accounts are involved, test the reactivation on a single account first. If that account connects successfully, apply the same process to the remaining accounts. If it still fails, the problem is likely not isolated to one account’s setup.
Check the Company File for Damage
When the error persists across every account and the preceding steps have not helped, the company file itself becomes the primary suspect. Structural damage within the file can disrupt the data structures that Bank Feeds relies on, producing connection errors that look identical to a setup or bank-side problem.
The standard diagnostic sequence is to run QuickBooks File Doctor, followed by the Verify Data and Rebuild Data utilities. Verify will scan the file and report any structural problems it finds; Rebuild attempts to repair them automatically. If Verify reports damage that Rebuild cannot fully correct, the file may need deeper attention. In those situations, a professional QuickBooks file-repair service can address the underlying damage directly, after which online banking typically reconnects without further intervention.
A Note on Isolating the Cause
The key to resolving OL-301 and OL-393 efficiently is narrowing down which of the three sources is responsible. If only one bank or one account is affected, the problem is more likely on the bank side or in that account’s feed setup. If every account fails regardless of bank, the company file becomes the more probable cause. Working through the steps in order — bank check, software update, feed reactivation, file repair — avoids unnecessary changes and gets Bank Feeds back online with the least disruption.