How to Fix QuickBooks Banking Error 102

QuickBooks Banking Error 102 means QuickBooks can't connect to your bank's website — usually because the bank is doing maintenance or having server issues. It typically clears up on its own within 24 hours. Meanwhile, check your bank's website directly for alerts, manually sync your bank feeds from the Bank Feeds Center, and re-enter your bank login credentials if you've changed them recently.

You sit down to reconcile, expecting this week's transactions to be waiting in your bank feeds. Instead: Error 102. No new transactions. Your books are suddenly a week behind, and you've got a reconciliation to finish.

Sound familiar? Here's the thing most people don't realize about Error 102: it's almost never your fault, and it's almost never QuickBooks' fault either. Nine times out of ten, your *bank's* website is down for maintenance or having a rough day, and QuickBooks simply can't get through. Your money is fine. Your data is fine. The connection is just... busy.

So before you start rebuilding things in QuickBooks, let's figure out what's actually going on — and fix the part you can control.

What is QuickBooks Banking Error 102?

Banking Error 102 appears when QuickBooks tries to connect to your bank or credit card company's website to download transactions and can't establish the connection. In QuickBooks Desktop, you'll see it in the Bank Feeds Center when you try to sync.

The critical thing to understand: this error is about the *connection between QuickBooks and your bank*, not about your company file or your data. Everything already in QuickBooks — your transactions, your reconciliations, your balances — is completely safe. QuickBooks just can't reach out and grab the new transactions right now.

If you're seeing other bank feed codes too, they may need different handling — for example, our guide on [OL and OLSU bank feed errors in QuickBooks](/fix-ol-and-olsu-bank-feeds-errors-in-quickbooks/) covers those.

Why does Banking Error 102 happen?

The usual suspects:

• Your bank's website is down for scheduled maintenance or dealing with an outage or server problem.
• There's a temporary communication failure between QuickBooks (or Intuit's servers) and your bank.
• Your bank login credentials changed — new password, new username — and QuickBooks is still using the old ones.
• The bank updated their website, changed security requirements, or moved their login page, and QuickBooks hasn't caught up yet.
• Your internet connection dropped, or your firewall, antivirus, or VPN is blocking the bank feed connection.
• You're running an older QuickBooks release that can't talk to your bank's updated systems.

How do you know it’s Error 102?

• The error code 102 appears in the Bank Feeds Center when you try to sync or download transactions.
• No new transactions download, even though you know activity happened on the account.
• You may see a message saying QuickBooks couldn't connect to your financial institution.
• The problem often starts suddenly — feeds worked yesterday, nothing changed on your end, and now they don't.

That last one is actually a useful clue. If nothing changed on your side, the problem is almost certainly on the bank's side.

Solutions that actually fix Banking Error 102

Start at the top. Most people never make it past Solution 2.

Solution 1: Give it a little time (seriously)

We know — not the answer you wanted. But Error 102 most commonly means your bank is doing maintenance or having server trouble, and those issues resolve on their own, typically within 24 hours.

• Try syncing again in a few hours. If it works, you just saved yourself a lot of unnecessary troubleshooting.
• Intuit's own guidance says these bank-side issues can take up to 24 hours (sometimes a bit more) to clear.

There's no point rebuilding bank connections for a problem that lives on your bank's servers. Patience is genuinely the fix here, most of the time.

Solution 2: Check your bank’s website directly

Before touching anything in QuickBooks, investigate the bank's side.

• Open your browser and log in to your bank's website directly — not through QuickBooks.
• If you can't log in there either, the problem is 100% on the bank's end. Check their status page or give them a call.
• Look for any messages, notifications, or alerts about maintenance, outages, or required actions on your account. Banks often post these right on the login page or account dashboard.
• Review your account pages and transaction history. If those load fine, the bank's site is up and the issue is specifically with the QuickBooks connection.
• If you recently changed your bank password, that's very likely your culprit — QuickBooks is still trying the old credentials.

Solution 3: Sync your bank feeds manually

Sometimes the connection just needs a nudge.

• In QuickBooks Desktop, go to Banking, then Bank Feeds, then Bank Feeds Center.
• Select the account showing Error 102.
• Click Sync All (or the sync/download button for that account).
• Let it run. If it connects this time, watch for prompts — QuickBooks may ask you to re-enter your bank login credentials or complete a multi-factor authentication step.
• Enter your current credentials carefully. And if your browser auto-fills passwords anywhere in this process, double-check it's not filling in an old one.

Solution 4: Update your bank sign-in information

If your bank login changed — or if QuickBooks just needs a fresh handshake — updating the credentials often clears the error.

• Go to Banking > Bank Feeds > Bank Feeds Center.
• Select the problem account and look for the option to edit or update your sign-in information.
• Manually enter your current bank username and password (don't rely on saved or auto-filled entries).
• Save, then sync the account again.

Also worth checking: has your bank added new security steps, like mandatory two-factor authentication or a terms-of-service acceptance? Those can block QuickBooks until you complete them on the bank's website first.

Solution 5: Deactivate and reactivate bank feeds for the account

If syncing and new credentials didn't help, a clean re-link often does.

• Go to Banking > Bank Feeds > Bank Feeds Center.
• Select the problem account and deactivate bank feeds for it. (This stops the feed — it doesn't delete any transactions already in QuickBooks.)
• Close the Bank Feeds Center, then reopen it.
• Set up bank feeds for the account again from scratch: Banking > Bank Feeds > Set Up Bank Feed for an Account.
• Follow the prompts, enter your current bank login, and complete any verification steps.
• Try syncing once more.

Solution 6: Check your connection and update QuickBooks

The boring-but-effective final checks:

• Make sure your internet is actually working — open a couple of websites to confirm.
• Temporarily disable any VPN, which can interfere with bank connections.
• Update QuickBooks Desktop: go to Help > Update QuickBooks Desktop, click Update Now, select Get Updates, and restart QuickBooks when it's done. Older versions sometimes can't communicate with banks that have updated their own systems.
• Check that your firewall or antivirus isn't blocking QuickBooks from reaching the internet.

Still seeing bank feed errors with a different code — like 185, which involves security verification? That's a different beast; see our guide to [troubleshoot QuickBooks Banking Error 185](/troubleshoot-quickbooks-banking-error-185/).

Conclusion!

That brings us to the end of the troubleshooting methods for QuickBooks Banking Error 102. We hope the solutions explained above helped you understand the possible cause of the error and get your bank feeds syncing again. If the error still appears or you run into any difficulty while following the steps, consider consulting a qualified and experienced QuickBooks professional for further assistance.

FAQs

You may also like:

QuickBooks Banking Error 105

QuickBooks Banking Error 109

fix QuickBooks banking error 324

troubleshoot QuickBooks banking error 185