Oracle Fusion Cloud Payroll 23A What's New

Expand All

MAY MAINTENANCE PACK FOR 23A

Revision History
Overview
Feature Summary
Payroll
1. Payroll for Mexico
  1. 1. Profit Sharing Reporting Enhancements

MARCH MAINTENANCE PACK FOR 23A

Revision History
Overview
Feature Summary
Payroll
1. Payroll for the United Kingdom
  1. 1. Legislative Changes for the Tax Year 2023-24
2. Payroll Controlled Availability
  1. Payroll Controlled Availability Features
  2. 1. Payroll for India

Update 23A

Revision History
Overview
Feature Summary
Payroll
IMPORTANT Actions and Considerations for Payroll

May Maintenance Pack for 23A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Module	Feature	Notes
28 APR 2023			Created initial document.

Overview

HCM Cloud applications have two types of patches you can receive that are documented in this What’s New:

Release Updates (23A, 23B, 23C, and 23D)
Optional Monthly Maintenance Packs to each update

It is important for you to know what Release Update your environment is on. You can find this in your Cloud Portal.

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our products better, please let us know. To enter an idea go to the Ideas Lab on Oracle Customer Connect. In this document wherever you see the light bulb icon after the feature name it means we delivered one of your ideas.

____________________

Date	Module	Feature	Notes
24 FEB 2023			Created initial document.

Date	Module	Feature	Notes
30 JUN 2023	Global Payroll	Adjust Individual Balance Responsive Page	Updated document. Revised feature information.
28 APR 2023	Global Payroll	Adjust Individual Balance Responsive Page	Updated document. Revised feature information.
28 APR 2023	Global Payroll	RetroPay Late Hire Additions	Updated document. Revised feature information.
31 MAR 2023	Global Payroll	Adjust Individual Balance Responsive Page	Updated document. Revised feature information.
31 MAR 2023	Global Payroll	Calculation Entries Additional Fields	Updated document. Revised feature information.
31 MAR 2023	Global Payroll	Enhanced Reports Available and Previous Versions Are No Longer Supported	Updated document. Revised feature information.
31 MAR 2023	Global Payroll	Values Defined by Criteria: Multiple Values Support in the Payroll Run	Updated document. Revised feature information.
31 MAR 2023	US Payroll	Regional Pay Data Report Enhancement for California	Updated document. Revised feature information.
24 FEB 2023	Global Payroll	Enhanced Reports Available and Previous Versions Are No Longer Supported	Updated document. Revised feature information.
24 Feb 2023	Global Payroll	RetroPay Late Hire Additions	Updated document. Revised feature information.
24 Feb 2023	US Payroll	New Hire State Electronic Report Enhancement	Updated document. Revised feature information.
02 DEC 2022			Created initial document.

SUGGESTED READING FOR ALL HCM PRODUCTS

HCM Common What's New - In this What's New you will find feature that are used across applications.
Human Resources What’s New - In the Global Human Resources section you will find features on the base application in which other application are built upon.

NOTE: Not all Global Human Resource features are available for Talent and Compensation products.

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1). These documents identify bug fixes and possible known issues. You will also need to review these documents based in the release update version you are currently on or will be moving to.
Oracle Help Center – Here you will find guides, videos and searchable help.
Release Readiness – New Feature Summary, What’s New, Feature Listing Spreadsheet, Spotlights and Release Training

GIVE US FEEDBACK

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

	Ready for Use by End Users (Feature Delivered Enabled) Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.
Feature	Report	UI or Process-Based: Small Scale	UI or Process-Based: Larger Scale*
Payroll
Global Payroll
Effective Date on Professional Payroll Pages
Adjust Individual Balance Responsive Page
RetroPay Late Hire Additions
QuickPay - Process Configuration Group Parameter
Values Defined by Criteria: Multiple Values Support in the Payroll Run
Autocomplete Rules for TimeCard Required and Overtime Period within HR Flows
Values by Criteria: Text Support in Payroll Run
Compile Formula Additional Parameters
Ability to Record Costing Information as part of a Global Transfer
Calculation Entries Additional Fields
Include Payroll Details in Change Assignment Approval Notification
Export Payroll Run Results
Export Payroll Balance Results
Global Payroll Replaced or Removed Features
Enhanced Reports Available and Previous Versions Are No Longer Supported
Payroll for Canada
CPP and QPP Exemption During Mid-Period Payroll Transfer
Load ROE Reasons Mappings Using HCM Data Loader
Enhanced Reporting Information Card
Support for HR and Payroll Data Validation Reporting
Payroll for Mexico
Work Risk Incident Premium Validation
Support for Dynamic Payroll Relationship Groups
INFONAVIT Involuntary Deduction Enhancement
Payroll for Oman
Social Insurance for GCC Citizens
Gratuity
Payroll for the United Kingdom
P60 End of Year Statement for Tax Year 2022-23
Benefits in Kind Proration on Mid-Period End or Termination
Court Order Processing Fee Override
P45 Flow - Errors and Warnings Report
P11D Audit Report Includes Person Number
LGPS – Calculation of Employer Contributions for Absences with Reduced Payment
Payroll for the United States
Regional Pay Data Report Enhancement for California
Regional Pay Data Report Enhancement
IMPORTANT Actions and Considerations for Payroll

Payroll

Global Payroll

Oracle Global Payroll is a high-performance, graphical, rules-based payroll management application. It’s designed to keep pace with the changing needs of your enterprise and workforce in order to reduce setup costs, administration, and processing time. It operates globally and consistently in every country supported by Oracle. It uses a highly scalable processing engine that takes advantage of the features of the Oracle database for parallel processing, resulting in optimal performance. In countries with payroll extensions delivered and supported by Oracle, the application delivers the calculations, tax reporting, and regulatory rules required to accurately process payroll and remain in compliance.

Effective Date on Professional Payroll Pages

A new Effective Date field is displayed on the following professional payroll pages:

Payslip
Person Results
Third-Party Person Payment Methods
View Process Information Groups

The effective date gives a date context to the data you are viewing on the page. The effective date is the same as the date you enter on the Advanced Person Search page.

However, if you don’t enter a date on the Advanced Person Search page, the effective date defaults to today’s date.

Use the Effective Date field to view information on a page as of a specific date. For example, if you have selected a date of 27, October 2022 and chosen to view Last 3 Months payslips, you can view your payslips for prior three months.

For payslips, the effective as of date is editable, and you can enter a different date. However for the other 3 pages, the effective as of date, is read-only and appears on the top right hand side of the page.

Use the effective date on some of the professional payroll pages to easily identify the date context for the data you are viewing on the page.

Steps to Enable

You don't need to do anything to enable this feature.

Adjust Individual Balance Responsive Page

Use the Adjust Individual Balances task to adjust one or more balances for a worker as of a specific date. For example, use this task for any of these actions for an individual worker:

Correct balance entries from the Load Initial Balances process
Correct balances omitted during the balance initialization process
Correct balances with incorrect tax dimensions or incorrect tax jurisdictions

The adjust balances process adjusts one or more balances that are fed by the element you select in the Adjust Values section of the Adjust Individual Balances responsive page. Select the name of the payroll balance you want to adjust and enter the adjustment details.

When you select a balance, the Adjustment Element drop-down includes list of elements feeding the selected balance, and that the employee is eligible for. If there is only one eligible element, the name of the element is displayed as read-only text. If the employee is not eligible for any of the elements that feeds the selected balance, you cannot proceed further, and you will have to select a different balance or leave the Balance field blank.

Adjust Multiple Balances Flow

After you select the payroll balance you want to adjust and enter the adjustment details, and click Submit, the application uses the Adjust Multiple Balances flow to submit the changes for the employee. A name is automatically generated for the flow that includes the name of the employee and the date of the balance adjustment. For example, if you use the Adjust Individual Balances to submit balance adjustments for Susan Smith as on 08, November 2022, the flow name is 'Balance_Adjustment_Susan_Smith_2022_11_08'.

You can view details of the balance adjustments submitted for an employee on the View Flows, Process Results Summary, and Person Results pages.

Impacted Balances

The Impacted Balances section displays details of the payroll balances that are impacted by the adjustment. For example, the Bonus element with an element input value of Earnings Calculated feeds these three balances:

Bonus
Gross Earnings
Net Pay

Therefore, if you select an element input value of Earnings Calculated, and select any one of these three balances to adjust, the Impacted Balances section displays adjustment details of the other two balances. This section displays the current balance values for the employee and indicates the new balance values after the adjustment is submitted. Use the section to view and validate the impact of the change on other payroll balances before you submit the balance adjustments for the employee.

Costing and Payment Details Section

Use the Costing and Payment Details section to enable or disable the costing of the adjustment results.

Use these steps to disable costing of the adjustment results.

Navigate to the Setup and Maintenance area and search for the Manage Profile Options task.
On the Manage Profile Options, click Actions < New and create the PAY_BAJ_UI_COST_FLAG profile option.
In the Profile Option Levels section, select Updatable. Click Save and Close.
Navigate to the Setup and Maintenance area and search for the Manage Administrator Profile Values task.
On the Manage Administrator Profile Values page, search for and select the PAY_BAJ_UI_COST_FLAG profile option.
In the Profile Values section, click Actions < New and specify the level at which you want to set the profile value.
Select Site in the Profile Level field and N in the Profile Value field to disable costing of the balance adjustment results.
Click Save and Close.

The Include adjustment in costing process check box is deselected by default and the balance adjustment results aren't costed.

Select the Include adjustment in payment balance check box to pay the adjustment results. The adjustment run results are included in the next pre-payment process. The period in which this balance adjustment payment is included is determined by the Date Earned value.

List of Values for Balances and Elements on the

If you’re using any of these predefined job roles, then the list of values for Balances and Elements on the Adjust Individual Balances responsive page are secured by the security privileges defined for the roles.

ORA_CMP_COMPENSATION_ADMINISTRATOR_JOB
ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB
ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB
ORA_PAY_PAYROLL_ADMINISTRATOR_JOB

However, if you are using a user-defined role, add the aggregate privilege ORA_PAY_REST_SERVICE_ACCESS_PAYROLL_REFERENCE_DATA_LOVS to the role to secure the list of values. If you don’t add this privilege, the Adjust Individual Balances responsive page doesn’t display the list of values for balances and elements.

For more information on how to secure the list of values for balances and element for a user-defined role, refer ‘Secure List of Values for a User-defined Role for Balance Adjustments’ topic on the Oracle Help Center.

Adjust one or more payroll balances for an employee using the responsive Adjust Individual Balances page and view the balance adjustment results on the View Flows, Process Results Summary, and Person Results pages.

Steps to Enable

Create and use the PAY_BAJ_UI_COST_FLAG profile option to enable or disable the costing of the balance adjustment results.

Key Resources

RetroPay Late Hire Additions Feature is from a customer submitted idea.

You can now configure the event action to enable the Evaluate Late Hires flow pattern and automatically evaluate late hires, create a net pay result, and create retro event notifications. This allows you to process the late hires within the Recalculate Payroll for Retroactive Changes flow. This flow pattern now contains two tasks, Calculate Payroll for Late Hire and Late Hire Retropay Notification that replaces the need to manually enter an element entry against the late hire because the Late Hire Retropay Notification task automatically creates the notification. You can also now view the late hire details for an employee using the Person Results and Payroll Checklist pages.

Use the sample HCM Data Loader (.DAT file) to enable all or some of the following events:

Create Flow: If set to Y, generates the Evaluate Late Hire flow pattern with its Calculate Payroll for Late Hire and Late Hire Retropay Notification tasks.
Hire Date Later: If set to Y, the retroactive net pay result is generated when an employee's hire date is later than the payroll process date.
Run Payroll Relationship Group: If set to Y, the retroactive net pay result is generated even when the original payroll was run with a payroll relationship group.
Additional Assignments: If set to Y, the retroactive net pay result is generated when a late assignment is added to a payroll relationship.

The flow results are available to view in the View Flows, Process Results and Person Results pages.

Use the View Flows page to drill down into the Evaluate Late Hires details.

Use the Payroll Checklist page to drill down into the Evaluate Late Hires tasks details. Calculate Payroll for Late Hire details contain the payroll calculations and Late Hire Retropay Notification details contain the event notifications generated.

Use the Person Results page to drill down into the Calculate Payroll for Late Hires details.

Calculate retroactive pay for late hires using the enhanced RetroPay Late Hire solution. This feature automates the calculation of retroactive earnings for late hires by removing the need for manual intervention and view the late hire details for an employee using the payroll flow and checklist.

Steps to Enable

Section A – New Users of Late Hire Functionality

If you are currently using the Late Hire functionality, go to Section B because you don't need to create a new Event Group and only need to update your existing Event Action. New users, follow these steps:

Create a new Event Action for your legislative data group.

Use this reference data as a template to create your new event actions (Create Flow, Hire Date Later, Run Payroll Relationship Group and Additional Assignments) for your legislative data group. Set each to Y to enable, or N to not enable. In this example, we have enabled all 4 event actions:

METADATA|EventAction|FLEX:PAY_EVENT_ACTIONS_DDF|CreateFlow

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|HireDateLater

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|RunPayRelationshipGroup

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|AdditionalAssignments

MERGE|EventAction|ORA_CREATE_RUN_REL_ACTIONS|Y|Y|Y|Y|

<Event_Action_Code>|1950/01/01|4712/12/31|

<Event_Action_Name>|ORA_CREATE_RUN_REL_ACTIONS||SYNC||Y|<Legislative_Data_Group_ID>

Note: You can modify line MERGE|EventAction|ORA_CREATE_RUN_REL_ACTIONS|Y|Y|Y|Y| to set to your needs. The 4 Ys represent the enabling of the 4 event actions in order. For example, if you do not want to enable Run Payroll Relationship Group, your line should be MERGE|EventAction|ORA_CREATE_RUN_REL_ACTIONS|Y|Y|N|Y|

Update your Event Action in the reference data with following details:

Replace <Event_Action_Code> with event action code, such as MY_EVENT_ACTION

Replace <Event_Action_Name> with event action name, such as My_Event_Action

Replace <Legislative_Data_Group_ID> with LDG ID

Zip the modified template as EventAction.zip.

Create a new Event Group for your legislative data group.

Use this reference data as template to create your new event group for your legislative data group:

Update Event Group in the reference data with following details:

Replace <Event_Group_Code> with event group code, such as MY_EVENT_GROUP

Replace <Event_Group_Name> with event group name, such as My_Event_Group

Replace <Legislative Data Group Name> with LDG Name, such as US Legislative Data group

Zip the modified template as EventGroup.zip..

Upload EventGroup.zip and EventAction.zip using HDL.

Section B – Existing Users of Late Hire Functionality

If you are currently using the Late Hire functionality, update the existing Event Action HDL and reload. You need to ensure the new HDL contains the new Metadata for the |FLEX:PAY_EVENT_ACTIONS_DDF, as per the example below. Existing users follow these steps:

Use this reference data as a template to create your new event actions (Create Flow, Hire Date Later, Run Payroll Relationship Group and Additional Assignments) for your legislative data group. Set each to Y to enable, or N to not enable. In this example, we have enabled all 4 event actions

METADATA|EventAction|FLEX:PAY_EVENT_ACTIONS_DDF|CreateFlow

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|HireDateLater

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|RunPayRelationshipGroup

(PAY_EVENT_ACTIONS_DDF=ORA_CREATE_RUN_REL_ACTIONS)|AdditionalAssignments

MERGE|EventAction|ORA_CREATE_RUN_REL_ACTIONS|Y|Y|Y|Y|

<Event_Action_Code>|1950/01/01|4712/12/31|

<Event_Action_Name>|ORA_CREATE_RUN_REL_ACTIONS||SYNC||Y|<Legislative_Data_Group_ID>

Ensure the Event Action reference data for <Event_Action_Code> , <Event_Action_Name> and <Legislative_Data_Group_ID> are as per the previous Event Action HDL.

Tips And Considerations

Original payroll must have a run type of Regular.

Key Resources

See the Process Payroll chapter in the Administering Global Payroll guide.

QuickPay - Process Configuration Group Parameter

The Process Configuration Group parameter is now available on the QuickPay submission page. Use the parameter to select a process configuration group of your choice when submitting a QuickPay.

If you don’t make a selection, the process configuration group value defaults to what you have set using the ACTION_PARAMETER_GROUPS profile option. However, if you haven’t set the profile option and the field is left blank, then it defaults to the default group for the QuickPay process.

Use the Process Configuration Group parameter on the QuickPay submission page to select a process configuration group of your choice when submitting a QuickPay.

Steps to Enable

You don't need to do anything to enable this feature.

Values Defined by Criteria: Multiple Values Support in the Payroll Run

With this feature, you can now calculate one or more values in the payroll run using a Values Defined by Criteria. For example, your company calculates car allowance and housing allowance rates for an employee based on their job. The job criteria details and the allowance values are captured in a Values Defined by Criteria. You can now indicate which of the values captured on the Values Defined by Criteria should be calculated when processing an element in the payroll run.

This feature extends the flexibility of Value by Criteria as customers can now retrieve multiple values when calling a Value by Criteria directly in the payroll run.

Steps to Enable

To enable this feature, create value definitions using the following steps:

Create a value definition for each type of value held on the Values Defined by Criteria.

Select the calculation type that corresponds with the calculation type of the value. For example, if the car allowance value on the Values Defined by Criteria has a calculation type of 'Flat Amount', the car allowance value definition should also have a calculation type of 'Flat Amount'.

NOTE: Enter a value identifier only when you define multiple value records for a criterion. Newly added validation will prevent the calculation of rates when a value identifier is captured for values defined by criteria with a single value record.

Enter the following details in the Calculation Values region:
- Select Value Identifier in the Calculation Type Override field. This indicates the value definition will retrieve one value (from multiple values), held on a Values Defined by Criteria.
- Enter the name of the Values Defined by Criteria.
- Enter the name of the value in the Value Identifier field such as car allowance.

Associate the value definition to your element using a Calculation Factor.

Create Calculation Value Definition

Autocomplete Rules for TimeCard Required and Overtime Period within HR Flows

You can now derive the Timecard Required flag and Overtime Period in the Payroll Assignment Business Object, based on HR assignment attributes such as job, grade, or department, using Autocomplete Rules.

When you create the rules, you must select the "Field Modification Rule Type". The Business Object is "Payroll Terms", and the Field value is "Default Payroll Values Indicator". Refer the below screenshot for details.

Field Modification Rule Type

Assumption: HR assignments records must already be available so that the TCR and/or OP can be derived from them.

This feature provides a better user experience while working on HR assignment attributes.

Steps to Enable

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR). Please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1) to get access.

Tips And Considerations

Creating the Rule with Auto Complete

Autocomplete rules will be supported in the following transactions:

Hire an Employee
Add contingent worker
Add Non-Worker
Add Pending Worker
Add Assignment
Add Temp Assignment
Create Work Relationship
Add a Pending Worker
Create and Edit Offer

For further information about the related action type codes for the EMP_Groovy_ActionTypeCode HCM Params function, please refer to the Configuring and Extending HCM Using Autocomplete Rules guide

Rule Sample

In the example below, the Autocomplete rule enables the defaulting of OP and TCR flag based on the Business Unit in the New Hire (EMPL_ADD_EMP) Flow:

Rule Setup

Rule Logic

Limitations:

This feature is not valid for HR Assignment EFFs and DFFs.
It is not possible to derive the payroll attributes based on Salary. Salary basis is not an HR assignment attribute, it's a Salary record.

Key Resources

To enable Autocomplete Rules in the HCM Experience Design Studio, you need to log a Service Request (SR). Please review and follow the instructions provided in the My Oracle Support document, Enabling Oracle HCM Cloud Autocomplete Rules (Document ID 2767655.1) to get access.

Access Requirements

You must be granted the Human Capital Management Application Administrator role to work in a sandbox.

Values by Criteria: Text Support in Payroll Run

With this feature, you can now create a Values Defined by Criteria to capture text values based on a set of criteria such as assignment job and location. You can also retrieve the appropriate text value for an employee when processing the payroll run. For example, the text value could be the name of a rule or other type of condition that is used for payroll calculation purposes.

Create Value

When you create a value record for a Values Defined by Criteria, you can now select the 'Text' calculation type.

NOTE: It's not possible to calculate a rate from a text value. Therefore, rate definitions and the HCM Rates process cannot retrieve text information from a value defined by criteria.

This feature extends the flexibility of Value by Criteria as customers can now capture and return 'text' values that can be used for payroll calculation purposes.

Steps to Enable

You don't need to do anything to enable this feature.

Compile Formula Additional Parameters

Optimize performance of the Compile Formula process by using these additional Flow Parameters provided.

Additional Flow Parameters

Name	Lookup	Description
Status	Compiled And Not Compiled Not Compiled	You can compile only not compiled formula or compile all not compiled and compiled formula.
Scope	Predefined and User Defined Formula Predefined Formula User Defined Formula by Enterprise and LDG User Defined Formula by LDG User Defined Formula by Legislation	You can determine which formula to compile. This parameter restricts the set of formulas to those selected for compile
Process Multi-Threaded	No Yes	You can select whether or not to run multiple threads.

These additional parameters provide greater flexibility in the selection of the formula you want to compile.

Steps to Enable

You don't need to do anything to enable this feature.

Ability to Record Costing Information as part of a Global Transfer

With this feature, you can now record an employee’s costing information as part of the Local and Global Transfer transaction. For example, an employee transfers to a new legal employer and as a result the costing information changes; within the global transfer transaction, you can now record the new costing data for the target assignment.

A new Person Costing selection box is available when starting a Local and Global Transfer transaction. If you select it, a new region is displayed within the flow, and you can specify the Costing details for the new assignment. This region is automatically pre-populated with the source assignment’s costing details, and if you do not make any changes, the costing details will be carried forward to the new assignment. You can also update the costing details for the new assignment, as required.

Steps to use this feature

1. Select the Local and Global Transfer Quick Action.

2. Select the assignment to transfer.

Person Search

3. Select the Person Costing.

Selection

4. Enter the details in When and Why section.

When and Why

NOTE: The Costing Region will only be displayed if the new legal employer is different to the current legal employer, and if the change is permanent.

5. Enter the other regions and continue to the Person Costing section.

Person Costing

Person Costing is pre-populated with the current assignment’s costing details. If the details are not relevant to the new assignment, you can either delete them or make inline edits.

Edit

You also create additional rows if the costing is split across various cost centers. As long as the total percentage is lesser than 100, the Add button will be displayed.

Add

Approvals

Once you submit the transaction, it goes through an approval process (if the approval is configured). Since costing details are part of the transaction, they won’t be committed until the transaction has been approved.

NOTE: While the transaction is pending approval, you can update the source assignment costing details via Costing for Persons Quick Action; it will have no impact on the costing details entered for the new assignment.

This feature provides a better user experience while recording an employee’s costing information as part of the Local and Global Transfer transaction.

Steps to Enable

By default, the person costing region is disabled. To enable it, create a rule in the Transaction Design Studio.

Person Costing exists at 4 different levels:

Payroll Relationship
Assignment
Payroll Relationship Element
Assignment Element

NOTE: Only Assignment level costing is supported within the Local and Global Transfer flow. If you store the costing details at any other level than assignment, you should not be enabling this feature. Other levels will NOT get copied from the source to the target assignment.

How does this feature work with existing copy costing feature?

You enable either the copy costing feature or the costing region but not both.

The existing copy costing feature allows you to simply copy costing details from the source to the target assignment, without the possibility to override them. When enabled, you can choose on a case-by-case basis whether to copy the costing data to the new assignment or not. It supports all the 4 costing levels mentioned above.

The costing region allows you to view and update the assignment-level costing prior to submitting the transaction.

NOTE: When costing region is enabled, you must make it mandatory. This is to ensure that the end user visits the costing region and enters the costing data. If the region is not visited, no data will be copied to the target assignment.

Tips And Considerations

If both Copy Costing feature and Costing Region are enabled, the Costing Region takes priority, that is, the Copy person costing override to the new employment record flag on the Payroll region will be hidden.
When the Costing Region is enabled, no further copy will happen. If the costing data exists at other levels than assignment, they will NOT be copied to the new assignment, nor will any future dated costing records.

Calculation Entries Additional Fields

The Calculation Entries page provides an overview of all earnings and deductions that will be processed for an employee within a payroll period. Use the Creator Type field within the Standard Entries collapsed region to identify the origin of the element entry. For example, an entry displayed on the page can be a Salary Proposal, Element Entry, Balance Adjustment, and so on.

Within the detail region of Time and Absence, you can see if the entry has been processed or not processed by a QuickPay or Payroll process.

Use the Creator Type field to identify the origin of an element entry on the collapsed Standard Entries page. View the Time and Absence Entries region to identify if an entry has been processed or not processed by a QuickPay or Payroll process.

Steps to Enable

You don't need to do anything to enable this feature.

Include Payroll Details in Change Assignment Approval Notification

With this feature, you can now enhance the Change Assignment approval notification to include payroll details. If you have enabled the Payroll Details region within the Change Assignment flow, you can now include payroll data within your approval notification template.

This feature allows the approvers to view the payroll data entered as part of the Change Assignment transaction.

Steps to Enable

Payroll Details are now available within the approval notification data model. Update your Change Assignment notification template to include this data based on your business requirements.

Tips And Considerations

NOTE: Ensure that all ongoing approval notifications are closed prior to upgrade.

For transactions submitted but not closed before upgrade, the following rules will apply:

Level 1 approver will not see any payroll data in the approval notification.
Level 2 approver may see payroll data depending on whether Level 1 approval edited the transaction and what types of changes were made.
Payroll Assignment Details will never be shown in the Approval Notification after upgrade if the initiator visited the payroll region with Other Info enabled.

Key Resources

For more information on customizing the notifications, refer the Fusion HCM BIP Notifications: Best Practice to Customize the Report Template, Data Model or Sub-Template (Doc ID 2647434.1)

Access Requirements

To view the payroll data in the approval notification, a user should have one of the following aggregate privileges:

Manage Payroll Relationship
View Payroll Relationship

Export Payroll Run Results Feature is from a customer submitted idea.

You can now export an employee’s payroll run results into a file, such as a Microsoft Excel Workbook File. When you are viewing the run results on the responsive page, use the Export button to export to a file and save.

Result Details page

Export employee’s payroll run results into a file directly from the page.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Export feature supports the following:

The export feature supports Microsoft Excel and CSV file formats. The setting is controlled using the profile option File Format for Export to Excel.

The Microsoft Excel report includes a separate column for each attribute and label supported by the list view.

The order of the columns on the report is in the same order as the attributes within each row on the Results page.

The report shows the same filtered values as that shown on the Results page. For example, if you have filtered the information on the Results page based on Primary or Secondary Classification, the exported worksheet will include only the same information shown on the filtered Results page.

Any attributes that are hidden on the page aren’t included in the report.

The sort order of the rows on the page is the same as the sort order of the rows on the report.

All attributes displayed in the collapsed and expanded view are included in the export file. Some attributes, such as Element Name, are included in both views. As a result, the export includes Element Name column that displays this information for the collapsed view and a separate Element Name column that displays the same information for the expanded view.

The first column in the export is always blank. This is a format limitation of the export feature and doesn't impact the integrity of the exported information.

Export Payroll Balance Results Feature is from a customer submitted idea.

Use the Export feature on the responsive Balance Results page to export payroll balance results displayed for an employee on the responsive page into a file, such as a Microsoft Excel Workbook File. You can now export the following information captured on the list view:

Balance Name Results and Balance Group Results
Balance Feeds

The Export feature supports the following:

The Microsoft Excel report includes a separate column for each attribute and label supported by the list view.

The order of the columns on the report is in the same order as the attributes within each row on the Balance Results page.

The report shows the same filtered values as that shown on the Balance Results page. For example, if you have filtered the information on the Balance Results page based on Balance Name or Balance Group Name, the exported worksheet will include only the same information shown on the filtered Balance Results page.

Any attributes that are hidden on the page aren’t included in the report.

The sort order of the rows on the page is the same as the sort order of the rows on the report.

The balance result only supports export of collapsed view. This is because the expanded view is dynamic and displays information based on the selection.

Export the payroll balance results information displayed for an employee on the responsive Balance Results page into a file, such as a Microsoft Excel Workbook File to facilitate easy filter, view, and comparison of the results data.

Steps to Enable

You don't need to do anything to enable this feature.

Global Payroll Replaced or Removed Features

From time to time, Oracle replaces existing features with new features, or removes existing features.

Replaced features may be put on a path of removal, the features below will let you know what update you will have to have moved to the newer feature. As a best practice, you should move to the newer feature as soon as possible for full support and to stay up with the latest updates that the product offers.

Any feature that is removed, will have an Update in which that feature is no longer available. Please make necessary plans to move off the feature by the Update indicated, as it will no longer be available.

Enhanced Reports Available and Previous Versions Are No Longer Supported

Starting with 23A, the following reports will no longer be supported, and enhancements will not be made. These reports will be removed from the application starting with Update 23D.

Run Payroll Costing Report
Run Payroll Activity Report
Run Statutory Deduction Register
Run Payroll Register Report

Enhanced versions of these reports have already been delivered which provide better support for the extraction of payroll balances for large volumes of data.

Run Payroll Activity Report for the Latest Process
Run Statutory Deduction Register for the Latest Process
Run Payroll Register Report for the Latest Process
Run Periodic Payroll Activity Report
Run Periodic Statutory Deduction Register
Run Periodic Payroll Register Report
Run Payroll Costing Results

The new version of the reports are already available.

Use the enhanced reports that use a much lighter report template with enhanced performance and scalability capabilities to handle high volumes of data.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For additional information, refer the following resources on the Oracle Help Center:

Latest Process Year-to-Date and Periodic Balances Reporting in the Administering Global Payroll guide.

Payroll for Canada

Payroll for Oracle Human Capital Management for Canada supports country specific features and functions for Canada. It enables users to follow Canada's business practices and comply with its statutory requirements.

CPP and QPP Exemption During Mid-Period Payroll Transfer

The Canada Pension Plan (CPP) and Quebec Pension Plan (QPP) employee and employer contributions are calculated according to legislative rules, and the exemption amounts are honored in cases where an employee experiences mid-period payroll transfers (of the same frequency) in the same period. With this update the exemptions are only applied for one payroll, and the calculations of the taxes are more accurate.

Further support of the exemption amounts, and compliance to legislative rules.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Hot Topics Email (To Receive Critical Statutory Legislative Product News): To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information: https://support.oracle.com/rs?type=doc&id=2102586.2
- Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Load ROE Reasons Mappings Using HCM Data Loader

You can now load default values in mass for the Record of Employment (ROE) Reason mappings using the HCM Data Loader (HDL). The reason mappings are held at the PSU level, and are used for terminations and absences. Once these mappings are configured, they are used by the ROE archive process to derive the Record of Employment Reason for issuing the ROE.

Using the HCM Data Loader for the Organization business object (OrgInformation), populate these attributes:

HCM Data Loader Attribute	Functional Description
OrgInformation	The name of the component record. Specify ‘OrgInformation’.
FLEX:PER_ORGANIZATION_INFORMATION_EFF	The code for the organization flexfield of the component record. Specify one of the flexfield contexts listed here. The flexfield contexts are: ORA_HRX_CA_PSU_LOA_ROE_MAP ORA_HRX_CA_PSU_TERM_ROE_MAP
EFF_CATEGORY_CODE	The category code for the extensible flexfield for the component record. Specify ‘HCM_PSU_CA’.
EffectiveStartDate	The start date of the organization component record
EffectiveEndDate	The end date of the organization component record.
OrgInformationContext	Specify the same value as the FLEX:PER_ORGANIZATION_INFORMATION_EFF. The flexfield contexts are: ORA_HRX_CA_PSU_LOA_ROE_MAP ORA_HRX_CA_PSU_TERM_ROE_MAP
OrganizationName	The name of the legal entity.
ClassificationName	The name of the organization component record. Specify ‘Payroll Statutory Unit’.
LegislationCode	The legislation code for the classification component record. Specify ‘CA’.
SequenceNumber	The sequence number for the classification component record. Note: This is sequential according to the component context. For example, if loading 2 records for terminations, and 1 for record for absences, populate 1 and 2 for the rows for terminations, and 1 for the row for the absence.
oraHrxCaPsuLoaRoeUnique(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)	The unique sequence number identifier of the Record of Employment: Absences flexfield data. Enter a unique number for each record of this type. If multiple rows for the same type, increase each row number by 1.
oraHrxCaPsuLoaClsfName_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)	The secondary classification of the absence element for the Record of Employment Mapping for absences. For example, ‘Sickness’.
oraHrxCaPsuRoeLoaReason_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)	The absence reason for the Record of Employment Mapping for absences. For example, ‘Leave of absence’.
oraHrxCaPsuTermRoeUnique(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)	The unique sequence number identifier of the Record of Employment: Termination flexfield data. Enter a unique number for each record of this type. If multiple rows for the same type, increase each row number by 1.
oraHrxCaPsuTermAction_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)	The action reason for the Record of Employment Mapping for terminations. For example, ‘Resignation’.
oraHrxCaPsuRoeTermReason_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)	The termination reason for the Record of Employment Mapping for termination. For example, ‘Quit’.

These mappings are held at the Payroll Statutory Unit (PSU) level. Once these mappings are loaded, you can view them by accessing the Payroll Statutory Unit Details region using the Manage Legal Entity HCM Information task located in the Setup and Maintenance work area.

Supports the ability to create default Record of Employment mappings in bulk using the HCM Data Loader, in addition to the page.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

For additional information on the Record of Employment reason mappings, see the technical brief noted in the Key Resources section.

This is a sample Organization.dat file used to create the Record of Employment mappings for terminations and absences.

METADATA|OrgInformation|FLEX:PER_ORGANIZATION_INFORMATION_EFF|EFF_CATEGORY_CODE|EffectiveStartDate|EffectiveEndDate|OrgInformationContext|OrganizationName|ClassificationName|LegislationCode|SequenceNumber|oraHrxCaPsuLoaRoeUnique(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)|oraHrxCaPsuLoaClsfName_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)|oraHrxCaPsuRoeLoaReason_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_LOA_ROE_MAP)|oraHrxCaPsuTermRoeUnique(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)|oraHrxCaPsuTermAction_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)|oraHrxCaPsuRoeTermReason_Display(PER_ORGANIZATION_INFORMATION_EFF=ORA_HRX_CA_PSU_TERM_ROE_MAP)MERGE|OrgInformation|ORA_HRX_CA_PSU_LOA_ROE_MAP|HCM_PSU_CA|2001/01/10|4712/12/31|ORA_HRX_CA_PSU_LOA_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|1|1|ZHRX_CA_Compassionate Care|Compassionate Care, Family Caregiver|||MERGE|OrgInformation|ORA_HRX_CA_PSU_LOA_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_LOA_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|2|2|Sickness|Strike or lockout|||MERGE|OrgInformation|ORA_HRX_CA_PSU_LOA_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_LOA_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|3|3|Other|Shortage of work, End of contract or season|||MERGE|OrgInformation|ORA_HRX_CA_PSU_LOA_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_LOA_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|4|4|Maternity|Maternity|||MERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|1||||5|Global Transfer: Location Change|Employer bankruptcy or receivershipMERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|2||||6|Global Transfer: Career Progression|Shortage of work, End of contract or seasonMERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|3||||7|Global Transfer: Internal Recruitment|Strike or lockoutMERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|4||||8|Global Transfer: Manager Request|QuitMERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|5||||9|Global Transfer: Worker Request|Quit, Follow spouseMERGE|OrgInformation|ORA_HRX_CA_PSU_TERM_ROE_MAP|HCM_PSU_CA|2001/01/01|4712/12/31|ORA_HRX_CA_PSU_TERM_ROE_MAP|ZHRX_CAVS_LE_02|Payroll Statutory Unit|CA|6||||10|Resignation: Personal Reasons|Quit

Key Resources

Refer to these documents on the Canada Information Center for additional information.

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2

CA – Payroll tab > Product Documentation > Technical Briefs > Record of Employment Processing
CA – Payroll tab > Product Documentation > Technical Briefs > Loading Canada Data Using HCM Data Loader

Hot Topics Email (To Receive Critical Statutory Legislative Product News)

To receive important Fusion Canada Legislative Product News, you must subscribe to the Hot Topics Email feature available in My Oracle Support. Refer to the document below on the Canada Information Center for additional information.

https://support.oracle.com/rs?type=doc&id=2102586.2

Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Enhanced Reporting Information Card

You can now use the new, responsive Reporting Information page to capture the information required to create a reporting information card for an employee. The Reporting Information page captures information used for these types of reporting information:

ROE information:
- ROE Data
- ROE Vacation Pay
- ROE Statutory Holiday Pay
- ROE Other Monies
- ROE Comments
- ROE Special Payments
Quebec Labour Standards Contribution
Year-End Data

The page retains the existing reporting card functionality, but it is enhanced to improve usability, which improves the overall user experience. It also provides a consistent look and feel with other HCM responsive pages, other localization tax card pages, and the employee self-service tax card page.

This illustration displays a reporting information card with a ROE Data component.

To add a new component, click Add on the Reporting Information section and select the component.

Each individual component offers its own set of unique component details to capture. For example, the illustration below displays the fields to capture when adding the Year-End Data component. You may also add multiple types of components within this page.

With this feature you will see improved usability of the page, and improved the overall user experience.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Note the important tips and considerations below:

The Effective As-of Date at the top of the page drives the date of the information displayed.
The payroll field is not defaulted. It is selected by the user using an LOV. The LOV only shows the payrolls assigned to the employee. It displays the payroll that is processed where the Effective As-of Date on the card falls between pay period start and end dates.
The active Tax Reporting Unit on the employee's card displays based on the Effective As-of Date on the card.
For additional information on the Record of Employment components, see the Record of Employment technical brief noted in the Key Resources section.
For additional information on the Quebec Labour Standards Contribution component, see the Administering Payroll for Canada guide noted in the Key Resources section.
For additional information on the Year-End Data component, see the Administering Canada End-of-Year Processing guide noted in the Key Resources section.

Key Resources

Refer to these documents on the Canada Information Center for additional information.

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2

CA – Payroll tab > Product Documentation > Technical Briefs > Record of Employment Processing
CA – Payroll tab > Product Documentation > Payroll Guides > Administering Payroll for Canada
CA – Payroll tab > Product Documentation > Payroll Guides > Administering Canada End-of-Year Processing

Hot Topics Email (To Receive Critical Statutory Legislative Product News)

https://support.oracle.com/rs?type=doc&id=2102586.2

Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Support for HR and Payroll Data Validation Reporting

You can now use the existing Payroll Data Validation Report to report exceptions for missing or invalid HR and payroll data that is required for payroll processing and reporting in Canada. The report is enhanced to include validations on this data:

Payroll is not setup for the employee
Tax card is not created for the employee
TRU association is not created on the tax card
Province of employment is not set on the tax card
Home address is not set for the employee
Person has multiple active home addresses at the same time
Temporary SIN is expiring in N days

The new parameter Number of Days to Validate Temporary SIN is used to allow the user to enter the number of days value. The report will validate X number of days from the effective date parameter entered. If the temporary SIN expires within the days specified, a message is reported.

This feature offers enhanced data validation on HR and payroll data that is required, which helps identify data issues before payroll processing occurs.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Refer to these documents on the Canada Information Center for additional information.

Canada Information Center: https://support.oracle.com/rs?type=doc&id=2102586.2

CA – Payroll tab > Product Documentation > Payroll Guides > Administering Payroll for Canada
CA – Payroll tab > Product Documentation > Payroll Guides > Administering Canada End-of-Year Processing

Hot Topics Email (To Receive Critical Statutory Legislative Product News)

https://support.oracle.com/rs?type=doc&id=2102586.2

Welcome tab > Other Documents > How To Use My Oracle Support Hot Topics Email Subscription Feature

Payroll for Mexico

Work Risk Incident Premium Validation Feature is from a customer submitted idea.

The Work Risk Incident Premium (WRIP) that may be set up in the Organization Card at the payroll statutory unit (PSU) or tax reporting unit (TRU) level, is now validated to ensure that it's between the Work Risk Incident Premium Low Value and Work Risk Incident Premium High Value. A message is displayed if the WRIP is not within the allowed range.

Organization Card - Employer Social Security component

Ensures the accurate calculation of social security.

Steps to Enable

You don't need to do anything to enable this feature.

Support for Dynamic Payroll Relationship Groups Feature is from a customer submitted idea.

You can use the Payroll Relationship Group parameter to run the Mexico processes for dynamic groups of employees, rather than just a static group. The dynamic payroll relationship group option is supported by configuring a formula that will dynamically build the list of employees, based on a defined criteria.

For example, you may configure a formula to create a group of terminated employees, union employees, or employees that are on vacation. You then attach those employees to a payroll relationship group. This feature is available for the following Mexico processes that have the Payroll Relationship Group parameter:

Calculate Mexico Profit Sharing
Run Mexico Annual Tax Adjustment
Run CFDI Payslip Interface
Social Security Archiver
SUA Interface Extract
Social Security Affiliation Report

You can limit the scope of the process to only select the individuals based on a defined criteria rather than having to define and maintain a static list.

Steps to Enable

To enable and use this feature, you will need to:

Optionally create a value set.
Create a payroll relationship group formula type formula.
Create a dynamic object group.

Key Resources

For additional information on creating dynamic object groups, refer to the Administering Global Payroll guide on the Oracle Help Center.
For additional information on creating Payroll Relationship Group Formula Type fast formulas, refer to the Administering Fast Formulas guide on the Oracle Help Center.

INFONAVIT Involuntary Deduction Enhancement Feature is from a customer submitted idea.

You can now create Instituto del Fondo Nacional de la Vivienda para los Trabajadores (INFONAVIT) loans using the element template for involuntary deductions.

Create the elements with the primary classification involuntary deductions.
Select the secondary element classifications of INFONAVIT Loan and INFONAVIT Loan Insurance.

Create the elements

Use the involuntary deductions calculation card to enter the relevant calculation information for loans and the associated loan insurance for employees that have an INFONAVIT loan.

INFONAVIT Loan - Involuntary Deduction Card

This enhancement changes the way in which you manage an employee's INFONAVIT loan.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information about involuntary deductions, refer to the How You Add Involuntary Deductions to a Calculation Card Help Center topic.

Payroll for Oman

Payroll for Oracle Human Capital Management for Oman supports country specific features and functions for Oman. It enables users to follow Oman's business practices and comply with its statutory requirements.

Social Insurance for GCC Citizens

Calculate social insurance contributions accurately with the delivered legislative rules and information for citizens of the GCC countries. You must provide the following information in order to calculate Social Insurance.

Type of employer
Country of employment
Nationality (Country of Citizenship)
Confirmation that the person is registered for Social Insurance in the Country of Employment
Whether or not it has been agreed that the country of citizenship will pay any difference in contributions
Contributory salary
Any additional personal details based on localization

With this enhancement, the following legislative information and rules are available to be used for calculating social insurance for your employees.

Minimum and maximum ages at which contributions should be deducted
Minimum and maximum earnings levels
Rules for proration on starters and leavers
Employer’s rates
Employee’s rates

Age Range: Citizens of all GCC countries should register with the appropriate authority for Social Insurance within the respective age ranges.

Legislation	Sector	Minimum Age	Retirement Age
OM	Government	18	60
OM	Private	15	59
BH	Govt/Private	18	60
AE	Govt/Private	18	59
KW	Govt/Private	18	65
QA	Govt/Private	18	60
SA	Government	17	59
SA	Private	0	60

Earnings Limit: The minimum and maximum earnings limits are stored in the Elements, Calculation Units and Rates part of the CIR as calculation vale definitions. The table below indicates the minimum and maximum earnings for the GCC legislation.

Legislation	Sector	Minimum Earnings	Maximum Earnings
OM	Government	0	3,000 OMR
OM	Private	180 OMR	3,000 OMR
BH	Government	327 BHD	NA
BH	Private	0	4,000 BHD
BH	Government Social Allowances	NA	150 BHD
AE	Government	NA	300,000 AED
AE	Private	1,000 AED	50,000 AED
KW	Government (working outside KW)	230 KWD	2,750 KWD
KW	Private	230 KWD	2,750 KWD
QA	Government/Private	NA	NA
SA	Government	NA	NA
SA	Private	1,500 SAR	45,000 SAR

Employee Rates:

Legislation	Government Sector Rate %	Private Sector Rate %
OM	7	7
BH	6	6
AE	5	5
KW	7.5	7.5
QA	5	5
SA	9	9

Employer Rates:

Legislation	Government Sector Rate %	Private Sector Rate %
OM	17.7	10.5 + 1 Hazard
BH	15	9
AE	15	15
KW	11	11
QA	10	10
SA	9	9

Contributory Salary (Private Sector): You can specify a contributory salary to be used in the calculation of Social Insurance. Use the balance Employee Private Sector Contributory Salary Base to provide a value for the contributory salary, or you can define a formula subject to rules on citizenship. For employer contributions, use the balance Employer Contributory Salary.

Contributory Salary (Government Sector): Use the balance Employee Government Sector Contributory Salary Base to provide a value for the contributory salary. For employer contributions, use the balance Employer Contributory Salary.The contributory salary for GCC citizens working in the government sector varies each period. For a Bahrain citizen the total of social allowances should not exceed 150 BHD.

The Contributory Salary balance is the basis for the calculation of employee's social insurance, any salary adjustment should be taken into consideration in this balance

Social Insurance Calculation (Private and Government Sector)

Citizenship	Employee Contributory Salary (Private Sector)	Employee Contributory Salary (Government Sector)
Bahrain	Basic Salary + All Allowances +Annual Bonuses	Basic Salary + Social Allowance
Kuwait	Basic Salary + All Allowances	Basic Salary + All Allowances
Qatar	Basic Salary + Social Allowance	Basic Salary + Social Allowance
Saudi Arabia	Basic Salary + Housing Allowance	Basic Salary
UAE	Basic Salary + All Allowances	Basic Salary + Social Allowance + Housing Allowance + Children Allowance + Cost of Living

Calculate social insurance contributions accurately with the delivered legislative rules and information for citizens of the GCC countries.

Steps to Enable

You don't need to do anything to enable this feature.

Gratuity

With this enhancement, you can estimate the calculation of gratuity, to aid in costing the amount that may be due for eligible employees on termination. You can also pay the actual amount of gratuity due when the employee leaves employment.

A gratuity calculation won't be processed for employees registered for social insurance.

Organization Calculation Card: You can choose to provide a gratuity or pension benefits program and define a Gratuity Formula to calculate the gratuity payment. Select 'True' on the check box for Gratuity to be Paid to activate either gratuity process. Attach the monthly salary calculation formula to the calculation card at the PSU level, to be used as the salary base for the gratuity calculation.

Person Calculation Card: You can set Override Amounts to override the gratuity amount calculated by a delivered formula. Use the component detail 'Oman Employee Gratuity Details' to specify the Override Amount. The Latest Gratuity Payment Date is auto-populated when the gratuity payment on termination is made. This card is created automatically as part of the termination process if your product usage is set to Payroll or Payroll Interface.

Elements and Balances: You can verify the delivered elements and balances for gratuity, so the gratuity calculation is correct for the Legislative Data Group (LDG).

Calculation Value Definitions: Use the delivered calculation value definitions from the value definition group Gratuity, with a calculation type of Flat Amount.

Automatic Gratuity Calculation Card Creation: The application automatically creates a gratuity calculation card when an employee is terminated and isn't registered for Social Insurance.

Monthly Gratuity Estimate: Add the element Employee Gratuity Accrual Initiator to the employees to initiate the accrual process and trigger the calculation of an estimated gratuity payment. You may need to initialize the gratuity accrual balance to ensure that the first period of gratuity accrual is calculated correctly.

Private Sector Gratuity Payment Calculation:

If the employee has more than 12 months of service then gratuity is calculated based on 15 days per year up to 3 years of service.
If the employee has more than 3 years service, for the first 3 years service, gratuity accrual is based on 15 days per year, plus 30 days per year, or part year, for the remaining service.

Government Sector Gratuity Payment Calculation (Hire Date After 8 March 2011):

If the employee has more than 60 months service, then gratuity is calculated based on 30 days per year.

Government Sector Gratuity Payment Calculation (Hire Date On or Before 8 March 2011):

If the employee has more than 24 months service, then gratuity is calculated based on 30 days per year.

The actual gratuity will be calculated and paid on the termination of an employee when the Employee Gratuity Details calculation card is present.

Calculate and estimate the calculation of gratuity for eligible employees.

Steps to Enable

You don't need to do anything to enable this feature.

Payroll for the United Kingdom

P60 End of Year Statement for Tax Year 2022-23

You can use the updated templates provided for the tax year 2022-2023 to generate and issue P60 End of Year Statement to your employees.

eP60 - Online
Plain Paper
Type LE(P)

You can stay compliant with updates provided for the P60 forms for the tax year 2022-2023.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information, see the topic End of Year P60 Process for the UK in the Administering Payroll for the United Kingdom guide on the Oracle Help Center.

Benefits in Kind Proration on Mid-Period End or Termination

You can prorate the car, van, and other benefits appropriately using the new attributes introduced for availability dates when your employee terminates part way through a tax period.

There are two date fields available on the Car and Car Fuel component:

Available from Date
Available to Date

These dates will record the actual period of the car benefit when the car was actually available to the employee.

The car availability from date should be updated every time you create a car component.

The car availability to date must be entered when there is a change in the benefit, for example, change of car or in case of a termination.

You can leave the benefit component open ended and enter the new available from and to dates. The application processes the component in payroll, and calculates the taxable amount as a prorated value based on the actual period the benefit was provided to the employee.

You can use this feature to effectively prorate the value of the taxable benefit correctly when there is a change in the car benefit, or when there is an employee termination mid-period.

Steps to Enable

You don't need to do anything to enable this feature.

Court Order Processing Fee Override

You can use the new field Processing Fee Override Amount if a particular court order type fee is not required, or a different value to that of the default amount is required.

This also includes the ability to override to zero. If no value is entered, the application considers the current default override fee or the override fee specified at the organization level for that court order type.

You can use the enhanced court order feature to override the processing fee for an individual employee court order calculation at the component level in the Court Order and Student Loan calculation card.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information, see the Define Court Order Adjustments and Overrides for the UK topic in the Administering Payroll for the United Kingdom on Oracle Help Center.

P45 Flow - Errors and Warnings Report

You can utilize the errors and warnings report when running the P45 flow, that lists all the anomalies found during the process. This implies that the process will stop and you need to review and fix the errors.

Here's the data for employer, organization, and employees that were previously marked as warnings are now shown as errors:

Employer Name
Employer PAYE Reference
Tax Reporting Unit Name
First Name
Last Name
Gender
Date of Birth
Person Number
Date of Leaving
Payroll Statutory Unit Name

You can use the Run Errors and Warnings Report task in the P45 process to review and fix issues.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information, see the P45 Process in the Administering Payroll for the United Kingdom on the Oracle Help Center.

P11D Audit Report Includes Person Number

You can identify employees reported on the P11D audit report using the two new fields included in the output. You need to use the Run P11D Archive flow pattern and all the relevant tasks.

The Run P11D Archive task produces the relevant audit reports, but doesn't generate any XML file. Person Identifier and Payroll Relationship Number have been added to the output file generated from the P11D process.

The Generate Online P11D and XML task produces the audit report and the XML file that will be submitted to HMRC. And it displays the persons processed on the Process Results page. Rollback or Mark for Retry options are enabled at both person level and task level.

The P11D Audit Report is enhanced to make the reconciliation process easier to identify employees based on person number and payroll relationship of the employee.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For more information, see the Processing Benefits-in-Kind Through Payroll and P11D Reporting in the Administering Payroll for the United Kingdom on Oracle Help Center.

LGPS – Calculation of Employer Contributions for Absences with Reduced Payment

You can now calculate employer contributions for periods with reductions in pay mid-period, due to absences such as sickness or maternity. This is done by prorating Permanent Pensionable Pay for days with normal pay and prorating Assumed Pensionable Pay for days with reduced or zero pay.

Comply with LGPS requirements to calculate employer contributions correctly for periods with mid-period reduction in pay, due to absences.

Steps to Enable

You need to create a new LGPS main scheme element to enable this feature.

Payroll for the United States

Payroll for Oracle Human Capital Management for the United States supports country specific features and functions for the United States. It enables users to follow the United States business practices and comply with its statutory requirements.

Regional Pay Data Report Enhancement for California

We have augmented California pay data reporting with the addition of the CA Pay Data Reporting Pay Bands calculation value definition. This calculation value definition tracks the pay bands included in the pay data reporting extracts. These bands are editable to accommodate any last minute changes announced by Civil Rights Department (CRD) of the state of California.

This feature makes the report a lot more flexible. It helps you capture and report any new requirements announced by Civil Rights Department (CRD) of the state of California.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Refer to these topics in the Oracle Help Center:

Regional Pay Data Report Enhancement

We have improved the flexibility of the Regional Pay Data Report by making the parameters related to contact information optional rather than mandatory.

This includes these parameters.

Contact Title
Contact Name
Contact Phone Number
Contact Address Line 1
Contact Address Line 2
Contact City
Contact State
Contact Country
Contact Postal Code

Contact information is no longer required on California Pay Data Report extract template; these are now captured as series of questions online.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

For additional info, see the following topic on the Oracle Help Center:

Regional Pay Data Report for the US

IMPORTANT Actions and Considerations for Payroll

REPLACED OR REMOVED FEATURES

From time to time, Oracle replaces existing Cloud service features with new features or removes existing features. When a feature is replaced the older version may be removed immediately or at a future time. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

Product	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Global Payroll	Enhanced Reports Available and Previous Versions Are No Longer Supported	23D	Run Payroll Activity Report for the Latest Process Run Payroll Statutory Deduction Register for the Latest Process Run Payroll Register Report for the Latest Process Run Periodic Payroll Activity Report Run Periodic Statutory Deduction Register Run Periodic Payroll Register Report Run Payroll Costing Report	Exists prior to 22D

_________________________

KNOWN ISSUES / MAINTENANCE PACK SPREADSHEETS

Oracle publishes a Known Issues document for every Update to make customers are aware of potential problems they could run into and the document provides workarounds if they are available.

Oracle also publishes Maintenance Pack and Statutory Maintenance Pack documentation of bugs that are fixed in the monthly or statutory patching.

To review these documents you must have access to My Oracle Support:

Oracle Human Capital Management Cloud Functional Known Issues and Maintenance Packs (Document ID 1554838.1)