From muster to wages, posted to the books.
Build a payroll run for any period from attendance and wage settings, adjust deductions, then finalize — each payslip posts as a labour-expense ledger row, fully reversible.
Everything the labour payroll module ships with.
Daily & monthly wages
Daily-wage labour is paid per attendance-day; monthly staff draw a fixed salary — both in one run.
Overtime & deductions
Overtime pay is computed from logged OT hours; per-person deductions are editable while the run is a draft.
Finalize → ledger
Finalizing posts one labour-expense ledger entry per person, attributed to the employee and paid from cash or bank.
Reversible runs
Void a finalized run and the ledger postings reverse — your books never drift.
Paise-accurate
All wage math runs on the same decimal-safe engine as the ledger, so totals reconcile exactly.
Period-based
Run weekly or monthly; payable days come straight from the attendance muster.
What this looks like on a real site.
Wage day takes an afternoon and a calculator
Build the run for the period and the numbers are already there — payable days from the attendance muster, rates from each person's wage settings, overtime from logged hours. What used to be an afternoon of counting register entries becomes a review: check the draft, adjust the deductions that need adjusting, finalise. The arithmetic is not the part you spend time on.
Labour cost never makes it into the books
Finalising posts one labour-expense ledger entry per person, attributed to the employee and paid from cash or bank. Wages are usually the largest cost on a site and the one most often reconstructed from memory at year end. Here it lands in the ledger as it happens, which is what makes per-site profit and loss believable.
You finalise a run and then find a mistake
Void it. The ledger postings reverse together with the run rather than leaving you to unpick a dozen manual counter-entries, so the books never drift out of agreement with what you actually paid. Runs are period-based, so a firm paying labour weekly and staff monthly can operate both cadences side by side.
Labour Payroll, answered.
Does this handle daily-wage labour and monthly staff together?
Yes, in the same run. Daily-wage workers are paid per attendance day; monthly-salary staff draw a fixed amount. Most construction firms have both, and running two parallel systems for them is exactly how the two sets of numbers stop matching.
How is overtime calculated?
From the overtime hours logged against each person in the attendance muster, at that employee's configured overtime rate. Nobody re-enters hours into payroll, which removes the most common source of wage disputes — the office's figure and the site's figure being different.
Can I adjust an individual before paying?
Yes. While the run is a draft, per-person deductions are editable — advances taken, material damaged, whatever your arrangement is. Once you finalise, the run posts to the ledger and becomes a record rather than a working document, though it can still be voided in full.
Are the totals exact?
Wage maths runs on the same decimal-safe engine as the ledger, so payroll totals and ledger totals reconcile exactly rather than differing by a few rupees for reasons nobody can trace. Over a year of weekly runs across dozens of workers, that difference is what keeps the books clean.