To prepare payroll from time tracking, close the pay period, clear every missing or odd punch, apply break and overtime rules by workweek, get employee confirmation and manager approval, then export approved hours by pay category into your payroll system. Do those steps in the same order every period and payroll stops being a scramble. This guide walks through each step, with the U.S. rules that affect the math.
TL;DR
- Set a cutoff, then clear exceptions (missed punches, open shifts, edits) before you calculate anything.
- Calculate overtime by workweek, not by pay period. Federal overtime generally starts after 40 hours in a workweek.
- Export hours by category (regular, overtime, leave, premium), mapped to each employee's payroll ID.
- Keep an approval trail: who approved what, what changed and why.
- Keep payroll records at least three years and time cards at least two years under federal rules for covered non-exempt employees.
Table of Contents
- What "payroll-ready" time data looks like
- Step 1: Set a cutoff and close the period
- Step 2: Clear exceptions first
- Step 3: Convert time into pay-ready numbers
- Step 4: Apply overtime rules by workweek
- Step 5: Employee confirmation and manager approval
- Step 6: Export to payroll
- Step 7: Archive the period and keep records
- Perspective: why we built time to payroll as one flow
- Build a repeatable calendar
- Common mistakes to avoid
- Let Heyhive assemble the hours
- FAQ
- Sources
What "payroll-ready" time data looks like
Raw punches are not payroll-ready. A clock-in at 8:02 and a clock-out at 4:34 tell you nothing about breaks, overtime or pay rate. Payroll-ready data is a clean record per employee, per period, split by what the hours are.
A useful export carries these fields:
- Employee identifier that matches your payroll system
- Pay period and workweek boundaries
- Regular hours
- Overtime hours
- Holiday or premium hours
- Paid leave and unpaid leave
- Location, job or cost center, if you allocate labor costs
Keeping categories separate matters because each one is paid differently. A single "total hours" number forces someone to rebuild the split by hand, and that is where errors creep in.
Step 1: Set a cutoff and close the period
Pick a fixed time when the period closes, such as Monday at 9 a.m. for the week that ended Sunday. Tell employees the cutoff in writing and repeat it in your team messaging channel. A cutoff gives everyone a deadline for fixing punches and requesting time off adjustments, and it gives you a stable data set to calculate from.
After the cutoff, changes should go through a documented correction request, not a quiet edit. That one habit protects you later when someone asks why a number changed.

Step 2: Clear exceptions first
Do not review every timecard line by line. Review the exceptions, then trust the clean records. The usual suspects:
- Missing or open punches: a clock-in with no clock-out, or the reverse.
- Shifts far longer or shorter than scheduled: compare each punch with the schedule.
- Missed or short breaks: especially where your state requires meal periods.
- Manual edits: anything changed after the fact.
- Off-site punches: for field and multi-site teams, a punch that does not match the job location.
This is where a GPS-verified time clock earns its keep. When arrival and departure are tied to a location, an off-site punch is flagged instead of discovered after the paychecks go out. Our guide to GPS time clock software covers how that verification works for mobile crews. For the review routine itself, see how an exceptions-first approach cuts approval time in this schedule approval workflow.
Handle changing shifts and multiple sites
Shifts that rotate and teams that split time across locations raise the error rate. For each scheduled employee, check the daily record, any open punches, workweek totals, breaks and the state rules that apply where the work happened. Log each exception and its resolution. If one person worked at two sites at two different pay rates, the hours need to be tagged by site or job so the right rate applies.
Step 3: Convert time into pay-ready numbers
Payroll systems usually want decimal hours, not hours and minutes. Divide the minutes by 60 and add them to the hours.
| Tracked time | Calculation | Decimal hours |
|---|---|---|
| 8 h 20 min | 20 ÷ 60 = 0.33 | 8.33 |
| 7 h 45 min | 45 ÷ 60 = 0.75 | 7.75 |
| 6 h 30 min | 30 ÷ 60 = 0.50 | 6.50 |
Two habits keep the conversion clean:
- Subtract unpaid breaks before you classify overtime. Otherwise, break time inflates the hours that count toward the threshold.
- Apply one documented rounding rule, once. Rounding every punch and then rounding the total compounds the difference. Decide on your rule, write it down and apply it at a single point. Federal guidance says rounding practices must not consistently shortchange employees, so check the rule against the Department of Labor's recordkeeping guidance or your payroll advisor before you adopt it.
Step 4: Apply overtime rules by workweek
This is the step that causes the most underpayment. Under the federal Fair Labor Standards Act (FLSA), covered non-exempt employees generally get at least one and one-half times their regular rate for hours over 40 in a workweek, and the Department of Labor says overtime is calculated by workweek. The regular rate can include things like nondiscretionary bonuses and commissions, not just the hourly wage.
The workweek is the unit, not your pay period. If you pay biweekly, you still calculate each week on its own:
| Week 1 | Week 2 | Biweekly total | |
|---|---|---|---|
| Hours worked | 50 | 30 | 80 |
| Overtime hours | 10 | 0 | 10 |
Averaging to 40 hours a week would show zero overtime. The correct answer is 10 overtime hours for week 1. Our FLSA overtime rules guide goes deeper on what HR needs to do, and if you pay a salary for fluctuating hours, read the fluctuating workweek method rules before you apply them.
Check your state and local rules
The FLSA is the floor. State laws may require a higher minimum wage or different treatment of breaks, tips and overtime, and the Department of Labor notes this on its FLSA fact sheet. Build the stricter rule into your pay configuration. If you operate in more than one state, set rules per location, not company-wide. Confirm specifics with your state labor department or a payroll professional.
Paid leave and premium pay
Track vacation, sick time and holidays as their own categories. They are paid, but paid time off is generally not counted as hours worked toward the overtime threshold. For hourly PTO, a consistent method avoids drift between what employees accrue and what they are paid. See how to stop accrual drift with hourly PTO tracking.
When someone works at more than one rate, or earns shift, weekend or holiday premiums, those amounts feed the regular rate used for overtime. Flag these employees in your review so the blended rate is calculated, not skipped.

Step 5: Employee confirmation and manager approval
Approval is the control that separates a payroll process from a guess. The sequence is simple:
- Employees review their hours and confirm them.
- Managers review exceptions, correct what is wrong and approve.
- Payroll or the owner reviews totals and a payroll preview.
Large institutions treat this as a requirement. University payroll offices tell employees to attest to their timecards and managers to review, correct and approve them, as in UCSF's pay period close guide. The University of Arizona's supervisor time approver practice states that supervisors must review their direct reports' time and that blind approval is not permitted. A small business does not need that bureaucracy, but it should hold to the same principle: a person looks at the numbers before money moves.
For a deeper look at running this well, see our manager's guide to timesheet approvals.
Keep an approval trail
Record who reviewed the hours, what was corrected and why. A note like "missed clock-out, confirmed with employee by text, corrected to 5:00 p.m." is enough. This trail answers disputes in minutes. Errors found after approval should go through a formal correction, not an overwrite; the same principle applies in other countries, and this walkthrough on fixing payroll errors shows how a correction process is structured in Portugal.
Step 6: Export to payroll
The handoff is where manual rekeying causes the worst mistakes. Whether you upload a file or sync directly, follow the same rules:
- Map each person by one ID. Use the payroll employee ID or time-clock ID, and make sure both systems agree.
- Export approved periods only. Unapproved time should never reach payroll.
- Keep categories separate. Regular, overtime and leave belong in their own columns or rows.
- One pay frequency per file. Do not mix weekly and biweekly employees.
- Do not rename or reorder required headers in a CSV template. Import tools often reject the file or misread the columns.
- Read import warnings. Then compare imported regular hours with what payroll shows before you approve the run.
If you reconcile after each run, you catch small drift before it becomes a pattern. We lay out an eight-step method in our U.S. payroll reconciliation workflow, and the thinking behind removing rekeying is in no-rekeying controls for time to payroll.
Step 7: Archive the period and keep records
Once payroll runs, archive the approved timecards, the export file, the exception log and the payroll preview together. Under the FLSA, the Department of Labor's recordkeeping fact sheet says employers must keep payroll records for at least three years, and the supporting wage-computation records, such as time cards and schedules, for at least two years. The records for covered non-exempt employees include:
- Employee identity and workweek start
- Hours worked each day and each week
- Pay basis and regular rate
- Straight-time and overtime earnings
- Additions and deductions, total wages and payment date
- The pay period covered
The same fact sheet says no particular timekeeping format is required. A time clock, a timekeeper or employee-entered time all work if the record is complete and accurate. State rules can require longer retention, so confirm with your state labor department.
Perspective: why we built time to payroll as one flow
We see the same pattern in restaurants, retail, service crews and field teams. The problem is rarely the math. It is the handoffs: a schedule in one place, punches in another, messages in a third, and a spreadsheet stitching them together on payday.
That is why Heyhive puts scheduling, the GPS time clock, attendance tracking and payroll-ready hours export in one interface. When the schedule and the punches live together, exceptions show up where you can see them, and you approve hours before they leave the building.
We believe AI should do the repetitive work and managers should keep the decisions. Our AI scheduling is designed to respect availability, certifications and overtime limits, and you approve before anything is published. Payroll prep works the same way: the platform assembles the hours, and you stay in control of what gets approved.
Heyhive
Build a repeatable calendar
A workflow only works if it runs on a schedule. Here is a simple weekly rhythm for a weekly workweek and a biweekly payroll:
| When | Action |
|---|---|
| Throughout the week | Fix missed punches as they happen |
| Workweek end | Employees confirm hours |
| Cutoff time | Lock the period, review exceptions |
| Day after cutoff | Manager approvals complete |
| Payroll day minus 2 | Export, import, compare, review preview |
| Payroll day | Approve and run payroll |
| After payroll | Archive and log corrections |
Adjust the days to your processing deadlines. Banks and payroll providers set their own submission cut times, so back your own deadlines out from theirs.
Common mistakes to avoid
- Averaging hours across weeks instead of calculating each workweek.
- Counting paid leave as hours worked toward overtime.
- Rounding more than once and drifting from actual time.
- Editing punches without a note, leaving no trail.
- Skipping state rules because the federal rule looked fine.
- Exporting before approval, which moves errors into payroll.
- Letting different IDs coexist, so hours land on the wrong employee.
For teams still deciding how to capture time, timesheets or a time clock is worth settling first, since the capture method shapes how many exceptions you face. Once you have clean data, attendance data reporting helps you spot patterns like chronic late arrivals before they hit payroll.
Let Heyhive assemble the hours
If you prepare payroll by hand from punches, messages and spreadsheets, you can cut the work down. With Heyhive, payroll-ready hours come from the same place you schedule and track time. Employees clock in with a GPS-verified time clock, you review exceptions, you approve, and you export hours ready for payroll.

Heyhive also generates full weeks of shifts in seconds with AI scheduling, so the schedule that sets expected hours and the time records that prove them stay connected. You can start free on Heyhive and see your own period close in one place.
FAQ
How do I calculate payroll hours from a time clock?
Subtract unpaid breaks from each shift, then convert minutes to decimals by dividing by 60. For example, 8 hours 20 minutes becomes 8.33. Add the daily totals for each workweek, and separate regular hours from overtime before you multiply by pay rates.
Is overtime calculated weekly or per pay period?
Weekly. Under the FLSA, covered non-exempt employees generally earn overtime for hours over 40 in a workweek, even if you pay biweekly. A 50-hour week followed by a 30-hour week still has 10 overtime hours. Your state may add its own rules, so check with your state labor department.
What should I check before approving timesheets?
Look for missing or open punches, shifts that differ sharply from the schedule, missed breaks, manual edits and off-site punches. Then check each employee's workweek total against overtime thresholds. Log any correction with who made it and why.
How long do I need to keep payroll and time records?
For employees covered by the FLSA, the Department of Labor requires payroll records for at least three years and time cards and schedules for at least two years. Some states require longer, so confirm the rule where you operate.
Sources
- Fact Sheet #21: Recordkeeping Requirements under the FLSA (U.S. Department of Labor)
- Fact Sheet #76: FLSA overtime and state law (U.S. Department of Labor)
- Pay Period Close Quick Reference Guide (UCSF Controller's Office)
- Supervisor Time Approver Required Practice (University of Arizona)
- Payroll Corrections in Portugal: How to Fix Errors
