Issue/Symptom/Question

We had an employee who was overpaid PTO by 7 hours. We are trying to understand how the system processed this as the PTO code is set to "E" if the balance is <0 (screenshot below). The system allowed the entry 7 hours of PTO on his last payroll of the year which was ultimately paid out even though this exceeded his balance by 7 hours. There was additional PTO paid out within the same pay period . We are trying to understand why the system allowed this to be paid.

Applies To

Penta for Windows

Payroll

Resolution/Fix/Answer

Here's what happened:

1. On the employee's payroll date of 12/28, the payroll user recorded 7 hours of PTO effective 12/24.  Penta's check added up PTO taken through the last date of PTO entered in this run (12/24), determined that the 12/24 time would take the PTO balance to zero, and allowed it.
2. Then on 12/29, the payroll user recorded another 7 hours of PTO, spread across spread across 12/21, 12/22 and 12/23.  Penta's check again added up PTO taken through the last date of PTO entered in this run (12/23), but excluded the 12/24 PTO because it came after the last date entered during this session, and again determined that the 12/21-12/23 time would take the balance to zero, and allowed it.

Penta does not look for future PTO entered in earlier sessions.  Penta assumes that PTO will be entered and distributed in the order that it was taken, which didn't happen in this case.