Methodology: Vacation Payout Calculator
What the calculator computes
The calculator takes four inputs — state/jurisdiction, unused vacation hours, final hourly rate, and (for generic states) whether the employer's policy promises payout — and produces one output: the base vacation payout owed at separation.
The math is simple: when payout is owed (per state rule + policy), the payout equals vacation hours × hourly rate. The branching logic is the value here, not the arithmetic.
What's modeled
Five mandatory-payout states by name, plus two generic catch-all entries:
- California (Labor Code §227.3) — earned vacation is wages; use-it-or-lose-it banned; §203 waiting-time penalty for late final pay.
- Colorado (CRS §8-4-101 + Nieto v. Clark's Market 2021) — earned vacation is wages; use-it-or-lose-it banned by state Supreme Court.
- Massachusetts (G.L. c.149 §148) — Wage Act; same-day final pay for involuntary discharge; treble damages for late payment.
- Nebraska (Neb. Rev. Stat. §48-1229) — earned vacation is wages; HFWA 2025 codified the combined-PTO trap.
- Montana (MCA §39-3-205) — earned vacation is wages; 110% penalty for late payment.
- Follows-policy state — generic option covering ~15 states (IL, NY, OH, IN, MD, NC, ND, OH, RI, WV, WI, NM, DC, LA, NH). Payout depends on what the employer's written policy says; the calculator asks the user.
- No-statute state — generic option covering ~30 states (TX, FL, GA, AZ, mountain-west, etc.). No payout required unless the policy explicitly promises it.
What's not modeled (and why)
The §203 waiting-time penalty (CA). Labor Code §203 imposes one day of wages per calendar day the final paycheck is late, capped at 30 days. Computing it requires the separation date AND the actual payment date, plus weekend/holiday handling and a "willful" determination. The calculator surfaces the rule as a note but doesn't compute the dollar figure — too many inputs needed for a quick-answer tool.
Treble damages (MA). Massachusetts c.149 §150 trebles unpaid wages plus attorney fees for late final pay. Same input-collection problem as CA §203.
Double damages (NE). Nebraska §48-1231 doubles unpaid wages + attorney fees for willful nonpayment.
110% penalty (MT). Montana MCA §39-3-205 applies a 110%-of-wages penalty for late final pay; not modeled as a dollar figure.
Blended regular rate. Workers paid multiple rates (shift differentials, non-discretionary bonuses, piece-rate, commissions) have a different blended rate for vacation payout under FLSA §7(g). Calculator uses a single hourly rate input.
Combined-PTO bank composition. The calculator surfaces the combined-PTO trap as a warning when a mandatory state is selected but can't detect whether the user's balance IS combined. Only the employer knows the leave-policy structure.
Probation-period clawback. Some employer policies attempt to claw back paid-out vacation if separation happens during probation. Generally illegal in mandatory-payout states; varies elsewhere. Not modeled.
State-specific nuances of follows-policy states. Illinois treats policy silence as default-to-payout. North Dakota has separate rules for voluntary vs involuntary separations. Rhode Island requires one year of service before payout obligations attach. The generic "Follows-policy state" option ignores these — users wanting state-specific accuracy should read the companion article.
Worked examples
Four scenarios spanning the four reason branches the calculator handles. Reproduce any of these by entering the inputs in the widget.
| State | Hours | Rate | Policy | Payout | Reason |
|---|---|---|---|---|---|
| California | 80h | $30 | n/a (mandatory) | $2,400 | mandatory by statute |
| Massachusetts | 80h | $30 | n/a (mandatory) | $2,400 | mandatory + treble damages on late pay |
| Follows-policy state | 80h | $30 | promises payout | $2,400 | policy promises payout |
| Follows-policy state | 80h | $30 | forfeits (use-it-or-lose-it) | $0 | policy forfeits earned vacation |
| No-statute state (TX/FL) | 80h | $30 | silent | $0 | no statute, policy silent |
Notice the same balance + rate produces 4 different payouts depending on state and policy. The branching logic is the value of the calculator; the arithmetic is trivial.
When this gets re-reviewed
Vacation-payout law moves slowly — most changes come from state-supreme-court rulings clarifying the wage status of earned vacation rather than new statutes. Re-review is triggered by any of these:
- State-supreme-court ruling — the load-bearing precedent is Nieto v. Clark's Market (Colo. 2021). A similar ruling in a sixth state would expand the named-mandatory list.
- Statutory amendment — the Nebraska HFWA (2025) codified the combined-PTO trap that was previously case-law. Any new state statute adopting wage treatment for earned vacation triggers a data-file update.
- Policy default changes — Illinois currently treats policy silence as default-to-payout. If another follows-policy state adopts an Illinois-style default, the generic bucket's behavior would need to split.
- Late-pay penalty rates change — CA §203, MA c.149 §150, NE §48-1231, MT §39-3-205. None are modeled as dollar figures, but their formulas appear in the methodology body and need updating if amended.
- Labor-commissioner opinion letter — DLSE-style guidance that changes the operational interpretation of an existing rule (e.g., the combined-PTO trap mechanics).
Data sources
State-specific rules come from primary sources:
- California DIR — Vacation FAQ + Labor Code §§201, 202, 203, 227.3
- Colorado CDLE — Wage and Hour + CRS §8-4-101 + Nieto v. Clark's Market (2021)
- Massachusetts AG — Wage Payment + G.L. c.149 §§148, 150
- Nebraska DOL — Wage and Hour + Neb. Rev. Stat. §§48-1229, 48-1231 + HFWA (2025)
- Montana ERD — Labor Standards + MCA §39-3-205
Companion article: Vacation Payout Laws by State.
How accurate is this?
Accurate enough for orientation — "do I have an unpaid-vacation problem, and what order of magnitude?" — not for litigation. Real damages math involves things the calculator doesn't collect: separation date, payment date, late-pay penalty cascades (§203 / treble / double damages / 110%), blended regular rate, attorney fees, and the specific posture of the claim. A calculator that collected all that would have a dozen inputs and most visitors would bounce before submitting.
This tool answers the typical query — "is vacation owed at separation in my state, and roughly how much?" — well enough for a quick check. For specific claim evaluation or policy design, that's what employment counsel is for.
Frequently asked questions
Why only 5 states named explicitly?
These are the five states with statutory mandatory payout — earned vacation is wages by state law, payout is required regardless of policy, use-it-or-lose-it is banned. Every other state either (a) follows the employer's written policy, or (b) has no statute at all. Both of those modes collapse to a single rule from the calculator's perspective ("depends on what the policy says"), so naming each individually would imply a level of state-specific math the calculator doesn't actually do.
Why don't you compute the §203 waiting-time penalty as a dollar figure?
Because it depends on day-by-day facts the calculator doesn't collect — the separation date, the actual payment date, weekend/holiday handling, and whether the delay was willful. The methodology FAQ explains the math (one day of wages per calendar day late, capped at 30 days) so users can compute their own exposure once they have the dates. Modeling it would require date pickers that most users don't have at hand and would imply legal-grade accuracy the rest of the calculator deliberately doesn't claim.
How is "final rate of pay" interpreted?
For hourly workers, the regular hourly rate at separation. For salaried workers, divide annual salary by 2,080 (52 weeks × 40 hours) for a standard equivalent. Workers with shift differentials, non-discretionary bonuses, or piece-rate components have a different blended regular rate under FLSA §7(g) — the calculator doesn't model this and assumes the user has the right hourly figure.
What about the combined-PTO trap warning?
The five mandatory-payout states treat combined vacation+sick PTO banks as vacation for payout purposes. If a worker has a 200-hour combined PTO balance in California, the entire 200 hours must be paid out — even if half was intended for sick use. The calculator surfaces this as a warning when a mandatory state is selected; it can't detect whether the user's balance IS combined (only the employer knows the leave-policy structure).
Does this handle remote workers correctly?
Implicitly yes — the calculator asks for the state where the WORK was performed, not where the employer is headquartered. The vacation-payout law of the work-location state governs. The article and methodology emphasize this because remote-worker compliance is the most-missed area in multi-state employment.
About Clockspot
Clockspot is online time clock software for small businesses — the simplest way to track employee time, with GPS location tracking, PTO accruals, job costing, and overtime calculation. Used in all 50 states since 2007.
Tracking vacation and sick leave separately so the right amount gets paid out when someone leaves is one of the things Clockspot handles — different leave types, different accrual rules, different payout rules per state. See how Clockspot tracks vacation.