Skip to main content
Solved

2026 Tax Engine Update changed options with no explanation of what the options mean

  • March 10, 2026
  • 4 replies
  • 129 views
  • Translate All

My client had to run the Tax Maintenance this week and there are now blank rows, the Values don’t have dropdowns and for example the Select Filing Status was Single, Married Filing Jointly, Married Filing Separately and Head of Household, but now everyone updated to an “S” with no options:

Is anyone else experiencing this issue? 

Best answer by jennifergable17

​@Sonia Echols I did open a case with Acumatica and we had to Reset Cashe and Reset Application, that fixed the additional lines and the dropdown for the values, but that cause the social security numbers to reformat leaving out numbers and moving the dash in the wrong place.  Acumatica stated that, “The issue appears to be caused by a bug, which has been addressed in 2025R2 Service Pack 1 Patch 2 (25.201.0213.2). We have not been given a timeline for when the SaaS environment will be upgraded to this version. In the meantime, as a workaround, you can add the fields manually via the UI or by using an import scenario.”

View original

4 replies

Sonia Echols
Acumatica Moderator
Forum|alt.badge.img+2

Hi Jennifer,

Please open a case with support.

Thank you,

Sonia Echols

 

Translate

​@Sonia Echols I did open a case with Acumatica and we had to Reset Cashe and Reset Application, that fixed the additional lines and the dropdown for the values, but that cause the social security numbers to reformat leaving out numbers and moving the dash in the wrong place.  Acumatica stated that, “The issue appears to be caused by a bug, which has been addressed in 2025R2 Service Pack 1 Patch 2 (25.201.0213.2). We have not been given a timeline for when the SaaS environment will be upgraded to this version. In the meantime, as a workaround, you can add the fields manually via the UI or by using an import scenario.”

Translate

Sonia Echols
Acumatica Moderator
Forum|alt.badge.img+2

​@jennifergable17,

Thanks for the update, and I’m sorry your customer ran into this issue.  Thank you for posting the workaround in case someone else hits the same issue.

Sonia

Translate

jschindler
Freshman I

When upgrading our production environment to build 25.201.0213, we also experienced this issue. Restarting the application and clearing the cache from within the Apply Updates screen did resolve the issue for us. 

Translate