Leave Management Guide
End-to-end leave from policy setup to daily requests.
Leave types
Supported types: annual, sick, unpaid, other (organization configuration).
Leave policy
Route: /hrms/leave (display) · template from /hrms/onboarding
One policy per organization (current product limit).
| Field | Purpose |
|---|---|
| Annual entitlement | Base days per year |
| Carry-over cap | Max days carried (if used) |
| Approval flags | Manager / HR / payroll stages |
Payroll here is an approval stage label — not payroll processing.
Leave year
Calculated from policy and hire date. Pro-rata for mid-year hires.
Entitlement and balances
- Engine computes balance from entitlement, approved leave, adjustments
- Opening balances:
opening_balance_dayson import (M26)
Working patterns
STANDARD default (Mon–Fri). Affects day counting for leave requests. Non-standard patterns have limited engine support.
Holiday calendars
Organisation calendar shell; dates entered manually. Intersects with working days for leave calculation where implemented.
Request flow
- Employee →
/hrms/my-leave(type, dates, reason) - Pending manager → manager action
- Pending HR → HR action
- Approved or Rejected
- Balance updates on approval
Cancellation
If supported in UI, employee or admin cancels pending/approved per rules — verify on request detail.
HR administration
HR sees all requests at /hrms/leave, can act on HR-stage items.
Part-time behaviour
LIMITED — standard pattern assumed unless working pattern extended.
Carry-over
Configurable cap on policy; not automatic statutory rules.
Historical migration
Use import opening_balance_days for migrated balances; does not import historical leave transactions.
Worked example (illustrative)
EXAMPLE: 20-day entitlement, hire date 1 July, pro-rata ≈ 10 days first year. Opening balance 3 days from prior system → total available per engine rules.
Not legal advice for any country.
Help
/help/leave