Future Dated Change is not a separate Webhook, but special behavior for existing webhooks when an action is dated to take effect at a specified time in the future.

Triggers for Future Dated Change Webhooks Notification

Once the future record becomes the current record, the Webhook sends.

Common use cases for this feature

1. new hires
2. department changes or reorgs
3. pay changes
4. employee terminations

📘

Example

• The company payroll processes weekly. Today is March 6.
  • The user enters employee department changes that take effect on March 13.
  • The department changes are effective on the March 17 check date.
  • The user enters new pay rates for employees that take effect on March 20. These pay rates are effective on the March 24 check date.
  • HR & Payroll does not trigger webhooks for these future changes.
• The user processes payroll for the March 10 check date. Once the payroll successfully processes, the March 17 check date becomes the current check date. The department changes become current and webhooks trigger in Web Link.
• The user processes payroll for the March 17 check date. Once the payroll successfully processes, the March 24 check date becomes the current check date. The pay rate changes become current pay rates and webhooks trigger in Web Link.