If you open QuickBooks Desktop 2023 and the Bank Feeds centre throws an error instead of downloading transactions, you are not looking at a glitch. Support for QuickBooks Desktop 2023 ended on May 31, 2026, and Intuit's discontinuation policy means bank feeds, payroll updates and security updates for that version all stopped on the same day. The software still opens. The live connection to your bank does not.
For firms with legacy clients still on Desktop 2023, this is the moment the books stop updating themselves. Every transaction that used to arrive automatically now has to be entered by hand or brought in through a file, and the question is how to do that without losing the reconciliation discipline a live feed gave you.
What actually stops when QuickBooks Desktop bank feeds are discontinued
Three things go dark at once, not one. Bank feeds stop downloading new transactions into the Bank Feeds centre. Payroll stops calculating and filing correctly because payroll tax tables are no longer updated. Security patches stop shipping, which matters if the workstation running Desktop is also on a network handling other financial data.
Firms sometimes notice the bank feed failure first because it is the most visible break in the daily routine, but all three are the same event under Intuit's policy: a version reaches its published end-of-life date and every online-dependent service tied to it is switched off that day. Nothing about the desktop application itself is disabled. You can still open a file, enter a bill, print a report, and post journal entries by hand. What you lose is anything that required Intuit's servers on the other end of the connection.
Why this keeps happening on a schedule, not as a one-off
QuickBooks Desktop discontinuation is not a single event; it is a rolling wave. Each annual Desktop version gets a fixed support window and then loses its online services on a set date, the same pattern that just closed out for the 2023 release. Desktop 2024 is the last non-Enterprise version Intuit sold, and when its own discontinuation date arrives, its bank feeds, payroll and security updates will stop the same way.
That detail matters for planning. In previous discontinuation cycles, a firm losing feeds on an old version could migrate to a newer non-Enterprise release and buy a few more years of live sync. That option is gone. Intuit stopped selling new non-Enterprise Desktop subscriptions after the 2024 release, so there is no newer annual version to move to. Firms on Desktop 2024 today are effectively on the last rung of that ladder, and once its support window closes, the choice is Enterprise, QuickBooks Online, or a workflow that does not depend on a live feed at all.
That is the practical reason this article exists: a bank feed is a convenience layer, not the only way transactions get into a ledger. Bank feeds versus statement conversion covers what a live feed actually proves and what it does not, which is worth understanding before you decide how much you miss it.
The QBO bridge: converting statements without a live feed
QuickBooks Desktop's Bank Feeds and Web Connect matching screen is built around one file format: QBO. That is true whether the file arrives from a live download or from a manual import. A spreadsheet, a CSV export, or a table pasted out of a statement document will not load into that matching interface. The interface simply does not read them. If your only usable data is a bank statement document or a downloaded transaction list in another format, it has to be converted into a QBO file before Desktop will do anything with it.
This is different from getting data into QuickBooks Online, where CSV mapping tools are more common. Desktop's banking workflow was built around the same Web Connect standard that banks use for live downloads, so a file destined for Bank Feeds has to speak that standard too. If you have hit a rejection here before, QuickBooks Desktop says your QBO file is not in the right format walks through the most common causes.
Getting from a bank statement to a QBO file
- 1
Pull the statement for the gap period
Download the statement covering everything since the last successful feed sync. If feeds stopped on May 31, 2026, that is your start date. - 2
Convert the statement to QBO
Run the statement through a converter that outputs the Web Connect (.QBO) format, not just Excel or CSV. Desktop's Bank Feeds screen has no path for those other formats. - 3
Import the QBO file into Desktop
Use File, then Utilities, then Import, then Web Connect Files, or drag the .qbo file onto the Bank Feeds centre the same way a live download would have landed. - 4
Work through the match screen
Review each transaction in the matching interface exactly as you would for a live feed, confirming it against the statement line by line before accepting it.
The matching step is where most of the value of a live feed actually lived, and it is fully preserved here. Desktop does not know or care whether a QBO file arrived from a bank's server or from a converted statement. It runs the same match logic either way.
What to check before you trust the import
A QBO import that loads without error is not the same as an import that is correct. Before you post anything from the match screen, confirm the balances tie out against the statement itself.
A single misread digit in a converted amount will not necessarily throw an error in Desktop; it will just sit there as a wrong number until reconciliation catches it, or until it does not. How to verify a converted bank statement in four checks is worth running through the first few times you do this, until the routine is automatic.
Convert to QBO with the balance already checked
Building a routine that doesn't depend on live sync
Firms managing several legacy Desktop clients through this transition tend to settle into a fixed cadence rather than converting on demand. Weekly works well for anyone who reconciles monthly and wants a buffer; monthly is enough for clients where the books only need to be current at close. Either way, the discipline that matters is consistency: convert on the same schedule you would have expected a feed to run, not only when someone remembers.
If a client's feed failure predates the Desktop discontinuation date entirely, for instance a bank changing its connection method, the backfill mechanics are the same and your bank feed stopped syncing and you need to backfill by hand covers that scenario specifically.
None of this restores a live connection. It replaces the one thing a live connection actually did, which was save you from typing each line yourself, with a conversion step that takes minutes instead of a subscription that Intuit no longer sells for this version.
Frequently asked questions
Does QuickBooks Desktop 2023 still work after May 31, 2026?
Yes. The software still opens and you can still enter transactions manually, but bank feeds, payroll updates and security patches stopped working on that date under Intuit's discontinuation policy.
Can I import a CSV file directly into QuickBooks Desktop Bank Feeds?
No. The Bank Feeds and Web Connect matching interface in Desktop only accepts QBO files. A spreadsheet or CSV export has to be converted to QBO before it will appear in the banking centre for matching.
Is moving to QuickBooks Desktop 2024 a permanent fix for lost bank feeds?
No. Desktop 2024 is the last non-Enterprise release Intuit sold, and it will reach its own discontinuation date in time, following the same policy. There is no newer non-Enterprise version to move to after that.
What happens to payroll and security updates when discontinuation hits?
Payroll processing and security updates stop on the same date as bank feeds. Firms relying on any of the three need a manual or file-based replacement for all of them at once, not just the bank connection.
How often do I need to repeat the statement-to-QBO conversion?
As often as a live feed would have synced, which for most firms means weekly or monthly. The right frequency depends on transaction volume and how current the books need to be for reporting or reconciliation.