Leave management in most Nepali organizations runs on a WhatsApp message and a handshake. An employee messages their manager requesting leave, the manager replies with approval or a counter-offer, and then something or nothing gets recorded in a register or spreadsheet. The leave management software Nepal businesses need replaces this informal process with one that tracks every request, records every approval, maintains accurate balances, and generates the reports that Labour Act compliance requires.
The informal approach creates two categories of problem. The first is employee disputes: when an employee believes they have 12 days of home leave remaining and HR says they have 7, and neither party can produce a clean record that resolves the disagreement, the conversation becomes personal rather than factual. The second is operational planning: when managers cannot see a team calendar showing who is on leave on which days, staffing decisions are made with incomplete information - leading to under-resourced periods, overlapping leave approvals, and service disruptions.
A structured leave management system addresses both. Every request is documented, every approval is recorded with a timestamp, every balance is calculated from the record, and every approved leave is visible on a team calendar. The system is also the foundation for leave encashment calculations at resignation, which requires accurate accumulated leave balances per employee.
Nepal Labour Act 2074 Leave Entitlements
Labour Act 2074 defines several categories of leave with specific entitlements. The leave system must be configured to match these provisions - organizations that define their own leave categories without reference to the Act risk either underproviding what the Act requires or confusing the categories in ways that create compliance gaps.
Below is a reference summary of the main leave types under Labour Act 2074. Note that specific entitlement figures, accumulation limits, and encashment provisions are subject to the current Labour Act provisions and any subsequent amendments. Verify the current entitlements with the Department of Labour or the Labour Act as amended:
| Leave Type | Entitlement | Key Notes |
|---|---|---|
| Home Leave (Earned) | 1 day per 20 days worked (~18 days/year) | Accrues after completing 1 year; can accumulate to a ceiling per Act provisions |
| Sick Leave | 12 days per year | Medical certificate required for consecutive absences beyond 3 days |
| Maternity Leave | 60 working days fully paid; up to 98 days total | Applies to female employees who have completed 180 days of service |
| Paternity Leave | 15 days | To be taken within 60 days of child's birth |
| Mourning Leave | 13 days | For death of close family members per the Act's defined category |
| Public Holidays | Per Nepal government gazette annually | Published list varies each year; organizations must update their leave calendar |
Nepal's public holiday list is published each fiscal year by the Nepal government and varies by year and region. Kathmandu Valley and non-Valley employees may observe different holidays in some cases. Organizations operating across multiple provinces should review the gazette for regional variations. The Nepal government publishes the holiday list through the Ministry of Home Affairs, and payroll and leave systems should be updated at the start of each fiscal year to reflect the current gazetted holiday list rather than using a fixed prior-year list.
An important distinction in the leave system is between leave that can accumulate and leave that cannot. Home leave accumulates up to the ceiling specified in the Act and can be encashed on resignation. Sick leave does not automatically accumulate year on year in the same way. Maternity and paternity leave are event-specific. Mourning leave is consumed when the event occurs. The leave system must track these different accumulation rules per leave type rather than treating all leave as a single pool.
Each leave type under Labour Act 2074 has different accumulation rules, encashment eligibility, and qualifying conditions. A leave management system must reflect these differences at the leave type configuration level, not apply a single policy to all leave categories.
Leave Request and Approval Workflow
A digital leave request and approval workflow replaces the WhatsApp-and-handshake process with a documented chain. The employee submits a leave request through the system - specifying the leave type, start date, end date, and reason. The system checks their current balance for that leave type and shows whether the requested days are available. If the balance is insufficient, the request is flagged before submission rather than after the manager has already approved it verbally.
The approval chain matters for leave management in the same way it matters for purchase orders and vouchers. A line manager may approve leave for their direct reports, but senior HR staff can override or escalate. Where a senior employee's leave needs HR sign-off before the line manager approval, the workflow should reflect this. The system should support multi-level approvals for specific leave types (maternity leave, for example, typically goes through HR rather than just the line manager) without making all leave applications require the same level of scrutiny.
When a leave request is submitted, the team calendar should update immediately to show the pending request. This allows the manager to see whether other team members are on leave during the same period before approving. Overlapping leave in a small team can create operational problems that are entirely preventable if the calendar is visible at the approval stage. The approval or rejection is recorded with a timestamp and, for rejections, a required reason. The employee receives a notification immediately upon the decision.
The leave approval workflow is a chain of documentation, not just a communication. Every request, approval, and rejection creates a record that resolves future disputes, informs the leave encashment calculation, and provides the audit evidence that Labour Act compliance requires.
Leave Balance Tracking and the Team Calendar
Accurate leave balances are the foundation of a credible leave management system. The balance for each employee must reflect all leave taken during the current fiscal year, all approved-but-not-yet-taken future leave, and the accrued balance from prior periods for accumulating leave types. When an employee asks how many home leave days they have remaining, the system should give an immediate answer that is verifiable from the leave transaction record.
Organizations that do not track leave balances in the same system as payroll face a specific risk at resignation: the leave encashment calculation requires accurate accumulated home leave days, and if those records have been maintained in a spreadsheet that has not been updated consistently, the calculation is contested. Building the leave balance record in the payroll system from the beginning of employment - accruing home leave as each month of service is completed - creates a clean, unambiguous record that makes the resignation settlement straightforward for both parties.
The team leave calendar is the operational planning tool. When a manager can see a colour-coded monthly calendar showing which team members are on leave on which days, they can identify periods of overlap, plan staffing around anticipated leave periods, and make informed decisions about whether to approve additional leave requests. This is particularly important for small teams where one absence significantly changes coverage, and for Nepal's festival period (Dashain and Tihar) when leave requests cluster heavily.
The team leave calendar converts individual leave records into a planning tool for operational management. Managers who can see their team's leave picture for the coming weeks make better staffing and project scheduling decisions than those who find out about coverage gaps after the fact.
Leave Encashment at Year-End and Resignation
Leave encashment requires two clean records: the accumulated home leave balance per employee, and the daily rate applicable to the employee at the time of encashment. Both are available from the payroll system when leave is managed in the same platform. The daily rate is the monthly basic salary divided by the working days per month. The encashment amount is the number of encashable days multiplied by the daily rate.
Some organizations offer within-service leave encashment - allowing employees to encash a portion of accumulated home leave in lieu of taking it, up to a limit. This is an organizational policy that may be offered beyond the statutory minimum. Where this is offered, the leave system must track the encashment against the balance and ensure the remaining balance is accurately maintained for future requests and the final resignation settlement.
The final settlement at resignation combines leave encashment with prorated festival bonus, any outstanding salary for the partial final month, and gratuity calculation. When all of these derive from the same integrated system, the settlement calculation is generated in minutes rather than assembled over several days from separate records. This speed matters: delayed or disputed final settlements create the labour complaints and disputes that Nepali businesses most want to avoid.
Leave encashment accuracy depends entirely on the integrity of the leave balance record. Organizations that maintain accurate leave records throughout the employment period process resignations without dispute. Those with inconsistent records face recalculation, negotiation, and potential Labour Office involvement at every resignation.
Leave requested via WhatsApp with no formal record of approval or rejection
Digital request with leave type, date, and reason - balance checked before submission
Leave balances tracked in a spreadsheet with inconsistent updates from multiple HR staff
Balances auto-updated on every approval - leave taken reduces the balance immediately
Manager approves leave without knowing whether other team members are on leave the same period
Team calendar shows pending and approved leave before manager decides - overlap visible at approval
Sick leave, home leave, and other types confused - balances incorrectly shared between types
Each leave type tracked separately with Labour Act 2074 accumulation rules per type
Leave encashment at resignation requires manual reconstruction of 3 years of leave records
Accumulated balance available instantly from the leave record - encashment calculated in seconds
Frequently Asked Questions
Yes. Leave management systems with mobile support allow employees to submit leave requests, check their current balances by leave type, and receive approval notifications directly on their phone. Managers can approve or reject leave requests from the mobile app as well. This is particularly useful for field staff and organizations where employees do not have regular access to a desktop workstation. The mobile request creates the same system record as a desktop submission - the data and audit trail are identical regardless of the device used.
Opening balances need to be established for each employee at the system start date. For home leave, this means calculating the accumulated leave as of the cutover date based on the employee's service record and the leave they have taken since joining. HR prepares opening balance figures from existing records (however imperfect) and enters them as the starting point in the new system. The system then accrues leave from the cutover date forward and records all requests and approvals from that date. The opening balance is the weakest link but a reasonable approximation is better than nothing, and from the cutover date forward the record is clean.
The Nepal government publishes the gazetted public holiday list each fiscal year (Shrawan 1). The HR administrator updates the system's public holiday calendar at the start of the fiscal year with the new list. This update automatically affects leave balance calculations - working days in any leave period are counted against the leave type balance, and public holidays are excluded from the deduction. If the holiday list is not updated, working days and holiday days get confused, producing incorrect leave deduction calculations for any leave period that spans a gazetted holiday.
Labour Act Leave Types, Mobile Approvals, and Accurate Balances in One System
MISAC's leave management module is pre-configured with the leave types specified under Labour Act 2074 - home leave, sick leave, maternity and paternity leave, mourning leave, and public holidays. Each type has its own accumulation rule, encashment eligibility, and approval workflow configuration. Administrators update the public holiday list at the start of each fiscal year and the calendar applies across all leave calculations automatically. Leave balances per employee per type are always current and available to both HR and the employee.
The mobile app allows employees to submit leave requests and check their balance from their phone without needing to be in the office or contact HR directly. Managers receive a notification and see the team calendar with the request period highlighted before approving. Approvals and rejections sync back to the employee within seconds. The entire request-to-approval chain is documented in the system with timestamps, and the approved leave reduces the employee's balance immediately.
MISAC Intelligence Pvt. Ltd. has set up leave management systems for Nepali organizations from 25-person offices to 500-person manufacturing and hospitality operations. The leave type configuration, approval chain setup, and opening balance migration are all handled during implementation so the first leave request in the system produces a correct balance and a clean audit record. Contact the team at mis.ac to see the leave management module for your organization's structure.
Ready to See MISAC in Action?
Replace WhatsApp leave requests with a structured system that tracks Labour Act leave types, maintains accurate balances, and feeds directly into payroll encashment calculations.