- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
As another EasyACCT customer affected by the 2025/2026 release, I want to reinforce how serious and widespread these issues are.
The current 2026 build continues to break core payroll and reporting functions that many firms rely on daily. Documented problems include:
- Payroll reports by department producing incorrect totals or unusable output
- Employees missing from earnings reports or excluded from totals
- Payroll journals by employee failing or returning blank results
- Manual processing and write-check functions behaving incorrectly
- Display and view screen regressions affecting usability
- Restores causing missing employees or corrupted company data
- Backups losing checks, deposits, or entire companies
These are not edge cases. Multiple users in this forum have reported the same failures over several weeks, with updates either failing to resolve the issue or introducing new defects. Some reports describe shifted payroll history, incorrect YTD and QTD calculations, and data being overwritten during roll-forward. At this point, the risk moves beyond inconvenience into compliance exposure.
From a practical standpoint, what many firms need right now is stability, not another rushed patch.
A reasonable and responsible solution:
- Keep the 2025 EasyACCT version active and supported
- Push updated 2026 federal and state payroll tables into the 2025 engine
- Allow firms to run live payroll, quarterlies, year-end forms, audits, and bank reconciliations on a stable platform
- Publish a clear timeline for a fully corrected 2026 release with detailed release notes covering payroll, reporting, journals, backups, and display fixes
No one expects development to stop. Users expect a safe fallback path. Forcing migration to a version still showing payroll, reporting, and data-integrity failures puts firms in an impossible position.
Leaving the 2025 version available with current tax tables gives customers a way to stay compliant while your team completes a proper fix. That approach protects users, reduces support strain, and restores confidence in the product.
Please give customers the option to work safely until the 2026 version proves production-ready.