QuickBooks Error OL-393: Fixing Bank Feed Download Failures
Resolve QuickBooks Desktop error OL-393 when bank feeds fail to download. Learn why this OL/OLSU error happens and how to switch to durable Web Connect imp
When your QuickBooks Desktop bank feed download suddenly fails and throws Error OL-393, it usually means your software cannot establish a valid connection with your financial institution. This error is part of the broader OL/OLSU bank-feed family. If you are running an older, discontinued version of QuickBooks, this error is rarely a fluke; it is often a sign that the automated connection method has expired.
Understanding the OL/OLSU Error Family
Errors beginning with "OL" (Online) or "OLSU" relate directly to QuickBooks' ability to communicate with your bank's servers. While OL-393 specifically indicates a connection or authorization failure, nearby codes like OL-301, OL-332, or OLSU-1013 generally stem from similar root causes. If you are seeing any of these codes during a bank feed update, the underlying breakdown is almost always tied to how QuickBooks is trying to pull the data.
Common Causes of OL-393
For desktop installations—especially those running beyond their sunsetting date—the causes are predictable:
- Expired Direct Connect: Intuit relies on specific server protocols to facilitate Direct Connect downloads. When a version loses support, these server-side connections are eventually severed.
- Stale Account Credentials: Your bank may have updated its security requirements, requiring you to reauthorize the connection from your bank's website portal.
- Server-Side Maintenance: Your financial institution might be experiencing temporary downtime.
- Company File Data Damage: In rarer cases, the banking configuration inside your
.qbwcompany file has become corrupted.
How to Fix Error OL-393
Follow these steps to restore your banking downloads without needing to upgrade or replace your software.
- Verify Your Bank's Status: Log in to your bank's website through a web browser. If the website is down for maintenance, QuickBooks cannot connect either. Wait and try again later.
- Update Your Account Information: While logged into your bank's website, check for any alerts, new messages, or prompts to accept updated terms of service. Clear these, as they can block automated downloads.
- Deactivate and Reactivate Feeds: In QuickBooks, go to your Chart of Accounts, right-click the affected bank account, and select Edit Account. Under the Bank Feed Settings tab, choose Deactivate All. Then, attempt to set up the bank feed again.
- Switch to Web Connect (.QBO): Direct Connect eventually ends for discontinued software. The durable, permanent fix is to bypass Intuit's servers entirely. Log into your bank, download your transactions as a
.QBOfile, and import them directly via the File > Utilities > Import > Web Connect Files menu.
Preventing Future Bank Feed Errors
The most reliable way to keep an aging QuickBooks Desktop installation fully functional is to stop relying on Direct Connect. By making manual Web Connect and CSV/IIF imports your standard workflow, you sever your dependence on Intuit's active server support. You control exactly when and how your transactions enter the file, ensuring your software remains useful for years to come.
When the Company File Is Damaged
If you have switched to manual Web Connect imports and QuickBooks still refuses to process the .QBO file—or throws OL-393 the moment you touch the bank feed settings—the problem is no longer the bank connection. The financial institution data within your company file is likely damaged. When this happens, the file's internal structure needs to be repaired to clear the corrupted banking protocols.