How to Stop Attendance Disputes Before Payroll Runs

By: Vikas Kohli|18 Nov 2026
HR manager reviewing employee attendance before payroll

Most payroll complaints start with attendance: a missed punch, an unapproved request or a late mark nobody explained. Each one turns into LOP, arrears or a reversal after salaries are paid. This guide shows how to write clear regularisation rules, set an attendance-to-payroll cut-off, run checks before you lock attendance and handle disputes that come in after payroll has run.

Try the HRMS That Makes HR Easy,

It Works on Autopilot.

Try QkrHR
HR Professional

Why Attendance Disputes Hurt Payroll

Attendance is the main input for monthly salary. Every absent day, half day or overtime hour changes the amount an employee receives. When that input is wrong, the error flows straight into the payslip.

Disputes are expensive for three reasons:

  • Time pressure. Under the Code on Wages, monthly wages must be paid before the end of the 7th day of the following month. There is very little time to sort out attendance questions after the month ends.
  • Rework. A dispute that comes in after payroll is locked means an LOP reversal, an arrears entry in the next payroll and sometimes a revised PF or ESI figure.
  • Trust. Employees who see unexplained deductions lose confidence in HR, even when the deduction is correct.

The Code also allows deductions for absence only for the actual period an employee was absent. A deduction based on wrong attendance data is therefore not just an employee-relations problem. It can become a compliance problem.

The good news is that most disputes are predictable. They come from a small set of causes: missed punches, field work that was not recorded, requests left pending with managers and policies employees don't understand. Fix those, and the number of complaints after payday falls sharply.

The rest of this guide sets out a simple system: clear rules, a fixed calendar, checks before locking and a fair way to correct mistakes.

The Most Common Causes Of Attendance Disputes

Before you change any policy, look at last quarter's complaints and sort them by cause. Most companies find the same handful of patterns.

CauseWhat happensFix
Missed punchEmployee was at work but shows absent or half dayAllow regularisation within a short window
Field or client visitNo punch at office, marked absentOn-duty requests, mobile or geo-tagged punches
Shift change not recordedLate mark or absence in the old shiftApproved shift change requests before the date
Work from home not approvedWFH day shows as absentWFH requests with manager approval
Pending approvalsRequest raised, manager didn't act before cut-offApproval deadlines and reminders
Holiday or weekly off errorWrong calendar for a locationLocation-wise holiday lists
Overtime not pre-approvedExtra hours worked but not paidOvertime requests and approval rules

Two lessons come out of almost every review.

First, many "attendance errors" are really approval delays. The employee did raise a request, but it sat with a manager until payroll closed. Fixing approvals alone can remove a large share of disputes.

Second, field staff and shift workers produce most of the complaints. Their attendance is harder to capture, so they need tools such as a field staff tracking app and on-duty requests, not just a biometric device at the office.

Track these causes every month. A small dashboard of disputes by reason and department shows where to act first.

Write A Clear Regularisation Policy

Attendance regularisation (AR) lets an employee correct a day where the system record is wrong, for example a missed punch. Without clear rules, AR either becomes a loophole or a source of complaints.

Your AR policy should answer these questions:

  • Who can apply? Usually the employee, with HR able to apply on their behalf in exceptions.
  • For what reasons? List them: missed punch, device failure, client visit, network problem. Use on-duty and WFH requests for planned work away from the office.
  • How far back? Set a backdated window, for example five days from the attendance date.
  • When does the month close? For example, requests for a month must be raised by the 5th of the next month, even if the five-day window is still open.
  • How many per month? A limit, such as three regularisations a month, prevents misuse. Allow HR to approve more in genuine cases.
  • Who approves, and how fast? Name the approver (usually the reporting manager) and a deadline, such as 48 hours. Pending requests should escalate automatically.
  • What evidence is needed? For example, a client visit note or a gate entry record.
  • What happens after the window? The day stays as recorded. Any correction goes through HR and is paid as arrears in the next payroll.

Publish the policy on your HRMS and include it in induction. Employees accept a rule they knew about in advance far more easily than one they discover on payday.

Set An Attendance-to-Payroll Cut-Off Calendar

A cut-off calendar tells everyone when attendance stops changing for a given payroll. Without it, requests keep arriving while payroll is running.

There are two common approaches.

Approach 1: Close the full calendar month. Attendance for the whole month is captured and locked a few days after month-end. This gives the most accurate pay, but the window is tight because salaries must be paid by the 7th.

Day of next monthActivity
1st–3rdEmployees raise final AR, on-duty and WFH requests
4th–5thManagers clear all pending approvals
5thAttendance closes for new requests
6thHR runs pre-lock checks and locks attendance
6th–7thPayroll is processed and salaries are paid

Approach 2: Mid-month cut-off. Attendance is locked on, say, the 25th. Days from the 26th to month-end are assumed present, and any absence in that period is adjusted as LOP in the next month's payroll. This gives payroll more time, but every month carries a few adjustments.

Whichever approach you choose:

  • Publish the calendar for the full year in advance, including holiday months.
  • Send reminders to employees two days before the request window closes, and to managers before the approval deadline.
  • Never change the cut-off for one department without telling everyone.

Late Marks, LOP And Overtime: Keep The Rules Fair

Late marks, loss of pay and overtime cause the most heated disputes, because they change the amount paid. Clear, written rules help.

Late marks. Many companies convert repeated late arrivals into a half day of leave or LOP, for example three late marks in a month. Put this in your attendance policy and standing orders. Since the Code on Wages allows deductions for absence only for the actual time not worked, take advice before deducting pay for short delays. Adjusting leave balances is usually safer than cutting pay.

Loss of pay (LOP). Decide on a daily rate method and use it consistently. With a monthly wage of ₹26,000 and a fixed divisor of 26 days, the daily rate is ₹1,000. Two days of LOP means a deduction of ₹2,000. Some companies use calendar days instead. Either can work, but switching between them causes complaints.

Overtime. Under the Labour Codes, the normal working day is eight hours and the week is capped at 48 hours. Work beyond normal hours must be paid at least twice the normal rate.

CalculationAmount
Monthly wage₹26,000
Daily rate (÷ 26)₹1,000
Hourly rate (÷ 8)₹125
6 overtime hours at 2×₹1,500

Require overtime to be requested and approved, ideally before it is worked. Keep accurate time records, because unpaid overtime claims often surface during exits or inspections.

Run Pre-Lock Checks Before You Lock Attendance

Locking attendance is the point where payroll processing takes over. A short checklist before the lock catches most problems that would otherwise turn into disputes.

QkrHR's Attendance Pre-Lock Checks gives HR a guided review for each month, in three groups:

  • Clear pending approvals. Leaves, attendance regularisations, short leaves, WFH requests, comp-off credits, on-duty requests, and adjustments and overtime. Anything still pending is listed, so HR can chase the approver before the lock.
  • People changes this cycle. Employees who have stopped coming, exits that are not yet complete, and new joiners for the month. These are the cases where attendance and salary most often go wrong.
  • Attendance readiness. Any pending attendance updates that still need processing.

The checklist saves progress and keeps a history of who reviewed it and when. If a dispute comes up later, you can show exactly what was checked before payroll.

Once the checks are clear, use Lock/Unlock Attendance to lock the month. After locking, attendance changes go through a controlled correction, not a quiet edit.

A good habit is to make the pre-lock review a named step in your payroll calendar, owned by one person in HR. The review is quick, and it is far cheaper than reversing LOP for dozens of employees after salaries are paid.

Handling Disputes After Payroll Has Run

Even with good rules, some disputes will come in after payday. A fixed process keeps them fair and quick.

  1. Log the dispute. Ask employees to raise it through the HRMS or helpdesk, not on chat. Record the date, the days in question and the amount involved.
  2. Check the evidence. Look at the punch log, device or mobile records, any face-check data, on-duty requests and manager approvals for those days.
  3. Decide and record the reason. If the employee is right, record why the original entry was wrong, for example a device failure or a delayed approval.
  4. Correct the attendance with a trail. In QkrHR, use Correct Attendance so that the change appears in Attendance Corrections History with who changed what and when.
  5. Reverse the LOP in the next payroll. Use LOP Reversals so the amount is paid as arrears in the next salary run through the payroll software, with PF and ESI calculated correctly.
  6. Tell the employee. Confirm the outcome and the month in which the amount will be paid.

Then measure. Useful monthly numbers include regularisation requests per 100 employees, average approval time, corrections made after the lock, and LOP reversals by department. If one team shows a spike, the cause is usually a device problem, a new shift pattern or a manager who needs a reminder about approvals.

Over a few months, these numbers show whether your rules are working.

Book Free Demo Now!

Table of Contents

Frequently Asked Questions

Haven't got your answer? Contact our support now

Attendance regularisation is a request to correct a day where the attendance record is wrong, for example because of a missed punch or a device failure. The employee applies, the manager approves, and the corrected record is used for payroll.

The Code on Wages allows deductions for absence only for the actual period not worked. Many companies adjust leave balances for repeated late marks instead of cutting pay. Put any rule in your written policy and take legal advice before deducting wages.

The day is processed as recorded in the system, which may mean LOP. If the request is later approved, HR corrects the attendance and reverses the LOP in the next payroll as arrears. Automatic reminders and escalations help prevent this.

There is no legal rule, so it is a company policy. A window of three to seven days from the attendance date, with a month-close date shortly after month-end, works for most companies. The window should leave time to pay wages by the 7th of the next month.

Work beyond normal working hours must be paid at least twice the normal wage rate. The normal working day is eight hours and the weekly limit is 48 hours. Keep approved overtime records for every employee.

Yes, but only through a controlled correction with an audit trail. The difference is then paid or recovered in the next payroll. Quiet edits to locked attendance make audits and disputes much harder to resolve.

Subscribe to our Newsletter

Subscribe to our email newsletter to get the latest posts delivered right to your email.