Thursday 21 June 2018

Choosing recurring or non recurring element for absence element setup

You can associate each absence type with a recurring or nonrecurring absence element. Each element has an input value with either hours or days as its unit of measure.

Using a Nonrecurring Element

Nonrecurring element entries are valid for one payroll period. When you enter an absence of a type associated with a nonrecurring element, the application creates an element entry for the period in which the absence start date falls. For example, if you enter an absence that starts on 4 May for someone on a monthly payroll, the entry is dated 01 May to 31 May.
The entry is only created when you enter the absence end date, and you must enter the absence duration at the same time. The duration can be defaulted if you set up an absence duration formula. The full value of the absence duration is recorded in the absence element entry, even if the end date falls outside of the payroll period.

Using a Recurring Element

Attention: This option is only available if you use Oracle Payroll and the Proration functionality is enabled in your localization.
UK Users: If you use the Statutory Absence Payments feature you must continue to use nonrecurring elements to record long term sick leave.
Use this approach if you want to begin processing absences before end dates are recorded. You do not enter absence duration on the recurring element entry. Instead, you use a payroll formula to calculate the absence duration to be processed in each payroll period. Use the absence duration formula to calculate the duration displayed on the Absence Detail window. This value is deducted from the current PTO accrual when you enter an end date for an absence type that is associated with a PTO accrual plan.
Recurring element entries start on the absence start date and end on the absence end date (if there is an end date). If the absence ends in the middle of a payroll period, the payroll run detects and processes the absence using the proration functionality.

No comments:

Post a Comment