Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
Plants, production units and processing facilities
Rotating shifts, night differentials, overtime, comp-off, contract labour and an ESI population that changes as wages move, a manufacturing payroll is an exceptions engine wearing a payroll's clothes.
In an office, attendance is close to binary: someone was in, or they were not. On a production floor almost nothing is binary. A punch at 22:40 belongs to a shift that started yesterday. A Sunday worked generates a comp-off with its own expiry. An hour past shift end may be overtime or may be a handover, depending on the rule.
Because the wage base moves with overtime and allowances, ESI applicability moves too, and it does not move on the neat monthly boundary an untrained system assumes. The result in most plants is a payroll input that is assembled by hand every month by someone who knows the exceptions, which makes the whole operation dependent on that person's memory.
Another site or branch opens, and attendance and rostering get harder with it.
The overtime bill jumps without anyone having approved the extra hours.
A wage dispute turns on attendance records nobody can fully stand behind.
A seasonal hiring surge doubles the headcount that has to be onboarded and paid.
Not a feature gap, the specific operational pressures this kind of company runs into, and why each one resists a spreadsheet.
Nobody is going to record which shift a punch belongs to. Auto shift detection from the punch timestamp, including across midnight, is the difference between a system that works on a plant and one that works in a demo.
These are contested figures. Calculating them from the shift definition and the employee's eligibility on the record, rather than from a supervisor's tally, is what makes them easy to defend.
The ₹21,000 gross threshold interacts with overtime and allowances, and contribution-period rules mean an employee does not simply drop out the month they cross it. Evaluating applicability monthly against the actual structure avoids both over- and under-deduction.
Different sites often carry different shift patterns, grace periods and weekly offs for entirely legitimate reasons. Configuring these per location, while filing as one organisation, is the requirement.
Half-yearly and annual LWF deductions land on state-specific dates that have nothing to do with the payroll cycle. Applying them inside the run rather than remembering them separately is the only reliable approach.
You do not have to switch everything on at once, and for a company like yours there is a sensible order. This is it, with the reasoning attached.
A manufacturing company generally pays two populations under different logic. Staff are salaried monthly, largely present during fixed hours, and their pay barely varies. Workmen are on shifts, their pay moves with attendance and overtime, and a substantial share of the monthly cost is decided by what happened on the shop floor that month.
The temptation is to run them as two systems, and it is usually a mistake. The statutory obligations are shared, the same PF and ESI registrations, the same returns, the same wage registers, and separating the populations means reconciling them again before every filing.
What actually differs is the rules, not the machinery: different shift patterns, different overtime treatment, different attendance capture. Holding those as configuration against one payroll run is what keeps the statutory output whole.
Continuous operations bring three problems that office attendance systems never encounter. Shifts rotate, so an individual's expected hours change week to week and the roster is the only thing that knows. Shifts cross midnight, and a system that splits them at the date boundary produces two short days and an overtime figure that is simply wrong.
And weekly offs move with the rotation rather than falling on Sunday, which changes the rate at which a day's work is compensated, a day worked on a rotated weekly off is not the same as a day worked on an ordinary weekday.
The design answer is to treat the shift rather than the calendar day as the unit of attendance, attribute it to the day it began, and hold the rotation as a pattern the roster generates rather than a spreadsheet somebody retypes each week.
The record-keeping obligations on a factory or covered establishment are specific and long-standing: registers of wages, attendance, overtime and leave, maintained in prescribed form and produced on demand.
An inspection does not usually test the total. It tests a particular person on a particular date, why was this worker marked absent, what overtime was paid for this shift, when was this leave approved and by whom. Answering that requires the original capture, any correction, the reason and the approver, all still retrievable.
This is the practical reason an attendance ledger should never be editable in place. A record that can be changed to match the answer currently needed is not evidence, and on the shop floor it is exactly the record most likely to be questioned.
The biometric hardware most plants already run, eSSL, Matrix, Realtime, ZKTeco, pushes into HRMagix over a secure API or a local sync service, so the capture layer does not need replacing. What changes is what happens to the punches after they arrive.
Yes. The shift engine supports 24/7 rotating multi-shift schedules with auto shift detection based on punch timestamps, configurable grace periods, night-shift differential allowances and automatic compensatory-off credit on approved weekend or holiday work.
From the shift definition and the employee's overtime eligibility on their record, against the attendance ledger, then carried directly into the payroll run rather than entered again.
They can have them. Shift patterns, grace periods, weekly offs, holiday calendars and leave schemes are configured per location, while the organisation continues to report and file as one.
The shift is treated as a single unit attributed to the day it began, rather than split at the date boundary. Splitting it produces two short days and an incorrect overtime calculation, and it is the most common cause of an attendance report disagreeing with a payroll run.
Yes, and they should be. Shift patterns, overtime treatment and attendance capture differ by population; the PF and ESI registrations, the returns and the wage registers do not. Keeping both in one run is what stops the statutory output needing reconciliation before every filing.
By rate, according to the rule configured for that day type. A day worked on a rotated weekly off is not compensated as an ordinary weekday, and where the employer grants compensatory time off instead, the same hours become a comp-off entitlement with an expiry rather than a payment.
Yes. A shared kiosk at the gate handles a shift changeover far faster than individual devices, and biometric readers remain appropriate where a controlled entry point already exists. Capture method is a property of the location, and all methods write to the same attendance ledger.
The ₹21,000 gross threshold interacts with overtime and allowances, and contribution-period rules mean an employee does not simply drop out the month they cross it. Applicability is evaluated monthly against the actual salary structure, avoiding both over- and under-deduction.
Looking for a custom walkthrough or have specific statutory policy requirements? Connect with our product specialists in Pune for a 1-on-1 consultation.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime