An Employee Disputes Their Hours: How to Handle a Timesheet Dispute (2026)

August 25, 202612 min read

An Employee Disputes Their Hours: How to Handle a Timesheet Dispute (2026)

The short answer: When a crew member says the check is short, you have a records problem, not an argument. Federal law puts the duty to keep accurate hours on you, and when your records are weak a court is allowed to accept the employee's reasonable estimate instead. Your first move is to say you will look into it, then actually reconstruct the week from timestamps. Pay any shortfall immediately, document what you found either way, and never let the complaint affect how the person is treated afterward. Punch makes the reconstruction take about four minutes, because the record already exists.

The First Hour Decides How Expensive This Gets

Most wage disputes are settled or escalated in the first conversation, and the two most common employer mistakes both happen there.

The first is denying it on the spot. "The system says 38, so you worked 38" ends the conversation without answering it. If your number turns out to be wrong, you have now told a worker that raising the issue internally does not work, which is exactly the moment people call an agency instead.

The second is treating the complaint as disloyalty. Section 15(a)(3) of the Fair Labor Standards Act makes it unlawful to discharge or discriminate against an employee for complaining about wages, and the protection is not limited to formal filings with the government. The Department of Labor's Fact Sheet #77A covers complaints made to the employer, and the Supreme Court held in Kasten v. Saint-Gobain Performance Plastics Corp., 563 U.S. 1 (2011), that an oral complaint can be protected activity. Cut hours, change the schedule, or reassign the person in the two weeks after, and you have handed them a second claim that is often easier to prove than the first one.

The correct opening is short. Thank them, ask which pay period and which days, say you will pull the record and come back with an answer by a specific date, and put that date in writing.

The Burden Does Not Sit Where Owners Assume

Owners tend to believe the employee has to prove the missing hours. That is only half true, and the other half is where small businesses lose.

In Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946), the Supreme Court set the framework still used today. The employee carries the initial burden. But where the employer's records are inaccurate or inadequate, the Court held the remedy "is not to penalize the employee by denying him any recovery on the ground that he is unable to prove the precise extent of uncompensated work." Once the employee produces enough evidence to show the amount of uncompensated work as a matter of just and reasonable inference, the burden shifts to the employer to produce evidence of the precise amount of work performed, or to negate the reasonableness of that inference.

Read that last sentence as an operations requirement. The word is precise. A spreadsheet rebuilt from memory at the end of the month is not precise. A text thread is not precise. If you cannot produce the exact hours, the employee's estimate becomes the working number.

29 CFR 516.2 lists what the record has to contain for every non-exempt worker, including the time of day and day of week the workweek begins, the hours worked each workday, the total for the workweek, the regular hourly rate, straight-time earnings, and overtime premium pay. The Department of Labor is deliberately neutral about method. Fact Sheet #21 says employers may use any timekeeping method they choose, and that any plan is acceptable "as long as it is complete and accurate." The law does not care whether you use an app. It cares whether the record survives a challenge.

One more thing has changed the balance. The Department of Labor publishes a free DOL-Timesheet app so workers can log their own hours, including travel, pre-shift and post-shift work, and on-call time, expressly so they have something to use if a pay dispute arises. Assume the person in front of you may already have their own log. Yours has to be better.

Run the Reconstruction, in This Order

Do not start with the paycheck. Start with the week.

Fix the workweek. Identify the seven consecutive 24-hour periods your overtime is calculated against, and confirm the disputed days fall where you think they do. A shift that crosses midnight, or a pay period that splits a week, is behind a surprising share of "my check is short" complaints.
Pull every punch for those days. Punch-in time, punch-out time, and lunch as its own recorded event rather than an automatic deduction. Automatic meal deductions are the single most common source of a genuine shortfall.
List every edit. Who changed what, when, and why. If a shift was corrected, the original values should still exist. If your system lets someone overwrite a cell with no trace, you have already lost this dispute.
Recompute overtime against the real hours. Adding 40 minutes to a Tuesday can push Friday over the threshold. Federal law sets the floor at 40 hours in a workweek, and several states add daily overtime and double time on top of it. Recalculate, do not eyeball.
Compare to what was actually paid. Gross, hours, and rate. Then write down the difference, even if the difference is zero.

The gaps that produce real underpayments repeat: unrecorded loading or drive time between sites, a shift rejected and never re-entered, a missed punch-out trimmed to a round number, two job sites worked under one continuous punch, and a bonus or shift premium that should have raised the regular rate used for overtime.

If You Were Short, Pay It Now

There is no advantage to slow-walking a correction you already know you owe.

Under 29 U.S.C. 255, an FLSA back-pay action can be brought within two years, extended to three years for a willful violation, meaning the employer knew or showed reckless disregard for whether the conduct was prohibited. Liquidated damages generally double the back pay, and 29 U.S.C. 260 lets a court reduce or eliminate them only where the employer shows the act was in good faith and it had reasonable grounds to believe it was not a violation. Finding the error yourself, correcting it in the next payroll, and documenting the fix is what good faith looks like in practice. Being told about it twice and doing nothing is what willful looks like.

If the dispute escalates instead, it usually escalates to a state agency rather than a courtroom. California is the model most owners will encounter first. An employee files with the Division of Labor Standards Enforcement, the agency notifies the parties within 30 days whether it will act, a settlement conference is scheduled, and if the matter proceeds to a Berman hearing it is generally held within about 90 days, with the hearing officer issuing an Order, Decision, or Award roughly 15 days after. The hearing is informal, the rules of evidence are relaxed, and both sides testify under oath. What you bring is your record. If it is a printout that anyone could have typed last night, it carries the weight of a printout.

If the Record Holds, Close It in Writing

A dispute you win still needs an ending.

Walk the employee through the actual timestamps, day by day, and show where their number and yours diverge. The gap is usually a lunch they forgot, a week boundary, or time they assumed was compensable and is not. Then send a short written summary: the days reviewed, the hours found, the total paid, and an invitation to come back if they have something you have not seen. Keep a copy. That paper shows a functioning internal process, which is exactly what an investigator or hearing officer looks for when deciding whether a business is careless.

Write the Dispute Procedure Before You Need It

Four lines in the handbook will do:

Report a pay discrepancy within a set number of days of the pay date, to a named person.
The company reviews the timestamps and responds by a stated deadline.
Confirmed shortfalls are corrected on the next regular payroll, or sooner where state law requires.
No one is penalized for reporting a discrepancy.

Say plainly that a reporting deadline is an internal service standard, not a waiver. It does not shorten anyone's statutory rights, and writing it as if it does is a bad look in a hearing. Pair it with your missed punch policy and your timekeeping policy so the three documents agree with each other.

How Punch Settles a Timesheet Dispute

Everything above turns on one question: can you produce the precise hours, months later, in a form a stranger will believe. That is what Punch is built to do.

The punches are timestamps, not entries. Crews punch in and punch out, and lunch is its own recorded action rather than an automatic deduction, so unpaid meal time never quietly inflates a paid total. Punch-in at a job site is confirmed by a geofence. Punches work with no signal and sync when service returns, so a basement or a rural site does not become a blank day and a later argument.

Corrections are documented, not silent. Owners and managers can add or fix a shift, and the edit will not save without a written reason. Punch keeps the original times, the new times, who made the change, and when. Employees cannot edit their own hours, which is the separation that makes the record credible to someone who was not there.

Every week is reviewed by a person. Shifts land in an approvals queue. Managers approve or reject with a reason, in bulk when the week is clean, and the employee is notified when something is rejected. When the pay period is marked paid, the hours lock and the action is recorded. If a dispute arrives later, you can show not just the hours but the review.

The math is already applied. Punch supports weekly and bi-weekly pay periods, applies your fixed workweek, keeps split shifts split, and ships overtime presets for more than 50 countries including the states that run daily overtime and double time. Reports break hours down by person, job site, and period, and export to Excel or a QuickBooks CSV, or push straight into QuickBooks Online. Square is supported as well. When you sit down to reconstruct a disputed week, the reconstruction is a filter, not a project.

On privacy, the proof is a geofence, never a camera. Punch does not do facial recognition and does not take a photo at a punch. Trust beats surveillance, and a job-site geofence reads better in a hearing than a folder of pictures of your crew's faces at 6 a.m. Web punches are deliberately not geofenced, because browser location is trivially spoofed and enforcing it would be theater.

Why Punch Wins Over Per-Seat Time Clocks

The record that protects you in a dispute should not be the reason your bill goes up.

ClockShark, Connecteam, QuickBooks Time, Buddy Punch, and Homebase all bill per user, and several of them put the audit trail, the shared-device kiosk, or the payroll export on a higher tier. Punch prices flat per organization. Every feature is on every plan. Owners are always free. Adding a seasonal crew for six weeks does not move your bill, and the protection does not arrive with an upgrade prompt attached.

Frequently Asked Questions

Can I refuse to pay hours the employee never recorded?

Generally no. The obligation attaches to work you suffer or permit, and the recordkeeping duty is yours. If the work happened with your knowledge, pay it and fix the recording problem that let it go unlogged.

How far back can an employee claim unpaid wages?

Two years under the FLSA, three if the violation was willful, and back pay is commonly doubled as liquidated damages. Many states run longer periods and add their own penalties.

Can I discipline someone for filing a complaint about their pay?

No. Complaints about wages, including oral and internal ones, are protected from retaliation. Adverse action afterward creates a separate claim.

What if the employee's own log disagrees with my system?

Compare them line by line and take the difference seriously. If your record is exact and attributed, it will usually explain the gap. If your record is a spreadsheet someone retyped, the employee's estimate is likely to prevail.

Should I require disputes to be reported within a certain number of days?

You can set an internal reporting window and it helps you respond quickly. It does not shorten anyone's legal rights, so do not write it as if it does.

The Bottom Line

A timesheet dispute is decided by whichever side can show the hours, not by whichever side is more certain. The law hands the recordkeeping duty to you and, when you fall short of it, hands the benefit of the doubt to the employee. So build the record while the work is happening, keep every correction attributed, and treat the complaint as a request for information rather than a challenge to your authority.

Start with Punch and have the answer before the question arrives.

This article is general information, not legal advice. Wage payment, recordkeeping, and claim procedures vary by state and are often stricter than federal law. Confirm your obligations with your state labor office or a qualified employment attorney.

Sources:

An Employee Disputes Their Hours: How to Handle a Timesheet Dispute (2026)