PTO Accrual and Rollover Ledger

How to use PTO Accrual and Rollover Ledger

Choose worked-hour or whole-period accrual and enter your rate and hour caps. Process dated accrual, use and rollover rows in source order, reporting the requested credit, cap withholding, expiration and exact final balance.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Choose worked-hour or whole-period accrual and enter your rate and hour caps. Process dated accrual, use and rollover rows in source order, reporting the requested credit, cap withholding, expiration and exact final balance.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–200 distinct events, Gregorian dates 1900–9999 in nondecreasing order from the opening date. Hour balances, rate and event units are nonnegative decimal strings with up to 6 places and at most 1,000,000. Fixed-period units must be whole. Opening and rollover caps cannot exceed maximum balance.
• Accrual is credited then capped at its own event. Same-date ordering matters. Usage cannot borrow below zero, and rollover occurs only where explicitly entered. No automatic January reset, working-day calculation, holiday calendar, payout, employer eligibility or employment-law rule.
• This is user-policy arithmetic, not an official PTO record or advice on lawful forfeiture. No employee system is contacted or changed.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.