Making Retroactive Adjustments to Positive Input

This topic provides an overview of retroactive adjustments and discusses how to correct positive input entries.

This topic discusses:

  • Positive input and the recalculation option.

  • Deleting positive input.

  • Applying deltas.

  • Mismatched segments and slices and the do not recalculate option.

  • Version numbers.

Positive Input and the Recalculation Option

Positive input overrides an element's recalculation rule during retroactive processing; the system uses the values provided through positive input to resolve an instance whether or not you selected the Always Recalculate check box on the element's Calculation page.

An exception to this rule applies to deleting positive input.

Deleting Positive Input

If you delete positive input for an element marked never recalculate, and the pay calendar has been finalized, it's best to keep the original entry and change the action to Do Not Process. Then when you rerun the payroll, the system doesn't resolve the element. If you delete the entry instead and there's element or period segmentation, results can be unpredictable.

Applying Deltas

To bring forward retroactive deltas as adjustments into the current period when segments match, the system sums deltas for the element and forwards them to the first segment in the current calendar. If the first segment is sliced, the system forwards the adjustments to the first slice within this first segment. When the element resolves multiple times per segment in the current period, the system observes the following hierarchy when it applies the summed deltas:

  1. Normal resolution of the element.

  2. Override occurrence.

  3. Additional occurrence.

In the current period, when multiple instances of positive input with only the Add action type exist, the system applies the adjustment to the normal resolution of the element, not to the additional resolutions. Where multiple rows exist as a result of Override and Add action types, the system applies the retroactive adjustment to the override resolution of the element. Lastly, if a normal resolution of the element does not exist, and an override resolution of the element does not exist, then the system applies the retroactive adjustment to the additional resolution of the element. It applies the adjustment amount only once.

Mismatched Segments and Slices

When retroactive processing occurs where element segmentation exists, the system compares the number of resolutions from the original calculation to the number of slices in the recalculation to determine if there is a mismatch. The system excludes positive input instances with an action type of Add in the count because this would cause a false mismatch.

Version Numbers

When you make retroactive adjustments to positive input from a non manual source, the system uses a versioning scheme to differentiate original entries from revised entries. The original entries are assigned the version number 1, populating the PI_VER_NUM field. The version numbers are incremented for subsequent adjustments. This versioning scheme differs from the version and revision numbers for tracking retroactive pay run results.

The system updates the version number assigned to all generated instances of positive input for that calendar, including any unchanged instances, so that you can differentiate between the complete set of original entries and the complete set of entries for retroactive processing.

Say the Absence Take process generates an instance of positive input with a value of 1000. Version 1 is automatically assigned to this and every other non manual entry. Now, two months later, a retroactive adjustment changes the value to 1200. When you rerun the payroll for the target calendar, the updated entry and all other non manual entries of positive input are automatically named version 2.

To correct an instance of positive input, make the correction in the pay period of the original entry. Assuming that you've defined retroactive triggers to detect the online changes, your entries are written to a trigger occurrence table. When you run the next payroll cycle for the payee, the system reads the data from the table and adjusts the positive input retroactively.