Fix QuickBooks Desktop Error OLSU-1013 (Bank Feeds Setup)
Resolve QuickBooks Desktop error OLSU-1013 when bank feed setup fails. Learn what the OL/OLSU error means and how to switch to reliable Web Connect imports
When you are setting up or refreshing bank feeds in QuickBooks Desktop, hitting a wall with an error code can bring your bookkeeping to a halt. Error OLSU-1013 is a common roadblock in this process. This guide explains what the error means, how to resolve it, and how to ensure your bank downloads keep working smoothly long-term.
Understanding the OL/OLSU Error Family
Error OLSU-1013 belongs to the OL/OLSU family of bank feed errors in QuickBooks Desktop. The "OL" stands for Online Banking. When you see a code starting with OLSU (or occasionally just OL, like OL-301 or OL-332), it means QuickBooks encountered a problem communicating with your financial institution's servers.
Because these codes are closely related, if you are seeing OLSU-1013, the underlying causes and fixes are generally the same as other nearby OLSU errors. These communication failures usually happen during the initial setup of a bank account or when QuickBooks tries to fetch the daily download.
Common Causes of OLSU-1013
This error typically surfaces when QuickBooks cannot establish a stable connection with your bank. The most frequent culprits include:
- Bank Maintenance or Outages: Your financial institution's servers might be temporarily down for maintenance.
- Outdated Bank Directory: QuickBooks relies on a local list of participating banks (the FIDIR file). If this list is outdated, the connection parameters may be wrong.
- Incorrect Credentials: A recent password change at your bank's website that hasn't been updated in QuickBooks.
- Direct Connect Deprecation: If you are running an older or discontinued version of QuickBooks, the Direct Connect bridges that Intuit used to route traffic may no longer be active for your software.
How to Fix Error OLSU-1013
You can resolve this error using a few standard troubleshooting steps. Try these fixes in order:
- Update your bank sign-in info: Go to your bank's actual website and log in to ensure your credentials are correct and that the bank isn't displaying any urgent messages or alerts requiring your attention.
- Deactivate and reactivate bank feeds: In QuickBooks, go to your Chart of Accounts, right-click the affected account, and select Edit Account. Under the Bank Feed Settings tab, choose Deactivate All. Save and close, then attempt to set up the bank feed again from scratch.
- Update your QuickBooks Desktop: Even if you are running an unsupported version, ensure you have the latest release patch installed for that specific year (e.g., the latest R-release for QuickBooks 2021). This can sometimes refresh the local bank directory.
The Durable Fix: Web Connect (.QBO) Imports
If you are running a discontinued version of QuickBooks Desktop, Direct Connect (the automated push of transactions into the software) eventually stops working entirely. Intuit shuts down the routing servers that facilitate these live connections for sunsetted versions, which will permanently trigger OLSU errors.
The most durable, long-term fix is to bypass live connections entirely and use Web Connect. This involves logging into your bank's website, downloading your transactions as a .QBO file, and importing them manually into QuickBooks. If your bank doesn't offer QBO downloads, you can usually download a CSV or Excel file and easily convert it to a QBO or IIF format. This method keeps your offline Desktop software fully functional without relying on Intuit's servers. For a complete walkthrough of this process, see our master guide to importing bank transactions into QuickBooks.
Preventing Future Bank Feed Errors
To keep your Desktop installation running smoothly, make a habit of downloading Web Connect (.QBO) files directly from your bank's portal on a regular schedule—such as weekly or monthly. By avoiding the live Direct Connect feature, you eliminate the server communication failures that cause OL and OLSU errors.
When the Company File Itself Is Damaged
Occasionally, OLSU-1013 is not caused by a server or connection issue, but by corruption within your working company file. If you have tried the steps above and the error persists specifically on one account while other accounts connect fine—or if the error is accompanied by crashing, freezing, or unreadable data—your .qbw file may be damaged. In these cases, running the standard Verify and Rebuild Data utilities in QuickBooks is the best first step to restore the file's integrity.