Small-business accounting audit · September 8, 2026
QuickBooks Desktop 2023 can still open while the services around it have already stopped being supported. That makes this a dangerous quiet failure: the company file may look normal even though payroll calculations, payment processing, bank feeds, emailed forms, support, and security updates no longer have the status the business assumes.
Guidance checked September 8, 2026, at 1:13 p.m. Eastern / 17:13 UTC. Intuit’s official pages timed out from our automated checking environment, so we verified their current indexed body text and link destinations and are stating that limitation plainly. Recheck your exact product, license, and connected services with Intuit and your accountant before making a financial-system change.
The short version: Intuit says support for QuickBooks Desktop 2023 ended after May 31, 2026. The affected family includes Pro Plus 2023, Premier Plus 2023, Mac Plus 2023, Enterprise Solutions 23.0, and listed Accountant editions. Intuit says live support, Desktop Payroll, Desktop Payments, online bank feeds, critical security updates, email from inside the product, Accountant Copy Transfer, and other connected services are affected.[1]
Why “it still opens” is the wrong test
An accounting application has two layers. The local layer opens the company file, records entries, and generates reports. The connected layer handles services such as payroll updates, bank downloads, payment processing, emailed forms, support, and vendor-delivered security fixes. A successful login proves only that the local application opened; it does not prove every connected dependency is current.
What may still work
You may still be able to open the local company file, review historical transactions, enter data manually, and run familiar reports. Exact behavior depends on the license and configuration, so treat this as an inventory question—not a promise that every local function remains available.
What needs an immediate audit
Payroll, direct deposit, employee access, bank feeds, online transfers, card and check processing, eInvoices, recurring-payment downloads, emailed forms, live support, security updates, and accountant-transfer workflows all deserve an explicit pass/fail test against Intuit’s affected-services list.[1]
Payroll stop condition: Do not assume a paycheck is accurate because QuickBooks produced one. Intuit says customers may still be able to create paychecks after payroll discontinuation, but advises against it because tax calculations will be incorrect.[2] Pause, involve the person responsible for payroll, and verify the current tax and filing workflow before issuing another payroll from the affected version.
A 45-minute triage before you buy or migrate anything
Confirm the exact edition, year, and release
Open QuickBooks and press F2 (or use Help → About QuickBooks) to view Product Information. Photograph or securely record the product name, year, release, license status, company-file path, and number of users. If the screen says 2024, 2022, or Enterprise 24.0, do not apply a 2023-specific plan blindly.
List the services your business actually uses
Ask the bookkeeper, owner, payroll contact, and front desk—not only the person who opens the file. Mark whether the business uses payroll, direct deposit, Workforce, bank feeds, bill payment, merchant processing, emailed invoices, recurring payments, multi-currency, or Accountant Copy Transfer. A feature nobody uses is not an outage; an invisible weekly dependency is.
Freeze a clean backup before testing changes
In single-user mode, use File → Back up Company → Create Local Backup, choose a separate destination, and enable Complete verification. Intuit describes a company-file backup as a save point and says Complete verification checks the backup before it is saved.[3] Keep this pre-change backup read-only and do not overwrite the only known-good copy.
Preserve payroll forms separately
Intuit says a normal company-file backup does not automatically back up payroll forms.[3] If payroll applies, export or preserve the payroll forms and the associated tax-forms folder using Intuit’s documented procedure, then have the payroll owner confirm what records must be retained.
Measure the gap instead of guessing
For every bank and card account, record the date of the last downloaded transaction and the last completed reconciliation. For payments, identify the last successful in-product transaction and where recurring payments are now managed. For payroll, record the last successful submission, tax-table status, filing status, and confirmation from the payroll provider. Do not “test” with a live customer charge or a real paycheck.
Choose a supported destination with the accountant
The right destination may be a supported QuickBooks release already included with an eligible subscription, QuickBooks Enterprise, QuickBooks Online, or another accounting platform. This is a business-process decision, not just an installer choice: inventory, job costing, payroll, integrations, user permissions, remote access, report layouts, and accountant workflow can change.
Rehearse and reconcile before cutover
Make the migration on a copy, keep the original intact, and compare the same date-bounded reports in both systems: balance sheet, profit and loss, accounts receivable, accounts payable, sales tax, inventory valuation when applicable, payroll liabilities, and open transactions. Intuit provides a supported Desktop-to-Online migration path, but a completed upload is not proof every business-specific workflow reconciled.[5]
Decision table: affected, not affected, and uncertain
Phone readers: swipe the table left to see every column.
| Situation | Likely state | What to do |
|---|---|---|
| Pro Plus, Premier Plus, Mac Plus 2023, or Enterprise 23.0 | Affected by Intuit’s May 31, 2026 service-discontinuation policy | Run the dependency audit now; confirm exact licensing and options with Intuit.[1] |
| QuickBooks Desktop 2024 or Enterprise 24.0 | Not the same 2023 cutoff | Do not assume permanent support; check the current lifecycle for that exact release. |
| Local file opens and reports run | Does not prove connected services or security updates are supported | Test each dependency without using live money or payroll. |
| Payroll is configured | High consequence | Pause affected-version payroll until the responsible payroll professional confirms calculations, deposits, filings, and employee access.[2] |
| Historical file kept only for lookup | Different risk from active daily bookkeeping | Keep it backed up, access-controlled, and separated from the active accounting workflow; document how records will be retrieved. |
| Hosted QuickBooks or a third-party add-on | Uncertain | Ask the host and vendor which QuickBooks release and connected services they support; “hosted” does not answer the lifecycle question. |
Good migration behavior versus expensive shortcuts
Good approach
- Inventory the exact version and every connected dependency.
- Create a verified local backup and separately preserve payroll forms.[3]
- Rehearse on a copy and preserve the pre-migration file.
- Compare financial reports and open balances before declaring success.
- Schedule a quiet cutover window and stop entry in the old file at a clearly recorded time.
- Keep the accountant and payroll owner in the acceptance decision.
Bad approach
- Keep issuing payroll because the button still works.
- Assume a bank-feed failure means the bank has no new transactions.
- Install an unknown “repair” or migration utility from a search ad.
- Upgrade the only company file with no frozen backup.
- Run Rebuild Data merely because the version is unsupported.
- Cancel the old service before reports, payments, payroll, and permissions reconcile.
Do not confuse lifecycle trouble with file damage
Service discontinuation does not by itself mean the company file is corrupt. Intuit says Verify Data scans for common file errors, while Rebuild Data is the repair path when verification finds integrity problems; Rebuild requires a backup and should be followed by another verification.[4] If you use Assisted Payroll, Intuit specifically says to contact it before rebuilding.[4]
That boundary matters. A lifecycle problem calls for dependency inventory and migration planning. A damaged-data problem calls for evidence preservation, verified backups, and a cautious repair path. Randomly rebuilding, renaming, moving, or repeatedly converting the only active company file can turn one known problem into several.
Two realistic examples
The harmless-looking warning
A two-person office opens its 2023 company file every day and manually records checks, so nothing looks broken. During the audit, the owner discovers bank feeds stopped months ago and the last reconciliation predates several fees and refunds. The recovery is a bounded bookkeeping cleanup—not a mystery software repair—because the cutoff date and account statements establish the missing period.
The costly wrong turn
A business sees payroll calculations on screen and assumes they remain current. It sends paychecks before confirming tax tables, deposits, forms, or provider status. The software producing numbers is mistaken for the payroll workflow being supported. That is exactly the point to pause and involve the payroll professional before more live transactions compound the discrepancy.
Related safeguards
- Do not open an active QuickBooks company file directly from a consumer sync folder. Our QuickBooks Desktop company-file storage guide explains safer local and supported multi-user patterns.
- A backup job saying “success” is not the same as a recoverable file. Use our one-file restore test as the general model, and perform a separate controlled QuickBooks restore test with the right accounting support.
FAQ
Will QuickBooks Desktop 2023 suddenly delete my company file?
Intuit’s service-discontinuation notice describes loss of support, connected services, and critical security updates—not automatic deletion of the local company file.[1] Access can still depend on license and subscription conditions, so confirm the exact product rather than treating this as a guarantee.
Can I keep using it only for historical reports?
That may be a different and lower-frequency use than active payroll, payments, or banking, but it still needs a retention plan, readable backups, access control, a compatible computer, and an answer for how records will be produced later. Keep active books on a supported workflow.
Should I move straight to QuickBooks Online?
Not automatically. First inventory Desktop-only features, third-party integrations, inventory, job costing, payroll, report layouts, user roles, and accountant preferences. Rehearse the candidate migration on a copy and compare reports before choosing it as the live destination.
Does a verified QuickBooks backup include payroll forms?
No. Intuit says the company-file backup does not automatically back up payroll forms and provides a separate preservation procedure.[3]
Should I run Verify and Rebuild before upgrading?
Verify is a reasonable integrity check. Rebuild is not a generic lifecycle fix; Intuit positions it for integrity problems found by Verify, requires a backup, and says to verify again afterward.[4] Assisted Payroll users have an additional stop-and-contact instruction.
Your next 15 minutes
- Press F2 and record the exact QuickBooks product, year, release, and company-file path.
- Mark yes or no for payroll, bank feeds, payments, emailed forms, Workforce, and Accountant Copy Transfer.
- Record the last successful date for each service you use.
- Do not send a live paycheck or customer charge as a test.
- Schedule a backup-and-reconciliation session with the bookkeeper, accountant, payroll owner, and IT support.
Treasure Coast help: If a QuickBooks 2023 dependency has already stopped or you need a careful backup-and-migration workbench, The IT Guys serves Port Saint Lucie, Jensen Beach, Fort Pierce, and Vero Beach. Bring the F2 Product Information details and the names of the services your business uses—never email us an unprotected company file.
Sources
- Intuit QuickBooks — QuickBooks Desktop 2023 service discontinuation policy.
- Intuit QuickBooks — QuickBooks Desktop Payroll discontinuation policy.
- Intuit QuickBooks — Back up your QuickBooks Desktop company file.
- Intuit QuickBooks — Verify and rebuild data in QuickBooks Desktop.
- Intuit QuickBooks — Move your QuickBooks Desktop company file to QuickBooks Online.
Evidence boundary: These sources establish Intuit’s listed 2023 discontinuation effects and its documented backup, payroll, file-check, and migration paths. They do not prove the state of a specific company file, tax filing, bank reconciliation, license, or third-party integration.