Fix Payroll Mismatch with Attendance: Reconcile Loss of Pay Before the Run Is Approved
For HR and payroll teams fielding salary complaints every month: find where attendance and pay disagree, and reconcile loss of pay before the run is approved.
To fix payroll mismatch with attendance, decide where loss of pay comes from. When HR keys absences into payroll by hand and payroll also reads the attendance system, the same absence can be deducted twice, or not at all.
In Indian factories and service businesses with shifts, biometric devices and late leave approvals, a handful of mismatches each month is common. Each becomes a complaint, a correction and a loss of trust.
This page gives the direct fix, an illustrative example from Hubballi, and how Apragya ties attendance to payroll.
Why pay and attendance disagree, and the fix
A payroll mismatch with attendance means an employee's paid days do not match the days they worked or were on approved leave. Someone is paid for an absence, or loses pay for a day they were present.
The common causes: missed punches that show as absent; leave approved after the attendance cut-off; a wrong holiday calendar; night shifts crossing midnight; joiners and leavers mid-month; half days handled differently by HR and payroll; loss of pay entered twice, once by hand and once from attendance; and manual corrections overwritten by a later device sync.
The fix is one source of truth for loss of pay, reviewed before the run is approved.
- Fix the attendance cut-off date, and apply it every month.
- Clear missed punches and pending leave before the cut-off.
- Check the holiday calendar and shift timings for each location.
- Decide one source for loss of pay: attendance or manual entry, not both.
- Agree a rule for half days and apply it consistently.
- Review loss-of-pay days per employee before approving the run.
- Correct any error in the next run with arrears or a recovery.
An example: a Hubballi food processing unit
Take an illustrative unit with 260 workers on three shifts and eSSL devices at the gate. Before approving the run, the payroll lead checked the loss-of-pay summary against each cause.
The pre-approval check, cause by cause
- Missed punches clearedEleven corrected with supervisor confirmation.Done
- Leave approved by cut-offFour requests still with managers.Pending
- Holiday calendarLocal festival holiday present.Checked
- Night shift daysCross-midnight shifts counted once.Checked
- Loss-of-pay sourceAttendance only; manual list cleared.Ready
- Half-day ruleHR and payroll counted half days differently.Mismatch
The four leave requests were approved the same day, and HR and payroll agreed one rule for half days before the run was approved. Complaints the following week fell to two, both about late punches that were fixed in the next run.
How Apragya handles attendance and payroll reconciliation
Step 1 of 5
Device punches
Punches from eSSL devices feed attendance.
- Device punches: Punches from eSSL devices feed attendance.
- Derived attendance: Punches, shifts, holidays and leave produce each day's status.
- Corrections kept: A manually corrected day is not overwritten by a later derivation.
- One loss-of-pay source: Choose attendance, manual entry or none for each company.
- Loss-of-pay summary: Per-employee days shown for review before the run is approved.
What pay and attendance mismatches cost
Employee trust
Wrong deductions lead to complaints and attrition.
Overpayments
Absences paid in full are hard to recover.
Rework
Corrections, arrears and revised payslips every month.
Statutory knock-on
PF, ESI and TDS change with the wrong pay.
Getting the loss of pay calculation right
Most mismatches are not calculation errors. They are inputs that disagree. A single source for loss of pay, reviewed before approval, removes most of them.
Separate registers, against Apragya
| Feature | Register plus payroll sheet | Apragya |
|---|---|---|
| Punches | Typed from the device | Fed from eSSL |
| Loss of pay | Keyed by hand | From one chosen source |
| Corrections | Lost on the next sync | Kept as manual overrides |
| Review | After payslips go out | Before the run is approved |
| Odd swings | Found by complaints | Flagged by an AI anomaly check |
Checked against public information on 16 September 2026.
What keeps pay and attendance in step
One employee record
HR, attendance and payroll share the same employee.
Self-service
Employees check attendance, apply for leave and see payslips on the phone.
Anomaly check
An agent flags unusual swings in a run for review.
Timesheets
Approved hours are summarised for payroll, split into regular and overtime.
Per company
Each company runs its own payroll.
Audit log
Run approvals and corrections are logged.
See attendance, payroll runs and payroll corrections. If the problem is typing, read how to fix manual data entry errors.
Getting started
- Set a fixed attendance cut-off.
- Choose one source for loss of pay.
- Connect your eSSL devices.
- Agree the half-day rule.
- Review the loss-of-pay summary each run.
Choosing one source for loss of pay usually removes the most complaints.
What it costs to start
Loss of pay calculation, answered
How is loss of pay usually worked out?
What if an employee's leave was approved after payroll?
Will a device sync overwrite HR's correction?
How are half days handled?
What does it cost to start?
Reconcile loss of pay before payday
Connect attendance to payroll and review loss-of-pay days before approving the run.