Dayforce time and attendance configuration sits at the intersection of HR policy, payroll calculation, and labor law compliance — which means every misconfiguration has three places it can cause problems. Most mid-market implementations configure the basics well enough to get through go-live, then spend the next year dealing with overtime calculation errors, shift differential disputes, and accrual discrepancies that trace back to design decisions made without understanding their downstream effects. This guide covers Dayforce time and attendance configuration in the depth that prevents those problems: how work rules actually work, where compliance exposure hides in punch rounding, how shift differentials are calculated, and where accruals go wrong.
Work rule setup: the four components
Work rules are the core configuration object in Dayforce T&A. Every time entry is processed through a work rule, which determines how punches are interpreted and what pay codes result. A work rule has four interdependent components: Pay Policy, Shift, Schedule, and Work Assignment. Getting any one of them wrong affects how hours are classified and how pay is calculated.
Pay Policy
The Pay Policy defines the overtime calculation rules that apply to an employee — daily overtime thresholds, weekly overtime thresholds, and the sequence in which premium calculations are applied. In California, daily overtime applies after 8 hours (1.5x) and after 12 hours (2x), and seventh-day overtime rules apply independently of the weekly total. Outside California, most employers apply only the federal 40-hour weekly threshold.
A Pay Policy is not "one per state." It's one per combination of overtime rules, and there are more combinations than most HR teams realize: salaried non-exempt employees may have different overtime thresholds than hourly non-exempt, union employees may have collectively bargained overtime rules that differ from statutory, and employees who work in multiple states within a week need Pay Policies that handle multi-state overtime correctly. Document every distinct combination of overtime rules before building Pay Policies.
Shift
The Shift component defines the expected start and end time for a work period, the grace period before a punch is considered late or early, and the paid/unpaid status of meal breaks. Shift configuration is where the punch rounding rules live — see the next section for why this is your highest compliance risk in T&A.
One important detail: the Shift component does not drive scheduling. It defines the template that punch rounding and exception alerting reference. Actual schedule assignments happen through the Schedule component. If your Shift and Schedule are out of sync — different start times, different break durations — exception reports will generate false alerts and real alerts will be buried in noise.
Schedule
The Schedule component defines the actual expected work pattern for an employee: which days they work, what hours they're expected to start and end, and how their expected weekly hours are distributed. The Schedule drives absence detection (if someone is expected at 8am and doesn't punch, the system generates an unplanned absence), overtime projections, and schedule-based shift differential triggers.
For organizations with variable scheduling, the Schedule component is the most complex to maintain. Variable schedules require either manual schedule input each period or integration with a scheduling system that pushes schedule data to Dayforce ahead of each work week. Implementations that don't plan for variable schedule maintenance end up with schedules that don't match reality — which makes every exception report meaningless.
Work Assignment
The Work Assignment links an employee to a specific work rule combination, effective-dated to when it applies. An employee who moves from a day shift to a night shift needs a new Work Assignment effective-dated to the start of the new shift — not a change to the underlying Shift or Pay Policy objects, which might be shared with hundreds of other employees.
Need hands-on help with Dayforce?
Talk to our team →The most common Work Assignment mistake in mid-market implementations: treating Work Assignment as a one-time setup rather than an ongoing maintenance process. Every time an employee's overtime rules, schedule, or shift differential eligibility changes, their Work Assignment needs to be updated. If that maintenance process isn't defined and owned, Work Assignments drift from reality within six months of go-live.
Punch rounding vs. actual time: the compliance risk most companies miss
Punch rounding is one of the most consequential T&A configuration decisions, and it's the one that generates wage and hour liability when it's configured incorrectly or without documented policy basis.
Dayforce supports several rounding approaches:
-
Nearest increment rounding: Punches are rounded to the nearest defined interval (5, 6, 10, or 15 minutes). A punch at 8:07 on a 15-minute rounding schedule rounds to 8:00; a punch at 8:08 rounds to 8:15.
-
Schedule-based rounding: Punches within a defined window of the scheduled start or end time are rounded to the scheduled time. Punches outside the window are recorded as actual time.
-
Actual time (no rounding): Every punch is recorded at the exact clock time.
The legal requirement for any rounding approach is that it must be neutral over time — it cannot systematically round in the employer's favor. The Department of Labor's standard is that rounding is permissible if, over time, it averages out to actual hours worked. If your rounding approach consistently rounds start-of-day punches down (in employer's favor) and end-of-day punches up (also in employer's favor), it's not neutral, and it's wage theft under the FLSA regardless of whether it's unintentional.
The safer approach for most mid-market employers: schedule-based rounding with a tight window (5 minutes either side), and actual time for any punch outside the window. This captures the operational benefit (timesheets aren't fragmented by 2-minute early punches) without the neutrality risk of nearest-increment rounding applied across all punches.
Whatever rounding approach you configure, document it and confirm with employment counsel that it's compliant in every state where you have employees. California restricts punch rounding more than federal law — if you have California employees and a rounding configuration that was designed for a non-California workforce, you have a compliance gap.
Rounding configurations set at go-live are rarely reviewed post-launch Most T&A rounding configurations are set during implementation and never revisited. But if your workforce has changed — new states, new shift patterns, hourly workers added to a previously salaried population — the rounding rules that were compliant for your original setup may not be compliant for your current setup. If your Dayforce T&A configuration is more than 18 months old and your workforce has materially changed, a rounding compliance review is worth doing before someone else asks you to do it. Contact us if you want a second opinion.
Shift differential configuration and the order-of-operations problem
Struggling with Dayforce Consulting?
Harmon & Co specializes in Dayforce consulting for mid-market companies. We fix it the first time — no endless ticket queue, no generic advice.
