QuickBooks Error 105 is a bank connectivity error that appears in QuickBooks Online when the application cannot reach your bank’s servers to pull in new transactions. Like Error 102, it is a bank feed error but Error 105 has its own distinct causes and a specific meaning that points you toward the right fix faster.
This guide explains what QuickBooks Error Code 105 means, what causes it, and how to fix it covering both general bank connection issues and specific situations with Wells Fargo and Chase. It also explains the difference between bank error 102 and 105, which are frequently confused.
QuickBooks Error 105 means that QuickBooks Online attempted to connect to your bank’s website to retrieve transaction data and the connection failed either because the bank’s servers are slow or unresponsive, the bank’s website is temporarily unavailable, or the connection was interrupted before any data could be returned.
The QuickBooks error 105 meaning is distinct from Error 103 (wrong credentials) and Error 106 (account not found). Bank Error 105 in QuickBooks Online is a server responsiveness issue: QuickBooks can identify your bank and knows where to connect, but the bank’s systems are not responding in time or at all. It is almost always a temporary condition, though in some cases it indicates a more permanent block or connection change that needs to be addressed.
When QuickBooks shows Error Code 105, new bank transactions stop importing into your QuickBooks bank feed. The banking page will display the error alongside the affected account, usually with a message indicating that the bank’s website is unavailable or that QuickBooks is having trouble connecting. Your existing QuickBooks data is not affected no transactions are deleted and no existing records are changed. The error simply means the automatic feed has paused until the connection is restored.
Once your bank feed starts importing transactions again, review and reconcile the downloaded entries using our guide to QuickBooks bank reconciliation.
The clearest symptom is the error notification on the Banking page in QuickBooks Online. Beyond that, you may notice:
Bank error 105 in QuickBooks Online does not produce a pop-up or disrupt other QuickBooks functions it is isolated to the banking feed for the affected account.
Understanding the cause of QuickBooks banking error code 105 in your specific situation helps you choose the right fix without working through every option. Here are the main causes.
The most common cause of Error 105 is bank-side maintenance. Banks schedule routine maintenance windows often at night or on weekends — during which their servers are offline or in a restricted state. QuickBooks cannot access transaction data during these windows and displays Error 105 as a result. This type of error clears on its own once the bank completes its maintenance and restores normal service.
Even outside scheduled maintenance, Error 105 may appear if the bank’s servers are under heavy load, encountering connectivity issues, or facing an unexpected outage. This does not mean that the bank’s public website is down. QuickBooks relies on a separate data connection to retrieve transaction information & this connection can become unavailable even if the bank’s website is working properly.
If you can access your bank account in a browser but QuickBooks is still showing Error 105, this is the likely cause.
Banks periodically redesign their online banking platforms or update the technical infrastructure behind their data feeds. When a bank makes significant changes to its website or to how they serve transaction data to third-party services, the existing QuickBooks connection can break. In these cases, Error 105 may persist until the connection is refreshed or re-established in QuickBooks Online.
Some financial institutions impose restrictions on automated third-party data access particularly for business accounts. If your bank has updated its data-sharing policy, enabled a new security layer, or the QuickBooks connection has been flagged as an unusual access pattern, the bank may be actively blocking the feed. This is sometimes described as QuickBooks error 105 fi blocking where the financial institution itself is the source of the block rather than a temporary server issue. Signs of a bank-side block include Error 105 that does not resolve after 24–48 hours despite the bank’s website working normally.
If the credentials stored in QuickBooks for the bank connection have changed because you updated your online banking password and did not update it in QuickBooks, or because you changed your banking username QuickBooks may fail to authenticate with the bank and produce Error 105. This is more commonly associated with Error 103, but outdated credentials can also surface as a 105 in certain bank configurations.
Banks regularly push security prompts to users new terms of service, two-factor authentication requirements, re-verification of linked third-party services, or security questions that must be answered before data access is permitted. If your bank is holding a verification request that you have not completed, it will block QuickBooks from accessing the data feed until you take the required action on the bank’s own website.
A brief internet disruption on your end, or a short-lived server hiccup on the bank’s side, can also produce Error 105. These resolve quickly often within minutes and a manual update in QuickBooks after the connection has stabilized will pull in any missed transactions.
Before working through the fixes, run these quick checks. They take few minutes and will often tell you whether to wait or act immediately.
Confirm you know the current username and password for your bank’s online banking account. If you recently changed your banking password or username, note the new credentials you will need to update them in QuickBooks.
Open your bank’s website in a browser and sign in. If the bank website server is down or under maintenance, Error 105 will fix eventually on its own once the bank restores service.
If the site is working fine, the issue is more specific and requires active troubleshooting.
Make sure the bank account connected in QuickBooks is still active and accessible. Navigate to the specific account in your online banking portal and to ensure that it’s showing recent transactions.
Try opening any other website to confirm whether your internet is working fine. A slow or unstable internet connection can cause a temporary Error 105 that resolves itself as soon as the connection is stable.
Browse through your online banking portal or scheduled downtime to check for the notices on your bank’s website or any maintenance banners, and alert messages. If planned maintenance is causing the issue, note down the expected completion time and return after it is done.
If you are able to access your bank, your account is active, internet connection is stable and there is no maintenance alerts, try the solutions below. The issue is either outdated credentials, a connection that needs refreshing, or interruption at your bank’s end.
To resolve QuickBooks Error Code 105, verify that your bank’s website is accessible, check for server outages & test your internet connection. Then, refresh your bank connection in QuickBooks, update your banking credentials and try downloading transactions again.
The first step is to confirm whether the credentials saved in QuickBooks for the bank connection is accurate and updated. To check the bank login details,
If you have recently previously changed your online banking password, update it here. Outdated credentials are a straightforward cause of a failed bank connection and one of the quickest fixes to apply.
QuickBooks Online is browser-based and updates automatically, but refreshing your session can clear a stuck connection state.
Keeping your browser fully updated is also part of this step a QuickBooks error 105 update software reminder in some error messages refers to ensuring the browser and QuickBooks Online session are current. An outdated browser can interfere with how QuickBooks communicates with bank data feeds.
If your internet connection is unstable, QuickBooks may fails to maintain the connection to the bank’s data feed and create issues while retrieving transactions.
An outdated QuickBooks session or stored authentication data can prevent the bank feed from refreshing properly. Clear your browser’s cache and cookies for intuit.com and quickbooks.com to remove old session data and restore a fresh connection.
After clearing, try to perform a manual bank update from the Banking page. This will fix browser-level session conflicts that can contribute to Error 105.
Security software installed on your computer or network may interfere with QuickBooks Online connection to bank data services. This issue is common on corporate networks but can also occur on personal devices following a security software update.
Check whether your browser is being blocked from accessing Intuit’s banking endpoints. Temporarily disable your browser’s VPN extension if one is active, and test whether the bank update succeeds. If your organization uses a network-level firewall, check whether access to *.intuit.com is permitted.
If your firewall settings are restricting QuickBooks or browser access to Intuit services, review our guide on Windows Firewall blocking QuickBooks for additional troubleshooting steps.
If your bank has changed its online banking platform or your account details have changed new account number, new routing number, or a switch to a different bank portal the connection information stored in QuickBooks may be outdated.
This is one of the most effective fixes for persistent Error 105 banks frequently require re-verification for third-party data access and do not always notify users by email.
A manual update forces QuickBooks to attempt a fresh connection to the bank’s data feed.
If the Update completes without Error 105, the issue was a temporary bank-side problem that has now cleared. If Error 105 returns, the connection needs to be refreshed at a deeper level continue to Fix 9 or Fix 10.
If the bank connection appears to be broken at a structural level perhaps the bank has updated its platform try removing the bank link and searching for the bank again as if connecting it for the first time.
In QuickBooks Online, go to Transactions > Banking > Add account. Search for your bank by name and select it from the results. QuickBooks will use the latest connection configuration for your bank rather than an older version that may no longer work. You will be prompted to sign in to your bank during this process.
Disconnecting and reconnecting is the most thorough fix for a broken bank connection and is appropriate when all other steps have been tried without success.
Before disconnecting: review and categories any pending transactions in the Banking page. When you reconnect, QuickBooks may import recent transactions again having your existing ones already reviewed reduces the cleanup needed after reconnection.
Disconnect Bank Account:
If reconnecting your bank account results in duplicate, uncategorized, or unmatched transactions, follow our QuickBooks Online cleanup guide to review your books.
Error 105 is part of a broader set of bank connectivity issues in QuickBooks Online. This section explains the underlying banking feed behavior not the fixes, but the reasons the feed fails so you can make better decisions about when to wait versus when to act.
QuickBooks Online connects to banks through a financial data aggregator a service that sits between QuickBooks and the bank and handles the technical work of pulling transaction data. When this aggregator cannot reach your bank’s servers whether due to maintenance, a changed connection, or a block QuickBooks banking error 105 appears. The aggregator operates independently of QuickBooks itself, which is why Intuit’s response to some Error 105 cases is simply ‘wait for the bank to restore their feed’ rather than a QuickBooks-side fix.
When Error 105 is active, the data pipeline between your bank and QuickBooks has stopped. Transactions that posted to your bank account after the connection broke are not lost they are simply not yet in QuickBooks. Once the connection restores and you run a manual update, QuickBooks will pull in all transactions from the last successful sync point. You do not need to manually enter transactions that are already in your bank account; they will arrive when the feed restores.
If QuickBooks cannot connect to your bank even when you try to search for it again or reconnect it, the bank may have temporarily removed its connection from the QuickBooks-supported bank list, or the bank’s data feed infrastructure is undergoing significant changes. This is uncommon but does occur during major bank platform migrations. In these cases, the fix is to wait for Intuit to update the connection and then reconnect the account when it becomes available again.
A full disconnection and reconnection of the bank account is warranted when: Error 105 has persisted for more than 48 hours despite the bank’s website working normally, you have completed any required bank verifications, and a manual update has not cleared the error. It is also necessary when your bank has migrated to a new platform and the old connection configuration is no longer compatible.
Wells Fargo is one of the banks most frequently associated with QuickBooks bank errors, including Error 105. This is partly due to the size & complexity of Wells Fargo’s online banking infrastructure. Partly it is also caused due to Wells Fargo’s security policies around third-party data access.
Why Is QuickBooks Error 105 Showing With Wells Fargo?
QuickBooks error 105 Wells Fargo typically appears after Wells Fargo has performed a platform update, changed their data-sharing requirements, or flagged the QuickBooks connection for re-verification. Wells Fargo periodically updates the terms under which third-party services can access account data, and if you have not accepted the latest terms on their website, the connection will stop working.
Wells Fargo also has specific security measures for business banking accounts that can block automated data access if the account has not been used recently or if unusual access patterns are detected.
Check Your Wells Fargo Online Banking Access
Sign in to your Wells Fargo business banking account directly at wellsfargo.com. Confirm the account is accessible & look for any messages, prompts, or notifications requesting your attention. Check the account settings for any alerts related to third-party data access or connected services.
Verify Wells Fargo Login and Security Requirements
In QuickBooks Online, confirm that the credentials stored for the Wells Fargo connection match your current Wells Fargo online banking username and password. If Wells Fargo has required a password change or if you updated your password outside QuickBooks, update the credentials in QuickBooks’s bank connection settings. If Wells Fargo is prompting for additional verification before permitting third-party access, complete that verification on Wells Fargo’s website this is the single most effective fix for persistent QuickBooks Error 105 with Wells Fargo.
Chase is another bank frequently mentioned alongside QuickBooks bank connectivity errors. As with Wells Fargo, the underlying cause is usually a combination of platform changes and Chase’s requirements for third-party data access.
Why Is QuickBooks Error 105 Showing With Chase?
QuickBooks error 105 Chase most often appears when Chase has updated their online banking platform or when Chase is requesting re-authorisation of third-party data access. Chase periodically asks business banking users to confirm that they consent to data sharing with connected services, and if this confirmation has not been completed, the QuickBooks bank feed stops working.
Chase also experiences scheduled maintenance windows that can produce temporary Error 105 appearances particularly outside business hours and on weekends. These clear on their own once the maintenance window closes.
Check Your Chase Online Banking Access
Verify Chase Login and Security Requirements
Confirm the Chase banking credentials saved in QuickBooks are current. If Chase has recently required a password update or introduced new security requirements for your business account, update those details in QuickBooks’s bank connection settings. Once updated, run a manual bank update in QuickBooks Online to ensure if the connection is restored.
QuickBooks bank error 102 and 105 are the two bank connectivity errors users most commonly encounter and confuse. They share a surface similarity (both stop the bank feed) but have meaningfully different causes.
QuickBooks bank error 102 means QuickBooks cannot connect to the bank’s servers at all the connection attempt fails at the point of initial contact. QuickBooks error 105 means QuickBooks can identify the bank and initiate a connection, but the bank’s servers are responding too slowly or returning an error that prevents data from being retrieved. In practical terms: Error 102 is a connection failure, and Error 105 is a data retrieval failure.
QuickBooks Bank Error 102 vs. 105
| Error | What It Means | Most Common Cause |
| QuickBooks error 102 | QuickBooks cannot reach the bank’s servers. | Bank is down, under maintenance, or has changed its connection |
| QuickBooks error 105 | QuickBooks reaches the bank but data cannot be retrieved. | Bank server is slow, unresponsive, or actively blocking the connection. |
| QuickBooks error 103 | Bank credentials stored in QuickBooks are incorrect. | Password or username changed but not updated in QuickBooks. |
| QuickBooks error 106 | The connected bank account cannot be found. | Account number changed or account closed. |
| QuickBooks error 108 | Bank has a message requiring your attention. | New terms of service or security action pending on bank’s site. |
Yes bank maintenance and temporary server issues can trigger either Error 102 or Error 105 depending on exactly where in the connection process the failure occurs. The troubleshooting steps are also similar: check the bank’s website, attempt a manual update, complete any pending bank verifications, and wait if the issue is maintenance-related. The key distinction is that Error 105 is more likely to involve the bank actively blocking or throttling the data feed, whereas Error 102 is more likely to indicate the bank is simply unavailable.
If Error 105 has persisted for more than 24–48 hours and standard fixes have not resolved it, work through these escalation steps.
Check Whether Your Bank Website Works Normally
Confirm the bank’s website is fully operational not just loading, but allowing you to log in and access account details. If the bank is encountering a prolonged outage or degraded service, Error 105 will continue until the bank restores normal operations. There is nothing to fix in QuickBooks during an active bank outage.
Confirm Your Bank Account Works Outside QuickBooks
Log in to your bank and confirm you can access the specific account linked in QuickBooks. View recent transactions, confirm the account is active & verify there are no restrictions on the account. An account that is accessible in the bank’s portal but still facing Error 105 in QuickBooks points to a connection-level block rather than an account problem.
Check for Ongoing Bank Connection Problems
Some banks have ongoing compatibility issues with QuickBooks’s data aggregator that Intuit is aware of and working to resolve. Check the QuickBooks Online community forums or Intuit’s status page for any known issues with your specific bank. If Intuit has flagged a known connection problem with your bank, the resolution will come from Intuit’s side rather than through user-side troubleshooting.
Try the Bank Connection Again Later
For bank-side issues particularly extended maintenance windows or infrastructure updates the most appropriate response is to wait and retry. Set a reminder to return to the QuickBooks Banking page after 12–24 hours and attempt a manual update. Attempting the update repeatedly in a short window does not speed up the resolution and is not necessary.
Contact Your Bank if the Connection Is Blocked
If Error 105 exists for more than 48 hours and the bank’s website is working properly, contact your bank’s business banking support team. Ask whether there are any restrictions on third-party data access for your account, whether any re-authorisation is required for connected services. Also, check if there are known issues with QuickBooks connectivity. The bank’s team has visibility into account-level blocks that are not visible to you through the online portal.
Contact QuickBooks Support if Your Bank Is Working Normally
If your bank confirms that its services are functioning normally and no further action is needed, reach out to QuickBooks Online support through support.intuit.com. Share your bank’s name, when the error first occur, the date of your last successful sync & the troubleshooting steps you’ve already attempted. Intuit’s support team can then investigate the connection between the data aggregator and your bank and escalate the issue if necessary.
Keep Your Bank Login Information Current
Update the bank credentials stored in QuickBooks any time you change your online banking password or username. Stale credentials are one of the most preventable causes of bank feed failures. Make it a habit to update the QuickBooks connection immediately after any banking credential change.
Complete Bank Verification Requests
When your bank sends a request for re-verification, new terms acceptance, or security confirmation whether by email or within your online banking portal complete it promptly. Banks block third-party data access for accounts with pending verifications, and these blocks directly cause bank error 105 in QuickBooks Online.
Monitor Bank Website or Security Changes
Follow your bank’s communications email newsletters and in-portal announcements for notifications about platform updates or changes to third-party data access policies. When a bank migrates to a new platform, QuickBooks connections often need to be refreshed. Doing this proactively, before an error appears, avoids a gap in your transaction data.
Keep QuickBooks Online Updated
QuickBooks Online receives automatic updates, but your browser needs to be updated separately. Using an outdated browser can cause compatibility issues & disrupt communication with bank data services. To avoid these problems, ensure that Chrome, Edge, or Firefox is running its latest stable version.
Refresh Bank Connections When Required
Bank connections in QuickBooks Online do not need to be permanently reconnected on a fixed schedule, but if you notice a connection that has not successfully synced in several days, refreshing it proactively through a manual update or a disconnect and reconnect prevents a larger gap from accumulating. Checking the Banking page’s last-updated dates once a week is a quick habit that catches issues early.
QuickBooks Error 105 is almost always a bank-side issue and in most cases it resolves on its own within a few hours once the bank completes maintenance or restores their data feed. The key is knowing when to wait versus when to act: if the bank’s website is down or in maintenance, wait. If the bank is working normally and the error has persisted for more than 24 hours, take action.
For Wells Fargo & Chase users, log in to your bank’s website. Then, complete any pending verification or re-authorisation prompts. These platforms need periodic re-confirmation for third-party data access. However, completing those prompts will restore the QuickBooks connection.
If you have worked through every fix above and Error 105 continues to appear, BooksMerge QuickBooks support team can help diagnose whether the issue is a bank-side block, a connection configuration problem, or something that needs to be escalated to Intuit. Contact us here.
QuickBooks Error 105 means QuickBooks Online cannot retrieve transaction data from your bank’s servers. The connection reaches the bank but the bank’s system is either responding too slowly, is temporarily unavailable, or is actively blocking data access. It does not mean your QuickBooks data has been damaged or that your bank account has a problem — it means the automatic transaction feed has paused.
The most common causes are: bank maintenance or a temporary server issue, outdated login credentials stored in the QuickBooks bank connection, a pending bank verification that has not been completed on the bank’s website, a change to the bank’s platform that broke the existing connection, or the bank blocking third-party data access. In most cases the cause is bank-side rather than a QuickBooks problem.
The fix depends on the cause of Error 105 in QuickBooks. Wait if the bank is undergoing maintenance, update outdated login credentials or complete any pending bank verification. If the issue persists, disconnect and reconnect your bank account in QuickBooks to establish a fresh connection.
To fix error 105 in QuickBooks Online: sign in to your bank’s website and complete any pending prompts, update the credentials stored in your QuickBooks bank connection, clear your browser cache, and click Update on the Banking page. If the error 105 QuickBooks Online fix does not take hold after these steps, try disconnecting and reconnecting the bank account from the Banking page.
QuickBooks is showing bank error 105 because it cannot retrieve data from your bank’s servers during the connection attempt. The bank’s servers may be in a maintenance window, the connection may have been broken by a bank-side platform change, your bank credentials may be outdated, or your bank may be holding a verification request that has not been completed. Signing in to your bank’s website and checking for any pending actions is always the right first step.
QuickBooks connects to banks through a financial data aggregator. If the aggregator cannot reach your bank — due to the bank being down, a changed connection, a block, or a required verification — QuickBooks cannot pull transactions. The fix depends on the specific cause: waiting for bank maintenance to complete, updating credentials, completing a bank verification, or reconnecting the account.
QuickBooks Error 105 with Wells Fargo usually means Wells Fargo has updated their platform or is requiring re-authorisation of third-party data access. Sign in to your Wells Fargo business banking account at wellsfargo.com and check for any pending prompts or messages. Completing any required action on Wells Fargo’s website typically restores the QuickBooks connection without further steps.
QuickBooks Error 105 with Chase is most commonly caused by Chase requesting re-confirmation of data-sharing consent or a scheduled Chase maintenance window. Log in to your Chase business banking account and look for any notifications or prompts. Chase sometimes places these in the account settings section rather than on the main banking screen. If no prompts are present and the error has been running for more than 24 hours outside a known maintenance window, update your Chase credentials in QuickBooks and attempt a manual bank update.
Error 102 means QuickBooks cannot establish a connection to the bank’s servers at all. Error 105 means a connection was attempted but the bank’s servers were too slow, unresponsive, or returned an error that prevented data retrieval. Both stop the bank feed, and both are usually bank-side issues, but Error 105 is more likely to involve the bank actively throttling or blocking the data feed, while Error 102 more often reflects the bank being simply unavailable.
The troubleshooting steps for QuickBooks banking error 105 follow this sequence: confirm the bank’s website is working, check for pending bank verifications, verify credentials in QuickBooks, clear browser cache and run a manual update, disable VPN or browser extensions that may interfere, update the bank details in QuickBooks if they have changed, and as a last resort disconnect and reconnect the bank account. If the error exists even after applying all steps, contact your bank’s business support team and then QuickBooks support.
AI-triaged.
Human-solved.
Instant QuickBooks diagnostics, then a certified ProAdvisor takes over live.
first-call fix
match time
live coverage
