QuickBooks Error 105: Troubleshooting Internet Interruptions During Sync

August 3, 2026 6 min read

QuickBooks Error 105 indicates that an internet interruption or server communication breakdown occurred while syncing transactions between QuickBooks and your financial institution. The connection was initialized, but the data stream dropped before the transaction payload could be completely delivered. This error is usually caused by temporary traffic spikes on your bank’s servers, local network instability, or scheduled server maintenance. Waiting 15 to 30 minutes and running a manual update, or checking for local network drops, resolves the issue in most situations.

Fast-Fix: The 45-Second Solution

To resolve Error 105, run a manual bank feed update after checking your connection. Go to Bank Transactions, select the account showing Error 105, and click the Update button in the top right corner. Run this update 2 or 3 times spaced a few minutes apart. If the error persists, test your internet stability and check your bank’s website to see if they are performing system maintenance.

Quick Status & Triage Snapshot

Data Risk Tier: Low. The sync process uses atomic transactions—interrupted downloads are dropped entirely, preventing partial, corrupt, or duplicate records.
Multi-User Impact: None. Only the online bank download pipeline is affected; all other accounting workflows operate normally.
Common Trigger: Unstable local Wi-Fi, bank server updates, latency on Intuit’s aggregation network, or VPN packet dropping.
Estimated Fix Time: 5 to 30 minutes (or waiting out external bank server updates).

Diagnostic Flowchart: Error 105 Decision Path

[Start: Error 105 Appears During Sync]
       |
       v
Click "Update" in Bank Transactions.
Does the sync complete after 2-3 attempts?
       |
      +---> YES: Issue was a momentary packet drop. Problem resolved.
      |
      +---> NO: Open a browser and visit your bank's login page.
                   |
                   v
            Does the bank website display a maintenance notice or load slowly?
                   |
                  +---> YES: Bank servers are overloaded or updating. Wait 24 to 48 hours.
                  +---> NO: Are you using a VPN, proxy, or unstable Wi-Fi connection?
                               |
                              +---> YES: Disconnect VPN / switch to Ethernet cable, then update.
                              +---> NO: Clear browser/application cache and refresh feed.

Is Your Data at Risk?

Your financial data is completely secure.

Safe State: When Error 105 occurs, QuickBooks’ download protocol rejects incomplete data blocks. It does not write incomplete lines to your register or “For Review” tab.
Safe Manual Workaround: If you have an urgent deadline and the connection remains down, you can export a .QBO or .CSV transaction file from your bank’s website and upload it manually without risking file corruption or duplicate entries.

Technical Anatomy: What This Error Means

The automated bank feed synchronization relies on a steady TCP/IP data pipe between three nodes: your local QuickBooks instance, Intuit’s aggregation servers, and your bank’s API gateway.

Error 105 occurs when this pipeline breaks mid-stream:

Socket Timeout: The initial connection handshake succeeds, but the bank’s server takes too long to package and send the transaction payload. The waiting socket reaches its timeout limit and terminates the connection.
Packet Fragmentation & Loss: If your local network suffers packet drops (common on congested Wi-Fi or unstable VPN tunnels), the SSL/TLS stream corrupts. QuickBooks drops the incomplete transmission to prevent corrupt data entry.
HTTP 502/504 Upstream Gateways: When financial institutions push maintenance patches or batch updates, their API gateways may return 502 Bad Gateway or 504 Gateway Timeout errors, which QuickBooks translates as Error 105.

Differential Diagnosis: Don’t Confuse This With…

QuickBooks Error 101: Indicates that the connection timed out before any connection handshake could be established with the banking server. Error 105 indicates the connection began, but dropped mid-sync.
QuickBooks Error 102: Signifies that the bank’s website is undergoing formal, reported maintenance or its servers are completely offline.
QuickBooks Error 9999: An unhandled script or communication error where the bank’s web structure blocked the data scraping/API script entirely.

Step-by-Step Repair Guide

Follow these steps to clear the communication block.

Step 1: Perform Consecutive Manual Updates

Banks frequently handle high volume during early mornings, weekends, or month-end processing. A manual refresh often connects cleanly.

In QuickBooks, go to Bank Transactions (or Banking).
Click the Update button in the top right corner.
If the error reappears, wait 2 to 3 minutes and click Update again.
Run this manual update 2 to 3 times to see if an open socket goes through.

For more on manual sync strategies, see Manual Fix: 5 Steps to Resolve QuickBooks Bank Feeds Not Updating.

Step 2: Verify Your Local Network Environment

Local network latency can interrupt transaction data transfers.

Disable Active VPNs: Virtual Private Networks redirect traffic through remote servers, creating latency and triggering anti-fraud blocks from banks. Temporarily disable your VPN and re-test the sync.
Switch from Wi-Fi to Ethernet: If your workstation is on Wi-Fi, momentary signal drops will sever bank sessions. Use a direct Ethernet connection where possible.
Reboot Network Hardware: Power-cycle your local modem and router to clear cached DNS tables and buffer overruns.

Step 3: Clear Browser and Application Cache

Corrupted temporary internet files can prevent the bank feed interface from establishing fresh connections.

If using QuickBooks Online via Browser:
1. Open your browser settings and select Clear Browsing Data.
2. Choose Cookies and other site data and Cached images and files.
3. Set the time range to All Time and click Clear Data.
4. Restart the browser in an incognito window and retry the sync.
If using QuickBooks Desktop:
1. Go to Help > Internet Connection Setup and verify that your system is set to use your computer’s internet connection settings.
2. Open Windows Control Panel, select Internet Options, go to the Advanced tab, and click Restore advanced settings.

Step 4: Import Transactions Manually (When Deadlines Loom)

If the bank’s servers are down for extended maintenance, you do not have to wait to reconcile your accounts.

Log into your bank’s website directly.
Download your transaction history in .QBO (WebConnect) format. (If .QBO is unavailable, choose .CSV).
In QuickBooks, go to Bank Transactions.
Click the dropdown arrow next to Link Account and select Upload from file.
Follow the prompts to map and import the transactions directly into your review screen.

For a step-by-step walkthrough, see Sync Failure: How to Manually Upload .QBO Files to QuickBooks.

Hard Stop: When to Call an Expert

Cease repeated manual sync attempts and wait or contact support if:

The error persists continuously across multiple accounts for more than 48 hours, and your bank confirms its API is operational.
Your bank indicates they have transitioned to a new direct-feed provider and your current connection profile has been retired.
The sync repeatedly downloads scrambled transaction payloads or truncated character strings into the register.

Closing the Books

QuickBooks Error 105 is almost always a temporary communication dropout between servers, not a sign of broken financial books. Your register remains safe and accurate. By retrying the manual update, removing network bottlenecks like VPNs, or using a quick manual file upload when facing strict deadlines, you can keep your books on track while server traffic returns to normal.

Sync Failure: How to Manually Upload .QBO Files to QuickBooks

October 7, 2026

QuickBooks Error OL-334: Correcting Outdated or Incorrect Bank IDs

October 6, 2026

Manual Fix: 5 Steps to Resolve QuickBooks Bank Feeds Not Updating