Leave Management
Aiden holds every leave policy as configuration — accrual, carry-forward, encashment, pro-rata joining — and keeps balances that attendance and payroll both respect, so leave never has to be reconciled twice.
What it does
- Configurable leave types and accrual rules
- Carry-forward, encashment and pro-rata joining
- Approval routing with delegation
- Leave-without-pay flowing straight into payroll
Your policy, not a vendor’s assumption
Leave rules differ by company, grade and sometimes province, and they change. Aiden treats leave types, accrual frequency, carry-forward caps, expiry, encashment and pro-rata rules for joiners and leavers as data you control.
Because the balance formula lives in one service, the figure an employee sees in self-service, the figure a manager sees when approving, and the figure payroll uses for encashment are always the same number.
Requests that route themselves
A leave request follows your approval workflow — line manager, department head, HR, or whatever your policy says — with delegation when an approver is away and escalation when nobody acts. Approvals arrive by notification and can be actioned without hunting for the request.
Once approved, the absence is reflected in attendance immediately, and any unpaid portion is already waiting for payroll.
Liability you can put a number on
Accrued leave is a real financial liability, and most Pakistani businesses only discover its size at settlement. Aiden values outstanding balances against current salaries on demand, so finance can see the exposure at any point rather than at year end.
Balances that survive an argument
Leave disputes are almost always arithmetic disputes: an employee believes they have three days left, the register says one, and nobody can reconstruct how either number was reached. Aiden derives balances from the ledger of accrual, usage, adjustment and encashment events, so the number can always be explained line by line.
Because attendance, self-service, approvals and payroll all read the same service, there is no second copy to drift. Adjustments — a credited comp-off, a corrected opening balance — are recorded as their own entries with a reason and an approver, rather than by editing a total.
A leave request, end to end
- 1An employee applies for three days annual leave from self-service; the balance shown is the same figure payroll uses.
- 2The request routes to their line manager, with escalation configured if it is not actioned in two days.
- 3The manager approves; the employee is notified and the days are reserved against the balance.
- 4Attendance marks those days as authorised absence rather than absent, so no deduction is triggered.
- 5At year end, the unused portion carries forward up to your cap, and anything above it expires per policy.
What it connects to
- Attendance & Time Tracking — authorised absence appears on the day record
- Payroll — unpaid leave and encashment reach the payslip
- Workflow & Approvals Engine — routes and escalates requests
Questions about leave management
Can we configure our own leave policy?
Yes. Leave types, accrual frequency, carry-forward caps, encashment and pro-rata rules are all configuration — no code change is needed to match your policy.