What Error 106 specifically means: QuickBooks successfully authenticated with your bank using your credentials — the login worked. But when QB then asked the bank to list the accounts available under those credentials, the account you connected to QuickBooks was not in that list. This means the account itself is either closed, has changed, is not accessible under those credentials, or QuickBooks is connected to the wrong portal and that portal doesn't have visibility of the account.

Error code

106

Banking · Account Not Found

Related: Error 103 · Error 324 · Error 108

What it means

Error 106 means QuickBooks logged into your bank successfully using your credentials, then asked the bank for a list of accounts under that login — and the account linked in QuickBooks was not in the list. This is an account visibility problem, not a credentials problem. The account is either no longer available, has changed, or is not visible under the connected portal.

Your QuickBooks data is safe. Error 106 is a bank connection issue — your transactions, ledger, and company data in QuickBooks are unaffected. Only the live bank feed is interrupted.

Account Number Changed

Most common cause — the bank changed the account number after a bank merger, security incident, or account type change. QuickBooks is looking for the old account number which no longer exists. Log into your bank and confirm the current account number.

Account Closed at the Bank

The bank account was closed — either intentionally or by the bank due to inactivity or other reasons. A closed account will not appear in the bank's account list, so QuickBooks returns 106. Confirm the account status by logging into the bank website directly.

Wrong Bank Portal Connected

QuickBooks is connected to a personal banking portal but the account is a business account (or vice versa). The business account is not visible under the personal login credentials. Disconnect and reconnect using the correct portal URL for the account type.

Bank Merger or Rebrand

The bank was acquired, merged, or rebranded. The old bank's connection URL no longer returns account data. QuickBooks must be reconnected to the new bank's portal and new account details. This requires a full disconnect and reconnect.

Account Moved to a Sub-User or Business Profile

The bank restructured its online banking portal and moved the account under a business profile, sub-user, or subsidiary login. The primary credentials no longer have direct visibility of the account. Access the account separately on the bank website to confirm.

Bank Does Not Support QuickBooks Connection

Some financial institutions — particularly regional banks and credit unions — have intermittent or broken QuickBooks connections. The bank's data feed infrastructure doesn't reliably expose accounts to third-party applications, causing persistent 106 even when the account is active. Manual CSV import is the reliable workaround.

METHOD 1 Log Into Your Bank Website and Verify the Account is Visible Do this before touching QuickBooks

Since Error 106 is generated by the bank — not QuickBooks — the diagnostic must start at the bank's website. Confirm the account exists, is active, and is visible under the credentials used in QuickBooks.

METHOD 2 Disconnect and Reconnect the Bank Account Account confirmed active at bank — connection refresh needed

If the account is confirmed active and visible on the bank website, the existing QuickBooks connection needs to be reset. This is safe — disconnecting only removes the live feed, not any transactions already downloaded into QuickBooks.

METHOD 3 Reconnect Using the Correct Bank Portal URL Business vs. personal account portal mismatch

Many banks operate separate portals for personal and business accounts — same bank, different URL, different account list. If QuickBooks is connected to the personal portal but your account is a business account, the business account will not appear in the list, producing 106.

METHOD 4 Contact Your Bank — Confirm Account Details and New Number After bank merger, rebrand, or account restructure

If the bank was recently acquired or merged, or if you received any notification about account changes, the account number or bank portal URL may have changed. QuickBooks will continue to return 106 until connected to the new account details.

METHOD 5 Use Manual CSV Import as a Workaround Bank has persistent connection issues — keep books current

Some regional banks and credit unions have persistent QuickBooks connection issues that Intuit cannot resolve because the bank's data feed infrastructure is unreliable. If 106 persists after all reconnect attempts, manual CSV import keeps your books current while you wait for the bank connection to be fixed.

How is Error 106 different from Error 103?

Both are banking errors but they fail at different steps of the bank connection process. Error 103 means QuickBooks attempted to log in using your credentials and the bank rejected the login — the username or password is wrong, or third-party access isn't enabled. The connection fails before even seeing the account list. Error 106 means QuickBooks successfully logged in — the credentials were accepted — but when QB then asked for the list of accounts, the specific account linked in QuickBooks wasn't in that list. Fix Error 103 by correcting credentials. Fix Error 106 by investigating the account itself at the bank.

Will I lose any transaction history if I disconnect and reconnect the bank feed?

No — disconnecting a bank feed only removes the live connection. All transactions that were previously downloaded and accepted into QuickBooks remain in your books permanently. They are stored in your QuickBooks company file, not in the bank feed connection itself. When you reconnect the bank, you set a start date for new transactions to download from — set this to the day after your last downloaded transaction to avoid re-downloading anything already in QuickBooks.

My bank says the account is active and QuickBooks says it can't find it. Who is right?

Both can be simultaneously true. The account is genuinely active at the bank — but the specific data connection between QuickBooks and that bank's account feed may be broken for other reasons: the bank uses multiple portals and QB is on the wrong one, the account moved to a different sub-profile within the same bank credentials, or the bank's QuickBooks connection infrastructure has a bug affecting that account type. In community reports, specific banks like First Horizon have persistent 106 issues affecting many users simultaneously — this is a bank-side integration problem that Intuit and the bank need to resolve together. If you've confirmed the account is active and multiple reconnect attempts haven't helped, manual CSV import is the most reliable workaround until the bank's integration is fixed.