Data Service Team

QuickBooks Error 350 occurs when the secure connection between QuickBooks Online and a connected bank or credit card account expires or stops working. It usually means the account needs to be reauthorized before QuickBooks can resume downloading transactions. The error is generally related to bank-feed authentication rather than a damaged company file. To fix QuickBooks Error 350, open All apps → Accounting → Bank transactions, select the affected account, click Fix now, confirm your bank sign-in details, complete any required security verification, and select Save and connect. If the error keeps returning, check whether the bank requires additional authorization or whether multiple QuickBooks companies share the same bank login. This guide explains how to resolve Error 350, prevent recurring bank-feed interruptions, and safely verify that transactions are downloading correctly. What Does QuickBooks Error 350 Mean? QuickBooks Error 350 indicates that the existing authorization between QuickBooks and your financial institution has expired or is no longer valid. The bank may require you to sign in again, approve access, or accept updated security terms before transaction downloads can continue. Banks control their own authorization policies. Some connections may require reauthorization every 90 business days, while others may require it at different intervals. The timing depends on the financial institution and its connection method. Important: Error 350 does not, by itself, establish that your company file is damaged or that your existing accounting records have been deleted. It primarily interrupts automatic bank-feed updates. However, you should still review the transaction history in QuickBooks and at your bank to identify any missing downloads. Common Causes of QuickBooks Error 350 Understanding the cause helps you choose the right fix instead of repeatedly reconnecting the same account. 1. Expired bank authorization The bank's security authorization may expire after a specified period. QuickBooks then needs renewed permission to access the account and download transactions. 2. Updated bank security requirements A bank may introduce new authentication procedures, multifactor verification, revised terms, or updated permissions for third-party applications. Until the required steps are completed, the existing connection may not work. 3. Changed bank login credentials A password or username change can require the bank connection to be authenticated again. Even if you can access QuickBooks normally, the saved bank authorization may no longer be valid. 4. Incomplete account selection during reconnection During reauthorization, the bank may display a list of checking, savings, or credit card accounts. Selecting an incomplete set of accounts can leave some existing QuickBooks connections unable to access the accounts they need. If the bank provides an All Accounts option and the login is shared across multiple QuickBooks companies, select it when appropriate, then carefully verify the account mapping. 5. Multiple QuickBooks companies sharing one bank login Some banks limit how connected applications or authorization sessions can be used. If several QuickBooks companies share the same bank credentials, reconnecting from one company may affect access from another, depending on the bank's connection rules. This is not a universal behavior for every bank. If Error 350 repeatedly shifts between companies, investigate the shared login and account-selection process before reconnecting each company again. 6. Browser or authentication-session problems Cached browser data or an incomplete sign-in session can sometimes interfere with the authorization process. A private browsing window is a useful diagnostic step if the normal reconnection attempt fails. Fix 1: Reconnect the Bank Account Using Fix Now Start with this method because it renews the existing connection without requiring you to disconnect the account. Sign in to QuickBooks Online. Open All apps, select Accounting, and choose Bank transactions. Find the bank or credit card account displaying Error 350. Select the affected account and click Fix now. Confirm or re-enter the username and password used on your bank's website. Complete any security verification or authorization prompts. Review the accounts presented by the bank and select the appropriate accounts. Select Save and connect. If QuickBooks confirms that the connection is complete and transactions have been updated, select Close. Return to Bank transactions and confirm that the error has cleared. Review the downloaded transactions before adding or matching them to your books. Why this works: Reauthorization renews the permission QuickBooks needs to retrieve bank transactions. It is generally preferable to disconnecting the account immediately. Fix 2: Ask the Original Connection User to Reauthorize If the Error 350 message includes Send a request, the person currently signed in may not be the user who originally established the connection. Follow these steps: Locate the Error 350 message in Bank transactions. Select Send a request, if available. Ask the original connection user to check their email for the authorization request. Have that person follow the request and complete the bank reconnection process. Return to QuickBooks and confirm that the account updates successfully. This approach can help organizations where a bookkeeper, accountant, or company administrator originally established the connection. Do not share bank passwords or one-time verification codes with coworkers. The authorized user should complete the authentication process through the appropriate sign-in flow. Fix 3: Use a Private Browser Window If Fix now fails repeatedly, test whether the problem is related to the browser session. Open a private or incognito browser window. Sign in to QuickBooks Online. Open All apps → Accounting → Bank transactions. Select the affected account and try Fix now again. Complete the bank's authentication prompts. If the reconnection works in the private window, browser cache or session data may have contributed to the problem. You can then clear the relevant browser cache and cookies, close the browser, reopen it, and sign in again. If the error remains, do not assume the browser is responsible. Continue with the bank-account and authorization checks below. Fix 4: Disconnect and Reconnect the Bank Feed Use this method only if the standard reconnection process fails and you have reviewed the transactions already downloaded into QuickBooks. Step 1: Review downloaded transactions Open Bank transactions and review the pending or For Review transactions for the affected account. Categorize, match, or otherwise resolve transactions that are ready to be processed. This step reduces the risk of creating duplicate entries or overlooking transactions after reconnecting. Step 2: Disconnect the account Open Bank transactions and locate the affected account. Select the account's edit or pencil icon. Choose Edit account info or the equivalent account-editing option shown in your interface. Select Disconnect this account on save. Save the change. Menu labels may vary by QuickBooks interface. Disconnecting the bank feed is not the same as deleting the accounting account from the chart of accounts. Do not delete the account merely to clear Error 350. Step 3: Reconnect the account Return to Bank transactions. Select Link account. Search for your financial institution. Sign in using the bank's official authentication process. Select the correct bank accounts and map them to the existing QuickBooks accounts. Complete the authorization and connection steps. Step 4: Verify the result Check the latest download date and review the new transactions. Match downloaded entries against existing transactions before adding anything new. If the bank offers an account-selection option such as All Accounts, review that option carefully, particularly if the same login supports multiple QuickBooks companies. Fix 5: Stop Error 350 From Returning Across Multiple Companies If several QuickBooks companies use the same bank login and Error 350 keeps returning after reconnection, investigate how the bank handles simultaneous authorizations and account access. A practical approach is to designate one authorized person to manage bank-feed setup and reconnection across the affected companies. This person can coordinate account selection, reauthorization, and connection changes to reduce conflicting updates. Other team members can continue reviewing, categorizing, matching, and reconciling transactions according to their permissions. They should avoid repeatedly changing the bank connection while the designated person is resolving the issue. Before reconnecting, confirm that the intended bank accounts are available and selected. Where the bank supports it, make sure the authorization includes all accounts required by the relevant QuickBooks companies. Key point: A shared bank login is a possible explanation for recurring errors, not proof of the cause. If the problem continues, confirm the bank's connection limits and ask the bank or QuickBooks support to investigate the specific setup. Fix 6: Check the Bank Website Before Trying Again Sometimes the issue cannot be resolved from QuickBooks alone because the bank requires an action on its own website. Open your bank's website in a separate browser tab and verify that: You can sign in successfully. No security challenge or multifactor authentication request is waiting. No updated terms or third-party access consent needs approval. The relevant bank account is open and accessible. The bank has not announced a service interruption affecting connected applications. Complete any required bank-side steps, then return to QuickBooks and try the connection again. If you cannot sign in directly to the bank, contact the bank first. QuickBooks cannot complete authorization while the financial institution is denying access. How to Check for Missing or Duplicate Transactions After Error 350 Resolving the connection does not automatically confirm that every transaction is recorded correctly. Perform a brief reconciliation check after the bank feed resumes. Note the last successful bank-feed download date. Compare the transaction history on the bank website with the transactions available in QuickBooks. Identify transactions from the period when the connection was interrupted. Review the For Review or pending transaction list. Match downloaded transactions to existing entries wherever appropriate. Add only transactions that are genuinely missing from the books. Review the account reconciliation to confirm that the recorded balance agrees with the bank statement. If automatic downloads leave a gap, ask whether your bank supports a manual transaction export and whether your QuickBooks version accepts the available file format. Import only the missing date range when possible, and review duplicates carefully before finalizing the import. Can You Continue Working While Error 350 Is Active? Yes, you can usually continue working with existing QuickBooks records while the bank feed is unavailable. However, newly posted bank transactions may not appear automatically until the connection is restored. For time-sensitive bookkeeping, use your bank statement or an authorized transaction export to identify activity that has not been downloaded. Follow your organization's procedures for recording and matching those transactions, and avoid importing the same activity twice. If you are approaching a reconciliation deadline, verify the date of the last successful download and account for the missing period before marking the reconciliation complete. When to Contact the Bank or QuickBooks Support Contact your bank if you cannot sign in, the bank requests additional approval, the account is unavailable, or the bank reports a connection outage. Seek QuickBooks support if the bank website works normally but Error 350 persists after reauthorization, if the required accounts do not appear during connection, or if multiple companies continue to lose access after coordinated reconnection attempts. Before requesting assistance, gather the exact error message, the affected bank and account type, the last successful download date, the steps already attempted, and whether other QuickBooks companies use the same bank login. Never send your bank password, one-time verification code, or full account number in a support request. Frequently Asked Questions About QuickBooks Error 350 1. What is QuickBooks Error 350? QuickBooks Error 350 indicates that the secure connection to a bank or credit card account has expired or is no longer working. Reauthorization is usually required to resume automatic transaction downloads. 2. Does Error 350 mean my company file is damaged? No. Error 350 primarily identifies a bank-feed connection problem. The error alone does not establish that the company file is damaged or that accounting records have been lost. 3. How do I fix QuickBooks Error 350 quickly? Open All apps → Accounting → Bank transactions, select the affected account, choose Fix now, complete the bank sign-in and authorization steps, and select Save and connect. 4. Why does Error 350 keep coming back? Possible causes include recurring authorization requirements, incomplete bank-account selection, unresolved bank security prompts, or connection limitations when several QuickBooks companies share a bank login. Identify which condition applies before repeating the same fix. 5. How often must I reconnect my bank? There is no single schedule for every bank. Reauthorization timing depends on the financial institution, its security policies, and the type of connection being used. 6. Should I disconnect my bank account immediately? No. Try Fix now first. If you need to disconnect and reconnect, review downloaded transactions beforehand and verify that the bank account maps to the correct existing QuickBooks account. 7. Can Error 350 cause duplicate transactions? The error itself does not necessarily create duplicates. However, reconnecting or importing transactions without reviewing existing entries can lead to duplicates. Match downloaded activity against existing records before adding it. 8. What if Fix now does not work? Try a private browser window, check for pending security prompts on the bank website, and verify that the correct accounts are selected. If the connection still fails, consider a careful disconnect-and-reconnect process or contact the appropriate support team. Conclusion: Resolve QuickBooks Error 350 and Restore Bank Feeds QuickBooks Error 350 usually means that your bank-feed authorization needs to be renewed. Start with Fix now, complete the bank's security requirements, and verify that the correct accounts are connected. If the problem persists, test a private browser session, check for bank-side prompts, and investigate account-selection or shared-login issues before disconnecting the feed. After the connection is restored, compare the downloaded transactions with your bank activity, match existing entries, and investigate any gaps before completing reconciliation. If QuickBooks Error 350 continues to interrupt bookkeeping, bank-feed updates, or month-end reconciliation, the Data Service Team can help troubleshoot the connection and identify the next appropriate steps. Need help resolving QuickBooks Error 350? Call +1-(888)-718-7888 for assistance with bank-feed troubleshooting and QuickBooks errors.