Concept: Supported, Unsupported, and Unprocessed Retro Events

Some events that you or someone else in your organization enter can trigger retro pay calculations. You can also select workers to process in smart retro using those events. The

Payroll Retro Event Categories

tab on the

View Payroll Event Categories

report lists individual retro triggering events for each category. A triggering event can be a supported or unsupported event. Examples:

A change in benefit election deductions triggers retro, but not a change in benefit dependents.
A compensation change triggers retro and is a supported event.
A pay group change triggers retro but isn't a supported event for Payroll for Australia, France, Ireland, the UK, and the U.S.
A company change triggers retro but isn't a supported event for Payroll for Canada.
A company change is a supported event for Payroll for Ireland only when the companies share the same Employer Registration Number.

When an event triggers retro, Workday considers all events from the last completed period to the No Retro Processing Prior To (NRPPT) date. Those events include both supported and unsupported events, regardless of whether they're related to the triggering event.

Example for Payroll for Australia, France, Ireland, the UK, and the U.S.: The current pay period is July, and Meghan has a retro bonus to process from June. Your payroll administrator enters a pay group change also effective in June but doesn't notify you. When you run retro, Workday considers both the bonus and the pay group change.

Example for Payroll for Canada: The current pay period is July, and Meghan has a retro bonus to process from June. Your HR partner enters a company change also effective in June but doesn't notify you. When you run retro, Workday considers both the bonus and the company change.

Workday generates retro differences that you can pay in target pay periods for workers when you enter events for them that both:

Trigger retro pay calculations.
Are supported events.

You can identify supported events for each country in the

All Supported Payroll Retro Transaction Types

report.

Workday doesn't calculate retro differences for unsupported events regardless of the retro setting on the pay component. You can view these events on the

All Unsupported Payroll Retro Transaction Types

report. When you run retro for workers with unsupported events, Workday:

Identifies the event as
Unsupported
in reports.
Changes the workers' NRPPT date to 1 day after the last period with completed results.
Ignores any events, supported or unsupported, before that date.

You can review these events on the

Retro Calculation Processing Report

and make manual adjustments as needed.

For Payroll for Australia, France, the UK, and the U.S., when you retroactively make changes to a worker's pay group and have a supported retro event, Workday processes the supported retro event only when the effective date of the supported retro event overlaps with the payroll results affected by the pay group change. Example: You complete pay calculations for January, February, and March. You retroactively make changes to the worker's pay group in February and then run pay calculation and complete for April. If you enter retro pay input in April, Workday processes retro for this supported event as the payroll results for April aren't affected by the pay group change. If you add payroll input to any of the prior pay periods such as January, February, or March, Workday doesn't process retro for this supported event and identifies the unsupported retro pay group change.

For Payroll for Canada, when you retroactively make a company change to a worker  and have a supported retro event, Workday processes the supported retro event only when the effective date of the supported retro event overlaps with the payroll results affected by the company change. Example: You complete pay calculations for January, February, and March. You retroactively make changes to the worker's companyy in February and then run pay calculation and complete for April. If you enter retro pay input in April, Workday processes retro for this supported event as the payroll results for April aren't affected by the company change. If you add payroll input to any of the prior pay periods such as January, February, or March, Workday doesn't process retro for this supported event and identifies the unsupported retro company change.

For Payroll for Ireland, when you retroactively transfer a worker between companies with the same ERN and have a supported retro event, Workday processes the supported retro event only when the effective date of the supported retro event overlaps with the payroll results affected by the company change. Example: You process a worker’s February transfer in April and then run pay calculation and complete for April. If you enter retro pay input in:

April, Workday processes retro for this supported event as the payroll results for April aren't affected by the company change.
A completed prior period (Example: March), Workday doesn't process retro for this supported event and identifies the unsupported retro company change.

When workers have a supported retro event such as a payroll input, any of these factors can cause Workday not to consider it in retro:

The event occurs before the worker's NRPPT date, or in the same period as that date.
The worker has unsupported events occurring in the same pay period.
You select the
Do Not Recalculate During Retro
or
Always Gross-Up
check box on the earning related to the event.
You leave the
Recalculate During Retro
check box clear on the deduction related to the event.
The worker isn't eligible for the pay component related to the event.
For Payroll for Canada and the U.S., the worker has positions in more than 1 company and they have no existing pay results in those companies. Workday reports the entry as processed but doesn’t generate any results to forward to their current payroll. You can identify workers with multiple jobs in different pay groups and companies on the
Audit - Workers with Multiple Jobs having Different Organization Assignments
report. Example: Jane is in company A and you enter an additional job in company B and a bonus for the same period retroactively. When you run retro, Workday processes the retro bonus but doesn't pay it in company B.

When you run retro for workers with unprocessed events:

Workday identifies those events as
Unprocessed
in reports.
You can adjust the configuration and run retro again to process them. Example: You can manually resolve unsupported events and move the workers' NRPPT date before the unprocessed event occurs.

When you use a position override to determine a worker's payroll processing position, retroactive changes to position override attributes can cause the processing position to change. Changing the processing position isn't a retro event and doesn't trigger a retro calculation. But when a supported retro event occurs, Workday rederives the processing position when you run the retro calculation.

Example: Ben has 2 positions in the same pay group and company. His primary position is the payroll processing position. You retroactively adjust Ben's scheduled weekly hours, so that his additional position becomes his processing position. When a supported retro event occurs, Workday uses the additional position to calculate retro differences.

Retroactive changes to the processing position can also affect worker eligibility for pay components in the retro period.