Software
Attendance management systems for Nepali workplaces
Attendance data that does not reach payroll is just a log. What makes it valuable is the connection to pay.
Updated August 2026
Attendance is usually the first HR process a Nepali organisation automates, often with a biometric device at the entrance. The device solves capture. It does not solve the harder problem, which is what the data means for pay.
Capture methods and where each fits
| Method | Suits | Watch for |
|---|---|---|
| Biometric device | Fixed offices and factory floors | Device-to-system sync reliability and power interruptions |
| Mobile check-in | Field staff, sales, multi-site work | Location handling and connectivity in remote areas |
| Web check-in | Office and hybrid staff | Needs a clear policy on what counts as present |
| Manual entry | Exceptions and corrections | Must be logged as an override with a reason |
Registers on the Nepali calendar
Attendance is inherently a per-day record aggregated into a month, which makes the calendar unavoidable. Bikram Sambat months vary between roughly 29 and 32 days, so a system assuming a fixed 30-day month will misstate per-day figures.
The register employees and inspectors recognise is a Nepali-calendar one. Producing it should not require exporting to a spreadsheet and converting dates.
The connection to payroll
Attendance affects pay in two directions: unpaid absence reduces gross salary, and overtime increases it. Both change gross, which changes the annual tax projection.
A system that cannot distinguish approved paid leave from unapproved absence forces payroll into a manual judgement every month. That is where attendance automation stops saving time.
- Approved leave and unapproved absence distinguished automatically from leave records.
- Overtime captured against the rule that applies to the employee’s grade.
- Half-days, late arrival and short hours handled by policy rather than by exception.
- Corrections logged as overrides with an author and a reason.
Evaluating a system
- 1Confirm registers can be produced on the Bikram Sambat calendar with true month lengths.
- 2Confirm the shift and public holiday calendar is Nepali.
- 3Confirm attendance feeds payroll directly rather than through a manual export.
- 4Confirm leave approvals suppress absence deductions automatically.
- 5Confirm manual corrections are logged and reportable.
- 6Test with a month of your own data, including an employee who took unpaid leave.
Overtime, and why it is the hardest part
Overtime is where attendance stops being a record and becomes a payment. It is computed from hours captured by the device, priced by a rule that depends on the employee’s grade, and paid through payroll — so an error propagates from the turnstile to the payslip without anyone reviewing it.
The controls worth insisting on are approval before payment and a visible working. Overtime that is calculated and paid without an approval step gives you no opportunity to catch a device fault, and overtime paid without a stored working cannot be explained to the employee who queries it.
- Overtime accrues only from approved hours, not from every minute past the shift end.
- The rate rule is configured per grade rather than applied uniformly.
- The hours, the rate applied and the resulting amount are all visible on the payslip.
- A device outage produces a flagged gap rather than a silent zero.
Frequently asked questions
Does an attendance system need to support the Nepali calendar?
Yes, if it produces registers or feeds payroll. Bikram Sambat months vary in length, so anything computed per day against a fixed 30-day assumption will be wrong for most months of the year.
What is the point of connecting attendance to payroll?
Unpaid absence reduces gross pay and overtime increases it, and both change the annual tax projection. Without the connection, someone reconciles attendance against payroll manually every month.