How Sidheshwarr RMC Runs Attendance and Payroll for 300 People Across Three Plants and a Head Office

Sidheshwarr RMC is a ready-mix concrete business with 300 people spread across three plants and a head office. Every one of them is on Mera Attendance, and every month that same attendance feeds payroll. This is how a setup like that works, and what it replaces.

The setup at a glance

• 300 employees across three plants and one head office
• Attendance captured in Mera Attendance, one record per person
• Payroll run from that same attendance, with no file passed between systems
• One system for all four locations, instead of one register or spreadsheet per site

Why plants and a head office are hard to run on one register

A plant and a head office keep different rhythms. Plant teams work in shifts and often start before office hours. Head-office staff keep desk hours. Run attendance on paper registers or separate spreadsheets per location and HR ends up collecting four sets of numbers, reconciling them, then re-typing the result into payroll. That is where errors creep in, and where the month-end arguments start.

Multiply that by 300 people and the reconciliation becomes a job in itself. The goal is not a faster punch. It is one fewer reconciliation.

One system, four locations

Each plant and the head office is set up as its own branch. A plant manager sees the attendance for their plant and nothing else. Head-office HR and the owner see all four locations side by side. Branch-wise management is built into the core of MeraUdyog, so this is a setup choice, not a customisation project.

How people check in

Mera Attendance gives you several ways to record presence, and each location can use the mix that suits it:

• GPS and selfie check-in on the phone, so every punch carries a photo and a location
• Geo-fencing, so check-in only opens inside the radius you draw around a plant gate or the office
• Biometric check-in for fixed points such as a gate
• Web check-in for desk-based staff

A plant and a head office do not need the same method, and Mera Attendance does not force one. Staff who work away from a fixed point can still check in from the phone, and the punch is saved offline if the signal drops, then synced when it returns.

From attendance to payroll

Attendance feeds the payroll run on the same data core. Late marks and absences adjust pay without anyone uploading a file, and every deduction carries its reason, so an employee who asks why their pay changed gets a clear answer. Missed punches go through a regularisation request and approval, which keeps corrections on record instead of in a phone call.

What it replaces

• A register or spreadsheet per location
• “Present” messages in a WhatsApp group
• The month-end job of reconciling four sets of attendance
• Re-typing attendance into a payroll sheet

If you run something similar

1. List every plant, branch and office as its own location.
2. Choose a check-in method per location. Gates and fixed points can differ from desk teams.
3. Define the shifts each location actually runs.
4. Decide who approves regularisation requests at each site.
5. Run your first payroll alongside the old process once, then switch.

If you operate plants, depots or branches with a few hundred people, see Mera Attendance or book a walkthrough built around your own shifts and sites.