Skip to main content

Retroactivity

Overview​

Retroactivity handles changes discovered after an earlier calendar was already processed. The engine determines which past periods are affected, which method applies, and how current or prior balances should change.

Corrective Vs Forwarding​

DimensionCorrectiveForwarding
Effect on original periodOriginal results are recalculated and effectively replaced.Original results remain as processed.
Effect on current periodCurrent period mainly reflects the new recalculated state.Current period carries the delta adjustment forward.
Accumulator impactPast balances are updated.Past balances may remain while current balances absorb the delta.

What Creates Retro Triggers​

Retro is usually triggered by effective-dated changes to job data, compensation, supporting elements, or manually corrected element values. Run type configuration decides whether those triggers are consumed, while retro limit dates and calendar order decide how far the system goes.

Retro Adjustment Sources​

Run types can be configured so one run type forwards retro deltas into another. This is useful for infrequent runs, such as bonus or supplementary runs, that should not become the long-term carrier of retro adjustments. Instead, the deltas can be pushed into a regular production payroll run.

Corrective Handling And Accumulators​

Oracle's accumulator documentation adds one subtle but important point: when forwarding accumulators exist, the accumulator itself can override the pay entity's default corrective retro choice. This is a balance-design decision, not just a run-type decision.

Operational Notes​

  • Respect retro limit dates to control reprocessing volume.
  • Review calendar order when retro spans multiple dependent calendars.
  • Validate GP_RSLT_DELTA and related result records during analysis.
  • Recheck generation control and segmentation settings when retro output looks incomplete.

Key Takeaways​

  • Corrective and forwarding methods serve different audit and operational goals.
  • Retro scope depends on triggers, limit dates, run type settings, and calendar order.
  • Accumulator design can influence how retro behaves in practice.