Payroll Conversion Chart: Minutes to Decimal
The full 1 to 60 minute payroll conversion chart, the formula behind it, and the decimal mistake that quietly underpays your hourly staff every week.
Payroll Conversion Chart
The full minutes to decimal hours table, the formula behind it, and the one mistake that turns eight hours thirty into eight point three zero
You came here for a table, so the table is directly below and you can stop reading after it if that is all you need.
But there is one thing worth sixty seconds of your time before you go, because it is the reason this conversion exists as a problem at all. Eight hours and thirty minutes is 8.50, not 8.30. If you have ever typed the second one into a spreadsheet, and almost everybody has, you underpaid somebody by twelve minutes on that shift and the sheet looked completely fine.
That error is silent, it is systematic, and it always runs in the same direction. So: the chart, the formula, the mistake, and the point at which the chart stops being the right tool. I build FirstHR. This page will not try to sell you anything for the first thousand words, because if you run payroll for four people, a chart and a spreadsheet is a completely reasonable system and I am not going to pretend otherwise.
The Chart
Every minute from 1 to 60, in decimal hours, to two places and to four.
And if you only ever deal with quarter hours, which is most people, you need four numbers rather than sixty.
The Formula
There is only one, and it is short enough that the chart is really a convenience rather than a necessity.
Why Payroll Uses Decimals
Because you cannot multiply hours and minutes by a wage.
An hourly rate is a rate per hour. To find out what somebody earned, you multiply hours by rate. And 8 hours 30 minutes is not a number. It is two numbers wearing a colon, and there is nothing you can usefully do with it arithmetically.
Turn it into 8.5 and it becomes a number. Multiply by $22 and you get $187. That is the entire reason. It is not a payroll convention and it is not an arbitrary preference: it is the only form in which the calculation is possible, which is why every payroll system in existence stores time this way. The number it produces is the input to gross pay, and everything downstream inherits it.
The Decimal Mistake
Now the part that is actually worth your time, and the reason a page about a lookup table needs more than a lookup table.
Look at what is happening. In 8:30 the digits after the colon are minutes. In 8.30 the digits after the point are hundredths of an hour. They are different units and they look almost identical, and a tired person transcribing forty timesheets on a Friday will absolutely conflate them.
Check it in reverse if you want to be sure. 0.30 of an hour is 0.30 × 60, which is 18 minutes. So writing 8.30 records eight hours and eighteen minutes for somebody who worked eight hours and thirty minutes. You have quietly removed twelve minutes from their day.
If you find the same thing in your own sheet, the arithmetic fix takes a minute and the rest is a record: which periods, which people, how much, and what changed so it cannot happen again. Write it down while you still have the numbers in front of you, because the periods you have to reopen are the ones you will otherwise reconstruct from memory.
Decimal Hours Back to Minutes
The conversion runs the other way too, and you need it more often than you would think. Multiply the decimal part by 60 and you get minutes. 0.75 × 60 = 45, so 8.75 hours is 8 hours 45 minutes.
Three situations where you will want it. Checking a payroll register against a paper timesheet, because the register is in decimals and the timesheet is in clock times and you cannot compare them until one is translated into the other. Reading a PTO balance, since accrual balances are almost always carried in decimal hours. And sanity-checking a number that looks wrong, which is the fastest way to catch the mistake in the section above: take the 8.30 that somebody typed, multiply 0.30 by 60, get 18 minutes, and ask whether the employee really left at eighteen past.
| Decimal | Minutes | Note |
|---|---|---|
| 0.10 | 6 minutes | A tenth of an hour. This is why six-minute rounding produces clean numbers |
| 0.17 | 10 minutes | 10.2 strictly, because 0.17 is itself a rounded 0.1667 |
| 0.25 | 15 minutes | Exact |
| 0.33 | 20 minutes | 19.8 strictly. The rounding artifact shows up when you go backwards |
| 0.50 | 30 minutes | Exact |
| 0.67 | 40 minutes | 40.2 strictly, same artifact in the other direction |
| 0.75 | 45 minutes | Exact |
| 0.90 | 54 minutes | Nine tenths of an hour |
Notice what the right-hand column is telling you. The quarter hours convert exactly in both directions because 15, 30 and 45 divide cleanly into 60. Everything else does not, so a value that was rounded to two decimal places on the way in does not come back out as a whole number of minutes. That is harmless, but it is worth recognizing so that a 19.8 does not send you looking for an error that is not there.
The tenths are the ones people look up without a table. A tenth of an hour is 6 minutes, so 0.90 of an hour is 54 minutes, 0.80 is 48, and 0.40 is 24. Multiply any tenth by six and you have the minutes, which is worth knowing because PTO balances and accrual rates are usually quoted in tenths.
From Clock Times to Hours Worked
The chart converts minutes. It does not tell you how many minutes there were, and on a real timesheet that is the step people actually get wrong, because subtracting one clock time from another involves borrowing sixty rather than borrowing ten.
The reliable sequence: convert both times to the 24-hour clock, subtract, borrow 60 if you need to, then take off any unpaid break. Here is a genuinely awkward shift worked all the way through.
| Step | Working | Result |
|---|---|---|
| Clock in | 7:52 AM | 7:52 |
| Clock out | 4:38 PM, so add 12 to the hour | 16:38 |
| Subtract | 38 minutes is less than 52, so borrow an hour: 15:98 minus 7:52 | 8 hours 46 minutes |
| Unpaid meal break | 8 hours 46 minutes minus 30 minutes | 8 hours 16 minutes |
| Convert the minutes | 16 ÷ 60 = 0.2667 | 8.2667 hours |
| Round to two places | 8.2667 | 8.27 hours |
| Gross at $18/hr | 8.2667 × 18 | $148.80 |
The wrong version of that day is 8.16 hours, which pays $146.88. Under two dollars, on one shift, for one person. Run it five days a week for a crew of six and it is a number you would notice if it were a single invoice.
Two variants worth knowing. A shift that crosses midnight cannot be subtracted directly: 9:15 PM to 5:40 AM is not 5:40 minus 21:15. Add 24 hours to the clock-out first, so 29:40 minus 21:15 gives 8 hours 25 minutes, or 8.4167. Separately, when a shift straddles the boundary of your defined workweek you also have to decide which week those hours belong to for overtime purposes, and that is a workweek-definition question rather than a conversion question. Whatever you decide, apply it the same way every time.
Reading a Decimal Time Clock Export
A decimal time clock reports totals in hundredths of an hour, so the figure it hands you is already converted and 8.27 does not mean eight hours and twenty-seven minutes. It means 8 hours and 16 minutes, because 0.27 times 60 is 16.2. Most time card exports work the same way.
Three things to check the first time you open one of these files. Whether the total column is decimal hours or hours and minutes, because some clocks produce both and the header rarely says which. Whether the device already deducted an unpaid break. And whether it rounded the punches before totaling them.
Reconcile one employee against the raw punches before you trust the totals for everybody. If the export and your own subtraction of the in and out times disagree by a few minutes, the gap is either the rounding or a break rule, and it is much cheaper to find out which in week one than after a year of it.
Converting a Full Timesheet
The order of operations matters more than people expect, and doing it in the wrong order is a second, separate way to get the number wrong.
Rounding, and the Legal Catch
Rounding and converting are two different operations and it is worth keeping them separate in your head. Converting is arithmetic and it has one right answer. Rounding is a policy, it is optional, and it has legal constraints attached.
You are permitted to round. Per 29 CFR 785.48, the practice of recording starting and stopping times to the nearest 5 minutes, or to the nearest tenth or quarter of an hour, is accepted for enforcement purposes, provided that it is used in such a manner that it will not result, over a period of time, in failure to compensate the employees properly for all the time they have actually worked.
Which is a genuinely uncomfortable finding, because it means the compliance question is not answerable by reading your own policy. It is answerable only by looking at the data and checking which way it actually landed. The Department of Labor spells out the mechanics in Fact Sheet 53: time from 1 to 7 minutes may be rounded down, but time from 8 to 14 minutes must be rounded up and counted as a quarter hour.
The audit itself is mechanical. Take a sample of real shifts, put the actual punch next to the rounded punch, work out the difference in minutes on each one, and add up which direction the differences went. If the total leans toward the employer across a period, you have your answer regardless of how even-handed the rule reads. The time clock rounding guide has a worksheet for running that comparison and a plan for fixing a policy that fails it.
The simplest way to avoid the whole problem, and it is genuinely available to a small business in a way it was not in 1938: do not round at all. Pay the actual minutes. The regulation exists because mechanical punch clocks and hand-calculated payroll made precision impractical. If your hours are already in a spreadsheet, that justification does not apply to you.
How Many Decimal Places
Two is standard. Four is better in one specific circumstance, and it is worth knowing which one you are in.
| Two decimal places | Four decimal places | |
|---|---|---|
| Example: 20 minutes | 0.33 | 0.3333 |
| Example: 10 minutes | 0.17 | 0.1667 |
| Example: 40 minutes | 0.67 | 0.6667 |
| Precision | A hundredth of an hour is 36 seconds | A ten-thousandth of an hour is under half a second |
| Right for | Most small businesses. Perfectly adequate | Many employees, many partial hours, or where the rounding is applied hundreds of times a month |
| The risk | If you always round down rather than to nearest, the error accumulates in one direction | Effectively none, but it is more digits to type and to check |
The rule that actually matters is not the number of places. It is that you round to the nearest rather than always down. Two decimal places, rounded to nearest, is fine forever. Two decimal places, always rounded down, is a rounding convention that has quietly become an underpayment policy, and the fact that each individual instance is worth a few seconds is precisely what makes nobody look at it.
Converting a Salary to an Hourly Rate
Divide the annual salary by 2,080. Forty hours a week across fifty-two weeks is 2,080 hours, and that is the standard divisor. A $50,000 salary is $24.04 an hour. A $100,000 salary is $48.08 an hour.
You reach for this more often than you would expect. Pricing a new role against hourly market rates, comparing a salaried candidate with an hourly one, or working out what an hour of somebody's time costs before you commit them to a project. All three start with the same division.
| Annual salary | Hourly at 2,080 hours | Per 40-hour week |
|---|---|---|
| $30,000 | $14.42 | $576.92 |
| $40,000 | $19.23 | $769.23 |
| $50,000 | $24.04 | $961.54 |
| $60,000 | $28.85 | $1,153.85 |
| $75,000 | $36.06 | $1,442.31 |
| $100,000 | $48.08 | $1,923.08 |
| $120,000 | $57.69 | $2,307.69 |
It runs backwards just as easily. Multiply an hourly rate by 2,080 and you get the annual equivalent, so $25 an hour is $52,000 a year and $18 an hour is $37,440. That is the figure to quote when somebody asks what an hourly role is worth over a year, and it is the same arithmetic used on the salary versus hourly decision.
How Many Payroll Hours Are in a Year
2,080, by convention. It is forty times fifty-two, and it is a divisor rather than a count of actual working days, which land between 260 and 262 depending on how the calendar falls. Almost nobody works 2,080 hours exactly, and it is still the right number to budget against.
It also lines up with how you pay. Twenty-six biweekly runs of 80 hours is 2,080. Twenty-four semimonthly runs works out at 86.67 hours each, which is why semimonthly payroll never gives you round hour figures. How the calendar splits those runs is a pay period question rather than a conversion one.
If the role is not a forty-hour role, use the hours you actually schedule. A thirty-hour week is 1,560 hours a year, and running a part-time salary through the 2,080 divisor understates the hourly rate by a quarter.
Doing It in a Spreadsheet
If you are converting more than a few values a week, stop looking them up. The lookup is where transcription errors come from, and the formula is one cell.
The thing to understand first, because it explains every odd result you will get: Excel and Google Sheets store a time as a fraction of a day, not as a number of hours. 6:00 AM is 0.25. Noon is 0.5. So subtracting one time from another gives you a fraction of a day, and multiplying by 24 turns it into decimal hours. That single fact accounts for most of the confusion people have with time in spreadsheets.
| What you want | Formula | What to watch |
|---|---|---|
| Decimal hours from clock in and clock out | =(B2-A2)*24 | Type the times with a colon, as 7:52 AM, so the cell is stored as a time rather than as the number 752 |
| Same, but the shift crosses midnight | =MOD(B2-A2,1)*24 | Without MOD you get a negative number, because the clock-out looks earlier than the clock-in |
| Subtract an unpaid break entered in minutes | =(B2-A2)*24-C2/60 | The break is minutes, so it gets divided by 60 like any other minutes |
| Decimal hours from hours and minutes in two columns | =D2+E2/60 | Only the minutes column is divided. This is the chart, as a formula |
| Round to the nearest quarter hour | =MROUND(F2,0.25) | Rounds to nearest in both directions, which is the behavior the rounding regulation expects |
| Round to the nearest tenth of an hour | =MROUND(F2,0.1) | A tenth of an hour is six minutes |
| Round to the nearest five minutes | =MROUND(F2,1/12) | Five minutes is a twelfth of an hour |
| Weekly total | =SUM(F2:F8) | Works normally because these are plain numbers, not times |
Three traps, in descending order of how often they bite.
The first is formatting. When you subtract two time cells the result inherits time formatting, so =(B2-A2)*24 can display as something that looks like a clock reading rather than 8.27. The number underneath is correct; the display is not. Set the result column to Number with two decimal places and the problem disappears permanently.
The second is summing times rather than decimals. A column of durations kept in time format totals wrongly past 24 hours, because the format wraps at a day and 26 hours displays as 2:00. The fix is either the [h]:mm custom format or, better, converting each day to a decimal first and summing plain numbers. Which is the same advice as in the timesheet section, arrived at from a different direction.
The third is FLOOR. It is tempting because it produces tidy numbers, and =FLOOR(F2,0.25) is a policy of always rounding down dressed up as a spreadsheet function. Use MROUND. If you want to be certain you never have this argument, skip the rounding formula entirely and pay the actual decimal hours.
When the Chart Is Not Enough
Honest answer, and it is not the one a software company is supposed to give.
Notice what actually changes across those rows, because it is not what you would expect. The arithmetic never gets harder. Minutes divided by 60 is the same operation whether you have two employees or two hundred.
What gets harder is the transcription. Hours read off a paper timesheet, typed into a spreadsheet, by a person, on a Friday. Every one of those steps is a place for a digit to go missing, and the number of those steps scales directly with headcount while the difficulty of the division does not. Which means the case for a tool is never really about the conversion. It is about removing the retyping.
Common Mistakes
The unifying feature of all of them is that they are invisible. A conversion error does not produce a number that looks wrong. It produces a number that looks completely plausible and is quietly short, on every partial shift, for as long as nobody checks.
And the records are the thing that decides how that ends. Under the Fair Labor Standards Act, you are the party required to keep accurate records of hours worked, and per the DOL guidance on FLSA recordkeeping, those records must show the hours worked each day and each week. Which means in a dispute about whether somebody was paid for the time they worked, the burden of producing the evidence sits with you, and a spreadsheet that has been quietly converting wrong is not a defense.
Which is why the sixty seconds at the start of this page were worth more than the table. The table you can look up any time. The knowledge that 8.30 is a trap is the thing that stops you needing to.
Frequently Asked Questions
What is a payroll conversion chart?
A payroll conversion chart is a reference table that converts minutes into decimal hours, so that time worked can be multiplied by an hourly rate. Payroll systems and spreadsheets work in decimals rather than in hours and minutes, which means 8 hours and 30 minutes has to become 8.5 before you can multiply it by anything. The chart simply lists every minute from 1 to 60 alongside its decimal equivalent, and it exists so that whoever is running payroll does not have to do the division sixty times a week.
How do you convert minutes to decimal hours for payroll?
Divide the minutes by 60. That is the entire formula and there is nothing else to it. 30 minutes divided by 60 equals 0.5, so 8 hours and 30 minutes is 8.5 hours. 45 minutes divided by 60 equals 0.75, so 7 hours and 45 minutes is 7.75 hours. The reason a chart exists at all is not that the calculation is hard, it is that doing it in your head sixty times while also running payroll is where mistakes come from.
What is 30 minutes in payroll time?
0.50 hours. Half an hour is half of one, so it is 0.5 in decimal. This is the single most looked-up value in payroll conversion and it is also the one that produces the most common error, because 8 hours and 30 minutes is 8.50 hours, not 8.30. Typing the minutes straight after the decimal point feels natural and it is wrong, and in this specific case it underpays the employee by 0.2 hours on every shift.
What is 15 minutes in decimal for payroll?
0.25 hours. A quarter of an hour is a quarter of one. Similarly, 45 minutes is 0.75 and 60 minutes is 1.00. Those four values, being 0.25, 0.50, 0.75, and 1.00, cover the overwhelming majority of real timesheets, because most shifts start and end near a quarter hour. If you memorize nothing else from this page, memorize those four and you will rarely need to look anything up.
What is 10 minutes in payroll time?
0.17 hours to two decimal places, or 0.1667 to four. Ten divided by sixty is 0.16666 recurring, which is one of the values that does not come out cleanly and where the number of decimal places you carry starts to matter. Six minutes, by contrast, is exactly 0.10, which is why some employers round to the nearest six minutes rather than the nearest fifteen: it produces clean tenths of an hour and the arithmetic stays tidy.
Why does payroll use decimal hours instead of minutes?
Because you cannot multiply hours and minutes by a wage. An hourly rate is a rate per hour, so to work out what somebody earned you have to multiply hours by rate, and 8 hours 30 minutes is not a number you can multiply by anything. Converting it to 8.5 makes it a number. It is not a payroll convention or an arbitrary choice: it is the only way the arithmetic works, and every payroll system in existence stores time this way for exactly that reason.
Is 8 hours 30 minutes 8.30 or 8.50?
8.50, and getting this wrong is the most common error in manual payroll. The instinct is to write the minutes after the decimal point, because that is how a clock reads. But the decimal point does not mean minutes, it means fractions of an hour, and 30 minutes is half an hour, so it is 0.5. Writing 8.30 means eight hours and eighteen minutes, because 0.30 of an hour is 18 minutes. You have just shortchanged the employee by twelve minutes without noticing.
How do I calculate total hours for payroll from a timesheet?
Work each day separately, then total. For each day, subtract the start time from the end time to get hours and minutes worked, then subtract any unpaid break, then convert the minutes to a decimal. Once every day is in decimal hours, add the days together to get the weekly total. Do the conversion before you add rather than after, because adding hours and minutes together and then converting is where people lose track of whether they carried the sixty.
How do I convert an annual salary to an hourly rate?
Divide the annual salary by 2,080, which is forty hours a week across fifty-two weeks. A $50,000 salary works out to $24.04 an hour, and $100,000 works out to $48.08. It runs backwards by multiplying, so $25 an hour is $52,000 a year. Two cautions attach to it. If the role is not a forty-hour role, divide by the hours you actually schedule, because a thirty-hour week is 1,560 hours a year and running it through 2,080 understates the rate by a quarter. And the result is a budgeting figure rather than an overtime rate: for a salaried non-exempt employee, the regular rate is the salary divided by the number of hours that salary was intended to compensate, which is not automatically forty.
Should I round employee time before converting it?
You may, within limits, and you have to be careful. Federal regulation permits rounding time to the nearest five minutes, tenth of an hour, or quarter hour, but only if the rounding does not, over a period of time, fail to compensate employees properly for the time they actually worked. In other words it has to be neutral in effect and not merely neutral in appearance. A policy that rounds in both directions but where employees habitually arrive early and leave on time will systematically favor the employer, and that is a problem regardless of how the rule was written.
How many decimal places should I use for payroll?
Two is standard and sufficient for most small businesses. Four is better if you have a lot of employees or a lot of partial hours, because a hundredth of an hour is 36 seconds and rounding to two places on every entry, in the same direction, adds up across a workforce. The practical rule is that two decimal places are fine as long as you are rounding to the nearest hundredth rather than always rounding down, since always rounding down is what turns a rounding convention into an underpayment.
What is 1 minute in decimal hours?
0.02 to two decimal places, or 0.0167 to four. One minute divided by sixty is 0.01666 recurring, which is a good illustration of why single minutes are where precision starts to matter. On a single shift it is nothing. Across a workforce of twenty people over a year it becomes real money, particularly if the rounding always goes the same way, which is exactly the situation the FLSA rounding rules exist to prevent.
Do I need to convert minutes if I use payroll software?
No. Any payroll system does this automatically, and if your hours are flowing in from a timekeeping system rather than being typed by a person, the conversion is invisible and you never think about it. The reason this page exists is that a great many small businesses are still doing it by hand, on paper timesheets typed into a spreadsheet, and that is a completely legitimate way to run payroll at a small enough size. It just has a specific failure mode, and knowing what it is means you avoid it.
What is the difference between 0.5 and 0.50 hours?
Nothing. They are the same number, and the trailing zero is just a formatting choice. Where it matters is legibility: a column of numbers written to two decimal places is much easier to scan and check than a column where some values have one decimal place and some have two. If you are doing this in a spreadsheet, format the column to a fixed number of decimal places, because inconsistent formatting is how a 0.5 gets read as a 0.05 by a tired person on a Friday.
Does the conversion change for overtime?
No. The conversion is exactly the same, and it happens first. You convert the time worked to decimal hours, you total the week, and then you work out which of those hours are overtime and apply the multiplier. What does change is the consequence of getting the conversion wrong: an error in the hours flows into the overtime calculation and gets multiplied by one and a half, so a small conversion mistake becomes a larger overtime mistake.
Is it legal to round employee hours down?
Not systematically, no. Federal regulation permits rounding, but it must not result, over a period of time, in a failure to properly compensate employees for the time they actually worked. An employer who always rounds down is failing that test on its face. The subtler version is an employer whose policy rounds both ways but whose employees consistently clock in early and out on time, so that the rounding lands in the employer's favor in practice. Neutral on paper is not the standard. Neutral in effect is.
What is a decimal hour?
An hour expressed as a decimal number rather than as hours and minutes. 1.5 decimal hours is one hour and thirty minutes. 0.25 decimal hours is fifteen minutes. It is simply a different notation for the same quantity of time, and payroll uses it because it is the notation you can do arithmetic in. The confusion arises because both notations use a dot and they mean completely different things: in 8:30 the part after the colon is minutes, and in 8.30 the part after the point is hundredths of an hour.
How do I convert decimal hours back into minutes?
Multiply the decimal part by 60. So 8.75 hours means 0.75 times 60, which is 45 minutes, giving 8 hours and 45 minutes. This is worth knowing because it is how you sanity check a number that looks wrong. If a timesheet says 8.30 hours and you multiply 0.30 by 60, you get 18 minutes, and if the employee actually worked 30 minutes past the hour then somebody has made exactly the error this page is about.
Why do some charts show four decimal places?
Because most minute values do not convert cleanly. Twenty minutes is 0.3333 recurring, forty minutes is 0.6667, ten minutes is 0.1667. To two decimal places those become 0.33, 0.67, and 0.17, which involves a small rounding at every entry. For a business with three hourly employees that is irrelevant. For one with thirty, where the rounding is applied hundreds of times a month, carrying four places removes a source of drift that would otherwise accumulate quietly in one direction.
Can I just use a payroll conversion chart forever?
For a very small team, honestly yes, and anybody who tells you a three-person business needs a time-tracking platform is selling you one. The chart is not the weak point. The weak point is transcription: hours being read off a paper timesheet and typed into a spreadsheet by a human being on a Friday afternoon. That is where errors enter, and it is a problem that gets worse with headcount rather than with arithmetic. The chart scales fine. The typing does not.
What happens if I underpay someone because of a conversion error?
You owe them the difference, and if it went on for a while and touched overtime, you may owe more than you think. Wage and hour claims are not forgiving of the explanation that it was a spreadsheet error, and because a conversion mistake is systematic rather than random, it typically affects every employee and every pay period rather than just one. Which means an error worth a few dollars a shift becomes a real number once it is multiplied by your headcount and the months it ran for.