QuickBooks Online Error 350: How to Renew Your Bank’s OAuth Connection

October 13, 2026 6 min read

QuickBooks Online Error 350 occurs when the Open Authentication (OAuth) token connecting Intuit to your financial institution has expired, revoked its permissions, or encountered updated server protocols at your bank. When this happens, automated transaction downloads stop completely. To resolve Error 350, you must re-authenticate your banking credentials directly through your bank’s secure sign-in portal within QuickBooks Online to generate a fresh security token.

Fast-Fix: The 45-Second Solution

To fix QuickBooks Online Error 350, select Transactions > Bank transactions, locate the affected account displaying the error, and click “Verify your account” or “Sign in.” When your bank’s secure portal opens in a pop-up window, enter your online banking credentials, complete any multi-factor verification, and grant Intuit permission to sync. Once authorized, click Update to resume your automated bank feed.

Quick Status & Triage Snapshot

Diagnostic MetricAssessment
Data Risk TierZero Risk: Already categorized ledger entries and reconciled transactions are unaffected.
Multi-User ImpactAccount-Wide: Automated downloads stop for all company users until an admin re-authenticates the feed.
Common TriggerExpired 90-to-365-day security tokens, bank security profile updates, or password resets on your bank portal.
Estimated Fix Time3 to 5 minutes.

Diagnostic Flowchart: Error 350 Decision Path

[Error 350 Banner Displays]
           │
           ▼
Does the bank card show "Verify your account" or "Sign in"?
     ├─► YES ──► Complete bank portal login & MFA.
     │            │
     │            ├─► Connection succeeds ──► Click "Update" (Resolved)
     │            └─► Loop/Blank window occurs ──► Open QBO in Incognito Mode
     │
     └─► NO (Button missing) ──► Go to "Edit account info" > Check "Disconnect this account on save"
                                   │
                                   └─► Reconnect via "Link account" with fresh OAuth token

Is Your Data at Risk?

Error 350 carries no risk of data loss for existing transactions. The issue is strictly an authorization handoff failure between Intuit’s servers and your bank’s API.

  • Existing Register Data: Every transaction previously matched, added, or reconciled in your register remains permanently saved.
  • Pending Transactions: Transactions waiting in the “For Review” tab are preserved.
  • New Transactions: Financial activity occurring at your bank while Error 350 is active will backfill automatically once the connection is renewed.

Do not delete the affected account from your Chart of Accounts. Doing so wipes your historical general ledger balances. Disconnecting and reconnecting the bank feed is safe; deleting the account is not.

Technical Anatomy: What Error 350 Means

Most major financial institutions—including Chase, Bank of America, and Wells Fargo—use OAuth 2.0 API standards instead of screen scraping. Instead of storing your bank username and password, QuickBooks Online receives a secure, encrypted digital token from your bank.

This token acts as a revocable key allowing Intuit to download read-only transaction data. These tokens expire periodically by design—frequently every 90 days, 180 days, or whenever you update your banking password. When the token expires or your bank rolls out an API security update, Intuit’s API requests are rejected with a 350 status code: Token Expired or Invalid Authorization.

Differential Diagnosis: Don’t Confuse This With…

Step-by-Step Repair Guide

Step 1: Re-Authorize the OAuth Connection in QuickBooks Online

  1. In QuickBooks Online, navigate to Transactions (or Bookkeeping) and select Bank transactions.
  2. Select the blue card for the account showing Error 350.
  3. Click the link on the alert banner that reads Verify your account, Sign in, or Update connection.
  4. A secure window from your financial institution will launch. Enter your banking username and password.
  5. Complete your bank’s multi-factor authentication (SMS code, email push, or hardware token).
  6. Check the boxes beside the accounts you want to connect to QuickBooks.
  7. Click Confirm, Allow, or Authorize.
  8. Once the window closes, click Update in the top right corner of the Bank transactions dashboard.

Step 2: Clear Browser Redirect Conflicts (If the Sign-In Window Loops)

If clicking “Verify your account” results in a white screen, an infinite spinner, or redirects you back to QuickBooks without establishing a connection, your browser’s cached cookies are interfering with the OAuth handshake.

  1. Open your browser in a private or incognito window.
  2. Sign in to your QuickBooks Online account.
  3. Attempt the OAuth re-authorization described in Step 1.
  4. If it succeeds in incognito mode, clear your primary browser’s cache and cookies. For step-by-step instructions, see Cache & Cookies: How to Clear Browser Data Specifically for Intuit.

Step 3: Disconnect and Reconnect the Online Banking Feed

If the re-authorize button fails to clear the 350 error code, reset the handshake by disconnecting and reconnecting the feed:

  1. In Bank transactions, select the tile for the affected account.
  2. Click the Pencil icon (Edit) on the account tile, then select Edit account info.
  3. Scroll down and check the box marked Disconnect this account on save.
  4. Click Save and Close. The account card will disappear from the bank feed screen (your register transactions remain intact).
  5. From the top-right corner, click Link account.
  6. Search for your bank and enter your credentials via the OAuth authorization window.
  7. Carefully link each bank account to its existing counterpart in your Chart of Accounts. Do not create a new account in QuickBooks.
  8. Set the download date range to match the day after your last imported transaction to prevent duplicates.

If your connection issues are specifically tied to large institutional changes, follow our bank-specific guides:

Hard Stop: When to Call an Expert or Switch to Manual Uploads

If you re-authorize the account and the bank portal confirms access, but QuickBooks Online immediately throws Error 350 again, your bank’s Open Banking API bridge may be undergoing an internal migration.

  • The Immediate Workaround: Do not spend hours reconnecting repeatedly. Download a .QBO or .CSV file directly from your bank’s online website, then import it directly into QuickBooks Online using our walkthrough: Manual Import Guide: How to Upload .CSV and .QBO Files to QuickBooks.
  • The Escalation Point: If the account has been disconnected and reconnected twice and continues throwing Error 350 across multiple browsers, open a ticket with Intuit Support to verify whether your financial institution has changed its API endpoint identifier.

Closing the Books

Bank feed disconnects are inconvenient, but Error 350 is a safety mechanism rather than a sign of software failure. As long as you never delete the account directly from your Chart of Accounts, your general ledger remains safe while you renew the authentication token.

QuickBooks Online Error 103 Fix: Fixing Invalid Login & Device Recognition

August 6, 2026

QuickBooks Online Error 102: Troubleshooting Bank Server Maintenance Issues

July 2, 2026

QuickBooks Online Error 101: How to Resolve Bank Connection Timeouts

July 2, 2026