These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Leave management
Example screen with sample data
Leave management
Help employees understand their leave and give managers a clear view of the time being requested. The calculation follows the employee’s effective schedule and policy, while the balance preserves the difference between available days, future commitments and absence already taken.
OverviewPending Leave Approvals×
Core HR · Leave management
New
Pending Leave Approvals
Leave requests
| Request number | Employee | Operational label | Start date | End date | Days | |
|---|---|---|---|---|---|---|
| LR-98027 | Omar Haddad | Annual leave, May 12-16 | 19 Oct | 25 Oct | 28,398.60 | |
| LR-18034 | Hana Park | Sick leave, October 3 | 21 Oct | 29 Oct | 17,576.25 | |
| LR-66679 | Leila Farouk | Parental leave, November 1 start | 15 Oct | 19 Oct | 9,709.85 | |
| LR-67817 | Sofia Petrov | Personal day, June 9 | 15 Oct | 20 Oct | 7,336.86 | |
| LR-78102 | Omar Haddad | Bereavement leave, April 22-24 | 31 Oct | 09 Nov | 30,189.37 |
6 of 6 records
Annual leave, May 12-16Leave requests · LR-98027
SubmittedEmployeeOmar Haddad
Start date19 Oct
End date25 Oct
Days28,398.60
What you can do
Calculate the dates the employee will miss
A request includes both its start and end date. Its daily breakdown uses the approved employee work pattern, local calendar, holidays and date overrides in effect for each date. It does not assume that everyone works the same weekdays or hours.
A full scheduled working day counts as one day, including a part-time scheduled day. Partial absence is a fraction of that day’s scheduled hours; nonworking dates contribute no leave. The request retains this calculation and its policy, calendar and schedule versions.
- Check employment and leave eligibility on the requested dates.
- Reject overlapping absence that would use the same time twice.
- Split cross-year requests into the relevant leave-year balances.
- Resolve missing or conflicting policy settings before reservation.
Use the applicable policy without guessing
Country, employer and employment-type rules determine the eligible leave policy through configured precedence. Explicit exceptions require their authorized review. Documentation requirements retain a protected evidence path rather than exposing sensitive reasons to the line manager.
The policy defines its leave year, permitted negative balance, any advance reservation limit, fractional precision and earning rules. An advance reservation is authority to commit future time; it is not an accrual of days that have not yet been earned.
A material date, type or fraction change returns for calculation and review. An existing approval cannot follow a different daily breakdown automatically, and later schedule changes do not silently replace the basis of an accepted request.
Reserve the request through approval
Submitting a valid request reserves its eligible day fractions atomically against the relevant balances. Submitted requests and approved future leave both remain pending commitments. Approval changes the request’s authority without releasing the reserved days for another request.
| Leave event | Balance effect |
|---|---|
| Submit | Reserve the requested eligible fractions |
| Approve | Keep those future fractions reserved |
| Take an elapsed day | Move the same fraction from pending to taken |
| Reject or cancel unused time | Release only the unconsumed reserved fraction |
For example, available time falls when a request is reserved. It does not fall a second time when the same days move into taken leave. Concurrent requests compare the current balance version so they cannot spend the same available days.
Give the right person the decision
The assigned Manager reviews routine leave within current scope. HR Manager handles the policy’s required escalations or designated leave types. Actual-person conflict checks prevent self-approval, including through another role or an expired delegation.
Pending Leave Approvals presents the operational dates, duration and decision context. Manager receives safe documentation-readiness information where needed, rather than medical files or sensitive explanations. A broader reporting tree does not override those field restrictions.
Recognize absence as it happens
Daily confirmation moves only the elapsed approved fraction from pending to taken under the configured factual or elapsed-day rule. The whole future interval is not recorded as completed absence on its first day. Any required leave-of-absence employment change follows its own approved lifecycle event.
The assigned Manager or HR Manager confirms unused cancellation under policy before releasing reserved time. Correcting absence already taken or changing an earned balance requires independent HR Manager review. The original contribution remains visible, and a repeated request cannot release or reverse it twice.
Keep earnings and year-end movements explainable
Annual, monthly, per-pay-period and lump accrual methods use their configured period or entitlement event. Each earning has one stable identity, with explicit eligibility, proration, rounding and annual limits. A per-pay-period calendar can come from an external system without bringing payroll calculation into Core HR.
Year-end close resolves pending reservations before one paired carryover transfer under the approved cap. The old closing balance remains historical and cannot be spent again. Carryover preserves the source of reserved days. Expiry cannot silently remove the funding behind an approved future request. Cross-year allocations and corrections reconcile each affected balance instead of applying today’s rules to every historical day.
Opening migration uses reconciled balance buckets with reserved-day details. Historical accruals and taken leave remain evidence and are not posted again on top of those opening values. Leave Utilization reports earned, used, carried and pending time against that disclosed basis; medical or statutory conclusions are not inferred from a usage pattern.
What it keeps track of
Data model- Leave types
- Leave categories with country- and class-scoped accrual rules. Vacation, Sick, Parental, Bereavement, Unpaid, Jury Duty.
- Leave policies
- Effective country/type/entity leave rule with explicit schedule, reservation, accrual and rollover semantics.
- Work calendars
- Versioned local holiday/nonwork date basis used only for day-based leave calculation.
- Work schedules
- Effective employee work-pattern snapshot for leave dates; not time tracking or shift-roster software.
- Leave requests
- Employee-submitted leave requests requiring manager approval.
- Leave days
- Frozen daily fraction, leave-year and balance allocation with explicit reserved/taken/cancelled evidence.
- Leave entries
- Append-only signed day ledger; each business effect changes explicit balance buckets atomically.
- Leave balances
- Derived day balance for one employee, leave-type pool and leave year; effective ledger entries and active daily reservations are the authority.
- Approval decisions
- Immutable actual-person decision bound to exact subject, revision, domain scope and conflict exclusions.
- Employment spells
- Dated employment episode for a stable employee identity, preserving rehire breaks and employer changes.
Who uses it
Permissions- Employee
- Prepares leave requests and supplies permitted absence facts.
- Manager
- Reviews assigned routine requests.
- HR Manager
- Handles required escalation, policy and balance corrections.
- HR Specialist
- Administers explicitly granted work without inheriting approval authority.
- Admin
- Maintains reviewed technical controls.
Set up Core HR your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.