Do Employers Have to Count PTO, Vacation, and Sick Hours Toward Weekly Overtime?

This question comes up constantly in HR departments and payroll teams, and the confusion is understandable. An employee works 36 hours, takes 8 hours of vacation, and suddenly you've got 44 paid hours on the timesheet. Do you owe overtime? The answer under federal law is no — but the nuances matter, and getting this wrong has real consequences.

Here's what you actually need to know about how PTO, vacation, sick leave, and holiday pay interact with overtime rules.

The FLSA rule is clear

Under the Fair Labor Standards Act, only hours actually worked count toward the 40-hour weekly overtime threshold. Paid time off — in any form — does not qualify as hours worked. Vacation days, sick leave, personal days, and holiday pay when an employee isn't actually working are all treated the same way: they generate compensation but they don't generate overtime eligibility.

This means an employee who works 36 hours and uses 8 hours of PTO in the same week has a total of 44 paid hours but zero overtime hours. The paycheck reflects 44 hours of pay at regular rate. No time-and-a-half applies. The employer owes overtime only when the employee has actually worked more than 40 hours in the workweek.

The flip side of this rule is equally important. If an employee works 42 hours and also uses 8 hours of PTO in that same week, they get both: 2 hours of overtime pay for the hours they actually worked beyond 40, plus regular-rate compensation for the PTO. The two calculations don't interact — overtime isn't reduced because PTO was used, and PTO doesn't inflate the overtime calculation.

Why this confuses people

Most of the confusion comes from how payroll systems display the numbers. A timesheet showing 44 "hours" looks like it should trigger overtime, especially if the system doesn't clearly distinguish between worked hours and PTO hours. Employees see a 44-hour paycheck and assume they earned overtime. Managers reviewing timesheets apply the same logic.

This is a documentation and system design problem as much as a legal one. Payroll software should clearly separate worked hours, overtime hours, and paid leave hours on every pay stub. When these categories are blurred, disputes follow. It's the same reason clear payroll integration between your HRMS and payroll systems matters — manual entry and unclear categorization introduce errors that compound over time.

What about holiday pay?

Holiday pay follows the same logic. If your organization pays employees their regular rate for a day they don't work — a federal holiday, for instance — those hours do not count toward overtime. An employee paid for Thanksgiving Day without working that day has not "worked" those hours in any legal sense.

The exception is when an employee actually works on a holiday. Those hours are worked hours and count toward the 40-hour threshold just like any other worked hours. Employers may also choose to pay a premium rate for holiday work — time and a half or double time — but that's a contractual benefit, not an FLSA requirement. The overtime calculation still only kicks in at 40 worked hours regardless of holiday premium pay.

Employer discretion and written policy

Federal law sets the floor but doesn't stop employers from offering more. A company can voluntarily choose to include PTO hours in overtime calculations — treating paid time off as if it were worked time for the purpose of overtime eligibility. This is more generous than what the law requires, and while it's uncommon, some employers use it as a retention benefit.

If an employer establishes this kind of policy, it needs to be consistently applied and clearly documented. Inconsistent application — counting PTO toward overtime for some employees but not others — creates exposure under anti-discrimination statutes even if the underlying policy is legal. This connects directly to how compliance checks often surface: a policy that looks fine on paper but gets applied unevenly across teams or protected classes is where the legal risk actually lives.

Whatever policy the employer establishes, it should be in writing, reviewed by counsel, and reflected consistently in payroll processing.

State law can change the calculation

The FLSA governs federal minimum standards. California, New York, Illinois, and other states can impose stricter requirements. As of 2026, no state has changed the fundamental rule that PTO doesn't count as worked hours for overtime purposes — but state laws govern other aspects that interact with this calculation.

California, for instance, requires employers to pay out unused PTO at termination because it treats accrued vacation as earned wages. That doesn't change the overtime calculation, but it changes how you account for PTO in total compensation. Employers operating in multiple states need to track state-specific rules carefully, particularly around accrual caps, payout requirements, and how leave policies interact with final pay obligations.

For employers wondering about related overtime exemption rules — such as whether exempt employees are affected by these calculations at all — the answer is that overtime rules don't apply to properly classified exempt employees regardless of how PTO is handled. That classification is its own analysis.

Sick leave: the same rules apply

Sick leave follows the same FLSA logic as vacation: paid but not worked means it doesn't count toward overtime. An employee who takes two sick days in a workweek is still only eligible for overtime based on the hours they actually worked during that week.

This matters particularly for organizations with mandatory paid sick leave laws. Many states and municipalities now require employers to provide paid sick leave, and the fact that this leave generates compensation does not change the overtime analysis. Employers paying out sick leave under state mandate are not triggering overtime eligibility just by making those payments.

Where things get complicated is when sick leave intersects with FMLA or other protected leave. Those interactions don't change the overtime math, but they do affect how HR manages the documentation and tracking. Having reliable time tracking software that accurately captures worked hours versus paid leave is what makes this manageable at scale — especially for organizations with large hourly workforces where errors compound quickly.

Other leave types: bereavement, jury duty, FMLA

The same logic applies to other paid leave categories. Paid bereavement leave, paid jury duty, and any other form of paid absence that doesn't involve actual work do not count toward overtime. Understanding bereavement leave policies and how they interact with other time-off calculations is worth getting right, especially for organizations managing multiple leave types simultaneously.

Unpaid FMLA leave is even simpler from an overtime perspective — there's no compensation at all, so there's no ambiguity about whether those hours count.

Payroll processing implications

From a payroll processing standpoint, the right approach is to maintain three clean categories for every workweek: worked hours, overtime hours (worked hours beyond 40), and paid leave hours. These should be calculated independently and displayed separately on pay stubs.

When payroll systems automatically pull hours from time-tracking systems, the categorization needs to flow correctly. PTO approved in the HR system needs to land in the paid leave bucket in payroll, not the worked hours bucket. Errors at this integration point are common and tend to either underpay overtime (by treating PTO as if it reduces the worked hour count) or overpay it (by treating PTO as worked hours). Both create problems — one legal, one financial.

For organizations that have struggled with payroll accuracy, this is often where the issue originates. Choosing the right HR payroll software that handles these categorizations automatically and accurately is worth the investment — it removes the manual categorization risk entirely.

What happens when employers get it wrong

Under-calculating overtime is a wage and hour violation. The Department of Labor can require back pay for up to two years (three years for willful violations), and employees have the right to sue for unpaid overtime plus an equal amount in liquidated damages plus attorney's fees.

Over-calculating overtime — treating PTO as worked hours and paying overtime that wasn't owed — is less legally problematic but creates costs and sets precedent that's difficult to unwind. Employees expect consistency, and changing overtime practices that have favored them invites complaints and potential claims that the policy change was discriminatory or retaliatory.

Either error is avoidable with clear systems and policies. The same principles that apply to disciplinary action at work apply here: documented, consistently applied policies are what make HR decisions defensible when they're challenged.

The bottom line

Federal law is clear: PTO, vacation, sick leave, and holiday pay do not count toward the overtime threshold. Only hours actually worked count. An employee with 40 worked hours and 8 PTO hours in a week has no overtime entitlement. An employee with 42 worked hours and 8 PTO hours is owed 2 hours of overtime.

The practical work is in the systems and policies: keeping worked and paid-leave hours cleanly separated in payroll, applying whatever leave-counting policy you establish consistently across your workforce, and staying current on state law requirements that layer on top of the federal baseline.

If your payroll calculations have been combining PTO with worked hours in overtime calculations, a payroll audit is worth running sooner rather than later.