BN105 not resetting match limit

We created a new match limit schedule for our Roth/401k plan and ran BN105 - New deductions were created on PR14 but the limits were not reset. PR999 was run before the payroll.
Has anyone seen this before?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

Check out this article and patch

KB 1677154
Deduction amount/percent of benefit plan not following Cumulative Schedule (BN19.4) upon add of Benefit Plan

mp33580

Thank you. Did you have to apply this? Or did anyone?

unknown

A client had the same problem you described, but with 403b. This CTP was the Infor recommended solution. As far as I know it fixed the issue, but I have reached out to them to see how the fix went, and I will get back to you when I hear something.

unknown

Yes, I had the same issue last week. Never had a problem in prior years, but we upgraded to v10 in October. We are hosted and have to schedule patches to be applied, so I had to do a manual fix, because payroll had to process. I did a query of the pr14 records (to get the sequence number) and then our payroll department did an upload to change the PR14 record to the correct amount.

mp33580

An update - we applied the patch and BN105 worked like it used to in LSF9 for anyone that had only a pre-tax or only a Roth. The limits did not reset/re-calculate for anyone that had both the pre-tax and the Roth, so now I have to go back in and calculate the balance limits for those manually and then upload the changes to PR14. I re-opened my ticket with Infor.

There is something else wrong with LSF10 that we have had a ticket open with Infor for several months on with no response, and that is that if an employee has both the pre-tax and the ROTH, and you change the pre-tax percentage on BN32 instead of starting a new plan, a new pre-tax deduction is created on PR14, and an end date isn't put on the old deduction, so the employee gets both of the match deductions. We didn't find this until we had been on LSF10 for a few months so we had some employees with 6 active match deductions. IT had to go directly to the EMDEDMASTER table to put stop dates on the old deductions because PR14 would not let us enter a stop date. This was not happening in LSF9 and our deductions did not change. If anyone else has experienced this I would like to hear from you.

unknown

we are experiencing the same issue with the limits not resetting, can you provide the patch # you applied?

mp33580

KB 1677154
Deduction amount/percent of benefit plan not following Cumulative Schedule (BN19.4) upon add of Benefit Plan

d-wilcox

We have a match limit of $7800 per year. Of course there are a few employees who reach this limit. I normally run the BN105 to reset but I forgot this year and the first 2016 payroll amount added to 2015 balance for one employee and did not give the match to another. It sounds like you don't necessarily have to run the BN105 each year but then how does the limit reset?

mp33580

I got this from Infor today on the issue above where the BN105 did not reset the limits for 401k/Roth in one plan, or a ROTH alone.

Priority 2 JT-878073 has been sent to Development. We will notify you when the fix is available.

Copyright © 2025 Infor. All rights reserved.