Employee Leave Management in Nepal: A Practical Guide

Leave disputes rarely come from bad people. They come from unwritten rules. One manager lets a staff member take a day by message, another insists on a form, and at year-end nobody agrees on the balance. A clear leave process, written once and followed by everyone, removes most of these arguments. This guide shows how to build one for a Nepali workplace.

Step 1: List your leave types

Start with what your appointment letters and policy already promise. Typical categories include annual or home leave, sick leave, casual leave, maternity and paternity leave, mourning leave and unpaid leave. Public holidays and weekly off days are separate. Entitlements and conditions are shaped by the Labour Act and its regulations as well as your contracts, so have them reviewed by your lawyer or labour officer, and then write the final version in your own handbook. Software only enforces what you give it.

Step 2: Decide how balances work

For each type, record:

• How many days an employee earns and from when
• Whether unused days carry forward, and up to how many
• Whether unused days can be encashed at exit or year-end
• Whether the leave needs a document, such as a medical note after a certain number of days
• Whether weekends and public holidays inside the leave period are counted

Choose a leave year. Many Nepali organisations follow the fiscal year from Shrawan, others follow the calendar year. Either works if you are consistent and the system rolls balances over on the right date.

Step 3: Define the request and approval flow

A good flow has three parts. The employee submits a request with dates, type and reason. The direct manager approves or rejects, with a comment. HR confirms the balance and records it. For longer leave you may add a second approver. Specify how much notice is expected for planned leave and what counts as an emergency.

When the flow lives in software, requests wait in an approval inbox instead of getting lost in WhatsApp messages. Staff can see the status, and managers can see who else in the team is already away before approving.

Step 4: Load the holiday calendar

Nepal has many public holidays, and the dates of festivals follow the lunar calendar, so they differ each year in Bikram Sambat. Some holidays apply to specific communities or genders. Load the list when the government announces it and mark which holidays apply to your organisation. This avoids deducting leave for a day the office was closed.

Step 5: Handle the awkward cases in writing

Situation	Decide in advance
Half-day leave	Is it allowed, and is it counted as 0.5 day?
Sick on a Sunday or Saturday	Does the weekend inside a sick period count?
Working on a public holiday	Substitute leave or extra pay?
Leave before probation ends	Is any leave allowed, and is it unpaid?
Balance runs out	Unpaid leave, advance on next year, or refusal?
Employee leaves with a negative balance	Is it deducted from final settlement?

Step 6: Connect leave to attendance and salary

Approved leave should show on the attendance sheet as leave, not as absence. Unpaid leave should flow into the salary calculation as a deduction under the same proration rule you use for joiners. If your attendance is captured by a device, an attendance system that reads approved leave will avoid the monthly argument about who was "absent" but actually on leave.

Step 7: Review at year-end

Before the leave year closes, send each employee a statement of their balance. Ask them to confirm or query within a week. Then process carry-forward and encashment according to your policy. Because everything is recorded, this takes an afternoon instead of a fortnight.

Common mistakes

The first is relying on messages. A "yes, take tomorrow off" in a chat never reaches HR. The second is giving managers no visibility of team leave, which results in unplanned gaps. The third is changing policy mid-year without recording the effective date. The fourth is forgetting that leave balances are a liability: unused days that can be encashed are a cost, and the owner should see that figure.

Using software for leave

A leave module in HR management software holds your rules, calculates balances, shows a team calendar and keeps the history. It does not replace judgement. Managers still decide whether a request suits the workload. But it removes counting errors and lost messages.

A worked example

Consider a company with thirty staff and a policy of an agreed number of annual leave days, with a limited carry-forward. Sita applies for four days around a festival. The system checks her balance, shows her manager that two other team members are already off on two of those days, and the manager approves three days and asks her to move one. The decision is recorded with a comment. When the month closes, the approved days flow to attendance as leave and nothing is deducted from pay. At year-end Sita receives a statement showing the days taken and the days carried forward. Nobody had to count anything by hand.

Communicating the policy

A rule that is not understood will be broken. Share the leave policy at joining, post a summary where staff can see it and repeat the key points whenever you change the process. Explain the reason behind notice rules: teams need time to cover work. When people understand the reason they follow the rule more willingly, and managers find it easier to say no when they must.

Next step

Draft your leave table this week: type, days, carry-forward, document needed, who approves. Share it with us on WhatsApp and we will set it up in a demo so you can test requests and approvals yourself.

Get a demo and quote for HR Management Software

Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.

Chat on WhatsApp

Or call / WhatsApp +977 9846280400

Your name Phone / WhatsApp Email (optional) Business / organisation What do you need?

Request demo

More guides on HR Management Software