Why We Built Hajir Khata Around Nepal's Fiscal Year, Not a Generic Calendar

Short answer: Nepal's fiscal year runs from Shrawan to Ashad (mid-July to mid-July), not January to December — payroll and tax reporting built around a generic calendar year requires manual workarounds every year, while software built around the actual Nepali fiscal year doesn't.

Why the fiscal year matters for payroll specifically

Tax slabs, annual leave cycles, and statutory reporting in Nepal are typically structured around the Shrawan-to-Ashad fiscal year. Payroll software built on a generic Gregorian January-to-December year forces HR teams to manually adjust reports and calculations to match the actual fiscal calendar every year — a workaround that's easy to get wrong, especially around the fiscal year-end.

What breaks with a generic calendar

• Annual leave accrual resets on the wrong date, creating mismatched balances
• Tax slab calculations don't align cleanly with the actual reporting period
• Year-end reports need manual date-range adjustment instead of running natively

Why this is a foundational design choice, not a setting

Retrofitting fiscal-year logic onto software originally built around a calendar year usually means it's implemented as an afterthought — a date filter bolted on top, rather than the actual basis for how leave, tax, and reporting periods are calculated. Software designed around the Nepali fiscal year from the start avoids that entire category of edge cases.

The practical takeaway

When evaluating HR or payroll software in Nepal, it's worth directly asking whether fiscal-year reporting is a native feature or a manual workaround — the answer tends to reveal how much of the product was actually built for Nepal, versus adapted to it after the fact.