Showing results for 
Search instead for 
Did you mean: 
Level 1


Ever since I had to upgrade to QB2020, I have not been able to download transactions from my bank feed.  I get an error message: OL337.  Any advice?  Bank of the West was unable to help.

3 Comments 3
Tori B
QuickBooks Team


Hi there, @bkg13.


Thanks for coming to the Community for support. I can see how the error OL337 can be frustrating when trying to download transactions from your bank feed. But no worries, I've got you covered! 


First, let's check if your company file may have data integrity issues by creating a test company file and downloading the transactions there. I've included the steps below to do this.


1. Open your QBDT company file, then go to the File menu at the top.
2. Pick New Company on the drop-down, then select Express Start.
3. In the newly created test company, add the bank account, which was experiencing issues, and set up the account for Bank Feeds.
4. Then, Download Bank Feed transactions to test the account.




Please note: If the transactions download as normal, then you'll know that your company file is facing some data integrity issues. However, if it doesn't work, this means your bank needs your confirmation to verify your identity, or they're making some changes on their server or website. In this case, you may need to wait some time or contact your bank and speak with their QuickBooks experts team.


If your file is facing data integrity issues, I recommend to run a Rebuild and Verify on the company file. Once you've completed the rebuild and verify, try downloading the transactions again. 


Please let me know if you have any questions or concerns. I'll be here every step of the way. You can reach out to the Community at any time. Take care and have a fantastic day! 

Level 1


I created a test company file, but I got another error message when I tried to connect my bank account.  Error code OLSU1013.  The link to common fixes took me straight back to the "Fix OL and OLSU Bank Feeds error in QuickBooks Desktop" post.  So now I'm in this circular feedback loop with no answers.  I called Bank of the West, waited on hold for 30 minutes, told the rep about my problem, was put on hold for 5 minutes, and then received a recording directing me to this website and then disconnected.  So no help anywhere, just finger pointing from QuickBooks and Bank of the West.

QuickBooks Team
QuickBooks Team


I know going through multiple troubleshooting steps and not having any of them work can be a real pain, especially when you have more important things to do, bkg13.


I appreciate you performing the steps provided by my colleague and the time you've spent contacting your bak provider. You'll encounter the OLSU-1013 error if There’s a problem with your banks such as pending alerts on your online bank account or a problem with their servers. Aside from that, you'll encounter this issue for the following possible reasons:

  • There’s a problem with one or more bank accounts in your company file
  • The file from your bank isn’t compatible with QuickBooks
  • You’re using an outdated version of Internet Explorer or you’re using an unsupported version of QuickBooks

If you already performed the recommended troubleshooting steps in the Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop article, I'd suggest contacting your Technical Support Team. They'll pull up your account in a secure environment and investigate what's causing this issue. Here's how to reach them:

  1. Click the Help icon on the top menu. 
  2. Choose QuickBooks Desktop Help
  3. Tap Contact us.
  4. Select Search for something else and enter your concern in the Tell us more about your question: field. 
  5. Tap Search
  6. Choose Start a Message or Get Phone Number to connect with our support. 

Feel free to visit our Banking page for more insights about managing your bank feeds in QuickBooks.


I'll be right here to continue helping if you have any other concerns or questions about QuickBooks. Assistance is just a post away. Take care always. 

Need to get in touch?

Contact us