Tips for Retroactive Processing

What is the value of an element that receives a forwarding adjustment?

• When you use forwarding retro, the adjustment is included in the resolved value for the element.

• Output results keep the current and adjustment values for earnings and deductions separate. But when the element is used, the two values are summed to obtain the resolved value for the element.

• The batch resolution modules sum the current and adjustment values when an element is used.

How do I keep the adjustment value of an element separate from the current value?

Generally, when you use forwarding retro, the adjustment is included in the resolved value of the element. However, to keep the adjustment value for an element separate from the current value, you forward the adjustment to another element using the Retro Process Overrides page. If the purpose of the element is to track adjustments, define the other element with the calculation rule amount = 0.

Can Global Payroll calculate retro across countries?

The default retro method, retro process definitions, and trigger event IDs are defined by country. The system does not calculate retro across countries. However, if a payee transfers to another country, and it's later discovered that the payee should have received additional pay while employed in the first country, it might be possible to process retro for that payee even though he or she is inactive in the original country. This depends on the forward limits that apply at the pay entity level and other processing rules that determine how long after a payee is inactive he or she remains eligible for retroactive processing.

What happens when multiple triggers are generated and each points to a different retro process definition?

Suppose that multiple retro events occur, causing multiple retro triggers to be written to the trigger tables. If these triggers call for that calendar run to be processed (recalculated) using different process definitions, a conflict will occur. In such a situation, where the events that cause retroactive processing activate the application of more than one process definition for the same payee in the same calendar, the system writes an error message and does not process retro. Only the current period is calculated. Retro triggers are not marked as processed.

For a payee, you cannot have more than one process definition resulting from the retro events that cause retroactivity for that calendar run. The same process must apply for all calendars in the calendar group.