Minutes to Decimal Hours: The Timesheet Conversion That Costs People Money
Clocks run in base 60 and payroll runs in base 10, and the gap between them produces a specific, repeatable error: writing 7 hours 45 minutes as 7.45 instead of 7.75. On an hourly rate of 40, that single slip underpays by 12 on one shift — and it repeats every week it goes unnoticed.
The conversion
Divide the minutes by 60. That is the whole rule, and the reason it works is that a decimal hour is a fraction of an hour, not a count of minutes.
- 15 minutes = 0.25
- 20 minutes = 0.333
- 30 minutes = 0.5
- 40 minutes = 0.667
- 45 minutes = 0.75
- 50 minutes = 0.833
Only the quarter-hours convert to tidy decimals, which is why quarter-hour rounding became the norm on paper timesheets. Anything else recurs, and where it recurs you have a rounding policy to decide rather than a number to write down. The time duration calculator returns both the hours-and-minutes form and the decimal figure from the same pair of clock times, so the conversion never has to be done by hand.
Rounding is a policy, not a detail
Twenty minutes is 0.3333 recurring. Stored as 0.33, it loses two seconds; across 200 entries that is a few minutes, which nobody will notice. The problems appear when rounding is applied at the wrong stage or in a consistent direction.
Two rules keep it clean. Round once, at the end, not on each entry — rounding every line and then summing accumulates error that summing first and rounding once does not. And round in a way that does not systematically favour one party; always rounding down is a pay cut administered by arithmetic. If your payroll system rounds to the nearest quarter hour, know that a 7-minute overrun disappears and an 8-minute one becomes a full quarter.
Night shifts and the negative-hours bug
A shift from 22:00 to 06:00 subtracts to minus sixteen hours if you treat the times as plain numbers. The fix is to recognise that the end time being earlier than the start time means a day boundary was crossed, and add 24 hours before subtracting.
Spreadsheet formulas written by hand rarely account for this, which is why overnight shifts are the most common source of impossible timesheet totals. Daylight-saving transitions add a second layer: in most jurisdictions a shift spanning the spring-forward is paid for the hours actually worked, which is one fewer than the clock suggests, and the autumn transition adds one. Those two shifts a year are worth checking manually.
Breaks: the deduction that depends on your contract
Unpaid breaks come off the total; paid rest breaks do not. Which is which is set by local employment law and by the specific contract, and the two frequently disagree — a jurisdiction may mandate an unpaid meal break of a certain length while a contract provides paid short rest breaks on top of it.
The practical approach is to record actual start, actual end and actual unpaid break minutes as three separate fields rather than recording a single "hours worked" figure. Three fields can be re-derived under a different policy later; one aggregate cannot, and if a pay query arrives six months on, the raw fields are the only defensible record.
Turning hours into a rate you can compare
Decimal hours are also what make rates comparable. An annual salary divided by (hours per week × paid weeks per year) gives a true hourly figure, and the paid-weeks number is where salaried and contract work separate: an employee is typically paid across all 52 weeks, while an independent contractor bills closer to 44 to 46 after holiday, sickness and unbilled administration.
That difference, plus employer pension contributions and any health cover, is why a contract rate has to exceed the salaried equivalent to be worth the same. The salary to hourly calculator converts in both directions with hours and paid weeks as explicit inputs, which is what makes the two employment models genuinely comparable rather than superficially so.