Group Term Life issue (GTL)

We are having issues with our Group Term Life calculation on employee's that have a change during the month. We process our BN150 for frequency = P (biweekly pay period). Wondering what others use for their As of Date on the BN150? We are currently using the pay period check date for the As of Date and pay period end date for the Time Record Date.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

We use the pay end date which would be a Sat for us. The check date is the following Thursday.

matt-mcdevitt

We use the pay period end date for both the As of Date and Time Record Date fields.

plancor

Hello, I'm hoping that there might be more information related to this old post. We, too, use a BN150 Frequency of P=biweekly pay period and an effective date and time record date of the pay period end date. When an employee's life insurance enrollment changes mid-pay period (for example because of a pay change), the BN150 is only reporting the number of days that the new enrollment has been effective. For example,within a pay period April 20 - May 3, there are old life enrollment records ended April 30 and new life enrollment records dated May 1. The BN150 is only reporting three days and the cost associated with only three days. We expect it to report 14 days where the first 11 days are from the old life enrollment and 3 days are from the new life enrollment. How do others handle life enrollment changes that occur mid pay period? Thank you

0911060553270289.pdf

Legacy Contributor

I just discovered an issue with our BN150 calculations yesterday. Our BN150 is the same as yours (Frequency = P; As of Date and Time Record Date = pay period end date). This gives me a place to start looking at the calculations. I haven't had a chance to dig into it to see what's going on. I did go back and look at history - it seems this started at the beginning of 2020. Prior to that the GTL amounts we fairly consistent from one check to the next.

lcjohnson

We had this issue as well. We had to install CTP 120832 back in January.

karin-jensen

I noticed the issue plancor described when I ran the BN150 for the first pay period of 2020. I ended up running two separate BN150s with two different dates to capture the entire pay period...but I'm interested in an overall fix.

lcjohnson, I noticed that the "read me" file for CT120832 says the issue occurs when the first record has a begin and end date that is the same date, but I'm wondering if that's true, or if it also holds true for records that don't have the same begin and end date--just when there are two different records active during the pay period. Can you speak to that?

lcjohnson

Hi KJensen, Yes, we had the exact issue that plancor describes above. If an employee's pay rate changed in April, their Basic Life would update effective 5/1. Our bi-weekly pay period ended on 5/2, so when this week's payroll runs, it would only calculate for the 2 days (5/1 and 5/2) at the new rate. We would expect it to calculate 12 days at the old rate that ended 4/30 and 2 days at the new rate effective 5/1. Our payroll department actually discovered this issue back in October, but we didn't get a resolution and the CTP entered until January.

Copyright © 2025 Infor. All rights reserved.