What a hotel bookkeeper needs at payroll period close
· payroll, recordkeeping, overtime
At period close your bookkeeper needs six things, and only six: a punch file with nothing still open, the period boundary expressed in the property’s own days, the workweek you designated, hours already split the way payroll pays them, any rate change with its effective date, and one line saying what you reconciled. Send those and close happens once. Send a raw hours dump and it happens twice — now, and again in three days when the corrections arrive.
The bookkeeper’s problem is ambiguity, not absence
Most properties do send the hours. The back-and-forth that follows is almost never about missing data; it is about data that could mean two things. Is this 82-hour total two workweeks or one pay period? Did the night audit shift that started Saturday land in this period or the next? Is the 6.5 on the 14th a short shift, or a forgotten clock-out an approver guessed at?
Each has a defensible answer, and the bookkeeper cannot pick it. So they ask and wait, or they assume — and an assumption that produces a plausible number is the one nobody finds.
1. A punch file with nothing still open
Every shift has a start and an end. Every edited punch has been approved before the file was generated rather than after. Every exception — the missing clock-out, the thirteen-hour shift at a property that never schedules past 9pm — is resolved, not flagged.
Resolved means someone decided, and the record says who and when. Any time-keeping system worth using keeps an append-only history of punch edits, so the original time, the corrected time and both names survive. That history is not really for the bookkeeper. It is for the same conversation eleven months later, when somebody disputes a paycheck and everyone’s memory is a reconstruction.
The daily habit is what makes this cheap. Resolving exceptions the same morning turns period close into a formality; saving them up turns it into two hours of archaeology on the day you have least time.
2. The period boundary in the property’s own days
This is the item most likely to be wrong and least likely to be noticed.
A night auditor clocks in at 10:45 pm on the last day of the pay period and out at 6:55 am the next morning — 8.17 hours. Which period is it in? The answer does not have to be a particular one; it has to be stated and applied the same way every close. Most properties attribute the shift to the day it started, which puts all 8.17 hours in the closing period.
What breaks it is a system that dates punches in UTC rather than at the property. A 10:45 pm clock-in at a US Central-time property is already tomorrow in UTC, so the whole shift files itself into the next period — and into the next workweek, which is the part that costs money. The same defect splits an overnight workday across two calendar days, and each half can sit under a daily overtime threshold the real shift cleared. A punch dated on the wrong day is not a formatting problem; it is a pay calculation running on the wrong inputs.
Worth checking once: pull the last shift of a period and confirm its date matches the date the person worked it. If it does, you never have to think about this again.
3. The workweek you designated, in writing
Overtime is figured per workweek, not per pay period. Under the federal rule (29 U.S.C. §207(a)) covered non-exempt employees earn overtime past 40 hours in a workweek, and several states add a daily threshold on top — which states, and what they require, varies and changes, so check your own rather than assuming the federal one is all that applies.
A biweekly period contains two workweeks, and the total tells you nothing about either. An invented front desk agent at a 52-room independent, workweek designated Sunday through Saturday:
| Sun | Mon | Tue | Wed | Thu | Fri | Sat | Week total | |
|---|---|---|---|---|---|---|---|---|
| Week 1 | 8.0 | 8.5 | 8.0 | 8.0 | 8.0 | 3.5 | — | 44.0 |
| Week 2 | 8.0 | 8.0 | — | 7.5 | 8.0 | 6.5 | — | 38.0 |
Eighty-two hours across the period. Read per workweek, that is 4.0 overtime hours — all of them in week 1, none in week 2, because the 38-hour week does not borrow from the 44-hour one. Read as a period total, 82 against 80 gives 2.0.
Both numbers pay all 82 hours. The difference is the premium on two of them: at a placeholder $17 an hour the half-time premium is $8.50, so the period-total method underpays that person by $17. It is small, it recurs every period the two weeks are uneven, and it never announces itself, because 82 hours is correct and only the split is wrong. The conclusion holds at any threshold and any premium rate — a period total cannot produce a workweek answer.
Getting the boundary and the split right before the file leaves the property is most of this job. ProfitClock dates every punch on the property’s own calendar day and hands out a payroll-ready export — see how the time and attendance side works, or start a free trial and close one period against your own punches.
4. Hours already split the way payroll pays them
Regular hours, overtime hours, and any additional premium category the property actually uses, per employee, per workweek. Not a single hours column with a note attached.
The split cannot be reconstructed downstream. Given 82 flat hours, nobody outside the property can recover which days they fell on, which workweek each belonged to, or whether a 13-hour Tuesday crossed a daily threshold. Those answers live in the punch data, and the punch data is at the property. Sending the total and expecting the split back asks someone to invert an operation that destroyed its own inputs.
5. Rate changes, with effective dates
A mid-period raise is the other quiet one. If someone moved from $16.00 to $17.25 on the ninth day of a fourteen-day period, the file needs the rate and the date it started — the hours on either side are paid differently, and if any are overtime hours, the regular rate the premium is calculated on moves too. A change sent as “she’s on $17.25 now” gets applied to the whole period, which is wrong in one direction or the other and is exactly the error the employee finds first. Same treatment for a new hire, a termination, and anyone who worked two jobs at two rates.
6. One line saying what you reconciled
Not a report. A sentence: “14 days, 9 employees, 61 shifts, 0 open exceptions, 2 approved punch edits, one rate change on the 9th.”
It takes thirty seconds and does two things: it tells the bookkeeper the file is final rather than a draft to hold, and it gives both of you a number to check later. If the payroll register comes back with 58 shifts, someone knows immediately rather than at the next audit.
What not to send
The schedule — it is what you planned, where the time record is what happened, and payroll is owed the second one. A PDF, which will be retyped, and retyping is where digits get transposed. And a preliminary file “to get started” — there is no such thing; it will be processed, and the corrections will arrive after the run.
Where this is genuinely hard
Some of it does not reduce to a checklist.
A period that ends mid-shift. You are choosing between splitting one shift across two periods and attributing all of it to one. Both are defensible; only one can be your standing rule, and switching between them is what causes trouble.
Multiple rates for one person. A front desk agent who also covers maintenance at a different rate makes the overtime premium materially harder, and the right method depends on how you agreed to pay them. A question for an accountant, not a blog post.
Very small properties. At three hourly staff the owner often is the bookkeeper. The list still helps, as a monthly self-check rather than a package — the value is in having answered the questions once, not in the sending.
Nothing here is legal advice, and wage-and-hour rules differ by state and change; your own state’s labor department and your accountant are the authorities on what applies to your property.
The checklist
- Punch file closed — no open shifts, edits approved, exceptions resolved.
- Period boundary in the property’s calendar days, overnight-shift rule written down.
- Workweek definition included.
- Hours split into regular, overtime and any premium — per employee, per workweek.
- Rate changes with effective dates; new hires and leavers noted.
- One reconciliation line: days, people, shifts, exceptions, edits, changes.
Six items, one file, sent once.
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