Payroll does not speak in hours and minutes — it speaks in decimals, where 7 hours 45 minutes is 7.75 and a week of shifts must sum to a single number a pay system can multiply by a rate. This Time to Decimal Calculator converts any hours : minutes : seconds duration into decimal hours and, if you add an hourly rate, straight into gross pay — the exact conversion every timesheet, invoice and payroll run depends on.









Worked Example: A 7 Hour 45 Minute Shift at $20

The conversion is one division: minutes become a fraction of an hour, so 45 minutes = 45 / 60 = 0.75, and the shift is 7.75 decimal hours. At $20 per hour the gross is 7.75 × 20 = $155.00 — the number payroll actually processes. Watch the two classic traps inside this innocent example. The first is reading 7:45 as 7.45: that error (treating minutes as hundredths) understates the shift by 0.30 hours — $6.00 at this rate, $30 across a five-shift week, and thousands across a workforce and a year, which is why the mistake survives in disputes and audits. The second trap is rounding: payroll systems commonly round decimal hours to two places (hundredths), and minutes convert imperfectly into that grid — 20 minutes is 0.3333…, carried as 0.33, a third of a cent lost per occurrence and a rounding policy question (round-half-up is the fair convention) rather than an arithmetic error. Seconds, when they appear from time-clock exports, convert at 3,600 per hour: 90 seconds is 0.025 hours — small enough that many policies truncate them, but the calculator includes them so the policy, not the math, makes that decision. A five-day week of these shifts sums to 38.75 hours: under a 40-hour overtime threshold, so no time-and-a-half engages — the boundary case where the decimal sum, not any single day, decides the pay category.

The Conversion Table Worth Memorizing

Minutes recur in patterns worth knowing cold, because timesheets are built from a small vocabulary of clock fragments. Every 6 minutes is exactly 0.1 hour — the reason many time systems bill in six-minute (tenth-hour) increments. The quarters are exact: 15 minutes = 0.25, 30 = 0.50, 45 = 0.75. The thirds are the repeating ones: 20 minutes = 0.3333, 40 = 0.6667 — and their sums misbehave in hundredths (0.33 + 0.33 + 0.33 = 0.99, not 1.00), which is why weekly totals assembled from rounded daily figures can sit a hundredth below the true sum, a discrepancy every payroll professional has met and every timesheet policy should pre-decide. Odd minutes convert by the same division — 1 minute = 0.0167, 7 minutes = 0.1167, 52 minutes = 0.8667 — and the reverse journey (decimal back to clock time) multiplies the fraction by 60: 0.8667 × 60 = 52 minutes. This calculator travels the forward direction and shows the exact fraction before rounding, so the hundredths your system will use are visible rather than hidden. Where your employer’s system rounds each day versus rounding the week, the difference over a pay period is bounded by half a hundredth per rounding event — pennies, but pennies with a paper trail, and the arithmetic above is how you verify either policy was applied as written.

Where Decimal Time Runs the World

Payroll and timesheets are the home turf: every major payroll platform stores durations as decimal hours, and every audit of unpaid minutes is a conversion exercise. Freelancers and consultants invoice in decimals — the six-minute increment of legal billing (0.1 hour) is decimal time wearing a suit, and a day of tracked tasks becomes a billable figure only through this conversion. Manufacturing and logistics price labour and machine time per decimal hour, so cycle times recorded in minutes and seconds enter costing only after conversion. Aviation and healthcare log duty and procedure times in decimals for regulatory limits whose breaches are computed, not estimated. Spreadsheets are the silent failure mode worth a paragraph: Excel and Sheets store times as fractions of a day, so a cell showing 7:45 multiplied by a rate returns nonsense until multiplied by 24 — converting to decimal hours first (this page’s output) is the fix, and half the “my spreadsheet pay is wrong” questions on earth are that one missing step. In every domain the principle is identical: clocks divide the hour into sixtieths, money divides it into hundredths, and this page is the border crossing between the two systems.

A Full Week, Converted: The Overtime Boundary

Watch the conversion carry a real week. Shifts of 8:24, 7:45, 8:00, 6:30 and 9:15 convert to 8.40, 7.75, 8.00, 6.50 and 9.25 — a total of 39.90 decimal hours, worth 39.90 × $20 = $798.00 straight time. Note Friday’s quiet role: the longest day (9.25) triggered no premium, because daily overtime is not the federal rule — the weekly sum governs, and 39.90 sits a tenth of an hour below the 40-hour threshold. Now add a Saturday stint of 2:06 — 2.10 decimal — and the week becomes 42.00 hours: the first 40 pay at $20 ($800) and the 2.00 beyond the threshold pay at time-and-a-half, $30 ($60), for $860 total. Two lessons ride on this example. The threshold test and the rate test are separate multiplications applied to separate slices of the decimal total — blending them (42 × some averaged rate) is how underpayments are born. And the Saturday fragment shows why minutes matter at boundaries: had Saturday been 1:54 (1.90 decimal) instead of 2:06, the week would total 41.80 hours with only 1.80 at the premium rate — a $6 swing decided entirely by twelve minutes. The discipline is to convert every shift exactly, sum exactly, and only then split at the threshold. Payroll errors concentrate exactly at these seams, and they are always conversion errors before they are policy errors.

Six-Minute Billing: The Tenth-Hour Professions

Lawyers, consultants and agencies bill in tenths of an hour because 0.1 is exactly six minutes — the largest increment that stays honest and the smallest that stays sane. A morning of tasks logged in clock time becomes an invoice only through this page’s arithmetic: calls and drafting of 18 minutes, 42 minutes, 1 hour 12 minutes and 24 minutes convert to 0.3, 0.7, 1.2 and 0.4 — 2.6 billable hours — and at a $250 rate, a $650 morning. Two conventions govern the rounding at the fragment level, and confusing them is a billing-ethics issue rather than an arithmetic one: round-to-nearest tenth (a 7-minute call at 0.1167 becomes 0.1) versus the round-up policy many firms disclose in engagement letters (the same call becomes 0.2, the next whole six-minute block). Neither is wrong; an undisclosed one is. Freelancers on hourly platforms live under the platform’s own version of the same grid (tracker screenshots converted to decimal minutes), and the professional habit worth copying from all of them is logging in clock time and converting at invoice time — because decimal figures reconstructed from memory at week’s end are fiction with good formatting, while clock records converted by formula are evidence.

Converting Back: Decimal to Clock Time

The return journey matters when a decimal total must become a schedule again. Split the number at the point: whole hours carry over, and the fraction multiplies by 60 to restore minutes. The 39.90-hour week from the overtime example, if it were a single duration, would be 39 hours and 0.90 × 60 = 54 minutes; the 38.75-hour week converts to 38 hours 45 minutes; a lone 0.1 is exactly 6 minutes — the billing increment coming home. A fraction that still carries decimals after the ×60 (0.8667 hours → 52.002 minutes) yields seconds by one more multiplication, and the pair of multiplications is the exact mirror of the divisions that built the decimal: ÷60 and ÷3,600 going in, ×60 and ×60 coming out. Keep both directions in the same document whenever you publish a conversion, because the reader checking your timesheet is travelling the other way.

Common Mistakes

Writing 7:45 as 7.45 (the $6-a-shift error above). Rounding each minute-fragment before summing instead of summing exact fractions and rounding once at the end. Forgetting that an unpaid lunch break must be subtracted before conversion, not from the decimal afterwards (both work arithmetically — but only one matches the time record an auditor will compare against). Mixing decimal hours with decimal days in spreadsheets (7.75 hours is 0.3229 days). And applying an overtime multiplier to the whole decimal sum when only the hours beyond the threshold earn it: the threshold test and the rate test are separate steps, in that order.

Related Tools

Continue with the Days Between Dates Calculator, the Reading Speed Calculator, the Battery Charge Time Calculator, or browse the full Everyday Life Calculators hub.

Frequently Asked Questions

How do I convert minutes to decimal hours?

Divide the minutes by 60 and add the whole hours: 7 hours 45 minutes = 7 + 45/60 = 7.75 hours. Seconds divide by 3,600. The calculator performs both and shows the result to four decimal places before any rounding.

What is 45 minutes in decimal?

0.75 hours. The quarters are the friendly ones: 15 minutes = 0.25, 30 = 0.50, 45 = 0.75. Thirds repeat: 20 minutes = 0.3333 and 40 = 0.6667.

Why does payroll use decimal hours?

Because pay is hours × rate, and multiplication needs a single decimal number. Clock format (7:45) cannot be multiplied by $20 directly; its decimal form (7.75) can — 7.75 × 20 = $155.00.

Is 7.45 hours the same as 7 hours 45 minutes?

No — that is the most expensive typo in timesheets. 7 hours 45 minutes is 7.75 hours; 7.45 hours is 7 hours 27 minutes. The 18-minute gap is $6.00 at $20/hour.

How should decimal hours be rounded?

Common practice rounds to hundredths (two decimals) with round-half-up. Sum exact values across the week first and round once at the end where policy allows — rounding each day separately can drift the total by a hundredth or two.

How do I convert decimal hours back to hours and minutes?

Take the fractional part and multiply by 60: 7.75 → 0.75 × 60 = 45 minutes, so 7 hours 45 minutes. Any remaining fraction of a minute × 60 gives seconds.