If three of your employees walked in tomorrow and quit, how much would you owe them for vacation they earned but never took? If you are not tracking accrued PTO as a liability, you are already carrying a debt you cannot see — and in about half the states, that debt becomes a final paycheck you must pay on a statutory deadline, with daily penalties if you miss it.
Federal law does not require you to offer paid vacation at all. But once you do, two sets of rules take over: accounting rules that decide when that time becomes a liability on your books, and state wage-payment laws that decide whether you must cash it out when someone leaves. Small businesses that treat PTO as an informal perk until payroll day are the ones that end up surprised at year-end, at month-end close, or at termination.
This guide shows you how to accrue vacation correctly month by month, how to calculate the liability with payroll taxes, how cash and accrual books diverge, what happens to the balance when an employee quits, and the state-by-state payout patterns that determine whether a forfeiture clause you copied from a template will actually hold up.
Why Your PTO Balance Is Already a Debt
Under accrual accounting, you recognize an expense when the work is done, not when the cash moves. An employee who earns four hours of vacation this month has already performed the service that entitles them to paid time off later. Even if they do not take the time until December — or until they quit next year — the cost belongs to the period when it was earned.
That is why accrued vacation sits on the balance sheet as Accrued Vacation Payable, a current liability alongside accrued wages, not as a footnote you remember at year-end. If you use the cash basis for your tax return, you will not see the same line, but the economic obligation is identical. The difference is timing, not existence.
For many small employers the liability is material without looking large per person. Ten employees averaging 40 unused hours at $28 per hour is $11,200 in wages alone. Add the employer share of Social Security, Medicare, and state unemployment, and the true liability crosses $12,000 — before you consider a manager at a higher rate or an accrual cap you never enforced.
When GAAP Says You Must Accrue
Accounting for compensated absences lives in ASC 710-10-25-1. You accrue a liability when all four conditions are met at the same time:
- The employee has already performed the service. The right to the time off comes from work already done.
- The right vests or accumulates. Vesting means the employee can be paid for it even if they quit. Accumulating means it carries forward to a future period. If it does neither — a true use-it-or-lose-it grant that disappears at year-end with no carryover and no payout on exit — you generally do not accrue.
- Payment is probable. You expect some of the time will actually be taken or paid out.
- The amount can be reasonably estimated. You know the hours and the pay rate.
Most PTO policies that allow any carryover, or that promise payout at termination, meet all four. A policy that says "all unused vacation is forfeited on December 31 and never paid at separation" and is enforced consistently may not require an accrual — but that language collides immediately with state law in places like California, Colorado, and Montana, where forfeiture of earned vacation is prohibited outright. In those states you cannot contract your way out of the liability, so you must accrue.
Vesting vs. Accumulating Is Not Wordplay
A common source of confusion is the vesting distinction. Sick leave that accumulates but does not vest — the employee loses it if they quit, and can only use it if they are sick — is accrued only when it is probable the employee will use it before it expires. Vacation that accumulates and vests, which is the norm for PTO banks, is accrued at the full balance of earned but unused hours.
If you combine vacation and sick time into a single PTO bank, several states treat the entire bank as vacation wages. California has applied this to combined banks for decades: if any portion of the bank could be used as vacation, the whole balance can become payable at separation. You do not get to label the bank "PTO" and then claim the sick portion is forfeitable if your policy never separates the buckets.
How to Calculate the Liability
The formula is straightforward, but the details are where small businesses understate the number.
**Liability = Unused accrued hours × Current hourly rate × (1 + payroll tax burden) **
Include these pieces:
- ** Hours:** Earned minus taken, per employee, per your accrual schedule. If you grant 120 hours per year on an accrual basis, that is 10 hours per month, not 120 on January 1. If you grant upfront on January 1, the hours are earned by agreement on that date, not ratably — your policy language decides.
- ** Rate:** Use the current pay rate at the balance-sheet date, not the rate when the hours were earned. When you give a raise in November, every hour banked earlier in the year reprices to the new rate.
- ** Payroll tax burden:** Add the employer share you will owe when the time is taken or paid out — 7.65% for Social Security and Medicare up to the wage base and above, plus state unemployment and any other payroll-based contributions. Many businesses use a loaded rate of 7.65% to 9% as a practical estimate.
- ** Cap and carryover:** Apply your written cap. If you cap accrual at 160 hours, stop accumulating beyond that until the employee draws down. If you allow only 40 hours to carry over, the excess forfeited hours drop out — but only where forfeiture is legal.
A Small-Business Example
Imagine a team of five:
- Two hourly associates at $22/hour, each with 32 unused hours
- Two specialists at $34/hour, each with 48 unused hours
- One manager at $48/hour with 56 unused hours
Wages-only liability: (64 × 22) + (96 × 34) + (56 × 48) = $1,408 + $3,264 + $2,688 = $7,360
Add an 8% payroll tax load: $7,360 × 1.08 = $7,948.80
That $7,949 is the current liability before any year-end true-up. If the manager received a raise from $44 to $48 mid-year, the earlier hours already on the books need to be repriced — a step that is easy to miss if you roll forward last quarter's spreadsheet without updating rates.
Update the calculation at each month-end close, not just December 31. A quarterly or annual catch-up turns a smooth liability into a surprise expense spike.
The Journal Entries
You do not need a complex setup — three entries cover most situations, assuming accrual basis.
1. Month-end accrual for time earned this period
If employees earned $2,400 of vacation wages this month and the related employer payroll taxes are about $184:
- Debit: Vacation Wages Expense — $2,400
- Debit: Payroll Tax Expense — $184
- Credit: Accrued Vacation Payable — $2,400
- Credit: Accrued Payroll Taxes Payable — $184
Some businesses combine the tax load into the same liability account; separating it keeps the payroll tie-out cleaner.
2. When an employee takes PTO
The employee uses 8 hours at $30/hour, or $240:
- Debit: Accrued Vacation Payable — $240
- Debit: Accrued Payroll Taxes Payable — $18.36
- Credit: Cash (or Wages Payable through payroll) — $258.36
You do not double-count expense here — the expense was already recognized when the time was earned. You are settling the liability.
3. When an employee quits and you pay out the balance
The employee leaves with 40 unused hours at $30/hour:
- Debit: Accrued Vacation Payable — $1,200
- Debit: Accrued Payroll Taxes Payable — $91.80
- Credit: Cash — $1,291.80
If your policy or state law says the balance is forfeited, you reverse the accrual instead: debit the liability and credit Vacation Wages Expense (or a separate forfeiture gain) in the period the forfeiture occurs. Do not simply delete the hours from a spreadsheet without a reversing entry — your prior periods already recognized the expense.
If you are on the cash basis, you skip entries 1 and 2 for management purposes and recognize the whole cost in entry 2 or 3 when cash moves. Your tax return will match that pattern, but your management balance sheet will understate obligations. Many cash-basis owners keep a separate accrual worksheet for decision-making even if they do not post the entry formally.
Cash Basis vs. Accrual Basis: Why Your Books and Tax Return Disagree
The same PTO creates a temporary book-tax difference. For GAAP you expense it when earned. For federal income tax you generally deduct it when paid — when the employee takes the time or receives the payout.
That timing gap creates a deferred tax asset if you keep GAAP books. Using the $7,949 example above at a 25% combined tax rate, the deferred asset would be about $1,987. It reverses automatically as the time is used or paid. The asset belongs on your balance sheet; it is not a valuation allowance exercise for most small businesses, just a mechanical result of the deduction coming later.
If you present accrual-basis financials to a bank, the PTO liability affects your current ratio and working capital. Lenders that review your balance sheet at year-end will see it. Showing up with no PTO accrual while your handbook promises carryover and payout invites the question of what else is off the balance sheet.
What Happens When Someone Quits
No federal statute requires you to pay out unused vacation. The Fair Labor Standards Act is explicit: vacation, sick leave, and holiday pay are matters of agreement. Government-contract wage determinations are the narrow exception. For everyone else, the answer is "it depends on your state and your written policy."
Three practical tests decide the payout:
- Is accrued vacation considered wages in your state? In roughly 20 states it is. Where the statute says earned vacation is wages, you must pay it at separation even if your handbook says otherwise. An unenforceable forfeiture clause does not make the liability disappear.
- What does your written agreement say? In states where payout is not mandated, the policy controls — but only if it is clear, communicated, and applied consistently. "PTO is not paid at termination" must actually be in the document the employee acknowledged, not in a draft you meant to publish.
- Is the time earned or merely granted? Some states distinguish time that accrues as work is performed (earned) from time front-loaded on January 1 before it is earned (granted). Forfeiting unearned, unaccrued time is far more defensible than forfeiting earned time.
Three Buckets of State Law
You do not need to memorize 50 statutes to operate correctly — you need to know which bucket your state falls into and act accordingly. Confirm your specific state with your state labor agency or counsel, because legislatures adjust these categories.
Bucket 1 — Must pay accrued vacation as wages; use-it-or-lose-it prohibited. California, Colorado, Montana, Nebraska, and a handful of others. In these states, earned vacation never expires and cannot be forfeited. You may impose a reasonable accrual cap that pauses further earning once the ceiling is hit, but you cannot wipe a balance that already exists. California also requires the final payout at the employee's final rate, and final wages — including that payout — are due by the statutory deadline (immediately on involuntary termination, within 72 hours on voluntary resignation, or sooner if notice was given).
Bucket 2 — Must pay if your policy or contract promises payout, or is silent. The majority of states, including Illinois, Massachusetts, and many others. If your handbook promises payout, you must do it. If your handbook is silent on payout, many of these states treat silence as a promise to pay. To make forfeiture enforceable here, you need explicit, unambiguous written language that says unused time is not paid at separation — and you must not have a past practice of paying it anyway.
Bucket 3 — No payout required unless you agree to it. A smaller group including Florida, Georgia, and Texas, where there is no general statutory requirement to pay accrued but unused vacation at separation absent an agreement. Your policy still governs, and contractual promises are enforced, but the statute alone does not create the wage.
Two traps catch small businesses moving between buckets:
- The sick-leave combination trap. As noted, combining vacation and sick into one bank can convert a forfeitable sick balance into a payable wage in Bucket 1 states. If you want different rules for sick and vacation, keep separate banks and separate accrual records.
- The handbook contradiction. A handbook that says on page 12 "PTO is not paid at termination" and on page 18 "all accrued PTO will be paid within 14 days of separation" is not a policy — it is a lawsuit. Resolve the conflict before someone quits.
Final-Paycheck Deadlines and the Penalty for Missing Them
Payout, when required, is not just an amount — it is a deadline. States attach their own final-paycheck timing rules and penalties:
- California requires involuntary final wages immediately at termination and within 72 hours for a quit (sooner if 72-hour notice was given). An accrued-vacation payout that is late can trigger waiting-time penalties of up to 30 days of the employee's daily rate.
- Colorado requires payment of accrued vacation by the next regular payday or within 14 days, whichever is earlier.
- Illinois, where accrued vacation is treated as earned, requires the payout by the next regular payday.
- New York requires final wages, including vacation owed under policy, by the next regular payday, with liquidated damages and penalties for willful failures.
Even in states without a PTO-specific penalty, late final-pay statutes often apply to vacation wages as wages generally. The pattern is consistent: missing a $400 PTO payout can generate a penalty several multiples larger than the payout itself, plus the administrative cost of responding to a wage claim. Calendar the deadline by termination type and state, and treat the payout as part of the final payroll run, not as a correction you get to later.
Caps, Carryovers, and the Reasonable-Limit Balance
Accrual caps are the compliant alternative to use-it-or-lose-it forfeiture in restrictive states. Instead of wiping a balance on December 31, a cap pauses further accrual once the employee hits the ceiling — say, 1.5 times the annual accrual — and resumes when they use time and drop below it.
To make a cap workable:
- State the cap as a multiple of the annual accrual, not as an arbitrary hour number disconnected from the grant.
- Apply it prospectively and in writing, with advance notice. Cutting a balance retroactively looks like forfeiture under another name.
- Track it per employee in your payroll or HR system, not in a manager's spreadsheet that no one else reconciles.
Carryover limits serve a different purpose: they decide how much of the current year's grant can move into next year. A limit like "up to 40 hours carries over" is common outside Bucket 1 states, but in California and Colorado a carryover limit that forfeits earned time is not enforceable as a forfeiture. Frame it as a cap on future accrual rather than a wipe of past accrual if you operate in those states.
7 Bookkeeping Mistakes That Create PTO Disputes
1. Not accruing at all. The most common error is recognizing vacation only when it is taken. Your income statement understates labor cost in high-earning months and overstates it in vacation-heavy months, and your balance sheet hides the liability.
2. Forgetting the payroll tax load. Accruing wages without the employer tax distorts the liability and creates a mismatch when you pay. Load the rate consistently.
3. Not repricing after raises. A raise reprices the entire unused bank. Recalculate all affected employees in the same period the raise takes effect.
4. Copying a template forfeiture clause that your state prohibits. A use-it-or-lose-it sentence that is void in California does not protect you in California. It merely creates evidence that your policy was not reviewed for the states where you actually employ people.
5. Letting systems drift from policy. Your handbook says the cap is 160 hours, but your payroll software is set to 200. Or the software caps correctly but no one reconciles the spreadsheet you send to your accountant. Reconcile the system balance to the general ledger monthly.
6. Combining sick and vacation into one untracked bank without understanding the payout consequence. If you combine, budget and accrue as if every hour is payable where you operate — or separate the banks.
7. Leaving PTO off the pay stub. Several states require accurate PTO balances on wage statements. An inaccurate or missing balance is both a compliance miss and the exhibit an employee will attach to a wage claim.
A Monthly Checklist to Keep Your Liability Accurate
You do not need enterprise software to get this right. You need a repeatable close routine.
- Read the policy against the states where you have employees. Highlight the sentence that says whether unused time is paid at separation, the cap, the accrual rate, and the carryover rule. If you employ in Bucket 1 states, strike any forfeiture language for vacation and replace it with a cap.
- Pull the hours report from payroll. Earned minus taken per employee, not a company-wide total.
- Apply current rates and the loaded tax rate. Use the pay rate in effect at month-end.
- Post the accrual entry. Debit expense, credit liability. Keep vacation expense separate from regular wages so you can see the true cost of benefits.
- Reconcile the liability account. The general-ledger balance should equal the hours report times loaded rates. Investigate any variance before you close.
- Review caps and negative balances. No one should accrue beyond the cap, and unpaid time off that exceeds available PTO should not create a negative PTO bank unless your policy explicitly allows negative balances.
- Document terminations immediately. Calculate the payout at the final rate, calendar the state deadline, and include the payout in the final payroll run with appropriate withholding. File the calculation with the termination paperwork.
- Show the balance on the pay stub where required. Accuracy here prevents the "I had 80 hours, you say 32" dispute.
- Keep a GAAP worksheet even if you file cash basis. Management decisions — hiring, overtime, pricing — are better when they reflect the real obligation.
If you run Beancount or another plain-text ledger, this routine is a natural fit for a scheduled transaction or a small script that reads your payroll export and posts the month-end accrual automatically. The point is not the tool, it is the cadence: small, accurate accruals every month beat one painful true-up at year-end, and they leave an auditable trail when a final paycheck is questioned.
Simplify Your Financial Management
PTO feels like a people policy until it becomes a balance-sheet liability and a final-paycheck deadline. A monthly accrual habit keeps your books honest and your separations uneventful.
Beancount.io gives you plain-text accounting that is transparent, version-controlled, and ready for the kind of monthly close routine this topic rewards — you can see every accrual, every reversal, and every payout in a format you control. Explore the documentation and the Fava dashboard to see how versioned, auditable books make recurring liabilities easier to track, and visit pricing when you are ready to get started for free.