Balances people trust, because nothing is silently edited.
Request, approve, and see the balance move — with every movement kept, so the number can always be explained.
Request, approve, and see the balance move.
Employees request a date range with hours per day against a balance that is checked at request time. Supervisors approve or decline with a reason. Every movement (accrual, grant, use, adjustment) is an append-only ledger entry, and the balance is derived from the ledger rather than edited directly.
That is why the number can always be explained. Nobody has to remember what happened; the ledger shows it.
- Three plans ship: PTO, sick and supplemental, each configurable and effective-dated
- Supplemental award requests follow their own approval path
- Approved leave flows into the pay-period totals alongside worked hours
Your leave policy, configured once.
Plans carry their own accrual rules, negative-balance policy and posting rules. Holiday calendars are effective-dated templates assigned to populations, so a change next year does not rewrite last year.
Policy questions stay yours to decide: carryover, negative balances, how much accrues and when. They are settings, not behaviours you discover in month three.
- Pending leave is visible as pending until it is approved
- Holiday calendars sized to the population they are assigned to
- Every plan change is effective-dated like the rest of the record
See leave and time as one record.
A demo shows a request move from ask to balance to pay-period total.