QuickBooks Desktop Bank Feeds Not Working: Checks and Fixes

If your QuickBooks Desktop bank feeds died recently, you’re not imagining it, and it’s probably not your bank login. In 2026 there are three separate things breaking Desktop bank feeds, and the fix depends on which one hit you.

Cause 1: Your version was discontinued (Desktop 2023 and older)

US Desktop 2023 online banking ended after May 31, 2026; older versions reached their cutoffs earlier. Intuit’s policy also ends transaction uploads. Downloading a .QBO file from your bank does not restore a discontinued service: upgrade an eligible subscription or choose another supported product. Manual entry is an option only if your license and subscription still allow editing.

Cause 2: The February 2026 Windows update broke Express Web Connect

A Windows update (the “RB 02/18/2026” rollup) broke bank feeds for many Desktop users — including supported versions like Enterprise 24 — particularly accounts using Express Web Connect. Intuit’s official replies in the community thread were generic, but a community member found the workaround that others confirmed works (details below).

Cause 3: Ordinary OL/OLSU errors

Errors like OL-301, OL-393, OLSU-1013 are usually bank-side: the bank changed its connection protocol, your bank password changed, or the bank requires re-authorization. Intuit’s standard sequence: create a test company file and try the same bank there — if the test file fails too, it’s the bank connection, not your data.

Web Connect (.QBO) import on a supported version

Intuit requires a supported Desktop version and an Intuit-account sign-in for Web Connect imports. Back up your company file first. If your bank offers a .QBO file, try importing it to distinguish a feed-connection problem from a file-import problem:

1. Deactivate the broken feed: Chart of Accounts → right-click the account → Edit Account → Bank Feed Settings → Deactivate All Online Services → save.
2. Go to your bank’s website (the bank, not QuickBooks) and find Download/Export transactions.
3. Choose the format “Web Connect for QuickBooks 2018 and above” — the file must be .QBO. (CSV won’t import directly; Quicken’s .QFX won’t either.)
4. Pick your date range and download.
5. Open the .QBO file (double-click, or in QB: File → Utilities → Import → Web Connect Files). QuickBooks asks which account to associate it with — choose your existing account, not “create new.”
6. Review transactions in the Bank Feeds Center as usual.

Heads-up on duplicates: the first manual import often overlaps transactions the old feed already pulled. Check the import date range against your register and delete duplicates once. Subsequent imports are clean if you keep date ranges consistent.

Should you just migrate?

Compare a supported Desktop subscription with Online or another product against your workflow and reporting needs. Existing Desktop Plus subscribers can upgrade to the continuously updated 2024 platform; migration is not mandatory. See your options here and check the current migration requirements before moving data.

FAQ

My bank doesn’t offer a QuickBooks .QBO download. Some smaller banks only offer CSV. You’ll need a CSV→QBO converter tool, or enter transactions manually.

Will manual imports mess up reconciliation? No — imported transactions behave exactly like fed ones. Reconcile as normal.

Is Desktop 2024 ending in 2027? Intuit’s current policy provides continuing updates and support for existing subscribers. It does not announce the September 2027 shutdown previously stated here. Keep your subscription active and install offered updates; a supported version can still have bank-specific connection problems. See Intuit’s release policy.

Sources: Intuit — Fix OL/OLSU errors, Intuit — Fix Web Connect import errors, QB Community — Windows update RB 02/18/2026 thread