QuickBooks Desktop 2023 Support Ended in May. Here Is What Actually Broke.

August 10, 2026

---

If you are reading this, something in your QuickBooks Desktop 2023 file probably stopped working and nobody warned you loudly enough. Here are the facts up front, then the honest math on your three options — including the one almost nobody explains.

What exactly stopped working on May 31, 2026?

On May 31, 2026, QuickBooks Desktop 2023 — including the Accountant editions — reached end of support. Live bank feeds stopped, payroll tax tables froze at their last update, security updates ended, and Intuit support closed. The software still opens and your file still works. The connected services around it are gone.

This is what "end of support" actually means, and it is why the discovery is so disorienting. Nothing crashed. There was no error screen on June 1. The program launches exactly as it did in May. But the parts of the product that depend on Intuit's servers — the bank connections, the payroll updates, the support line — went dark, and they went dark for everyone still on 2023 at once. Intuit has cited over one million active Desktop users, and the practitioner forums fill up with the same language every time a version sunsets: "bank feeds stopped," "payroll tables frozen," "forced migration."

For context, this is the middle of a scheduled sequence, not a one-off. Desktop 2022 lost support on May 31, 2025. Desktop 2023 lost it on May 31, 2026. And Desktop 2024 is the final non-Enterprise version Intuit will ever make — no 2025, 2026, or 2027 outside the Enterprise line — with support ending September 30, 2027. That date is the true hard cliff. May 31, 2026 was just its leading edge.

My bank feeds stopped after the May cutoff — is Web Connect the only option?

For most banks, effectively yes. Direct bank feeds require a supported Desktop version, so a 2023 file cannot reconnect. What remains is the manual Web Connect workflow: log into your bank's website, download the transaction file, and import it into QuickBooks yourself. Slower, but it keeps the books moving.

If you go this route, treat it as a process, not an emergency patch. Pick a rhythm — weekly works for most files — download from every account on the same day, import, and reconcile immediately while the download is fresh. The failure mode with manual imports is not the import itself; it is the three-week gap where nobody downloaded anything and now two statements have to be reconstructed. The feed used to enforce discipline for you. Now the calendar has to.

The honest caveat: Web Connect is a bridge, not a destination. It buys you time to make a real decision. It does not change the fact that you are running unsupported software with no security updates.

Are my payroll tax tables really frozen?

Yes. If you run payroll through Desktop 2023, the tax tables froze at their final update before the May 31, 2026 cutoff. As rates and thresholds change after that date, the software keeps calculating against stale numbers — and the checks still print, which is exactly why this failure is dangerous.

This is the quietest broken piece and the one to fix first. Dead bank feeds announce themselves; a frozen tax table does not. Every payroll run after the cutoff looks normal on screen while the underlying calculations drift away from what is actually owed, and the person responsible for the difference is you, not Intuit. If you are still running payroll on 2023 right now, either verify every calculation manually against current published tables or — the saner answer — move payroll off Desktop 2023 before you decide anything else. Payroll should not wait for your ledger decision.

What do I actually move to — Enterprise or QBO?

This is the most-asked question in every Desktop thread, and the honest answer is that there are three options, not two: ride Desktop 2024 until its own sunset, pay for Enterprise, or migrate to an online ledger. Each carries a different price and a different kind of risk.

Option 1: Desktop 2024, until September 30, 2027. Desktop 2024 is the last non-Enterprise version ever made, and it remains supported until September 30, 2027. If your Pro or Premier subscription was active, you likely have rights to 2024 and can restore working bank feeds and payroll updates by upgrading. The catch: Intuit stopped selling new US Pro, Premier, and Mac subscriptions on September 30, 2024. If you were on a standalone 2023 license without an active subscription, that door is closed. And even for those who can take it, understand what it buys — roughly fourteen months from today, after which you face this exact decision again with no further Desktop versions behind it. It is a runway, not a destination.

Option 2: Enterprise — Desktop that continues, at Enterprise prices. The Enterprise line is the only Desktop product with a future. Single-user list pricing runs roughly $1,700 to $2,700 per year depending on tier — before hosting, if you want the file accessible anywhere, and before additional seats. The recurring community verdict — "Enterprise is too expensive" — is not really about the number. It is about paying enterprise pricing to keep the feature set you already had.

Option 3: QuickBooks Online, or another online ledger. QBO raised prices again in August 2026: Essentials now lists at $85 per month and Plus at $140 — per company, every month. For an owner with one entity, that is the subscription. For a bookkeeper or firm, multiply by the client list, then add the migration itself: conversion, chart-of-accounts cleanup, retraining, and the weeks of checking that follow. The subscription is the visible cost. The migration labor is usually the larger one.

Why does "it looked right until we reconciled" keep coming up?

Because migrations and automation both fail the same way: quietly. The recurring practitioner complaints — "bank rules broke," "it auto-added the wrong thing," "the books balance but the reports are wrong" — describe errors that survive a glance and surface at reconciliation or tax time, after they have compounded for months.

This is the real reason experienced bookkeepers are cautious about the exodus, and it deserves to be said plainly rather than dismissed as resistance to change. A converted file can tie at the trial-balance level while individual accounts are subtly wrong. An automated categorization engine can be confidently wrong in ways that look plausible in a transaction list. The practitioners saying "I still have to check everything anyway" are not being stubborn — they are describing what standing behind a set of books actually requires. Any migration plan that does not account for verification is a plan to discover problems at year-end.

What is a parallel run, and why do it before you migrate?

A parallel run keeps your current system as the system of record while a candidate system books the same months alongside it. You compare the outputs — categorizations, reconciliations, the reports themselves — against books you already trust, before you commit anything. It turns a forced migration into an evaluated one.

This is the piece missing from almost every migration conversation. The standard path is: pick a destination, convert, hope, and find out at reconciliation. A parallel run inverts that. Desktop keeps running exactly as it is — Web Connect imports and all — while the new system processes the same real months. If the outputs match your own judgment, you migrate with evidence. If they do not, you have lost nothing but the comparison time, and you learned it before your books depended on the answer.

One honest mention of where we fit: Nalo is AI bookkeeping software built around exactly this evaluation. It categorizes against your own history with the evidence shown, routes anything uncertain to review instead of guessing, and never posts without confirmation. Firm pricing is published — $100/$85 per client per month — alongside a published free parallel-run evaluation month during which your Desktop file remains the system of record; for a single business it is $100 a month. Among the AI bookkeeping tools courting Desktop refugees, it is the only one that publishes both the price and the free pilot. The full comparison, including the honest cases where another option fits better, is at nalo.app/quickbooks-desktop-alternative/.

What should you do this week?

Restore the data flow first — set up the Web Connect routine so no transactions go missing while you decide. Move payroll off the frozen tables before anything else. Then choose your path with the real dates in view: the leading edge of this migration arrived on May 31, 2026, and the hard cliff is September 30, 2027.

Fourteen months sounds like a long time. It is not, once you subtract year-end, tax season, and the weeks a careful migration actually takes. The businesses that come through this well will be the ones that chose a destination on evidence, on their own schedule — not the ones who waited for the second cutoff to choose for them.