QuickBooks Error 350 occurs when the Open Authorization (OAuth) connection between QuickBooks and your financial institution has expired, been revoked, or become invalid. This happens when security credentials change, token lifespans end, or the bank updates its third-party connection policies. QuickBooks cannot download new transactions until you re-authorize the link. To fix Error 350, click the re-authorization prompt within your Bank Feeds window to launch your bank’s secure login portal, enter your credentials, and grant QuickBooks updated access permissions.
Fast-Fix: The 45-Second Solution
To resolve Error 350, go to your Bank Feeds Center, locate the affected bank account, and select “Update” or “Sign In.” A secure browser window will open displaying your bank’s login screen. Enter your primary online banking credentials, complete any multi-factor authentication steps, and click “Agree” or “Confirm” to issue a fresh digital security token. Once re-authorized, your bank feed sync will resume immediately.
Quick Status & Triage Snapshot
- Data Risk Tier: Low. Error 350 is an authentication token expiration. Your historical transactions, general ledger, and account balances inside QuickBooks are completely secure.
- Multi-User Impact: Account-wide for transaction downloads. While all users can continue recording manual transactions, no user can download live bank data for that institution until the token is renewed.
- Common Trigger: Routine security token expiration (typically every 90 to 365 days), a recent online banking password change, or an update to your bank’s third-party app security settings.
- Estimated Fix Time: 3 to 5 minutes.
Technical Anatomy: How OAuth Tokens Work and Why They Expire
Modern financial institutions use OAuth 2.0 protocol rather than storing your raw bank username and password inside QuickBooks.
When you initially connect your bank feed, your financial institution generates an encrypted token. This token acts as a digital keycard: it grants QuickBooks limited, read-only access to transaction history without exposing your actual login credentials.
[QuickBooks Desktop] ---- Sends Expired Token ----> [Bank API Server]
|
Token Expired/Revoked
|
[QuickBooks Desktop] <-- Returns Error 350 <----------------+
(Prompts Re-Authentication)
OAuth tokens are intentionally programmed with expiration dates. Furthermore, if you change your banking password, update multi-factor authentication settings, or if the bank updates its API framework, the existing token is invalidated immediately for safety. When QuickBooks attempts to sync using an invalid token, the bank server returns an authorization error, which QuickBooks maps as Error 350.
Diagnostic Flowchart: Error 350 Decision Path
- Check the Bank Feeds window.
- Does a banner state “Needs Attention” or “Verify your account”?
- Yes: Click the prompt, log in through the pop-up portal, and grant access.
- No: Proceed to step 2.
- Does a banner state “Needs Attention” or “Verify your account”?
- Review recent credential changes.
- Did you or another administrator update the online banking password recently?
- Yes: The old token was invalidated. Deactivate the online feed and re-link the account using the new password.
- No: Proceed to step 3.
- Did you or another administrator update the online banking password recently?
- Inspect bank-side permissions.
- Log directly into your bank’s portal via browser. Under “Third-Party App Access” or “Security Settings,” is Intuit/QuickBooks listed as disconnected or expired?
- Yes: Re-enable access permissions inside the bank portal, then re-sync QuickBooks.
- No: The desktop connection cache may be damaged. Clear temporary internet files or reset the bank connection.
- Log directly into your bank’s portal via browser. Under “Third-Party App Access” or “Security Settings,” is Intuit/QuickBooks listed as disconnected or expired?
Differential Diagnosis: Don’t Confuse Error 350 With…
- QuickBooks Error 103: Indicates that the username or password entered does not match the bank’s records. Error 350 means your connection was previously authorized, but the security token itself has expired. If credentials are actively failing, consult QuickBooks Error 103: Fixing Invalid Login & Device Recognition Issues.
- QuickBooks Error 108: Occurs when your login works, but an unacknowledged security message or terms update on the bank’s website is blocking data transmission. See QuickBooks Error 108: Clearing Bank Website Security Notices & Actions.
- QuickBooks Error 324: Indicates that the login succeeded and the token is valid, but the specific account number or credit card ID cannot be found. See QuickBooks Error 324: Reconnecting Renamed or Replaced Bank Accounts.
Step-by-Step Repair Guide
Follow these steps in order to refresh the authorization token and re-establish transaction downloads.
Step 1: Execute the In-App Re-Authorization
The fastest path to resolving Error 350 is renewing the token directly through QuickBooks:
- Open QuickBooks Desktop.
- Navigate to Banking > Bank Feeds > Bank Feeds Center.
- Locate the financial institution displaying the alert icon.
- Click Verify your account (or Update).
- A secure dialog box from your bank will appear within QuickBooks.
- Enter your online banking username and password.
- Complete the Multi-Factor Authentication (MFA) step if your bank texts or emails a verification code.
- When presented with the authorization screen, check all relevant accounts and click Allow or Connect.
- Allow QuickBooks to complete the handshake and confirm the connection is active.
Step 2: Clear Temporary Internet Files and Browser Data
QuickBooks Desktop relies on Windows Internet components and Edge WebView2 to render the bank’s OAuth pop-up login screens. If outdated session cookies are stored locally, the login window may fail to refresh the token properly.
- Close QuickBooks Desktop.
- On your keyboard, press Windows Key + R to open the Run command.
- Type
inetcpl.cpland press Enter to open Internet Properties. - On the General tab, find the Browsing history section and click Delete….
- Ensure Temporary Internet files and website files and Cookies and website data are checked.
- Click Delete, then select OK.
- Reopen QuickBooks and repeat Step 1.
Step 3: Deactivate and Reactivate Bank Feeds
If the in-app update button fails to refresh the token or spins endlessly, disconnecting and reconnecting the account register clears the corrupted token locally.
- Go to the Lists menu and select Chart of Accounts.
- Locate the account associated with Error 350, right-click it, and select Edit Account.
- Select the Bank Feed Settings tab.
- Select Deactivate All Online Services, then click Save & Close. Confirm any warning prompts.
- Exit QuickBooks and restart your computer to clear lingering service processes.
- Reopen QuickBooks, navigate to Banking > Bank Feeds > Set Up Bank Feed for an Account.
- Type the name of your financial institution, follow the prompts to sign in, and complete the OAuth authorization screen.
- Critical Step: In the account matching window, ensure you choose Use Existing QuickBooks Account and map to your existing ledger account. Do not create a duplicate account.
What to Do If Token Renewal Continues to Fail
If your bank displays an error during the OAuth web redirect (such as a blank window or an HTTP 400/500 error), the bank’s authorization server may be temporarily down or undergoing maintenance.
To keep your reconciliations on schedule while waiting for the bank’s OAuth API to clear:
- Log in to your bank’s website via an ordinary browser window.
- Export your cleared activity as a Web Connect file (.QBO).
- Import the file manually into QuickBooks by following Sync Failure: How to Manually Upload .QBO Files to QuickBooks.
- If transaction updates continue to fail across multiple accounts, review Manual Fix: 5 Steps to Resolve QuickBooks Bank Feeds Not Updating.
Hard Stop: When to Escalate to Your Financial Institution
If completing the OAuth login screen results in an error message that explicitly states “Application Not Supported,” “Invalid Client ID,” or “Access Restricted by Account Administrator,” stop attempting to re-authenticate inside QuickBooks.
This message indicates that your financial institution has altered its enterprise application permissions. Contact your bank’s treasury management or commercial online banking support. Instruct them to verify that Intuit Data Feeds / QuickBooks Desktop has administrative clearance to connect to your commercial accounts.
Closing the Books
QuickBooks Error 350 is not a sign of data corruption; it is a routine security measure designed to protect your banking data. When an authorization token runs its course or security settings change, re-authenticating with your bank ensures your accounting data continues to flow safely and uninterrupted.