The settings in the Time and Attendance section of the Properties tab in System Admin > Client Properties control how Dayforce processes time and attendance.
Use Tardy Rule
Controls whether the site uses tardy rule processing. When selected, tardy rules are enabled and Dayforce provides additional controls on the timesheet to handle when employees clock in or clock out either early or late. See Tardy Processing.
Cost Time Entries Against
Controls how Dayforce accounts for an employee’s wages and worked hours, including when employees clock in at different locations from where they were scheduled. Select an option in the Cost Time Entries Against drop-down list to determine where Dayforce charges an employee's worked time (that is, where the cost is allocated). The Cost Time Entries Against client property has the following options:
- Scheduled or primary location: Cost is tied to the location where the employee was scheduled, regardless of where they clocked in. This is the default setting.
- Clock location: Cost is tied to the location where the employee clocked in, regardless of where they were scheduled. There is no link to the schedule.
- Clock location; Always link to schedule: Cost is tied to the location where the employee clocked in and a link to the clock entry is added to the schedule.
Enable support for split pay by business day start time
Used to configure Dayforce to split pay by the business day start time. When selected, Dayforce can be configured to split the pay for shifts that cross between two business days for employees, based on their pay policy. For example, if the business day starts at midnight, and an employee works from 10:00 PM on Monday to 5:00 AM on Tuesday, Dayforce splits the pay for the shift so that the employee is paid for two hours on Monday and then five hours on Tuesday.
When selected, Dayforce shows the Split Pay at Day Start Time checkbox in Pay Setup > Pay Policy. When the Split Pay at Day Start Time checkbox is selected for a specific pay policy, the pay for employees who are assigned the policy is split when it crosses two business days.
Enable support for job rate worked
Enables the Respect job rate worked and Allow lower job rate to override base rate checkboxes in Pay Setup > Pay Policy.
By default, Dayforce pays employees at the higher of either their base rate in People, or the rate for their primary work assignment. For example, if an employee’s base rate is $10, and the rate for their primary work assignment is $9, Dayforce would pay the employee at their $10 rate. In cases where an employee works a non-primary work assignment, they are paid at the higher of either their usual rate or the rate for the work assignment they actually worked. Continuing the example above, if the employee works a shift for a non-primary work assignment with a rate of $12, Dayforce would pay them their $12 rate.
When the Allow lower job rate to override base rate checkbox is selected in Pay Setup > Pay Policy, Dayforce ignores the employee’s base rate and pays the employee the higher of either the rate for their primary work assignment or the rate for the work assignment they actually worked. Continuing the example above, the employee would be paid their $9 rate by default, except for time worked at their non-primary work assignment with the $12 rate.
When the Respect job rate worked checkbox is selected in Pay Setup > Pay Policy, Dayforce ignores the employee’s primary work assignment rate and pays them at the higher of either their base rate for the rate for the work assignment they actually worked. Continuing the example above, the employee would be paid their $10 base rate for time worked at their primary work assignment, and their $12 rate for their non-primary work assignment.
When both of these checkboxes are selected, Dayforce always pays the employee at the rate for the work assignment they actually worked, regardless of their base rate or the rate for their primary work assignment.
Unpaired Threshold
Defines the maximum duration, in hours, an “in” clock entry can occur from the next “out” clock entry and still be paired by Dayforce and considered a single shift. For example, enter 14 and employees can clock in and out within 14 hours and Dayforce pairs the clock entries together as a single worked shift. An employee could clock in at 8:00 AM and clock out any time before 10:00 PM (14 hours later) and Dayforce considers the time a single, worked shift.
This client property also defines when Dayforce marks recorded shifts on the timesheet with a missing clock entry problem. After the unpaired threshold has passed from when an employee clocks in, Dayforce marks the shift with the problem icon and states that the shift is missing an out clock entry. The employee’s manager would then need to correct the problem by providing an end time to the worked shift. Continuing the example, if the employee hadn't clocked out by 10:00 PM, beyond the unpaired clock entry threshold, Dayforce considers the shift to have no out clock entry and marks it as a problem on the timesheet. The employee can’t record an out clock entry against this shift.
This also defines the number of hours that must elapse before an employee can clock in again after an unpaired in clock entry. Continuing the example above, if the employee clocked in again within the 14 hour threshold set by this setting, Dayforce marks the second in clock entry as a problem as well.
Unpaired Threshold should be set to a significantly large duration to cover any scenario that might arise where employees work late.
It also defines the number of hours that a shift override lasts. A shift override is a supervisor function performed on the Dayforce Touch Clock.
Note: When Dayforce makes comparisons for the unpaired threshold, it considers the in clock entry after any rounding rules have been applied and the raw clock entry time of the out clock entry.
Ignore Employee Rate for Unpaid Hours in Reports
Select the checkbox and Dayforce includes hours worked with a pay rate of zero when generating reports. Clear the checkbox and Dayforce includes hours with a pay rate of zero in reports only if the Include Unpaid Hours in Total checkbox is selected in the report options.
Auto delete balance transactions after employee termination
Sometimes administrators need to backdate an employee termination. For example, if there’s a lag between the time when an employee is terminated and the recording of the termination in Dayforce, and the lag spans several days or weeks, it’s possible that the employee could accrue entitlements during that time. When this checkbox is selected, Dayforce automatically deletes any balance transactions after an employee is terminated in the system. When cleared, Dayforce doesn’t delete any balance transactions after an employee’s termination. This property is disabled by default.
The following list details which entitlements are deleted and which aren’t:
- Balance transactions that belong to transmitted, closed, approved, or locked pay periods aren’t deleted.
- Transactions managed through Dayforce payroll via pay entries, awarded through payroll processing on pay out, or committed in payroll aren’t deleted.
- In open periods, only timesheet transactions after the last pay date are deleted when the Last Pay Date is specified in the employee’s HR record. Timesheet transactions before the last pay date aren’t deleted.
- Transactions manually added in the employee’s HR record aren’t deleted.
When this client property is enabled, the balance period is deleted only if:
- There are no balance transactions within the period.
- The balance period start date occurs on or after the termination date (that is, the balance period start date is greater than or equal to the termination date).
Note: This functionality has no effect on time away from work transactions, which are still removed automatically by Dayforce after employee termination regardless of the configuration of the Auto delete balance transactions after employee termination property.
Attendance Management Default Period Range (Months)
Enter the default period range that’s populated, by default, in the Period of fields of the Load panel in Attendance Management. By default, this field is set to 3 and Dayforce populates the Period of fields with a range of three months prior to the current date.
Important: Increasing the default value from 3 to a higher number might cause performance issues in Attendance Management.
Attendance Management Period Limit (Months)
Enter the maximum number of months in the past that users can load in Attendance Management. By default, this field is set to 18. For example, consider a user who is loading attendance data on 3/28/2022. With this default period limit configuration, the user can’t load attendance data for dates before 9/28/2020 because they exceed the 18-month period limit.
Important: Increasing the default value from 18 to a higher number might cause performance issues in Attendance Management.
Restart Attendance Points on
Select one or both options in this selection list to configure Dayforce to reset an employee’s number of accrued attendance incident points in some situations. You can configure Dayforce to reset incident point totals after employees are rehired or given a new attendance policy assignment. The options are: Attendance Policy Change and Rehire.
Use transactional data for attendance
By default, Dayforce examines employees’ pay summaries only when calculating absences. For example, if an instance of the Assign Pay Code Rule updates the pay code associated with an absence to a pay code that wasn't an exception (that is, the Is Exception checkbox wasn't selected in the pay code’s configuration), Dayforce doesn’t count the time associated with this pay code as an absence.
Conversely, with this checkbox selected, Dayforce examines an employee’s clock entries, pay adjustments, and transfers to calculate their absences. This means that the time in the example above would still be counted as an absence, even though it had been reassigned to a non-exception pay code.
Retry for X more times, if database result is a deadlock
Controls the number of times that Dayforce should retry saving a timesheet when the process fails due to a deadlock. For example, if you enter 3, Dayforce retries the save three more times. If the save still fails, Dayforce shows an error message indicating that the user should click Save again.
Enable period authorization
Controls the ability to use period authorization policies to automatically authorize all days in a pay period, while using an Unauthorization Rule to identify exceptions and unauthorize records based on a configured set of parameters. See Period Authorization Policies.
Enable real time calculations (HTML Timesheets)
Controls whether Dayforce shows the Enable real time calculations checkbox in the Options panel of Employee Timesheet and Timesheets. When you select the Enable real time calculations checkbox, Dayforce automatically recalculates the displayed data when you make changes to your timesheet. When you clear the checkbox, Dayforce shows the Recalculate button in the toolstrip:
When there are unsaved changes, Dayforce displays an icon () to indicate that the shown data isn’t up to date. When you click Recalculate, the data in the timesheet is updated and the icon is removed.
Note: Enable real time calculations isn’t available when using Dayforce in the Internet Explorer 8, Internet Explorer 9, or Opera Mini browsers.
Apply Higher Minimum Wage
When this client property is selected, Dayforce enables the following settings:
- The Age Start and Age End fields in Pay Setup > Minimum Wages.
- The Minimum Wage Effective Start On drop-down list in Pay Setup > Pay Policy. Use this drop-down list to specify when a minimum wage increase becomes effective when an employee moves to a new pay band based on their birthday. The drop-down list contains the following options:
- Birthday
- Start of Birthday Week
- Start of Week Following Birthday Week
- Start of Birthday Pay Period
- Start of Pay Period Following Birthday Pay Period
Time Review Max Count
Controls the maximum number of records that can be loaded in Time Review. Enter a number to limit the number of records that the feature shows. For example, to limit the number of records to 100, enter 100 in this field.
When users access Time Review and apply their predefined filters (for example, to view records needing authorization), and the number of records available exceeds the maximum specified in the client property, Dayforce shows a notification letting users know that more records exist. Then, when they finish authorizing records, they can rerun the filter to show more records.
Display Time Review Grid Lines
When enabled, Dayforce shows the Show Grid Lines checkbox in the Options dialog box in Time Review. When you select the Show Grid Lines checkbox, Dayforce shows grid lines between the columns for icons in Time Review.
Reject Time Entries If Pay Period Locked
With this checkbox selected, Dayforce rejects time entries if the pay period is locked.
Reject Time Entries If Pay Period Transmitted
With this checkbox selected, Dayforce rejects time entries if the pay period has already been transmitted.
Reject Employee Time Entry Imports For Locked Periods
When this checkbox is selected, Dayforce rejects time entry imports if the pay period is locked.
Engine past-dated calculation limit (months)
Defines the maximum number of prior months that Dayforce includes when it calculates changes using the attendance, base rate, entitlement, job step rate, and payroll engines. This client property also works in tandem with the WFM GDPR Compliance Check site-level background job, which tracks calculations and database requests made by WFM engines to ensure Dayforce meets data minimization settings configured for compliance with General Data Protection Regulation (GDPR) legislation. The default value is 999.
For example, if you enter 14 and initiate a pay summary recalculation for 24 months in the past, the recalculation won’t be performed for the period outside of the calculation limit (in this case, the first 10 months are excluded).
Important: If you configure the Engine past-dated calculation limit (months) client property with a value equal to or greater than 120 (or, 10 years), the background job fails to run and the job log contains an error message.
Additionally, when this client property is configured, a warning message appears in Employee Timesheet, Manager Timesheet, Time Review, and Timesheets when you load time and attendance records that fall outside of your configured past-dated calculation limit. For example, if you enter 2 and load a timesheet from three months in the past, the following warning message appears:
Records per page (Recommended range: 200 - maximum 500)
Controls the number of employee timesheet records that Dayforce shows per page in Timesheets. Specify the maximum number of employee records allowable per page. The recommended maximum value is 500, but you can enter a larger number. Note that a large number of records on a single page in Timesheets might affect performance in Dayforce.
When a user loads a location that contains a number of employees that’s larger than the Records per page value, Dayforce divides their timesheets across separate pages. Users can click the navigation buttons above the timesheets to load a different page:
Note: When pages are applied in Timesheets, some functionality becomes unavailable in the feature. See “Navigate Between Pages in Timesheets” in the Manager Guide.
Enable Auto Confirmation on Start and End Time
Select this checkbox and Dayforce automatically confirms shifts’ start and end times in the shift details dialog box in Timesheets. When selected, the green confirmation checkmarks don’t appear in the shift details dialog box. Instead, Dayforce shows arrow icons which you can use to adjust the start and end times:
Sum balance transactions by TransactionSource
Select this checkbox and Dayforce checks for the source of balance transactions when recalculating and showing updated approved and accrued totals in balance summaries. When this checkbox is selected, approved, and accrued balance totals are updated as follows:
- Dayforce decreases approved balance totals when a time away from work (TAFW) transaction is processed.
- Dayforce decreases approved balance totals and increases accrued balance totals when a TAFW period is canceled.
- Dayforce increases and decreases approved balance totals when the duration of an approved TAFW request is decreased and increased.
- Dayforce increases accrued balance totals as employees accrue balances through the entitlement accrual rules they’re assigned.
Pay Admin Checklist Records per page (2 - 500 per page)
Controls the number of pay group calendar records that Dayforce shows per page in Pay Admin Checklist. The recommended maximum value is 500, but larger numbers are supported. Note that showing a large number of records on a single page in Pay Admin Checklist might affect performance in Dayforce.
When a user loads a pay group that contains more pay group calendar records than the Pay Admin Checklist Records per page value, Dayforce divides the records across separate pages. Users can click the navigation buttons above the list to load a different page:
If you use filters, Dayforce also applies the filters to records on pages that aren’t loaded. However, if you make changes on one page, you must save them before you attempt to load a different page.
This client property also enables mass action functionality where users can edit multiple pay group calendar records, even those on pages that aren’t loaded. See “Edit Multiple Records (Mass Action)” in the Pay Approval Guide.
Pay Approve Checklist Records per page (2 - 500 per page)
Controls the number of location records that Dayforce shows per page in Pay Approve Checklist. The recommended maximum value is 500, but larger numbers are supported. Note that showing a large number of records on a single page in Pay Approve Checklist might affect performance in Dayforce.
When Pay Approve Checklist contains more locations than the Pay Approve Checklist Records per page value, Dayforce divides the records across separate pages. Users can click the navigation buttons above the list to load a different page. If you use filters, Dayforce also applies the filters to records on pages that aren’t loaded. If you make changes on one page, you must save them before you attempt to load a different page.
This client property also enables mass action functionality where users can edit multiple pay group calendar records, even those on pages that aren’t loaded. See “Edit Multiple Records (Mass Action)” in the Manager Guide.
Disable Validation For Job Step Overlap
Before You Begin: This client property is hidden and can only be enabled by contacting support. The client property isn’t selected by default so you only need to contact support if you don’t want validations for job step overlap.
Controls whether or not validation messages are shown when a duplicate record of a job rate is about to be created in Pay Setup > Job Rate in either the Job Rates or Job Step Policy tab. For example, if you try to add a job rate in the Job Rates tab that already exists in the Job Step Policy tab, a validation message shows in the Problems panel.
Additionally, the following configurations within job sets result in a validation message:
- Duplicate departments.
- Duplicate departments and jobs combined.
- Duplicate configuration with no department, but similar jobs selected.