Payroll for a 3-shift plant: where the errors actually come from

Where payroll errors get in

Punch1Missed or double punches

Roster2Shift swaps not recorded

Attendance3Night shift on the wrong day

OT & allowances4Worked out in Excel

Payroll run5Paid on the contractor’s headcount

Payslip✕ Wrong pay, disputes, audit risk

When payroll goes wrong in a plant, the payroll team usually takes the blame. But the salary formula is rarely the problem. By the time the payroll run starts, most errors are already in the data: a missed punch, a shift swap nobody recorded, overtime added up in a spreadsheet.

Offices with one general shift can get away with that. A plant running three shifts, seven days a week, with a few hundred contract workers on top, cannot. Every one of those small gaps becomes a wrong payslip, a dispute at the HR window, or a finding in the next audit.

The five places errors get in

Follow a worker’s day from the biometric device to the payslip and the same five weak points show up in almost every plant:

1. Missed or double punches. A device was offline, a worker came in through another gate, or someone punched twice. Without a same-day exception, these surface at month-end, when nobody remembers what happened.
2. Shift swaps that never reach the system. Supervisors swap people between shifts all the time, usually by word of mouth. The system still pays the rostered shift.
3. Night shifts booked to the wrong day. A shift that starts at 22:00 and ends at 06:00 spans two calendar dates. Systems that think in calendar days split it, or count the morning punch-out as a new day.
4. Overtime and allowances worked out in Excel. Overtime thresholds, caps and night allowances are often applied by hand after the attendance export. Every manual step is a chance to get it wrong, and nobody can say later why a number is what it is.
5. Contract labour paid on the contractor’s headcount. The contractor bills for the number on their register, and nobody checks it against who actually came through the gate.

One worker, one night: how a 3-shift day trips payroll

One day, three shifts, one worker

Shift A06:00–14:00AA Shift B14:00–22:00B Shift C22:00–06:00C Ravirostered on BRostered BWorked COT 06:0010:0014:0018:0022:0002:0006:0010:00 NIGHT Date changes 1 2 3

1. 1Ravi swapped from B to C. If the swap isn’t in the system, he’s paid for B and loses his night allowance.
2. 2His shift crosses midnight. The 06:00 punch-out belongs to the shift that started the day before, not to a new day.
3. 3He stayed two hours after his shift ended. That’s overtime, payable at twice the ordinary rate.

Ravi’s night is ordinary. He swapped onto C shift to cover for a colleague, worked through midnight and stayed two extra hours to finish a changeover. It is also exactly the kind of night that payroll systems get wrong.

If the swap only lives in the supervisor’s head, Ravi is paid for B shift and misses the night allowance he’s owed under your policy or wage settlement. If the system treats midnight as the end of a day, his shift is split in two, or his 06:00 punch-out opens a new attendance day with no punch-in. And the two hours after his shift ended are overtime, which the law requires to be paid at twice the ordinary rate of wages. If the overtime is added up by hand, it may also miss a daily or weekly limit.

None of this is unusual. In a plant of 500 people, some version of Ravi’s night happens dozens of times a month.

Contract labour: the headcount nobody reconciles

One contractor, one month

Present at the gatebiometric, average per day 212

Billed by the contractoraverage per day 18 nobody saw at the gate 230

Covered in PF / ESI challanscontractor’s deposits 34 with no proof of PF/ESI 196

18 workers×daily rate×26 days=paid for work nobody checked

Illustrative numbers.

Contract workers are often a third or more of a plant’s workforce, and they sit outside the company payroll. They’re paid through the contractor’s bill, so they’re easy to overlook in the payroll process.

Two numbers are worth checking every month. First, does the contractor’s billed headcount match gate attendance? If your biometric devices record contract workers, you already have the data. Even a small daily gap, multiplied by the daily rate and the working days, adds up to real money.

Second, is the contractor depositing PF and ESI for everyone they bill for? If they don’t, the liability can fall back on you as the principal employer. Ask for the challans and the worker list behind them, and match the names, not just the totals.

What a clean attendance-to-payroll flow looks like

The same flow, done right

Punch✓Flagged the same day

Roster✓Swaps approved in the app

Attendance✓Shift tied to its start date

OT & allowances✓Rules, not spreadsheets

Payroll run✓Gate count checked against the bill

Payslip✓ Right first time

The fix is not a better spreadsheet. It’s moving each check to where the problem starts, so the payroll run gets clean data:

• Exceptions on the same day. Missed and double punches are flagged the morning after, and the supervisor resolves them while people still remember.
• Swaps and roster changes in the system. A swap is approved in the app before the shift, so attendance is matched to the shift the person actually worked.
• Shifts tied to their start date. A night shift belongs to the day it started, however late the punch-out.
• Overtime and allowances by rule. Thresholds, caps, rates and allowances are set up once per category of worker, and calculated the same way every month, with no hand edits.
• Contract headcount checked against the gate. Gate attendance is reconciled with the contractor’s bill and challans before the bill is approved. If gate entry is still on paper, that’s one of the gaps worth closing first (see how to handle the other 20% of your ERP).

When the data arrives clean, the payroll run itself becomes the easy part: statutory deductions (PF, ESI, professional tax, LWF), payslips and the bank file.

What to look for in payroll software

Checklist: payroll software for a plant

• Shift patterns as rulesA/B/C, general and rotating shifts set up without custom code.
• Shifts that cross midnightPunches tied to the shift’s start date, not the calendar day.
• Overtime thresholdsDaily and weekly limits, caps and the double rate, by category.
• Allowances by ruleNight, shift and attendance allowances calculated, not typed in.
• Exceptions before cut-offMissed punches and swaps approved by supervisors, on mobile.
• Contract labourGate attendance reconciled with the contractor’s bill and challans.
• Statutory deductionsPF, ESI, professional tax and LWF, with state-wise rules.
• Audit trailEvery change to attendance and pay, with who made it and when.

Most payroll software demos well with one general shift and a handful of employees. A plant is a harder test. When you evaluate a system, don’t use the vendor’s sample data. Bring your own:

• your actual shift patterns, including the one that crosses midnight
• a real month’s attendance export, with its missed punches
• your overtime rules and allowance policy
• one contractor’s bill and the matching gate data

Then ask the vendor to run that month in front of you. How the system handles your messiest week tells you more than any feature list.

---

See Algorisys HRMS + Payroll run your own shift rules. Bring your roster and a month of attendance data to a demo, and we’ll walk through how it handles your shifts, overtime and contract labour. Book a demo → or read more about HRMS.