Recurrences represent when, and at what frequency, employees earn more benefits. For example, you can configure that employees earn more vacation time every three months. You can also configure a rollover recurrence, which represents how often benefits are paid out or reduced. For example, you can configure entitlements so that at the start of every year, employees can carry over only five unused vacation days from the previous year.
You can set up different types of recurrences in Pay Setup > Entitlements in the Recurrences tab.
Role feature access: Pay Setup > Pay Setup > Entitlements > Entitlement Definitions
When you configure a recurrence, you can customize:
- Its frequency, such as weekly or yearly, using the Frequency Type and Frequency Value settings.
- Its start and end dates, using either the Start Date Type or Start Date setting, and either the End Date Type or End Date setting.
- When it occurs, using the Occur Type, Occur Value, Occur Offset, and Occur Offset Unit settings.
Some of these settings are optional. Each section below describes these settings:
For each recurrence that you configure, you must set a frequency type in the Frequency Type drop-down list. In the Frequency Value field, you can set the number of times that the recurrence repeats, such as every 2 weeks or once a year. This field supports only whole numbers. The Frequency Value unit depends on your selection in the Frequency Type drop-down list.
| Option | Description |
|---|---|
| Daily | The entitlement recurs daily. |
| Weekly | The entitlement recurs weekly. |
| Monthly | The entitlement recurs monthly. |
| Yearly | The entitlement recurs yearly. |
| Once | The entitlement recurs one time. |
| Semi-Monthly |
The entitlement recurs twice a month, fifteen days apart. If the recurrence start date is the beginning of a month or if there’s no start date configured, the entitlement recurs on the 1st and 16th dates of a month. If you configure a recurrence start date at a different point in a month, the entitlement recurrences are offset but are still fifteen days apart. For example, if the recurrence start date is April 25, the entitlement recurs on May 10, May 25, and so on. |
| Contract Hours Period Start | The entitlement recurs at the start of a work contract period. |
| Contract Hours Period End | The entitlement recurs at the end of a work contract period. |
| Last Transaction In Period |
The entitlement recurs after the last balance transaction. It’s recommended that you configure an offset with this frequency type so that recurrences don’t overlap with subsequent balance transactions. This functionality doesn’t include balance transactions that are triggered by the system’s entitlement engine. Rather, it includes balance transactions from other sources, such as timesheets and time away requests. For more information about source types for balance transactions, see the Balance Events section in The Table View Tab. Important: If you use this frequency type, make sure that you leave the Recalculate Balance Periods checkbox cleared when running the Award Entitlements To Employees background job. See Award Entitlements To Employees. |
| Semi Monthly Middle And End Of Month | The entitlement recurs twice a month on the 15th date and on the last date of the month. Depending on the month, this could be the 30th or 31st date, or the 28th or 29th date in February. |
Recurrence Start and End Dates
Optionally, you can configure the start and end of a recurrence. You can configure the recurrence start and end using one of two methods:
- The Start Date Type and End Date Type settings. In these drop-down lists, you can select key dates for the recurrence’s start or end, such as the employee’s hire date or termination date. Some options are available only for the recurrence’s start or end, as noted in the table below.
- The Start Date and End Date fields. Use these fields to configure customized dates for the recurrence’s start or end.
Don’t use both the Start Date Type and Start Date settings, or both the End Date Type and End Date settings. Choose one setting or the other, depending on your requirements. Consider an example where a user selects an option in the Start Date Type drop-down list and enters a customized start date in the Start Date field. In this scenario, Dayforce prioritizes the Start Date field configuration and uses this date for the recurrence, and ignores the selection in the Start Date Type drop-down list.
| Option | Description |
|---|---|
| Birth Date |
Before You Begin: This option is available only in the Start Date Type drop-down list. The employee’s birth date, as set in People in the Personal > Confidential Information screen. |
| Hire Date | The employee’s most recent hire date, as set in People in the Employment > Employment Settings screen in the Key Information tab. |
| First Date Worked | The employee’s first date worked, as set in People in the Employment > Employment Settings screen in the Key Information tab. |
| Start of Year | The start of the year (January 1). |
| Termination Date | The employee’s termination date. This option is meant for employees who are terminated at the start of their termination date. |
| Seniority Date | The employee’s seniority date, as set in People in the Employment > Employment Settings screen in the Key Information tab. |
| First Fully Terminated Date | The first date after the employee’s termination. This date follows the employee’s termination date. This option is meant for employees who are terminated at the end of their termination date instead of the start. |
| Original Hire Date |
Before You Begin: This option is available only in the Start Date Type drop-down list. The employee’s original hire date, as set in People in the Employment > Employment Settings screen in the Key Information tab. |
| Entitlement Override Date | The employee’s entitlement override date, as set in People in the Employment > Employment Settings screen in the Key Information tab. See Set an Entitlement Override Date. |
| Long Service Leave Eligibility Date |
Before You Begin: This option is available only in the Start Date Type drop-down list. (Australia and New Zealand only) The employee’s Long Service Leave (LSL) eligibility date, as set in People in the Employment > Employment Settings screen in the Key Information tab. |
| Last Day in Policy |
Before You Begin: This option is available only in the Start Date Type drop-down list. The last effective date of the employee’s entitlement policy assignment. When you change an employee’s entitlement policy assignment in People and recalculate balances, entitlements that you’ve configured with this recurrence start date will process and end-date the balance period the day before the assignment change. This option should be used exclusively for entitlements where you want to end-date the balance period. See End-Date Balance Periods. Also, this option is incompatible with rollover and proration recurrences. When you’ve configured a recurrence with this option, you can’t select the recurrence in the Rollover Recurrence or Proration Recurrence drop-down lists in Pay Setup > Entitlements in the Entitlements tab when you’re configuring an entitlement. |
Occur Settings for Recurrences
Optionally, you can specify when a recurrence occurs with more granularity. Use these settings to specify when a recurrence occurs:
- Occur Type: The type of day that the recurrence occurs. The options are: Day, Day of the Week, and Day of Last Week. See the table below for descriptions of these options.
- Occur Value: The number that represents when Dayforce performs any entitlement actions that are tied to the recurrence. The number that you enter depends on the option that you selected in the Occur Type drop-down list. See the table below for more information.
- Occur Offset: The number of days that Dayforce offsets the recurrence’s action by, based on your Occur Type and Occur Value configuration. For example, enter 2 and the action occurs two days after the date specified by the Occur Type and Occur Value settings in each frequency period.
- Note: The original recurrence and adjusted recurrence must be within the calculation period, otherwise the system won’t detect the recurrence.
- Occur Offset Unit: The unit for the occur offset. Day is the only option.
| Option | Description |
|---|---|
| Day | The day that the action occurs. In the Occur Value field, enter the number of days into the frequency period that the action occurs. |
| Day of the Week | The day of the week that the action occurs. In the Occur Value field, enter a number from 0 to 6 to represent the day of the week the action occurs. 0 represents Sunday and 6 represents Saturday. |
| Day of Last Week | The day from the previous week that the action occurs. In the Occur Value field, enter a number from 0 to 6 to represent the day of the week the action occurs. 0 represents Sunday and 6 represents Saturday. |