HR & Payroll Software for Nepal's Manufacturing & Construction
Rotating shift rosters, overtime priced at the Labour Act 2074 rate, gate biometrics that keep working when the plant link drops, and PF/CIT/SSF/eTDS payroll that pays only the hours a supervisor approved.
One System for the Plant, the Site and the Head Office
Production runs on shifts and the office runs on a calendar. NepalHRM holds both under one payroll instead of reconciling two systems every month.
Where Factory Payroll Actually Breaks
Not in the salary formula. In the four places between the gate reader and the salary sheet where a manufacturing month is different from an office month.
Labour Act 2074 section 32 sets overtime at no less than 1.5 times the hourly rate, with a statutory ceiling of 4 hours a day and 24 hours a week. A spreadsheet that pays a flat figure is the finding a labour inspection writes up.
A 22:00 to 06:00 shift belongs to the day it started, not the day it ended. Get that wrong and every night worker looks absent on one date and doubled on the next.
Fixed-term hires, site labour and consultancy contracts each carry their own end date. When nobody sweeps those dates, headcount reports quietly count people who left.
Punches happen at a factory gate where the link drops. Attendance that depends on a live connection to the cloud loses exactly the shift you needed for payroll.
From the Gate Punch to the Salary Sheet
Every step a manufacturing month runs through, in one platform: roster, punch, overtime approval, per-day allowances, statutory deductions.
Shift templates with a night flag
Name a shift once (start, end, grace minutes, paid and unpaid breaks) and flag it as a night shift so a midnight-crossing roster stays grouped under the day it began.
Rotating rosters, daily to monthly
Assign a shift to one person or in bulk with a start and end date, and rotate it daily, weekly or monthly. The weekly grid stays a Draft until you click Publish week.
Overtime at the statutory multiplier
Five rate tiers ship with the account: Regular at 1.5x, Weekend at 2.0x, Holiday at 2.5x, Night at 1.75x and Emergency at 2.0x. The payslip figure is hours times hourly rate times the tier.
Only approved overtime is paid
Overtime raised from punches sits pending until it clears the employee, team leader and HR chain. The salary sheet reads approved rows only, so nobody pays a claim twice.
Gate biometrics through an edge agent
ZKTeco and Hikvision readers report to an edge agent on the plant LAN, which posts signed batches of punches upstream. The agent keeps collecting while the link is down.
Import the reader you already own
For a device NepalHRM does not talk to directly, save its monthly export as an import profile once (header row, Time In column, BS or AD dates) and reuse it every month.
Contract labour with an expiry sweep
Permanent, fixed-term, probation, internship, consultancy and part-time contracts, each with its scans attached. A daily job flips any contract past its end date to Expired.
Khaja and canteen priced per day
A salary component can be a per-day rate rather than a monthly figure, so a tiffin or field allowance pays for the days actually worked and a canteen deduction runs the same way.
Nepal payroll on the plant's numbers
Approved attendance sets payable days, approved overtime adds its line, then PF, CIT, SSF and eTDS calculate on the total against current IRD slabs.
The hours are counted by the reader, and priced by the tier.
Overtime reaches payroll one of two ways. An employee raises it, or NepalHRM raises it from the day's punches once worked minutes cross the attendance policy threshold. Either way the claim carries a rate tier and stays pending until the team leader and HR clear it. Section 32 of the Labour Act 2074 fixes the floor at 1.5 times the hourly rate and the ceilings at 4 hours a day and 24 hours a week. NepalHRM prices what you approve at the tier you chose; the daily and weekly ceilings remain a supervisor decision, not a lock the software applies for you.
- Regular OT · 1.5x hourly rate
- Weekend OT-W · 2.0x
- Holiday OT-H · 2.5x
- Night OT-N · 1.75x
- Emergency OT-E · 2.0x
Tier names and multipliers are the defaults every account starts with. Rename them, change a multiplier or add your own.
The three modules a plant switches on first
Roster and overtime before anything else, because that is where the month is won or lost. Payroll reads both.
Shift templates, rotating rosters, the weekly publish step and the overtime approval chain.
Biometric devices, edge agents, the raw punch log, attendance policies and regularisation.
Payable days from attendance, per-day components, PF, CIT, SSF and eTDS on IRD slabs.
Questions from Plant HR and Production Managers
Overtime is priced through rate tiers. Every account starts with five: Regular at 1.5x, Weekend at 2.0x, Holiday at 2.5x, Night at 1.75x and Emergency at 2.0x, and the payslip amount is hours times the employee's hourly rate times that multiplier. Section 32 of the Labour Act 2074 sets the 1.5x floor and the 4 hour daily and 24 hour weekly ceilings. NepalHRM prices the hours you approve; the ceilings stay a policy your supervisors enforce.
Yes. Build each shift once with its start, end, grace minutes and breaks, and mark the overnight one as a night shift so a 22:00 to 06:00 roster is counted under the day it started. Assign shifts individually or in bulk with a date range and a daily, weekly or monthly rotation. The weekly schedule stays in Draft until you publish the week, so a half-built roster is never visible to the floor.
Yes. ZKTeco and Hikvision readers are added by vendor, model, IP, port and serial, and an edge agent installed on that plant network collects their punches and posts them upstream in signed batches. The agent keeps reading the device while the connection is down and sends the backlog when it returns, so a dropped line delays attendance rather than losing it.
Import its own monthly export instead. You map that file once (which row is the header, which column is Time In, whether the date column is Bikram Sambat or AD) and save the mapping as an import profile. Every following month the same file imports without remapping, which is usually faster than replacing hardware that already works.
Yes. Contracts are typed as permanent, fixed-term, probation, internship, consultancy or part-time, and every type except permanent requires an end date. Signed scans, the offer letter and the NDA attach to the contract record. A daily job moves any contract past its end date to Expired, so a headcount report never counts a term that finished last month.
As per-day salary components. Instead of a fixed monthly figure, the component holds a rate per day and the payslip multiplies it by the days the employee actually earned it, with the earning rule set per component. A canteen deduction is built the same way. Both then sit inside the normal PF, SSF, CIT and TDS calculation rather than beside it.
Yes, and only approved overtime does. A claim raised by an employee, or raised from attendance when worked minutes cross the policy threshold, stays pending until it clears the team leader and HR. The salary calculation for the period reads approved rows only. Unapproved hours are visible in reports and are not paid.
Bring the Roster, the Gate and Payroll Into One Month-End
Show us one shift pattern and one month of overtime. We will build the roster, price the hours at your tiers and run the salary sheet against them in the demo.
- Rotating shift rosters
- Labour Act 2074 overtime rates
- Offline-tolerant gate punches
- Free onboarding