The wrong portal trap: Many major banks have separate login portals for personal vs. business accounts — same bank, different URL, different credential set. QuickBooks may be connected to your personal portal when your business account lives at a different address. This produces 103 even when you enter credentials that work perfectly on the personal site. Always verify you are using the business banking URL when connecting a business account to QuickBooks.

Error code

103

Banking · Credential Rejection

Also appears with Error 310

What it means

Error 103 is generated by your bank — not by QuickBooks. When QuickBooks attempts to connect to your bank's servers using the credentials stored in QBO, the bank's authentication system rejects the login. This is always a credentials issue: wrong password, wrong username, wrong account portal, or the bank requires a permission step that hasn't been completed.

Password Changed at Bank

Most common cause — you updated your password at the bank but QuickBooks is still using the old one. QuickBooks does not automatically detect bank credential changes. Every time you update your bank password, you must also update it in QuickBooks manually.

Wrong Bank Portal Selected

QuickBooks is connected to a personal banking portal when the account is a business account (or vice versa). Banks like Chase, Bank of America, and Wells Fargo have entirely separate portals with different credentials for personal vs. business accounts.

Third-Party Access Not Enabled

Some banks require you to explicitly grant permission for third-party applications like QuickBooks to access your account data. Without this permission enabled in your bank settings, the bank rejects every connection attempt with 103 regardless of correct credentials.

Browser Auto-Fill Entering Wrong Credentials

Browser auto-fill populates the QuickBooks credential fields with saved credentials from a different account or an outdated password. Always disable auto-fill and manually type credentials when updating bank connections in QuickBooks.

Bank Migrated to New Login System

The bank upgraded to a new authentication system (common after bank mergers or security upgrades) — new login URL, new credential format, or new MFA requirement. The old connection method is permanently rejected. A full reconnect with the new system is required.

Account Security Lock

Multiple failed QuickBooks connection attempts can trigger the bank's security system to temporarily lock the account or flag it for suspicious activity. Log into the bank website directly and check for security alerts or locked account messages before attempting further QuickBooks reconnection.

METHOD 1 Verify Credentials Work on the Bank Website First Do this before touching QuickBooks

The most important diagnostic step — and the one most users skip. If your credentials don't work on the bank's own website, no QuickBooks fix will help. Confirm the credentials are correct at the source before spending time in QBO.

METHOD 2 Update Sign-In Info in QuickBooks (Existing Connection) If credentials changed at bank since last connection

If you have an existing bank connection that broke after a password change, update the stored credentials in QuickBooks without disconnecting the account — this preserves your transaction history.

METHOD 3 Enable Third-Party Access in Your Bank Settings Required by some banks — often overlooked

Many banks now require explicit permission before allowing third-party applications to access account data. If your bank has this setting and it is not enabled, every QuickBooks connection attempt will be rejected with 103 regardless of correct credentials. Check your bank's security or account settings for this option.

METHOD 4 Disconnect and Reconnect Using the Correct Bank URL If wrong portal was originally selected

If QuickBooks is connected to the wrong bank portal (personal vs. business), the only fix is to disconnect and reconnect using the correct URL. This does not delete your existing categorised transactions — only the live feed connection is reset.

METHOD 5 Check for Bank Security Lock or Required Action If repeated failures have locked the account

Multiple failed QuickBooks connection attempts can trigger your bank's security system. The bank may have locked third-party access, issued a security alert, or require you to complete an action (confirm identity, agree to updated terms) before connections are allowed again.

My bank says the issue is on QuickBooks' end. Is that possible?

In most cases, no — Error 103 is generated by your bank's authentication system rejecting QuickBooks' login request. Banks will sometimes say "it's the third-party app's problem" when the issue is actually their own third-party access restriction not being enabled, or a new authentication requirement they have introduced. The most productive approach is to confirm credentials are correct, check your bank's third-party/data sharing settings, and if still unresolved, ask the bank specifically what credential format they require for third-party application access — not just general internet banking access.

How is Error 103 different from Error 324?

Both are banking connection errors but they represent different failure types. Error 103 = the bank rejected the login credentials — QuickBooks can find the bank and reach its server but the username/password is wrong or not authorised. Error 324 = the bank accepted the login but cannot find the specific account — the account number changed, was closed, or the connection references the wrong account. Fix 103 by correcting credentials or enabling access. Fix 324 by disconnecting and reconnecting with the updated account details.

What can I do while Error 103 is preventing bank feed updates?

While 103 is blocking the live bank feed, you can manually import transactions to keep your books current. Most banks allow you to download transactions as a CSV, OFX, or QFX file from your online banking portal. In QuickBooks Online, go to Bookkeeping → Transactions → Bank Transactions → Upload transactions — and select your downloaded file. This keeps your reconciliation on track without needing the live connection. Once you resolve the 103 error and reconnect, set the bank feed start date to the day after your last manual import to avoid duplicates.