Chase Bank Fix: Resolving QuickBooks Error 103 for Chase Accounts

October 7, 2026 7 min read

QuickBooks Error 103 on Chase accounts indicates that JPMorgan Chase’s authorization servers have rejected the login credentials or digital access permissions submitted by QuickBooks. While Error 103 can point to a mistyped username or password, on Chase accounts it is frequently caused by expired third-party data-sharing permissions, an outdated connection protocol, or attempting to use personal login credentials for a commercial account. To fix Error 103 on a Chase account, log into the Chase website, verify that third-party access is authorized in your Security and Privacy dashboard, and reconnect the bank feed using Chase’s direct OAuth window.

Fast-Fix: The 45-Second Solution

To resolve Chase Error 103, sign in to Chase.com directly using an incognito browser window to verify your username and password. In Chase, navigate to Profile & Settings > Security & Privacy > Linked Apps and ensure Intuit/QuickBooks is listed as “Active.” Next, open QuickBooks, go to your Bank Feeds Center, click “Edit Account Info” on the Chase account, and re-enter your credentials through the secure Chase authorization window.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low. Error 103 is strictly an authentication barrier. It does not alter your existing registers, cleared transactions, or balance sheet history.
  • Multi-User Impact: Isolated to transaction downloads for Chase accounts. General multi-user accounting operations remain fully functional.
  • Common Trigger: Recent Chase online banking password changes, expired third-party sharing permissions, credential mismatches between Chase Personal and Chase Business profiles, or Chase security lockouts.
  • Estimated Fix Time: 5 to 15 minutes.

Technical Anatomy: How Chase Authenticates with QuickBooks

Chase relies on the Financial Data Exchange (FDX) and OAuth 2.0 application frameworks. QuickBooks never stores your actual Chase username and password.

Instead, when you connect your accounts, QuickBooks opens a secure session with Chase. You authenticate on Chase’s site, and Chase passes an encrypted token back to QuickBooks:

[QuickBooks Desktop] ---- Initiates Update Request ----> [Chase Security Gateway]
                                                                  |
                                                       Token Invalid / Blocked
                                                       (Password Changed / Expired App)
                                                                  |
[QuickBooks Desktop] <--- Returns Error 103 <---------------------+
(Prompts for New Credentials)

Error 103 occurs when Chase’s gateway rejects this exchange. This happens if you change your Chase password (which instantly revokes all existing access tokens), if your business profile requires an administrative login rather than an employee login, or if Chase flags the incoming connection request for additional identity verification.

Diagnostic Flowchart: Chase Error 103 Decision Path

  1. Test credentials on Chase.com directly.
    • Can you sign in to your Chase account through a regular browser without security alerts?
      • No: Your Chase account has an active credential issue, password reset requirement, or security hold. Resolve it with Chase first.
      • Yes: Proceed to step 2.
  2. Review third-party app permissions.
    • Under your Chase Profile & Settings, is QuickBooks listed with access granted to all relevant checking, savings, and credit card accounts?
      • No: Toggle permissions to “Active” for all accounts you want to track, then retry the sync.
      • Yes: Proceed to step 3.
  3. Determine Chase account type.
    • Are you managing a Chase Commercial Banking account using a physical security token (J.P. Morgan Access)?
      • Yes: Standard desktop bank feeds cannot use consumer/business credentials. You must use Direct Connect with treasury credentials or import files manually.
      • No: The desktop connection cache is out of date. Follow the deactivation and re-linking steps below.

Differential Diagnosis: Don’t Confuse Chase Error 103 With…

Step-by-Step Repair Guide for Chase Accounts

Follow these steps in order to re-authorize Chase and restore automated transaction downloads.

Step 1: Confirm Your Chase Login Credentials

Before changing settings in QuickBooks, confirm that your login works outside the software:

  1. Open a web browser in Incognito/Private mode.
  2. Go directly to www.chase.com.
  3. Sign in with your primary business or commercial username and password.
  4. Important: If Chase prompts you to verify your identity via a text code, accept updated disclosures, or change an expiring password, complete those steps immediately.
  5. Once your account summary dashboard loads cleanly, sign out.

Step 2: Verify Third-Party Permissions in Chase

Chase requires account owners to explicitly authorize third-party financial applications:

  1. Sign back into your Chase online account.
  2. Click the Profile & Settings icon (the person silhouette) in the top-right corner.
  3. Select Security & Privacy, then click Linked Apps & Websites (or Manage Linked Apps).
  4. Locate Intuit or QuickBooks in the list of applications.
  5. Confirm that its access status is set to Sharing.
  6. Check that every bank and credit card account you need to download into QuickBooks is selected. If a new card was recently issued, it may be unchecked by default.
  7. Save your settings and sign out of Chase.

Step 3: Refresh the Chase Connection in QuickBooks Desktop

Now that your permissions are active on Chase’s site, update the connection in QuickBooks:

  1. Open QuickBooks Desktop and go to Banking > Bank Feeds > Bank Feeds Center.
  2. Select your Chase account.
  3. Click Edit Account Info (or choose Update if an alert banner is visible).
  4. When the embedded browser opens, enter your Chase username and password.
  5. If Chase prompts you for a two-factor verification code via SMS or email, enter it immediately.
  6. When prompted to confirm account access, verify that each bank account is linked to the correct QuickBooks ledger account.
  7. Click Confirm to finalize the authorization.

If the in-app update still displays Error 103, the stored authentication profile in your company file may be corrupted:

  1. Go to Lists > Chart of Accounts.
  2. Right-click your Chase account and select Edit Account.
  3. Under the Bank Feed Settings tab, select Deactivate All Online Services. Click Save & Close.
  4. Repeat this step for any other Chase accounts linked under the same login credentials.
  5. Close and restart QuickBooks Desktop.
  6. Return to Banking > Bank Feeds > Set Up Bank Feed for an Account.
  7. Type Chase in the search field, log in, and complete the connection wizard.
  8. Crucial: Map each Chase account to your existing general ledger accounts in QuickBooks. Do not create new accounts.

What to Do if Chase Online Sync Remains Blocked

If Chase has placed a temporary security hold on third-party aggregators, you can continue updating your books manually while the hold clears:

  1. Log into your Chase online banking portal.
  2. Select your checking or credit card account, click Download Activity, choose QuickBooks (.QBO), and select your date range.
  3. Import the file directly into your ledger by following Sync Failure: How to Manually Upload .QBO Files to QuickBooks.
  4. If transaction updates continue to fail across other institutions as well, review Manual Fix: 5 Steps to Resolve QuickBooks Bank Feeds Not Updating.

Hard Stop: When to Escalate to Chase

If you have verified that your password is correct, confirmed that linked app sharing is enabled, and reset the connection in a clean sample company file, but Chase continues returning Error 103:

  • The issue may be caused by an administrative security hold on your online profile.
  • Call Chase Online Banking Support (1-877-CHASE5) and ask for the Digital Integration Support Team.
  • Tell the representative: “Our third-party accounting connection through Intuit is receiving an authorization rejection (Error 103). Please verify whether our online profile has an external data-sharing block or security restriction active on third-party aggregators.”

Closing the Books

Chase Error 103 is an authorization issue, not a data corruption problem. By confirming your credentials on Chase’s site, verifying third-party app permissions, and re-linking the account in QuickBooks, you can restore your automated Chase bank feeds quickly and safely.

Manual Fix: 5 Steps to Resolve QuickBooks Bank Feeds Not Updating

October 6, 2026

QuickBooks Error OL-301: Fixing Desktop Web Connect Connectivity

October 6, 2026

QuickBooks Error 9999: Fixing Script Errors in Bank Feed Sync

October 6, 2026