Payroll that reads attendance instead of arguing with it.
Attendance, shifts and overtime feeding a salary structure built the way structures are actually built here.
Factory payroll is not office payroll. There are shifts, there is overtime, there are people paid on attendance rather than on a flat month, and there is a salary structure made of components — basic, HRA, conveyance, allowances — each with its own rule. Software that models a salary as one number cannot produce a correct payslip from any of that.
What usually happens instead is two systems that do not speak. Attendance lives in a biometric machine or a register; payroll lives in a spreadsheet. Once a month somebody reconciles them, and the reconciliation is where the errors are introduced — a shift counted wrong, overtime at the wrong rate, a half-day that became a full one.
HR and payroll software for manufacturing has to start from attendance rather than from a monthly figure. Keeping the two in the same system removes the reconciliation entirely. Days present, shifts worked and overtime hours are what the calculation reads. The structure does the rest, component by component, and the payslip is a result rather than an entry.
What you get
Attendance and shifts
Days, shifts and overtime recorded against the employee, in the shape a factory actually works rather than a nine-to-five assumption.
Component salary structures
Basic, HRA, conveyance and allowances defined as parts with their own rules, not a single gross figure split by hand.
Overtime that calculates
Extra hours priced by the rule that applies to them, so overtime is a computed line rather than a monthly negotiation.
Employee master
One record per person — joining date, department, designation, structure — that everything else references.
Payslips from the data
Generated from attendance and structure together, so what is paid and what was worked cannot drift apart.
Department-wise cost
Labour cost readable by department, which is the number that makes a costing exercise honest.
Why the structure matters more than the total
A salary in India is rarely one number, and the components are not cosmetic — they carry different treatment, and the split affects what the employee actually receives. Building the structure as components means a revision changes a rule rather than requiring every affected payslip to be recalculated by hand.
It also makes an increment straightforward. Raising basic by a percentage recalculates everything that derives from it, rather than becoming an exercise in adjusting five figures until the total matches what was promised.
The reconciliation that should not exist
Wherever attendance and payroll are separate systems, somebody spends the first days of the month moving numbers between them. It is tedious, it is done under time pressure, and it is where nearly every payroll error originates — not in the calculation, but in the transfer into it.
When payroll reads attendance directly there is nothing to transfer. The month closes and the figures are already there, which also means a query from an employee is answerable from the record rather than from whoever did the reconciliation.
Labour cost where costing needs it
Job costing that counts material and ignores labour produces a number that is reassuring and wrong. Having attendance in the same system makes departmental labour cost available to the costing exercise, which is what turns 'this order was profitable' from an assumption into a calculation.
Questions people ask.
Does it handle shift and overtime calculation?
Yes. Shifts and overtime hours are recorded against the employee and priced by the rule that applies, so overtime is calculated rather than agreed each month.
Can salary be defined as basic, HRA and allowances?
Yes. The structure is built from components with their own rules rather than as a single gross figure, which is what makes an increment a rule change instead of five manual adjustments.
Does payroll read attendance automatically?
Yes, and that is the point. Days present, shifts and overtime feed the calculation directly, so there is no monthly reconciliation between two systems to get wrong.
Can we see labour cost by department?
Yes. Because attendance sits in the same system as production, departmental labour cost is available to costing rather than being estimated.
Is this separate from the rest of the ERP?
It is a module of the same system, reading the same database. That is what allows attendance to reach payroll and labour cost to reach job costing without an export in between.
Related parts of the system
Tell us what you make.
The useful version of a demo uses your own item list and last month's orders, not ours.
Get in touch