2025-2026 Update Bugs

[VPMgmtMike]

After installing the 2025-2026 EasyACCT update, as I opened each company it took an extended amount of time to convert the files (20 minutes or longer). When I opened an updated company, my computer was extremely slow, We lost the decimal places on statements, my mouse cursor would not stop spinning. After waiting on hold forever, Tech support assisted me in reverting back to the 2024 version. For the price of this software, I expect better. When I asked if I would be notified when the bugs in the update were fixed, the reply was probably not. Unacceptable Intuit! 

[nickeypoo72]

I can't believe there have been this many varied issues with a new year's program roll out!  😞  I've been using this program over 30 years and this may be the worst I've seen so far.  Hope they get it fixed ASAP!  In the meantime, we'll be using the old version until someone comments things are working smoothly!

[VPMgmtMike]

Agreed!

[DividoAcct]

Completely unacceptable!  We too updated to the 2025 two weeks ago and had the same issues so we lost three days of data and returned to the 2024.  Sadly with the year end approaching the 2024 doesn't offer us the W2's etc.  Tech support told me that it's possible that they wont have it fixed any time soon.   Even worse is that they still have it available to upload so many are doing so without knowing what we know.

[Kathi_at_Intuit]

Hi @VPMgmtMike Thanks for posting in the Community and for sharing here. We understand it’s important for the software to function smoothly, and it can be very frustrating when it doesn’t. The development team is aware of the behavior you’re seeing and they are actively working on a resolution and we appreciate your patience as this is being addressed. You will be notified as soon as a fix becomes available.

[Kathi_at_Intuit]

@nickeypoo72 Thanks so much for being a long-time customer and for sharing here in the Community. We know how frustrating it can be to encounter issues during a new year’s rollout. Our Development team is aware of the concerns and is actively working to get them resolved. We appreciate the patience and we will notify you as soon as a fix becomes available.

[Kathi_at_Intuit]

Hi @DividoAcct Thank you for sharing your experience with the update. We understand how important year-end processing is and how challenging it can be when the software doesn’t perform as expected. The development team is aware of the concerns reported with the 2025 release and is actively working toward a resolution. You will be  notified when a fix becomes available.

We also appreciate you pointing out the concern about others installing the update without knowing the current limitations. That feedback has been shared with the appropriate teams.
 

[TScott1]

Does EasyAcct Professional 2024/2025 version not allow the 2025 W2s & 1099 info to transfer to the 2025 Info Return System?

[Alicante06]

I agree with you 100%.  Can you tell me how you returned to the 2024.  Did you have to Uninstall the 2025/2026 program first and then sign in online to download the previous year 2024?  Thank you in advance.  

[Kathi_at_Intuit]

Hi @TScott1 Great to see you in the community and thanks for posting. Here is a helpful article about transferring, it states the transfer from EasyACCT to Info Return System only works if you are on the same version in both programs. 

How to transfer forms 1099, W2, 940 and 941 from EasyACCT to the Information Return System

If you need further assistance with this please reach out to EasyACCT Support. They will be able to help with this. 

[Kathi_at_Intuit]

Hi @Alicante06 Nice to see you in the Community and thanks for posting about how to return to the 2024/2025 program. For this, we recommend contacting EasyACCT Support directly. They are best equipped to asist you with this. 

[Mark398]

Will there be an update instead of rolling back?

[Kathi_at_Intuit]

Hi @Mark398 Welcome to the Community and thanks for posting! Our development team has been releasing updates to fix concerns in the 2025/2026 program.  If you need further assistance with the program we recommend reaching out to EasyACCT Support. 

[Kathi_at_Intuit]

Hello all,

There is a new release of EasyACCT now available – Version 2025.1.10.

This release includes the following items below:

• GL report is showing incorrect information from sales Journals
• EasyACCT Client transfer does not give an option to transfer in payroll transactions
• EasyAcct is sorting by the first number on Employees, and Vendors

We know this release does not cover all concerns that have been raised, but we wanted to keep you updated on the progress being made. We will continue to share updates as more become available.

Thank you!

Kathi

[IntuitSuzi]

Hello, all!

There is a new release of EasyACCT available. Update to the latest version:

https://accountants.intuit.com/support/en-us/help-article/update-products/check-version-easyacct/L05...

For those using Hosted, the update will be available this upcoming weekend.

[Alicante06]

Status Update — Latest EasyACCT Release Installed / Bank Reconciliation Issue Still Unresolved

For visibility and record-keeping:

I received notification today of a new EasyACCT release and have updated to the latest available version. After updating, I can confirm that the bank reconciliation issue remains unchanged.

Specifically, prior-year reconciliation data (outstanding checks and deposits, uncleared items, and cleared transactions) still does not carry forward, leaving the bank reconciliation incomplete and inaccurate. This issue has now remained unresolved since it was first reported on 12/12/25.

This confirms that the most recent release does not address this blocking defect. Given the duration of the issue and its impact on core accounting functionality, further clarification on escalation status, prioritization, or targeted resolution sequencing is increasingly important for planning purposes.

If other users have updated to the latest release and are seeing the same result, please confirm here for visibility.

Thank you.

[robert-bly]

I downloaded the program today.  Had the same issue with the bank reconciliation.  

[Neil Luong]

Still having problems with the payroll module.

[awh]

Will all date entered since the download revert also, or will there be data loss?

[awh]

Ignore that.  I found the answer.  It would have been helpful if Intuit had pulled the update when it realized there were serious issues.  We updated this week - unfortunately.  Do we have an estimated repair date?

[Kathi_at_Intuit]

Hello All, 

Thank you for sharing the details in the Community. We hear the concern that it would have been helpful to pause or pull the update once problems were identified, and that feedback has been shared with the appropriate team for review. 

While some concerns have been addressed, we recognize there are still items that need to be resolved. Your continued input on what is working and what is not is helpful, and we appreciate everyone continuing to speak up so these issues remain visible and known. We will continue posting updates directly in the community threads.

At this time, we do not have an estimated timeline for all fixes. However, the most recent release (Version 2025.2.01) included the following updates:

• 2026 Tax Tables and Form W-2
• Enter Transaction screen issue where the amount disappears when tabbing to the Open Manual Payroll Entry screen from the Reference cell
• A/P invoices dated on the first or last day of the month not appearing on the AP GL Distribution report
• Ability to delete employees from the Employee Information screen
• Earnings Report filter excluding valid employees
• Bank Reconciliation showing the period in the Payee/Description field
• New Vendor Account Number not saving or displaying when created via the transaction entry flow
• Automatic invoices not calculating
• A/P automatic invoices not generating and displaying an error message
• Earnings record and Employee Information not matching the Payroll Journal

Please continue to bring forward concerns. Every item raised is shared with our support and development teams for review. Your feedback truly matters and helps guide where focus is needed most.

If you are still experiencing any of the items listed above after installing Version 2025.2.01, please contact EasyACCT Support so they can take a closer look with you.

Thank you again for your patience, honesty, and for continuing to speak up. We know this has been a difficult rollout, and we genuinely appreciate you hanging in there while we work to get the necessary fixes in place.

Kathi

[StahlManager]

All these issues are unacceptable considering how much we paid for your product!!  I'm having issues with the A/R GL distribution and summary telling me that I have "No records indicated"  not only for December, but the entire year!!  I spent 4 hours on the phone with customer service last Friday and have an active ongoing ticket that still hasn't been resolved.  I haven't closed the year and can't start inputting anything for the new year until this issue is resolved.  My employees are not going to be happy if I can't compile payroll checks this week!!!  Stopping making excuses and resolve the issues today or you'll be issuing refunds before the week is up!

[VPMgmtMike]

Hi Kathi,

 Thanks for the update. Please let me know when ALL of the bugs have been fixed. Until then we are sticking with the 24-25 version. We cannot halt all work for our entire office to try an update that may or may not work and then have to once again revert to the old system. If your corrections are not complete by the end of the month, we will be forced to manually create W-2's for our employees. That is a lot of extra work! We expect so much more from Intuit. Will Intuit be issuing a credit or a refund for each day the 2026 update is not working? 

[awh]

Thank you so much for the reply!  A list of issues we are aware of at the moment:

Bank Reconciliation:  When continuing a prior reconciliation, current and prior transactions are all missing.  When transferring in for a new reconciliation, software goes to file error, then run time error, then closes the program.

Payroll reports by employee:  We were unable to get this to work on one account, but, oddly enough, were able to get it to work on my largest account - although it took 12 minutes to fully populate.  It seems that some of this may be hit or miss - works on some clients but not on others or works on one day but not the next.

It is Extremely. Slow.  Cannot stress this enough.  Takes about 20 minutes to close write up on my largest client.

We are relieved that live payroll ran successfully today, and the ACH file posted to the bank without error.  This was a very small client, however (ten employees).  Will have much larger payrolls this week and are hopeful for no issues.  We also have not had issues so far running G/Ls or other reports as some posters here have relayed, though it did take about fifteen minutes to run a 28-page GL.  We have run some quarterly payroll reports, and they seem to be working, albeit slowly.  Most pressing issues at the moment are inability to reconcile and processing time.  There is a tremendous amount of work to be done by February 2nd, and we really cannot afford the delays that the software is causing.  Hopefully all will be resolved soon.

[awh]

One more issue to note:

In payroll manual processing, when adding an after the fact check, the program will not move to the next blank record to enter the next check.  We had to close and open manual processing again to get it to proceed.  We had this issue on two different clients.

[awh]

Transfer to information return system is also still not working.  Is there any new information from Intuit regarding status or progress on software repairs?

[Kathi_at_Intuit]

Hello All,

You are welcome for the updates, and we appreciate and thank everyone for taking the time to share both what is working and where frustrations remain. We understand this has been a difficult and frustrating rollout. We have reviewed this forum and gathered all feedback shared to help ensure nothing is falling through the cracks. All concerns raised have been provided to the appropriate Support and Development teams.

Updates are being delivered in releases, and there is not a single milestone where everything is addressed at once. As fixes and changes are released, we will continue updating this thread with what is included so that anyone who comes across the discussion later can easily see what has been resolved.

If anyone is experiencing freezing, one step that may help is moving the company file to a different location and testing again. Any new posts in this thread will also be reviewed to make sure each concern is known and tracked. We will continue to monitor everything closely.

Thank you again for sharing detailed feedback and ongoing observations.

[Kathi_at_Intuit]

Hi @awh we do not have an estimated time when this or all will be fixed. We will keep updating the post as updates become available. 

[StahlManager]

Kathi,

I haven't seen a single new release come through other than 2025.2.01 and obviously that hasn't fixed anybody's problems.  If this isn't fixed by tomorrow, I will be asking for a credit for everyday that I haven't been able to use this software!!! 

[suetax]

I just discovered another issue with Accounts Receivable. I just entered some payments and it posts the payment under the correct client in customer information with the correct payment advice # and date. When I print the payment advice, it lists a different client and a different date, but the payment advice #, invoices paid and the amounts are correct. When I try to print a transaction register for the payments posted, it says "No records exist for this range". I entered the date that was used to post the payments which is showing up correctly under the customer information but when I try to print a transaction register it says no records exist. I printed a Detailed Aged Receivable Listing and the invoices that were paid were taken off like they should be.

I am also having trouble closing 2 different clients for year 2025. So far these are the only 2 that I have had issues with when closing the books for 2025. I get an error message when I am closing the General Ledger that says "Unable to close the General Ledger module with a year-end date of 12/31/24. Before proceeding you must first close the following modules. The current year-end dates for the modules are: A/P Year-end date 12/31/23" I went to the screen to close the A/P and it says "Last Vendor Year-end Close: 12/31/25", if I close this it will put me in 2027 and I want in 2026. How can I get it to let me close the General Ledger for 2025 so I can enter 2026 transactions?

[StahlManager]

Suetax,

I haven't even attempted to close 2025 yet because my A/R GL distribution is showing "No records exist" for December and the entire year.  I was trying to close out my December before closing out the year, but I can't do that. I spent 4 hours on the phone with them last Friday and another 2 on hold on Monday before speaking with someone.   Right now I have had to figure up my payroll the old fashioned way and hand write checks until I can close out 2025 and start 2026.  I'm completely frustrated and angry that this company can't get this problem fixed in a timely manner! This makes so much more work for all of us to endure and they need to pay for that!  I will make it my mission to not let them get off the hook for this one.

[VPMgmtMike]

I agree 100%

[awh]

Questions:

The programmers should know the answer to this by now:  Are these issues with file paths, or is data actually missing/corrupted?

If the program changes little (and it does) from one year to the next, how could so many issues have occurred at once?

Have the programmers worked directly with any subscriber regarding the issues, given that this problem is now well into it's second month?

Has Intuit deprived EasyAcct of resources in hopes that it will be able to phase it out and possibly increase subscriptions to QB?

Just curious.

[DividoAcct]

I agree!

[mikeyst28]

Of course they have. That is not a new development. The last few years they seem to put no resources into EasyAcct and try to push everyone toward QB. You can't even find Easy Acct on their website without searching into the depths. If you try to contact customer support EasyAcct is not even a selectible option, you have to go through a Lacerte option. QB sucks and we will never switch to that and I'm sure many others feel the same way. Drake is going to get a lot of new business very soon...

[Toshia]

Is it safe to enter information into this 2025-2026 software or run payroll? Any response would be appreciated. thanks

[mikeyst28]

If you already installed the update and rolled stuff over then I don't see an issue. If you have problems then they are probably already there the minute you did the update. We haven't had any issues yet with payroll or data entered in 2026, most of the major issues are with the rollover.  Just this morning while reconciling accounts we found 2 payroll checks from December that are just completely different after the rollover. Wages, tips, taxes, all just completely different amounts than what were shown when the payroll was run in December. So now how do we know if any of our w-2s are correct?

[bduteau]

You can add vendor reports not printing which makes 1099 preparation very difficult.  Like many others I the minute I get though tax season I will be looking at other options.  Your lack of care for the professional community and attempts to push us to QuickBooks is unacceptable.  

[DividoAcct]

QuickBooks is the last place that I'll land.  Although we reverted back to the previous version our staff did loose 3 days of keying.  W2's are going to take days to complete that would have otherwise taken hours.  It's all simply unacceptable.

[Rayb78]

I keep checking on here to see if there any updates to our issues!

After the update, on one account so far, it deleted a current employee when I went to do the first payroll of 2026 ( I did not hit delete terminated employees) and added that person's wages for 2025 to an inactive employee!  I called on Dec 30th, rep said others were having the same issue and it would be noted.