Entering new hires / terminations / transfers during payroll cycle

Does anyone allow the entry of new hires, terminations and/or transfers while payroll is processing?

We currently hold these types entry payroll is running. However, we are implementing a new security system where they want to pull position information from Lawson to determine what building/department access the employees should have. To make this work, we would no longer be able to hold entry - employees would need to be in the correct position/status on the effective date for them to have the correct access. The vendor of the security system says they have clients who also use Lawson and this works for them.

Thanks.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

We just started testing updating transactions prior to their effective date. We wouldn't be entering them while payroll is running. We did run into some issues with the process. We bring time records from KRONOS. We also needed to change our schedule rule on the PA06 to be a "2". For us, we believe them to be minor.

I have not had a chance to speak to our IT dept, but, I am thinking that maybe our interface data to KRONOS could be pulled by pending actions instead of HRHISTORY.

Here are our issues:

Changes made with a future effective date are seen immediately in ESS and MSS.

If an employee goes from nonexempt to exempt and we have updated the PA in Lawson, there is an error message on the time record if they had OT in the payroll being processed for time worked the past 2 weeks. We had to change the exempt flag back to allow the OT to process.

We pay our barg unit employees by step and grade schedule but non barg are not, so if you go from not having a schedule, grade and step to having one, the rate of pay won't be populated on the time record. I guess I should say we don't store rates of pay in KRONOS.

The last thing has to do with term dates. If we term them in KRONOS, then the time records won't extract from KRONOS. Not sure, if that is our PAYDATA interface issue or not. We will be exploring that.

I'd be interested in hearing from others as well.

0911060553270289.pdf

lcjohnson

I'm resurrecting this old post.

We use Lawson Talent Management 10.0.2 as our system of record, and interface to S3 for Payroll, Benefits, and Absence Mgmt using the LT101. We currently hold all Actions for the new pay period until the Payroll run is complete for the prior pay period. This was mostly done out of habit from our legacy system. For a number of reasons we would like to start processing the actions as soon as the new pay period starts. We tried this in our test system, and although the pay rate that pulled on the check was from the previous pay period (based on the eff date), the Department/Accounting unit was from the new pay period. We didn't test the exempt flag, so that may be an issue as well. Has anyone else experienced this issue? We logged a Case and they were able to duplicate the issue and created a Jira ticket.

I imagine we are one of the few company's that have been holding these actions until after payroll. Has anyone else had this issue?

Thanks!

sriman-shivakoti

We jsut started entering them as you mention. We changed a rule on our PA06 to help with some of the issues you mention above. We pay many employees via step and grade schedule so that rule had to be switched to primary position.

We also don't put them in too far in advance because the HR11 displays the "new" information regardless of the date of the personnel action. I think ESS and MSS displays the same as the HR11. It has been a while since we tested so my memory gets a little foggy on the details.

Legacy Contributor

We are all S3, moving to foundations/LTM next year. We always process hires in advance, even during payroll cycle. We process transfers on the first Monday of the payperiod in which they are effective (our payroll closes on Tuesday) and we process terms after the payroll is complete (Tuesday evening). We have a scheduled job that "holds" all our transfers that come from our Recruitment Management System (RMS) until the payperiod starts. We schedule PA100 to run for the current payperiod only for everything but hires. We use MSS for terms so we just don't push them from the Inbasket until Tuesday. If someone manually enters an immediate change while payroll is running, that causes problems but otherwise, it has been fine for several years using that process.

Copyright © 2025 Infor. All rights reserved.