Blog

Night audit payroll: which day the overnight shift lands on

· overtime, scheduling, payroll

A night audit shift running 22:00 to 06:00 belongs to two calendar days, and something has to decide which one gets the hours. The answer that keeps payroll honest is the day the shift started — one shift, one day, eight hours in one place. Many systems cut the shift at midnight into a two-hour day and a six-hour day — in some it is the out-of-the-box setting, in others it is off by default, and in most it is a setting somebody chose once and nobody has looked at since, and that single decision is how a small hotel’s overnight overtime goes missing with nothing on the timesheet looking wrong.

Where the night audit breaks the arithmetic

Take an invented 72-room exterior-corridor property off an interstate. One night auditor covers the desk from 22:00 to 06:00, and the property designates its workweek Sunday 00:00 to Saturday midnight — the fixed, recurring window overtime is actually measured against. Yours may start on a Monday; what matters is that it is fixed and that you know which day it is.

One Tuesday night, the morning desk agent calls out, so the auditor stays until 08:00. That is a ten-hour shift. Here is what two systems record for the same ten hours:

TuesdayWednesday
Shift credited to the day it started10.0 h0 h
Shift cut at midnight2.0 h8.0 h

Both rows total ten hours. Both reconcile against the week. Only one of them contains a long day.

That matters immediately in a state with a daily overtime threshold. Several have one and the details differ — our rundown of daily overtime rules by state is the place to check which, and your own state’s rule is the one that governs you. Under a daily-eight rule, that ten-hour night earned two hours at time-and-a-half. Cut at midnight it becomes a two-hour day and an eight-hour day, neither past eight, so no premium is ever computed on it. At $17 an hour the premium that disappears is $17 — small enough never to be queried, and it recurs every time somebody covers a morning.

What the midnight cut does to the workweek, in every state

The daily case needs a state rule. The weekly case does not, because every workweek is measured on its own and the midnight cut moves hours across the boundary between two of them.

Same property, a week where the auditor covers six nights instead of the usual four — Monday through Saturday, eight hours each, 48 hours actually worked. The week before was a Monday-to-Thursday pattern, so nothing carried in over the Sunday boundary:

Hours in the Sunday–Saturday weekOvertime
Credited to the day each shift started48.0 h8.0 h
Cut at midnight42.0 h2.0 h

The Saturday-night shift starts at 22:00 Saturday and ends at 06:00 Sunday. Cut at midnight, six of its eight hours land in the following workweek — a week that opens at six hours and will never come close to forty. So six hours that were earned past the fortieth get paid straight: at $17 an hour that is $51 of premium, in one week, at one property, with nothing on any report to point at.

This is hard to spot because in a steady week it cancels: if the auditor works the same nights every week, six hours leave at one end and six arrive at the other, and the totals look right indefinitely. The error only surfaces in the week that actually had overtime in it — precisely the week you needed to be right.

The three answers a time system can give

There are only three, and you are entitled to know which one you have bought.

  1. Cut the shift at midnight. Two entries, two dates, two short days. This is a common default and in some systems the shipped one, and it is the one that produces both numbers above.
  2. Credit the whole shift to the day it ended. One shift, one line, which is better. But “yesterday’s labor” now includes hours worked before yesterday began, so every per-day figure you read in the morning reports a day that hadn’t started yet.
  3. Credit the whole shift to the day it started. One shift, one line, on the day the work began. This is the one that matches how the property already talks: nobody at a front desk calls 03:00 Wednesday anything other than Tuesday night.

Being honest about where this is contested: option 1 is not simply wrong everywhere. Where a jurisdiction’s daily rule is written around a 24-hour workday beginning at midnight, splitting at the boundary is an argument somebody can make — a question for your own state’s rule and your payroll provider rather than for a blog post. What is not contested is that you should have one rule, applied the same way every week, and be able to say what it is.

If you want to see which rule your own hours are sitting under before the next payroll run, start a free trial and look at one week of overnights.

The check to run on one week of your own punches

This needs nothing but your own time system and one week of punches.

  1. Find one overnight shift in the last fortnight — any punch pair that crossed midnight.
  2. Pull up the date the shift started. If the shift’s full length is there, you are on option 3. If only the hours before midnight are there, you are on option 1. If the day shows nothing and the following day shows everything, you are on option 2.
  3. Find the week boundary. Look at the shift that starts on the last evening of your workweek. Check whether its hours all landed in that week, or whether some of them opened the next one.
  4. Check the longest night of the month — the one where somebody covered a call-out. Work out the overtime by hand and compare it against what the system computed. This is the case where a wrong grouping turns into a wrong cheque.

Step 4 is the one worth doing properly, because it is the only one that produces a number. A daily labor report read the morning after a long night is where the discrepancy shows, and that morning is the last point at which it is cheap to fix.

The schedule gets this wrong too, and earlier

The grouping problem has a twin on the scheduling side, and it bites before anyone has clocked in at all.

A schedule that stores a start time and an end time has to work out that 22:00 to 06:00 is eight hours. Subtract one from the other naively and you get minus sixteen — which some systems reject as invalid, so the night audit cannot be scheduled at all, and others store, so the shift reads as negative hours in every total that touches it. The same blind spot hides collisions: a 22:00–06:00 Monday shift and an 04:00–12:00 Tuesday shift overlap by two hours while sharing no date, so a check that compares within a single day will cheerfully double-book one person.

ProfitClock is built on the third answer above. An overnight shift is one shift, dated to the day it starts, measured so its length is eight hours rather than minus sixteen, and checked for overlap across the midnight boundary rather than inside one date. Every per-day figure — punches, overtime thresholds, the daily labor flash — reads the day as the property’s own, which is the same rule that governs whether your time clock computes overtime on the right day at all.

Where this doesn’t apply

If nobody at your property works past midnight, none of this is your problem, and some small hotels genuinely close the desk overnight.

It is also worth saying what fixing the grouping does not fix. It will not recover a night the auditor forgot to clock out of — a missing punch needs an edit with a reason attached, not a better day boundary. And it will not settle which jurisdiction’s daily rule applies to you, which no software can answer and which changes.

What it does settle is the thing that should never be in doubt: the eight hours somebody worked between Tuesday night and Wednesday morning are eight hours, on one day, in one place, every week — including the week it finally mattered.

Start seeing what labor actually costs

Set up your property, put staff on the clock, and read tomorrow morning’s labor number.

14-day free trial · No credit card · Cancel anytime