All articles
Leave4 min read·

The Complete Guide to Leave Management: Types, Requests, Carryover, and Encashment

How to design a leave policy that runs itself: creating leave types, allocating balances, handling requests and approvals, automatic carryover, and turning unused days into cash.

S

SimpleHR Team

SimpleHR

SimpleHR leave management dashboard with requests and employee balances

Leave management is one of those things that feels simple until someone’s leave doesn’t get approved on time, and then everyone knows your name. Done well, it’s a quiet system: employees request time off, managers approve it, balances stay accurate, and nobody has to chase anyone down.

This guide walks through how to set up leave so it runs itself: defining leave types, allocating balances, handling requests and approvals, automatic year-end carryover, and (if your policy allows) letting employees convert unused days into cash.

Start by defining your leave types

Before anyone can take time off, your HR team creates the leave types your company recognizes, typically annual leave, sick leave, and maybe unpaid or special leave. Each type carries the rules that shape how it behaves.

  • Name & description: e.g. “Annual Leave: 20 days per year.”
  • Default duration: the baseline number of days for the type.
  • Paid or unpaid: paid leaves are compensated; unpaid leaves are not.
  • Carryover: whether unused days roll into the next year, and the maximum that can roll over.
  • Encashment: whether unused days can be converted to cash, and the maximum allowed.

Leave types come first

You have to create leave types before you can allocate them to employees, and employees can’t request leave until they have an allocation. Setup order matters: types → allocations → requests.

Allocate balances to employees

Once a leave type exists, it can be allocated to employees. The default duration is a starting point: you can customize the exact balance per employee in their profile. This is how you handle different policies for different people (e.g. more days for senior staff).

Handle requests and approvals cleanly

The best leave workflow is boring in the best way: request in, notification out, decision back.

Employees submit a leave request from their My Leave Requests page. Their manager is notified (by email or push, depending on how you’ve configured notifications) and reviews it. On approval or rejection, the employee is notified of the decision. Everything is tracked, nothing gets lost in a mailbox.

ActorCan doTool
EmployeeSubmit & track own requestsMy Leave Requests
ManagerApprove/reject own & subordinates’Leave Requests
AdminApprove/reject all requestsLeave Requests

Automate year-end carryover

The dreaded January spreadsheet (calculating who carried over how many days) is exactly the kind of work HR software should remove. When a new year starts, SimpleHR can Create New Year Allocations for all employees in one action.

If carryover is enabled for a leave type, unused days from the previous year are automatically added to the new allocation (up to the maximum you set). Employees don’t even need to submit carryover requests; it just happens.

Carryover in action

Annual leave has carryover enabled with a 5-day maximum. An employee ends the year with 8 unused days. Their new allocation automatically includes up to 5 rolled-over days. No spreadsheet, no follow-up emails.

Turn unused leave into cash with encashment

Some companies let employees convert unused leave days into money, a benefit that rewards people who don’t take all their time off. Encashment works through the same request flow: an employee requests to encash available days, a manager approves, and the amount is tracked.

  1. Open the Leave Encashment section on the My Leave Requests page.
  2. Choose the leave type and the number of available days to convert.
  3. Submit the request; it appears as Pending.
  4. The manager or admin approves or rejects (a reason is required for rejection).
  5. You’re notified of the decision by email or push.

Encashment is optional per leave type and capped by a maximum number of days, so you control exactly how much time can be monetized under your policy.

Don’t forget the company holiday calendar

A shared holiday calendar keeps everyone aligned. Admins and managers add public holidays for the whole company, and everyone sees upcoming holidays on the dashboard. Note that holidays are informational; they don’t automatically add or remove leave days, even if they overlap with an employee’s leave.

Frequently asked questions

Does carryover require employees to submit anything?
No. Unused days are carried over automatically when new year allocations are created, as long as carryover is enabled for the leave type and within the maximum allowed.
Can different employees have different leave balances?
Yes. The default duration is just a starting point; you can customize each employee’s allocation in their profile to match your policy.
How do employees request encashment?
Through the Leave Encashment section on the My Leave Requests page. It’s only available if the leave type allows encashment and within the configured maximum.
Can I turn the leave module off entirely?
Yes. Leave (and related modules) can be enabled or disabled from Settings. Disabling hides all related pages and widgets for every user.

The bottom line

Leave management runs smoothly when the policy is encoded up front: clear leave types, accurate allocations, a clean request-and-approve flow, automatic carryover, and optional encashment. Configure those once, and leave becomes the quiet, reliable process it’s meant to be for employees and HR alike.

Put it into practice

Explore the live demo or grab the source code and set up SimpleHR for your team today.