HRMS projects are usually justified on payroll efficiency and judged, months later, on whether staff trust the system. Those are different criteria and the second is harder.
This is a practical account of what works in Indian manufacturing and distribution environments, where the workforce is rarely sitting at desks, the statutory obligations are unforgiving, and a payroll error is not an inconvenience but a notice.
What HR time actually goes on
Measure before designing. In the organisations we work with, the consistent pattern is that HR time concentrates in four places: chasing attendance exceptions and regularisations, assembling payroll from an attendance ledger and a complex Excel workbook, answering individual queries about leave balance and payslips, and preparing statutory filings.
The fourth is unavoidable but automatable. The third disappears almost entirely with self-service. The second is where the largest single saving sits — organisations processing payroll for several hundred employees routinely spend six to eight days a month on it.
The first is the one that requires design rather than automation, because attendance exceptions are usually a symptom of a system that does not match how people actually work.
Attendance for workforces that are not at desks
This is where most HRMS implementations fail first, because the reality is messier than the software assumes. A plant has three rotating shifts with a night allowance and a weekly off that moves. Contract labour comes through a vendor and needs separate tracking for compliance. Field staff cannot punch on a device because there is no device where they are. Some staff work at a client site; some are on tour.
Support the full mix and land it in one ledger: biometric and RFID at fixed locations, geofenced mobile punch with selfie verification for field staff, web punch for office employees, and manual entry with an approval trail for genuine exceptions. The source of each entry must be recorded, because that matters when an entry is later disputed.
Shift handling must be built for rotation from the start: patterns defined once and applied forward, swaps with approval, overtime computed against your actual policy rather than a generic rule, and grace periods that reflect what your HR policy really says rather than what a vendor assumed.
Payroll that is computed, not assembled
Payroll should run from the attendance ledger and the salary structure with no re-keying between them. Structures need to support the components Indian companies actually use — basic, HRA, conveyance, special allowance, shift allowance, production incentive, attendance bonus — and deductions for PF, ESI, professional tax, TDS, loans, advances and recovery.
The statutory outputs should be generated rather than built by hand: PF ECR file, ESI contribution file, professional tax challan data at West Bengal slabs, TDS computation with Form 16, bonus calculation, gratuity provisioning and leave encashment. Registers required under the state Shops and Establishments Act and the Factories Act produced on demand rather than maintained separately.
And the run itself should be a controlled process: freeze attendance, compute, review an exception report, approve, then generate payslips and the bank file. Every run versioned, so an arrear or correction in a later month traces cleanly to what changed.
| Statutory item | Handled by |
|---|---|
| Provident Fund | Computed on correct wage base with ceiling handling; ECR file generated |
| ESI | Applicability by threshold, contribution file, mid-year crossing rules |
| Professional Tax | West Bengal slabs applied automatically; monthly challan data |
| TDS | Declarations, proof workflow, quarterly computation, Form 16 |
| Bonus and gratuity | Provisioning and computation under the applicable Acts |
| Contract labour | Vendor-wise tracking, licence validity, minimum wage compliance |
The productivity question, answered honestly
Management usually wants to know whether the workforce is productive, and the instinct is to reach for monitoring — continuous location tracking, keystroke logging, screenshot capture. We generally decline to build these, and we say why once rather than repeatedly.
They damage trust more than they recover productivity, and the damage is not confined to the monitoring. A workforce that believes it is being surveilled becomes less forthcoming about problems, which is expensive in a plant environment where early reporting of an anomaly is worth a great deal.
The same management questions are answerable from outcome data, and better. Visits completed against plan for field staff. Jobs closed per shift for service teams. Output per person-hour for production. Task completion for project teams. These connect to something the business actually cares about — a dashboard showing average keyboard activity tells you nothing actionable, while one showing a territory at 62% of its visit plan while another is at 104% starts a useful conversation.
What we will and will not build
We build attendance, visit check-in, task tracking and outcome measurement. We generally decline continuous location tracking and keystroke or screenshot surveillance. If you want it anyway, we say this once and then discuss what is proportionate — but we would rather have made the argument.
The employee experience decides adoption
An HRMS is used by everyone in the company, and most of them are not in HR. If applying for leave requires an email and a follow-up, if the payslip arrives as an attachment somebody has to request, if nobody can see their leave balance without asking — then the system exists for HR's convenience and everyone else experiences it as friction.
Build the employee app as a first-class surface: payslips available immediately with a year of history, leave balance and application with the approval chain visible, attendance regularisation requests, tax declaration and proof upload, reimbursement claims with photographed bills, and a directory. Notifications on WhatsApp, because that is what people actually read.
And design for the actual workforce. Bengali and Hindi alongside English. Works on a low-end Android device. Kiosk mode on a shared tablet for staff without smartphones. Printed payslips where required. Assuming universal smartphone access is still wrong in many manufacturing environments.
Rolling it out without a payroll disaster
Parallel run, without exception. Process two to three months alongside your existing method and reconcile every employee to the rupee, investigating every difference — which frequently uncovers errors in the old process rather than the new one. Only after consecutive clean months do you switch over.
This is the single practice that makes payroll go-lives uneventful, and skipping it is the single most common cause of the ones that are not. A payroll error affects every employee simultaneously and destroys confidence in a way that takes a year to rebuild.
Sequence the rest around it: attendance and leave first, since they feed payroll and their errors surface quickly; payroll after; self-service launched with the payroll go-live so employees experience a benefit at the same moment they experience a change.
Key takeaways
- Measure where HR time actually goes before designing — it concentrates in four predictable places.
- Support the full attendance mix in one ledger, with the source of every entry recorded.
- Generate statutory outputs rather than assembling them; West Bengal rules differ and must be tested.
- Prefer outcome measures over surveillance — they answer the same questions without costing trust.
- Parallel-run payroll for two to three months and reconcile to the rupee before switching.
Frequently asked
For a straightforward office workforce we often recommend exactly that. Custom becomes justified with complex shift patterns, contract labour compliance, plant-specific allowances and incentives, multi-entity payroll, or per-employee licence costs at scale. Several clients tried a product first and moved because their shift and incentive logic could not be expressed in it.
Yes, and for factories this is often the compliance risk that matters most. Contract workers tracked by vendor with licence validity, wage compliance against minimum wages, attendance, and the registers required under the Contract Labour Act. Vendor bills verified against attendance rather than accepted on trust, which frequently pays for the module by itself.
In almost all cases. We work regularly with ESSL, ZKTeco and Matrix and can read from most others through their SDK, a database poll or a scheduled export. If a device is genuinely closed we say so before the project starts rather than discovering it mid-build.
In your cloud account in an Indian region by default, or on-premise if policy requires. Field-level access control so managers see attendance without compensation, all access logged, documents encrypted at rest, and retention configured to your data protection obligations.