How to Calculate Hours Worked for Payroll (Rounding Rules Explained)

A shift that runs from 8:52 to 17:08 is not, in most workplaces, paid as exactly 8 hours and 16 minutes. Almost every payroll process rounds clock times first, then converts the result into decimal hours, then applies an hourly rate, and often an overtime rate above some threshold. None of that is complicated once it is laid out as a sequence of steps, but skipping or reordering any one of them is the single most common reason a calculated paycheck does not match what an employee expects.

This guide walks through how to calculate hours worked for payroll from start to finish: rounding rules and where they come from, converting hours and minutes into the decimal figure payroll software actually uses, overtime thresholds, and the specific mistakes that most often make a calculated wage wrong. The hours calculator on this site handles the raw elapsed-time part of this, both for a single shift and for a span across multiple dates; this guide covers everything payroll does with that number afterward.

How to calculate hours worked for payroll: why raw clock times are not what gets paid

Subtracting a start time from an end time gives an exact answer, down to the minute. Most employers do not pay that exact figure, for a practical reason: employees rarely clock in or out at a perfectly round time, and processing payroll to the literal minute for every employee, every shift, adds friction without changing much about what anyone actually gets paid over a full pay period. Rounding to a fixed increment, most commonly the nearest quarter hour, is the standard middle ground.

In the US, this practice is specifically addressed rather than left to guesswork. Department of Labor regulations at 29 CFR 785.48(b) permit rounding employee time to the nearest five minutes, nearest tenth of an hour, or nearest quarter hour, on the condition that the rounding is applied consistently and averages out over a longer period rather than systematically working against employees. That last condition matters more than the rounding increment itself, and the common mistakes section below covers exactly how it gets violated in practice.

Rounding to the nearest quarter hour, worked through exactly

A quarter hour is 15 minutes, and its midpoint is 7.5 minutes. That single fact is the entire "rule": a clock time that falls 1 to 7 minutes past a quarter-hour mark is closer to that mark, so it rounds down; a clock time that falls 8 to 14 minutes past a mark is closer to the next one, so it rounds up. People often call this the 7-minute rule, since 7 minutes past a mark is the largest gap that still rounds down.

Worked example. An employee clocks in at 8:52 and clocks out at 17:08, with a 30-minute unpaid lunch. 8:52 sits 7 minutes after the 8:45 mark and 8 minutes before the 9:00 mark, so it rounds down to 8:45. 17:08 sits 8 minutes after the 17:00 mark and 7 minutes before the 17:15 mark, so it rounds up to 17:15. The rounded shift, 8:45 to 17:15, is exactly 8 hours and 30 minutes, or 510 minutes. Subtracting the 30-minute lunch leaves 480 minutes, exactly 8.0 decimal hours. At an hourly rate of $18.00, that is 8.0 times 18, or $144.00 for the day.

Notice what the rounding did in both directions here: it moved the clock-in time later (costing the employee 7 minutes) and the clock-out time later as well (gaining the employee 7 minutes). Over a single shift those two adjustments happened to cancel out exactly, which will not always happen, but it illustrates why the regulation's "averages out over time" condition is realistic rather than aspirational: a consistent rounding rule genuinely does round in both directions depending on where the actual clock time falls, not just one direction every time.

An overnight shift, rounded and paid the same way

Rounding works exactly the same way across a midnight boundary, and it is worth confirming that explicitly since overnight shifts are where ad hoc payroll math most often goes wrong.

Worked example. A night-shift employee clocks in at 23:47 and clocks out the next morning at 8:03, with a 20-minute unpaid break. 23:47 sits 2 minutes before midnight and 13 minutes after the 23:45 mark, so it rounds down to 23:45. 8:03 sits 3 minutes after the 8:00 mark, so it rounds down to 8:00. From 23:45 to 8:00 the next day is 8 hours and 15 minutes, or 495 minutes: 15 minutes to reach midnight, plus 480 minutes (8 full hours) from midnight to 8:00. Subtracting the 20-minute break leaves 475 minutes, which is 7 hours and 55 minutes, or 7.9167 decimal hours, rounded to 7.92. At $22.00 an hour, that comes to 475 divided by 60, times 22, which is $174.17.

The sequence that made this work is fixed and matters more than any single number in it: round each clock time first, then work out the elapsed time treating the end time as belonging to the next calendar day, then subtract the unpaid break, then convert to decimal, then multiply by the rate. Doing these steps in a different order, rounding after subtracting the break for instance, can land on a slightly different final figure.

Converting to decimal hours, and why payroll needs it

An H:MM figure like 8:15 is how people naturally read a duration, but it does not multiply cleanly by a wage. Multiplying 8.15 (misreading the colon as a decimal point) by an hourly rate gives a meaningless number; multiplying the correct decimal equivalent, 8.25, gives the right one. Converting means treating minutes as sixtieths of an hour: 15 minutes is 15 divided by 60, or 0.25; 30 minutes is 0.50; 45 minutes is 0.75; and any other minute value divides the same way, usually rounded to two decimal places to match how payroll software displays it.

Overtime thresholds

Once a total is in decimal hours, whether a portion of it gets paid at a higher rate depends on rules that vary a great deal by country and, within the US, by state. Under the Fair Labor Standards Act, non-exempt employees in the US are generally owed time and a half for hours worked beyond 40 in a single workweek. Some states go further: California is the best known example of a state that also requires daily overtime, generally after 8 hours worked in a single day, independent of the weekly total. Outside the US, overtime rules are set entirely separately by each country's own labor law, so a 40-hour weekly threshold is not a safe assumption to carry elsewhere. Treat any specific threshold as something to confirm against the labor law that actually applies, not as a universal constant.

Worked example. An employee at $20.00 an hour works 46 hours in a single workweek. The first 40 hours are paid at the regular rate: 40 times $20.00 is $800.00. The remaining 6 hours are paid at time and a half, so the overtime rate is $20.00 times 1.5, or $30.00 an hour: 6 times $30.00 is $180.00. Total pay for the week is $800.00 plus $180.00, or $980.00, not the $920.00 that a flat $20.00 rate across all 46 hours would give.

One detail catches people off guard the first time they run payroll on anything other than a strict weekly cycle: overtime is calculated per workweek, a fixed and recurring 7-day period the employer sets, not per pay period. A biweekly or semi-monthly pay period almost never lines up exactly with two clean workweeks, so a pay period showing 78 total hours across two weeks is not, on its own, enough information to work out overtime. Each of the two workweeks inside that pay period needs its own 40-hour threshold checked separately; a week with 44 hours and a week with 34 hours owes 4 hours of overtime, even though the two-week total, 78 hours, is under 80.

Adding up a week: from daily shifts to gross pay

Daily figures only become a paycheck once the week is added up. Take five shifts already rounded and converted to decimal hours: 8.50, 8.25, 9.00, 7.75 and 8.50. They total 42.00 hours. Under the usual federal rule, the first 40 hours are regular time and the remaining 2 hours are overtime at 1.5 times the regular rate. At 20 an hour that is 40 times 20, which is 800, plus 2 times 30, which is 60, for a gross pay of 860. The order matters: rounding and conversion come first, the weekly total second, and the overtime split last, because overtime is judged on the workweek as a whole and not on any single day. A few states also pay daily overtime, so a week that looks fine under the federal rule can still trigger extra pay under local law.

Manual timesheets, spreadsheets, or software: what actually differs

None of the four rows above changes what the correct answer actually is. What changes is how easy it is to apply the same rule consistently across every employee and every shift, which is exactly the condition regulations like 29 CFR 785.48(b) actually care about.

Common mistakes that make a calculated wage wrong

Rounding in only one direction. A rounding rule that always moves a clock-in later or a clock-out earlier, rather than rounding to the nearest mark regardless of direction, systematically reduces paid hours over time. This is the specific pattern regulators flag as improper, not rounding itself.

Forgetting to subtract the unpaid break before converting to decimal. Converting the full shift length to decimal and then subtracting a break measured in minutes mixes units and produces a wrong total unless the break is converted to the same decimal scale first. Subtracting the break in minutes before converting, as in both worked examples above, avoids the mismatch entirely.

Mishandling the midnight boundary. Subtracting an overnight shift's clock times directly, without treating the end time as the next calendar day, produces a negative number or an obviously wrong tiny one. This is exactly the failure mode the hours calculator's overnight handling exists to avoid, and it is worth checking any manual timesheet against a tool that handles it automatically.

Ignoring the daylight saving changeover. In the US, clocks move forward an hour in early spring and back an hour in late autumn. A shift worked across either changeover has a wall-clock length that differs by an hour from the employee's actual working time, in one direction or the other depending on which changeover it is. Many employers pay for the actual hours worked rather than the wall-clock difference, though the specific requirement can depend on company policy or state law.

Confusing a 12-hour and 24-hour entry. Entering 8:00 as morning when the shift meant evening, or the reverse, is an easy slip when timesheets mix 12-hour clock entries without AM or PM marked clearly. A 24-hour format removes the ambiguity entirely, which is one reason many payroll and scheduling systems default to it.

Putting the full pipeline together

That covers how to calculate hours worked for payroll up through rounding and decimal conversion; once the hours are correct, decimal, and rounded to whatever rule applies, the rest of the pipeline is a straightforward chain of conversions rather than anything specific to time tracking. Multiplying decimal hours by an hourly rate gives gross pay for that shift or period; the salary calculator converts a wage between hourly, weekly, monthly and annual figures if any of those need comparing directly. From gross pay, the take-home-paycheck calculator estimates net pay after federal tax and FICA, which is the number that actually lands in a bank account. For a full week of shifts rather than one at a time, the time card calculator totals several days of clock-in and clock-out times, with breaks, into a single weekly figure and applies an hourly rate directly.

One case worth calling out on its own: a remote team spread across time zones should convert every clock-in and clock-out time to one shared zone before comparing or totalling anything. Two employees who both clocked in at "9:00" local time, one in New York and one in London, were not working the same 9:00, and totalling their hours as though they were introduces an error that has nothing to do with rounding or overtime. Converting first, using something like this site's time zone calculator, avoids the mismatch before it has a chance to happen.

Start with the raw duration

Every calculation in this guide starts from a plain elapsed-time figure between a start and an end. Get that number right first, for a single shift or for a span across several dates, with the hours calculator, then apply whichever rounding and overtime rules actually govern the payroll in question on top of it.