PTO Accrual After an FTE Change and Unpaid Leave
Northline Health has 600 US employees on a biweekly payroll. Its 'Standard PTO' accrual plan grants hours based on length of service and FTE, using a 40-hour week as the full-time equivalent. On March 1, an employee moves from 0.8 FTE to 1.0 FTE. From June 1 to July 15 she takes an unpaid personal leave. In August the HR analyst finds her PTO balance is 14 hours higher than expected. A new hire who started June 20 shows a zero balance even though the plan is open to all regular employees. The payroll team wants to 'just adjust the balance' before the next pay run. The absence administrator says the plan has not changed in two years and blames the manager. You need to find the configuration cause and protect audit history.
1. What configuration should you inspect, in what order, and why?
Read the worked answer
I would start with enrollment and eligibility, because a zero balance for the new hire suggests the person may not be enrolled or may not have met an eligibility criterion. I would check the absence plan and accrual plan eligibility profiles, the enrollment record, and the enrollment date. If the new hire was eligible on day one, the issue is enrollment; if there is a service or waiting-period rule, the zero balance may be correct.
Next I would inspect the accrual plan rules: accrual frequency, length-of-service bands, FTE proration, and whether the plan uses assignment FTE as of the accrual date. The 14-hour overbalance is consistent with the plan continuing to accrue at 1.0 FTE during unpaid leave or with a missed FTE effective-date change. I would also check whether the unpaid leave absence type is configured to suspend accrual. Finally, I would review the employee's assignment history and balance adjustments. The order matters because adjusting the balance first would hide whether the cause is eligibility, enrollment, proration, or suspension.
2. How would you correct the balance and prevent recurrence? Include testing and audit considerations.
Read the worked answer
I would not allow a direct balance edit without a reason code. First I would determine the correct balance from the enrollment date, FTE history, and the suspension period. Then I would use a balance adjustment with a clear reason, effective date, and approver, so the correction is auditable. If the cause is a missing suspension rule, I would fix the absence type or plan configuration and recalculate future accruals; I would not rely on a one-time adjustment alone. For the new hire, I would enroll the worker if eligible or document why the zero balance is correct.
Testing should happen in a sandbox with three cases: the FTE change, the unpaid leave, and the new hire. I would verify accrual at each period boundary and check that the adjustment does not create a negative or duplicate balance. After validation, I would load or enter the correction in production and reconcile the next two pay periods. Prevention includes a quarterly audit of FTE changes against accrual balances and a checklist for leave types that must suspend accrual.
3. The payroll team wants the adjustment completed before the next pay run. What sequencing issues would you raise?
Read the worked answer
The main sequencing issue is that a balance adjustment and a payroll payment are not the same thing. PTO balances are absence records; payroll pays hours only when an absence is recorded or an element is entered. If payroll pays out the 14 hours before the balance is corrected, the employee may be overpaid and the balance may go negative. I would separate the two actions: correct the absence balance first, then decide whether any payout is required.
I would also check the pay period cutoff. If the correction misses the cutoff, it should not be forced into the current run by editing a processed result. Use the next run or an off-cycle payment if policy allows. I would confirm with payroll whether the 14 hours are to be removed from the balance only or also recovered from pay. If recovery is needed, document the employee communication and use an auditable element entry rather than a manual check.