RS (Plans) - Health Savings and Flexible Spending Accounts - Enrollment Stopped and Deduction Duplic

We experienced a strange phenomenon in BN32.1 where some Health Savings Account and Flexible Spending Account plan enrollments terminated 11/30/2020 either due to voluntary cancellation or contribution change. However, the deduction was duplicated, which meant another deduction record with the same start date as the corresponding benefit record was created ending 12/3/2020, The original deduction record ended 11/30/2020 as expected. The affected employees had deductions or duplicate deductions in December where they should not have, I've no clue what caused this issue much less how to prevent it. I do know how to correct it when it is caught PRIOR to payroll processing - delete deduction cycles. Has anyone experienced this situation? Thank you.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Accepted answers

All comments

unknown

Good morning Karen, yes, we reported this issue to Lawson support back in May and they are STILL flubbing around trying to come up with a solution. If you can, please open a support case so that they know other customers are experiencing this issue. In the meantime, we have created a process flow to look for these "extra" deductions and send us a list if it finds any, so that we can try to turn them off by zeroing out the balance or removing the deduction cycles proactively. FYI, if you look at the sequence number on the "extra" deductions in the EMDEDMASTR table, you will see that they are orphaned - the sequence number on each benefit deduction needs to match a sequence number on the corresponding BN32 record (BENEFIT table).

unknown

If I am reading this correctly, we just installed a CTP to fix this issue. For us, it was like @pbelsky states, an open, orphaned record on PR14 for an entry on BN32 that was closed. The CTP is 122463 and was released in August; we had first noticed the issue in June and surmised it was a result of the many W4 patches.

unknown

We had to paint-screen on EMDEDMSTR to fix since PR14 would not let us change the amount to anything but $0.01 and wouldn't let us add an end date because the deduction is tied to a benefit plan.

unknown

Hi lwoodworth, we installed this patch also but it did not completely correct the issue for us. We found that, once Lawson created the orphaned deductions, that they would continue to be created every time we needed to change the HSA contribution amount, even with the patch installed. We have > 200 employees with orphaned deductions in our system after moving a group employees to a different HSA plan. Lawson support is supposed to be working on a program to "fix" the orphans we already have, and then maybe the patch would work for us. They have delivered 2 iterations of the program to us so far, and neither has worked yet. Hoping the 3rd time will be the charm.

lwoodworth, may I ask, did you report the issue to lawson support, or just discover it and then find a patch and apply it? I am asking because it took months for me to get them to believe this was a real problem.

unknown

Also, when I asked lawson support if I could just add an end date directly in the EMDEDMASTR table (same as painting a screen) as you have done, I was told by them not to do it because it would "break the fix program." I was afraid I would lose the support I had already worked a couple of months to get from them, so I did not update the database.

unknown

I did not open an incident - we saw the CTP on the weekly patch notifications.

unknown

Thank you, @pbelsky! I did open an case with Lawson but all I got was a workaround to fix...not an acknowledgment that this type of issue had been reported before. I was thinking I would have to check each pay period end for "orphaned" deductions like you described until I could figure out what was wrong and the solution. I assume by "orphaned deductions, there is NOT a sequence number in the EMDEDMASTER table?

unknown

Thank you, @lwoodwoth for your response.

unknown

Correct, Karen. If you look at a BENEFIT record for your RS plan, you will see that there are 3 sequence number fields on the record, one for each type of deduction - employee pre tax, employee after tax, and company. So if an employee has an orphaned employee pre tax deduction for your RS plan, the sequence number of that deduction on EMDEDMASTR will not match any employee pre tax deduction sequence number on any the BENEFIT record for the employee for the RS plan.

I hope that makes sense!

unknown

Yes, it does. I compared an impacted employee's HSA deductions between the BENEFITS and EMDEDMASTR tables and found the matching sequence numbers you mentioned. Thank you!

Copyright © 2025 Infor. All rights reserved.