Stop reprocessing of cascading paycode and leave edits

When you make a paycode edit, if there is a cascading paycode edit or leave rule cascade that draws from the same accrual as the edit, then the cascades reprocess. This is the expected behavior. You can stop reprocessing of cascades, if needed, using system settings. The global system settings allow the cascade to occur when it is first entered and then stops subsequent cascades when other edits are made (through the UI or API). Those edits include standard paycode edits that draw from the same accrual.

You can stop reprocessing in signed-off and unsigned-off time.

Also see More on reprocessing cascading paycodes and leave edits.

  1. Go to Administration > Application Setup > System Configuration > System Settings > Global Values tab.
  2. Find this setting:
  3. global.WtkTotalizer.StopReprocessingCascades
  4. Enter a date for when you want the behavior to begin and save.
  5. When this setting is enabled, cascades occur when they are first entered and do not recascade when subsequent paycode edits are made. This setting stops reprocessing all cascades (those that occur in signed-off time and unsigned-off time). If you only want to stop reprocessing of cascades in signed-off time, then continue to the next step.
  6. To stop reprocessing of cascades only in signed-off time, find this setting:
  7. global.WtkTotalizer.AllowReprocessingCascadesInUnsignedOffTime
  8. Set the value to true and save.
    • true — When the global.WtkTotalizer.StopReprocessingCascades setting is enabled and true is selected for this setting, then cascades are only reprocessed in unsigned-off time. Cascades do not reprocess in signed-off time.
    • false — When the global.WtkTotalizer.StopReprocessingCascades setting is enabled and false is selected for this setting, then cascades do not reprocess in both signed-off and unsigned-off time.

Cascading paycodes are used to trigger cascading accrual takings as configured in the Cascading policy. For example, cascading accrual takings can be configured like this:

  1. Take time from vacation accruals until that time is depleted.
  2. Take time from sick accruals until that time is depleted.
  3. Additional time taken is unpaid.

Cascades by design adjust as accrual balances become available. For example, an employee requests 40 hours off for December which depletes their vacation and sick accrual balances. Then, the employee takes time off in November but since they don’t have any vacation or sick time available (because that time is already being used for the 40 hours in December), then this time is unpaid.

Later, the employee cancels the December vacation. Now, the time the employee took off in November reprocesses and is paid vacation time since the time is now available. In many circumstances, this is the desired and expected behavior. However, there are circumstances when you may not want this behavior to occur, for example:

  • When the reprocessed cascade is in a signed off period, which generates a pending historical correction.
  • When adding a standard paycode edit for time-off to a timecard that has a cascading paycode edit or leave rule cascade and these all draw from the same accrual. In this scenario, the cascades reprocess.