Free tools Windows power users keep installed
One-click scans. No signup required.
Most QuickBooks Online bank-feed failures are fixed by checking access at the bank first, then using the error-specific action in All apps → Accounting → Bank transactions. Do not disconnect an account just because a feed stopped. Sign in to the bank’s website, confirm the account is open and usable, look for a security or terms prompt, and then select Update in QuickBooks. Use the code shown on screen to decide whether you need to verify credentials, reauthorize access, or map an account that changed.
The procedures below cover the common codes 101, 102, 103, 105, 324 and 350, including safe reconnection when several QuickBooks companies share one bank login.
As an Amazon Associate I earn from qualifying purchases.
Start with a safe 10-minute triage
Bank feeds depend on two systems: the bank must permit access and QuickBooks must have a valid authorization to retrieve transactions. Checking both sides prevents an unnecessary disconnect that can create a second problem.
Recommended Free Tools
- Open the bank’s own website in a separate tab. Sign in with the same user ID you use for the feed. Complete any security question, one-time-code request, password change, updated-terms acknowledgement or account alert. If the bank’s site will not let you sign in, resolve that with the bank before changing QuickBooks.
- Confirm the account is open and active. Intuit’s Error 101 guidance treats an account as active when it has a balance or transactions within the previous 12 months. A closed, dormant or restricted account cannot provide a normal feed.
- Check the bank’s status and transaction pages. Make sure the account page loads and recent transactions are visible. A bank outage or maintenance window can make a valid QuickBooks connection appear broken.
- Request a manual refresh. In QuickBooks Online, select All apps → Accounting → Bank transactions, choose the affected account and select Update. Most banks update with QuickBooks about every 24 hours, but the interval varies by institution, so an update request does not guarantee an immediate new transaction.
- Read the exact code before reconnecting. A private or incognito browser window, or another supported browser, can show whether a stale session is involved. Treat that as a diagnostic step; it cannot repair a bank outage, an invalid password or an expired authorization.
- Record what changed. Note the bank, account type, displayed code, recent password or account-number changes, and whether another QuickBooks company uses the same bank credentials. This information determines the safest recovery path and helps support avoid repeating steps.
If bank access fails, the bank is the first escalation point. If bank access works and the code-specific procedure below still fails, contact QuickBooks support with the recorded details.
#1 Best Overall
Choose the route that matches the displayed error
| Error | What it generally indicates | Best starting route |
|---|---|---|
| 101 | Inactivity or a bank-side prompt; there is no single cause for every 101. | Sign in at the bank, handle prompts, verify activity, then refresh. |
| 102 or 105 | QuickBooks cannot connect to the bank at that moment. | Check the bank’s site and notifications, select Update, then wait and retry if the bank is resolving an issue. |
| 103 | The bank rejected the user ID or password supplied for the connection. | Prove the credentials at the bank’s site, then reconnect with the confirmed login. |
| 324 | QuickBooks cannot find the previously connected account. | Determine whether account details, credentials or the selected account set changed before using Fix now. |
| 350 | The secure authorization between QuickBooks and the bank expired or no longer works. | Use Fix now, reauthorize and save the connection with the correct account selection. |
The code identifies a likely failure mode, not a promise that one action will work in every case. Bank-specific authentication, account types and maintenance windows can change the result.
Fix Error 101: inactivity or a required bank action
Error 101 has several possible causes. Intuit’s current U.S. guidance, updated August 24, 2026, directs you to verify the account at the bank and complete any pending request before refreshing QuickBooks (Intuit’s Error 101 instructions).
Step 1: complete the bank’s prompt
After signing in directly at the bank, look for revised terms, a consent screen, a security-profile update, a password prompt or a message asking you to confirm personal details. Complete the prompt in the bank’s environment; do not try to answer it inside a QuickBooks error dialog.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Step 2: verify the account is active
Open the specific account, not merely the bank’s landing page. Confirm that it remains open and that it has a balance or transaction activity within the last 12 months. If the bank has closed or restricted it, ask the bank how to restore access or confirm the closure before touching the QuickBooks connection.
Step 3: refresh after the bank action
Return to All apps → Accounting → Bank transactions and select Update. If the feed remains at Error 101 even though the bank login and account are usable, try a private browser window to rule out a session problem, then contact support with the code and the date you completed the bank prompt.
Fix Errors 102 and 105: QuickBooks cannot connect
Errors 102 and 105 mean QuickBooks cannot establish a connection to the bank. The official procedure is to inspect the bank’s website and request an update rather than immediately deleting the connection (Intuit’s Error 102 and 105 guidance).
Check whether the bank is reachable
Sign in at the bank and open the account’s transaction view. Read any service bulletin, maintenance notice or fraud-verification request. If the bank’s own pages are unavailable, the feed may recover only after the bank restores its service.
Request an update in QuickBooks
In All apps → Accounting → Bank transactions, select the affected account and choose Update. Watch for a new timestamp or a changed status. This requests a connection attempt; it does not force the bank to publish transactions that are still pending or outside its normal release schedule.
Allow time for a bank-side incident
Intuit notes that a bank may need 24 hours or more to resolve the condition and recommends retrying after a short wait when the bank is working on an issue. There is no fixed resolution window that applies to every institution. If the bank is reachable, no prompt is pending and repeated updates still produce 102 or 105, escalate with the code and your bank’s confirmation that the account is accessible.
Fix Error 103: verify the bank credentials
Error 103 usually means the user ID or password entered for the bank connection is incorrect. Intuit’s U.S. article, updated August 4, 2026, instructs users to verify the login directly with the bank before retrying QuickBooks (Intuit’s Error 103 instructions).
- Open the bank’s website yourself and enter the credentials there. Use the bank’s normal sign-in page, not a link supplied in an unexpected message.
- If the bank rejects the login, use the bank’s own recovery process or call the bank. Do not guess repeatedly, and never send your password to a colleague, QuickBooks support representative or anyone else.
- Once the direct sign-in succeeds, return to the QuickBooks banking connection and enter that same confirmed user ID and password. Complete any multi-factor challenge in the bank’s authentication window.
- Save the connection and run an update. If the bank login works in a browser but QuickBooks still returns 103, capture the exact code, the bank name and the time of the successful bank sign-in for support.
Fix Error 324: QuickBooks cannot find the account
Error 324 appears when QuickBooks can no longer locate the bank account that was connected, even though the bank itself may still be active. Intuit lists changed account details, different credentials and selecting a different group of accounts during reauthorization as possible scenarios. Its guidance was updated August 21, 2026 (Intuit’s Error 324 instructions).
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Identify which detail changed
- Account details changed: The bank may have converted, renumbered or replaced the account.
- Credentials changed: The original connection may have used a different bank login, profile or business entity.
- Account selection changed: During authorization, only some accounts may have been shared, so QuickBooks cannot see the one previously mapped.
Compare the account name and last four digits shown at the bank with the account listed in QuickBooks. Do this before disconnecting anything; deleting the old connection can make it harder to determine which QuickBooks account held the existing history.
Use Fix now and preserve the QuickBooks account
- In Bank transactions, locate the account showing 324 and choose Fix now.
- Sign in with the bank credentials that currently open the intended account.
- When the bank asks which accounts to share, choose All Accounts or Consent All when that option is presented. This allows QuickBooks to see the account needed for mapping.
- When QuickBooks displays the discovered accounts, map the updated bank account to the existing QuickBooks account rather than creating a duplicate, provided the account is the same real-world account with changed details.
- Save the connection and review the downloaded transactions for the correct account before accepting or categorizing them.
Take extra care with several QuickBooks companies
If multiple QuickBooks companies use one bank login, the account choices made during authorization can affect more than the company currently on screen. Intuit recommends that one person manage the connection and select All Accounts during authorization. Coordinate the change with the other company owners, then check each company’s feed after the reconnection.
Fix Error 350: reauthorize an expired secure connection
Error 350 means the secure connection between QuickBooks and the bank has expired or is no longer valid. Intuit’s instructions, updated August 21, 2026, use the Fix now workflow (Intuit’s Error 350 instructions).
- Open All apps → Accounting → Bank transactions and select the affected account.
- Choose Fix now.
- Confirm or re-enter the bank sign-in details and complete the bank’s authentication request.
- Select Save and connect.
- Review the account list and choose the intended accounts, using All Accounts when offered so the existing account can be found and mapped correctly.
Reauthorization timing is controlled by the bank. Intuit gives examples ranging from every 90 business days to every 18 months; neither interval is universal. A new 350 can therefore be a normal authorization renewal rather than evidence that your password is wrong.
Reconnect without losing the intended account
Disconnecting is a last resort, not the first response to a red error banner. Before changing a connection, write down the QuickBooks account name, the bank account’s last four digits, the login profile used and the other companies that share that profile.
Use this decision sequence
- Bank login fails: stop and resolve access with the bank.
- Bank login works and a prompt appears: complete it at the bank, then refresh QuickBooks.
- Credentials changed: use the confirmed current login in the code-specific reconnect flow.
- Account details changed: use Fix now and map the discovered account to the existing QuickBooks account.
- Several companies share the login: coordinate one administrator, authorize all required accounts and verify every company afterward.
Do not create a new QuickBooks account merely because the bank presents a new display name. A duplicate can split transaction history and complicate reconciliation.
Best Value
Use browser troubleshooting for persistent screens
A private or incognito window, a different supported browser, and a fresh sign-in can help distinguish a stale session or cached page from a real bank-connection failure. Sign in directly through the normal QuickBooks and bank websites, complete the test, and close the private window afterward. Browser troubleshooting does not replace bank maintenance, credential verification or reauthorization; it only removes local session variables from the diagnosis.
Know what a manual update can and cannot do
Selecting Update sends a refresh request for the selected feed. Most banks update with QuickBooks every 24 hours, but the actual cadence varies. A transaction that the bank has not released, a pending card authorization or a bank-side outage will not appear simply because you clicked Update. Check the bank’s own transaction status before assuming QuickBooks dropped data.
After a successful update, review the date of the latest downloaded transaction and the account name before accepting items. If the timestamp advances but one expected transaction is missing, investigate the bank’s posting status rather than repeatedly reconnecting.
When to contact the bank or QuickBooks support
Contact the bank first when
- The bank’s website rejects the login or requires an account-access reset.
- The account is closed, dormant, locked or absent from the bank’s own account list.
- The bank displays a service interruption, security hold or mandatory terms acknowledgement.
- The bank confirms that its online account works but its third-party connection service is degraded.
Contact QuickBooks support when
- You can sign in at the bank, the account is active and the documented code workflow still fails.
- The same error returns after a successful reauthorization and account selection.
- Several companies share credentials and an authorization change appears to affect more than one feed.
- QuickBooks shows the wrong account for mapping or appears to be creating a duplicate.
Give support the bank name, account type, exact error code, time of the last successful update, recent credential or account changes, browser tested and whether other companies use the same login. Authenticate directly in the bank or QuickBooks window; never place a bank password in a support ticket or chat message.
Quick Recap
Prevent the next bank-feed interruption
- Keep the bank’s contact email and phone number current so security notices reach the account owner.
- Record which bank login and account selection each QuickBooks company uses, especially when one profile serves several companies.
- When the bank asks for new terms or authentication, complete it promptly instead of waiting for the feed to fail.
- Assign one person to maintain shared bank connections and tell other company users before changing account authorization.
- After a password, account-number or bank-profile change, run a controlled update and verify the mapped account name and last four digits.
- Keep a short incident note with the code, date, bank response and successful recovery step; it speeds up the next escalation.
Quick recovery checklist
- Sign in at the bank and clear prompts.
- Confirm the account is open, active and visible with transactions.
- Run All apps → Accounting → Bank transactions → Update.
- Match the exact code: 101, 102/105, 103, 324 or 350.
- Use Fix now only when the code calls for reauthorization or account mapping.
- Select All Accounts or Consent All when the bank presents that choice, particularly for shared credentials.
- Review the mapped account and downloaded transactions.
- Escalate to the bank or QuickBooks with the code and documented changes if the error persists.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
