Troubleshoot connected bank transactions that stopped downloading in QuickBooks Online

Creation date: 10/30/2026 1:38 PM    Updated: 10/30/2026 1:38 PM

Symptoms

Use this guide when a connected bank or credit-card feed has not brought in recent posted activity, the account card shows an error, Update does not finish, or QuickBooks asks you to verify the connection again. A delay does not necessarily mean transactions are lost. Intuit notes that most banks update on a schedule that can vary, and bank maintenance or security prompts can interrupt downloads.

Safe troubleshooting steps

  1. Document the gap without changing records. Note the connected account's display name, the last download time shown in QuickBooks, the newest posted transaction date visible at the bank, and the exact QuickBooks error code. Use only masked account references such as the last four digits. Do not include balances, full numbers, or transaction lists in a ticket.

  2. Confirm the bank side independently. In a separate browser tab, navigate to the bank's official website yourself. Confirm only that the authorized user can sign in and that the account pages load. Review notices for maintenance, new terms, security questions, consent renewal, or a changed login flow. Never give bank credentials or bank MFA codes to QuickBooks support or your help desk.

  3. Run one manual update. In QuickBooks Online, go to All apps, Accounting, then Bank transactions, and select Update. Complete any verification prompt directly in the bank or Intuit window. Record the result and time. Do not keep clicking Update in a loop.

  4. Rule out a stale session. If the update fails without a clear bank notice, sign in to QuickBooks through a private or incognito browser window and try one update. Intuit specifically recommends this test because extensions and cached sign-ins can interfere with the connection.

  5. Interpret common timing errors carefully. Intuit's guidance for errors 102 and 105 says QuickBooks cannot connect to the bank and that some incidents resolve after the bank corrects its service. Waiting a few hours and checking the bank's site is safer than repeatedly reconnecting. For other error numbers, follow the error-specific Intuit article or escalate with the exact code.

  6. Update connection credentials only when they truly changed. If the bank username, password, or account number changed, use the account card's Edit sign in info option and enter the information directly in the secure connection flow. Do not paste credentials into chat, a ticket, or an email. If the bank login has not changed, do not reset it merely as a test.

  7. Pause before any fallback import. Manual file upload can create duplicates if the connection later downloads the same date range. Do not upload a file, reconnect to a new QuickBooks account, or create transactions unless support and the authorized bookkeeper first confirm the date range, destination account, and duplicate-prevention plan.

What not to do

Do not disconnect or delete the connected account, add a second connection for the same bank account, exclude entries, delete transactions, change opening balances, create adjustments, or modify accounting records. Do not categorize, match, or reconcile as part of technical troubleshooting without authorized bookkeeper approval.

When to escalate

Escalate when the bank website works but QuickBooks fails in a private window, the error remains after the bank's stated outage, multiple accounts at one institution fail, or the feed has a material date gap. Include company name, masked account label, bank name, exact error code and message, last successful download time, newest posted date at the bank, manual-update time and result, private-window result, browser and version, and sanitized screenshots. Never attach bank statements, credentials, MFA codes, full account numbers, tax IDs, payroll data, or customer financial records.

Official Intuit sources