Concept: Retro Pay Calculation Preprocessor
You can use the
Run Retro Pay Calculation Preprocessor
task to get insights into the number of workers that require a retro pay calculation for a specific pay group. This enables you to anticipate processing times and identify specific workers that might cause performance delays in upcoming retro calculation runs.On the task, you can specify the relevant
Run Frequency
and the Pay Run Groups and/or Pay Group Details
. For the Calculation Criteria
you can select either of these run frequencies:
- Run Now
- Run Once in the Future
- Daily Recurrence
- Weekly Recurrence
- Monthly Recurrence
You can view the
Payroll Run Retro Pay Calculation Preprocessor
job on the Background Process
page that displays these columns on the Calculation Criteria
tab:
- Pay Group Detail
- Size Calculated
- ~Workers~ with Retro Events
- ~Workers~ without Retro Events
For
~Workers~ with Retro Events,
Workday:
- Adds to count when:
- Worker has supported retro results currently in progress.
- Worker has a new supported retro event detected.
- Doesn’t add to count when:
- Worker has a completed, suspended, or unsupported retro in the current retro run.
- Worker has a Payroll Retro Worker Data Event in progress.
- Worker has unsupported retro events entered since the last retro processed time.
- Worker has been terminated.
You can further drill into the number of
~Workers~ with Retro Events
for a specific pay group, and view details on Count
, Retro Calculate From Date
, and Retro Event Impact
. The Retro Event Impact
column indicates how a retro event type impacts the calculation with these statuses:
- New Events Detected- This status applies when a new supported retro event is identified and either of these conditions are met:
- There’s no in-progress retro worker result.
- The new event's effective date is before the effective date of an existing, in-progress retro worker result.
- Recalculating In-Progress Retro Events -This status applies when an update triggers a recalculation, based on either of these conditions:
- The worker already has an active, in-progress retro worker result.
- A new supported retro event is detected with an effective date after the event that triggered the current in-progress retro worker result.