Non-employees - Required deductions

We are in the process of adding non-employee into Lawson and are planning to use our existing process levels, depts, job codes, etc. To differentiate the non-employees we are using employee status. Wondering how others have handled Required Deductions when using a status for non-employees? We currently have several required deductions that are created based on the process level that the employee is assigned to. Thinking this will have to be greatly expanded to include process level & status so all these deductions are not automatically created for the non-employees. How have others handle this?

Find more posts tagged with

Comments

Legacy Contributor

We testing using a second company to house all non-employees. All non-employees will go to the same department in the second company and 1 of 4 process levels. As non-employees are added to the system a user field will be utilized to show the actual department(s) they work for. The goal was to avoid day to day maintenance of keeping the department information the same in both companies.

moellerg

We keep all of our non-employees in a separate company. We require very little in the non-employee company.

jreese

Like Greg, we keep all our non-employees in a separate company. One reason is that you don't need as much information on the non-employees so you can change the number of required fields plus they don't ever get mixed up in Payroll. I would not suggest mixing employees with non-employees in the same company if you can avoid it. The only caveat is that if one of the non-employees/contractors is in a management position we do need to create a second record for them in the main company so that they have MSS access to their direct reports.

Legacy Contributor

Can you assign employees to the non-employee if they're in different companies? Example on Assignment tab HR11 add the non-employee Supervisor to an employee record.

Legacy Contributor

We are also in the process of adding non-employees to Lawson and trying to decide whether to create a new company or process level in the current company. Since they will not be paid the position code will not have any expense/payroll information. I have tried creating a new company or process level but they both require GL information. What GL information do you use in Lawson for the company or process level.

sriman-shivakoti

I am planning on using different process levels. I did have to put in some GL info but since we will not be paying them, I am not expecting anything to pass to the GL.

deanna-plant

For those of you doing this in a process level and/or company, how are you keeping the federal and state deductions from automatically being created?

sriman-shivakoti

With the employee status set to NN - no pay, no benefits, I have no taxes being created.

deanna-plant

Thank you Margie. We have tested and it is functioning as you have indicated.

Legacy Contributor

We are considering doing something like this. Do you think this would work in the following situation? We included extended medical benefits for spouses during last year's VERP (Voluntary Early Retirement Plan) offering. We have provided the same offering (although rare) within a few severance packages. The issue is that these folks are on a spreadsheet, not housed in Lawson, which means they aren't picked up on our weekly file feeds to vendors. Now that we are outsourcing benefit management, the same issue arises - they can't be in the feed if they are not in Lawson. So we were considering adding the spouses in a different company??? Another option is for developers to create a quick table that we can populate with existing participants, then add as necessary, whereby our feed logic would pull from Lawson then add from this other non-employee table. Thoughts?

Legacy Contributor

All of our non-employees are held in a separate company with little GL set up. We built the minimum needed to add an Employee record (status, process level, departments, location codes, Personal Actions for terms and rehires, etc). This allows us to keep them completely separate from our paid staff.

Copyright © 2025 Infor. All rights reserved.