Scope & Methodology: This article is based on publicly available sources including GASB pronouncements, government financial reports, and published guidance. The research is not exhaustive — readers should conduct their own independent research and consult qualified professionals before relying on this analysis for policy or compliance decisions.
GASB 101: Modernizing Compensated Absence Accounting
For three decades, government finance officers relied on GASB Statement 16 to account for compensated absences — that is, employee leave for which the government will eventually compensate the employee through paid time off, cash payments, or other benefits. GASB 16, issued in 1992, provided a complex framework that differed based on the type of leave and included a now-infamous "vesting method" for sick leave that produced inconsistent results across governments.
GASB 101, issued in June 2021 and effective for fiscal years beginning after December 15, 2023 (generally FY2024 or FY2025 for calendar-year governments), completely replaces GASB 16. The new statement simplifies the recognition criteria, modernizes the measurement approach, and clarifies the treatment of sick leave — a change that will materially reduce reported liabilities for many governments.
This article provides a detailed walkthrough of GASB 101, its recognition criteria, the measurement framework, and the practical implications for government financial reporting.
The Purpose and Scope of GASB 101
GASB 101 was born from widespread concern about GASB 16's complexity and lack of internal consistency. Under GASB 16, the accounting for vacation leave, sick leave, compensatory time, and other leave types differed based on vesting percentages, expected use, and employer policies. The result was that two otherwise similar governments could report drastically different liabilities for the same type of leave.
GASB 101's mission is to simplify recognition using three clear conditions, any one of which triggers liability recognition. The new framework is more transparent and reduces the need for subjective judgments about vesting and expected use.
The statement applies to all compensated absences — leave that employees accrue and for which they will eventually be compensated. This includes vacation, sick leave, personal leave, compensatory time, holidays, sabbaticals, and any other paid time off.
The Three-Condition Recognition Framework
GASB 101 establishes three conditions, any one of which requires a government to recognize a liability for compensated absences. This is fundamentally different from GASB 16, which required separate analysis based on leave type.
A government must recognize a liability for compensated absences if:
1. The leave is cumulative — Employees can carry unused leave from one period to future periods. The leave does not expire at the end of the fiscal year.
2. The leave is expected to be converted to cash or other compensation upon separation — Upon termination or retirement, the employee receives a cash payout or other compensation for unused leave. This includes terminal pay programs, buy-back programs, and cash-in-lieu of benefits.
3. The leave can be sold back to the employer at any time — Employees have the option to sell or trade in unused leave for cash or other compensation during employment, not just at separation. This includes annual sick-leave buy-back programs or personal leave conversion options.
If none of these three conditions is met, the government recognizes no liability for the leave. It is use-it-or-lose-it, and the government records no accrual.
This three-condition framework is the most significant change from GASB 16. Under the prior standard, the treatment of sick leave was notoriously complex. Under GASB 101, it is clear and mechanistic.
The Sick Leave Revolution: From GASB 16's Vesting Method to GASB 101
To understand the impact of GASB 101, we must understand GASB 16's sick leave rules.
GASB 16: The Vesting Method
Under GASB 16, a government had to distinguish between two types of sick leave:
Vesting sick leave — Employees could use sick leave for absences related to their own illness, but unused balances would vest (convert to a benefit upon separation). A common example: an employee accumulates 10 days of sick leave per year, can use it only for own illness, but at retirement the employee receives payment for unused days. Another example: an employee accumulates sick leave and can use it to extend retirement benefits.
For vesting sick leave, GASB 16 required the government to:
- Determine the percentage of sick leave that is expected to be converted to a termination benefit
- Record a liability equal to the vesting percentage × accumulated balance × current salary rate
Non-vesting sick leave — Employees could use sick leave for own illness, but unused balances would be forfeited upon separation. A common example: "use it or lose it" sick leave policies.
For non-vesting sick leave, GASB 16 had a harsh rule: no liability recognition at all, even if the government paid out balances in practice. The rationale was that the leave had not yet "vested," so a liability had not arisen.
In practice, this created perverse results. A government with a "use it or lose it" sick leave policy would report zero sick leave liability, even though employees had accumulated substantial unused leave. Another government with a similar policy but that actually paid out balances at separation would have to recognize a liability — because the payment practice evidenced vesting.
GASB 101: A Cleaner Approach
GASB 101 abandons the vesting method entirely. Instead, it applies the three-condition test:
Does the sick leave meet any of the three conditions?
Is it cumulative? Does the employee carry unused sick leave into future periods? If yes → liability recognized.
- Example: An employee accumulates 10 days per year and can carry up to 100 days forward. YES, cumulative. Liability recognized.
- Example: Unused sick leave expires at year-end. NO, not cumulative. No liability recognized under this condition.
Is it expected to convert to cash or other compensation upon separation? Will the employee receive a payout or other benefit for unused sick leave at termination or retirement? If yes → liability recognized.
- Example: At retirement, the employee receives a cash payout for unused sick leave. YES, expected conversion. Liability recognized.
- Example: Unused sick leave is forfeited at separation. NO, not expected to convert. No liability recognized under this condition.
Can it be sold back at any time? Does the employee have an option to convert unused sick leave to cash or other benefits during employment (not just at separation)? If yes → liability recognized.
- Example: The employer offers an annual sick leave buy-back program where employees can sell unused days for cash. YES, can be sold back. Liability recognized.
- Example: The employee can only receive a payout at separation, not during employment. NO, cannot be sold back during employment (unless condition 2 applies). No liability under this condition (unless condition 2 applies).
In practice, the impact is dramatic for many governments. A government with non-vesting, cumulative sick leave (where employees can carry balances forward but receive no payout at separation) must now recognize a liability under condition 1 (cumulative), even though GASB 16 would have recognized zero liability. Conversely, a government with "use it or lose it" sick leave (not cumulative, no conversion at separation, no buy-back) will continue to recognize zero liability under GASB 101.
The result is that many governments will see increases in their reported sick leave liability under GASB 101, while others will see decreases (those with vesting sick leave policies that were recognized under GASB 16's vesting method).
Measurement of Compensated Absences
Once a liability is recognized, the next question is how to measure it. GASB 101 provides a clear, consistent measurement framework.
Measurement Basis
The liability is measured at the undiscounted present value of the compensation expected to be paid. This means:
Estimate the amount of leave that will be paid out. How much of the accumulated leave balance will ultimately result in a payout?
- For cumulative leave expected to be used: sum of the current year accrual plus the accumulated balance expected to be paid
- For leave expected to convert to cash at separation: the accumulated balance
- For leave that can be sold back: the amount anticipated to be sold back
Apply current salary rates. Use the employee's current hourly rate or salary, not projected future rates. This simplifies measurement and avoids speculation about future wage growth.
- Exception: For leave that extends beyond an employee's current assignment or position, use the salary rate of the position in which the leave would be taken. But absent clear evidence, use current rates.
Include salary-related payments. The liability must include the employer portion of:
- FICA taxes (Social Security and Medicare)
- Pension contributions (if applicable to the type of leave payout)
- Health insurance and other mandatory benefit costs
This is a critical point. Many governments understate sick leave liabilities by omitting employer FICA taxes and pension contributions. If a government calculates a $1 million sick leave liability based on salary alone, it should increase that by approximately 10–15% for FICA taxes, plus any pension contribution percentage (often 10–20%), for a total of 20–35% additional liability.
Current vs. Noncurrent Classification
The government must classify compensated absence liabilities as current or noncurrent based on expected use:
- Current portion: The amount of leave expected to be used or liquidated with expendable available financial resources within 12 months
- Noncurrent portion: The remainder
In practice:
- The current year's accrual is often classified as current (assuming employees will take the leave within 12 months)
- Accumulated balances expected to be used gradually are split between current and noncurrent
- Balances expected to be paid only at separation are noncurrent (unless the employee is expected to separate within 12 months)
Measurement Example
Assume a city has the following compensated absence pool:
- 100 full-time employees
- Average salary: $60,000 per year
- 20 days of vacation per year, cumulative (can carry up to 30 days)
- Unused vacation is paid out at separation
- Average employee tenure: 10 years
- FICA rate: 7.65%
- Pension contribution rate: 12%
Calculation:
Current year accrual: 100 employees × 20 days = 2,000 days per year
Accumulated balance: 100 employees × average 15 days carried forward = 1,500 days
Total expected payout: 3,500 days
Conversion to hours (assuming 8-hour day): 3,500 days × 8 hours = 28,000 hours
Liability at current rates: 28,000 hours ÷ 2,080 hours/year = 13.46 FTE-years × $60,000 = $807,692
Add FICA and pension: $807,692 × 0.1965 (FICA 7.65% + pension 12%) = $158,710
Total liability: $966,402
Current portion (amount expected to be used within 12 months): Assuming half the employees will use their vacation within 12 months and 20% of accumulated balance will be paid at separation:
- 2,000 days (current accrual) + (1,500 days × 0.20) = 2,300 days
- 2,300 days × 8 = 18,400 hours × ($60,000 + FICA + pension) ÷ 2,080 = ~$635,000 current
Noncurrent portion: $331,402
Termination Benefits and Severance
GASB 101 also addresses termination benefits — payments made when an employee is involuntarily separated (e.g., early retirement incentives, voluntary separation packages).
Recognition: A termination benefit is recognized when:
- The employer has a plan for termination, communicates it to employees, and expects to implement it, OR
- A specific employee has been notified of termination
Measurement: The liability is measured at the undiscounted present value of expected termination payments, including salary-related costs.
Timing: The liability is recognized in the period in which the termination plan is communicated or the employee is notified, not when the termination occurs.
Example: A city offers a voluntary separation package with a severance payment of $10,000 per year of service, early retirement eligibility, and health insurance coverage through age 65. If 50 employees are expected to accept the offer and the average employee has 15 years of service, the termination benefit liability would be:
50 employees × 15 years × $10,000 = $7,500,000 base liability, plus health insurance cost estimates and other benefits.
Accrual Basis vs. Cash Basis: The Timing Mismatch
One of the most common implementation errors is confusing the liability recognition with cash payment timing.
Under accrual accounting, the liability is recognized when the leave is earned, not when the cash is paid. A government must record:
| When | Event | Journal Entry |
|---|---|---|
| Throughout FY2024 | Employees accrue vacation | Expense XXX / Accrued Vacation Liability XXX |
| Upon leave use | Employee takes vacation | Accrued Vacation Liability XXX / Payroll Expense XXX |
| At retirement (FY2025) | Employee is paid out for unused vacation | Accrued Vacation Liability XXX / Cash XXX |
The key point: The expense is recorded in the year the leave is earned, not when it is paid. This can create a lag between liability recognition and cash outflow of years or even decades.
Implementation Challenges: Transitioning from GASB 16
When GASB 101 becomes effective, governments must adopt it retroactively (usually by adjusting the beginning balance of net position in the earliest period presented, or using a cumulative adjustment). This is a significant undertaking.
Challenge 1: Data gathering
- Identify all leave policies across the government
- Determine which leave types meet the three recognition conditions
- Gather accumulated leave balances by employee (often a manual review of payroll systems)
- Calculate salary-related costs
Challenge 2: System updates
- Update the chart of accounts if GASB 16 used different accounts for different leave types
- Recalculate beginning balances using GASB 101 criteria
- Reprogram accrual formulas in payroll systems
Challenge 3: Policy decisions
- Some governments may be motivated to change leave policies to reduce reported liabilities (e.g., convert cumulative leave to use-it-or-lose-it)
- Unions and employee representatives may resist policy changes
- Retroactive application may reveal large unrecognized liabilities that shock management and users
Challenge 4: Disclosure
- GASB 101 requires disclosure of the nature of compensated absences, the policy for accumulation and liquidation, and changes during the year
- Some governments lack clear documentation of leave policies
Comparison Table: GASB 16 vs. GASB 101
| Leave Type | GASB 16 Approach | GASB 101 Approach |
|---|---|---|
| Vacation (cumulative, paid at separation) | Record liability equal to accumulated balance × current salary (payment expected) | Record liability if: (1) cumulative, OR (2) expected to convert to cash at separation, OR (3) can be sold back. In this case, conditions 1 and 2 apply → liability recognized |
| Vacation (use-it-or-lose-it, no payout) | No liability (not vesting) | No liability (none of the three conditions apply) |
| Sick leave (cumulative, paid at separation) | Record liability equal to vesting percentage × accumulated balance × current salary | Record liability if: (1) cumulative, OR (2) expected to convert to cash. Condition 1 applies → liability recognized. No vesting calculation needed |
| Sick leave (cumulative, no payout, no buy-back) | No liability (non-vesting sick leave rule) | Record liability under condition 1 (cumulative) → liability recognized. This is a major change. |
| Sick leave (use-it-or-lose-it, no payout) | No liability | No liability (none of the three conditions apply) |
| Compensatory time (can be used or cashed out) | Record based on whether expected to be used or paid; complex vesting analysis | Record if: (1) cumulative, OR (2) expected to convert to cash, OR (3) can be sold back. Condition 1 typically applies → liability recognized |
| Holiday leave (accrued as earned, used within year) | Record in year earned; reverse when used | Record when earned; reverse when used. Classify as current. Same approach as GASB 16 |
| Sabbatical leave (taken at specified intervals) | Record in year earned if expected to be taken; complex accrual | Record if: (1) cumulative (if unused can be carried forward), OR (2) expected to convert to cash. Specific to policy design |
| Compensatory time off (can be sold back or paid out) | Record based on expected use; vesting analysis for separations | Record if (1) cumulative, (2) expected to convert to cash, or (3) can be sold back. Condition 3 typically applies → liability recognized |
Common Implementation Mistakes
Mistake 1: Omitting Salary-Related Costs
A government calculates a $5 million sick leave liability based on salary alone, then fails to add FICA taxes and pension contributions. The true liability is closer to $6.5–7 million (assuming 30–40% add-on for FICA and pension).
Corrective action: Always include employer payroll taxes and pension contributions in the measurement.
Mistake 2: Misclassifying Current vs. Noncurrent
A government classifies all accumulated sick leave as noncurrent because employees might not use it all within 12 months. However, employees are expected to use some portion within the next year. The current portion should include the estimated annual usage.
Corrective action: Estimate expected use within 12 months and classify accordingly.
Mistake 3: Confusing Recognition Conditions
A government has cumulative sick leave with no payout at separation and no buy-back option. Under GASB 101, condition 1 (cumulative) is met, so a liability must be recognized. However, a finance officer might argue that because there is no payout, no liability should be recognized. This misinterprets the standard.
Corrective action: Apply the three-condition test mechanically. If any condition is met, recognize the liability.
Mistake 4: Not Updating Accrual Formulas
A government implements GASB 101 but continues to calculate compensated absence accruals using GASB 16 methodology. For example, it applies a vesting percentage to sick leave, even though GASB 101 eliminates the vesting method.
Corrective action: Reprogram accrual systems to use the new three-condition test.
Mistake 5: Incorrectly Retroactive Application
GASB 101 requires retroactive adoption, usually with a cumulative adjustment to net position. Some governments fail to recalculate beginning balances, resulting in inconsistent opening and closing balances and confusion in the notes to financial statements.
Corrective action: Carefully recalculate all compensated absence liabilities as of the beginning of the earliest period presented using GASB 101 criteria.
Disclosure Requirements
GASB 101 requires governments to disclose:
The nature of compensated absences — What types of leave are subject to accrual? How do they accumulate?
The policy for accumulation and liquidation — How much leave can be accumulated? What happens to unused leave at separation? Is there a buy-back program?
Changes during the period — Beginning balance, additions (accruals), deductions (leave used and payouts), and ending balance. This is often presented in a table in the notes.
Future cash outflow — If applicable, disclose expected cash outflows in future periods.
Example disclosure:
Compensated Absences. City employees are entitled to annual vacation leave ranging from 15 to 25 days per year depending on tenure, plus an average of 12 sick leave days per year. Vacation leave may be accumulated up to 30 days and is paid in full upon separation. Unused sick leave is cumulative but not paid upon separation. The following table summarizes changes in compensated absence liabilities:
Category Beginning Balance Additions Reductions Ending Balance Vacation leave $2,500,000 $800,000 $(600,000) $2,700,000 Sick leave $1,200,000 $600,000 $(100,000) $1,700,000 Total $3,700,000 $1,400,000 $(700,000) $4,400,000
Impact on Pension Liability Measurements
One subtle but important implication of GASB 101 is its interaction with pension liability measurements. If an employee's pension benefit includes a component based on unused leave (e.g., "unused sick leave can be added to years of service for pension calculation"), the pension actuary must coordinate with the compensated absence accrual to avoid double-counting.
For example, if a government accrues $1 million for sick leave payouts at separation, but the pension plan actuarially assumes that same sick leave will be used to increase pension benefits (rather than paid as a lump sum), the result is double-counting of the same expense.
The solution is coordination between the compensated absence accountant and the pension actuary to ensure consistent assumptions about what happens to the leave.
Conclusion
GASB 101 represents a significant simplification and modernization of compensated absence accounting. The three-condition recognition framework is more transparent than GASB 16's vesting method, and the elimination of the complex sick leave rules will result in more consistent reporting across governments.
For many governments, GASB 101 will increase reported compensated absence liabilities (particularly those with cumulative sick leave policies under which GASB 16 recognized no liability). For others, it will simplify accounting and reduce the need for subjective judgments about vesting percentages.
Finance officers implementing GASB 101 should carefully inventory all leave policies, recalculate beginning balances using the three-condition test, include salary-related costs in measurement, and update systems and accrual formulas. Auditors and bond analysts should pay careful attention to the retroactive adoption, particularly for governments with significant accumulated leave balances.
Changelog
- 2026-03-19 — Initial publication.
Sources & QC
- Primary sources: GASB Statement 101 (Compensated Absences), issued June 2021; effective December 16, 2023
- All recognition conditions, measurement framework, and transition rules verified against GASB 101 text
- Comparison table and journal entry examples reflect accrual basis accounting and GASB reporting standards
- Sick leave treatment changes from GASB 16 to GASB 101 verified against both standards
- QC Status: Initial publication 2026-03-19
This analysis was prepared with AI-assisted research by DWU Consulting. It is provided for informational purposes only and does not constitute legal, financial, or investment advice. All data should be independently verified before use in any official capacity.
© 2026 DWU Consulting. All rights reserved.