QuickBooks bank connection errors 101, 102 and 105: accepted fixes

QuickBooks Online users are seeing a cluster of bank feed failures that share one instruction order: look at the bank first, then look at QuickBooks. The accepted answer on the community thread, posted by Intuit, separates errors 101, 102 and 105 into different causes. Its central advice is the same for all three. Confirm the account is reachable and active before you run an update.

A dead Continue button after bank authorisation

One failure mode in the accepted answer does not carry a numbered code. It appears after you finish authorisation inside the bank’s mobile app. The page that loads afterwards has no connection back to the QuickBooks Online window where you started. Because QuickBooks receives no signal that authorisation succeeded, the Continue button stays unresponsive.

The recommended fix is to keep the authorisation and the connection request in the same place. Using the QuickBooks Online mobile app is the suggested route, since the app can receive the bank’s confirmation cleanly. Where the bank offers a choice, entering your credentials directly on the web page does the same thing and avoids the split session.

The device also matters. Some banks redirect the process into their own mobile app automatically. The accepted answer suggests trying a different browser, or switching to a desktop or laptop, because a desktop browser is more likely to keep the authorisation on the page. These are all environmental changes. None of them involve changing a QuickBooks setting.

Error 101 and the quiet account

Error 101 gets the clearest diagnosis in the accepted answer. It points to a bank account that has gone quiet, typically for 12 months or more. An account with a zero balance and no deposits, withdrawals or payments in that window can be treated as inactive by the bank, even if it remains open.

Banks sometimes send a message asking you to confirm the account is still in use. That prompt can arrive by email, by text, or inside the bank’s own app, and it is easy to miss. Meanwhile, QuickBooks keeps trying to pull data from an account that no longer answers.

The fix starts on the bank’s website. Log in, check that the account shows recent activity, and respond to any outstanding prompts. Only then return to QuickBooks and refresh the connection. In QuickBooks Online, the path is Accounting, then Bank transactions, then Update. Self-Employed users select Settings, Manage accounts, and Refresh all. QuickBooks Sole Trader has a Refresh option under Bank transactions.

Errors 102 and 105 point back at the bank

Errors 102 and 105 are the most straightforward of the three. The accepted answer says they describe problems at the bank, usually maintenance or a server outage. QuickBooks is not the source of the failure, and there is no QuickBooks setting that will clear it.

The advised course is to wait 24 to 48 hours for the bank to restore service, then run the refresh path used for error 101. The answer also tells users to check the bank’s website for alerts or outage notices. That check can confirm whether the wait is necessary, or whether the bank has already reported the problem.

The order is the real solution

Users often press Update before checking the bank, because the error looks like a connection fault inside QuickBooks. The accepted answer intentionally reverses that order. Error 101 is an account status problem, errors 102 and 105 are service problems, and the dead Continue button is an authorisation handoff problem. In each case, the first step happens somewhere outside QuickBooks.

The practical takeaway is simple. Do not refresh repeatedly. Visit the bank, confirm the account is active and the service is running, then update the feed once. That sequence is the accepted fix for all three error codes, and it explains why the stale connection behaves the same way regardless of which number QuickBooks shows.