Multiple Assignments

The UK Statutory Absences solution supports multiple assignments for Statutory Sick Pay, Statutory Maternity Pay, Statutory Adoption Pay, Statutory Paternity Pay and Sickness During Maternity absences.

It does not currently support the payment processing for any other absences on multiple assignments, therefore payments for other absences, which have multiple assignments will need to be done by the customer.

If the application does detect an absence type that is associated with multiple assignments, a certification will be produced setting the payment value to zero. A user can void the certification, but they would then need to ensure that the payments and processing for the absences are correct.

Note: If an assignment has a start date after the start date of the absence record, you will need to end date the current absence record and create a new one on the relevant assignment start date.

Customers wishing to process multiple assignment absences for Statutory Sick Pay and Sickness During Maternity are strongly recommended to enter absences at assignment level.

To enable multi-assignment processing the user must follow the setup steps in this document, existing customers that wish to enable multiassignment processing will also need to follow some of the setup steps in this document. After the move to multiassignment processing has been done customers will not be able to return to previous statutory absence processing. Careful consideration should be done by customers before moving to multiassignment processing.

Customers with Existing Setup

Customers who are already using the Oracle SMP/SDM/SAP/SPP/SSP solution and wish to move to the new processing need only do these:

  • Enable processing for the relevant absence type (Enabling processing for SMP automatically enables processing for SDM).
  • Ensure that the absence type display feature items have Deferred processing on subsequent absences and Deferred processing on initial entry are Unselected.

Customers Without Existing Setup

Customers without existing setup should follow these setup instructions. Ensure that you set up the required components in this order:

  • Create the rate definitions.
  • Create the required elements to be associated with the statutory absence plans.
  • Create the statutory absence plans.
  • Create the absence types, including assigning the appropriate certifications to the absence type.
  • Enable processing.
Note: Absence plans and types vary depending on the type of absence being set up.

If you have multiple types with different units of measure, you need to use a separate plan for each type.

Transfer of TRU During an Absence Period

Assignments that are transferred to another TRU will need to be re-evaluated. The evaluation will happen within the new TRU and the absence will be processed only using absence information from the new TRU. This can cause non-payment due to not passing statutory checks and certificates will be produced for any checks that aren't meet. Any re-evaluation will also only use the start date of the assignment in the new TRU and so payment schedules might not be accurate for the absence.

User will need to manually work out the correct information and update the absence record accordingly, this might involve using the override fields. This is done at the user's discretion and own risk and they would then need to ensure that the payments and processing for the absences are correct.

In the case of Sickness During Maternity it will not be possible to enter the Sickness During Maternity absence record if no Statutory Maternity record exists in the new TRU. Customer will need to calculate the payments manually and also provide their own solution using core functionality to suit their organizational requirements.

Assignments on Different TRUs

Statutory Maternity Pay, Statutory Adoption Pay, Statutory Paternity Pay and Sickness During Maternity absences are entered at a person level. (Core Functionality) This means that one absence record is used to provide information to all the assignments on the different TRUs. The start and end date of the absence will need to be the same for all assignments on all the TRUs.

Each TRU will have a case for the assignments that are aggregated for the TRU and any overrides or certificates entered at case level will only be applicable to the TRU which associated with the Case.