|
|
|
|
|
|
LOP Business Rule - Clock data takes precedence
Employees who clocked in/out for the whole day or part of the day are not expected to be on leave during that time.
This topic describes what LOP does in Daily View for the Time and Attendance module where employees use clocks to record their actual start and finish times for the day.
This topic assumes the employee passes the validation checks for Actual Pays
When a leave request is approved and the day does not yet have any Actuals, i.e. before you have run the T&A processes 'Import Clock Data', 'Process Clock Data' and 'Clock Result Data', PayGlobal creates timeband for the portion of the leave request the fits within the employee's roster.
If the duration requested is greater than what the employee was expected to work (i.e. outside the hours of the employee's derived roster), PayGlobal adjusts the Leave Request Units Requested to match the Hours on the leave timeband.
In order to determine whether or not there is enough valid information to create a leave timeband for a day on which an employee has clock data, the LOP feature must analyse the existing clock data. This is necessary because in the case of a missing clock swipe or excess(erroneous) clock swipe the end times applied to the resulting timebands are sometimes invalid, e.g. the end time may result in a value of 00:00 meaning the midnight before the start time. This is a limitation within the Time and Attendance module - see Limitations for more details.
When it is determined that the existing timebands are valid, PayGlobal does the following:
 |
Topic: 44111
