How to report imputed GTL, code C box 12, on W2 when noncash pay class includes other types of nonca

Hello group,

This is our first year end on lawson payroll. We are in process of doing test runs of our W2s and here is the situation we have found ourselves in: We originally set up our PR27 by entering our noncash pay class, which contains other pays in addition to group term life, into the GTL parameter. When we ran a test print of W2s, we saw that code C box 12 for group term life was showing the sum of all the non-cash pay sum groups included in our noncash pay class. We did some digging and found information in the 2017 payroll year end guide which said that Lawson was functioning as designed - if we used the pay class in the parameter, it would report the total of every pay in the pay class. The guide also mentioned the use of PR11 and the year end fields on HR11 as an alternative. We tried these on a single employee, and they worked as described - the correct amount printed for code C box 12. My question is, is this truly the best practice? It seems very clumsy and error-prone to have to track imputed GTL for the W2 manually for each individual employee. Is there a batch program, or something else I am missing, that can help me populate these fields automatically? I figured there must be other customers out there who have more than one noncash pay sum group in their payclass, so I am hoping to get some feed back on how others handle this. Thank you!!!

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

karin-jensen

We have separate pay classes for Noncash and GTL. While our Noncash pay class includes the GTL, the GTL pay class is set up ONLY with those pay summary groups that should be reported in Box 12 with code C. Then in your PR27, use the GTL pay class rather than the Noncash pay class. WAY simpler than using PR11!

unknown

Thank you kjensen your reply is really helpful, and here is why! I think we tried what you are describing and it did not work, BECAUSE we did it "after the fact" for payroll year 2017... All during 2017, we had all of our non-cash pay codes assigned to a single pay sum grp, not a one-to-one paysumgrp paycode relationship. This single pay sum grp was then assigned to the noncash pay class. Then, at W2 time, we created the new GTL payclass, and I have a feeling it was already too late for 2017! It sounds like you are saying that if we start doing what you have done (and for the payrolls that have already occurred in 2018, maybe do some sort of adjustment), we should be ok GOING FORWARD. Does this sound correct / make sense?

karin-jensen

That could be it. We've always had separate pay codes and pay sum groups for our various noncash fringe, so creating a GTL pay class with only the GTL pay sum groups after the fact wasn't a problem for me.

2011-10-27_CH-Stammtisch_2.pdf

unknown

Thanks again kjensen for taking the time to reply and share what you have done. We are going to try your set up in one of our test environments, and I am hopeful that it is going to get us where we need to be!

matt-mcdevitt

FYI - We also have the same setup as KJensen - one pay class for GTL only and another pay class for all noncash codes, including GTL. Also, I believe you are correct in stating the GTL pay class needs to be setup at the beginning of the year before 2018 payments are created. I believe any codes added/removed mid year on the PR20.3 Pay Summary Group Relationship screen will only post data into that pay class from that point forward.

michael-butler

I believe you could also use the PR11, it will still be by employee but I am sure you do an upload using add-ins

sriman-shivakoti

I think there is a mixing of terms in this thread. A pay summary group differs from a pay class. Pay classes are set up containing one or more pay summary groups. Pay summary groups can belong to many pay classes. Data is stored in the many tables used for payroll historical processing at the PSG level. On some tables the PCD seq no exists so you can extract based on pay code when joining on that sequence number and the sequence number in the PRPAYCODE table.

sriman-shivakoti

One more thing I will add, all your non cash pay summary groups (pay codes) need to be included in the Noncash Pay Class defined on the HR00. We have most of our pay codes set up as a one to one relationship to pay summary groups.

unknown

Thank you Turner and Michael! I thought I'd share what we learned about the PR11 here, in case it might help someone later: We have found that sometimes those multiple line forms can be tricky to upload to, so we are going to upload

the GTL amounts to HR11, in the Reportable Insurance field on the Year End tab. HR11 is straightforward to upload to - and doing this actually puts the value on the PR11.

unknown

Thank you Margie, you are exactly right, this is how we got into trouble, because all of our noncash was under the same PSG, which is under the one noncash pay class that Lawson allows on HR00.

Copyright © 2025 Infor. All rights reserved.