How to Fix QuickBooks Banking Errors OL-301, OL-332, OL-334, OLSU-1013 & OLSU-1024

Bank Feed Not Working? Get Your Transactions Downloading Again

You go to download your bank transactions in QuickBooks Desktop, same as you do every week, and instead of your transactions coming through you get hit with an error code. OL-301. Or OL-332. Maybe OLSU-1013. Whatever the specific number is, the result is the same — QuickBooks can't connect to your bank, and your transactions aren't downloading.

If you're seeing any of these errors, take a breath. You're not the only one dealing with this. These are some of the most common errors in QuickBooks Desktop, and they pop up constantly — sometimes because your bank made changes to their website, sometimes because QuickBooks needs an update, and sometimes for reasons that seem completely random. The point is, they're fixable. If you have general QuickBooks questions, our FAQ page is a good starting point. I'm going to walk you through everything: what each error actually means, what's causing it, and exactly how to get your bank feed working again.

What's in This Guide:

▶ What OL and OLSU errors actually mean

▶ Quick reference table for each error code

▶ 7 common causes

▶ 10 step-by-step fixes (start with #1)

▶ Tips for keeping your bank feed working

▶ FAQs

What Do OL and OLSU Errors Actually Mean?

Before you start troubleshooting, it helps to understand what these error codes are actually telling you. They're not random numbers — they give you a clue about what's going wrong between QuickBooks and your bank.

OL errors stand for "Online Banking" errors. These happen during the actual communication between QuickBooks Desktop and your bank's servers. Think of it like QuickBooks picking up the phone to call your bank and ask for your latest transactions. An OL error means that phone call didn't go through — the connection failed, the bank didn't respond the way QuickBooks expected, or something in the middle got in the way.

OLSU errors stand for "Online Services Update" errors. These are related but slightly different. OLSU errors happen when QuickBooks tries to update the connection settings for your bank — basically the instructions QuickBooks uses to know how to talk to your bank. If those instructions are outdated or can't be downloaded, you get an OLSU error.

In plain terms: OL errors mean "I tried to talk to your bank and it didn't work." OLSU errors mean "I can't even figure out how to talk to your bank right now."

Quick Reference: What Each Error Code Means

Here's a quick breakdown of the specific errors you might be seeing. The fixes are mostly the same for all of them, but knowing which one you have helps you understand the likely cause.

Error Code	What It Means
OL-301	Bank connection failed. This is the most common one. QuickBooks tried to reach your bank and the connection was refused or timed out. Could be a temporary bank issue, expired credentials, or a bank website change.
OL-332	Your bank needs you to log in to their website directly. Usually means the bank has posted new terms and conditions, a security update, or a disclosure that requires you to agree to it in your web browser before QuickBooks can connect again.
OL-334	Bank connection issue, often triggered after the bank makes changes to their website or security system. Similar to OL-301 but usually points to the bank's end rather than yours.
OLSU-1013	QuickBooks can't connect to the bank's server at all. The bank's server might be down, the connection details might be wrong, or your internet connection might be blocking the request.
OLSU-1024	The bank feed connection needs to be refreshed or reconnected. QuickBooks knows how to talk to the bank, but the existing connection has gone stale. Usually fixed by disconnecting and reconnecting the bank feed.

Why These Errors Happen in the First Place

Understanding the root cause saves you time because you can often skip straight to the fix that matches your situation. Here are the most common reasons your bank feed stops working.

Your bank changed their website or security settings

This is the number one cause by far. Banks update their websites, upgrade their security systems, and change the way outside programs connect to them on a regular basis. When your bank does this, QuickBooks suddenly doesn't know how to talk to them anymore. This is especially common with smaller regional banks and credit unions that are migrating to new online banking platforms.

You need to accept new terms on your bank's website

Your bank posts an updated privacy policy, terms of service, or security agreement on their website. Until you physically log in through a web browser and click "I agree" or "Accept," the bank blocks all third-party connections — including QuickBooks. You won't see the prompt inside QuickBooks because QuickBooks doesn't display your bank's web pages.

QuickBooks is out of date

Intuit releases updates for QuickBooks Desktop throughout the year, and many of those updates include changes to bank connectivity. If you're running an older version of QuickBooks — or even a recent version that's a few updates behind — the bank connection code might not match what your bank currently expects.

Your bank login credentials changed

If you recently changed your online banking password, set up a new username, or your bank required you to reset your password for security reasons, QuickBooks is still trying to log in with the old credentials. The bank rejects the connection and QuickBooks shows you an OL error.

The bank feed connection went stale

Sometimes the connection between QuickBooks and your bank just stops working for no obvious reason. The technical handshake that keeps the two systems in sync expires or gets corrupted. This is more common with Direct Connect and happens naturally over time, especially if you haven't downloaded transactions in a while.

Your bank is doing maintenance

Banks take their online banking systems offline for maintenance more often than you'd think — usually late at night or on weekends. If you happen to try downloading transactions during that window, QuickBooks gets an error because the bank's server literally isn't there. Most bank maintenance windows last a few hours.

Your bank dropped support for Direct Connect

Some banks are moving away from Direct Connect (which lets QuickBooks talk directly to the bank) in favor of Web Connect or Express Web Connect. If your bank made that switch and you're still set up for Direct Connect, the connection fails because that door is closed on the bank's end.

How to Fix QuickBooks Banking Errors — Step by Step

Work through these fixes in order. The first few are quick and easy, and they solve the problem for most people. Only move on to the later steps if the earlier ones didn't work.

FIX #1

Log Into Your Bank's Website Directly

This is the fix you should always try first. Before you do anything in QuickBooks, open a web browser — Chrome, Edge, Firefox, whatever you use — and go to your bank's website. Log in with the same username and password that QuickBooks uses to connect.

Step 1 Open your bank's website in a browser and log in with the same credentials QuickBooks uses.

Step 2 Look for any pop-up messages, new terms and conditions, security alerts, or "action required" banners. Accept everything, agree to everything, answer any security questions, and verify your phone number or email if prompted.

Step 3 Make sure you can see your accounts and recent transactions on the bank's website.

Step 4 Go back to QuickBooks and try downloading transactions again.

This single step fixes OL-332 almost every time and clears up OL-301 and OL-334 in a lot of cases.

FIX #2

Update QuickBooks to the Latest Release

Intuit releases patches and updates regularly that include bank connectivity fixes. If you're even one or two updates behind, your version of QuickBooks might not be able to connect to banks that have updated their systems.

Step 1 In QuickBooks, go to Help → Update QuickBooks Desktop.

Step 2 Click the Update Now tab.

Step 3 Check the Reset Update checkbox to make sure you're getting everything fresh, then click Get Updates.

Step 4 When the update finishes, close QuickBooks and reopen it. QuickBooks will install the update during startup — let it finish before you try anything else.

A lot of OL and OLSU errors disappear after a good update because Intuit has already patched the connection issue on their end.

FIX #3

Deactivate and Reactivate Your Bank Feed

If updating didn't do the trick, the next thing to try is disconnecting your bank feed and setting it back up. This forces QuickBooks to create a brand new connection to your bank instead of trying to use the old (possibly broken) one.

Don't worry about your data. Deactivating your bank feed doesn't delete your account or your transaction history. It just removes the online connection to the bank.

Step 1 Go to Banking → Bank Feeds → Bank Feeds Center.

Step 2 Find the bank account that's giving you trouble. Click on it.

Step 3 Click Deactivate All Online Services for that account. QuickBooks will ask you to confirm — go ahead and confirm.

Step 4 Set it back up: go to Banking → Bank Feeds → Set Up Bank Feed for an Account. Search for your bank, enter your login credentials, and link it to the same QuickBooks account you were using before.

Step 5 Once the new connection is established, try downloading transactions.

This clears OLSU-1024 and many OL-301 errors because you're starting with a fresh connection that uses the bank's current settings.

FIX #4

Delete the Bank Connection and Create a New One

This is similar to Fix #3 but goes a step further. Instead of just deactivating and reactivating, you're completely removing the bank from QuickBooks' connection list and adding it back from scratch.

Step 1 Go to Banking → Bank Feeds → Manage Bank Feeds.

Step 2 Find your bank in the list and select Delete or Remove. This does not delete your bank account in QuickBooks or any of your recorded transactions. It only removes the online connection.

Step 3 Close QuickBooks completely and reopen it.

Step 4 Set up the bank feed again from scratch using Banking → Bank Feeds → Set Up Bank Feed for an Account. Search for your bank, log in, and link the accounts.

This is the fix that tends to work for stubborn OLSU-1013 errors and OL-301 errors that won't go away with a simple deactivation.

FIX #5

Check If Your Bank Still Supports Your Connection Type

Banks periodically change which connection types they support for QuickBooks. There are three main types:

Direct Connect — QuickBooks connects directly to the bank's server. This is the fastest and most reliable option, but not all banks offer it, and some that used to have dropped it. Direct Connect usually requires a monthly fee from the bank (typically $10-15/month).

Express Web Connect — QuickBooks connects to your bank through Intuit's servers, which act as a middleman. This is the most common connection type and doesn't usually require an extra fee from the bank. Most banks support this.

Web Connect — You manually download a file from your bank's website (usually a .QBO or .OFX file) and import it into QuickBooks. This is the least automated option, but it works with almost every bank and is a good fallback if the other methods are broken.

Check Go to Banking → Bank Feeds → Set Up Bank Feed for an Account and search for your bank. QuickBooks will show you which connection type is available. If your bank used to offer Direct Connect but doesn't anymore, that explains why your existing setup stopped working.

FIX #6

Switch Your Connection Type

If you're currently using Direct Connect and it's not working, try switching to Express Web Connect. Or if Express Web Connect is acting up, try using Web Connect as a temporary workaround.

Step 1 Deactivate your current bank feed (see Fix #3) and set it up again, choosing a different connection type during the setup process.

Step 2 When QuickBooks asks how you want to connect, pick a different option than what you had before.

Web Connect workaround: If you switch to Web Connect as a temporary fix, log into your bank's website, go to your account, look for a download option (usually under account history or statements), and download transactions in QBO or OFX format. Then in QuickBooks, go to File → Utilities → Import → Web Connect Files and select the file you downloaded. It's a few extra clicks, but it gets your transactions into QuickBooks while you work on getting the automatic connection fixed.

FIX #7

Check If Your Bank Is Experiencing an Outage

Sometimes the problem isn't on your end at all. Your bank might be having technical issues or running maintenance on their systems. Before you spend two hours troubleshooting, it's worth checking.

Check your bank's website or app. If you can't log in through the website either, the problem is clearly on the bank's end. Wait a few hours and try again.

Check the Intuit status page. Intuit maintains a list of known bank connection issues. Sometimes a specific bank is having problems that affect all QuickBooks users, and Intuit will post a notice about it.

Call your bank. Tell them you're having trouble connecting through QuickBooks (or any third-party financial software). They can check if there's a known issue on their end. Many bank customer service reps deal with these calls regularly and can give you a straight answer about whether their system is down.

If the bank is having issues, there's nothing to fix on your end. Just wait it out and try again later — usually the next morning or the next business day.

FIX #8

Reset Your Bank Credentials in QuickBooks

If you recently changed your online banking password or your bank made you reset it, QuickBooks is still trying to use the old login information. You need to tell QuickBooks about the new password.

Step 1 Go to Banking → Bank Feeds → Bank Feeds Center.

Step 2 Click on the bank account that's having the issue.

Step 3 Look for an option that says Edit Credentials or Change Password. Click it and enter your current online banking username and password — the same ones you use to log into your bank's website.

Step 4 Save the changes and try downloading transactions again.

This is a quick fix that people often overlook. If you changed your password on the bank's website three weeks ago and your bank feed stopped working around the same time, this is almost certainly the problem.

FIX #9

Run QuickBooks Tool Hub — Program Problems

QuickBooks Tool Hub is a free program from Intuit that includes a bunch of repair tools for common QuickBooks problems. If the fixes above haven't worked, it's worth running the program repair tools to make sure there isn't a deeper issue with your QuickBooks installation.

Step 1 If you don't already have QuickBooks Tool Hub installed, download it from Intuit's website. Search "QuickBooks Tool Hub download" and grab it from the official Intuit page. Install it and open it.

Step 2 Inside Tool Hub, click on the Program Problems tab.

Step 3 Click Quick Fix My Program. This shuts down any QuickBooks processes running in the background and runs a quick repair on the program.

Step 4 Once it finishes, open QuickBooks and try your bank feed again.

If Quick Fix My Program doesn't solve it, you can also try the QuickBooks Program Diagnostic Tool in the same section. It takes longer to run (sometimes 20-30 minutes) but it does a more thorough repair of the program files.

FIX #10

Contact Your Bank's QuickBooks Support Line

Here's something a lot of people don't know: many large banks have a dedicated phone number or support team specifically for QuickBooks and other accounting software connections. This isn't the regular customer service line — it's a team that specializes in fixing third-party connections to the bank's systems.

If you bank with Chase, Bank of America, Wells Fargo, Citi, or any other major bank, call their regular customer service number and ask to be transferred to their "online banking technical support" or "third-party software support" team. Tell them you're having trouble connecting QuickBooks Desktop to your account and give them the specific error code. They can check on their end whether there's a known issue, whether your account has the right permissions for third-party connections, and whether they need to reset something on their side.

For smaller banks and credit unions, the regular customer service team usually handles this. Tell them you're getting an error when trying to download transactions into QuickBooks and ask if they've heard similar complaints from other customers. If the bank recently switched their online banking platform, they'll know about it and can walk you through what changed.

Tips for Keeping Your Bank Feed Working

Once you've got your bank connection working again, here are some things you can do to keep it from breaking again — or at least make it less painful when it does.

✓

Download transactions regularly

Don't let weeks or months go by without connecting to your bank. The more often you download, the less likely the connection is to go stale. Once a week is a good habit. If you can set a reminder to do it every Friday afternoon, you'll stay on top of it.

✓

Keep QuickBooks updated

Turn on automatic updates if you haven't already. Go to Help → Update QuickBooks Desktop → Options tab, and set it to update automatically. That way you always have the latest bank connectivity patches without having to think about it.

✓

Log into your bank's website periodically

Even if you don't need to, log in through a browser every couple of weeks. Accept any new terms, answer any security prompts, and make sure there are no "action required" messages waiting for you. This prevents the most common cause of OL-332.

✓

Don't change your banking password without updating QuickBooks

If you change your online banking password, go into QuickBooks right away and update the saved credentials for that bank feed. Don't wait until the next time you download transactions and wonder why it's not working.

✓

Know your connection type

It's helpful to know whether you're using Direct Connect, Express Web Connect, or Web Connect. That way, if something breaks, you know what you're working with and can troubleshoot more quickly. You can check this in the Bank Feeds Center under the account details.

✓

Keep Web Connect as a backup plan

Even if your automatic bank feed is working great, it's good to know how to manually download a QBO file from your bank and import it into QuickBooks. If your automatic connection goes down right before a deadline, you can still get your transactions in by going the manual route. It takes five extra minutes but keeps you from being stuck.

Important Note About QuickBooks Versions and Bank Feeds

Bank feeds in QuickBooks Desktop require either an active QuickBooks Desktop Plus subscription or a supported version of QuickBooks that hasn't been discontinued. Intuit officially supports QuickBooks Desktop versions for about three years after their release. After that, they stop providing updates — including the bank connectivity updates that keep your bank feeds working.

If you're running a version of QuickBooks Desktop from 2021 or earlier, your bank feeds may have already stopped working or will stop working soon because Intuit is no longer updating the bank connection code for those versions. The software itself still works fine for entering transactions manually, running reports, and everything else — but the automatic bank download feature gets cut off when support ends.

If that's the situation you're in, you have two options: upgrade to a newer version of QuickBooks Desktop that's still supported, or switch to Web Connect (manually downloading and importing QBO files from your bank's website). Both options work, and both will get your transactions into QuickBooks.

If you're thinking about upgrading, we carry all current versions of QuickBooks Desktop at Accountings Cart — Pro Plus, Premier Plus, and Enterprise. One-time purchase, real license keys, no ongoing subscription. Learn how to buy QuickBooks Desktop without a subscription , or check our shop to see what's available and what fits your business.

2024 Download Guide → 2023 Download Guide → Browse All Products →

Quick Summary: Banking Error Fixes at a Glance

Fix	What It Does	Best For
Log into bank website	Accept new terms, clear security prompts	Very High
Update QuickBooks	Gets latest bank connectivity patches	High
Deactivate/reactivate feed	Creates a fresh connection to the bank	High
Delete and recreate connection	Fully removes and rebuilds the bank link	High
Check connection type	Verifies bank still supports your connection method	Moderate
Switch connection type	Changes from Direct Connect to Express Web Connect or vice versa	Moderate
Check for bank outage	Confirms the problem is on the bank's end	Depends
Reset bank credentials	Updates saved username/password in QuickBooks	High
QuickBooks Tool Hub	Repairs program-level issues	Moderate
Contact bank's QB support	Gets help from the bank's side	Depends

Frequently Asked Questions

Will I lose my transaction data if I disconnect my bank feed?

No. Disconnecting or deactivating your bank feed only removes the online connection between QuickBooks and your bank. All the transactions you've already downloaded and recorded in QuickBooks stay exactly where they are. Your bank account, your chart of accounts, your reconciliations — none of that is affected. You're just resetting the pipeline that brings in new transactions.

I'm getting a different OL error number not listed here. Do the same fixes apply?

Yes, for the most part. There are a bunch of OL error codes (OL-301, OL-332, OL-334, OL-393, and others), but they all fall into the same category of "QuickBooks can't communicate with your bank." The ten fixes listed above apply to all of them. Start with Fix #1 and work your way down.

Can I use multiple bank feeds in QuickBooks at the same time?

Absolutely. You can connect as many bank accounts as you want — checking, savings, credit cards, even loan accounts if your bank supports it. Each one has its own connection, so if one bank feed breaks, it doesn't affect the others. If you're getting errors on one account but the others are working fine, focus your troubleshooting on just that one connection.

My bank says they don't support QuickBooks anymore. What do I do?

Some smaller banks and credit unions do drop support for direct QuickBooks connections. If that happens, your best bet is Web Connect — manually downloading a QBO file from your bank's website and importing it into QuickBooks. It's not automatic, but it works. Log into your bank, download your recent transactions in QBO or OFX format, and import them through File → Utilities → Import → Web Connect Files. You might also want to ask your bank if they plan to add support back in the future, or consider switching to a bank that supports QuickBooks connections if it's a dealbreaker for your workflow.

Bank feed errors are one of the most frustrating things about QuickBooks Desktop because they make you feel like something is seriously wrong when usually it's just a connection hiccup. If you've tried the fixes above and you're still getting OL or OLSU errors, don't hesitate to reach out. We work with QuickBooks Desktop every single day, and there's a good chance we've seen your exact situation before.

And if your version of QuickBooks is getting old and you're thinking about upgrading, check our 2024 download guide or take a look at our shop. We carry QuickBooks Desktop Pro Plus, Premier Plus, and Enterprise — all genuine license keys, all at fair prices. A newer version means better bank connectivity, more security patches, and fewer headaches down the road.

Written By