2018 conversion - Earnings tab in Employee Maintenance - skipping qtr 1

SUGGESTED

I am having the same issue.  The benefits are also all in the 2nd qtr.  

Parents
  • 0
    SUGGESTED

    KB 93052 Fixed on Payroll Update 2.18.4.0.  Should be in the read-me notes.  This was a conversion issue so the fix was in the conversion program.  In order to get the prior years history fixed, you would need to perform a new migration/conversion. The prior year-to-date history is does have the correct value and this does not affect current year data.  We are aware that this affected only Prior year Earnings and Deductions quarters.   I have not heard anything about the Benefits as that does not store data by quarters.  Please let me know if I have missed something.

  • 0 in reply to Linda KR

    ???  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.

  • 0 in reply to TomTarget

    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. 

  • 0 in reply to [email protected]

    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.

    .

Reply
  • 0 in reply to [email protected]

    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.

    .

Children
No Data