PTO policy is a financial document, not an HR nicety

It's tempting to treat the time-off policy as a feel-good paragraph in the handbook. It isn't. Accrued, unused PTO is a real liability on your books, in several states it must be paid out at termination, and the accrual rules you choose quietly determine how much that liability grows. A vague policy ("take time when you need it") and a sloppy accrual implementation are how small companies end up with a five-figure surprise the first time a long-tenured employee leaves.

So write the policy like the financial document it is. The good news: once the rules are explicit, the math is mechanical, and the whole thing can run on autopilot.

Step 1: pick an accrual model

There are three common models, and the right one depends on your size and cash-flow tolerance, not on what sounds generous.

  1. Accrual (per-period). Employees earn a fixed amount of PTO each pay period — say 4.62 hours per biweekly period for a 15-day annual policy. This is the default for most companies because it ties the liability to time actually worked and limits exposure if someone leaves early in the year. The tradeoff is that new hires have very little PTO for the first few months.

  2. Lump-sum (front-loaded). The full annual balance lands on January 1 (or the work anniversary). Simple for employees to understand, but it maximizes your liability on day one of the year and creates a payout headache if someone front-loads, takes it all, and leaves in February.

  3. Unlimited / discretionary. No accrual, no balance, no payout liability — which is precisely why finance teams like it. The catch is that unlimited PTO often reduces time taken (no balance to "use up"), and several states still require you to track and pay out time that was effectively earned. It is not a way to avoid the rules; it's a way to relocate them.

For most growing companies, per-period accrual is the safe default. It's predictable, it's defensible, and it scales without nasty surprises.

Step 2: nail the four numbers that define the policy

A complete PTO policy answers four questions in numbers, not prose:

  • Accrual rate and period. How many hours per week, biweekly, semimonthly, or monthly period. Derive it from the annual target divided by the number of periods.
  • The cap. A maximum balance beyond which accrual stops ("accrual cap" or "use-it-or-lose-it ceiling"). Without a cap, balances — and your liability — grow forever. A common cap is 1.5x to 2x the annual accrual.
  • Carryover. How much rolls into the next year. Some states prohibit pure use-it-or-lose-it for earned vacation, so a cap-with-rollover model is usually safer than a hard reset.
  • Waiting period. Whether new hires accrue from day one or after a probationary period (often 90 days). Be explicit, because this is a frequent source of disputes.

Write these as a table in your handbook by tenure band (e.g., 15 days years 0–2, 20 days years 3–5, 25 days after). Tenure-based accrual is itself a retention lever — and a cheaper one than comp (see retention strategies that outperform comp hikes).

Step 3: separate the leave types

Lumping everything into one "PTO" bucket is simpler but often illegal. Sick leave is mandated and regulated separately in many states and cities, with its own accrual minimums and carryover rules — you generally cannot fold it into discretionary vacation. At minimum, track these as distinct balances: vacation/PTO, sick, unpaid, bereavement, jury duty, and parental leave.

Hosting HR's leave management module tracks a separate balance per leave type precisely because the rules differ — sick time accrues and carries over under different law than vacation, and conflating them is a compliance trap. Whatever system you use, keep the buckets distinct so you can apply the right rules and report cleanly.

Step 4: automate the accrual (or it won't survive contact with reality)

Here is where most policies quietly break. A beautifully written policy that depends on someone manually crediting hours every pay period will drift the moment that person is busy, on leave, or gone. Within a year your balances are wrong, your liability number is fiction, and the year-end reconciliation is a multi-day scramble.

The fix is to make accrual a scheduled job, not a human task. Set the rate, period, and cap once per person per leave type, and let the system credit balances automatically every cycle — catching up missed periods, clamping at the cap, and writing an audit-log entry for every credit. That's exactly how the automatic accrual scheduling works in Hosting HR: a daily job credits each balance once per elapsed period, so December's balances are correct because every prior period was correct. The audit trail matters as much as the automation — when an employee disputes a balance, you want a dated record of every credit and deduction, not a recollection.

The same discipline applies to deductions: approving a leave request should deduct from the matching balance automatically, and cancelling it should restore the hours. Manual reconciliation between "approved requests" and "balances" is the second most common way PTO accounting goes wrong.

Step 5: handle the state-law landmines

You don't need to be a lawyer, but you do need to know where the landmines are:

  • Payout at termination. Several states (California chief among them) treat accrued vacation as earned wages that must be paid out on separation. Your cap and carryover choices directly size that liability.
  • Use-it-or-lose-it limits. Some states prohibit forfeiting earned vacation outright; a cap that stops accrual is allowed where a policy that deletes earned time is not. Know the difference for every state you employ in.
  • Sick-leave mandates. Many jurisdictions require a minimum sick-leave accrual and carryover. Your policy floor is the law, not your preference.
  • Remote employees. An employee working from a state triggers that state's leave law regardless of where your office is. Multi-state employers should map their policy against every state they hire in. (The same trap applies to pay disclosure — see salary transparency: a state-by-state map.)

A short policy beats a perfect one nobody reads

The best PTO policy is the one your team actually understands and your system actually enforces. Put the four numbers in a table, separate the leave types, automate the accrual with an audit trail, and check it against the law in every state you employ in. Do that and the year-end balance scramble simply stops happening — the balances were right all along.