You’re offline. This is a read only version of the page.
We have had 2 different customers who have had issues with deductions automatically inactivating when they use a deduction end date. Even if the end date is well after the pay period end date, the deductions are inactivating automatically and are not being taken. The same deduction remains active for all employees that were not given an end date. It is definitely not a change and roll-down situation as we have isolated it to happening during the payroll calculation step. In both cases the companies are using a particular third party product however, the third party refuses to take responsibility or even consider the possibility that it is their issue. The question is, does GP inactivate benefits at all or simply stop processing the deduction once the end date has been reached?
Thanks!
*This post is locked for comments
Greenshades provided a fix once the verified that the issue was with their Benefits Enrollment software.
We know there are no changes in class. We have already logged it as has the third party and the changes always show under the name of the person who did the calculation or ran their synchronization, both actions have caused the issue. We checked the employee before running the sync or the calc and they were active and then checked immediately after and they were inactivated. No one else was in the system. The third party is a benefit enrollment software package which, in both customers, is installed but is not set up yet. The package is supposed to verify that the employee is enrolled in the current instance of the benefit (current year) and inactivate them if they are not. I suspect that, since the employee is not entered into the Benefit enrollment software, the system is seeing the end date and then checking to see if they are currently enrolled. Since they are not in, it is not seeing them as being currently enrolled and is inactivating them. They refuse to entertain the idea, however. Even though they saw the change after the synchronization was run as well. I spent over 12 hours working with MS support on this the first time it happened on this same customer and we are certain it is nothing related to GP.
We will not inactivate a deduction, but we will not take it based on the end date and how it falls with the pay period dates, so yes it would not be taken in the payroll, but it would typically stay active. The only time I see the auto inactive happen is with Class ID changes if they are doing that, and the class does not have the benefit or the deduction then it will inactivate it.
You could always install the detail activity tracking tool, it is free, then it tracks who is changing the record and when if this will help you narrow it down.
mbs.microsoft.com/.../NOAM_PSTL
Thanks
Terry Heley
Microsoft
Deanne, There are no limits and the employee had plenty of money left. The issue is that the Inactive Box automatically got checked when payroll was calculated and every time the sync with the third party was run (we tested multiple scenarios). I have never seen the box automatically check itself under any other conditions.
Could there be a dollar amount limit somewhere? Also, did the employees have enough funds to have this deduction taken?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,151
Super User 2024 Season 2
#2
Martin Dráb
229,993
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (