FSA Worksheet Calculating Remaining Pay Periods Incorrectly For Event Maintenance Events When Using Check Date
(Doc ID 2080557.1)
Last updated on JUNE 18, 2018
Applies to:PeopleSoft Enterprise HCM Benefits Administration - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The FSA Worksheet is calculating the remaining pay periods incorrectly for Event Maintenance events such as HIR where the deduction begin date is after the current pay period end date, but the Pay Check Date is several days later.
The current design of this calculation utilizes the configuration of the Balance ID associated to the FSA Benefit Plan for the field Use Date to identify if Check Date or Pay End Date is used to count the open on cycle pay periods for the Pay Calendar associated to the employee. If Pay Check Date is used and there is a delay between the Pay End Date and the Pay Check Date, the potential concern is that the current unconfirmed pay period is also included in the count. This does not make business sense.
1. The Current pay period ends on 11/18/15, with a check date of 11/27/2015.
2. The Current pay period deductions will be confirmed on 11/19
3. The Deduction begin date for a new election is 11/19/2015 but is elected on 11/16/2015
Since the current pay period has not yet been confirmed at the time the employee views the FSA worksheet, the FSA worksheet counts the check date for the current pay period, even though the deduction begin date is not dated until AFTER the pay period ends. This results in one too many pay periods remaining.
If this same Employee viewed the worksheet on 11/20, AFTER the pay period has processed, the pay periods remaining will be correct.
The count should only include check dates that occur AFTER the pay end date of the pay period that contains the deduction begin date.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!