PTO Laws by State

The first time an employee left with a chunk of unused vacation on the books, I did not know whether I owed it to them. I assumed there was a simple federal rule. There is not. Whether you must pay it out depends on which state your employee works in, and in some states unpaid PTO becomes a wage claim with penalties attached.

PTO laws by state are the rules each state sets for whether employers must offer paid time off, whether they must pay out unused PTO when someone leaves, and whether they can make employees forfeit unused time. There is no federal requirement to provide PTO at all; the rules that matter come from the states.

This guide is for the owner or manager handling compliance without a dedicated HR department. It covers the federal baseline, the four distinctions that matter, a 50-state table, state spotlights, guidance for remote teams, payout and tax mechanics, and a checklist you can use.

I built FirstHR to keep employee records and signed policy acknowledgments in one place, because multi-state PTO compliance starts with knowing where each person works and what your written policy told them. One note before the rules: this is general information, not legal advice. PTO law changes and varies by state, so confirm current rules with your state labor agency or employment counsel before acting.

Quick Answer: Is PTO Required by Law?

No federal law requires employers to provide paid time off, and most PTO rules come from the states. Here is the compliance picture at a glance, before we work through each piece in detail.

The short version: offering PTO is optional almost everywhere, but once you offer it, state rules on payout and forfeiture can bind you, and a few states now require offering paid time off at all. The rest of this guide takes those rules one at a time, because blurring them together is the single biggest source of employer mistakes.

The Federal Baseline: No PTO Required

There is no federal law requiring employers to provide paid vacation or paid personal time, or to pay out unused time when an employee leaves. The federal floor, set by the Fair Labor Standards Act, is simply silent on PTO, and that one fact clears up most of the confusion.

Because the federal baseline is silent, everything that follows is state law, which is why the rest of this guide is organized state by state. It also means an employer with staff in several states cannot rely on one national policy: each employee is governed by the rules of the state where they work.

The Four Distinctions That Actually Matter

PTO law turns on four separate questions: whether you must offer PTO at all, how it accrues, whether you must pay it out when someone leaves, and whether employees can be made to forfeit it. Each has a different answer in different states, and running them together is where compliance mistakes come from.

There is a fifth distinction that deserves its own mention: vacation versus sick leave. General PTO (vacation or a combined bank) and mandated paid sick leave are governed by different laws, and treating a sick-leave mandate as if it were a general-PTO requirement, or vice versa, is a common error. The sections below take each of these questions in turn.

Must You Offer PTO? (Only Three States)

For the vast majority of employers, offering PTO is entirely optional. No federal law and no state law requires employers to offer paid vacation specifically, and many businesses use discretionary time off as a flexible benefit. Only three states require employers to provide paid time off that employees can use for any reason.

Those three states are Maine, Nevada, and Illinois. The Maine Earned Paid Leave law and the Nevada paid-leave statute came first, and Illinois joined with its Paid Leave for All Workers Act. Each requires covered employers to let employees earn and use paid time off for any reason.

Coverage is where the three diverge. Illinois covers employers of all sizes, Maine applies above 10 employees, and Nevada applies at 50 or more, each with its own exemptions. Everywhere else, whether to offer PTO is a business decision rather than a legal one, and federally these benefits remain a matter of agreement between employer and employee.

At the federal level, the Protected Time Off Act would create a nationwide right to earn and use general PTO. Its current version, H.R. 4763, introduced in the House on July 25, 2025, sets an hour of paid annual leave per 25 hours worked and has not passed. Plan around the state-by-state reality, not a bill sitting in committee.

Payout on Separation: The High-Stakes Rule

Whether you must pay out unused PTO when an employee leaves depends on the state where they work and, in many states, on your written policy. It is also the distinction that most often turns into a costly mistake, because in some states unpaid PTO becomes an enforceable wage claim.

Employers must pay out accrued unused PTO on separation, whatever their own policy says, in the 10 states that treat accrued vacation as earned wages: California, Colorado, Illinois, Louisiana, Maine, Massachusetts, Montana, Nebraska, North Dakota, and Rhode Island.

Two of the 10 attach a condition. Maine's payout statute binds employers with 11 or more employees, and Rhode Island's rule turns accrued vacation into wages after a year of service, payable with the final wages on the next regular payday.

Two others in the group carry a narrow exception. North Dakota lets an employer withhold earned PTO at separation in one case only. The worker must have under a year of service and quit on less than five days' notice, and the employer must have given written notice of that rule at hiring. Montana's rule covers vacation, and payout of a separate PTO bank there depends on the employer's policy.

Elsewhere the answer turns on your written policy, and the default splits two ways. In Indiana, Maryland, New York, North Carolina, Wisconsin, and Wyoming it runs toward the employee: you owe the balance unless a written policy you gave employees clearly forfeits it. Wyoming also requires the employee's written acknowledgment of that policy.

In the remaining states, the District of Columbia included, state law adds no payout rule of its own, and the state enforces whatever payout your handbook or established practice promised. In Texas or Florida, for example, nothing is owed unless your policy says so.

Indiana is the state most often filed in the wrong column. Accrued vacation there is compensation, but the Indiana Department of Labor is explicit that a company policy may set conditions that must be met before accrued vacation is paid. That makes Indiana policy-conditional, not an earned-wages state.

The practical takeaway: your written PTO policy matters enormously in the policy-conditional states, where it is your main tool, and far less in the earned-wages states, where the law overrides it on payout. In an earned-wages state, accrued vacation is owed at separation whatever your handbook says, apart from the conditions and narrow exceptions above. Either way, the rule follows the employee's work location, which becomes critical for remote teams.

Use-It-or-Lose-It Rules

A use-it-or-lose-it policy requires employees to use their PTO by a deadline or forfeit it. In most states this is permitted if clearly communicated, but a few states prohibit forfeiting earned vacation entirely, which changes what you can do.

Three states clearly prohibit use-it-or-lose-it for earned vacation: California, Colorado, and Montana. In these states, accrued vacation is earned compensation that cannot simply expire, so instead of forfeiture you must allow rollover or pay the time out. Reasonable accrual caps, which stop employees from earning more once they hit a ceiling, are generally still allowed; what is prohibited is taking away time already earned.

Montana states the distinction about as plainly as a labor agency can. Its Department of Labor and Industry says flatly that use-it-or-lose-it policies are not permitted in Montana, while maximum accumulation amounts are, because a cap stops further accrual rather than erasing what was earned.

Other strict payout states, Illinois and Louisiana among them, bar forfeiture at separation without banning use-by dates. Nebraska is the state that splits the lists, which is why some sources name three states here and others four. Its Supreme Court held in Roseland v. Strategic Staff Management (2006) that accrued vacation is wages due when employment ends.

The Roseland decision never addresses a use-by deadline directly. Even so, the University of Nebraska-Lincoln read it as clearly stating that vacation, once earned, cannot be forfeited, and suspended its own use-or-lose rule in response. In Nebraska, cap accrual rather than forfeit what was earned.

Everywhere else, a use-it-or-lose-it policy is generally allowed as long as it is in writing and clearly communicated to employees in advance. A forfeiture or use-by-date rule that is not written down and communicated is hard to enforce and easy to challenge. Write the policy into your employee handbook, apply it consistently, and confirm your specific state permits it.

Sick Leave vs Vacation: Do Not Conflate Them

One of the most common errors is treating paid sick leave and general PTO as the same thing. They are governed by different laws, and the states that mandate one are not the same as the states that mandate the other.

Mandated paid sick leave is a distinct, and more widespread, requirement than any-reason PTO. According to a Congressional Research Service tally (April 2026), 17 states plus the District of Columbia require private employers to provide paid sick leave, with cities and counties adding local ordinances on top. These laws typically set an accrual rate (often one hour per 30 hours worked), annual use caps, and carryover rules.

Actual access runs ahead of the mandates, because most employers offer the benefit without being told to. The Bureau of Labor Statistics reported that 81 percent of private industry workers had access to paid sick leave in March 2026, well above what 18 jurisdictions could account for on their own.

The list of mandate states moves in both directions, so a saved copy is never safe to reuse. Nebraska added a mandate under its Healthy Families and Workplaces Act, effective October 1, 2025 for employers with 11 or more employees. Missouri went the other way: the paid sick time voters approved took effect in May 2025, and the legislature's repeal took effect that August.

Virginia is next. Its statewide paid sick leave law covers employers with 50 or more employees from July 1, 2027, those with 25 or more from January 1, 2028, and every employer from January 1, 2029.

Sick-leave mandates do not reach the vacation side at all. A state can require paid sick leave without requiring vacation PTO, and it can require vacation payout without mandating a single hour of sick leave. The three states that require any-reason PTO are a third, separate group again.

The practical implication for a multi-state employer is that a single state can hand you three overlapping obligations: a sick-leave mandate, possibly an any-reason PTO mandate, and payout or forfeiture rules on any vacation you offer. They do not cancel each other out, and satisfying one says nothing about the others.

Keeping vacation and sick leave as clearly labeled, separately tracked categories makes that far easier to manage than one lumped bank. In some states, California among them, combining them subjects the whole bank to the stricter vacation rules. When in doubt, keep the categories distinct and check each state's specific sick-leave law.

50-State PTO Compliance Table

For each state and DC, this table shows whether PTO payout on separation is generally required, whether use-it-or-lose-it is restricted for earned vacation, and whether paid sick leave is mandated. Use it as a starting reference, not a substitute for checking the current statute, because laws change and details such as coverage thresholds and policy conditions matter.

In the payout column, Required (earned wages) means the state overrides your policy either way. Required unless policy means you owe payout unless your written policy clearly forfeits it. Policy governs means state law sets no payout default, so your handbook or established practice decides and the state enforces what it promised.

Whichever label a row carries, read your own handbook language before you act on that row. A row with a condition in parentheses, such as an employee count or a year of service, binds you only once that condition is met. Check it before you assume a row applies to you.

Several states shown simply as Required scale their sick-leave mandate by size as well. In Maryland, Massachusetts, Oregon, and Rhode Island, smaller employers owe unpaid leave rather than paid, and Connecticut covers every employer from January 1, 2027 (only those with 11 or more until then).

Rows move, and the sick-leave column moves fastest. Missouri is the cautionary example: the state labor department confirms employers there are no longer required to provide paid sick time as of August 28, 2025, four months after the voter-approved mandate took effect. Several states shown as not required also have cities with their own ordinances. Before you rely on any row, confirm the current rule with that state's labor agency.

State Spotlights

A few states have rules strict or distinctive enough that they deserve individual attention, because they are where employers most often get caught out. If you have employees in any of these, read the state's guidance closely.

California is the strictest of the group. Its Division of Labor Standards Enforcement states that paid vacation is a form of wages, earned as labor is performed. It also says that a use-by-date forfeiture policy is illegal, that a cap on accrual is fine, and that unused earned vacation is paid at the final rate of pay whenever employment ends. Late final pay then adds waiting-time penalties on top.

Combining vacation and sick leave into one PTO bank can subject the whole bank to those California rules, so many employers there keep the two separate. Colorado likewise treats accrued vacation as earned and voids any forfeiture, a reading its Supreme Court upheld. Illinois requires any-reason paid leave statewide and prohibits forfeiture of earned vacation on separation.

Massachusetts carries one of the harshest penalty regimes in the country. Its Wage Act counts holiday and vacation payments as wages, requires a discharged employee to be paid in full on the day of discharge, and awards treble (triple) damages plus costs and attorney fees to an employee who prevails. A payout you owe a Massachusetts leaver is therefore worth budgeting three times over if you are tempted to argue about it.

New York has no vacation-payout statute, but its labor department is explicit that when an employee has earned vacation and there is no written forfeit policy, the employer must pay the accrued vacation. The state mandates paid sick leave too, and New York City layers its own ordinance on top.

Washington pairs a sick-leave mandate with no vacation-payout requirement. Texas and Florida have no PTO or payout mandate at all, so an employer's written policy governs entirely, which makes a clear handbook especially important there.

The pattern is worth naming. Strict states treat vacation as wages and penalize forfeiture; hands-off states leave the whole question to your policy. A written policy is therefore the through-line of compliance everywhere, either as the document the state overrides or as the document that is the rule.

Five More States Employers Ask About

The five states below are the ones I get asked about most often after California, and each carries a wrinkle that a single table row cannot hold. This is a selection rather than a ranking, so if your state is not here, work from the 50-state table above and confirm the current rule with that state's labor agency.

The pattern across the five: in four of them your handbook is the operative document, and in Colorado it is not. That split is the thing to settle before you write one PTO policy for a multi-state team. The broader employment rules for each sit in the state compliance guides, including Colorado and Tennessee.

Each of those wrinkles comes from a primary source, and those pages are worth bookmarking rather than trusting a summary. The Arizona statute sets the earned paid sick time caps by employer size. The Tennessee labor department sets out the next-payday-or-21-days final wage rule on its wages page.

Wisconsin is the one that surprises employers, so read its page directly. The Department of Workforce Development puts the default in an if-then sentence that turns on whether you wrote down a forfeiture clause at all: silence in the policy means the balance is owed. After a department investigation, a court can add increased wages of up to 100 percent, doubling what you owe.

Remote and Multi-State Employees

The rule that catches growing businesses off guard is this: PTO obligations follow the state where the employee actually works, not where your company is headquartered. As remote work spreads, this has become one of the most common compliance gaps.

A remote employee working from California is entitled to the California PTO protections even if your business is based in Texas. That means a single company can owe payout to some employees and not others, and ban forfeiture for some and not others, all on the basis of where each person sits.

The exposure is quiet. If you hired across state lines without updating your PTO policy by location, you may already be out of compliance and have no signal telling you so. The fix is to keep state-specific PTO rules for employees in mandatory-payout and forfeiture-ban states, reflect them in your handbook, and make sure your payroll and tracking systems know where each person actually works.

Payout Mechanics: Calculation, Tax, Timing, Penalties

When you do owe a PTO payout, four practical details determine how to do it correctly: how you calculate it, how it is taxed, when it is due, and what happens if you are late.

Calculation is straightforward: multiply the employee's accrued unused hours by their hourly rate. For a salaried employee, convert the salary to an hourly equivalent first, then multiply. An employee with 40 accrued hours at 25 dollars an hour is owed 1,000 dollars before withholding.

Taxation follows supplemental-wage rules. The Internal Revenue Service (IRS) treats a lump-sum payout of unused vacation as supplemental wages. Its Publication 15 sets the optional flat rate at 22 percent for 2026, so you can apply that federal supplemental withholding rate to the payout for federal income tax.

The flat rate is optional: you may instead combine the payout with regular wages and withhold on the total. Social Security (6.2 percent) and Medicare (1.45 percent) come off as well, so at the flat rate, estimated federal withholding comes to roughly 29.65 percent before any state income tax.

Timing is governed by the final-paycheck law in each state and varies widely. California requires immediate payout on involuntary termination, while Illinois gives you until the next regular payday and Tennessee the later of the next payday or 21 days.

Penalties for getting the timing wrong can be severe, from the California waiting-time penalty of up to 30 days of wages to the Massachusetts treble damages rule under its Wage Act. In the strict states a PTO payout mistake is a wage violation, so the timing and calculation rules in your own state are worth writing down.

No HR Team? Your PTO Compliance Checklist

If you are a founder or manager handling this without an HR department, you do not need to memorize all 50 states; you need to get the handful of things that apply to you right. The register below is where that gets written down.

The sheet takes one row per state you actually employ someone in, the four questions answered for that state, what your handbook currently says next to the answer, and the date you last checked it against the state labor agency. The gap column is the point of the exercise, because the mismatch between the rule and your own policy language is where the wage claim comes from.

One row per state, not one row per employee, and a row exists the moment somebody starts working from that state rather than when you get around to updating the handbook. The verification date matters as much as the answer: these rules move, and a row checked two years ago is a guess with a date on it.

Frequently Asked Questions