Why cant's EasyAcct allow for 2026 payroll and posting in the 2024/2025 program which worked so we can work

[dkurtzke]

No ETA on Bank Rec Program which crashes and looses data.  

For a firm like yours, this isn’t inconvenience — it’s:

• Inability to close year-end books

• Delayed financial statements to business clients

• Corporate returns delayed

• Staff sitting idle or doing workarounds

• Reputational risk

• Potential client loss

That’s measurable financial damage, not user frustration.

When a vendor:
 Takes payment
 Markets professional reliability
 But can’t deliver core functions
 And gives no restoration date

[Lucius]

Yes, you can do it by:

1. If you have opened a company in 2025/2026 and entered something:

- Export everything that has been done in 2025/2026. Save a copy of folder "26TTBLS."

- Install 2024/2025 and copy "26TTBLS" to the installation folder.

- Restore the very last company file in 2024/2025. 

- Import the exported in 2024/2025. 

- Enjoy the issue-free 2024/2025.

2. If you just opened a company in 2025/2026 and have not entered anything:

- Install 2024/2025 and copy "26TTBLS" to the installation folder.

- Restore the very last company file in 2024/2025. 

- Enjoy the issue-free 2024/2025.

Note that you can't e-file or print 940 for 2025 in 2024/2025. Other than this, is there any reasons we have to use and suffer the sluggish and slow 2025/2026?

For 940 filing, finish up everything you need in 2024/2025, back it up and open it in 2025/2026 just for e-filing and printing. Always make backups since EasyACCT is currently unstable and unreliable.

Just sharing a workaround that may help some despairing people like me. I am not responsible for any issues that may occur. 

[dkurtzke]

Due to ongoing operational failures following the recent software conversion, the firm has implemented a temporary dual-system workflow to ensure continuity of financial reporting and timely tax return preparation.

This procedure has been established to allow completion of year-end financial closing processes while the server-based production environment remains partially nonfunctional.

This interim procedure was implemented to:

Prevent delays in corporate tax return preparation

Maintain accurate year-end financial reporting

Protect client service continuity

Preserve revenue flow during peak filing season

This action represents a business continuity safeguard necessitated by software malfunction, not a change in standard accounting policy.

Laptop Installation (Restored Conversion Backup) 2024/2025	Official year-end close, adjusting entries, reconciliations, and tax reporting
Server Version	Ongoing operational activity and POS transaction processing

The laptop file is designated as the authoritative tax reporting ledger for the 2025 year-end close.

This interim procedure was implemented to:

Prevent delays in corporate tax return preparation

Maintain accurate year-end financial reporting

Protect client service continuity

Preserve revenue flow during peak filing season

This action represents a business continuity safeguard necessitated by software malfunction, not a change in standard accounting policy.

[Victoria C]

Lucius - this is pretty much what I've done and it looks like it's going to work. geez what a terrible mess.