This page (revision-4) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 3 KB JEscott to previous
3 26-Nov-2021 10:22 3 KB JEscott to previous | to last
2 26-Nov-2021 10:22 3 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 removed one line
!!!VACATION PAY OVERVIEW
At line 6 changed one line
This process respects and does not interfere with the time scheduling module. When an employee is put on vacation for three weeks, [UPCVAC] will pick up and pay the employee three weeks vacation. The schedule exceptions on [DTSH]/[DTESH] for the coming weeks will still reflect that the employee is away from post even though the leave has been processed by payroll. When time scheduling is used to populate the payroll with time, the employees who have already been paid in advance do not get paid again by the scheduling system.
This process respects and does not interfere with the time scheduling module. When an employee is put on vacation for three weeks, [UPCVAC] will pick up and pay the employee three weeks vacation. The schedule exceptions on [ITTE] for the coming weeks will still reflect that the employee is away from post even though the leave has been processed by payroll. When time scheduling is used to populate the payroll with time, the employees who have already been paid in advance do not get paid again by the scheduling system.
At line 15 changed 7 lines
In order for leave lines to qualify for the [UPCVAC] program they must have the following set up:
*The [X_ABSENCE_SOURCE] lexicon must have a value of AT DATA ENTRY.
*The [X_ACCRUAL_STATUS] lexicon must have a value of 1-REQUESTED.
*The Start and End Dates of the leave line must match that of the Pay Period’s Start and End Dates.
*The leave line must span an entire week, it cannot be just for 1 day.
*The Time Basis of the Time Code must be HOURLY or DAILY.
*The Payroll must be WEEKLY.
Time to be taken is entered in the Leave Lines ([IAAL]) for all future attendance time.
At line 16 added one line
Vacation pay is generated for Leave Lines ([IAAL]) that span an entire weekly pay period. If the leave line does not begin or end on a week boundary, then the line will not be picked up. There can be NO gaps in time between leave lines. The first gap of any size will terminate vacation generation for the employee.
At line 29 changed one line
Vacation Pay is generated for Leave Lines that span an entire week. If the Leave Line does not begin or end on a week boundary, then the line will not be picked up. There can be NO gaps in time between leave lines. The first gap of any size will terminate vacation generation for the employee.
Vacation pays are generated for multiple continuous weeks into the future depending on time codes provided during report selection.
At line 48 removed 5 lines
----
![Notes|Edit:Internal.VACATION+PAY]
[{InsertPage page='Internal.VACATION+PAY' default='Click to create a new notes page'}]