Bank feed errors 101 to 106 disrupt QuickBooks Online connections
QuickBooks Online users hit numbered bank feed errors from 101 to 106; the vendor's accepted guidance maps each code to a cause and a fix.
Bank feed failures in QuickBooks Online follow a pattern, and Intuit’s accepted guidance sorts that pattern into numbered codes. Each code carries its own cause and its own remedy. Some faults sit with your bank, some with the sign-in details you saved, and one with the account itself.
A numbered family of bank feed faults
The guidance thread, written for the Australian edition, walks through errors 101, 102, 103, 105 and 106 in detail, and names 108 and 109 in the same series. The five detailed codes split cleanly by ownership. Errors 102 and 105 belong to the bank’s systems. Error 101 belongs to account inactivity, error 103 to credentials, and error 106 to an account that no longer exists.
Does error 101 mean the bank has flagged your account?
Often, yes. The vendor describes error 101 as an inactivity fault. An account counts as dormant when it holds a zero balance and shows no deposits, withdrawals or payments for twelve months or longer. Missed prompts deepen the problem. Banks send emails, text messages or in-app notices asking you to confirm an account’s status, and an unanswered notice can stall the feed.
The remedy starts outside the software. Log in to your bank’s website and confirm you can still get in. Check that recent transactions exist, then clear any alert or confirmation prompt waiting there. Finish by forcing a refresh of the connection from inside QuickBooks, using the update step covered below.
Errors 102 and 105 sit on the bank’s side
Both codes point to maintenance or server trouble at the financial institution. Nothing in your settings caused them, and nothing in your settings will clear them. The accepted advice is patience: give the bank 24 to 48 hours to resolve its own systems.
Two actions help in the meantime. Look for an outage notice or maintenance announcement on the bank’s own website. Then run a manual update of the connection, so the feed catches up the moment the bank recovers.
Error 103 is a sign-in mismatch
A wrong user ID, a wrong password, or the wrong bank listing will each produce error 103. The feed cannot authenticate, so it fails on every attempt until the details change.
For an existing connection, open the bank transactions area, find the tile for the affected account, and choose its edit control. Select the option to edit the account sign-in, enter corrected credentials, then save and connect. For a new connection, search for your bank by its exact web address. Several similarly named listings can exist, so retry with an alternate if the first refuses your details.
Error 106 points to a closed account
Error 106 appears when the software cannot locate the account at the bank, and the usual reason is closure. Confirm that first. Log in through the bank’s website or mobile app and check the account’s status directly.
If the account is gone, the connection has nothing left to serve. The guidance is to disconnect it: open the bank transactions area, select the tile for the closed account, choose the edit control, and disconnect the account. Any replacement account can then be linked fresh.
How do you force a manual refresh?
The update step matters across nearly every code here, so we keep it close at hand. In QuickBooks Online, open All apps, choose Accounting, then Bank transactions, and select Update. In QuickBooks Self-Employed, the path is Settings, then Manage accounts, then Refresh all.
One press polls every connected account at once. Running it after a fix on the bank’s side is usually what brings a stalled feed back.
Do errors 108 and 109 need separate steps?
The same series lists 108 and 109 among the codes it covers. The published detail, though, concentrates on the faults above, and the general toolkit overlaps heavily. Check the bank’s site, verify your credentials, confirm the account is open, and run the update step. That sequence addresses most of this family regardless of the exact number on screen.
The order worth trying
When a feed fails and the code is unclear, a short sequence resolves most cases. Confirm you can log in to the bank directly. Clear any prompt waiting there. Check that the account is open and active, then run the update step inside QuickBooks. If the fault lies with the bank’s systems, give it a day or two.
That sequence mirrors the logic of the accepted answer itself: match the code to the cause before touching anything. Error 101 needs activity restored, 103 needs correct details, 106 needs a disconnection, and 102 or 105 simply needs time.