The Payslip Modeler enables employees and payroll administrators to model a paycheck/payslip by running a mock payroll run.
Employees can use this feature to make decisions regarding various benefit options and savings using the estimates. They can check their estimated take-home pay based on an upcoming bonus or tax refunds.
Payroll administrators can use this feature to answer employee queries or to perform what-if analysis.
The terms Payslip Modeler/Paycheck Modeler refer to the same functionality. The application displays these terms depending on your localization.
The Payslip Modeler feature is enabled by default for these localizations:
Australia
India
Canada
Mexico
US
South Africa
UK
Contact your system administrator to check if this feature is available for your localization.
For more information, see Using Payslip Modeler, Oracle Self Service Human Resources Deploy Self-Service Capability Guide
See: Setting up Payslip Modeler
Before you can use the Payslip Modeler, you must ensure to set up the following:
Set the profile option HR: Enable Payroll Simulation to Yes to use this module. If the profile option is set to No, you cannot use the Payslip Modeler.
See: User Profiles, Oracle Human Resources Management Systems Configuring, Reporting, and System Administration Guide
Set the profile option HR: Enable Multiple Assignments for Payroll Simulation to Yes to select the secondary assignment when there are multiple assignments. If set to No, then you can run the payslip modeler process on the primary assignment only.
See: User Profiles, Oracle Human Resources Management Systems Configuring, Reporting, and System Administration Guide
Enable or disable the payslip modeler at the Payroll level by specifying Yes in the Enable Simulation field. You cannot run a payroll run and payslip modeling simultaneously. If the Payslip Modeler is enabled, then you can set the locking period, which is the number of days before and after the specified date when the payslip modeler is enabled to make the changes. This restricts users from making updates to payroll information while modeling their payslip during a mock payroll run during the specified period.
See: Defining Payroll, Oracle HRMS Payroll Processing Management Guide
Specify the document type as Payslip Modeler in the Self-Service Preference window at the business group level or the organization level.
See: Entering Self Service Preference Information, Oracle HRMS Enterprise and Workforce Management Guide
Create an element set and include the elements that you want to exclude from being processed in the modeling process. Specify the element set in the Modeler Exclusion Element Set field in the Self-Service Preference window at the business group level or the organization level. This skips the elements within the element set from being processed while running a modeling process.
Specify the Payroll Simulator Template in the Self Service Preference window at the business group level or organization level. If no template is specified, then the application uses the default template to generate the model payslip.
The following table lists the predefined templates that are available for different localizations.
| Localization | Predefined Template | Technical Name |
|---|---|---|
| Australia | AU Payroll Simulator Template | PAYAUPSSM |
| India | IN Payroll Simulator Template | PAYINPSSM |
| Canada | CA Payroll Simulator Template | PAYCAPSSM |
| Mexico | MX Payroll Simulator Template | PAYMXPSSM |
| US | US Payroll Simulator Template | PAYUSPSSM |
| UK | UK Payslip Template | PAYGBPSSM |
| South Africa | ZA Simulated Payslip Template | PAYZAPSSM |
Note: You can also create your own template associated with the Data Definition PAY<LEG_CODE>SIMPAYSLIP.
See: Entering Self Service Preference Information, Oracle HRMS Enterprise and Workforce Management Guide
To enable an element to be available for payslip modeling, query the element and select Yes in the Enable Simulation field in the Element Extra Information window. You can enter input values for this element required for simulation in the Element Description window.
Important: Only user enterable input values are available for Payslip modeling.
If the Multiple Entries check box is enabled for an element, then you cannot use this element for payslip modeling. Instead, create a copy of the base element, enter input values, attach the appropriate formulas and balances as the base element and then use this element for payslip modeling. Ensure that this new element is not used for payroll run.
It is necessary to create a new element for the corresponding Multiple Entries Allowed element and set up the new element as Yes for Enable Simulation. Ensure to specify the previously created element as Original Element under Simulation Details for the new element. Enter input values, attach the appropriate formulas and balances to the new element. This is to ensure that Simulation ignores the Original element entries in Simulation run and uses only new element entry.
Example to Understand the Restrictions on Multiple Entries Allowed Enabled Elements
You cannot select Yes for the Multiple Entries Allowed enabled elements. This is an expected behavior of Paycheck/Payslip Modeling.
For example, consider an employee with an Overtime element. This element entry is added on the days when an employee works overtime. In a month, if the employee does overtime for 10 days, then this element entry gets added 10 times. If the employee wants to model a paycheck and view the net take home after working overtime for 10 days or more, then it will not be practical to add 10 entries for 10 days in the Paycheck Modeling page. Instead, the employee can add the total overtime hours. Therefore, you can use an element that indicates the total overtime hours for the pay period instead of each day. If there are already some Overtime entries added to the employee in the application for the current period, then it is necessary to suppress these entries when the employee tries to model overtime hours so that Paycheck Modeling/Simulation gives desired results depending on the inputs.
To handle this scenario, the Overtime element (the elements with Multiple Entries Allowed) is not allowed to be directly enabled for simulation. Instead, it is necessary to create a new element to support simulation.
The element created for simulation can have validations to the input values. Specify any rules or validations on the maximum number of hours that can be entered, for example, overtime entries can accept a maximum of 5 hours per day, then these can be relaxed in the new element to suit the requirement of simulation so that 50 hours can be entered for the complete month in a single entry.
For the new element, it is necessary to specify the existing Overtime element as the Original Element in the Simulation Details. This will ensure that whenever the employee tries to model overtime hours using the new element, then any existing overtime element entries are ignored during Paycheck Modeling/Simulation.
See: Defining Elements, Oracle HRMS Compensation and Benefits Management Guide
Note: There is a restriction for the predefined elements being used for payslip modeling. For predefined elements, if you set up the details in one business group, then these details will be accessible to other business groups. For example, it is not possible to enable Input Value A for one business group and Input Value B for another business group for the predefined element Regular Salary. This limitation occurs for predefined elements applicable to all localizations. Therefore, if there are multiple business groups, then you must define a single structure for the predefined elements.
If there are custom elements, then the custom elements are accessible only for that business group.