Payroll Relationship Type Mappings

Define payroll relationship type mappings for each HCM Cloud legislation. The mappings control when the application creates payroll relationships for a specific type of person such as employee or candidate. The mappings also define if the person type is processed by Cloud Payroll.

Oracle HCM Cloud delivers predefined payroll relationship type mappings for all the supported country extensions. If you're configuring a legislation that isn't predefined by Oracle, define mapping rules for all person types including candidates that the legislation uses. The Configure Legislation for Human Resources task would create mapping rules for person types such as employee. You can use this task to create any person type mapping rules that aren’t predefined by Oracle.

This table summarizes the behavior of the application when a person type is mapped to these payroll relationship types.

Note: Few legislations have extended this list of payroll relationship types to meet their country specific requirements.

Payroll Relationship Type	Application Behavior
Standard	Creates a payroll relationship and includes the person in payroll processes.
Element Entries Only	Creates a payroll relationship, but doesn't include the person in payroll processes.
Pending Worker Standard	Creates a payroll relationship and includes the person in payroll processes
Pending Worker Element Entries Only	Creates a payroll relationship, but doesn't include the person in payroll processes.
Candidate Standard	Creates a payroll relationship and includes the person in payroll processes.
Candidate Element Entries Only	Creates a payroll relationship, but doesn't include the person in payroll processes.

Note: If a person type isn't mapped to a payroll relationship type, the application doesn't create payroll relationships. In this scenario, you wouldn't be able to capture payroll information for the person type such as salary, element entries, and personal payment methods.

Payroll Relationship Type Mappings Example for US Legislation

Payroll relationship types are mapped to one or more person types for each legislation.

Here's an example of the mapping rules predefined for the US legislation.

Person Type	Payroll Relationship Type	Process in Payroll
Employee	Standard	Yes
Retiree	Standard	Yes
Non-Worker	Non-Worker	No
Contingent Worker	Contingent Worker	No
Contingent Worker Candidate	Candidate Element Entries Only	No
Employee Candidate	Candidate Standard	No

Here, Employee and Retiree person types are both mapped to the Standard payroll relationship type. If a US worker has both employee and retiree assignments within the same PSU, the application will group these assignments under the same payroll relationship.

Note: Use the Configure Legislation for Human Resources task in My Client Groups to view the predefined rules for your legislation.