Skip to main content

SUMMER SAVINGS 90% OFF QuickBooks for 3 months* Ends 8/27

Buy now
Switch to QuickBooks and 70% off for 3 Months
May 11, 2024
Solved

Why can't I connect my Chase bank account to QuickBooks (Error 4000)?

  • May 11, 2024
  • 5 replies
  • 66 views

I received the below 4000 message when trying to connect to my Chase bank for the first time.

 
Can you please advise?
 

Something unexpected happened and we can’t connect to Chase Bank.

Try again in a few hours. (4000)

Best answer by katelynner

This message usually points to a temporary hiccup, either in your browser or on the bank's end, rather than anything wrong with your account. Here's how to work through it.

 

Step 1: Try a private or incognito browser window

Cached browser data can sometimes cause QuickBooks to behave unexpectedly.

  • Google Chrome, Mozilla Firefox, or Microsoft Edge: press Ctrl + Shift + N.
  • Safari: press Command + Shift + N.

Try connecting your Chase account again in that private window.

 

Step 2: Try a different supported browser

If the same message shows up, switch to another supported browser to rule out an issue specific to the one you're using.

 

Step 3: Check Chase's website directly

Sign in to your Chase account through your regular browser and look for any messages, notifications, or alerts that might need your attention before QuickBooks can connect.

 

Once you're connected, you can trigger a manual update if needed and you should then see all of your transactions flowing into QuickBooks.

 

Let us know how it goes, or if you're still seeing the same message after trying these steps.

 

5 replies

QuickBooks Team
May 11, 2024

Hi there, @Affinitistyle.

I want to ensure that you can connect your Chase bank account to QuickBooks Solopreneur. Let's perform troubleshooting steps to get this fixed.

 

It's possible that QuickBooks may behave unexpectedly due to data issues in your browser. To verify this, try using an incognito or private browser. To open an incognito window, you can use the following keyboard shortcuts:

 

  • Mozilla Firefox and Microsoft Edge: Press Ctrl + Shift + N
  • Google Chrome: Press Ctrl + Shift + N
  • Safari: Press Command + Shift + N

If you continue to experience the same result, I suggest using other supported browsers. This will help us identify if the issue is specific to your current browser.

 

If the issue persists, you can check the bank's website to make sure everything is also working on their end. This way, you can sign in from there and check for any messages, notifications, or alerts.

 

Once you're connected, you can already categorize your bank transactions. You can visit this article as a reference: Categorize bank transactions in QuickBooks Solopreneur.


As you connect your bank, rest assured that I'm always here to lend a helping hand. Should you need assistance with any other areas, feel welcome to drop me a comment below.

May 11, 2024

Thank you - will give this a try

katelynner
Community Manager
August 21, 2026

This message usually points to a temporary hiccup, either in your browser or on the bank's end, rather than anything wrong with your account. Here's how to work through it.

 

Step 1: Try a private or incognito browser window

Cached browser data can sometimes cause QuickBooks to behave unexpectedly.

  • Google Chrome, Mozilla Firefox, or Microsoft Edge: press Ctrl + Shift + N.
  • Safari: press Command + Shift + N.

Try connecting your Chase account again in that private window.

 

Step 2: Try a different supported browser

If the same message shows up, switch to another supported browser to rule out an issue specific to the one you're using.

 

Step 3: Check Chase's website directly

Sign in to your Chase account through your regular browser and look for any messages, notifications, or alerts that might need your attention before QuickBooks can connect.

 

Once you're connected, you can trigger a manual update if needed and you should then see all of your transactions flowing into QuickBooks.

 

Let us know how it goes, or if you're still seeing the same message after trying these steps.