The Seniority Qualifier checks to see which employees are eligible for attendance policy updates. It restricts the associated attendance rule to apply only to employees with a specific seniority. This seniority can be based on a variety of factors, such as length of service or the date employees were assigned to the attendance rule policy.
For example, you can configure the qualifier so that only employees with two to three years of service are eligible. Or if you need to configure a more granular range, you can specify 16 to 18 months.
| Setting | Description |
|---|---|
| Start Date |
The start date that determines the employee’s seniority. This is the date Dayforce starts counting the seniority criteria from. You can select one of the following dates:
|
| Scale |
The employee eligibility that the seniority is based on. This sets what Dayforce counts to determine eligibility. This can be measured in years, months, weeks, days, or hours (either the number of hours an employee has been with the organization, or the number of hours they have worked). The Calendar Month and Half Calendar Month options function slightly differently than the other options in this drop-down list, in that they look only at static calendar months (that is, the first to the end of the month), rather than rolling months (for example, from the 16th of one month to the 16th of the next month). When determining how many calendar months of seniority an employee has achieved, Dayforce counts the number of month ends between the start date and the date being evaluated. For example, an employee who started January 16 has achieved two calendar months of seniority on March 1. Similarly, when determining how many half calendar months an employee has achieved, Dayforce counts the number of month ends and the number of transitions between the 15th and the 16th of a month that have occurred between the two dates. This means that on March 1, the employee who started January 16 has achieved three half calendar months of seniority, while an employee who started earlier in January has achieved four. |
| Greater or equal to | The number of seniority units an employee must have to meet eligibility. This can be in years, months, weeks, days, hours, or minutes, depending on the value selected in the Scale drop-down list. |
| Less than | The number of seniority units that an employee must have less than to be eligible. For example, with Months of Service selected in the Scale drop-down list, 6 entered in the Greater or equal to field and 18 entered in the Less than field, only the employees who have worked six months or more, but fewer than 18 months, are considered eligible. |
| Calendar year start date |
The start of the calendar year. By default, when a date isn’t selected in this field, Dayforce uses January 1. To configure a different start date for the calendar year, click the calendar icon and select a date. For example, with May 1 configured as the start date for the calendar year, Dayforce calculates how many calendar years of seniority an employee has using May 1 as the start date. This means that on May 1, 2012, an employee who started on July 1, 2011 is considered to have one year of seniority. Note: Dayforce examines this setting only when Calendar Year is selected in the Scale drop-down list. |
| Qualify month end if day not in month | Dayforce uses the last day of the month in cases where the start date is a date that doesn’t exist in the current month. For example, an employee qualifies for an entitlement after three months of service from their start date of January 31. With this checkbox cleared, Dayforce applies the entitlement on May 1, because there isn’t a 31st day in April. With this checkbox selected, Dayforce uses the last day of the month, in this case April 30, instead. |
| Exclude leap year day in years of service | Exclude leap year days when Dayforce calculates years of service. |