QuickBooks Error OL-393: 5 Ways to Fix Bank Feed Connection Problems in 2026

QuickBooks Error OL-393 can interrupt bank-feed downloads in QuickBooks Desktop, preventing transactions from reaching your company file. The problem may involve your bank's connection service, pending online banking alerts, inactive accounts that remain connected to Bank Feeds, outdated financial institution information, or damaged bank-feed data.

Start by checking your bank's website and looking for inactive QuickBooks accounts that still have online banking enabled. These checks can help identify common causes before you disconnect an account or attempt a company-file repair.

This guide explains how to troubleshoot QuickBooks Error OL-393, refresh a bank-feed connection, test whether the problem is specific to your company file, and protect your accounting records during recovery.

What Is QuickBooks Error OL-393?

QuickBooks Error OL-393 is associated with online banking and Bank Feeds problems in QuickBooks Desktop. It can occur when QuickBooks cannot complete a banking request successfully.

The error does not automatically mean your company file is damaged. A bank-side connection problem, account configuration issue, or local bank-feed problem may be responsible.

Common causes include:

• Pending alerts, security prompts, or updated terms on your bank's website.

• An inactive QuickBooks bank account that still has online banking enabled.

• A bank that has changed its supported connection method.

• Outdated financial institution information in QuickBooks.

• Temporary bank-server or internet connectivity problems.

• Incorrect account configuration or damaged bank-feed data.

The exact cause depends on your setup and the message displayed. Work through the following steps in order, testing the connection after each major change.

Fix 1: Deactivate Bank Feeds for Inactive Accounts

One important check is whether an inactive bank account in QuickBooks still has online banking enabled. A lightning bolt icon beside an inactive account can indicate that Bank Feeds remains configured for it.

How to check inactive accounts

1. Open QuickBooks Desktop and your company file.

2. Select Lists > Chart of Accounts.

3. Enable Include Inactive at the bottom of the window.

4. Review inactive bank accounts for a lightning bolt icon.

5. If you find one, right-click the account and select Edit Account.

6. Open Bank Feed Settings or the equivalent bank settings tab.

7. Select Deactivate All Online Services, then confirm.

8. Select Save & Close.

9. Close and reopen the company file, then retry the active account's download.

Repeat the check for other inactive accounts that still have online banking enabled.

Before disconnecting an account, review any pending downloaded transactions. Match or resolve pending items first where necessary. Deactivating Bank Feeds stops future downloads for that account; it does not repair every possible cause of OL-393.

Fix 2: Check Bank Alerts and Refresh the Connection

Your bank may require you to acknowledge a security notification, confirm updated terms, or complete another online banking step before allowing a transaction download.

Check your bank account

1. Open your bank's official website in a browser.

2. Sign in using your normal secure process.

3. Look for pending alerts, security confirmations, updated terms, or messages about online banking.

4. Complete any required action.

5. Confirm that you can access the relevant account normally.

If the bank reports an outage or a change to its QuickBooks connection service, contact the bank's online banking support team.

Refresh the QuickBooks connection

If the bank account is accessible and no outstanding alerts remain, review the connection settings in QuickBooks.

1. Back up your company file before making changes.

2. Open Banking > Bank Feeds > Bank Feeds Center.

3. Select the affected account and review any pending transactions.

4. If necessary, disconnect its Bank Feeds service using the account settings.

5. Close and reopen QuickBooks.

6. Select Banking > Bank Feeds > Set Up Bank Feeds for an Account.

7. Search for your bank and follow the setup instructions.

In supported QuickBooks Desktop workflows, holding Ctrl while selecting setup buttons can help refresh the bank connection. Follow the prompts carefully and do not hold Ctrl while entering credentials.

If the bank has changed its supported connection method, verify whether it requires Direct Connect or Web Connect. Not every financial institution supports both.

Fix 3: Test Bank Feeds in a New Company File

If OL-393 continues, a test company can help determine whether the issue also occurs outside your primary company file.

This is a diagnostic test, not proof by itself that the bank or the original company file is solely responsible.

1. Back up your main company file.

2. In QuickBooks Desktop, select File > New Company or use the available company-creation workflow.

3. Create a temporary test company.

4. Set up a test bank account and connect it to the same financial institution, if supported.

5. Attempt a bank-feed download.

Review the results:

• The test company also fails: The problem may involve the bank, connection service, credentials, network, or financial institution configuration.

• The test company succeeds: The issue may be specific to the original company's account setup or bank-feed data.

Do not enter unnecessary real financial information into a test company. Use the minimum information required for the diagnostic, and do not confuse test transactions with your live accounting records.

Fix 4: Update Financial Institution Information and Verify Company Data

QuickBooks maintains financial institution information used for supported online banking connections. If the information is outdated or has not refreshed correctly, a connection may fail.

Refresh the financial institution information

Make sure QuickBooks Desktop is updated to the latest release available for your installed product. Then retry the Bank Feeds connection.

QuickBooks may update its Financial Institutions Directory (FiDir) through its bank-feed processes. If the connection still fails, use the supported refresh procedure for your version rather than deleting configuration files manually.

Verify and rebuild company data only when appropriate

If the test-company results point toward the original company file, consider checking its data integrity.

1. Create a current backup.

2. Select File > Utilities > Verify Data.

3. Review the results.

4. If QuickBooks reports data damage, follow its recommended repair procedure.

5. Use Rebuild Data only when appropriate and follow the backup prompts.

6. Retry Bank Feeds and verify that transactions download correctly.

Do not assume that OL-393 always indicates damaged company data. A rebuild is not the first step for a problem that may be caused by a bank connection or an inactive account.

Creating a replacement bank account and merging it with an existing account should also be a later option, not an automatic fix. Account merging can affect accounting history and should be performed only after a backup and careful review of the account records.

Fix 5: Review Bank-Feed Logs and Contact the Bank

If the error persists, bank-feed logs may help identify where the request is failing.

In supported QuickBooks Desktop versions, bank-feed logging can be enabled through Edit > Preferences > Checking > Company Preferences. The exact options can vary by version and mode.

After enabling logging:

1. Reproduce the OL-393 error.

2. Record the date, time, affected account, and exact message.

3. Locate the generated log files using the location appropriate to your QuickBooks version.

4. Review the logs for relevant connection or bank-response details.

5. Contact your bank's online banking support team if the logs point to a bank-side response or connection issue.

Do not share banking passwords, full account numbers, or other sensitive information in an unsecured support request.

If the bank confirms that its connection service is working, the logs and test-company results can help narrow down the next step in QuickBooks.

OL-393 vs. Other QuickBooks Bank-Feed Errors

Error or issue

• QuickBooks Error OL-393

• QuickBooks Error OL-332

• QuickBooks Error OL-301

• QuickBooks Error OL-202

• QuickBooks Error OL-221

• Bank transactions not downloading

• Duplicate bank-feed transactions

• QuickBooks bank reconciliation difference

What to investigate

• Bank-feed connection, account configuration, inactive online accounts, or bank-side response

• Authentication or online banking sign-in problems, depending on the exact message

• Bank connection service, supported product version, and the response from the financial institution

• Review the bank's connection response and the specific message shown

• Investigate the precise bank-feed response and supported connection method

• Check connectivity, credentials, bank alerts, and Bank Feeds setup

• Review downloaded transactions and match them carefully before adding entries

• Compare bank statements, downloaded transactions, and recorded accounting entries

These issues can have overlapping symptoms, but they are not interchangeable. Use the exact error code and message to select the appropriate troubleshooting path.

Frequently Asked Questions

Does QuickBooks Error OL-393 mean my company file is damaged?

No. OL-393 can be caused by bank connectivity, account configuration, or bank-feed data issues. A test company and the available logs can help determine whether the original company file may be involved.

What should I check first for OL-393?

Start by signing in to your bank's website and checking for alerts. Then review inactive QuickBooks accounts for online banking connections that are still enabled.

Why does OL-393 return after I reconnect my bank?

The underlying cause may remain unresolved. Check inactive accounts, pending bank notifications, connection-method changes, and financial institution information before repeatedly disconnecting and reconnecting the same account.

Can I fix OL-393 without rebuilding my company file?

Often, yes. Start with bank alerts, inactive accounts, connection settings, and bank-side service checks. Consider Verify Data and Rebuild Data only when evidence suggests a company-file data issue.

What is the difference between OL-393 and OL-332?

They are different bank-feed error codes. OL-332 is generally associated with authentication or sign-in issues, while OL-393 requires investigation of the banking request and connection response. Use the precise error message to guide troubleshooting.

When should I contact my bank?

Contact the bank if you cannot sign in, see pending security requirements, learn that its online banking service has changed, or encounter the same failure in a separate test company. Ask for support with its QuickBooks-compatible banking connection.

Can I manually import bank transactions while OL-393 is unresolved?

If your bank supports QuickBooks Web Connect, you may be able to download a compatible .QBO file and import it. Back up your company file first, then review existing entries carefully to avoid duplicate transactions.

Conclusion

QuickBooks Error OL-393 can interrupt bank-feed downloads, but it does not automatically indicate company-file damage. Start by checking bank alerts and inactive accounts with online banking enabled. Next, refresh the connection, test with a temporary company if needed, and investigate financial institution information or company data only when the evidence supports it.

After a successful download, review the transactions in the Bank Feeds Center and match them against existing entries before adding them to your books. This helps prevent duplicate records and protects reconciliation accuracy.

Need help troubleshooting QuickBooks Error OL-393? Data Service Team can help you assess bank-feed errors, connection problems, and related QuickBooks Desktop issues.

Call +1-(888)-718-7888 to discuss your QuickBooks troubleshooting needs and the next steps for restoring bank-feed downloads.

Troubleshooting options can vary by QuickBooks Desktop version and financial institution. Confirm the supported connection method and follow the prompts for your specific setup.