Icon  Struggling with software errors? Get expert help—fast, secure, and available 24/7.

QuickBooks Error OL 393: Causes, Fixes & Prevention Tips

Published: 29 October, 2025 | Updated: 29 October, 2025

Error Code Experts Staff

Author

Error Code Experts Staff
QuickBooks Error OL 393

QuickBooks Error OL 393 usually occurs when users try to download transactions or connect to their bank account. The error often appears due to outdated bank information, inactive bank accounts, or issues with internet banking settings. This guide explains what causes the error, how to identify it, and provides complete steps to fix it effectively.

What is QuickBooks Error “OL 393”?

QuickBooks Error OL 393 is a banking connectivity issue that occurs when the software cannot establish a secure link with the financial institution. It prevents users from downloading recent bank transactions, updating account information, or performing online banking tasks.

This error is commonly linked to outdated account setups, incorrect bank login details, or temporary interruptions from the bank’s server.

Why does QuickBooks Error “OL 393” occur?

QuickBooks Error OL 393 occurs due to several reasons, including:

  • Incorrect or outdated bank login credentials.
  • A deactivated or closed bank account in QuickBooks.
  • Temporary issues from the financial institution’s server.
  • Corrupted QuickBooks company files.
  • Outdated QuickBooks Desktop version.
  • Changes made by the bank to its online banking system.

How can you identify QuickBooks Error “OL 393”?

Users can identify QuickBooks Error OL 393 by noticing the following signs:

  • QuickBooks displays the message: “QuickBooks was not able to complete your request [OL 393].”
  • Online banking stops working.
  • Transaction download fails repeatedly.
  • The bank feeds center does not refresh.
  • QuickBooks freezes or runs slow while connecting to the bank.

What are the steps to fix QuickBooks Error “OL 393”?

You can fix QuickBooks Error OL 393 by following these methods in order. Start with the basic solutions and move to advanced troubleshooting if the error persists.

Solution 1: Update QuickBooks Desktop and Bank Feeds

  1. Open QuickBooks Desktop.
  2. Go to Help > Update QuickBooks Desktop.
  3. Click Update Now, then select Get Updates.
  4. Restart QuickBooks after updates are complete.
  5. Reconnect to your bank account and check if the error persists.

Updating ensures compatibility with your bank’s latest online systems.

Solution 2: Refresh Bank Connection

  1. Go to Banking > Bank Feeds > Bank Feeds Center.
  2. Select the affected account.
  3. Click Deactivate Bank Feed Service.
  4. Close and reopen QuickBooks.
  5. Go to Bank Feeds Setup again and reactivate the account.

This resets the connection between QuickBooks and your bank.

Solution 3: Verify Account Information

  1. Log in to your online banking account through a web browser.
  2. Check for any alerts, updates, or verification requests.
  3. Update your password if required.
  4. Return to QuickBooks and re-enter your credentials under Bank Feeds Setup.

Solution 4: Check Company File Integrity

  1. Go to File > Utilities > Verify Data.
  2. If QuickBooks detects issues, choose Rebuild Data.
  3. Once done, restart QuickBooks and try connecting to your bank again.

This process fixes any file corruption that could be triggering the error.

Solution 5: Create a Test Company File

Creating a test file helps identify if the issue is specific to your company file.

  1. Go to File > New Company > Express Start.
  2. Add a dummy bank account and try connecting to the same bank.
  3. If the error does not appear, your main company file may be damaged.

You may need to restore a recent backup or repair the data file.

Solution 6: Contact Your Bank

If all steps fail, reach out to your bank to confirm there are no ongoing issues with online banking. Ask if there were any recent updates in connection settings or web-connect changes that could affect QuickBooks access.

Is there an automated tool to fix QuickBooks Error “OL 393”?

Yes. You can use the QuickBooks Tool Hub — an official Intuit utility that automatically diagnoses and repairs banking connection issues.

Steps:

  1. Download QuickBooks Tool Hub from Intuit’s official website.
  2. Open it and go to Program Problems > Quick Fix my Program.
  3. After completion, restart QuickBooks and test your bank connection.

How can I prevent QuickBooks Error “OL 393” in the future?

  • Keep QuickBooks Desktop updated.
  • Regularly verify and rebuild company data.
  • Use a strong, updated internet connection.
  • Check your bank’s website for system alerts.
  • Avoid using outdated login credentials.

What if QuickBooks Error “OL 393” is not fixed after troubleshooting?

If the issue remains unresolved after all the above solutions, it may indicate a deeper problem with the company file or the bank’s connection protocol. In that case, professional assistance is recommended for advanced diagnosis and repair.

How can our experts assist you in resolving QuickBooks Error “OL 393”?

If you are still facing QuickBooks Error OL 393, contact Error Code Experts. Our team specializes in resolving QuickBooks banking errors efficiently. You can email us at support@errorcodeexperts.com or call +1-800-949-1746 for instant support. We ensure quick diagnosis, secure data handling, and full restoration of online banking functionality.

CTA Image CTA Image

Let’s Get In Touch

Dealing with a QuickBooks error? From installation issues to company file problems—we’ve got you covered. Chat or call now to get real help from real QuickBooks experts, 24/7. We resolve errors quickly so your business stays on track—without the wait.

Error Code Experts Staff

Author

Error Code Experts Staff

We are a team of certified IT and financial systems specialists with over 10 years of experience in fixing accounting software issues. We specialize in system integration, data migration, and diagnostics - making it easier for accountants and business owners to resolve complex errors. When not solving technical problems, our team enjoys refining internal tools and sharing practical fixes with the wider accounting community.