
FOX
WorkEasy Software recognized as a Top 25 Global Work Tech Vendor. Work Tech Awards honor best-in-class vendors.
Six clock-in and clock-out rules that change paid hours before anyone looks, a worked example of each, the federal rule behind it and the setting that fixes it.

She clocked in at 9:03. Her time card says 9:06, and she wants to know why her time was changed. Down the hall, the night crew can't clock back in after midnight, and somebody is splitting a 10 p.m. to 4 a.m. shift by hand at 11:59 p.m. Payroll has a 30-minute lunch coming off the first job of the day instead of the job someone was actually on at noon. None of these are software bugs. They're clock-in rules doing exactly what they were set to do, which isn't what anyone meant.
Here are six clock-in and clock-out rules that commonly cause payroll errors, a worked example of each, what federal law says, and the setting that fixes it.
A note on the law. This article explains federal wage and hour rules in general terms. It isn't legal advice. State and local laws can be stricter, and the right setup depends on your workforce, so check with an employment attorney or your state labor department before you change how you round time, deduct breaks or count overtime.
Clock-in and clock-out rules cause payroll errors when the rule the software applies isn't the rule the business meant, or when two rules collide. The usual culprits are rounding that always favors one side, a workweek that starts on a different day than payroll expects, overnight shifts that land on the wrong day or week, automatic meal deductions taken when no break happened, early clock-ins that turn into unapproved overtime, and forgotten clock-outs that create 20-hour shifts. Each one changes the hours before anyone looks at a timesheet, so the error reaches the paycheck unless someone catches it. The fix is to write each rule down, set it once in your time and attendance system, test it on a real week of punches and review exceptions before payroll closes. WorkEasy Software applies rounding, break, overtime and punch rules by company, group or employee and flags exceptions before payroll.
Already found a paycheck that came out wrong? Talk to us about how your rules are set.
What goes wrong. Rounding is meant to make punches easier to read, not to change pay. It goes wrong when it always rounds the same way, for example rounding clock-ins up and clock-outs down, or when employees see a different time on their time card and assume they've been shorted.
Example. Quarter-hour rounding (the "7-minute rule") turns a 7:07 clock-in into 7:00 and a 7:08 clock-in into 7:15. If the rule always rounds clock-ins up to the next quarter hour and clock-outs down, an employee who clocks in at 6:56 and out at 3:08 is paid from 7:00 to 3:00. That's 12 minutes lost a day, an hour a week.
What the law says. Department of Labor rules allow rounding to the nearest 5 minutes, tenth or quarter hour if, over time, employees are paid for all the time they actually work (29 CFR 785.48(b)). Some states are stricter.
The fix. Use neutral rounding (or none), apply it the same way to clock-ins and clock-outs, keep the actual punch visible next to the rounded one, and check your state's rules before you round meal breaks. Check a month of rounded vs actual totals: they should come out close.
What goes wrong. Federal overtime is calculated per workweek. If your time system's workweek starts on Sunday and payroll assumes Monday, or one site starts on Saturday, hours land in the wrong week and overtime is paid in one week and missed in the other.
Example. An employee works 40 hours Monday to Friday, then 10 hours on Saturday and 10 on Sunday. With a Monday-to-Sunday workweek, that's 60 hours and 20 hours of overtime. With a Sunday-to-Saturday workweek, Sunday's 10 hours belong to the next week: 50 hours and 10 hours of overtime this week. Same punches, different paycheck.
What the law says. A workweek is a fixed, recurring seven-day period that can start on any day and hour. It can be changed if the change is intended to be permanent and not made to avoid overtime, and overtime can't be averaged across two or more workweeks (29 CFR 778.104 and 778.105).
The fix. Pick one fixed workweek per pay group, set it in your time system, and make sure payroll uses the same one. If you change it, do it at a pay period boundary and check the transition week.
What goes wrong. A shift that starts at 10 p.m. and ends at 6 a.m. belongs to two calendar days. If the system isn't set up for overnight work, employees can't clock back in after midnight, punches get duplicated, or hours split across days in a way that breaks daily overtime or shift differentials. Daylight saving weekends add or remove an hour in the middle of the shift.
Example. A warehouse worker on 10 p.m. to 6 a.m. Saturday into Sunday, with a Sunday workweek start: two hours belong to the old week and six to the new one. If the system puts all eight on Saturday, Sunday's week is short and overtime may be missed.
The fix. Decide how overnight shifts are assigned to days and weeks, set it once, and test it on a real overnight shift before go-live and after every daylight saving change. Make sure each clock's location is set to the right time zone.
What goes wrong. Someone forgets to clock out on Friday and clocks in on Monday. Without a limit or an alert, the system sees one very long shift, or an open punch that payroll has to guess at.
Example. An employee clocks in at 6:00 a.m. Friday and forgets to clock out. The next punch, Monday at 6:00 a.m., is read as a clock-out: a 72-hour shift and a week of phantom overtime, unless a manager catches it.
The fix. Set an alert for forgotten clock-outs that goes to the employee and the manager the same day, cap the length of a shift that can be approved without review, and require a manager to approve any fix.
What goes wrong. Automatic lunch deductions save time when everyone takes lunch. They cause errors when someone works through lunch, when the deduction comes off the wrong job or department, or when two break rules overlap and deduct twice.
Example. A rule deducts 30 minutes after 5 hours worked. A nurse who covers the floor through lunch on a 10-hour shift is paid for 9.5 hours instead of 10. Over a year of busy Fridays, that adds up to unpaid work.
What the law says. Bona fide meal periods, ordinarily 30 minutes or more with the employee completely relieved of duty, don't have to be paid (29 CFR 785.19). If the employee works, it's paid time. Many states have their own meal and rest break rules.
The fix. Deduct only when no break was punched, or have employees confirm breaks at clock-out. Make sure the deduction comes off the job the employee was on, and send missed-break alerts to managers. Review overlapping break rules.
What goes wrong. Employees clock in 15 or 20 minutes before their shift. If those minutes are counted and nobody approved them, they push people into overtime. If they're not counted but the person was working, that's unpaid work. It gets worse when the rule applies to some clocks or groups and not others.
Example. Five people on a 6:00 a.m. crew clock in at 5:40 every day. That's 20 minutes each, 100 minutes a day and more than 8 hours a week, much of it at overtime rates by Friday.
What the law says. Time between an early punch and the start of work doesn't have to be paid when the employee comes in early by choice and isn't working (29 CFR 785.48(a)). Time spent working does.
The fix. Set a window for how early people can clock in before their scheduled shift, block or flag punches outside it, and send unscheduled hours to a manager to approve. Make sure every clock has the rule.
Not sure how your rules are set today? We'll walk through them with you.
| Rule | What goes wrong | What to check |
|---|---|---|
| Rounding | Rounds one way, and employees see changed times | Rounding increment, direction, which punches it applies to, whether the actual punch shows beside the rounded one |
| Workweek start | Overtime in the wrong week | First day of the workweek in the pay period setup, matched to payroll |
| Overnight shifts | Can't clock in after midnight, or hours land on the wrong day | How overnight shifts are assigned to days and weeks, location time zone |
| Shift length | Forgotten clock-out becomes a 72-hour shift | Forgotten clock-out alerts, whether long shifts need approval |
| Meal deductions | Deducted when no break was taken, or off the wrong job | Break rule type, paid or unpaid, job costing, missed-break alerts |
| Early clock-in | Unapproved minutes become overtime | Punch restriction window, unscheduled punches, manager review |
Switching systems? Set and test these rules before go-live. See switching time and attendance systems without missing a payroll.
In WorkEasy Time and Attendance, every rule (rounding, breaks, overtime and punch restrictions) is set for everyone, a group or one employee, so one location can run different rules from another in the same system. Rounding can follow the schedule or a fixed increment and can apply to manually entered time too. Punch restrictions set how early or late people can clock in around their scheduled shift and can stop clock-ins once someone hits weekly overtime. Break rules can be paid or unpaid, with their own time codes and job costing. Alerts tell employees and managers about forgotten clock-ins and clock-outs for scheduled shifts, and about forgotten breaks. Every change to a punch is kept in the timesheet history.
Want to see your own rules run on a real week of punches? Book a quick demo.
Short answers to the questions that come up most often.
Federal Department of Labor rules allow rounding punches to the nearest quarter hour if it's neutral over time, so employees are paid for all the time they actually work. It isn't allowed if it only ever rounds in the employer's favor. In practice, quarter-hour rounding is where the 7-minute rule comes from: punches 1 to 7 minutes past the quarter round down and 8 to 14 round up. Some states are stricter. Some employers now pay to the minute instead. In WorkEasy, rounding is set per company, group or employee.
Yes, but only for breaks that actually happen. Under federal law, a bona fide meal period, usually 30 minutes or more with the employee fully relieved of duty, doesn't have to be paid, so an automatic deduction is a convenience, not a right. If someone works through lunch, that time is paid work and the deduction has to be reversed. State meal and rest break laws add more rules. Setups that avoid this deduct only when no break was punched, or require employees to confirm their breaks. In WorkEasy, automatic break deductions are set by group with their own time codes, and break alerts can tell managers when a break is missed.
Not always. Under federal rules, time between an early punch and the start of the shift doesn't have to be paid if the employee isn't working and isn't required to be there, for example someone who clocks in at 5:45 and drinks coffee until 6:00. If they start working, it's paid time, and it counts toward overtime. The simplest way to avoid arguments is to stop early punches outside a set window and send anything unusual to a manager. In WorkEasy, punch restriction rules set how early people can clock in before their scheduled shift, with a manager override.
For federal overtime, hours count in the workweek in which they're actually worked, so a shift that crosses the start of a new workweek is split at that point. Within a week, some employers show the whole shift on the day it started for scheduling and reporting. What matters for federal overtime is that the hours land in the workweek they were worked. States with daily overtime count it by workday, so the workday start time matters too. Decide the rule, set it once in your time system and test it on a real overnight shift.
Yes. Federal rules let an employer pick any fixed, recurring seven-day workweek, starting on any day and hour, and change it if the change is meant to be permanent and isn't made to avoid paying overtime. Plan the change at a pay period boundary, check how overtime is calculated in the transition week, and tell payroll and employees before it happens. In WorkEasy, the first day of the workweek is part of the pay period setup.
WorkEasy Software in the news
Learn what the news media is saying about WorkEasy Software products and service.







