Managing financial data efficiently is essential for maintaining accurate business records, and QuickBooks Automatic Bank Feeds play a crucial role in that process. When these feeds stop functioning properly, it disrupts banking updates, delays reconciliations, and complicates overall bookkeeping tasks. In this comprehensive guide, we explain proven methods to fix QuickBooks bank feeds not working, ensuring seamless syncing between your financial institution and QuickBooks.
Why Automatic Bank Feeds Fail in QuickBooks Desktop?
When automatic bank feeds stop working in QuickBooks Desktop (QBDT), it can disrupt your entire bookkeeping workflow. Bank feeds are supposed to fetch transactions automatically from your financial institution and import them into QuickBooks — but sometimes, this connection breaks. Common underlying issues include:
- Bank-side Errors or Maintenance — your bank may be temporarily unable to deliver data to QuickBooks.
- Outdated QuickBooks or Unsupported Version — older or unsupported versions may not comply with updated banking protocols.
- Internet / Security Protocol Mismatch — firewall restrictions, internet security settings, or outdated web browser settings (especially with internal browsers like Internet Explorer) can block the connection.
- Data Integrity Problems in Company File — sometimes, a corrupted company file or internal data inconsistencies prevent proper transaction download.
- Authentication or Connectivity Glitches — login issues, credentials errors, or stale session tokens may cause the feed to stop working.
When bank feeds stop syncing, QuickBooks may display messages such as “Bank Feed Not Working,” “Error 102,” “Error 108,” “Error 101,” or “Connection to bank lost.” Each error requires specific troubleshooting steps.
Because of these assorted causes, solving the problem usually involves a series of checks and fixes, progressing from simplest to more technical. Below we present a comprehensive guide.
7 Methods to Troubleshoot QuickBooks Desktop Bank Feeds Not Working
Method 1. Backup Your Company File First
Before doing anything, always create a backup of your QuickBooks company file. This ensures you can restore your data in case anything goes wrong during the troubleshooting process.
Method 2. Ensure Your QuickBooks Version is Supported & Up-to-Date
- Confirm that your version of QuickBooks Desktop is still supported by checking official documentation or the support portal.
- If not, upgrade to a newer version. Many banking protocol updates only work on current or recently supported releases.
- Install all available updates/service packs — sometimes the fix is as simple as updating your software.
Method 3. Check Internet Connectivity and Security Protocols (e.g. TLS 1.2)
- Make sure your internet connection is stable, and that firewall or antivirus settings are not blocking QuickBooks.
- Verify that QuickBooks (and its internal browser component) support the security protocols now mandated by banks (for example, TLS 1.2).
- If using older browser components (e.g. embedded Internet Explorer), consider using an updated or alternate browser to access your bank site manually when needed.
Method 4. Test Bank Feed in a Sample / Test Company File
Sometimes, the problem lies with your specific company file rather than QuickBooks or the bank connection.
- Create a test company file (via File → New Company) and attempt to download bank feed data there.
- If bank feed works in the test file, the issue likely relates to your main company file (data corruption, settings glitch).
- If it doesn’t work, the problem is more likely connection-related (bank, internet, QuickBooks settings).
Method 5. Use “Refresh”, “Send/Receive”, or Manual Reconnect of Bank Feed
- Navigate to Banking → Bank Feeds → Bank Feeds Center, and click the Refresh (or Send/Receive) icon for your account — sometimes feeds just hang and need a manual update.
- If this doesn’t work, try deactivating and reactivating bank feeds:
- Go to Lists → Chart of Accounts.
- Right-click the problematic account → Edit Account → Bank Settings tab → Deactivate All Online Services → Save & Close.
- Then immediately re-do Set Up Bank Feeds for that account.
- If you use Direct Connect, ensure you re-enter bank credentials correctly when setting up. Mistyped credentials or changed authentication requirements (e.g. bank enforces new 2-factor authentication) often break feed.
Method 6. Verify & Rebuild Data if Data Integrity Is Corrupted
If feeds are still failing, your company file may have data corruption. Use QuickBooks’ built-in tools:
- Close all windows (
Window → Close All). - Go to File → Utilities → Verify Data.
- If QuickBooks detects no data problems → fine.
- If errors are detected → run File → Utilities → Rebuild Data to repair integrity problems.
- After rebuilding, try the Bank Feed download again.
Method 7. Use Manual Import as a Temporary Workaround
If automatic feeds still fail — but you urgently need to update your books — manually download transactions from your bank and import them:
- Log into your bank’s website; download transactions in a format supported by QuickBooks (e.g. .QBO).
- In QuickBooks: go to File → Utilities → Import → Web Connect Files, choose your .QBO file and import into the correct account.
- Once imported, mark transactions as “Added” or “Matched” accordingly. Be aware — when/if the feed works again, this process may generate duplicates unless handled carefully.
This method does not solve the root issue, but ensures your bookkeeping remains up-to-date while you continue troubleshooting.
Must Read: How to Categorize Bank Transactions in QuickBooks Online?
Common Specific Issues & How to Address Them
1. When You Get the “OL-393” or Similar Error
If QuickBooks shows a bank feed error code like OL-393 or fails to download any transactions but shows connection as “successful,” this often signals a communication protocol mismatch, or that your bank changed its security/API.
What to do:
- Deactivate and reactivate bank feeds.
- Ensure QuickBooks is fully updated.
- Contact your bank to confirm they support QuickBooks Web Connect or Direct Connect for your account type.
2. When Credit Card Feeds Work but Checking Accounts Do Not (or vice versa)
Sometimes only certain account types sync — for example, your credit card downloads, but checking account transactions fail. This often stems from bank-side restrictions or updates (e.g., institution changes what account types are available via Direct Connect).
What to do:
- Check with your bank: maybe they made changes (new login flow, multi-factor authentication).
- Remove and re-add the problematic account under bank feeds, rather than trying to “fix” within the same connection.
3. If Everything Seems Correct — But Feeds Still Fail
After checking QuickBooks version, internet, data integrity, and bank settings — if bank feeds continue to fail:
- Use manual import (.QBO) to stay operational.
- Contact QuickBooks Support, especially if your version is still supported — there may be backend issues or known bugs affecting certain banks or user cohorts.
Best Practices to Prevent Bank Feed Failures in the Future
- Keep QuickBooks Updated – always install the latest patches or minor releases.
- Regularly Back up your Company File so you can quickly roll back if data corruption occurs.
- Monitor your Bank’s Website for announcements of maintenance or changes to online banking protocols.
- Use Manual Import Periodically, especially if you see long gaps in automatic feed, to avoid reconciling large transaction backlogs.
- Re-authenticate Login Credentials occasionally (especially if your bank forces password resets or new security setups).
- Run Verify/Rebuild Data every few months or after major changes to keep data integrity in check.
Adopting these practices reduces the odds of the automatic bank feed breaking — and helps ensure your bookkeeping remains smooth and reliable.
Conclusion
Automatic bank feeds in QuickBooks Desktop are a tremendous convenience — but when they stop working, they can derail your bookkeeping. By following the thorough checklist above — from backing up your data, ensuring a supported QuickBooks version, verifying internet/security protocols, testing in a clean company file, to manual import workarounds — you give yourself the best chance to restore bank feed functionality.
If after all these steps bank feeds remain nonfunctional, rely on manual imports and reach out to QuickBooks support at toll-free number 1-877-400-0650 to investigate potential bugs or bank-specific issues.
Frequently Asked Questions
There are multiple possible reasons: your bank might have temporarily changed or interrupted its connection with QuickBooks, or there may be issues on the QuickBooks side. In some reported cases with FirstBank of Colorado, users noticed that credit‑card transactions got reversed (expenses showed as deposits and vice versa), or error codes like “Error 6000” appeared.
If nothing changed on your end (login credentials, account status), it’s often recommended to contact both your bank and QuickBooks support for deeper investigation.
Upgrading to QuickBooks Desktop 2024 has caused feed issues for some users. Common triggers include: bank‑side changes, server downtime, or incompatibilities between the bank’s service and QuickBooks.
To troubleshoot: back up your company file; log into your bank outside QuickBooks to confirm no alerts; ensure your internet/firewall settings permit QuickBooks to connect; and try the feed in “Classic Mode” if available.
This is a common issue. Often, it’s related to browser cache or temporary glitches with the connection. Clearing your browser cache, or using a private/incognito browser window, can help.
If that doesn’t work, manually disconnecting and reconnecting your bank account sometimes restores the feed — though this can delete pending transactions in the “For Review” tab.
As an alternate route, you can download your transactions directly from the bank and upload them manually (via WebConnect or .QBO files) to ensure your records stay up to date.
Missing or partial transactions can occur when:
1. Your bank recently changed its connection protocol or account type.
2. There are pending alerts on your bank account (e.g. terms to accept, security prompts) — until resolved, feed may fail.
3. The .QBO or WebConnect file downloaded from the bank is incompatible or corrupted. In such cases, manually downloading and importing a fresh .QBO file may help.
Duplicated entries sometimes result from re‑importing transactions that QuickBooks already downloaded, or from connection glitches. In QuickBooks Online, you can “Exclude” duplicates from the “For Review” tab to avoid incorrect records.
That message typically means that your QuickBooks Desktop license / registration information is invalid or corrupted. QuickBooks uses a registration file (Entitlement file) to verify that the software copy is valid.
How to fix:
1. Close QuickBooks.
2. Download and run the latest version of QuickBooks Tool Hub.
3. Use the “Installation Issues → 3371 Error Fix” option to correct entitlement errors.
4. If problems persist, manually delete the entitlement file (EntitlementDataStore.ecml) from C:\ProgramData\Intuit\Entitlement Client\ (v8 or v6, depending on your installation), then restart QuickBooks and register it again.
After successful re‑registration, bank feeds and WebConnect (.QBO) imports should work again.
If all troubleshooting fails (re-registering QuickBooks, reconnecting accounts, clearing cache, trying alternate modes), the last resort is to manually download transactions from your bank and import via WebConnect (.QBO) — in Desktop or Online version.
Meanwhile, you may want to contact your bank to confirm there are no ongoing server or connection issues. If multiple users report similar problems with the same bank, your bank’s configuration may have changed for all customers.


