@taxiowa  Product Quality Control in tax software has slowly and steadily declined over the past decade.  It is cheaper for the company to just release the software and let the users find the bugs in the code.  The users are the final quality control.

Ok, so the users find a bug.  There is no actual system in place to notify the company of the bug.  The company usually doesn't alert all of the users of the bug.  The company doesn't usually provide any updates about when the bug will be fixed, or a work around solution, or that an update to the fix the bug is in the most recent update.  The company doesn't usually tell the users when they decide they are not able or willing to fix the bug and you are on your own to find the work around that suits you.  Then, if they do release a software update that fixes the bug, the fix may very well change tax returns that have already been filed.  Or, it might change tax returns that you have already employed a work around on and after the update your work around is now making the returns compute incorrectly. 

So yeah, this is a big problem for the software users that has been steadily getting worse year by year.  You must constantly be on guard when an update comes through.  Did the current update change anything on the returns that were completed since the previous update, or worse yet, change something on returns that have already been e-filed successfully.

Iowa did change most of the Iowa tax laws and, of course, almost all of the Iowa tax forms.  Obviously it's a very large programming project.   But the program code should have been completed last summer/fall and the software should have been ready to roll in January.  Instead, the programmers seem to be writing the code in the middle of the tax filing season.  It's no wonder that the programmers have created new bugs during the filing season.      

FUBAR!