Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Payroll fix

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.

An HR executive watching a worker use a fingerprint device at a factory gate

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.

  1. Fix the attendance cut-off date, and apply it every month.
  2. Clear missed punches and pending leave before the cut-off.
  3. Check the holiday calendar and shift timings for each location.
  4. Decide one source for loss of pay: attendance or manual entry, not both.
  5. Agree a rule for half days and apply it consistently.
  6. Review loss-of-pay days per employee before approving the run.
  7. 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 summary showed two open items before a single payslip went out.

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.

Pay envelopes paired with attendance cards, one pair set apart with a ribbon
The half-day rule was the one open item, agreed before the run was approved.

How Apragya handles attendance and payroll reconciliation

Step 1 of 5

Device punches

Punches from eSSL devices feed attendance.

  1. Device punches: Punches from eSSL devices feed attendance.
  2. Derived attendance: Punches, shifts, holidays and leave produce each day's status.
  3. Corrections kept: A manually corrected day is not overwritten by a later derivation.
  4. One loss-of-pay source: Choose attendance, manual entry or none for each company.
  5. 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

FeatureRegister plus payroll sheetApragya
PunchesTyped from the deviceFed from eSSL
Loss of payKeyed by handFrom one chosen source
CorrectionsLost on the next syncKept as manual overrides
ReviewAfter payslips go outBefore the run is approved
Odd swingsFound by complaintsFlagged 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

  1. Set a fixed attendance cut-off.
  2. Choose one source for loss of pay.
  3. Connect your eSSL devices.
  4. Agree the half-day rule.
  5. 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

INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus Payroll
2,000
AI Credits a month
Included on Starter
Free
Up to 3 users
CRM, HR and Vendor Onboarding

Loss of pay calculation, answered

How is loss of pay usually worked out?
Salary for the month is reduced in proportion to unpaid days over the days used as the base. Your salary structure decides the base.
What if an employee's leave was approved after payroll?
Correct it in the next run with arrears, and tighten the approval cut-off.
Will a device sync overwrite HR's correction?
No. A day marked as a manual override is left as corrected.
How are half days handled?
Agree one rule and apply it everywhere. Check how your setup counts half days before the run.
What does it cost to start?
Payroll is available from the Starter plan, INR 3,999 a month for up to 10 users, which includes CRM and HR plus a choice of enterprise apps and 2,000 AI Credits a month. Pro, at INR 7,999 a month, covers 25 users and every enterprise app.

Reconcile loss of pay before payday

Connect attendance to payroll and review loss-of-pay days before approving the run.