QuickBooks Error 105 is an online banking connectivity failure that occurs when the software cannot establish a stable handshake with your financial institution’s server during a transaction sync. This is typically triggered by a sudden drop in local network packets or temporary maintenance on the bank’s side.
Fast-Fix: The 45-Second Solution
Force a manual synchronization refresh inside QuickBooks or clear pending alerts on your bank’s website. These errors often stem from momentary internet bandwidth drops or bank server downtime interrupting data transmission. Click the Update button in your bank feeds panel two to three times to retry, verify your internet connection, or manually import a transaction file to bridge the gap and restore your data feed.
Quick Status & Triage Snapshot
- Data Risk Tier: Low. This error affects live internet data transmission rather than the integrity of your core database file. No local transactions are corrupted when this occurs.
- Multi-User Impact: Isolated. It only stops the specific workstation attempting to sync bank feeds from pulling new data. Other users can continue invoicing and data entry normally.
- Common Trigger: Occurs right after clicking “Update” on bank feeds, following router connection drops, or during off-peak bank server maintenance hours.
- Estimated Fix Time: 5 to 15 minutes.
Diagnostic Flowchart: Error 105 Decision Path
When Error 105 hits, think of it like a radio signal that drops out mid-broadcast. You need to isolate whether the broadcast station (the bank) is down or if your receiver (QuickBooks and local network) cut out.
- Initiate Sync Update: Error 105 appears on screen.
- External Browser Test: Open a separate web browser and log in directly to your bank’s online portal using the exact same credentials.
- Result A (Cannot Log In / Server Error Screen): The bank is undergoing maintenance. Action: Wait 24 hours or use a manual file upload.
- Result B (Successful Log In): The bank’s server is functional. The issue lies within the local connection or QuickBooks cache. Action: Proceed to manual refresh and cache clearing.
- Manual Refresh Run: Execute the manual sync utility inside QuickBooks up to three consecutive times to clear stuck network packets.
Is Your Data at Risk?
Your accounting data is completely safe. Error 105 is strictly a communication breakdown between the outside world and your ledger. It acts like a delivery truck getting stuck at a closed gate; the goods haven’t been ruined, they just haven’t been delivered to the warehouse yet. You do not need to run data rebuild utilities or worry about balancing issues inside your company file when this specific code appears.
Technical Anatomy: What This Error Means
When QuickBooks attempts to download new financial data, it initiates a secure connection sequence with the financial institution. Think of this process like two gears meshing together to transfer power. If your internet bandwidth drops for even a second, or if the bank’s server delays its response by a few milliseconds, the teeth of those gears slip.
QuickBooks expects a constant, unbroken stream of encrypted data packets. When that stream gets interrupted, the handshake fails, the software aborts the process to protect connection security, and it returns Error 105.
Root Cause Analysis: Why This Happened
- Bank Side Maintenance (70% probability): Financial institutions frequently update their servers during off-peak hours. During these windows, their automated data exchange pipelines go offline, even if the consumer login page looks normal.
- Local Network Drops (20% probability): Packet loss over Wi-Fi, momentary router reboots, or internet service throttling can kill the connection mid-sync.
- Stuck Browser Cache or Cookies (10% probability): Outdated script components saved locally inside your system can block QuickBooks from establishing a clean, updated path to the financial portal.
Risk Escalation & Severity Factors
While the error itself is low risk, certain environmental setups can make it harder to clear:
- Satellite or Cellular Hotspots: If your system is running on a high-latency connection, sync drops will happen far more frequently.
- Aggressive Local Firewalls: A security program that analyzes internet traffic in real-time might flag the bank feed download stream as suspicious and cut it off mid-packet.
The Cost of Delay: Today vs. End of Week
- Today: Your live bank feed updates are paused. You cannot see today’s cleared checks or deposits automatically inside your bank feed match screen.
- End of Week: Unreconciled accounts will back up, delaying weekly financial reporting and preventing your team from identifying missing or duplicated entries.
Differential Diagnosis: Don’t Confuse This With…
It is easy to mix up connection errors. Make sure you are not actually dealing with these distinct issues:
- Error 102: This indicates the bank website is completely offline or facing a catastrophic server failure, rather than an intermittent internet interruption during active transmission. See
QuickBooks Error 102: Resolving Bank Website Maintenance & Server Errors. - Error 103: This means your login credentials are wrong or the bank is actively blocking the software due to unrecognized device flags. See
QuickBooks Error 103: Fixing Invalid Login & Device Recognition Issues. - Error 108: This occurs when there is a critical prompt, such as a new terms-of-service agreement or a mandatory security alert, waiting for your manual confirmation on the bank’s website. See
QuickBooks Error 108: Clearing Bank Website Security Notices & Actions.
Step-by-Step Repair Guide
Step 1: Force a Manual Bank Feed Refresh
Sometimes the data pipe just needs to be cleared out by running consecutive synchronization requests.
- Navigate to the Banking menu on the left-side dashboard.
- Select the specific bank account that is displaying Error 105.
- Click the Update button in the upper right corner.
- If the sync drops again, wait 60 seconds and click Update a second and third time. Often, subsequent attempts bypass temporary network hops.
Step 2: Clear Local Connection Blocks and Validate Bank Alerts
If a manual update fails, you must verify that the bank isn’t holding the connection back due to an unacknowledged notification.
- Minimize QuickBooks, open your web browser, and navigate directly to your financial institution’s business login page.
- Enter your username and password. Do not use auto-fill; type them manually.
- Look closely at your home account screen. If there is a pop-up window asking you to update your password, accept a new privacy policy, or confirm a paperless billing notification, complete it immediately.
- Log out of the bank website, return to QuickBooks, and run the manual update again.
Step 3: Run a Local Network Reset
If the bank portal is clear but QuickBooks still cannot finish the sync, your local network setup is likely dropping data packets.
- Shut down QuickBooks completely.
- Unplug the power cable from your internet router and modem.
- Leave them unplugged for a full 60 seconds to completely flush the physical memory cache of the hardware.
- Plug the modem back in first, wait for the online lights to go solid, then power up the router.
- Reopen QuickBooks and attempt the bank feed sync.
Hard Stop: When to Call an Expert
If Error 105 stays on your screen for more than 48 consecutive hours, and you have confirmed that your internet connection is perfectly stable on other websites, stop trying to force the sync. This indicates an underlying script mismatch between Intuit’s servers and the financial institution’s modified security layer, which requires a back-end ticket to resolve.
Professional Intervention: What a ProAdvisor Will Do
When an expert or ProAdvisor steps in, they will analyze the raw connection logs to see exactly where the data packet drops dead. If the internal connection cannot be stabilized immediately due to a bank-wide security rollout, they will bypass the live feed entirely. They will log into the financial portal, extract an encrypted banking file, and execute a manual data import to bring your books completely up to date without using the broken sync utility.
Estimated Professional Repair Costs
| Service Level | Scope of Work | Estimated Cost |
|---|---|---|
| Standard Remote Support | Local firewall adjustment, cache clearing, connection testing. | $100 – $200 |
| Deep Data Synchronization Fix | Manual .QBO extraction, statement mapping, ledger alignment. | $250 – $500 |
Related Error Clusters & Technical Silos
Banking communication failures frequently travel in packs. If you are fixing a connection issue here, you might also run into problems related to your Windows firewall blocking secure web ports. If your local machine cannot talk to any secure external servers, you may need to evaluate your system’s network security rules. See Firewall Error 12029: Fixing Connectivity Blocks During QuickBooks Sync. If the live feed remains blocked for an extended period, you can always circumvent the automated engine by following the workflow outlined in Sync Failure: How to Manually Upload .QBO Files to QuickBooks.
Bottom Line
Keep a level head when dealing with Error 105. Your company’s financial books are not broken, and your historical data is completely safe. The issue is simply a momentary traffic jam on the information highway between QuickBooks and your bank. Avoid force-closing your accounting software mid-update; instead, let the error cycle through naturally, verify the bank website via your browser, and allow the system time to re-establish its connection path.