Advance the Pay Group Hands Off Date

The Hands Off Date in the Pay Group configuration defines the lock date prior to which employee payroll and schedule records are finalized and protected from recalculations or unintended modifications.
Note: The Employee Schedule Data and Payroll Data archiving policies evaluate both the Aging Date (configured in the Job Scheduler task parameters) and the Pay Group Hands Off Date. During execution, the archiving process uses the minimum or earlier date between the aging date and the hands-off date as the effective archive cutoff:

$$\text{Effective Archive Date} = \min(\text{Aging Date}, \text{Pay Group Hands Off Date})$$

To ensure historical data is successfully archived and does not remain in active database tables:
  • Regularly advance the Pay Group Hands Off Date after payroll processing and lockouts are complete.
  • If the hands-off date is not advanced, the archiving tasks will not archive any data beyond that static date, effectively preventing the archiving of schedule and payroll records.

Business rules and behavior

  • Inclusive Boundary: All dates on or prior to the Hands Off Date are locked from automatic default record generation such as default EMPLOYEE_SCHEDULE or WORK_SUMMARY records during Full Recalculation processes.
  • Mid-History Pay Group Changes: If an employee transfers between pay groups, the system evaluates the specific Hands Off Date associated with the active pay group for each effective historical period.
  • Impact on Archiving: When an Archiving Task is configured, records dated on or before the Hands Off Date are eligible for archiving. Records after this date are protected and skipped, regardless of the Aging Date set in the task.

    See Configuring archiving tasks.

Protection of archived dates

In Infor Workforce Management 2026.09 and later, the system does not regenerate default EMPLOYEE_SCHEDULE records for dates that are already archived.

Previously, default EMPLOYEE_SCHEDULE records were regenerated for archived dates. This caused the Employee Schedule Data archiving task to fail with constraint violation errors.

Note: 
  • Default schedule generation skips dates that fall within an archived range.
  • The Employee Schedule Data archiving task runs without constraint violation errors for these dates.
  • No configuration change is required to apply this behavior.