PTO accrual inputs
Choose Hours or Days, then enter all PTO amounts in that same unit.
Enter the current balance; negative values work for borrowed-leave policies.
{{ unitLabel }}
{{ accrualMethodHint }}
Enter a non-negative rate; decimals are allowed for fractional hours or days.
{{ rateSuffix }}
Use whole periods or months, e.g. 6 for the next six accrual cycles.
Enter PTO already used in this range; add future scheduled leave under Advanced.
{{ unitLabel }}
Pick a quick-fill, then adjust unit, rate, cap, and periods to match the policy.
Optional date for ledger labels; leave as-is if only balances matter.
Use final, even, or first-period placement to match how your report summarizes usage.
Enter regular eligible hours per period, such as 80 for a biweekly schedule.
Common values: 12 monthly, 24 semimonthly, 26 biweekly, or 52 weekly.
Choose the reporting increment, from 0.01 for detail to 1.00 for whole units.
{{ cap_enabled ? `Cap on: trim each period at ${formatAmount(balance_cap)}.` : 'Cap off: balances can grow above the configured cap amount.' }}
{{ cap_enabled ? 'On' : 'Off' }}
Enter the policy cap in {{ unitLabel }}, such as 120 hours or 15 days.
{{ unitLabel }}
{{ carryover_enabled ? carryoverHint : 'Carryover off: no reset checkpoint is applied.' }}
{{ carryover_enabled ? 'On' : 'Off' }}
Enter the maximum PTO carried past the checkpoint in {{ unitLabel }}.
{{ unitLabel }}
Use a whole period number, often the final period of a policy year.
Planned future leave:
Add optional future leave by period, amount, and note; historical PTO stays in the main field.
No planned future leave rows.
Use a whole period number from 1 to {{ normalizedPeriodCount }}.
Enter planned PTO in {{ unitLabel }}; decimals are allowed.
{{ unitLabel }}
Optional note up to 80 characters, e.g. vacation, shutdown, appointment.
Period Opening Earned Used Planned Cap lost Carryover trim Ending Copy
{{ row.label }} {{ formatAmount(row.opening) }} {{ formatAmount(row.earned) }} {{ formatAmount(row.used) }} {{ formatAmount(row.planned) }} {{ formatAmount(row.capLost) }} {{ formatAmount(row.carryoverLost) }} {{ formatAmount(row.ending) }}
Brief item Value Note Copy
{{ item.label }} {{ item.value }} {{ item.note }}
Policy check Status Review note Copy
{{ item.label }} {{ item.status }} {{ item.note }}
No valid PTO projection to chart.
No valid PTO projection to chart.

                    
Customize
Advanced
:

Introduction:

PTO accrual is how paid time off moves from a policy promise into a usable balance. Some employers credit a fixed amount each pay period, some spread an annual allowance across the year, and some earn leave from eligible hours worked. The arithmetic looks simple until the policy also has usage timing, maximum banks, carryover limits, or different rules for vacation, sick, personal, and protected leave.

A PTO balance is a ledger, not one isolated number. Each earning period opens with the prior balance, adds newly earned time, subtracts used or scheduled leave, and may be trimmed by a cap or reset rule. If a vacation is posted before the next accrual, the bank can go negative temporarily; if a cap is checked before later leave, earned time can be lost even when the ending balance later falls below the cap.

People usually run PTO projections before requesting a long break, reconciling a payroll balance, planning year-end carryover, or explaining why a handbook promise does not match an employee self-service balance. Pay frequency, eligible hours, the chosen unit, and the placement of already-used leave can all change the answer without changing the annual allowance.

Common PTO policy wording and projection effects
Policy wording Projection effect Common mistake
Annual allowance The yearly amount is spread across the policy's earning periods. Using 12 periods for a biweekly payroll, or 26 periods for a monthly plan.
Fixed deposit per pay period or month The same amount is credited every projected period. Treating a monthly deposit as a pay-period deposit.
Earned per eligible hour worked Accrual depends on eligible hours in each period. Using scheduled hours when the policy counts only eligible paid hours.
Cap or maximum bank Earned time may be lost when the balance is above the limit. Assuming later leave can recover hours that were already capped.
Carryover limit A checkpoint can trim the balance to the amount allowed past the reset. Placing the reset in the wrong period or applying it before leave is deducted.
PTO ledger flow from opening balance through accrual, used leave, planned leave, policy trims, and ending balance.

Two policy details deserve extra attention. A frontloaded bank and an earned-accrual bank can show the same current balance while meaning different things for borrowing, future availability, and separation payout. A combined PTO bank can also hide leave types that follow separate employer, contract, or legal rules.

Paid time off is also a policy and jurisdiction question, not just arithmetic. Vacation, sick leave, personal leave, and combined PTO banks can follow different rules, and U.S. federal law generally does not require ordinary vacation pay unless a contract, employer policy, state rule, public-sector rule, or specific federal-contract requirement says otherwise.

A projection is most useful when it is treated as a planning estimate. It can show whether scheduled leave is likely to overdraw the bank, whether a cap may waste future accrual, or whether a carryover rule may trim time at a checkpoint. It cannot by itself approve leave, settle a payout dispute, or replace the employer's official payroll record.

How to Use This Tool:

Start with the handbook wording, then check the ledger period where the balance changes in a surprising way.

  1. Choose Balance unit as hours or days. Keep Opening balance, Accrual rate, PTO already taken in range, caps, carryover limits, and planned leave rows in that same unit.
  2. Use Policy quick-fill only as a starting point. After applying a preset, confirm the unit, accrual method, rate, cap, carryover setting, and period count against the actual policy.
  3. Select Accrual method. Use Fixed per pay period or Fixed per month for a fixed deposit, Per hour worked for hourly earning rules, and Annual allowance spread over periods when the policy starts from a yearly amount.
  4. Enter Periods to project or Months to project. If the policy starts from an annual allowance, confirm Periods per year in Advanced so each projected period receives the right share.
  5. Use Historical usage timing to place already-used PTO at the first period, evenly across the range, or at the final period. This can change Lowest projected balance even when total usage is unchanged.
  6. Turn on Apply accrual cap or Apply carryover limit only when the policy has those limits. Enter the cap amount, carryover amount, and checkpoint period from the policy, not from a rough annual estimate.
  7. Add Planned future leave rows for scheduled vacations, shutdowns, appointments, or other future deductions. A row beyond the projection range is moved to the final period and shown as a warning.
  8. Review Accrual Ledger, Balance Snapshot, Policy Check, PTO Balance Runway, and PTO Accrual Movement. If a validation message appears, fix negative rates or usage, a projection length below 1, or an invalid annual-period value before relying on the result.

Interpreting Results:

Projected ending balance is the headline number, but it should not be read alone. Lowest projected balance shows whether the bank goes negative at any point, Cap and carryover loss shows time removed by policy limits, and Policy Check flags the conditions most likely to need a handbook or payroll review.

A positive ending balance can still hide a temporary shortfall if leave is deducted early and later accrual restores the account. A clear ending balance also does not prove the policy timing is correct. Compare the period-by-period movement in Accrual Ledger with the payroll system's posting order, especially around caps, carryover checkpoints, and display rounding.

  • Review on Balance runway means the ending balance or the lowest balance drops below zero.
  • Reached on Accrual cap means earned PTO was trimmed after accrual posted and before usage reduced the balance.
  • Trimmed on Carryover checkpoint means the checkpoint reduced the balance to the carryover limit.
  • Applied on Usage timing means already-used PTO was included according to the selected timing rule.

Technical Details:

A PTO projection is a repeated balance calculation. Each period starts with the prior ending balance, adds the period's earned PTO, applies a cap when one is active, subtracts historical usage and planned leave, and then applies a carryover trim only at the selected checkpoint period.

The earning rule controls the size of each period's credit. A fixed pay-period or monthly policy uses the entered rate directly. A per-hour policy multiplies the rate by eligible hours worked. An annual allowance divides the yearly amount by the number of periods in the policy year.

Formula Core:

The period equation shows the calculation order. Visible amounts are rounded to the selected display increment, while the running balance keeps full precision until it is formatted.

Ep = rate, rate x eligible hours, or annual allowance / periods per year Cp = max(0, balance after accrual - cap) when cap is on Rp = max(0, balance after usage and planned leave - carryover limit) at checkpoint Bp = Bp-1 +Ep -Cp -Up -Pp -Rp
PTO formula variables and units
Symbol Meaning Unit
B Running PTO balance at the end of the period. Hours or days, matching Balance unit.
E PTO earned during the period. Hours or days per period.
C Accrual removed by an active balance cap. Hours or days lost to cap.
U Already-used PTO placed by the selected timing rule. Hours or days deducted.
P Planned future leave assigned to the period. Hours or days deducted.
R Carryover trim applied at the checkpoint. Hours or days removed.
PTO accrual method and boundary rules
Area Rule Why it matters
Projection length At least 1 period and no more than 260 projected periods are used. Rows beyond the range are folded into the final period and flagged.
Historical usage timing Already-used PTO can be placed in the first period, spread evenly, or placed in the final period. The same total usage can produce a different lowest balance.
Cap timing The cap is checked after accrual posts and before usage is subtracted. Cap loss can occur even when later leave brings the ending balance below the cap.
Carryover timing The carryover checkpoint is clamped to the projected range and applied once after usage and planned leave for that period. A wrong checkpoint period can make the reset appear too early or too late.
Display rounding Visible balances and exports are rounded to 0.01, 0.05, 0.10, 0.25, 0.50, or 1.00. Small decimals can round away in the table while still affecting later periods.

With the default values, 24.00 opening hours plus 3.08 hours per period over six periods earns 18.48 hours. The default planned vacation row subtracts 16.00 hours in period 4, and 8.00 hours of already-used PTO is applied at the final period. The projected ending balance is 18.48 hours, with no cap loss or carryover trim because the 120.00 hour cap is not reached and carryover is off.

For annual-allowance policies, the period divisor is the main sensitivity. An 80-hour annual allowance over 26 biweekly periods earns about 3.08 hours per period, while the same annual allowance over 24 semimonthly periods earns about 3.33 hours per period. The annual total is the same, but short-range projections can differ because the earning cadence changed.

Limitations and Privacy:

This projection is a planning aid for arithmetic under the values entered. It does not decide leave approval, wage treatment, payout at separation, forfeiture, tax handling, state-law compliance, or contract rights. The calculator runs the projection in the browser, and the PTO values entered are not sent to a calculation server by the tool's own workflow.

  • Use payroll records as the source of truth for actual balances.
  • Confirm whether the policy combines PTO into one bank or separates vacation, sick, personal, statutory, or protected leave.
  • Check the handbook for the exact posting order around accrual caps and carryover resets.
  • Use legal, HR, payroll, or union guidance when the result affects pay, termination, protected leave, or a dispute.

Worked Examples:

Default six-period projection. Start with 24.00 hours, earn 3.08 hours per period for six periods, keep the default 16.00 hour planned vacation in period 4, and apply 8.00 hours of historical usage at the final period. Balance Snapshot shows 18.48 hours earned, 8.00 hours used, 16.00 hours of planned future leave, and a Projected ending balance of 18.48 hours.

Hourly accrual with mid-range leave. A policy earning 0.033333 hours per eligible hour and 80 eligible hours per period earns about 2.67 hours per period. With 10.00 opening hours, no historical usage, and a 12.00 hour planned leave row in period 3, Accrual Ledger falls to about 6.00 hours after that period and ends near 14.00 hours after later accruals.

Carryover trim at year end. A 20-day annual allowance over 12 periods with 8.00 opening days and a 5.00 day carryover limit at period 12 earns 20.00 days during the projection, then trims the balance to 5.00 days at the checkpoint. Policy Check should show Carryover checkpoint as Trimmed.

Planned leave outside the range. If a four-period projection includes a planned leave row for period 9, the row is applied to period 4 and a warning appears. Increase Periods to project or change the planned leave period if the scheduled leave really belongs later.

FAQ:

Can I mix hours and days?

No. Choose Balance unit first and enter every balance, rate, cap, carryover limit, usage amount, and planned leave amount in that same unit.

Why did the ending balance stay positive while Balance runway says Review?

The ledger can drop below zero before later accrual brings it back up. Check Lowest projected balance and the period row where the negative balance appears.

Why did cap loss appear if I used PTO later?

The cap is applied after accrual posts and before usage is subtracted. Once the cap trims earned PTO in that period, later usage does not restore the lost accrual.

Why am I seeing a validation error?

The calculator rejects negative accrual rates, negative usage, negative caps, negative carryover limits, projection lengths below 1, and annual-allowance periods per year of 0 or less.

Does this decide whether unused PTO must be paid out?

No. The result only projects the entered balance rules. Payout, forfeiture, approval, and protected-leave questions depend on the actual policy, jurisdiction, contract, and employment facts.

Glossary:

PTO bank
The balance of paid time off available under a policy.
Accrual
New PTO credited during a pay period, month, eligible-hour block, or policy year.
Opening balance
The amount available at the start of the projection before new accrual and deductions.
Annual allowance
A yearly PTO amount divided across the policy's earning periods.
Balance cap
A maximum bank that can remove earned PTO when the balance is above the limit.
Carryover checkpoint
The period where a carryover rule trims the balance to the amount allowed past a reset.
Planned leave
Future scheduled PTO deducted from a specific projected period.

References: