Can You Fire an Employee for Time Theft?

Yes — and then it gets complicated

Falsifying time records is grounds for termination essentially everywhere. At-will employment covers you in 49 states, time theft is misconduct under any reasonable reading, and no employment lawyer is going to tell you that clocking in for a shift you didn't work is protected activity.

What makes these terminations different from firing someone for stealing cash or property is everything downstream. With cash, the amount is known and the act is binary. With time, you are asserting that a person was paid for hours they weren't there, using records that person is about to tell you are wrong — and you still owe them money for the hours they actually did work, including the shift where you caught them.

The wage-law trap, up front

This is the one that turns a justified firing into a Department of Labor problem, so it goes first.

Under the Fair Labor Standards Act you owe wages for hours actually worked. Not hours you approve of. Not hours net of what you believe was padded. If someone worked six real hours and claimed eight, you owe six — and you cannot dock the other two as a penalty, cannot deduct the value of the padded time from the final check, and cannot zero out a shift because the punch record was falsified. Docking pay as discipline is a separate violation from the underlying dispute, and it's the one that's easy for an investigator to prove.

Salaried exempt employees add a second layer: partial-day deductions can jeopardize the exemption itself, which is a much more expensive problem than the time theft. If the person you're about to discipline is on salary, that is the moment to make a phone call rather than a correction.

Your evidence is only as good as your clock

The uncomfortable part of most time theft cases is that the employer cannot actually prove the thing they know happened. What you have determines what you can do:

• A PIN pad or a shared login proves nothing.It authenticates a code, not a person. If your entire case rests on the fact that someone's code was entered, the employee's answer is that anyone could have entered it, and they're right.
• GPS and geofence records place the punch, not the person.Strong evidence that a clock-in happened from a couch six miles away. Weaker against “my coworker had my phone,” which is technically a different offense by a different person.
• A photo on every punch is the version that ends arguments.It's a picture of someone else clocking in as them. This is why photo capture keeps showing up as the cheapest control with the best return, and why facial recognition closes it entirely.
• The punch edit log is the underrated one.A supervisor repeatedly editing the same employee's hours, or anyone editing their own, is documentary and hard to explain away. Most systems keep this log and almost nobody opens it.

Pull the records before the conversation, the same way you would with any other theft. Some time systems let employees edit historical punches right up until a manager approves the period.

The policy has to exist first

Time theft is the one category where employers routinely discipline for a rule they never wrote down. “Everyone knows you can't clock in your friend” is not a policy, and it will not survive an unemployment hearing where the former employee says the practice was tolerated for years.

What the handbook needs to name specifically: that clocking another employee in or out is falsification of company records, that falsification is grounds for termination, and what the escalation path is. Signed acknowledgment on file. If you don't have that today, write it, distribute it, and understand that the first offense after distribution is your clean case — not the ones before it.

Consistency is the thing that actually loses cases

Buddy punching is usually not one person. It's a habit that has spread through a shift, often with a supervisor who knows and hasn't cared, and the moment you decide to enforce the rule you are choosing who to enforce it against.

Fire the newest hourly employee for a practice the shift lead has run for two years and you have handed a plaintiff's attorney the shape of a discrimination claim, regardless of what was actually in your head. Selective enforcement is the failure mode here, more than the underlying facts. If the problem is systemic, announce a reset: the policy is being enforced starting now, for everyone, and here is the new clock. Then enforce it evenly from that date.

Immediate termination, or progressive discipline?

Cash theft is usually a firing offense on the first instance. Time theft genuinely isn't, most of the time, and treating it as one is often the wrong call on the merits rather than just the risk.

A documented warning for a first instance, termination for a repeat, is both defensible and proportionate — and it's what most handbooks already say, which matters because departing from your own written process is the fastest way to look arbitrary. Reserve immediate termination for the cases that earn it: a sustained scheme, a supervisor approving fraudulent hours, an employee who lies in the investigation interview. That last one does real work. The falsification is often arguable; lying about it to your face usually isn't.

The part worth sitting with

If buddy punching is widespread on a crew, the honest question is why people felt they needed it. Sometimes the answer is a clock-in process that adds twenty unpaid minutes to a shift, a schedule nobody can physically make, or a manager everyone routes around. Firing one person resolves none of those, and the practice reappears within a quarter.

The durable fix is a clock that makes the fraud impossible rather than a policy that makes it punishable — the full field is in the best time theft and buddy punching prevention software, and the time theft guide covers what it costs and where the biometric privacy laws bite. As with anything on this page: not legal advice, and final-pay rules vary enough by state that the twenty-minute call is worth it.