HR systems that respect both compliance and the people in them

Attendance 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.

We support the full mix: biometric and RFID devices 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. All of it lands in one attendance ledger with a clear record of the source, which matters when an entry is later disputed.

Shift and roster handling is built for rotation: patterns defined once and applied forward, shift swaps with approval, overtime computed against your actual policy rather than a generic rule, and late or early marking with grace periods that reflect what your HR policy really says.

Payroll runs from the attendance ledger and the salary structure, with no re-keying between them. Structures 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 salary recovery.

The statutory outputs are generated, not built by hand: PF ECR file, ESI contribution file, professional tax challan data, TDS computation with Form 16 generation, bonus calculation, gratuity provisioning and leave encashment. Registers required under the West Bengal Shops and Establishments Act and the Factories Act are produced on demand rather than maintained separately.

A payroll run is a controlled process: freeze attendance, run computation, review an exception report, approve, then generate payslips and the bank transfer file. Every run is versioned, so an arrear or correction in a later month traces cleanly to what changed.

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.

We build the employee app as a first-class surface: payslips available immediately with a year's 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 company directory. Notifications go out on the channel people actually read, which in most Indian workplaces is WhatsApp.

This matters commercially as well as culturally. Every one of those self-service functions removes a stream of interruptions from an HR team that has better things to do than answer leave-balance questions on the phone.

Beyond payroll, the parts of HR that consume the most time are hiring and onboarding. We build applicant tracking with a job portal, structured interview stages, feedback capture and offer generation, followed by an onboarding checklist that spans HR, IT and the reporting manager so nothing is forgotten on day one.

Document management holds contracts, ID proofs, qualification certificates and statutory forms with expiry tracking — genuinely important where safety certifications or licences must be current. Confirmation, appraisal and exit processes carry the same structured treatment, including full and final settlement computed from the same ledger as regular payroll.

Management usually wants to know whether the workforce is productive, and the instinct is to reach for monitoring tools. We prefer outcome and activity measures that are visible, explainable and not resented: visits completed against plan for field staff, jobs closed per shift for service teams, output per person-hour for production, and task completion for project teams.

These are more useful anyway, because they connect to something the business cares about. A dashboard showing average keyboard activity tells you nothing actionable; one showing that a territory is at 62% of its visit plan while another is at 104% starts a useful conversation.

Payroll data is among the most sensitive a company holds. We build with field-level access control so a departmental manager sees attendance but not salary, encryption at rest, full audit logging of who viewed what, and deployment either in your cloud account or on-premise where policy requires it.

The system is built to handle scale properly — we have run payroll for organisations above ten thousand employees, and the design that matters is doing computation as a background job with a clear progress and exception view, rather than a web request that times out on the fourth attempt.