Daylight Saving Time Payroll: Pay Overnight Shifts Right

Daylight saving time payroll comes down to one rule: pay the hours actually worked, not the hours scheduled. The fall-back night runs 25 hours, so a scheduled 8-hour overnight shift is really 9, and all 9 are owed. The spring-forward night runs 23 hours, so that same shift is really 7, and 7 is all you owe.

The next changeover is 2 a.m. on Sunday, November 1, 2026, then 2 a.m. on Sunday, March 14, 2027. Both dates come straight from 15 U.S.C. 260a, which sets daylight saving time to begin "at 2 o'clock antemeridian on the second Sunday of March of each year" and end "at 2 o'clock antemeridian on the first Sunday of November." That timing is why this is a payroll problem at all: 2 a.m. lands in the middle of nearly every overnight shift in the country.

How does daylight saving time payroll work under federal law?

There is no daylight saving time provision in the Fair Labor Standards Act. There does not need to be. The FLSA pays for time worked, and both changeovers are just an unusual number of worked hours. The daylight saving time payroll rules are the ordinary ones, and the daylight saving time payroll requirements fit in a sentence: pay for the hours worked, and keep a record that shows them.

29 CFR 785.11 is the operative regulation: "Work not requested but suffered or permitted is work time." Nobody asked the overnight tech to live through the 1 a.m. hour twice, but they did, they were on duty, and the employer knew. That hour is compensable. Running the other direction, an hour the clock deleted is an hour nobody worked, and 29 U.S.C. 207 counts hours worked toward the 40-hour overtime threshold, not hours a schedule predicted.

Your records have to reflect the real number too. 29 CFR 516.2 requires "hours worked each workday and total hours worked each workweek" for every non-exempt employee. A timesheet showing a flat 8 on a night that ran 9 is a defective record even if you happened to pay the right amount.

Worth saying out loud: if nobody is on the clock at 2 a.m. that Sunday, none of this applies to you. A shift that starts at 9 a.m. Sunday still starts at 9 a.m. and still runs its normal length, because the clock finished changing hours earlier. The people affected are the ones physically working across the changeover. In practice that is night-shift nursing and assisted living, security and dispatch, hotel front desks, 24-hour manufacturing and distribution, long-haul and delivery, convenience stores, and casinos. Everyone else can skip to their normal payroll run.

Fall back: the 25 hour night and the 9 hour shift

Take an employee scheduled 11 p.m. to 7 a.m. on Saturday, October 31, 2026 into Sunday, November 1. They work 11 p.m. to 2 a.m., which is 3 hours. The clock rolls back to 1 a.m. They work 1 a.m. to 7 a.m., which is 6 hours. Total: 9 hours worked. Not optional, not a policy choice. All 9 get paid.

At $18 an hour, that shift alone pays $162 instead of $144 if the week stays under 40 hours. The interesting case is the employee who was already going to hit 40. Five overnight shifts of 8 hours is 40 hours; make one of them 9 and the week is 41, and hour 41 is overtime at one and one-half times the regular rate under 29 U.S.C. 207(a)(1). The week pays 40 x $18 plus 1 x $27, which is $747 instead of $720.

Fall back overnight shift pay and overtime

Fall back overnight shift pay is simple once the hour count is right: 9 worked, 9 paid. Daylight saving time overtime only enters when those 9 hours push the week past 40. Is overtime pay time and a half in that case? Federally it always is, so you pay time and a half on hour 41 and payroll overtime for the week is computed exactly the way it would be in any other week. Nobody needs a special definition of what is overtime pay on this night, because the changeover creates hours, not rules.

Run the part-time version too, because it is the more common one. A weekend-only employee who works two 8-hour overnight shifts is at 17 hours for the week after the fall change, nowhere near 40, so the extra hour is straight time: 17 x $18 is $306. No premium, no drama, but still a paid hour that a wall-clock timesheet would have swallowed.

Budget it as a crew number, not a per-person number. Six overnight employees at $18 who each cross 40 that week costs an extra $162 for the night. That is small, and it is also the exact kind of small that nobody accrues for and everybody argues about after the fact.

Spring forward: the 23 hour night and the 7 hour shift

Same schedule on Saturday, March 13, 2027 into Sunday, March 14. The employee works 11 p.m. to 2 a.m., the clock jumps to 3 a.m., and they work 3 a.m. to 7 a.m. Three hours plus four is 7 hours worked against an 8-hour schedule. Federal law requires pay for 7.

Plenty of employers pay the full 8 anyway, for morale or because a collective bargaining agreement or handbook says so. That is allowed. One consequence to get right: an hour paid but not worked does not count toward overtime. 29 CFR 778.218 deals with pay for occasional idle periods and states plainly that "no part of such payments may be credited toward overtime compensation due under the Act." So if you gift the 8th hour, the employee's hours-worked total for the week is still 39, and the gifted hour does not push anyone into overtime.

Keep the two numbers separate on the spring forward payroll run: hours worked (7) and hours paid (8). Merging them is how a generous policy turns into a broken record.

Punch rounding adds a wrinkle if you use it. A rule that rounds to the nearest quarter hour operates on the punch times, and the punch times are still real: 11:00 p.m. and 7:00 a.m. do not move. What changes is the elapsed time between them, which rounding does not touch. So rounding neither creates nor destroys the changeover hour. If your totals come out 8 on a spring-forward night, the problem is the duration calculation, not the rounding rule.

Which workweek absorbs the extra hour?

Depends entirely on where your workweek starts, and most employers have never written it down. 29 CFR 778.105 defines a workweek as "a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods," and it "need not coincide with the calendar week but may begin on any day and at any hour of the day."

• Workweek starts Sunday at 12:00 a.m. The repeated 1 a.m. to 2 a.m. hour falls on Sunday, so it lands in the new workweek. Your Saturday-ending week is normal and the following week carries the extra hour.
• Workweek starts Monday at 12:00 a.m. That Sunday overnight belongs to the week that is about to close, so the extra hour pushes that week's total.
• Workweek starts mid-shift, say Sunday at 6:00 a.m. Now a single overnight shift splits across two workweeks. Legal, but check which side the extra hour falls on before you approve the timesheet.

You also cannot net the two changeovers against each other. 29 CFR 778.104 says the Act "takes a single workweek as its standard and does not permit averaging of hours over 2 or more weeks." The lost spring hour and the gained fall hour sit about 34 workweeks apart. Each week stands alone.

Where time clocks get it wrong

The failure mode is boring and expensive. A system that stores wall-clock time and subtracts start from end computes 11 p.m. to 7 a.m. as 8 hours every night of the year. That overpays by an hour in spring, which is only a cost problem, and underpays by an hour in fall, which is a wage violation.

Clock behavior	Spring forward result	Fall back result
Stores wall-clock time, no time zone	Shows 8 h, actual 7 h (overpays)	Shows 8 h, actual 9 h (underpays)
Stores UTC, converts for display	Shows 7 h, correct	Shows 9 h, correct
Paper timesheet with written times	Whatever the employee wrote	Whatever the employee wrote

Test yours instead of trusting the marketing page. Punch a test employee in before 2 a.m. and out after on the changeover night, or set the device clock forward and run the pair. If the duration comes out 7 in March and 9 in November, the system stores absolute time and you can stop worrying about it twice a year. If you run a small overnight crew, the manual alternative is fine: pull every overnight punch pair from the changeover weekend and check the durations by hand. With one crew that is a five-minute job. Our time card calculator will do the arithmetic on any pair of times you feed it, and Kloqk's free time clock stores punches as absolute timestamps so the durations come out right without an override.

Salaried staff, shift differentials, and the regular rate

Exempt salaried employees are unaffected. 29 CFR 541.602(a) requires that "an exempt employee must receive the full salary for any week in which the employee performs any work without regard to the number of days or hours worked." A 23-hour Sunday does not shrink anyone's salary and a 25-hour Sunday does not enlarge it. Do not create a deduction or a bonus to reflect the clock change.

Non-exempt staff who earn a night differential need one more step. Under 29 CFR 778.207(b), the FLSA "requires the inclusion in the regular rate of such extra premiums as nightshift differentials (whether they take the form of a percent of the base rate or an addition of so many cents per hour)." So a $2 night differential on top of a $18 base makes the regular rate $20 for those hours, and overtime on the fall-back hour is computed from the blended regular rate, not from $18. Our overtime calculation guide works through the blended-rate math, and the state overtime guides cover states with daily overtime rules that change the answer again.

Arizona, Hawaii, and multi-state crews

Not every worker changes clocks. 15 U.S.C. 260a(a) lets "any State that lies entirely within one time zone" exempt itself from the advancement of time, so long as the entire state observes standard time. Arizona took that option: A.R.S. 1-242 says the state "elects to reject such time and elects to continue in force" its standard time. Hawaii uses the same opt-out.

For a company with staff in several states, that means the March and November weekends produce different worked-hour totals depending on where the employee is standing. A Phoenix dispatcher and a Denver dispatcher on the same overnight shift work different numbers of hours that night. Wall-clock math cannot see the difference. Time-zone-aware time tracking can.

How to pay overnight shift during time change, step by step

Daylight saving time payroll for small business owners is a data problem more than a legal one. The law is two sentences. The work is making sure the number that reaches payroll is 9 and not 8, which means verifying durations before you submit rather than after someone questions a check.

There is no such thing as daylight saving time payroll software, and no daylight saving time payroll app either. What exists is a time and attendance system that stores absolute timestamps and one that stores wall-clock text, and the difference between them shows up twice a year. Check which one you have before November rather than during it.

How do I run payroll from timesheets that week? The same way as any week, once the overnight durations are verified. Time tracking with payroll export removes the retyping step entirely, so approved hours land in Gusto payroll, ADP, or QuickBooks in the format each one expects. How do I get employee hours into QuickBooks is the version of that question we hear most often, and the answer is an export file rather than a keyboard. What time clock works with QuickBooks payroll matters less than whether the punch was stored correctly to begin with: time clock software for QuickBooks that computes 8 hours on a 9 hour night only delivers a wrong number faster.

Two housekeeping notes. The extra hour flows into payroll and payroll taxes like any other wage, so there is no special payroll tax treatment to look up. And biweekly pay periods change nothing about the analysis, because overtime is figured per workweek: find the workweek holding 2 a.m. Sunday and total that week on its own. A payroll hours calculator is plenty for checking a handful of overnight pairs, which makes daylight saving time payroll for employees on a single night crew a five minute job if you do it before the run.

Write the policy before payroll week

Two sentences in the handbook, decided in advance, applied to everyone.

1. Fall. "Employees on duty during the fall daylight saving change are paid for all hours actually worked, including the repeated hour." There is no second option here. This is the law.
2. Spring. Pick one: "paid for actual hours worked" or "paid for the full scheduled shift." Either is lawful. What is not defensible is paying the warehouse crew scheduled hours and the security crew actual hours on the same night.

Then run the changeover weekend as a short checklist:

• Confirm which workweek contains the 2 a.m. Sunday changeover.
• Pull every overnight punch pair from that weekend and verify durations show 9 in November and 7 in March.
• Recalculate weekly totals for anyone near 40 and flag the ones that crossed.
• Tell your payroll processor which spring policy you are on before you submit.
• Keep the corrected hours in the record, not just in the pay run.

Most daylight saving time payroll errors are caught in that fourth step or never caught at all. Twenty minutes twice a year is the whole cost of getting it right, which is a good trade against a wage claim built on a system that quietly recorded 8 hours on a 9-hour night.

This is general information for 2026, not legal advice. Some states add rules that interact with shift pay, and a collective bargaining agreement can require more than the FLSA does. Confirm specifics with your state labor department and the current text of 29 U.S.C. 207 before you set policy.