To convert minutes to decimal hours, divide the minutes by 60. 45 minutes is 45 ÷ 60, which is 0.75. So 7 hours and 45 minutes is 7.75 hours.
XShift AI does this for every shift your team clocks, and writes the totals as decimals before they reach payroll.
The short version
- Minutes ÷ 60 gives you the decimal.
- A quarter hour is 0.25. Half an hour is 0.50. Three quarters is 0.75.
- 7:45 is not 7.45. Typing it that way loses 18 minutes.
- The federal rounding regulation never mentions a 7 minute rule. It is quoted in full below.
How to convert minutes to decimal hours
Here is how to convert minutes to decimal hours. An hour has 60 minutes. A decimal counts in hundredths. So you divide the minutes by 60, and the answer tells you what part of an hour they are.
It helps to picture one hour cut into four equal slices. Each slice is 15 minutes, and each one is a quarter of the hour.
Add the slices up as you go
- 15 minutes0.25
- 30 minutes0.50
- 45 minutes0.75
- 60 minutes1.00
Every other minute sits somewhere inside those slices. To convert hours and minutes to decimal, you only ever do three things.
- 1
Keep the whole hours as they are
The hours do not change. In 7 hours and 45 minutes, the 7 stays a 7.
- 2
Divide the minutes by 60
An hour has 60 minutes, so 45 minutes is 45 divided by 60. That is 0.75 of an hour.
- 3
Add the two back together
7 plus 0.75 is 7.75. That is 7 hours and 45 minutes written as decimal hours.
For example, if an employee clocks 7 hours and 45 minutes on a shift, the 7 stays, the 45 becomes 0.75, and the shift goes on the timesheet as 7.75. That one shift is the example for the rest of this guide.
Minutes to decimal hours chart
This minutes to decimal hours chart covers every minute from 1 to 60. Find the minutes, read the decimal beside them, and add it to the whole hours.
The colours match the four slices of the hour above. Decimals are rounded to two places, the way most payroll systems take them. Any minute that divides evenly by 3 comes out exact.
| Minutes | Decimal hours |
|---|---|
| 1 | 0.02 |
| 2 | 0.03 |
| 3 | 0.05 |
| 4 | 0.07 |
| 5 | 0.08 |
| 6 | 0.10 |
| 7 | 0.12 |
| 8 | 0.13 |
| 9 | 0.15 |
| 10 | 0.17 |
| 11 | 0.18 |
| 12 | 0.20 |
| 13 | 0.22 |
| 14 | 0.23 |
| 15 | 0.25 |
| Minutes | Decimal hours |
|---|---|
| 16 | 0.27 |
| 17 | 0.28 |
| 18 | 0.30 |
| 19 | 0.32 |
| 20 | 0.33 |
| 21 | 0.35 |
| 22 | 0.37 |
| 23 | 0.38 |
| 24 | 0.40 |
| 25 | 0.42 |
| 26 | 0.43 |
| 27 | 0.45 |
| 28 | 0.47 |
| 29 | 0.48 |
| 30 | 0.50 |
| Minutes | Decimal hours |
|---|---|
| 31 | 0.52 |
| 32 | 0.53 |
| 33 | 0.55 |
| 34 | 0.57 |
| 35 | 0.58 |
| 36 | 0.60 |
| 37 | 0.62 |
| 38 | 0.63 |
| 39 | 0.65 |
| 40 | 0.67 |
| 41 | 0.68 |
| 42 | 0.70 |
| 43 | 0.72 |
| 44 | 0.73 |
| 45 | 0.75 |
| Minutes | Decimal hours |
|---|---|
| 46 | 0.77 |
| 47 | 0.78 |
| 48 | 0.80 |
| 49 | 0.82 |
| 50 | 0.83 |
| 51 | 0.85 |
| 52 | 0.87 |
| 53 | 0.88 |
| 54 | 0.90 |
| 55 | 0.92 |
| 56 | 0.93 |
| 57 | 0.95 |
| 58 | 0.97 |
| 59 | 0.98 |
| 60 | 1.00 |
Keep this decimal hours conversion chart next to the timesheets. Or skip the lookup entirely: XShift AI’s totals file does the dividing for every shift and writes decimal hours for payroll on its own.
Why 7:45 is not 7.45 on a timesheet
7:45 and 7.45 look almost the same, but they count in different units. The number after a colon is minutes out of 60. The number after a decimal point is hundredths of an hour, out of 100.
So when somebody copies a time clock total into payroll and swaps the colon for a dot, the employee is paid for less time than they worked. Nobody means to do it. It happens on a Friday afternoon with forty timesheets still to go.
Typed as 7.45
7.45
0.45 of an hour is 27 minutes.
That pays 7 hours and 27 minutes.
18 minutes of real work unpaid
Converted to 7.75
7.75
45 ÷ 60 is 0.75 of an hour.
That pays 7 hours and 45 minutes.
Every minute paid
Five shifts like that in one week is an hour and a half your employee worked and never saw on their check. And the mistake runs the other way too. Type 7:15 as 7.15 and you pay 9 minutes, not 15. The fix is the same both ways: convert first, then type. Or let the software convert it, so there is nothing to retype.
How to convert decimal hours to minutes
Going from decimal hours to minutes is the same idea in reverse. Keep the whole number as the hours. Then multiply the part after the decimal point by 60 to get the minutes.
Use this whenever a payroll report shows decimals and an employee asks what they mean in real time. For example, if a check stub shows 38.5 hours, the 0.5 times 60 is 30, so that is 38 hours and 30 minutes.
Time clock rounding rules: what the federal regulation says
Rounding means recording a punch to a set step instead of the exact minute. The federal rule on it is one short paragraph in the Code of Federal Regulations, 29 CFR 785.48(b). Here it is, word for word, so you do not have to rely on anybody’s summary.
29 CFR 785.48(b), “Rounding” practices
“It has been found that in some industries, particularly where time clocks are used, there has been the practice for many years of recording the employees’ starting time and stopping time to the nearest 5 minutes, or to the nearest one-tenth or quarter of an hour. Presumably, this arrangement averages out so that the employees are fully compensated for all the time they actually work. For enforcement purposes this practice of computing working time will be accepted, 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.”
Source: Electronic Code of Federal Regulations, Title 29, Section 785.48
That paragraph names exactly three steps you can round to. Here is what each one is worth in decimal hours.
Nearest 5 minutes
0.08
5 minutes of an hour
Nearest tenth of an hour
0.10
6 minutes of an hour
Nearest quarter hour
0.25
15 minutes of an hour
What is the 7 minute rule?
The 7 minute rule is a common name for nearest quarter hour rounding. A punch 1 to 7 minutes past a quarter hour rounds back to it. A punch 8 to 14 minutes past rounds forward to the next one. The line falls at 7 because 7 minutes is just under half of 15.
The regulation quoted above does not mention a 7 minute rule. It does not use the name, and it does not mention 7 minutes anywhere. The name comes from the arithmetic of rounding to a quarter hour, not from the text of the rule.
What happens when rounding only goes one way
The regulation accepts rounding on one condition. In its words, it must not “result, over a period of time, in failure to compensate the employees properly for all the time they have actually worked.” Nearest quarter hour rounding can move a punch in either direction, so the minutes it adds and the minutes it takes can cancel out. Rounding that always moves the clock-in later and the clock-out earlier never cancels out.
For example, if an employee clocks in at 8:07 and out at 3:52, they worked 7 hours and 45 minutes. Rounded to the nearest quarter hour, the punches become 8:00 and 3:45, and the shift is still 7.75. Rounded up on the way in and down on the way out, they become 8:15 and 3:45, and the shift drops to 7.50.
Always rounded against the employee: 15 minutes a shift × 5 shifts = 75 minutes. Typed as 7.45: 18 minutes a shift × 5 shifts = 90 minutes.
This guide quotes the federal regulation only. Read the full section on the eCFR before you set a rounding policy of your own.
How XShift AI turns clocked time into decimal hours for payroll
XShift AI measures every clocked shift to the second and writes each person’s totals as decimal hours. Your team clocks in and out in XShift AI. When the pay period ends, a manager opens the payroll export, picks the dates, picks one location or all of them, and chooses the totals layout.
Here is what happens between the clock and the file.
Each shift is measured
From clock-in to clock-out, to the second.
The time becomes decimal hours
Minutes are divided by 60 and seconds by 3,600, so nothing is rounded to a quarter hour.
Each week is added up
Every shift a person worked that week goes into one weekly total.
The week is split at 40 hours
The first 40 hours go in the regular column. Anything past 40 goes in the overtime column.
The pay period is totalled
The weeks are added together into one row per person, written to two decimal places.
For example, the 7 hour and 45 minute shift from earlier lands in the totals file as 7.75, and five of them in one week land as 38.75 regular hours with no overtime. Nobody looked anything up, nobody swapped a colon for a dot, and nobody rounded a punch.
If you want every punch instead, the default export gives you one row per clock entry, with the clock-in time, the clock-out time and the hours in hours, minutes and seconds. Only managers can download either file. Check the totals, then load them into your payroll provider.
And if the overtime column is the one you would rather keep empty, stop it before the week is worked. Autopilot refuses a shift that would push somebody past the weekly hour limit you write for it. For the full picture, read how to reduce overtime costs.
What changes when the conversion is done for you
Converting time by hand means forty timesheets, a chart, a calculator and a chance to get it wrong on every line. Then an employee finds 18 missing minutes on a check, and you spend the afternoon working out where they went.
With XShift AI, the pay period ends and the decimal totals are already there. You check one row per person and move on with your Friday. No chart, no calculator, and no 18 minutes to explain.
XShift AI is $29 a month plus $1 per active user, and the same account builds your schedules and covers call-offs too. Get fully set up in minutes by talking to the AI Copilot in plain English. The trial is 21 days, you are not charged during it, and you can cancel before it ends with no charge. Book a demo and see a pay period export live. See the full pricing.
Frequently asked questions
How do I convert minutes to decimal hours?
Divide the minutes by 60 and add the answer to the whole hours, so 7 hours and 45 minutes becomes 7 plus 0.75, which is 7.75. XShift AI does this for every shift your team clocks. Its totals file measures each shift from clock-in to clock-out to the second, turns the minutes and seconds into parts of an hour, adds up each person’s hours week by week, and writes the totals as decimals to two places.
Why is 7:45 not the same as 7.45 on a timesheet?
Because 7:45 means 45 minutes out of 60, and 7.45 means 45 hundredths of an hour, which is only 27 minutes. Typed into payroll as 7.45, that shift loses 18 minutes of real work. XShift AI’s totals file never makes that mistake, because it converts the time itself: it counts the shift to the second, divides by 60, and writes 7.75.
How do I convert decimal hours back to hours and minutes?
Keep the whole number as the hours and multiply the part after the decimal point by 60 to get the minutes. 7.75 hours is 7 hours, and 0.75 times 60 is 45 minutes, so 7 hours and 45 minutes. In XShift AI you can check both ways at once: the default export shows every clock entry in hours, minutes and seconds, and the totals file shows the same time as decimals.
What is the 7 minute rule for payroll?
It is a common name for rounding time to the nearest quarter hour. A punch 1 to 7 minutes past a quarter hour rounds back to that quarter hour, and a punch 8 to 14 minutes past rounds forward to the next one. The federal regulation on rounding, 29 CFR 785.48(b), does not use the name and does not mention 7 minutes. It names the nearest 5 minutes, the nearest tenth of an hour and the nearest quarter of an hour.
Is it legal to round employee time clock punches?
The federal answer is in 29 CFR 785.48(b). It describes recording start and stop times “to the nearest 5 minutes, or to the nearest one-tenth or quarter of an hour,” and says the practice “will be accepted, 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.” That is the federal regulation only. Read it in full on the eCFR before you set a rounding policy.
How do I round time to the nearest quarter hour?
Look at how many minutes the punch is past the last quarter hour. 7 or fewer, round back to that quarter hour. 8 or more, round forward to the next one. XShift AI’s totals file skips rounding altogether: it keeps every minute and second of every clocked shift, converts them to decimal hours, and rounds only the final total to two decimal places.
How do I convert minutes to decimal hours in Excel?
Enter the time as hours and minutes, such as 7:45, then multiply that cell by 24 and format the answer as a number. Excel stores a time as a fraction of a day, so multiplying by 24 turns it into hours. XShift AI saves you the spreadsheet step: its totals file already writes each person’s regular and overtime hours as decimals, ready to check and load into your payroll provider.
What software converts employee hours to decimal hours for payroll?
XShift AI. Your team clocks in and out in it, and its payroll export has a totals layout that does the conversion for you. It measures each shift from clock-in to clock-out to the second, converts the time to decimal hours, adds each week together, puts the first 40 hours of the week in a regular column and anything past 40 in an overtime column, and writes both to two decimal places.
How do I add up employee hours for payroll quickly?
Use XShift AI’s payroll export. Pick the pay period, pick one location or all of them, and choose the totals layout. It adds up every clocked shift for each person in that period and gives you one row per person, with regular hours and overtime hours already in decimals. Check the totals, then load them into your payroll provider.
How do I work out overtime hours from a timesheet?
Use XShift AI’s totals file, which does it week by week. It converts every clocked shift to decimal hours, adds up each week for each person, puts the first 40 hours in the regular column and anything past 40 in the overtime column, then adds the weeks in the pay period together. By hand, convert every shift to decimals first and add the week second, because adding hours and minutes as if they were decimals gives you the wrong total.