Leave Management in Nepal and the Labor Act 2074

Leave is one of those things that seems simple until you're the one tracking it. How many days does each employee have left? Did that sick leave get approved? Is this person's home leave balance carrying over or expiring? When it's all in someone's head or a spreadsheet, the answers get fuzzy — and fuzzy leave records turn into disputes at exactly the wrong moments.

Underneath the practical mess there's a legal layer. Nepal's Labor Act 2074 (2017) sets out leave entitlements that employers are required to provide. Getting leave management right means getting both the tracking and the compliance right. Here's a plain overview of both.

A note before the details: this is a general explanation, not legal advice. Labor rules get amended and interpreted, and specifics can vary by employment type and sector. For decisions with legal or financial consequence, confirm the current provisions with a qualified HR or legal professional.

The main leave types under the Labor Act

The Labor Act 2074 recognizes several categories of leave. The ones that matter most for day-to-day HR:

Annual leave (home leave). Employees accrue annual leave based on days worked — broadly, one day of home leave for a set number of days worked. This leave generally accumulates and can be carried forward up to a cap, which makes accurate running balances important; you can't reconstruct a year of accrual from memory.

Sick leave. Employees are entitled to a number of paid sick days per year. Unused sick leave and its carry-forward treatment differ from annual leave, which is one reason lumping all leave into a single "leave balance" causes problems.

Maternity leave. Female employees are entitled to a substantial period of maternity leave with pay, as provided under the Act. This is a legal entitlement, not a discretionary benefit.

Paternity leave. The Act also provides for paternity leave — a defined number of days for male employees — which many businesses still track informally and inconsistently.

Public holidays. Separate from personal leave, employees are entitled to public holidays, including the major festivals. Female employees are additionally entitled to certain days such as those connected to specific festivals. These need to be reflected in the working calendar so they aren't counted as absence or deducted from personal leave.

Why spreadsheets fail at this

The problem with tracking leave manually isn't that it's impossible — it's that it requires perfect, continuous discipline, and one missed update corrupts the record going forward.

Each leave type accrues differently and carries forward differently. Balances change every time someone takes leave or accrues more. A request has to be checked against the available balance for that specific leave type. With ten employees this is tedious; with fifty it's a part-time job; and at any size, the spreadsheet is only as accurate as the last person who remembered to update it.

The failures show up at the worst times. An employee is told they have no annual leave left when they actually had five days. A maternity leave entitlement is miscalculated. Two managers approve overlapping leave because neither could see the other's decision. These aren't hypothetical — they're the normal result of running statutory entitlements on a shared spreadsheet.

The fiscal-year timing problem

Here's a detail that trips up software not built for Nepal: leave accrual and annual reset are tied to the Nepali fiscal year, which begins on Shrawan 1 — not January 1.

If your system resets annual leave balances on the AD new year, every balance is wrong relative to how your business and your accountant actually account for the year. Leave management has to operate on the BS fiscal calendar to line up with everything else — payroll cycles, SSF, holiday lists. A leave system that resets at the wrong point in the year creates a discrepancy you'll be reconciling indefinitely.

What good leave management actually does

A proper leave system removes the manual tracking and the disputes that come with it. The pieces that matter:

Separate balances per leave type. Annual, sick, maternity, paternity — each tracked on its own with its own accrual and carry-forward rule, not merged into one number.

Request and approval in one place. An employee requests leave, the manager sees the request along with the current balance, and approves or declines. The balance updates automatically. No separate spreadsheet to remember to edit, no approval lost in an email thread.

Automatic balance calculation. The system accrues leave as the employee works and deducts it as leave is taken, so the balance is always current and always correct. Anyone can check it in a second.

BS fiscal-year alignment. Accruals and resets follow the Nepali fiscal year, so leave records line up with payroll and compliance.

A record you can stand behind. When a question comes up about how much leave someone took or had, there's a clear, dated history — not a debate about who remembers what.

The compliance angle

Beyond convenience, accurate leave records are a compliance matter. The Labor Act sets minimum entitlements, and an employer needs to be able to demonstrate that employees received what they were due. In a dispute — or an inspection — a clear leave record is the difference between a quick answer and a problem.

Maternity leave is the case where this matters most. It's a significant statutory entitlement, and mishandling it carries both legal and reputational cost. A system that tracks it correctly, against the right entitlement and the right calendar, protects both the employee and the business.

Leave management isn't the most exciting part of running a business, but it's one where getting it wrong is expensive and getting it right is mostly a matter of using a system designed for the job — one that knows Nepal's leave types, the Labor Act's entitlements, and the BS fiscal year they all run on.