From clock hours to decimal hours, instantly
Every payroll run, billing export and job-costing report stores work time as decimal hours, because a decimal multiplies straight into money: 7.75 hours at $22 an hour is $170.50 with no further arithmetic. This hours to decimal converter takes what you actually wrote down — hours and minutes — and produces that decimal instantly, in either direction.
Enter 7:45 and the converter shows 7.75. Enter 7.75 and it shows 7:45. Both fields update as you type, so the page doubles as a checker: paste a decimal from a payslip next to the time you believe you worked, and any disagreement between the two formats is visible at a glance.
The mechanics never change, whatever the entry looks like. Whole hours pass through untouched — 7 stays 7 — and the minutes divide by 60: 45 minutes is 45 ÷ 60 = 0.75, so 7:45 becomes 7.75. A 4-hour 12-minute stretch is 4 + 12/60 = 4.2 exactly. When the minutes are awkward — 7:23 is 7.3833, 5:47 is 5.7833 — the converter carries four decimal places, which is finer than any payroll system rounds, so whatever happens to the number afterward is policy, not arithmetic.
Payroll day: 7 hours 45 minutes is 7.75 hours
Here is the calculation that happens thousands of times a week inside small businesses. An employee's shift ran 7 hours 45 minutes. The owner converts: 45 ÷ 60 = 0.75, so the day is 7.75 decimal hours. At $22 an hour, the day pays 7.75 × $22 = $170.50. Over a five-day week of identical shifts, 38.75 hours at the same rate is $852.50 — and every one of those numbers started life as a clock time on a paper schedule.
The division only ever touches the minutes. That is the whole trick, and it is also the whole failure mode: people who convert 7 hours 45 minutes as 7.45 produce a day worth $163.90 instead of $170.50 — a $6.60 error per shift, silently repeated. At $22 an hour across a 40-hour year, writing minutes after the decimal point instead of dividing them underpays an employee by roughly $3,000. No payroll system catches it, because 7.45 is a perfectly valid decimal; it is just the wrong one.
The same conversion runs in reverse when someone reads a stub. A paycheck line that says 37.58 hours decodes as 37 hours and 0.58 × 60 = 34.8 minutes — so 37:35, or 37:34 if the system truncated instead of rounding. If you keep your own record, the minutes to decimal hours page converts each day's odd minute counts individually, and the decimal to time converter runs a single decimal back into hours and minutes when you want to know what 37.58 actually was.
Typing into payroll software: the ADP and Paychex decimal field
Open a payroll provider's hours-entry screen and the field is labeled hours — but it wants a decimal. ADP's Run and Workforce Now hours entry, Paychex Flex, Gusto, QuickBooks Payroll, Patriot, OnPay: all of them expect 8.25 in the regular-hours box, not 8:15. Some flag or reject a colon entry; worse, a few silently truncate 8:15 to 8.00, and the missing quarter hour never surfaces until the employee compares stubs.
So the weekly ritual for anyone keying hours by hand looks like this: read the paper timecard row — In 8:03, Out 12:11, In 12:41, Out 16:22 — difference each pair, subtract the unpaid lunch, land on 7 hours 49 minutes, convert, and type 7.82 into the software. That conversion is the one step the software will not do for you, which is why this page sits open in a browser tab next to the payroll login. Four decimals is more precision than the field wants; most providers accept two, and your company's rounding policy decides whether 7.8167 becomes 7.82 or 7.8.
A caution on the other side of the field: some systems accept more than they should. Typing 7.8167 into a field configured for quarter-hour rounding can produce 7.75, losing 4 minutes of pay; typing it into a tenth-rounding field produces 7.8. The safe order of operations is convert exactly, round once, per your policy, then enter — never enter raw and hope the system rounds the way you expect. For whole weeks rather than single days, the time card calculator totals seven days into one decimal figure and estimates the gross pay the entry should produce.
Why QuickBooks Time shows 5.7 instead of 5:42
Employees who clock in and out through an app — QuickBooks Time (formerly TSheets), When I Work, Homebase, Deputy — see their total come back as 5.7 or 40.35 and wonder where their minutes went. Nothing was lost. The app tracks exact minutes internally, then displays decimal hours because the export feeds payroll, and payroll speaks decimals. 5 hours 42 minutes is 5.7 exactly, because 42 ÷ 60 = 0.7.
The display setting is usually configurable, and the choice matters more than people expect. A team set to decimal display reports 40.35 hours; the same punches set to hours-and-minutes report 40:21. Both describe an identical week. The confusion starts when someone compares the app's 40.35 against a handwritten card that says 40:15 — one of the two has been misread, and it is almost always the handwritten one being read as 40.15.
Rounding, not the decimal, explains real discrepancies. Many of these apps round each punch to a set increment — nearest 15 minutes, nearest tenth — before totaling, so a 5:42 shift can legitimately export as 5.75 (quarter rounding) or 5.7 (tenth rounding) or 5.7 (exact). If your app's total disagrees with your own arithmetic by less than the increment, that is the setting; if it disagrees by more, look for a missed punch or an automatic break deduction. The decimal hours calculator on the home page handles a single check in either direction when one entry looks suspicious.
Nursing shifts: a 12-hour 24-minute day in decimal
Hospital nursing runs on 12-hour shifts, and the decimals get long. A scheduled 12-hour shift that actually ran from 06:45 to 19:09 is 12 hours 24 minutes of elapsed time. Subtract a 30-minute unpaid meal and the paid day is 11 hours 54 minutes — 11.9 decimal hours exactly, since 54 ÷ 60 = 0.9. The nurse sees 11.9 on the timesheet, the payroll system multiplies it against the hourly rate, and the shift-differential kicker (say $3.50 an hour for night portions) multiplies against the same decimal.
Three 12s a week is the classic pattern, but no three 12s come out identical. One runs short at 11:48 paid (11.8), one runs exactly 11.9, one runs over at 12:06 paid (12.1). The week totals 35.8 decimal hours — under 40, so no federal overtime — but the daily variations matter enormously in states like California, where anything past 8 in a day carries a daily premium regardless of the weekly total. A 12.1-hour California shift owes overtime on 4.1 of those hours even in a 35.8-hour week.
Decimal hours are also how staffing acuity reports get built. A unit manager comparing two weeks of roster data — 11.9, 11.8, 12.1, 11.9 — is averaging decimals, not clock times; 'average shift of 11.925 hours' is a number the staffing office can divide into census and budget targets. For checking a full two-week pay period of 12s day by day, the time card calculator keeps each day's decimal visible while totaling both weeks.
Billable hours: lawyers and the 0.1-hour increment
Law firms bill in tenths of an hour — the 6-minute increment — so every task's duration becomes a decimal before it becomes money. A 2-hour 18-minute client meeting is 2.3 hours billed (18 ÷ 60 = 0.3, no rounding needed). A 1-hour 52-minute contract review is 1.867 exact, which rounds up to 1.9 under the standard round-up convention. At a $400 hourly rate, that difference is $40 on a single time entry.
The decimal format is what makes the invoice checkable. A client can verify that 2.3 hours at $400 is $920; a narrative entry of '2 hours 18 minutes' invites arithmetic nobody wants to do. Legal timekeeping software — Clio, TimeSolv, the billable timer in any of the big platforms — records minutes and displays tenths for exactly this reason, and it is why the 0.1 increment shows up unchanged on decades-old paper invoices and brand-new e-billing portals alike.
Watch the increment system work over a day: five entries of 1:10, 0:48, 2:05, 0:24 and 1:33 come to 6 hours 0 minutes exactly — 6.0 decimal hours. Rounded up per entry, the same day bills 1.2 + 0.8 + 2.1 + 0.4 + 1.6 = 6.1 hours. That tenth of an hour, $40 at the $400 rate, is the increment system's margin over a day — small per entry, structural across a year, and the reason every firm's billing guidelines specify the increment in decimal terms rather than minutes.
Excel: the TEXT and MOD traps that corrupt hours
Spreadsheets are where good hour data goes to die, and both deaths have names. The first: Excel stores time as a fraction of a day, so a cell holding 7:45 is internally 0.3229 — not 7.45 and not 7.75. Multiply that cell by an hourly rate and you get $7.10 instead of $170.50. The fix is to multiply by 24 first: =(Out-In)*24 turns the fraction into true decimal hours. Formatted as a plain number, 7.75 appears; formatted as time, Excel cheerfully shows it back as 18:00, because 7.75 days is what the value now means.
The second trap is extracting minutes from a time value. The formula =MOD(A2,1)*24*60 gives total minutes correctly, but the tempting shortcut — using =MINUTE() on a cell and appending it after a decimal point, building '7' & '.' & '45' — produces exactly the 7.45 error from the payroll section above, at spreadsheet scale. A whole column of those numbers looks plausible, sums cleanly, and is wrong by 45 − 45/60 = 0.3 hours per row. Nobody notices until an employee with a calculator calls.
The reliable recipe, in plain steps: keep punch pairs as real time values, subtract them, multiply by 24 for decimal hours, and only then round — =ROUND((Out-In)*24,2) gives a clean two-decimal figure that sums and multiplies honestly. Total the week before applying any rounding rule, not after, or the rounding compounds. If the spreadsheet is fighting you, the converter above checks any single cell's intended value in a second, and the decimal time conversion chart covers the quarter-hour values most timesheets actually contain.
FMLA and compliance forms that demand decimals
Federal paperwork has opinions about your time format. On the Department of Labor's optional FMLA usage record (Form WH-380-E and the certification forms), hours of leave taken are recorded per day or week, and employers who track in increments typically report them as decimals — a 4-hour-30-minute FMLA day goes on the form as 4.5, not 4:30. The same convention runs through most leave-management systems: when the balance reads 61.25 hours remaining, that is 61 hours 15 minutes, and it drains in 0.25 or 0.125 chunks as partial days are taken.
The decimal requirement bites hardest on intermittent leave. An employee taking two-hour chunks for treatment accumulates 2.0, 2.0, 2.0 against a 480-hour annual entitlement (12 weeks × 40); an employee taking 2-hour-15-minute chunks accumulates 2.25 each time, and after twenty absences the difference between the two formats is 5 full FMLA hours. Getting the conversion wrong in the employee's disfavor is exactly the kind of record-keeping error FMLA litigation feeds on, so the safe practice is converting exactly — 15 minutes is 0.25, 20 minutes is 0.3333 — and rounding only once, at the form.
The same discipline applies to state paid-leave claims and workers' comp wage statements, which generally want average weekly hours as a decimal. Computing one from a month of varied shifts — say 40.25, 38.5, 41.75, 39.5 — means adding the decimals (160.0) and dividing by the weeks (40.0), a step that only works if every week was converted exactly in the first place. One week keyed as 38.30 instead of 38.5 skews the average and, on a wage claim, the benefit check.
Europe: logging hours against the 48-hour limit
Across the EU and UK, the Working Time Regulations cap average weekly working time at 48 hours over a reference period — typically 17 weeks. Compliance is proven with hour records, and those records are kept in decimal hours because the averaging arithmetic needs them: a week of 8:15, 8:40, 9:05, 8:50, 7:55 works out to 42.92 decimal hours (8.25 + 8.67 + 9.08 + 8.83 + 7.92, carried to two places). Sum all seventeen weeks and divide; if the average crosses 48, the employer has a problem the format cannot hide.
The decimal format also feeds the other mandatory counts. Daily rest of 11 consecutive hours, a 20-minute break on shifts longer than 6 hours, night-work limits of 8 hours on average — each check compares decimal figures, because 'did this worker exceed 48?' cannot be answered from a column of clock times without converting anyway. UK employers post-Brexit keep the 48-hour cap, with the opt-out agreement as the one escape hatch, and the record-keeping duty unchanged.
Practically, a manager auditing a European team runs the same loop as an American payroll clerk, just against a different threshold: convert each day to decimal, sum the week, compare against 48 rather than 40. The divide-by-60 step is identical — 8:40 is 8.67 hours whether the ceiling is Brussels' or Washington's — which is why the chart below the converter and the minutes to decimal hours table both work anywhere the week gets totaled.
Why 60 divides an hour: the base mismatch
The hour divides into 60 minutes rather than 100 because the system descends from Babylonian astronomy, which ran on base-60 arithmetic. Base 60 factors evenly by 2, 3, 4, 5, 6, 10, 12, 15, 20, and 30, which kept ancient timekeepers from needing fractions when splitting a day or a circle face. Quarter hours, thirds, and sixths all land on whole-number minute counts as a result. None of that helps with decimal multiplication, because modern payroll, billing, and spreadsheet software all operate in base-10. The divide-by-60 step exists because the two systems share the word "minutes" but assign it different underlying values.
The confusion that follows is mechanical. Writing 7 hours 45 minutes as 7.45 treats the digits after the decimal point as if they were minutes in a base-10 number — they are not. The decimal point separates whole hours from fractions of an hour expressed in hundredths, so 7.45 means 7 hours and 45/100 of an hour, which is 7 hours 27 minutes. The correct decimal is 7.75, because 45 minutes is 45 / 60 = 0.75. That 18-minute gap costs $6.00 per shift at $20 an hour, $150 over a five-day week, and roughly $3,900 over a working year.
Reverse conversion follows the same multiplier in the other direction: multiply the decimal fraction by 60 to recover the minutes. 0.35 hours × 60 = 21 minutes, so 4.35 decimal hours is 4 hours 21 minutes, not 4 hours 35 minutes. 0.83 hours × 60 = 49.8 minutes, meaning 6.83 decimal hours is just under 6 hours 50 minutes — not 6 hours 83 minutes. Any decimal figure should round-trip this way; if multiplying the fraction by 60 does not reproduce the original minutes, one of the two numbers contains the conversion error this page is built to catch.
Per-minute decimal reference: 0 to 55 in five-minute steps
The twelve five-minute markers cover the values that appear on most handwritten timesheets. Each is the minute count divided by 60, carried to four decimal places: 5 min = 0.0833, 10 min = 0.1667, 15 min = 0.25, 20 min = 0.3333, 25 min = 0.4167, 30 min = 0.50, 35 min = 0.5833, 40 min = 0.6667, 45 min = 0.75, 50 min = 0.8333, 55 min = 0.9167. The four that appear most often in payroll — 15, 30, 45, and 60 minutes — are the clean quarters: .25, .50, .75, and 1.00. Employers who round punches to the nearest 15 minutes use only those four fractions in the minutes column, so any stub decimal ending in .83 or .67 signals exact-minute tracking or sixth-of-an-hour rounding instead.
Between the five-minute marks, each individual minute has its own decimal. One minute is 1/60 = 0.0167. The step from one minute to the next is always that same 0.0167, which is why two entries differing by a single minute produce decimals 0.0167 apart: 7:22 is 7.3667 and 7:23 is 7.3833. At $25 an hour, that single minute is worth $0.42. Payroll systems that track exact minutes use this resolution. The minutes to decimal hours page lists all 60 individual values for anyone dealing with odd-minute entries every shift.
The FLSA's seven-minute rule for quarter-hour rounding creates a predictable grid in compliant timesheets: only .00, .25, .50, and .75 ever appear in the fraction position. A punch at 8:07 rounds down to 8:00; a punch at 8:08 rounds up to 8:15. Recognizing that grid matters when auditing a pay stub — a fraction outside the .00/.25/.50/.75 set means the employer uses a finer rounding increment, and comparing it against the decimal time conversion chart's quarter-hour values will not fully explain the figure. Knowing which rounding system is in play is the first step in any stub review.
Three worked shifts: from punch to decimal in full
A retail associate clocks in at 9:15 AM and out at 1:30 PM with a paid 15-minute rest break midway. Elapsed time is 4 hours 15 minutes. The break is under 20 minutes and compensable under 29 CFR 785.16, so it stays in worked time. 4 hours 15 minutes converts to 4 + 15/60 = 4.25 decimal hours, paying $68.00 at $16 an hour. Had the break been an unpaid 30-minute lunch instead, the entry would drop to 3 hours 45 minutes = 3.75 decimal hours — a $8.00 difference on that one shift, produced entirely by a change in break status rather than a change in the clock.
A warehouse associate starts at 7:30 AM, clocks out at 5:45 PM, and takes a 30-minute unpaid lunch. Elapsed time is 10 hours 15 minutes; subtract the meal to get 9 hours 45 minutes = 9.75 decimal hours. The first 8 hours are straight time at $18.50: $148.00. The remaining 1.75 hours are overtime at $27.75 (1.5 × $18.50): $48.56. Gross pay for the day is $196.56. Writing 9.45 for 9 hours 45 minutes — the classic minutes-in-decimal error — shaves the overtime line from 1.75 hours to 1.45 hours and drops the gross estimate by $8.31 before the week even finishes.
A school aide scheduled for 8 hours clocks in at 8:00 AM and leaves at 3:45 PM — 15 minutes early — with no unpaid break. The actual day is 7 hours 45 minutes = 7.75 decimal hours. Under a quarter-hour rounding policy, a 3:52 PM departure rounds up to 4:00 and records 8.0; a 3:45 PM departure stays at 7.75. That 0.25-hour gap is $4.25 at $17 an hour. Whether the early exit changes the paycheck depends entirely on the rounding increment — which is why knowing the policy in advance turns a stub discrepancy into a specific, answerable question.
Conversion mistakes that hide in plain sight
The error behind most disputed timesheets is writing minutes in the decimal field instead of dividing them. 1 hour 30 minutes entered as 1.3 should be 1.5. 2 hours 15 minutes as 2.15 should be 2.25. 4 hours 45 minutes as 4.45 should be 4.75. Each value looks reasonable in a column, sums without complaint, and produces pay that is silently short. At $20 an hour, entering 4.45 instead of 4.75 costs $6.00 on that shift; five such entries across a week cost $30, and 50 weeks cost $1,500 — all from a habit rather than a calculation.
Reading a decimal backward is the mirror mistake. 1.75 on a stub is 1 hour 45 minutes, not 1 hour 75 minutes — 0.75 × 60 = 45. 0.5 decimal hours is 30 minutes, not 50 minutes. Anyone who reads 8.5 as 8 hours 50 minutes expects pay for 8 hours 50 minutes of work, while the stub covers only 8 hours 30 minutes — a 20-minute gap worth $5.83 at $17.50 an hour. The decimal to time converter resolves any single figure in a second, and the pattern from the per-minute table above confirms the result.
Cross-midnight shifts produce a third category: negative elapsed time when someone subtracts a next-day out-punch from the same-day in-punch without adjusting for the date change. A 10:00 PM to 6:30 AM shift spans 8 hours 30 minutes = 8.5 decimal hours, but subtracting 6:30 from 22:00 directly yields a nonsense result. The reliable fix: add 24:00 to any out-time smaller than the in-time — 6:30 becomes 30:30 — then subtract the in-time (30:30 − 22:00 = 8:30), which converts cleanly to 8.5. The time card calculator handles this automatically when you enter a duration rather than raw punch times.
Payroll rounding rules: 6-minute, 15-minute, and the FLSA standard
The Fair Labor Standards Act permits employers to round punch times to the nearest 5, 6, or 15 minutes, provided the rounding policy is neutral over time — meaning it must not consistently favor the employer. The most common standard is the 7-minute rule for quarter-hour rounding: any punch within the first 7 minutes of a quarter rounds down to the start of that quarter, while a punch in minutes 8 through 14 rounds up to the next quarter. A clock-in at 8:07 AM records as 8:00; a clock-in at 8:08 AM records as 8:15. The resulting timesheet uses only four decimal fractions — .00, .25, .50, and .75 — making arithmetic simple and auditable. Courts have upheld this system in dozens of FLSA collective actions, most recently reinforcing that the 7-minute midpoint is the enforceable boundary, not 8 or 10 minutes.
The 6-minute rounding system — also called tenth-of-an-hour rounding — applies most commonly in legal billing, consulting, and some healthcare staffing. Here each 0 to 5-minute block rounds to the nearest sixth of an hour, producing decimals in increments of 0.1: 0.0, 0.1, 0.2 … 0.9, 1.0. A task that ran 22 minutes rounds to 0.4 hours (nearest sixth = 24 minutes), while 19 minutes rounds to 0.3 hours (nearest sixth = 18 minutes). Legal billing typically rounds up rather than to-nearest, so 19 minutes bills as 0.4 hours, adding $40 on a $400 hourly rate. The dispute between quarter-hour and tenth-hour rounding is significant: an employee who consistently clocks out 7 minutes before the next quarter will lose 0.25 hours per shift under quarter-hour rounding but only 0.1 hours under tenth-hour rounding — a $3.00 difference daily at $20 an hour.
Several states have tightened the FLSA floor. California prohibits rounding policies that consistently undercount employee time, and a 2021 California Supreme Court ruling (<em>Donohue v. AMN Services</em>) eliminated rounding for meal-period violations entirely in that state — exact-minute tracking is now required for meal breaks. Washington and Oregon both require rounding to be disclosed in writing. If you use the <a href='/time-card-calculator'>time card calculator</a> on a California payroll, entering exact decimal hours is safer than rounding to the nearest quarter, because any quarter-hour shortfall that persists across a pay period can create derivative claims under California Labor Code § 226.
Importing decimal hours into ADP, Gusto, and QuickBooks Time
ADP Workforce Now accepts CSV imports through the Time & Attendance module. The expected column header for duration is <code>HOURS_WORKED</code> and the value must be a plain decimal — 8.25, not 8:15 and not 8h15m. ADP applies its own rounding rule (configured per pay group) after import, so the file should carry pre-conversion exact values whenever possible. The most common import rejection code is <strong>ERR_INVALID_DURATION</strong>, triggered when a cell contains a colon or a letter — both formats that look like clock time rather than decimal hours. A second frequent error is <strong>ERR_EXCEEDS_DAILY_MAX</strong> for any row above the pay-group daily maximum, defaulting to 24.0; a night shift spanning midnight requires splitting into two date rows, each with its own decimal total, not a single row summing to 14.5.
Gusto's timesheet CSV import (available on the Plus and Premium plans) uses <code>hours_worked</code> in decimal format. One distinction from ADP: Gusto rounds the imported value to the nearest minute at the database level, so 8.1667 hours (8 hours 10 minutes exactly) is stored cleanly, but 8.1670 is silently truncated to 8.167 and then rounded to 8 hours 10 minutes. This is harmless for most entries but matters for legal billing files that carry four-decimal precision — export from the billing system first, divide by 60 where the source is raw minutes, then paste into Gusto with no more than three decimal places. The <a href='/'>decimal hours calculator</a> on this site displays four decimal places; for Gusto, use the value and drop the fourth digit.
QuickBooks Time (formerly TSheets) stores all duration as minutes internally and exposes decimal hours in reports. When you export a timesheet to QuickBooks Desktop, the file writes decimal hours in a <code>.IIF</code> format with the tag <code>DURATION</code>; QuickBooks Online uses a REST API field named <code>durationInSeconds</code>. A common integration bug surfaces when third-party apps write <code>durationInSeconds</code> as minutes rather than seconds — QuickBooks Online then displays a shift of 510 minutes as 8.5 hours correctly, but a shift of 510 seconds (8.5 minutes) shows as 0.14 hours. If imported entries look exactly 60× too small, the upstream system is passing minutes where seconds are expected. Converting with this page gives you the correct decimal-hour value; multiply by 3,600 if the destination field is in seconds.
Single-shift billing in trucking, nursing, and construction
DOT Hours of Service rules require carriers to log on-duty and driving time in hours and minutes, and most Electronic Logging Device (ELD) platforms — including KeepTruckin (Motive), Samsara, and PeopleNet — export duty-period totals as decimal hours for payroll. A driver who drove 9 hours 45 minutes and spent 2 hours 30 minutes on other on-duty tasks logs 9.75 + 2.50 = 12.25 total on-duty hours. The 11-hour driving limit under 49 CFR 395.3 means the driver may drive 11.0 decimal hours maximum; 11.25 is already a violation. ELD platforms flag the threshold at exactly 11.0 hours, so a decimal that looks like 10.98 versus 11.02 can be the difference between a clean log and a carrier safety score penalty. Converting the decimal correctly before entering it into a dispatch system is not a bookkeeping exercise — it is a compliance step.
Nursing shifts are often 12.0 or 12.5 hours, but actual clock time diverges because of bedside handoffs, mandatory 30-minute meal deductions, and California's meal-penalty rules. A 12-hour-25-minute shift minus a 30-minute unpaid meal is 11 hours 55 minutes = 11.9167 decimal hours, typically entered as 11.92 in scheduling software. Under the California 8/12-hour daily overtime structure, the first 8 hours are at straight time, hours 8 through 12 are at 1.5×, and hours past 12 are at 2.0×. On a 11.9167-hour paid shift, that gives 8.0 straight + 3.9167 at time-and-a-half — using 11.92 rather than 11.9167 adds 0.0033 hours, a $0.10 error per shift at $30 an hour, but across 26 pay periods of three 12-hour shifts per week the compounded total is $23.40 per year for one nurse. For a 200-nurse unit the cumulative figure exceeds $4,600 annually from rounding alone.
Construction per-diem billing typically runs on the prevailing-wage schedule for the trade, and certified payroll reports (federal form WH-347) require hours to appear as decimals accurate to the quarter hour. A laborer who worked 10 hours 10 minutes on a Davis-Bacon project should appear as 10.25, not 10.17 (exact decimal) and not 10 (truncated whole hour). Misreporting by even 0.25 hours on a certified payroll triggers a Davis-Bacon compliance finding during DOL audit. The <a href='/decimal-time-conversion-chart'>decimal time conversion chart</a> shows the nearest quarter-hour value for every 15-minute increment, making it the fastest cross-reference for WH-347 entry.
Where this page fits with the rest of the toolkit
For a single entry or a quick check, use the converter above. For a page of lookups, the decimal time conversion chart lists every 15-minute increment up to 12 hours in both directions, and the minutes page covers 1 through 60 minutes individually. For a whole week of hours, the time card calculator adds seven days together and multiplies by your hourly rate to estimate gross pay.
All of these tools run locally in your browser with no sign-up and no stored data, which matters when the numbers you are converting are your own working hours and pay. Open any of them on a phone and the layout collapses to a single column with full-size inputs.
Decimal hours vs HH:MM: which format to use where
Both formats represent the same reality but serve different audiences. Clock notation — 8:30, 7:45, 11:15 — reads naturally and reduces transcription errors when employees write down their own start and end times. Decimal hours — 8.5, 7.75, 11.25 — feed directly into arithmetic: one multiplication produces a dollar figure, one addition produces a weekly total, one subtraction produces overtime. Mixing the two in the same column of a spreadsheet creates a silent error that can persist for months before anyone notices the totals are off.
The table below shows the same five shifts in both formats, with a pay column at $19.50 an hour to show exactly what happens when a decimal is misread as clock notation:
<table><thead><tr><th>Clock time</th><th>Correct decimal</th><th>Wrong decimal (literal read)</th><th>Pay at $19.50/hr — correct</th><th>Pay — wrong decimal</th><th>Error per shift</th></tr></thead><tbody><tr><td>7:30</td><td>7.50</td><td>7.30</td><td>$146.25</td><td>$142.35</td><td>−$3.90</td></tr><tr><td>8:15</td><td>8.25</td><td>8.15</td><td>$160.88</td><td>$158.93</td><td>−$1.95</td></tr><tr><td>9:45</td><td>9.75</td><td>9.45</td><td>$190.13</td><td>$184.28</td><td>−$5.85</td></tr><tr><td>6:20</td><td>6.33</td><td>6.20</td><td>$123.44</td><td>$120.90</td><td>−$2.54</td></tr><tr><td>10:48</td><td>10.80</td><td>10.48</td><td>$210.60</td><td>$204.36</td><td>−$6.24</td></tr></tbody></table>
Notice that every error goes against the employee — a literal read of clock notation as a decimal always understates the minutes, because any minute value below 60 is a smaller decimal fraction than the equivalent time-based fraction. The worst case in the table is a 10:48 shift miscalculated as 10.48 hours, a $6.24 understatement on a single day. Over a year of five-day weeks at that shift length, the error compounds to $1,622 — roughly one week's gross pay lost to one arithmetic habit.
Overtime and break deductions: converting net paid time
Converting a shift to decimal is rarely a single operation. Most payroll calculations require subtracting unpaid time first, then confirming whether what remains triggers overtime. A warehouse worker clocks in at 6:52 AM and out at 4:03 PM — that is 9 hours 11 minutes of total time. Subtract a 30-minute unpaid meal and a 10-minute unpaid rest break (policies vary by employer and state; California mandates a 30-minute off-the-clock meal for shifts over 5 hours): 9:11 − 0:40 = 8:31 paid. Convert: 8 + 31/60 = 8.5167 decimal hours, rounded to 8.52 at the employer's precision.
The overtime threshold at 8.52 hours matters in California, where daily overtime begins at 8.0 hours. The straight-time portion is 8.0 hours at the base rate; the overtime portion is 0.52 hours at 1.5× the base. At $17.00 an hour: (8.0 × $17.00) + (0.52 × $25.50) = $136.00 + $13.26 = $149.26 for that day. An employee who performs this calculation by hand and rounds 8.5167 down to 8.50 loses $0.43 on that single shift — small in isolation, but identifiable on any properly formatted pay stub.
Federal FLSA overtime applies at 40.0 decimal hours per workweek, not per day. Convert each day individually, sum Monday through Friday (or Sunday through Saturday depending on the employer's defined workweek), and compare to 40.0. A week with daily totals of 8.52, 9.00, 7.75, 8.25, and 7.83 sums to 41.35 decimal hours — 1.35 hours of federal overtime at 1.5× the regular rate. The key is performing the full day-level conversion before summing; adding clock times directly (8:31 + 9:00 + 7:45 + 8:15 + 7:50 = 41:21, then converting) yields the same result only if no arithmetic error slips into the clock addition, which is a common source of discrepancy on handwritten time cards.
Step-by-step: five real shifts converted end to end
Step 1 — write the raw punch pair. Step 2 — compute elapsed clock time (end minus start, crossing midnight if needed). Step 3 — subtract unpaid time. Step 4 — convert minutes to decimal by dividing by 60. Step 5 — round to the increment your payroll system uses. Step 6 — verify against any automated total before approving. Here is that sequence for five common scenarios.
Scenario A: 8:00 AM – 4:30 PM, 30-minute unpaid meal. Elapsed: 8:30. Minus meal: 8:00. Decimal: 8.0 exactly. No overtime under FLSA. Scenario B: 7:45 AM – 5:15 PM, 30-minute meal. Elapsed: 9:30. Minus meal: 9:00. Decimal: 9.0. Under FLSA no daily OT; under California, 1.0 hour at 1.5×. Scenario C: 10:00 PM – 6:15 AM (overnight), 30-minute meal. Elapsed: 8:15. Minus meal: 7:45. Decimal: 7 + 45/60 = 7.75. No overtime. Scenario D: 6:00 AM – 6:00 PM, two 15-minute paid rest breaks, one 30-minute unpaid meal. Elapsed: 12:00. Subtract unpaid only: 11:30. Decimal: 11 + 30/60 = 11.5. Under California, hours 8.0–12.0 at 1.5× (4.0 hours), hours 11.0–11.5 at 2.0× (0.5 hours). Scenario E: 9:00 AM – 1:20 PM, no meal break (shift under 5 hours). Elapsed: 4:20. Decimal: 4 + 20/60 = 4.3333, entered as 4.33.
Every one of those scenarios runs through the same divide-by-60 step — the only variable is what you subtract before you divide. Get that subtraction right and the arithmetic is trivial. Use the converter above on the net paid minutes whenever you are unsure of the result; the converter does not know your break policy, but it does produce the correct decimal from any hours-and-minutes input you give it.
Common mistakes payroll clerks catch too late
Entering 8.45 when the shift was 8 hours 45 minutes is the single most common hours-to-decimal error in payroll. It happens because people read the colon out of 8:45 and type the remaining digits as a decimal point and a fraction. 8.45 decimal hours is 8 hours 27 minutes, not 8 hours 45 minutes — a difference of 18 minutes, worth $5.25 at $17.50 an hour. Over a 52-week year, that one recurring error costs an employee about $1,365.
A second mistake is applying a rounding rule twice. A punch at 8:07 rounds down to 8:00 under the FLSA 7-minute rule — that is the first and only rounding step. The resulting 8:00 converts to 8.0 exactly. Some manual workflows then round 8.0 to the nearest quarter again, which leaves it at 8.0 and does no harm, but in hours where the rounded decimal is 7.25 or 7.75 a second rounding pass can shift it by 0.25 — a 15-minute error on an already-rounded figure. Apply rounding once, then convert; never convert and then round the resulting decimal.
A third pattern: summing hours and minutes separately across a week and dividing the minutes column by 60 without carrying over when that column exceeds 60. Suppose five days produce minute remainders of 45, 30, 50, 20, and 35: total is 180 minutes, which is 3 hours. If the clerk enters those minutes as 0.180 rather than converting 180 ÷ 60 = 3.0 extra hours, the week shows roughly 3 decimal hours short of the correct total. On a $20-an-hour rate that is a $60 understatement in a single week, easy to miss in a payroll run but plainly visible in an end-of-year reconciliation.
Employer rounding rules: 5-minute, 6-minute, 15-minute
The FLSA allows three common rounding increments — 5, 6, or 15 minutes — as long as the policy is neutral over a representative period. In practice most hourly employers use 15-minute rounding because it produces the simplest decimals: .00, .25, .50, .75. The 7-minute midpoint rule means punches at minutes 0–7 round to :00 and punches at minutes 8–14 round to :15, making the effective range for each quarter-hour bucket 15 minutes wide and symmetric around its midpoint.
Six-minute (0.1-hour) rounding is mandatory in legal and consulting billing and increasingly common in healthcare timekeeping. A punch at 8:04 rounds to 8:00, while 8:05 rounds to 8:06 (the nearest sixth-of-an-hour boundary). Unlike the 15-minute grid, the sixth-of-an-hour grid produces ten possible fraction values per hour: .0, .1, .2 … .9. At $350 an hour a two-minute rounding difference is worth $11.67 on a single entry, which is why legal billing software typically rounds up rather than to-nearest to protect the firm from time lost in communication lag.
Five-minute rounding appears in some healthcare scheduling systems and produces 12 fraction values per hour: .0, .0833, .1667, .25, .3333, .4167, .5, .5833, .6667, .75, .8333, .9167. These are harder to eyeball than quarter-hour values, so employers who use 5-minute rounding almost always rely on software to generate the decimals — manual entry off a 5-minute grid introduces far more transcription errors than the rounding itself saves. If you see a payslip decimal that is not on the .00/.25/.50/.75 grid and is not a clean tenth, the most likely explanation is 5-minute rounding or exact-minute tracking. Use the <a href='/minutes-to-decimal-hours'>minutes to decimal hours</a> converter to verify the figure.