Decimal to Time

Rounding Decimal Hours

When sixty 1-minute entries each display as 0.02 hours, the column adds up to 1.20 hours even though the true total is 1.00 hours: a gap of +0.20 hours (12 minutes).

Whole numbers from 1 to 500. Each entry uses the same minutes value below.

Digits and one decimal point, such as 1 or 7.5.

Column total vs true total
Shown per entry
0.02 h
Sum of shown values
1.20 h
Exact total (add first, round once)
1.00 h
Gap
+0.20 h (12 minutes)

Each entry is rounded to 2 decimal places before it is added to the column sum.

Each entry shows as 0.02 hours, so the column adds up to 1.20 hours, which is more than the true total of 1.00 hours (+0.20 hours, or 12 minutes).

Exact integer mathRuns in your browserNothing you type is uploaded

Why it happens

Some timesheets and payroll exports store each shift or punch as its own decimal hour. The display rounds each entry on its own. One minute is about 0.016667 hours; at two decimal places that reads as 0.02 hours, so every entry is a little high before you add anything.

The errors accumulate. The demo above uses the same rounding as the Bulk Time Converter and the Minutes to Decimal converter: half-up to the decimal places you choose.

Sixty 1-minute entries at different decimal places
DecimalsShown per entrySum of shown valuesExact totalGap
10.00.01.0−1.0
20.021.201.00+0.20
30.0171.0201.000+0.020
40.01671.00201.0000+0.0020

How to avoid it

Keep minutes or exact decimal values through the sum, then convert or round once at the end. That is what the Bulk Time Converter total does, and what the Decimal Hours Calculator does when you add durations before formatting the answer.

When a system forces per-entry rounding, treat the column sum and the exact total as two related numbers. The Time to Decimal converter lets you set decimal places per entry; the Bulk Converter shows both the sum of rounded cells and the true total when they differ.

Billing systems that use tenths of an hour apply their own step size; see the Tenths of an Hour Chart for how those increments relate to minutes.

What this page does not tell you

This page is arithmetic, not payroll policy. Employers choose how many decimal places to store, whether to round each punch, and how totals are calculated. Check with whoever runs your payroll or billing if you need their rule, not a web calculator.

Nothing here is legal, financial or tax advice. For how this site converts units, limits inputs and reports totals, read the Calculation Method.

Questions

Why do my rounded hours add up to more than the real total?

Each row is rounded on its own before you add it. One minute is about 0.016667 hours; at two decimal places that displays as 0.02 hours. Sixty such rows sum to 1.20 hours while the exact total is 1.00 hours. The Bulk Converter adds exact values first and rounds once, which is why its total can differ from a hand-added column.

How many decimal places avoid the drift?

More decimals shrink the gap but do not remove it for every pattern. For sixty 1-minute entries, one decimal place shows 0.0 hours each, so the column totals 0.0 hours against a true 1.0 (gap −1.0). At three decimals each entry is 0.017 hours and the column reads 1.020 hours against a true 1.000 (gap +0.020). At four decimals the gap is +0.0020 hours. Use minutes, or add exact values first, when you need an exact total.

Should I add minutes first?

Yes when you can. Summing minutes (or exact decimal values) and converting once matches what the Bulk Converter and Hours Calculator do. Converting each row to 0.02 hours and adding afterward gives 1.20 hours for the sixty 1-minute example instead of 1.00 hours.

Why does each 1-minute entry show as 0.02 hours?

One minute is about 0.016667 hours. Rounded half-up to two decimal places that becomes 0.02 hours. The rounded value is slightly larger than the true minute, so repeating it adds extra time.

What is the difference between the column sum and the true total?

The column sum adds the numbers you see in each cell (1.20 hours in the default demo). The true total adds the exact durations first, then rounds once (1.00 hours for sixty 1-minute entries). The gap is +0.20 hours (12 minutes).

Does this demo use the same math as the Bulk Converter?

Yes. It runs the same batch engine as the Bulk Converter in minutes-to-decimal mode. When a column of rounded cells would differ from the exact total, the converter shows both totals and the gap.

Will fewer entries fix the problem?

Fewer rows mean a smaller gap in absolute terms, but per-entry rounding still matters. Forty 7-minute entries at one decimal place show 0.1 hours each, sum to 4.0 hours, and come out 0.7 hours short of the true 4.7 hours.

Can spreadsheet formulas avoid this?

Formulas that sum exact times or minutes and convert once behave like the tools on this site. Formulas that round each cell before summing behave like the column sum in the demo, for example 3.00 hours from one hundred 2-minute rows at two decimals versus 3.33 hours exact. See the Excel formulas page for Excel-specific setup.