Why timesheet math breaks in the real world
Payroll systems want decimal hours. Humans speak in hours and minutes. The gap between ‘7:45’ and ‘7.45’ is where overpayments, underpayments, and heated Slack threads are born. Seven hours and forty-five minutes is 7.75 hours, not 7.45. That single misreading on a daily timesheet becomes a sizable error across a team and a year.
Rounding rules, break deductions, shift differentials, and overtime thresholds add more ways to drift. Two honest people can compute different payable hours from the same punches if they disagree about whether to round to the nearest quarter hour or to convert exact minutes.
This article walks through conversions, common traps, and a reconciliation habit you can use whether you approve timesheets or submit them. It is educational operations math—not legal advice about wage-and-hour rules in your jurisdiction. When policy and local law conflict with a shortcut, policy and law win.
Minutes to decimal: the only formula you need
Decimal hours = hours + (minutes ÷ 60). Example: 7 hours 45 minutes → 7 + (45 ÷ 60) = 7.75. Example: 8 hours 6 minutes → 8 + (6 ÷ 60) = 8.10. Example: 0 hours 90 minutes should first be normalized to 1 hour 30 minutes → 1.50, or converted directly as 90 ÷ 60 = 1.50.
Never treat the minutes field as a hundredths field. ‘7:30’ is half an hour (7.50), not 7.30. ‘7:15’ is 7.25. ‘7:20’ is 7.333… which many systems round to 7.33 or to the nearest approved increment.
Going the other way: take the decimal fraction, multiply by 60, and round minutes according to policy. 6.75 hours → 0.75 × 60 = 45 minutes → 6:45. 6.33 hours is trickier because 0.33 × 60 = 19.8 minutes; know whether your system stored a repeating 1/3 hour (20 minutes) or a rounded two-decimal value.
- 15 minutes = 0.25 hours
- 30 minutes = 0.50 hours
- 45 minutes = 0.75 hours
- 10 minutes ≈ 0.1667 hours (often 0.17 if rounded to two decimals)
- 5 minutes ≈ 0.0833 hours
Rounding policies: pick one and apply it everywhere
Many workplaces round punches to the nearest five, six, or fifteen minutes. Others pay exact minute precision. Problems occur when employees convert exactly, managers round visually, and software rounds on import—three different results from one shift.
Document the rule in one sentence: ‘We convert exact minutes to decimal hours, then round each daily total to two decimal places’—or—‘We round each punch to the nearest quarter hour before totaling.’ Then use that rule for everyone in the pay group.
Be careful with break deductions. If a shift is 9:00–17:30 with an unpaid 30-minute lunch, payable time is 8.0 hours, not 8.5. Deduct breaks in minutes before converting, or deduct 0.50 after converting—but do not double-deduct.
Worked examples for common payroll spots
Daily total: punches show 08:03–12:00 and 12:30–16:57. Morning segment is 3 hours 57 minutes = 3.95 hours. Afternoon is 4 hours 27 minutes = 4.45 hours. Day total = 8.40 hours before any policy rounding. If policy rounds each segment to the nearest 15 minutes, recompute from rounded punches instead of mixing methods.
Weekly overtime intuition (illustrative only): suppose a jurisdiction pays overtime after 40 hours in a workweek. Five days of 8.40 decimal hours = 42.00 hours. That implies 40 regular and 2 overtime before other rules. Actual OT rules vary widely—daily OT, seventh-day rules, exemptions—so treat this as arithmetic practice, not a compliance determination.
Weighted pay across rates: 30 regular hours at one rate and 10 OT hours at 1.5× is not the same as averaging rates casually. Keep buckets separate. Convert time first, assign buckets second, multiply rates third.
Spreadsheets, imports, and silent corruption
Spreadsheets may interpret ‘7:45’ as a time of day, a duration, or text depending on cell format. If a duration cell displays 7:45 but the underlying value is a fraction of a day, multiplying by 24 yields decimal hours. If you typed 7.45 meaning 7:45, your sheet is already wrong.
CSV imports from clocks sometimes emit minutes as an integer column next to hours. Always verify with a known fixture: a 1-hour-30-minute shift must land at 1.5. If it lands at 1.3 or 130, you found the bug before payroll ran.
Our hours-to-decimal tool exists for quick, transparent conversions when you are auditing a line item. For recurring payroll, automate with tested formulas and keep a short reconciliation checklist rather than relying on one-off calculator use.
A reconciliation checklist before you approve pay
Spot-check at least one employee with an odd punch (not a clean 9–5). Confirm break deductions. Confirm the decimal conversion on that day by hand. Confirm the weekly sum equals the sum of daily decimals within expected rounding. Confirm OT buckets match policy thresholds. Confirm holiday or PTO codes did not double-count against worked hours.
When employees dispute a timesheet, ask them to state hours and minutes for the disputed day, convert together in the open, and compare to the system line. Most disputes collapse quickly when the 7:45 versus 7.45 confusion is drawn on a whiteboard.
Precision builds trust. Payroll math is not glamorous, but consistent conversion rules prevent the slow leak of wage errors that damage morale and create expensive corrections later.