my mistake i have been doing so many upgrades my test environment for the client is pu4 and 2.18.4.  still has the earning and deduction issue in employee maintenance.  I am happy to say benefits came over correctly!!

I won't have time today to do this but I can reach out to you next week.  Please private message me with your contact and a best time to reach you.    Thanks

???  I noted that this fix was supposed to be effective for 2.18.4,  but I'm still seeing the issue with clients converting using 2.19..0.

Hi Tom:

My personal opinion, I wouldn't upgrade anyone on 2.19.0 unless you tested it yourself.  I have heard there are issues.  However; I have not tested it myself, I  plan to get to it this week.  I would upgrade everyone to 2.18.5; it is my understanding that is where the fix is.  However; i did notice the same problem with merging the wages in 2.18.5 in the earning and deduction screens.  Reporting is correct for fed and mostly State unless locality taxes are involved.   Hopefully you do not have to deal with locality taxes. 

I agree.  I don't push out to clients until I have used it myself for a while.  I installed and started using 2,18.x version in November 2017 and didn't let client's upgrade until around April.  I started more regularly upgrading clients over the summer.  Really started migrating clients in November and December due to changes in payroll taxes in Washington state for 2019 that the old program couldn't handle well.

Unfortunately,  you can never touch test for every possibility.  

Most of the issues that really mattered became more obvious as we hit year end processing, but things seem to be getting fixed and nothing was  insurmountable.

2.19.0 actually fixed a number of problems I had detected in 2.18.x versions.

I will admit that I just realized that 2.18.x is to 2.19.0 is really an upgrade  not a product update although to be perfectly honest I haven't seen any major changes in it.  I've kind of treated it like it was an update.

There was a significant fix in 2.19 regarding data conversions that affected us in Washington state for workers comp (codes would not transfer) so I have pretty much considered 2.19 to be a necessity for most of my clients.  There is also something in it regarding deductions with goals during year end processing that was fixed with a 2.19 hot fix.  I don't know if it was created by 2.19 or whether it was present in 2.18.  I have been advising clients to watch their deductions carefully on their first payroll in 2019.

.