Compensated Absences Liability Under ASC 710-10: Accruing PTO, Vacation, and Sick Leave

Picture this: It's December 31, your books are about to close, and your controller drops a question that stops the conversation cold. "Did we accrue this year's unused vacation?" You glance at the payroll dashboard. Eighteen employees, an average of forty-three unused PTO hours each, and a wage base that has crept up six percent since January. Multiply it out, and the missing liability is real money — money that absolutely belongs on the December balance sheet, not the January income statement when employees finally cash it out.

That liability has a name, a citation, and a specific set of rules. It's called compensated absences, it lives in Accounting Standards Codification (ASC) 710-10, and it trips up far more growing businesses than it should. The good news: once you understand the four-part test and how the most common policies map onto it, the accrual becomes a quiet year-end checkbox rather than a January fire drill.

This guide walks through the recognition criteria, the journal entries, the tricky edge cases — sabbaticals, unlimited PTO, sick pay, carryover caps — and the practical bookkeeping habits that keep the reserve honest as it grows.

What Counts as a Compensated Absence

"Compensated absence" is the GAAP term for any future time off an employee can take while still being paid. The most familiar buckets are vacation, paid time off (PTO), and sick leave, but the definition also covers:

• Holiday pay (when carried, not when taken on a fixed calendar)
• Jury duty and military leave (where the employer tops up wages)
• Sabbaticals tied to length of service
• Severance-style "garden leave" earned with tenure
• Personal days and floating holidays that roll over

The unifying feature is that the employee earns the right by working, and that right results in a future cash outflow if exercised or paid out. ASC 710-10 governs whether and when that future outflow becomes a liability on today's balance sheet.

The Four-Part Test for Accrual

Under ASC 710-10-25-1, an employer must accrue a liability for future absences if all four of these conditions are met:

1. Services already rendered. The employee's right to the compensation arises from past work, not from future events.
2. Vests or accumulates. The right either vests (employee keeps it on termination) or accumulates (carries forward to later periods even if it never vests).
3. Payment is probable. Based on history and policy, the time off will be taken or paid out.
4. Amount can be reasonably estimated. You can calculate the dollar figure with reasonable accuracy.

If any one of those conditions fails, you do not accrue. The trick is that #2 — vests or accumulates — is broader than most managers assume. The right doesn't have to be both. Either one is enough.

Vesting vs. Accumulating, Spelled Out

Vesting means the employee gets paid for the time even if they quit. A standard "pay out unused vacation at termination" clause is a vesting right.

Accumulating means the time carries forward into next year and stays usable, even if the policy says, "Use it or lose it on December 31, but if you don't use it, it rolls into next year up to 80 hours." If the unused balance can be used in a future period, it accumulates. The carryover doesn't have to be unlimited; even a capped rollover counts as accumulating.

A right that is "use it by year-end or it disappears forever, with no termination payout" neither vests nor accumulates and is generally not accrued. But this is rarer than it sounds: many states (California, Colorado, Nebraska, Montana, and others) treat earned vacation as a vested wage by statute, overriding policy language and forcing accrual.

Sick Pay Has a Carve-Out

ASC 710-10-25-2 gives sick pay special treatment. An employer is permitted, but not required, to accrue a liability for nonvesting accumulating sick pay benefits — even when the other criteria are met. The logic: sick pay is contingent on actually being sick, and history shows most employees never use their full balance.

In practice, businesses choose between two policies:

• Combine vacation and sick into a single PTO bucket. The bucket then accrues in full because nothing inside it is identifiable as sick pay.
• Keep sick separate and elect not to accrue. Simpler bookkeeping, but only available when the sick pool genuinely can't be cashed out.

If your handbook says "any unused sick days are paid out at termination," the carve-out is gone — sick pay vests and must be accrued like vacation.

Sabbaticals: It Depends on Why You Grant Them

Per ASC 710-10-25-4, a sabbatical's accounting depends entirely on its purpose:

• For the employer's benefit (write a paper, attend training, develop a product the company will use): the time off is not attributable to past services. No accrual. Expense as taken.
• For the employee's benefit (a paid reward for tenure, with no work requirement during the leave): the compensation is earned over the requisite service period. Accrue ratably across that period.

A common structure — "every employee gets four weeks of paid sabbatical after seven years of service, with no work requirement during the leave" — is an accumulating, employee-benefit sabbatical. The expense should hit each of the seven years on the way in, not all at once when the leave is taken.

Unlimited PTO: The Surprise Non-Liability

Unlimited PTO is the rare policy that genuinely doesn't generate a balance-sheet reserve, provided you draft it correctly. Because there is no "balance" of unused hours, there is no accumulation. Because terminated employees have no quantifiable unused balance to cash out, there is no vesting. Both legs of criterion #2 fail, so no accrual is required.

Three caveats:

1. No termination payout language. If your policy or any state law forces a payout calculation at separation (some courts have looked at the average usage of similarly-situated employees), the right effectively vests and accrual returns.
2. No minimum accrued balance. Some "unlimited" policies sneak in a guaranteed floor (e.g., "you always have at least 80 hours available"). The floor accrues.
3. Disclosure may still be appropriate. Auditors often expect a note describing the policy and confirming that no liability is recorded.

If unlimited PTO is on the table primarily to remove the balance-sheet liability, get the language reviewed by counsel — not just HR. The accounting hinges on the legal enforceability of the "no carryover, no payout" structure.

How to Calculate the Accrual

The reserve at the balance-sheet date equals, for each employee:

Unused hours × hourly equivalent rate × probability of payment

For a salaried employee, the hourly equivalent is annual salary divided by standard annual hours (typically 2,080). Use the rate the employee will be paid at when the absence is taken — usually the current rate, but if you know a raise is locked in for January 1 and the policy lets balances roll forward, the higher rate is the more accurate measure. Probability is rarely modeled below 100 percent except where historical forfeiture is significant and well-documented.

Don't forget the employer's payroll tax burden on top — FICA, FUTA, and any state unemployment that will apply when the time is paid out. The reserve should be gross of those taxes; otherwise you understate the true cost.

A Worked Example

Suppose four employees end the year with these balances:

If the prior balance in "Accrued Compensated Absences" is $8,400, the adjustment is a $3,152 increase. Drop it into payroll expense and call it a year.

Journal Entries You'll Actually Use

For the routine year-end true-up:

Salaries and Wages Expense — Vacation     3,152
Payroll Tax Expense                          --
    Accrued Compensated Absences                   3,152

When an employee takes the time off and is paid:

Accrued Compensated Absences              1,260
    Cash / Payroll Clearing                        1,260

When an employee is paid out the balance at termination:

Accrued Compensated Absences              4,200
    Cash                                           4,200

If you discover that the reserve was overstated (employees forfeited rights or a policy change capped historical accruals), reverse the excess against current-period expense — don't park it in retained earnings unless the error is large enough to qualify as a correction of an error under ASC 250.

Common Mistakes That Inflate or Hide the Liability

Even well-run finance teams make the same handful of errors. Worth checking each one against your last close:

• Using the prior-year rate after raises. If wages went up, the reserve needs to go up even if hour balances didn't move.
• Excluding bonuses tied to pay. If vacation pay includes commission or shift differential, those should be in the rate.
• Forgetting payroll taxes. The IRS, the Social Security Administration, and the state aren't volunteering to absent themselves from the future paycheck.
• Accruing nothing for "use it or lose it" — when carryover actually exists. Even a 40-hour carryover cap means the right accumulates.
• Treating unlimited PTO as a free pass when state law disagrees. California courts have repeatedly questioned whether "unlimited" is genuinely unlimited.
• Skipping the test for sabbaticals. Long-service awards are often discovered for the first time during a Series A audit, with painful catch-up entries.
• Ignoring contractor true-ups. If a temporary worker becomes a W-2 employee mid-year and inherits a PTO balance, the accrual moves with them.

Cash Flow When the Liability Comes Due

A growing reserve is a non-cash expense — fine. But when employees actually take the time, you pay them at their current rate while productive output dips. That's a double hit to cash flow that doesn't show up anywhere on the balance sheet.

The smart move is to flag the reserve in your cash forecast as a tranche of future outflows, weighted by:

• Historical usage rate (most employees use 70-85 percent of accrued time within 18 months)
• Expected separations (terminations trigger lump payouts at current rates)
• Seasonal patterns (summer and December usage spikes)

If your liability has grown from $9,000 to $42,000 in three years and you operate on a 60-day cash buffer, you have a structural cash-flow risk hiding in plain sight. Some employers tackle it by capping carryover, by paying out balances above a threshold each March, or by buying back hours in exchange for a one-time bonus.

Bookkeeping Habits That Make the Year-End Painless

Accruing compensated absences isn't difficult math. It's a record-keeping discipline that breaks the moment payroll, HR, and accounting fall out of sync. A few habits that pay for themselves:

• Pull the unused-balance report on the last working day of every month, not just at year-end. Trends spotted in June are cheaper to fix than spreadsheets reconciled in February.
• Tie balances to a named system of record. If your payroll provider says "120 hours" and your HRIS says "104 hours," fix the underlying data feed; do not paper over it in a worksheet.
• Document the policy in plain text alongside your accounting policies file. When the policy changes, the diff is the audit trail.
• Reconcile the GL liability to the source report every month. A two-line journal entry every month beats a four-figure surprise every December.
• Treat the reserve as a real cash-flow item. Forecast it. Budget it. Don't let it grow silently.

Keep Your Compensation Liabilities Clear from Day One

Compensated absences are one of those quiet liabilities that look harmless until they aren't. The reserve grows in the background, year after year, and the only signal something is wrong is usually an audit comment or a startled investor reading your balance sheet. The fix is not exotic accounting — it's clean, auditable records that show, line by line, what each employee has earned, what's been paid, and what's left.

Beancount.io provides plain-text accounting that keeps every accrual entry, payroll true-up, and policy change inspectable in a way QuickBooks and spreadsheet hybrids can't match. Because every transaction is text, the diff is the audit trail — no black boxes, no hidden adjustments, no vendor lock-in. Get started for free and see why developers and finance teams are switching to plain-text accounting for the books that matter.