Oracle Cloud Human Resources (UK) :: Statutory Absences
Oracle Cloud Human Resources (UK) :: Statutory Absences
Oracle Cloud Human Resources (UK) :: Statutory Absences
Human
Resources (UK):
Statutory Absences
Implementation and Functional Considerations
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that
is the exclusive property of Oracle. Your access to and use of this confidential material is
subject to the terms and conditions of your Oracle software license and service agreement,
which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to
anyone outside Oracle without prior written consent of Oracle. This document is not part of
your license agreement nor can it be incorporated into any contractual agreement with
Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Purpose Statement................................................................. 3
Introduction ............................................................................ 8
Summary of Setup................................................................ 13
Certifications ..................................................................................................41
Appendix .............................................................................. 46
Oracle Fusion HCM for the UK enables you to calculate statutory absences as prescribed by the
UK legislation. This document covers the setup and implementation of the UK Statutory Absences.
This guide assumes that the reader is familiar with the Oracle Fusion Absence Management
product.
Entitlements to statutory payments are calculated and processed using predefined fast formulas.
The absences management process uses the certification feature to stop absence payments. You
can generate certifications manually or as mandated as a result of processing the absence. If a
certification needs to be overridden, this can be done by voiding the certification.
You use Global Absence Management to record the employee absences. Absence records
should be recorded with the start and end date corresponding to the person’s actual absence
incapacity to work (period of sickness), there should be no gaps in the absence record. Absences
should not be recorded by individual absence records for each day’s incapacity to work absence.
If records are created with gaps, the application may incorrectly calculate any entitlement or
payment for an absence.
For example, to record a persons’ absence (incapacity to work) for 1st to 7th June 2017, enter one record with
the start date 1st June 2017 and end date 7th June 2017.
You cannot record the absence (incapacity to work) as individual records, that is, separately for the 1st, 2nd,
3rd, 4th, 5th, 6th, and 7th June.
Recording a persons' absence (incapacity to work) for 1st to 7th June 2017 by entering a record for each day
will cause the system to incorrectly calculate the entitlements and payments.
If the absence (incapacity to work) is created as two separate records, 1st - 4th and 5th – 7th June, then the
absence will be incorrectly processed as the second record would not form a period of incapacity to work. The
absences would not be linked and hence the second absence record would not be payable.
Ensure that you set up the required components in the following order:
1. Create the rate definitions.
2. Create the required elements to be associated with the statutory absence plans.
3. Create the statutory absence plans.
4. Create the absence types, including assigning the appropriate certifications to the absence
type.
Note: Absence plans and types vary depending on the type of absence being set up.
You can attach multiple absence types to a single absence plan but the absence types must have
the same unit of measure. If the unit of measure is not the same for each type attached to a
single plan then the absence calculation may fail or produce an inaccurate information for the
absence.
If you have multiple types with different units of measure then you will need to use a separate plan for each
type.
There are certain Statutory Absences (Statutory Maternity Pay/Statutory Adoption Pay/Statutory Paternity Pay)
that are still payable after the person’s employment has been terminated, if the employee meets the eligibility
criteria. The details to enable this functionality are described in the relevant sections of this document.
If you have already set up the absences as not payable after termination, you must perform the following tasks:
1. Create a new element following the instructions in Payroll Elements.
2. Create a new plan using the instructions for the relevant absence, and attach the element created in step
1. Ensure that you set the Entitlement End Rule to be After Termination.
3. Create a new absence type using the instructions for the relevant absence type, and attach it to the plan
created in step 2.
4. New absence entries, made after the new setup, should be made using the new absence type.
5. For existing absences entered before the new setup that need to be paid after termination, you must
withdraw the old absence and reenter the absence using the new absence type.
Ensure that the effective date is set to the date from which you wish to start using the functionality.
It is not mandatory to implement this new functionality and you can continue to keep existing absences and
calculate the payable amounts after termination manually.
To ensure that the eligibility and payment of a UK statutory absence is correct the Average Weekly Earnings
(AWE) need to be ascertained for the employee. This is calculated using rules set out by HMRC, and includes
a certain period of time called the Relevant Period.
If payroll information is not available for the relevant period then the AWE calculation may not be able to be
performed or for certain absences may be calculated in an alternative way. If the calculation cannot be
performed this may imply that the employee does not have the requisite service and may not be eligible for the
absence. To perform the calculation accurately you must have all the payroll data for the relevant period
To be able to use the hook you will need to create a Fast Formula called
UK_ABSENCES_AWE_OVERRIDE_FORMULA and in it have the following text:
OP_AWE_OVERRIDE= <Value>
RETURN OP_AWE_OVERRIDE
The variable <value> can be either hard coded or reference another source of information, this is up to you.
You only need to create this once and it will be used by all statutory absences.
The hook can only be used in certain circumstances and this can be ascertained using the flow diagrams
contained in Appendix 2 (HR only and Payroll Interface) and Appendix 3 (Payroll).
To recalculate the AWE when a person has received a backdated pay rise, do the following.
» Statutory Paternity Pay – Manually recalculate the AWE value and enter it in the Override Average Weekly
Earnings field on the absence record. You can then re-evaluate the absence manually.
If the absence was not payable earlier, but is now payable, it will push new records to payroll that can
be processed.
» Shared Parental Leave – Manually recalculate the AWE value and enter it in the Override Average Weekly
Earnings field on the absence record. You can then re-evaluate the absence manually.
If any agreement associated with the absence has been authorized, it may need to be withdrawn to
alter the eligibility.
» SAP - Manually recalculate the AWE value and enter it in the Override Average Weekly Earnings field on
the absence record. You can then re-evaluate the absence manually.
If the absence was not payable earlier, but is now payable, it will push new records to payroll that can
be processed.
For the next period, the overridden AWE is used. If a retroactive run is triggered by any event causing
the previous payroll period to be recalculated, then the retro run should use the overridden value and
re-compute the absence that has already been processed and paid in the previous period.
» SMP – For more information see the Support for Alabaster ruling further on in this document.
Effective Dates
When creating new components, ensure that you set an effective start date, which covers the time scale of the
absences you wish to enter, including any absence history that you may need to migrate.
Note: The effective start date of the elements cannot be earlier than the 1st April 2012 for Statutory Sick Pay,
Maternity Pay, Adoption Pay and Paternity Pay and the 6th April 2015 for Shared Parental Leave Pay.
It should also be ensured that any employee’s schedules are effective from at least the start date of any
absences you wish to record.
Seniority Date
The Statutory Absence Service Start Date field is used to record the date (different to the hire date) that can be
used for calculating the period of service for entitlement and payment of UK statutory absences. The field is
located on the employees work relationship record.
If this field is populated any Statutory Absences for the person will have the length of service eligibility
calculated using the date that has been entered. If the field is not populated then the hire date from the
employees’ employment record will be used to calculate length of service eligibility.
Multiple Assignments
Oracle UK Statutory Absences solution does not currently support the payment processing for absences on
multiple assignments, therefore absence payments for multiple assignments will need to be done by the
customer.
If the system does detect an absence that is associated with multiple assignments a certification will be
produced setting the payment value to zero. A user may void the certification, but they would then need to
ensure that the payments and processing for the absences are correct.
If you choose to use the core reason functionality with absence type you should ensure that the linkage reason
is set to ‘No’ on the absence reasons tab of the absence type. Failure to do this could cause incorrect
processing of UK statutory absences.
Ensure that any absence types you create have the appropriate absence record maintenance values
populated, so that employees, managers and administrators can update or maintain absence records
appropriately.
In order for statutory payments to work correctly, you must specify the correct unit of measure for each statutory
plan, as described in subsequent sections of this document. Absence types can be in any unit of measure that
is appropriate for your business needs (for example, if your occupational plans are in hours, you will need to
setup the absence type in hours to ensure that you capture absences correctly). This may result in a mismatch
between the unit of measure on the type and statutory plan. In such cases, specify a conversion formula at the
plan level.
SUMMARY OF SETUP
The table below summarizes the items that you must create to fully implement the absences feature:
Maternity Leave One plan for Statutory Maternity Pay One element for Statutory Placeholder Rate
One or more plans for Occupational Maternity Definition
Maternity Pay schemes One element per occupational Average Weekly Earnings
plan for “Birth” Rate Definition
Adoption Leave One plan for Statutory Adoption Pay One element for Statutory Same Placeholder Rate
One or more plans for Occupational Adoption Definition
Adoption Pay schemes One element per occupational Average Weekly Earnings
plans for “Adoption” Rate
Definition
Paternity Leave – Birth One plan for Statutory Paternity Pay One element for Statutory Same Placeholder Rate
Birth Paternity Pay Birth Definition
One or more plans for Occupational One element per occupational Same Average Weekly
Paternity Pay schemes plans Earnings for “Birth” Rate
Definition
Paternity Leave – One plan for Statutory Paternity Pay One element for Statutory Same Placeholder Rate
Adoption Adoption Paternity Pay Adoption Definition
Same Occupation Paternity Pay Same elements as above Same Average Weekly
schemes as above Earnings for “Adoption”
Rate Definition
Sickness Leave One plan for Statutory Sick Pay One element for Statutory Sick Same Placeholder Rate
One or more plans for Occupational Sick Pay Definition
Pay One element per occupational
plans
Shared Parental Leave - One plan for Shared Parental Leave One element for Shared Same Placeholder Rate
Birth Birth Parental Leave Birth Definition
One or more plans for Occupational One or more plans for Same Average Weekly
Shared Parental Leave Pay Occupational Shared Parental Earnings for “Birth” Rate
Leave Pay Definition
Shared Parental Leave – One plan for Shared Parental Leave One element for Shared Same Placeholder Rate
Adoption Adoption Parental Leave Adoption Definition
Same plans as above Same elements as above
Sickness During One plan for Sickness During Maternity One element for Sickness Same Placeholder Rate
Maternity Pay Period Pay Period During Maternity pay Period. Definition
Note: Use Maternity, Paternity,
Shared Parental Leave or
Adoption as secondary
classification.
One element per occupational
plans
Shared Parental Leave Statutory Maternity Pay Shared Parental Leave - Birth Shared Parental Leave
for Mother Birth
Shared Parental Leave Statutory Adoption Pay Shared Parental Leave – Shared Parental Leave
for Adopter Adoption Adoption
Shared Parental Leave N/A Shared Parental Leave - Birth Shared Parental Leave
for Mother’s Partner Birth
Shared Parental Leave N/A Shared Parental Leave – Shared Parental Leave
for Adopter’s Partner Adoption Adoption
RATE DEFINITIONS
If salary basis is being used, you don’t need to create a dummy rate and you don’t need to follow the
instructions in this section. If salary basis is not being used, only then the dummy rate should be created such
that it returns a non-zero value. You can do this by following the instructions in this section.
To enable the payment of the absence in payroll, you must define rate definitions. When creating an absence
plan, you specify the payment rate that is applicable to this plan. This payment rate can either be derived by a
formula or based on a rate definition.
A placeholder rate must be associated with the absence plan as well as the element, to trigger the calculation
of the statutory rate. Use a single rate for all the statutory absence plans.
In addition, you may also need to create one or more rates to calculate the deduction from salary. This is
optional and depends on your policy regarding payment and deduction for absence:
» If you reduce the regular earnings by the absence payment then the rate definition is not required.
» If the deduction rate is based on various salary elements, a rate definition is required.
You must create elements to enable the payroll application to process absences, which have been transferred
from the Global Absence Management.
The absence element creation template has been extended to include the following:
» Automatic generation of required elements, including recovery and NIC compensation elements, where
required.
» Automatic balance feeds for PAYE, NI, and other deductions as well as balance feeds required for RTI
reporting.
» Creation of retroactive elements.
» Enable payment of absence after termination.
To create eligibility:
2. Click Actions.
If you selected the option to reduce the regular earnings by absence payment, the priority of element can be left
unchanged.
Perform the following steps using the Manage Elements task to edit these elements:
1. Search for the element
2. Open each of the absence elements created earlier.
3. Click Edit, then Correct.
4. In the Priority field, enter the Priority number 2600
5. Click Submit.
Depending on your business practices, you may need to create additional balance feeds such as Pensionable
Earnings.
The recovery amount and NIC Compensation also feed the appropriate statutory balances; this ensures that
they are reported automatically on the Full Payment Submission and Employer Payment Summary.
1. In the Payroll Calculation work area, select Manage Calculation Value Definition:
2. Search for Value Definitions prefixed by the name of the element created above:
3. Select <Base Element Name>_MAT_56DAY_VD.
4. Select Correct from the Edit menu.
5. Click Add under calculation values.
6. Create a row and select the Rate Definition Childbirth absence 56 day:
7. Click Submit.
Repeat the steps for all elements that you’ve created such as Maternity, Paternity Leave - Birth, Shared
Parental Leave - Birth.
Similarly, repeat the steps for Adoption, Paternity Leave - Adoption, Shared Parental Leave - Adoption. Ensure
that you link the relevant Rate Definition. In Step 3, select Normal absence 56 day:
Managing Offsets
By default, all the absence elements are processed and paid:
• If both statutory payment elements and occupational payment elements are setup as absence
elements, they will both be paid out to the employee.
• If your policy is to pay statutory only when occupational is exhausted, or offset statutory from
occupational, you must create Information elements, and modify the absence element processing
rules to output the results to the Information element.
To offset occupational absence payments against statutory absence payments, set the occupational absence
elements to a higher priority than the statutory absence elements. The default priority for the occupational
payment elements is 1750. It is recommended you increase this by 10.
For further information, refer to Solution to Offset Statutory Absence Payments from Occupational Absence
Payments (Doc ID 2258204.1) on My Oracle Support.
There are different rates of recovery and compensation; the rate you are entitled to is based on the size of the
company. There are two rates: Full (103%) and Partial (92%). By default, if the recovery type is left blank, no
recovery or compensation is calculated.
The Alabaster ruling specifies that any pay rise awarded between the beginning of the period covered by the
relevant period and the end of the maternity leave must be included in the elements of pay taken into account in
calculating the amount of Statutory Maternity Pay. This requirement is not limited to cases where the pay rise is
backdated to the period covered by the relevant period.
The pay rise will affect the amount paid to the employee during the first 6 weeks of Statutory Maternity Pay,
known as the enhanced pay period. This would mean that the person would be entitled to extra money. It
could also be the case that a person may have not qualified for Statutory Maternity Pay but now does due to
the increased pay.
Setup
To be able to use the elements you need to ensure that the Alabaster elements have an eligibility criteria
created for them.
Instructions on how to do this can be found in the Creating Element Eligibility section <insert link>.
» If the pay rise takes effect before or during the relevant period, you must use the Alabaster Adjustment
element and enter the amount that the person has been under paid. The element should have a start date
and end date matching the maternity absence.
It is the user’s responsibility to adjust the prorated amount to increase the AWE. The prorated (weekly
amount) amount to be uplifted should be set using Alabaster Adjustment element and be entering the value
in Amount field.
» If the pay rise takes effect after the relevant period then you will need to use the Alabaster Adjustment
element and you can either put in the amount of money (weekly amount) which the person has been under
paid or enter a percentage amount which the person has received as a pay rise. The element should have a
start date and end date matching the maternity absence.
Note: Do not enter both a value and a percentage.
1. In the Payroll Calculation work area search for the employee and then select Elements from the Earnings
and Deductions section .
2. In the elements entry screen select the add element icon. Set the effective date to the date on which you
wish the element to start, select the Alabaster Adjustment element from the drop down list. Press the
continue icon.
3. In the entry details screen in the Entry Values section enter the amount or the percentage as appropriate
and press the submit key.
4. You will be returned to the elements entry screen. Set the Effective date to be the end date of the relevant
period and select the entry Alabaster Adjustment. This will take you into the entry details screen. Select
the edit drop down menu and select end date and press the continue button.
5. You will now be taken back to the element entry screen and you will be able to see that the Alabaster
Adjustment element has an effective start and end date. These dates will depend on when the payrise
took effect and is described in the previous paragraph.
The Alabaster Adjustment element will now be included in the appropriate payroll runs and the employee will
receive the payments after appropriate payroll processing.
Statutory Maternity Pay (SMP) and Leave may be payable to an employee who meet the eligibility rules and
receives pay for this absence.
Field Value
Element Select the element which you created earlier for the plan.
Certificate name
Curtailment Notice
Death of Parent
KIT Days
Incorrect Notice
An employee may be entitled to Statutory Maternity Pay if they fall ill whilst still in the Statutory Maternity Pay
Period. They would not be entitled to Statutory Sick Pay. If a person has returned to work (ended their Statutory
Maternity Pay/Leave) from Statutory Maternity Pay/Leave and falls ill within the Maternity Pay Period then the
person will be entitled to Statutory Maternity Pay for each full week of sickness providing they meet the relevant
criteria, part weeks of sickness will not be paid and the normal Statutory Sickness payment rules do not apply.
If the person is not entitled to Statutory Maternity Pay then the absence will be recorded as non-payable. If the
absence is payable the rate at which the person is paid would be in line with the Statutory Maternity Pay rates.
If there is any part of the enhanced (90% of average weekly earnings) pay for the first six weeks unused, then
this will be paid until it has been used up, and any of the unused remaining 33 weeks at the statutory rate.
The Statutory Maternity Pay will be paid in weeks and continue to be paid in the rolling week cycle which was
started with the original Statutory maternity pay period.
For example, if the Statutory Maternity Pay period started on a Tuesday then the rolling week for payments
would be Tuesday to Monday. If a person feel ill on Thursday then they would not be entitled to payment until
they had completed a full week starting on the following Tuesday.
The maternity pay period is not reset, and ends at the original date set by the original maternity absence.
When the sickness absence passes out of the maternity pay period normal statutory sick pay rules will apply.
The absence will be non-payable if it is linked to the sickness absence during the maternity period which was
non-payable under Statutory Sick Pay. For the person to be entitled to Statutory Sick Pay after the maternity
pay period there must be a break of 56 days between the new sickness absence and any sickness absence
recorded in the maternity pay period.
Element Select the element which you created earlier for the plan.
An employee may be entitled to Statutory Adoption Pay (SAP) and Leave as long as they meet the criteria set
by the legislation. The rate at which it is paid is also set by the legislation.
6. In the Display Features tab, ensure that the Matching Date field is enabled in the Dates and Duration
section and Open ended is set to Do Not Display.
Certificate name
Incorrect Notice
Curtailment Notice
Death of Child
Death of Parent
KIT Days
An employee is entitled to Statutory Paternity Leave and Pay (SPP) if they meet the eligibility criteria set by the
legislation. The rate of pay which the employee receives is also set by the legislation.
Certificate name
Incorrect Notice
To ensure that the calculation is performed accurately the following predefined Fast Formula are used:
» UK Statutory Sick Pay Minimum Duration for Linking (ORA_HRX_GB_ABS_SSP_4DAYS_RULE) – The
formula checks if the absence is long enough to be linked to any other absences. Absences of less than 4
days cannot be linked to other absences as they are not long enough to form a period of incapacity to work.
» UK Statutory Sick Pay Entitlement (ORA_HRX_GB_ABS_SSP_ENTITLEMENT) – This formula performs the
following:
» Ensure that a Period of Incapacity to work is formed
» Identify the waiting days
» End payment after 28 weeks of paying statutory sick pay
» Check whether the chain of linked absences is longer than 3 years.
» Identify whether the employee has a Job Centre linking letter
» Check that the person has earned enough to meet or exceed the Lower Earnings Limit.
If payment needs to be stopped then the system will create the appropriate certification.
» UK Sickness Absence Validation (ORA_HRX_GB_ABS_SSP_VALIDATION) – This formula checks if the
absence is pregnancy related, and generates a warning message for Statutory Maternity Leave or Pay, if the
sick leave falls within 4 weeks of the due date of birth.
Overnight Shifts
When an employee is scheduled to work overnight (for example, shift starting at 10pm and ending at 6am), the
day that counts for SSP purposes is the day the shift starts. This functionality is supported in the Cloud: the
predefined entitlement formula looks at the start and end of the shift to determine which day qualifies for SSP,
based on when the shift started.
Note: The only pre-requisite is that the employee’s work schedule must be defined as Time and the absence
type unit of measure cannot be Calendar Days.
Example: An employee works overnight shifts, the shift pattern is from 10pm until 6AM the next morning, the
pattern starts on Monday and there last shift ends on the following Saturday at 6am. The employee has a
sickness absence starting on the Monday and ending on the Friday (they return to work for the Friday shift
starting at 10pm).
This absence will be processed as being absent from Monday (the beginning of the first shift) to Thursday (the
beginning of the last shift the employee was absent for).
The following figure illustrates how the duration of the absence is calculated:
To create a schedule that can be used for SSP calculations, set up a work schedule category and ensure that
the code value is SSP. You can specify a meaningful name.
1. In the Setup and Maintenance work area, search for Manage Standard Lookups task:
2. Click on Manage Standard Lookups and then search for the lookup type: ZMM%SCHE%.
3. Select the lookup type Schedule Category.
4. Add a child row with the Lookup Code as SSP, Effective date 1/1/10, meaning - UK SSP and description –
UK SSP.
5. Save the information.
You will now be able to create a work schedule and use the category created.
Once you have created the work schedule category, you can create schedules to reflect the SSP schedules
used within your organization. Ensure that the category is SSP (as created above), the effective start date is a
Sunday and the type is the same as the work schedule.
Based on your business requirements, the schedules can then be assigned to different levels of the
organization, this can be achieved by following the steps below:
1. Navigate to the Manage Work Schedule Assignment Administration page. Search for the Work Schedule
for Support schedule. Click the schedule to open it on the Edit Work Schedule Assignment page.
2. In the Resource Assignments region, click Add Row from the Actions menu. Select at what level you wish
to add the resource schedule at and then select the appropriate name. Ensure that the Primary field is left
blank and press submit.
Note: You can create as many SSP schedules as required by your organization, as long as they all have
the SSP category.
Field Value
Status Active
Linkage Period 56
» To record absence reasons, make sure the field is set to Display and Edit. You must define the reasons
in the Manage Reasons page.
» Ensure that the ‘Deferred processing on initial entry’ is not enabled. This allows the processing of
entitlement to be done on absence entry. If you choose to defer the processing, you can process
absences in batch by running the Evaluate Absences process.
» Ensure that ‘Deferred processing on subsequent absences’ is enabled. When changing an existing
absence record, it may have an impact on future-dated absences. Those future-dated absences must
be re-processed by Submitting the Evaluate Absences process.
Note: A new display feature has been added to allow scheduling of absences on non-working days. If
the unit of measure on the type is either Hours or Days, and you want to allow recording of absences on
non-working days, make sure that this new display feature ‘Schedule nonworking days’ is set to
Enabled. Any other unit of measure allows for that by default, and therefore the displayed feature can
be left unchanged.
Certificate name
Entitled to SMP
Linking letter
On strike
Waiting days
An employee may curtail their maternity or adoption leave in favor of sharing it with their partner. The shared
parental leave may be paid or unpaid. The amount of leave which can be taken as paid or unpaid will depend
on how much leave the person curtailing the maternity or adoption leave has left.
As well as using an absence plan and absence type, this functionality also uses the Leave Agreements. You
must create leave agreement templates to cater for different cases of shared parental leave. The details about
leave agreement functionality and how to create a template are described in the Leave Agreements section.
Field Value
Status Active
5. In the Entitlements tab, Click Add to add two bands, Band1Pay and Band2Pay. For Band1Pay set to 100
payment percentage, for Band2Pay set 0 payment Percentage.
6. In the Entries and Balances tab, select the check box Transfer absence payment information for payroll
processing. Enter the field values as shown below:
Field Value
Element Select the element which you created earlier for the plan.
Note: each plan should be linked to a separate element
Field Value
Status Active
8. In the Display Features tab, enter the field values as shown below:
Usage Value
9. Click Save.
Leave Agreements
The Shared Parental Leave functionality is governed by a leave agreement. This requires the user to set up a
leave agreement template that specifies:
» The source plan (where the entitlement is converted from a maternity or adoption leave)
» The target plan (the plan associated to the Shared Parental Leave agreement).
Leave agreements functionality controls the amount of leave which is used when a person consumes the
Shared Parental Leave. The mother or adopter must curtail their maternity or adoption leave or pay in order to
allow a partner to consume their Shared Parental Leave.
The Leave agreement functionality converts the remaining leave from a maternity or adoption plan, if the plan is
with the same employer. You can also manually enter leave values which can be used for Shared Parental
Leave. The Shared Parental Leave consists of payable and nonpayable leave and the amount of leave being
entered by a person is validated against the amounts in the leave agreement.
Field Value
Status Active
Formula ORA_HRX_GB_SHPL_AGREEMENT_VALIDATION
Source Absence Type Select the relevant absence type created for Statutory
Maternity leave.
Certifications
In order to manage other types of documentation on the employee’s leave agreement (such as Curtailment
Notice, Declaration of entitlement and Intention to take leave, Period of Leave notices), you must create
certifications and associate them with leave agreement template, where applicable.
To create Certifications:
1. In the Absence Administration work area, select Absence Certifications:
2. Click Create.
Field Value
Classification Documentation
Name As appropriate
Status Active
Trigger On demand
Note: None of the other sections are relevant to Documentation certification; default values can be
applied.
Once created, the certifications can be linked to the relevant leave agreement templates.
Once the setup is completed, you can create absence records for a person. The absence is processed by the
Absence Management application.
Linking Letter
At the start of their employment, an employee could present a linking letter, which indicates that the employee
has been receiving allowances directly from the Job Centre. This impacts their entitlement to SSP. The
employer does not have to pay SSP for sickness absences within 12 weeks of the date specified on the letter.
After 12 weeks, the employer is obliged to pay the SSP again.
.You can create a document record for linking letters. Use the predefined document type Job Centre Linking
Letter to do this.
Ensure that the From Date is the date indicated on the linking letter and end date corresponds to the end of the
12 week period during which the employee is not entitled to SSP. For any sickness record starting within that
period, a certificate is automatically generated to indicate that SSP is not payable for this absence.
If an employee exceeds the number of KIT days permitted, the week during which additional KIT days are
used, become ineligible for statutory payment. You can create a manual certification to stop the payment
for that week.
The absence start and end dates are also validated: they must falls within the agreement term dates.
If an employee exceeds the number of SPLIT days permitted, the week during which additional SPLIT days are
used, become ineligible for statutory payment. You can make that week nonpayable by creating a separate
absence record for that week and selecting the payment detail as Unpaid.
To enable statutory absence calculations in conjunction with your current implementation, perform the
following steps:
1. Identify the period for which the statutory payment history needs to be created.
• For sickness absences, it is advisable to create at least 6 weeks of history prior to the
Absence Processing Start Date, that is, the date when you want to start processing
absences in Fusion. This is because sickness absences are linked if they fall within 6
weeks of any previous absences. You can create more statutory payments history, if
required.
• For maternity, paternity, adoption, you may evaluate only those absences that are
ongoing as at the Absence Processing Start Date. Hence, at the most it would be 52
weeks prior to the Absence Processing Start Date.
You must create all the setup objects on or prior to that date.
4. Edit the Entitlement result formula to add the Absence Processing Start Date.
To stop calculation cards being processed in payroll for the portion of absence that has already been
paid, set the Absence Processing Start Date to the date you want to start processing absences in
Oracle Global Payroll. No absences will be processed prior to this date.
Note: The Absence Processing Start Date is stored in the payroll formula attached to your absence
element. Copy and edit this formula to enter the Absence Processing Start Date.
l_stop ='Y'
unit = 0
deduction = 0
net_pay = 0
)
f. Click Save.
g. Compile the formula.
h. Repeat for all the Entitlement Result formula.
5. Optionally, if the Qualifying Days for Statutory Sick Pay purposes are based on a work
schedule that is different to the employee work schedule, you must ensure that you setup an
alternate Statutory Sick Pay Schedule.
7. Modify the existing absence types as follows (as at the date identified in step 1)
o For Sickness absence type, add the linking rule (SSP only)
For further information on how to setup the absence type, refer to the following sections:
Note: The process also generates the absence calculation cards. Only those calculations card
with an effective date after the Absence Processing Start Date will be processed in Payroll.
Hence, the date prevents any previously paid absences to be paid again in the Oracle Fusion
application.
It is possible that an absence that needs to be evaluated is linked to one or more previous
absences. In such cases, there are two possibilities:
» You can process all the absence records within the chain.
» Process only the last absence in the chain. In this scenario, additional information is required for that
absence.
Additional data entry is available specifically for data migration, on the Absence Administration page:
Consumed SSP Weeks If the employee has consumed SSP entitlement before the migrated absence
record, then it is specified here. It is used to calculate the 28 weeks limit.
Note: If linked absences are created using HDL, they will only be used if
entered against the first absence in the chain. If you enter a number of
consumed SSP weeks in subsequent migrated absences, this
information will be ignored.
Original Start Date If the sickness has a long history of linked absences which are not migrated,
provide the start date of the first linked absence. It is used to calculate the 3 years
limit and overrides the system determined value.
Note: It can be entered on any linked absences, but the one entered on
the last absence record in the chain is the one that is taken into account.
Disqualified Reason If the employee was not entitled to SSP for the absence being migrated, enter the
certificate name that indicates the reason for disqualification. For example, LEL
not reached or On Strike.
Consumed Waiting Days When you use a single absence for migration then this field describes the number
of waiting days that have already been used by previous absences. The days will
be processed in this migrated absence.
Note: This field will be evaluated only on the first absence if it is part of a
chain of linked absences.
Disable Earnings Check If you select this check box, the application does not check against the lower
earnings limit (LEL) and assumes that the LEL is exceeded.
Use this to bypass the LEL check for periods where payment data is not
available.
For further information on how to use those additional fields, see Setting Up and Migrating UK Statutory
Absences (Doc ID 2234239.1), UK Statutory Absences Migration Document.
8. There is also a possibility that some of the existing absences payments were manually
stopped in your legacy application, that is, by manual intervention from an administrative user.
If the reason for nonpayment cannot be automatically detected by the process, the reason
needs to be indicated in the Disqualifying Reason field. You can do this in mass using the
HCM Data Loader (HDL). The following examples show how you can handle these scenarios:
» An absence record was found ineligible for SSP payment because the employee’s average weekly
earnings did not reached the LEL. Subsequently, the administrative user found that a mistake was
made in the employee’s salary and updated the absence to be paid. In this example, select the check
box Disable Earnings Check.
» An employee was taken into legal custody while on sick leave. For this reason, the absence
payment was stopped. The Disqualified Reason needs to be set to “Taken into Legal
Custody”.
Average Weekly Earnings Override to provide the value for average weekly earnings for maternity, adoption, and
ShPL.
Once the additional data requirement has been identified and entered on the absence record,
you can run the Evaluation Absence process to generate the entitlement to statutory payment
on historical absence records.
a) Select Schedule and Monitor Absence Processes task from the Absence Administration work
area:
b) Run Evaluate Absences process from list.
c) Enter the parameters as required.
» Effective Date: This should be the same date as identified in Step 1. Any absence records
with a start date prior to the effective date will not be processed.
» Run as test: This field should remain unselected as this is not currently supported for the
UK. This is because the SSP calculations rely on the availability of entitlement from
previous absences. If they are not available, the calculations will be incorrect.
» Increment effective date: This field should remain selected.
» Under Population Filters section, you can select various criteria to restrict the population of
employees for whom the process will run.
» Person Selection Rule: To filter based on additional criteria, you can write a Fast Formula
for the type Person Selection.
11. Verify the entitlement results for the processed absences against the results in your legacy
system.
If there are any discrepancies, you can update the data and rerun the process.
Note: If you have other plans attached to your absence types, those plans will also be re-evaluated
by the process. Based on the assumption that there has been no change in the absence records,
there should be no change in entitlement under those plans as a result of running the process.
The Shared Parental Leave is managed by the Leave agreement functionality from Release 12
onwards. Hence, the existing absences cannot be automatically converted. Follow the steps
described in section Shared Parental Pay and Leave (ShPL). Once you set this up, you can use it
for new cases of Shared Parental Leave.
HR Only/Payroll
Interface
Check in the
following order: SPP/SMP/
Yes
AWE in DDF SAP/ShPL
AWE from hook.
DDF or Hook
Yes contains a No
value?
System
AWE Test certification: LEL
No not reached.
succesful
Yes
Stop
Payroll
Document
Certification:
SPP/SAP/ DDF field Alternative AWE
Yes Yes value has been
SMP/ShPL populated?
used.
No
No
Sufficient
information to AWE Test
Yes Yes Stop
calculate the succesful
AWE?
SSP
No No
No System should
produce a LEL System
certification as certification: LEL
This is not a
insufficient not reached.
statutory payment.
information
available to
Skip LEL flex calculate the AWE
segment
populated?
Stop Yes
System
certification: LEL No This is so that the
not reached. User can populate entitlement formula is
DDF fields and triggered.
then void the
No
certificate.
Sufficient
AWE Test information to
Yes
succesful calculate the
AWE?
Void
certification or
No Stop
use DDF
fields?
No
Yes
Stop Yes
Some earnings
No
data?
Document
Certification:
Yes Alternative AWE
value has been
Earnings do used.
not cover 8
weeks
The AWE is calculated by using the period represented Yes Use hook?
by all of the earnings paid under the contract before the
Exact number
first day of sickness. So if the employee only received Yes
of weeks pay
five weeks earnings the AWE is calculated by dividing No
Use AWE value
the total of the 5 weeks earnings by 5.
No
System should
produce a LEL
certification as
insufficient
information
When an employee has not received eight weeks earnings and has not received an
available to
exact number of weeks pay the AWE is calculated by using the period represented by
calculate the AWE
all of the earnings paid under the contract before the first day of sickness. So if the
employee only received 2 weeks and 3 days earnings the average weekly earnings is
calculated by dividing the total of the 2 weeks 3 days (17 days) earnings and multiply
by seven regardless of the number of days a week the employee is expected to work.
System
certification: LEL
not reached.
Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA
Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com
CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0820
White Paper:Oracle Fusion HCM (UK): Statutory Absences Setup Functional and Implementation Considerations
August 2020
Author: Peter May