Resources who are both an employee and a non-employee

I am being asked if our current setup of employees and non-employees is the Infor recommended setup, so I'd like to see how your organizations are handling this. When we implemented Infor Global HR, we were advised to set up people who are both an employee and a non-employee as two separate resources (so the same person has 2 different employee IDs), and we have two RelationshipToOrganization values, including EMPLOYEE and NONEMPLOYEE. And when an employee leaves the organization, the status is changed to TERMINATED, but if a non-employee leaves the organization, the status is changed to INACTIVE. Is this how your organization handles this as well? If not, how do you manage people who are both employees and non-employees in GHR?

Your help is appreciated!
Sally Fields, HR Systems team at Children's Mercy Kansas City

Find more posts tagged with

Global HR General Discussions

Comments

jreese

We have the non-employees setup in a separate company. Like you the RelationshipToOrganization is NONEMPLOYEE. The reason for the two ids in our case is for security needs for our clinical system. The Status for both are TERMINATED.

unknown

We are a hospital with volunteers, agency staff, contractors, etc. We also have non-employee supervisors of employees. We schedule clinical non-employees in WFM. We have one number for one person. The relationship-status-worktype are based on the primary work assignment. We use assignment type to then break into employee vs non-employee types. Most interfaces are based on the primary work assignment and relationship. But the few that need to use secondary work assignments can do so.

rm_benefit_administration_aca_training.pptx

sfields

Gina, We also use the assignment type field on the work assignment to classify our non-employees, as all are in 1 of 2 job codes (99999 non-employee and 99998 non-employee manager). And we too allow non-employees to manage employees. We were cautioned against putting the work assignments of non-employee and employee roles on the same record, but I do love the idea of one number for one person. It's confusing when it comes to user provisioning, for example, when we want them to have the same email -- two actors (Actor for us = EmployeeID) can't have the same mingleID (mingleID = email address).

sfields

Also I should note that many of our downstream systems (e.g., Active Directory and our LMS system) can't accommodate non-primary work assignments.

unknown

We used to have an outside tracking number for non-employees and separate clinical log ins. But we are implementing EPIC and are using GHR to consolidate all person tracking into the one number one person framework. We will still have secondary badges for a CA who is also a nursing student her on degree rotation. We are partnered with a research university so most of our docs are univ employees, so affiliates to us.

Hannah Johnson

Hi Gina, we also have what we call our Contingent employees in the same HROrganization and break out by WorkAssignment. Curious though how you handle Hiring those Non Employees when they apply and are offered a paid position (not sure if that happens for you?).

We are struggling with this part now that we are on Talent Acquisition because we want them to apply as external but since they're already in our system, we can't Hire but have to Transfer which is a huge mess. We also struggle with the Turnover/Hire rates since we want to track that based on their Employee start/term dates and not their contingent.

Any feedback you could provide would be greatly appreciated!

Copyright © 2025 Infor. All rights reserved.