Timesheet math fails for one specific reason: hours and minutes are base-60 pretending to be decimal. Add 7:45 and 8:30 like ordinary numbers and you get 15.75 of something meaningless; treat 7.45 hours as 7 hours 45 minutes and payroll quietly shorts someone 18 minutes. Both mistakes vanish once the two notations are kept apart, and this guide shows how, with our free hours calculator doing the base-60 bookkeeping.
In this guide
The base-60 problem in one example
Add 7:45 and 8:30. The minutes give 75, which is not a minutes value; it carries: 75 minutes is 1 hour 15. So the answer is 7 + 8 + 1 = 16 hours, 15 minutes: 16:15. That carry-at-60 is the entire difficulty, and it is exactly the carry-at-10 you already do, happening at a threshold calculators and spreadsheets do not apply to plain numbers. Type 7.45 + 8.30 into a normal calculator and it answers 15.75, an answer in no unit at all, because 0.45 of an hour was never 45 minutes. Every timesheet error traces back to this paragraph.
Clock time vs decimal hours
Two legitimate notations exist, and each is right for its job:
- Clock notation (7:45): hours and minutes, base-60, what schedules and time clocks speak.
- Decimal hours (7.75): minutes divided by 60, base-10, what multiplication speaks; payroll and billing live here.
The conversion is one division: 45 minutes is 45/60 = 0.75, so 7:45 = 7.75 hours. The trap runs the other way: 7.45 hours is 7:27, not 7:45, because 0.45 × 60 = 27 minutes. The lookalike pairs (.15 vs :09, .30 vs :18, .45 vs :27) are responsible for most quiet payroll discrepancies, and the time to decimal converter exists so nobody does that division under deadline.
Adding a real week of shifts
Monday through Friday: 8:15, 7:50, 8:05, 8:30, 7:40. Convert everything to minutes, add, convert back:
- 495 + 470 + 485 + 510 + 460 = 2,420 minutes
- 2,420 / 60 = 40 remainder 20 → 40:20
- As decimal for payroll: 2,420 / 60 = 40.33 hours
The everything-to-minutes route is the error-proof one, because it does all carrying in one place. The hours calculator runs this exact pipeline for any number of entries, both notations in, both notations out.
Payroll: where the decimal matters
Pay is rate × decimal hours, never rate × clock notation. The week above at $22/hour, computed from exact minutes: 2,420 / 60 × 22 = $887.33. Notice the small print hiding there: multiply the rounded display value instead, 40.33 × 22, and you get $887.26, seven cents adrift, which is exactly why payroll systems carry more decimals internally than they show. A single clean shift of 38:45 at the same rate is 38.75 × 22 = $852.50, no rounding gap because 45 minutes converts exactly. Two conventions are worth knowing rather than discovering. First, many payroll systems round time to the nearest quarter hour (0.25), and the rounding rules, per-shift or per-week, up or to-nearest, are policy choices that compound over a year. Second, overtime thresholds compare against decimal totals, so a 40:20 week is 40.33 hours, twenty decimal minutes into overtime territory, not “basically forty”. How an hourly total becomes annual income, with overtime and unpaid weeks handled honestly, continues in our salary conversion guide.
Overnight shifts and breaks
- Crossing midnight: a 22:00 to 06:00 shift is 8 hours, but naive subtraction gives −16. The fix is adding 24 hours to the end time before subtracting, which every decent tool does automatically; the bug appears in hand-built spreadsheets that subtract raw clock values.
- Unpaid breaks: subtract them in minutes, in the same all-minutes pipeline, not as decimal afterthoughts. A 30-minute lunch is exactly 0.5 hours; a 20-minute break is 0.33, and rounding it to 0.3 leaks two minutes per day, ten per week, a paid hour every six weeks.
- Multiple intervals: a split shift is just more rows in the same sum, which is why the calculator takes a list rather than a pair.
Frequently asked questions
Why do timesheets use minutes at all instead of decimals?
Because clocks do: people arrive at 8:50, not at 8.83. The clock side is for humans and scheduling, the decimal side for arithmetic, and a timesheet system is precisely the translation layer between them.
Is 0.1 hours six minutes exactly?
Yes: 0.1 × 60 = 6. The clean lookups are worth memorizing: 0.1 = 6 min, 0.25 = 15, 0.5 = 30, 0.75 = 45; everything else deserves the converter.
How do seconds fit in?
Same logic one level down: 60 seconds carry into a minute. Most payroll ignores seconds, but duration tools, like converting 93,784 seconds into 1 day 2:03:04, run the identical carry chain through the seconds level.
What about time zones on distributed teams’ timesheets?
Durations are zone-free: 8 hours worked is 8 hours in any zone. Zones only bite when start and end stamps come from different clocks, in which case normalize both to one zone (or UTC) before subtracting, then never think about it again.