PTO vs Vacation: What Is the Difference?

The version of this question that cost me money was not the definitional one. I understood perfectly well that vacation is a type of PTO. What I did not understand, when I set up a single combined PTO bank because it seemed simpler, was that I had just converted every sick day my employees would ever accrue into a payable wage. Nobody told me. I found out when someone left with a large balance and my accountant explained what I owed.

That is the real content of this comparison, and almost every article on it stops before reaching it. Yes, all vacation is PTO and not all PTO is vacation, and that distinction is worth ten seconds. The distinction worth actually reading about is that the two policy models produce different legal treatment, different costs at separation, and different employee behavior, and that choosing between them is a real decision with real consequences.

This guide covers the definitions properly, then spends the rest of its time on the decision: what each model does well, what bundling sick leave into a PTO bank costs you in a payout state, why a PTO bank does not exempt you from sick leave mandates, and how a business with five to fifty people and no HR department should actually choose. I build the accrual tracking and balance management that make either model administrable into FirstHR. This is general information rather than legal advice, and time-off rules vary sharply by state, so confirm yours.

The Short Answer

All vacation is PTO, but not all PTO is vacation. Paid time off is the umbrella category covering every paid day an employee takes away from work, including vacation, sick days, personal days, and often bereavement and floating holidays. Vacation is one specific type of PTO, taken for rest, travel, or recreation.

That is the definitional answer, and it resolves the question as asked. But when an employer says PTO and another employer says vacation, they are usually signaling something more useful than a taxonomy: they are describing which policy model they run. PTO typically means a single combined bank of days usable for any reason. Vacation typically means a separate allowance, with sick time tracked in its own bucket alongside it. Those two designs behave very differently, and the rest of this guide is about that difference.

What Each Term Actually Means

Getting the vocabulary precise is worth doing once, because a surprising amount of confusion in time-off policy comes from two people using the same word to mean different things.

Neither of these is legally mandated at the federal level, which is the baseline every US employer starts from. The Fair Labor Standards Act does not require payment for time not worked, including vacations, sick leave, or federal holidays, and treats these as a matter of agreement between employer and employee. What complicates that clean baseline is that a growing number of states and cities do mandate paid sick leave specifically, which is a point I return to below.

PTO vs Vacation, Side by Side

Laying the two against each other on the dimensions that actually matter to an employer makes the practical difference visible faster than any amount of definitional prose.

Reading down that table, a pattern emerges. The PTO bank wins decisively on simplicity and flexibility, which are exactly the things a business without an HR department values most. The separate model wins on cost control and legal cleanliness, which are exactly the things that bite you later, when someone leaves or a state auditor asks a question.

That tension is the whole decision, and it does not have a universal answer. It has an answer that depends on your state and your workforce, and I will get to how to make it. First, the two models deserve a proper look.

The Two Policy Models

Almost every US employer runs one of two designs, and separating them cleanly is the fastest way to understand what you are actually choosing between.

The separate-buckets model remains the more common design across US employers, though consolidated leave plans are far from rare. Per US Bureau of Labor Statistics data, about 35 percent of workers with paid sick leave have it as part of a consolidated leave plan rather than a standalone sick bucket, which means roughly two thirds still keep the categories separate. Neither design is unusual, and neither is a signal of a serious or unserious employer.

The behavioral difference between them is real and frequently underrated. In a PTO bank, an employee who wakes up ill knows that taking the day costs them a day they could have spent somewhere better. That creates a quiet, persistent incentive to come to work sick, which is bad for them, bad for your other staff, and bad for you. Separate sick leave removes that tradeoff entirely: a sick day costs nothing but a sick day. If your business depends on people being physically present around each other, that is not a small consideration.

Which Model Wins on What

Stated plainly, with the tradeoffs on the table rather than buried.

Those pros are the reason PTO banks are appealing to a small business, and they are genuine. Fewer categories means fewer approvals, fewer arguments, fewer spreadsheets, and less of the specific administrative friction that a founder doing HR on top of their real job cannot afford. If your entire decision rested on ease of running the thing, the bank would win outright.

The cons are the reason the decision is not that simple, and the first one is the one that surprises people. It deserves its own section, because it is where the abstract distinction between PTO and vacation converts into a number on a final paycheck.

The Payout Trap Nobody Warns You About

This is the most important section of this article and the thing almost no comparison guide surfaces properly. In several states, accrued vacation is treated as earned wages that vest as the employee earns them. It cannot be forfeited, it cannot expire, and it must be paid out in cash when the employee leaves. Statutory paid sick leave, by contrast, generally does not have to be paid out.

Now put those two rules next to each other and look at what a PTO bank does. When you combine sick leave and vacation into a single pool, the entire pool is typically treated as vacation-equivalent, which means every hour of it becomes payable at separation. The sick days you would have owed nothing on, had you tracked them separately, are now cash.

California is the clearest example and the one worth understanding even if you are not there, because it shapes how many other states think about this. Per the California Department of Industrial Relations, there is no requirement to provide vacation at all, but once an employer establishes a vacation policy, accrued vacation is a form of wages that vests as it is earned, cannot be forfeited, and must be paid at the final rate of pay on separation. Use-it-or-lose-it vacation policies are therefore prohibited there, though a reasonable accrual cap is permitted: an employee stops accruing further time once they hit the cap, which is not the same as losing time already earned.

The rule varies by state, which is precisely why you cannot copy someone else's handbook. Some states require payout, some permit forfeiture, some are silent. Some prohibit use-it-or-lose-it, some allow it. Before you write a carryover or payout clause, confirm the rule in every state where you have employees, and revisit the state-by-state PTO rules if you operate in more than one.

A PTO Bank Does Not Exempt You From Sick Leave Laws

The second thing employers get wrong about PTO banks is assuming that the bank replaces a sick leave mandate. It does not. If your state or city requires paid sick leave, your PTO bank must independently satisfy every requirement of that law, or you are out of compliance regardless of how generous the bank is.

California is again instructive on the mechanics. Its paid sick leave law permits an employer to provide sick leave through an existing PTO plan, but only if that plan satisfies the accrual, carryover, and use requirements of the sick leave law. The mandate does not disappear because you called the pool something else; the pool simply has to be good enough to contain it.

Three requirements typically travel with a sick leave mandate and are easy to miss when designing a bank. The accrual rate must be at least what the law requires, which is often expressed as one hour per some number of hours worked. Carryover rules must be honored. And, crucially, you generally may not require an employee to explain why they are using the time, which is a rule people violate constantly by demanding a reason for a PTO day.

That last one is worth pausing on because it undercuts one of the perceived advantages of the bank. Employers often like a PTO bank because it lets them stop policing the reason for absences. But if a mandate covers the time, you are legally required not to police it, so the flexibility was never yours to grant in the first place. The deeper treatment of the distinction between these two categories is in the PTO versus sick time guide.

How Much Time Off to Offer

Once you have picked a model, the second question is the number, and it is worth anchoring against what employers actually do rather than guessing. Two benchmarks matter: what the market offers, and how much access varies by employer size.

The practical benchmark for a vacation-only allowance is roughly ten to fifteen days, typically increasing with tenure, plus about eight paid holidays. If you are running a consolidated bank instead, you generally need to offer more total days than a vacation-only figure, because that single pool now has to absorb illness and personal matters as well. A realistic small-business PTO bank commonly lands somewhere between fifteen and twenty days.

The mistake to avoid is quoting a bank number as if it were a vacation number. An employer offering fifteen days of consolidated PTO is not more generous than an employer offering twelve vacation days plus a separate sick allowance; they are roughly equivalent, and a candidate who has thought about it will notice. Be honest about what the number contains.

How to Choose, for a Small Business

Here is the decision sequence I would run if I were setting this up again from scratch at a fifteen-person business, in the order the questions actually matter.

The first question dominates the others, and that is deliberate. If you have employees in a state that requires payout of accrued vacation, the structural cost of a PTO bank is real and recurring, and it should drive the decision rather than being discovered later. That does not automatically mean separate buckets are right; it means that if you choose the bank anyway, you are choosing it with the cost understood rather than stumbling into it.

The fourth question is the one people skip and then regret. A coverage-critical hourly workforce plus a PTO bank equals people coming to work sick, because the bank makes illness expensive in a way separate sick leave does not. If your team works shoulder to shoulder in a kitchen or on a shop floor, that is not a philosophical concern, it is an operational one.

Once the model is chosen, the implementation is mechanical, and doing it in the right order prevents most of the disputes that arise later.

The last step is where a small business quietly loses time. Accruals compound, caps have to be enforced, and balances need to be visible to the employee, and doing that in a spreadsheet across a growing team is exactly the kind of task that works until it suddenly does not. The broader treatment of how paid time off works sits in the PTO guide.

Frequently Asked Questions