Payroll Hours vs Clocked Hours in a Timesheet
· 5 min read
You have a server who tapped in at 4:58 PM, took a 30 minute unpaid dinner break, and tapped out at 10:04 PM. The raw record says 5 hours 6 minutes. The number you pay on is 4 hours 36 minutes. Those are two different quantities, and if you put the wrong one in the timesheet row you either overpay or shortchange someone.
Payroll hours are the hours an employer actually pays a worker for in a given period, after unpaid breaks are removed and any corrections are applied. Clocked hours are the raw span between a clock-in and a clock-out, before anything is subtracted. The two are often close, but they are not the same number, and the timesheet row that feeds your pay run wants the payroll number.
Where the two numbers split apart
If nobody takes a break and nobody forgets to clock out, clocked hours and payroll hours match. That is the easy case. The gap opens up in a handful of ordinary situations:
- Unpaid breaks. A 30 minute lunch that you do not pay for comes out of the clocked total. Five clocked hours becomes four and a half payroll hours.
- Forgotten clock-outs. A volunteer leaves at noon and never taps out. The raw record keeps running, so the clocked span is wrong and the payroll number built from it would be inflated.
- Rounding and corrections. If you round to the nearest quarter hour, or you fix an entry a worker got wrong, the payroll figure moves away from the raw one.
- Overtime splits. The same clocked hours can map to regular and overtime payroll hours at different rates, which matters once someone crosses 40 in a week.
For a server on a split shift the unpaid break is usually the whole story. For an event crew the bigger risk is the forgotten tap-out, because people scatter the moment teardown ends.
Which number goes in the timesheet row
The pay column of a timesheet holds payroll hours, not clocked hours. The clocked times are the evidence behind that number: the 4:58 in and the 10:04 out tell you where 4 hours 36 minutes came from, and you keep them so the figure is checkable later.
A clean timesheet row usually shows both. The in time and out time sit on the left as the record. The payroll hours sit on the right as the thing you pay. If you only keep the final number and throw away the raw times, you cannot answer a question when someone disputes their hours three weeks later. If you keep the first tap of a shift and the tap that ends it but never derive the payroll figure, you have not finished the timesheet. You need both.
When you build the row by hand, the order is: take the clocked span, subtract unpaid break minutes, apply any rounding rule you use, then split into regular and overtime if the week runs long. A quick way to add up shift times handles the arithmetic so you are not doing it on a legal pad.
How forgotten clock-outs poison the payroll number
The quiet danger is the open entry nobody closed. If a raw record runs from a 9 AM clock-in to right now because someone forgot to tap out, any payroll number you build from it is garbage, and it is garbage in the direction that costs you money.
Kangaroo Clock handles this with a cutoff that closes stale entries. A forgotten clock-out is closed at its start time plus your cutoff, never at the current time. So a volunteer who ghosted the kiosk at noon does not show up with fourteen hours on the board at midnight. The clocked span stays sane, which keeps the payroll hours you derive from it sane too.
Decimal or HH:MM, and why it matters
Payroll hours show up in two formats and they are not interchangeable without a conversion. HH:MM is how the clock reads: 4:36 means four hours and thirty-six minutes. Decimal is what most pay math wants: 4.6 hours, because thirty-six minutes is six tenths of an hour. Writing 4.36 when you meant 4:36 is a common and expensive mistake, because 36 minutes is 0.6 of an hour, not 0.36.
If you multiply by an hourly rate, you want the decimal form. A converter for decimal and HH:MM saves you from doing that translation in your head across a whole roster. For a reusable grid you can print and fill by hand, a blank timesheet you can print keeps the columns in the right order.
Getting payroll hours out without the arithmetic
Kangaroo Clock records every clock-in and clock-out, applies the auto-close cutoff, and exports a CSV with a stable column schema that does not break between runs. The export includes a distinct-worker count, which matters for grant reporting where you report both hours and headcount. You take that file to whatever actually pays people.
One boundary to be clear about: Kangaroo Clock is not a payroll processor. It does not move or hold money and it does not cut checks. It gives you the clocked record and the hours, in a file your payroll system or your accountant can read. For the exact definition and a few edge cases, the payroll hours glossary entry lays it out plainly.
Next step: pull a week of real shifts, subtract the unpaid breaks, and see whether your clocked total and your payroll total actually agree. If they drift, you now know exactly which of the four reasons is doing it.
Tags: payroll, timesheets, time tracking, terminology
See it in your own setup
No signup needed. Add a few names, share a kiosk URL, watch hours land.