Where the payout question actually gets decided, using the two states that are clearest. California is the strictest of the states that protect leave on separation. Labor Code section 227.3 provides that "whenever a contract of employment or employer policy provides for paid vacations, and an employee is terminated without having taken off his vested vacation time, all vested vacation shall be paid to him as wages at his final rate", and adds that a policy "shall not provide for forfeiture of vested vacation time upon termination." The California Labor Commissioner's own guidance explains what makes leave vested: "Under California law, earned vacation time is considered wages, and vacation time is earned, or vests, as labor is performed."
Read those two together and the mechanism is plain. The obligation attaches to vested vacation, and vacation vests as labor is performed — which is another way of saying it vests through accrual. A policy that credits nothing as labor is performed produces no vested vacation, so section 227.3 has nothing to operate on. The same employer therefore owes a departing California employee a cash payout under a fifteen-day accrual policy and, on the face of the statute, nothing under a genuine unlimited policy.
Massachusetts reaches the same place by a different route. General Laws chapter 149, section 148, defines "wages" to include "any holiday or vacation payments due an employee under an oral or written agreement." The qualifier is the whole point: the statute makes vacation pay a wage only to the extent an agreement made it due. An unlimited policy makes nothing due, so nothing is a wage.
Neither of these is a peculiarity of one legislature. Both statutes protect something the policy created, which means a policy that creates nothing is outside them. Other states protect leave on separation and others do not, and the terms differ, so the question for any individual reader is answered by their own state's wage law rather than by either of these.
The word "genuine" is doing work in the paragraph above, and it is the part worth being careful about. A policy that is called unlimited but operates like an allowance — a stated expectation of a certain number of days, an informal cap that is enforced, a balance tracked in the background — is a question of fact rather than a question of the label on the handbook page. Where a dispute arises, what a state agency or court examines is how the policy actually worked, not what it was called. An employee weighing this should note what the policy does in practice, because that is what the evidence would be.
What replaces the balance is a set of soft constraints, and they are harder to plan around. Under an accrual policy the question "can I take three weeks in October" has an arithmetic answer that the employee can compute alone. Under an unlimited policy the same question is a negotiation with a manager, subject to business need and coverage, and there is no accrued entitlement to point at. That is not automatically worse: an employee who would never have accrued three weeks in their first year may be able to take it. It is, though, a different kind of thing to plan against, and it is the reason the useful questions about an unlimited policy are about culture and approval practice rather than about the policy text.
Two mechanical points that are easy to miss. First, an unlimited policy does not displace statutory leave. Family and medical leave, state paid family and medical leave, jury duty, military leave and state or local sick leave ordinances all continue to apply on their own terms, and a policy may or may not run concurrently with them. Second, because there is no balance, there is nothing to carry into a new job, nothing to be paid at a final rate, and nothing that appears on a final paycheck — which also means there is nothing to argue about, in either direction.
