Fusion Payroll: Recalculate Payroll for Retroactive Changes Process Doing Payment Reverse Based on Check Date, NOT Date Earned
Last updated on DECEMBER 09, 2016
Applies to:Oracle Fusion Global Payroll Cloud Service - Version 188.8.131.52.0 and later
Oracle Fusion Global Payroll - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Found that if an employee has changed assignment status retroactively from Payroll eligible to No Payroll, retro bases the payment reverse on check date and NOT date earned.
For example: an employee who was active till date earned should get paid for that period irrespective whether he was No payroll on check date . However retro thinks otherwise and taking back the payment.
Expect that Retro would not reverse the payment for the period where the employee went from Payroll eligible to No Payroll.
Employee who was active till date earned should get paid for that period irrespective whether he was No payroll on check date.
The issue can be reproduced at will with the following steps:
Payrolls already run till 9/23/16
Assignment status before making them ‘No Payroll’ : Active - Payroll Eligible
Updated to ‘No Payroll’ retro actively : Suspended - No Payroll Effective Start Date 9/13/16
Running the Recalculate Payroll for Retroactive Changes process
Employee was Payroll eligible till date earned 9/11/16 and no payroll from 9/13/16. Check date is 9/16/16 and retro calc reversing the payment for that pay period which is incorrect.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms