QuickBooks Error 106 Fix: Account Not Found or Inactive Bank Account

QuickBooks Error 106 indicates that the software is searching for a bank account that no longer exists, has been closed, or has been rendered inactive on your financial institution’s server. When the bank feed sync runs, QuickBooks submits an account identifier that the bank’s system rejects as invalid.

Fast-Fix: The 45-Second Solution

Disconnect the inactive account from Bank Feeds and reconnect it to link the new account ID. This error commonly stems from a changed account number, a closed bank account, or a modified server-side ID that disrupts the automated handshake. Open the Banking menu, click the pencil icon on the broken account card, select Edit account info, check Disconnect this account on save, and then select Link account to re-establish the connection.

Quick Status & Triage Snapshot

• Data Risk Tier: Low. Your existing financial ledgers, past reconciliations, and local data files remain entirely secure. The software is simply failing to pull new data from an external pipeline.
• Multi-User Impact: Isolated. This issue is tied strictly to the specific bank account link within the file. Other users can enter transactions, run payroll, and write checks without any interference.
• Common Trigger: This occurs immediately after a bank merges accounts, issues a new credit card number due to fraud, or updates their internal security servers.
• Estimated Fix Time: 10 minutes.

Diagnostic Flowchart: Error 106 Decision Path

When Error 106 happens, the communication pipe between your local ledger and the bank’s vault has been severed because the destination target moved. Use this decision path to track down the break:

1. Check Bank Portal Availability: Open an external web browser and log into your bank’s website directly.
   • Can you see the account listed on the bank’s online homepage?
   • No: The bank has deactivated or closed the account. You must stop trying to download transactions and disconnect the feed.
   • Yes: The account is active, but its internal digital ID has changed. Proceed to Step 2.
2. Verify Account Changes: Did you recently get a new physical debit/credit card, or did the bank change your account type?
   • Yes: The software is calling an old number. Disconnect the feed and map the ledger to the new card number.
   • No: The connection data cache is stale. Disconnect, clear the cache, and rebuild the link.

Is Your Data at Risk?

Your historical company data is completely safe. Error 106 is a matching error, not a database corruption event. It means QuickBooks is knocking on a door that has been bricked over on the bank’s side. Because no data can pass through a closed door, no corrupted records can enter your system. You do not need to execute a utility run or stop your daily operations; your existing balance sheets are intact.

Technical Anatomy: What This Error Means

Think of a bank feed link like a dedicated shipping line between two ports. When you first link your checking or credit account, the bank issues a specific alphanumeric identifier code to QuickBooks. This code acts like a unique landing slot.

During a sync request, QuickBooks says, “Send the transaction logs for landing slot XYZ.” If the bank updates its website, closes that card due to fraud, or changes your corporate account structure, slot XYZ vanishes. The bank’s server processes the request, finds no matching slot, and sends back an “Account Not Found” response. QuickBooks cannot interpret this dead end, drops the connection, and produces Error 106.

Root Cause Analysis: Why This Happened

• Account Deactivation or Replacement (65% probability): A credit card was replaced due to fraud, a loan was paid off, or a checking account was migrated to a new tier, creating a completely new account record on the bank’s end.
• Bank Server Migrations (25% probability): The financial institution updated its back-end database, shifting existing accounts to a new API path without updating the token stored inside QuickBooks.
• Mismatched Credentials or Profiles (10% probability): The user login profile was changed, causing the automated sync to lose visibility of specific sub-accounts under the master business profile.

Risk Escalation & Severity Factors

While your data isn’t in danger, the complexity increases based on how your banking is arranged:

• Sub-Account Structures: If you use a parent account with multiple employee credit cards attached to it, disconnecting one card incorrectly can drop the feed for every card in the cluster.
• Web Connect Manual Adjustments: If you regularly use web upload files rather than direct links, a hidden text mismatch in the downloaded file header can trigger this error code manually.

The Cost of Delay: Today vs. End of Week

• Today: Your live bank feed updates for this specific account are completely frozen. You must manually record any checks or payments to keep daily balances updated.
• End of Week: Missing a full week of downloads makes credit card reconciliation a manual chore. Untracked expense reports accumulate, and out-of-sync balances make cash flow forecasting inaccurate.

Differential Diagnosis: Don’t Confuse This With…

Error 106 has a very narrow cause, but it looks identical on screen to other banking issues:

• Error 103: This means the bank exists and the account is there, but your user credentials or security keys were rejected. See QuickBooks Error 103: Fixing Invalid Login & Device Recognition Issues.
• Error 324: This occurs when QuickBooks cannot find the bank account because it was renamed or replaced, which is a close cousin to 106 but usually involves a completely broken link page rather than an inactive record response. See QuickBooks Error 324: Reconnecting Renamed or Replaced Bank Accounts.
• Error 350: This points to an expired secure connection authorization token that needs to be renewed, though the underlying bank account remains active and unchanged. See QuickBooks Error 350: Renewing Expired OAuth Bank Connections.

Step-by-Step Repair Guide

Step 1: Disconnect the Broken Bank Connection

To clear the error, you must clear out the old, stale link configuration that is calling the wrong account ID.

1. Go to the Banking menu or Transactions tab on the left sidebar.
2. Locate the account card showing Error 106. Click the small Pencil icon in the top-right corner of that card.
3. Select Edit account info.
4. In the Account window that appears, look near the bottom and check the box marked Disconnect this account on save.
5. Click Save and Close. This severs the broken communication line but leaves all your historical transactions untouched in your chart of accounts.

Step 2: Clean the System Cache and Open Connections

Before setting up the new connection, clear out any lingering network session files.

1. Log out of QuickBooks completely.
2. Open your web browser, clear your internet history, cookies, and temporary cache files.
3. Close the browser, reopen it, and log back into your QuickBooks file.

Step 3: Re-Link and Map to the Active Account

Now, connect to the live account pipeline using a fresh search request.

1. Return to the Banking menu.
2. Click Link Account or Add Account in the upper right corner.
3. Type your bank’s name in the search bar and select it from the list.
4. Input your online banking user credentials when prompted to log in through the secure portal.
5. QuickBooks will fetch all active accounts tied to that login. Look at the list carefully.
6. Match the active bank account to your existing ledger account name in your Chart of Accounts dropdown list. Do not create a duplicate account unless it is a brand-new credit card line.
7. Click Connect and let the software run a fresh sync to pull down the missing data.

Hard Stop: When to Call an Expert

If you walk through the link process and your bank account does not appear anywhere in the connection list, or if your bank confirms the account is wide open but QuickBooks still returns Error 106 after multiple link attempts, stop. This means there is an account mapping block on the server host side or an unmapped sub-account conflict that requires deep technical utility alignment.

Professional Intervention: What a ProAdvisor Will Do

A ProAdvisor or data specialist will trace the raw bank ledger files to see how the bank is indexing your account numbers. If the direct connection is blocked by a bank platform change, they will step around the live automated bank feed sync system. They will download a raw web connect transaction file directly from the bank’s core system, inspect the formatting metadata, and force-load the data into your system safely.

Estimated Professional Repair Costs

Service Level	Scope of Work	Estimated Cost
Basic Connection Repair	Bank feed disconnection, cache purging, account re-mapping, sub-account grouping check.	$120 – $220
Advanced Manual Migration	Raw data extraction, statement import alignment, broken link resolution.	$250 – $450

Related Error Clusters & Technical Silos

Account connection breaks often indicate that other elements of your web tools need maintenance. If your system is failing to pull exterior updates generally, you might have an outdated browser component or system clock issue. If your direct links fail continuously, you can use manual file ingestion to keep your ledgers current while the server settles down. Check out Sync Failure: [How to Manually Upload .QBO Files to QuickBooks] for an alternative data route](<http://www.qberrors.com/errors/banking-sync-errors/manual-qbo-upload>).

Bottom Line

QuickBooks Error 106 is a minor alignment issue along your connection pipeline, not an internal database failure. Your books are intact, your historical data is clean, and your balances are safe. By severing the old, expired link data path and mapping a fresh link to the bank’s current server ID, your automated downloads will pick right back up where they left off without losing a single transaction line.