Loss of Pay (LOP): Calculation Rules and Payroll Setup

Loss of Pay (LOP): Calculation Rules and Payroll Setup

Every payroll team has lived through the same conversation. It is the 3rd of the month, salaries have been credited, and an employee walks up with a payslip and one question: "Why has this much been cut?" Nine times out of ten the answer is Loss of Pay — and nine times out of ten the argument that follows is not about whether the person was absent, but about how the deduction was arrived at. Getting loss of pay calculation right is less about arithmetic and more about the chain of decisions behind it: which divisor you use, which salary components you touch, whose approval closed the attendance record, and whether any of that was written down before the month began.

This guide is written for HR operations, payroll executives, founders running payroll themselves, and shift or attendance managers in India and comparable markets. It covers what LOP actually is, the three common per-day salary divisors and how each one changes the number, half-day and partial-day handling, late marks and short hours, sandwich leave, LOP during notice period and probation, reversals and regularisation, payslip transparency, the attendance-to-payroll pipeline, a sample policy clause you can adapt, and a dispute-handling runbook.

A note before we start, and it matters: every rupee figure in this article is illustrative. They exist to demonstrate method, not to state entitlements. Statutory rules on leave, wages, deductions and contributions in India vary by central and state legislation, by establishment type, by applicable Shops and Establishments Act, and by your certified standing orders and employment contracts. Treat the guidance here as operational design advice, and verify anything statutory with official sources and your own legal or compliance advisor before you configure it.

What Loss of Pay Actually Means

Loss of Pay — LOP, also written as Leave Without Pay (LWP) or simply "unpaid absence" — is the reduction in an employee's earnings for a pay period because the employee did not render service on one or more days (or parts of days) and had no paid leave balance or paid entitlement to cover that absence.

Two things are worth separating carefully, because conflating them is the root of most LOP disputes:

• LOP is a non-earning, not a deduction. The employee did not earn salary for those days, so the earning is reduced at source. It is different in character from a deduction such as a recovery of an advance, a fine, or a statutory deduction taken out of earned wages.
• A "deduction" is money taken out of wages that were earned. Deductions from wages are a regulated area in India and the permissible categories and limits are governed by wage legislation. Fines and punitive cuts in particular are treated differently from unpaid absence.

Why does the distinction matter practically? Because payslip presentation, contribution computation and how you defend the treatment in an audit all depend on it. Most well-run payrolls show LOP as a reduction of gross earnings — a "LOP days" count that scales earnings down — rather than as a line under deductions.

When LOP Typically Applies

One row there deserves emphasis, because it is a frequent configuration error. A mid-month joiner or leaver is not on LOP. They are on pro-rata salary — they were not employed on the other days at all, so no absence occurred. Some systems scale both the same way and the numbers can coincide, but the semantics differ and the payslip should say the right thing. If someone joins on the 16th and the payslip reads "LOP days: 15", you have created a document that says the employee was absent for half a month. That reads badly in a background verification and worse in a dispute.

The Core Formula

At its simplest:

LOP amount = Per-day salary x Number of LOP days

and

Per-day salary = LOP-applicable monthly salary / Divisor

Three variables, three decisions. The number of LOP days comes from attendance. The LOP-applicable salary comes from your component design. The divisor comes from your policy. Two organisations paying identical salaries to identical employees with identical absences will produce different LOP amounts if any one of those three decisions differs — and both can be entirely correct, because none of the three is dictated to you by a single universal rule. What you cannot do is leave them undefined, or change them silently mid-year.

Let us take each in turn, starting with the one that causes the most confusion.

Choosing a Per-Day Salary Divisor

The divisor is the number you divide monthly salary by to get a day's pay. There are three approaches in common use.

Method 1: Calendar Days in the Month

The divisor is the actual number of days in the month — 28, 29, 30 or 31.

Logic: salary is paid for the month, and the month has as many days as it has. Weekly offs and holidays are paid days sitting inside the month, so a day's pay is the monthly salary spread across every day.

Effect: the per-day rate fluctuates month to month. A day of absence costs more in February than in January.

Method 2: Fixed 30 Days

The divisor is always 30, regardless of the actual month length.

Logic: a stable, predictable per-day rate across the year. Easy to explain, easy to reproduce, easy to audit.

Effect: in a 31-day month, an employee present all month is paid 31 days' attendance against a 30-day divisor. In February, the reverse. It evens out roughly over the year but not exactly, and it produces one visible quirk — 31 days of LOP in a 31-day month, computed as 31 x (salary/30), exceeds monthly salary. Any system using a fixed-30 divisor must cap total LOP at monthly salary. This is not a hypothetical edge case; it turns up whenever someone is absent for a full month on unpaid leave.

Method 3: Actual Working Days

The divisor is the number of scheduled working days in the month after removing weekly offs and declared holidays.

Logic: the employee is paid for working days; weekly offs and holidays are a benefit attached to working days. An absence therefore costs a working day's pay, which is more than a calendar day's pay.

Effect: the highest per-day rate of the three, and the most volatile — it moves with the holiday calendar, and it differs between employees on different shift rosters or in different states with different holiday lists. It is also the method most likely to be questioned by employees, because "one day off cost me more than 1/30th of my salary" needs explaining.

The Same Scenario Under All Three Methods

Illustrative case: monthly gross of INR 60,000, February 2026 (28 calendar days, 4 Sundays as weekly offs, 24 scheduled working days, no declared holiday in this example), 2 days of LOP.

Same employee, same absence, same month, three defensible answers with a spread of INR 1,000 between the extremes. On a 500-person payroll with a handful of LOP cases a month, that spread compounds into a meaningful number — and into a meaningful volume of queries if nobody knows which method is in force.

Now run the same salary through a 31-day month. July 2026: 31 calendar days, 4 Sundays, one declared holiday in this illustration, so 26 scheduled working days. Again 2 LOP days.

Notice how the calendar-day method flips from being harsher than fixed-30 in February to being gentler in July, while the working-day method is consistently the most expensive for the employee.

Per-Day Rate Volatility Across a Year

To make the volatility concrete, here is the illustrative per-day rate on INR 60,000 monthly gross across four months of 2026, assuming Sunday-only weekly offs and no declared holidays (working-day counts will drop further once your holiday list is applied):

The fixed-30 column is the only one that does not move. That predictability is the single biggest reason it is popular with payroll teams, and the single biggest reason employees find it easy to accept: the arithmetic can be done on a phone calculator by anyone, in any month, and it always lands on the same per-day number.

Which Divisor Should You Pick?

There is no universally "correct" answer, and you should be sceptical of anyone who tells you there is. What matters is that the choice is (a) written into policy or the employment contract, (b) applied uniformly to all employees in a defined group, (c) applied consistently across months rather than switched to suit a case, and (d) explained on or alongside the payslip.

A few practical considerations:

• Fixed 30 is the most common default in Indian payroll systems and the easiest to defend on grounds of consistency and simplicity. Its weakness is the full-month-absence overshoot, which you handle with a cap.
• Calendar days self-caps neatly — 28 days of LOP in a 28-day month equals exactly one month's salary. Its weakness is month-to-month variability that employees notice.
• Actual working days is the most defensible on pure logic where pay is genuinely tied to working days, and is common in manufacturing and shift-heavy contexts. Its weakness is complexity: a per-location, per-shift, per-holiday divisor, producing the highest deduction.

Some organisations use fixed 30 for monthly-rated staff and actual working days for shift or hourly-rated staff, on the reasoning that the two populations have different pay bases. That is fine, as long as the grouping rule is objective and documented.

Above all: do not use one divisor for LOP and a different one for pro-rata joining and exit unless you have a written, explained reason. That asymmetry is a common source of "the maths doesn't add up" complaints, because an employee who joins mid-month and later takes LOP sees two different day-rates on two payslips and reasonably asks why.

Which Salary Components LOP Should and Should Not Touch

The second variable is the base you apply the per-day rate to. "Monthly salary" is not one number — it is a stack of components, and not all of them behave the same way when someone is absent.

The guiding question for each component is simple: is this component earned by rendering service on a day, or is it a reimbursement, a variable payout, or a statutory employer cost?

Two points to underline.

First, reimbursements. If an employee submits a genuine fuel bill for INR 3,000 and is on 2 days LOP, they should still be reimbursed INR 3,000. The expense was incurred. Scaling a reimbursement by attendance is a fast route to a legitimate grievance, and it also muddies the tax treatment of the component. Configure reimbursement components as LOP-exempt in your payroll system explicitly rather than relying on defaults.

Second, variable pay. Incentives, commissions and performance bonuses should be governed by the incentive scheme document, not the LOP engine. If the scheme pro-rates a quarterly incentive for unpaid absence beyond a threshold, that is a scheme rule, applied by whoever administers the scheme with its own calculation shown. Silently applying a monthly LOP factor to a quarterly incentive is a classic dispute, because the employee cannot reconcile the number against either document.

Worked Example: Component-Level LOP

Illustrative monthly structure, fixed-30 divisor, 3 LOP days (LOP factor = 3/30 = 0.10, so the employee is paid 90% of LOP-applicable components):

The total LOP impact is INR 6,000 — exactly 3 x (60,000 / 30), where 60,000 is the LOP-applicable gross, not the 66,000 headline gross. Had the system applied the LOP factor blindly to everything, the reduction would have been INR 6,600, short-changing the employee on a reimbursement and on overtime actually worked.

Half-Day and Partial-Day LOP

Full-day LOP is easy. Fractions are where systems and policies diverge.

Half-day LOP is simply 0.5 x per-day salary. Using the fixed-30 example on INR 60,000, a half-day costs INR 1,000. The harder question is not the arithmetic — it is defining what constitutes a half day.

Common definitions, any of which can be reasonable if written down:

• Hours-based: the employee worked at least the minimum hours for a half day (say 4 hours 30 minutes against a 9-hour standard day) but less than the minimum for a full day.
• Session-based: the employee was present for the first or second half of the shift, measured against a defined mid-point.
• Leave-request-based: the employee applied for a half-day leave and it was approved; attendance simply confirms presence for the other half.
• Punch-based: first punch after a cut-off time, or last punch before a cut-off time, is treated as a half day.

Whichever you use, the rule needs to state what happens at the boundaries. If the standard day is 9 hours and the half-day threshold is 4.5 hours, what is the treatment for 4 hours 25 minutes? For 8 hours 50 minutes? Boundary silence is where disputes live. A clean rule reads something like: "Under 4.5 hours of recorded working time on a scheduled working day, with no approved leave, is treated as a full-day LOP. Between 4.5 and 8 hours is treated as a half-day LOP unless regularised. 8 hours or more is treated as a full working day."

Worked Example: Mixed Fractional LOP

Illustrative: INR 60,000 gross, fixed-30 divisor (per-day INR 2,000), in a month with the following exceptions after regularisation closes:

LOP amount = 3.5 x 2,000 = INR 7,000 (illustrative). Note the 11th: three hours of work does not earn a half day under the illustrative rule above, so it is a full-day LOP. That is exactly the kind of case where an employee will argue "but I came in", and the only satisfying answer is a written threshold they were told about in advance.

Late Marks, Short Hours and Grace Periods

Converting lateness into LOP is legitimate and common, but it is the area where policies most often drift into being punitive rather than compensatory — and punitive deductions from earned wages are a regulated area in India that you should not design casually. Keep the framing on non-earning of time rather than penalty, keep the conversion proportionate, and have your policy reviewed by someone qualified before you roll it out.

A typical, proportionate structure looks like this (illustrative):

• A grace period of 10 to 15 minutes past shift start, not counted as late.
• A late mark recorded for arrival beyond grace.
• A monthly allowance of, say, 3 late marks with no consequence.
• Conversion of every 3 late marks beyond the allowance into 0.5 day LOP.
• A separate short-hours rule for total monthly hours falling materially below the scheduled total.

Some cautions from practice:

• Do not double-count. If a day is already a half-day LOP for short hours, it should not also feed the late-mark counter. Your attendance engine needs an explicit precedence order.
• Exempt genuine work situations. Client visits, night-shift handovers, on-call callouts and travel days should be tagged and excluded, not silently marked late.
• Publish the counter. A late-mark tally that only becomes visible on the payslip is a dispute waiting to happen.
• Do not apply shift-based late rules to genuinely flexible roles unless the arrangement defines core hours.
• Reset the counter on a defined cycle and state whether that cycle is the calendar month or the payroll cycle. They are often not the same.

Sandwich Leave, Weekly Offs and Holidays

"Sandwich leave" is the practice of counting an intervening holiday or weekly off as leave (or as LOP) when the employee is absent on both the day before and the day after it. It is one of the most contested rules in Indian HR, and it is worth being deliberate about because the employee-relations cost of an aggressive sandwich rule frequently exceeds the money it saves.

Four policy positions, each internally coherent:

Worked comparison. Illustrative INR 60,000 gross, fixed-30 divisor, per-day INR 2,000. An employee is absent on a Friday and the following Monday, with Saturday and Sunday as weekly offs, and has no leave balance.

Doubling a reduction on account of days the employee was never scheduled to work needs unusually clear disclosure. If you adopt anything other than Option A, three things are non-negotiable: it appears verbatim in the leave policy, it is acknowledged at onboarding, and it is flagged on the leave application screen before the employee submits. Consider too whether the rule is defensible in your legal and contractual context — leave rules interact with statutory provisions and standing orders, so verify rather than assume.

One related point: weekly offs and holidays inside a long unpaid absence are almost always counted within the unpaid period, because the employee is not in service on any of those days. That is a different situation from the sandwich rule and should be configured separately.

LOP in Special Situations

Ordinary mid-month absence is the easy case. The situations below are where configuration gaps show up.

The LOP Scenarios Matrix

The last row is the most common avoidable dispute in hybrid organisations. Someone worked, worked productively, and lost a day's pay because nobody tagged the day. That is a data problem masquerading as an attendance problem, and it destroys trust in payroll faster than almost anything else.

LOP During the Notice Period

This one deserves its own note. Several things can happen simultaneously when an employee takes unpaid absence while serving notice:

• The LOP itself reduces earnings in the month it falls, in the normal way.
• Your policy may say the notice period extends by the number of LOP days, so the last working day shifts. Many contracts do say this. Whether yours does is a contract question, not a payroll question — read the contract before the payroll team decides.
• If the notice period is not extended and the employee is short-served, a notice pay recovery may arise. That is a deduction, not LOP, and it belongs in the deduction block of the full-and-final statement with its own basis stated.
• Leave encashment at exit, where applicable, is computed on the encashable balance under your policy and the applicable rules. If LOP days affected leave accrual during the notice period, the encashable balance changes too — make sure the sequence of computation is defined so the same day is not counted twice.

Run notice-period cases through a manual review queue rather than pure automation until you trust the configuration. The combination of LOP, extension, recovery and encashment in one statement is where full-and-final settlements go wrong most often — and an F&F dispute lands after the employee has left, when goodwill is lowest.

LOP During Probation

There is nothing inherently different about LOP for probationers — a day not worked is a day not earned regardless of employment status. What usually differs is leave entitlement: many organisations give probationers a reduced quota, or no accrual until confirmation, which mechanically produces more LOP.

If that is your design, make it visible. A probationer who believes they have 18 days of annual leave and discovers on their first payslip that none had accrued will feel misled even if the offer letter said so. Show the accrued-versus-entitled distinction in the portal from day one, and nudge in the leave application flow when requested days exceed available balance.

Extended Unpaid Leave and Sabbaticals

For long unpaid absences, decide and document four things in advance, ideally in a written sanction letter the employee signs:

1. Span treatment — whether weekly offs and holidays inside the span are counted as unpaid (usually yes).
2. Benefit continuity — what happens to insurance cover, device allocation, and any recurring benefit during the period.
3. Accrual — whether paid leave continues to accrue during unpaid absence (commonly it does not, but verify against applicable rules and your policy).
4. Return terms — the confirmed return date, the role on return, and what happens if the return is delayed.

Statutory contributions during long unpaid absence follow the wages actually payable and the rules of the relevant scheme. Where the payable wage for a month is nil or near-nil, the treatment of contributions, of the contribution period, and of any minimum wage or scheme-specific floor needs to be checked against the current rules for that scheme. This is exactly the kind of question to route to your compliance advisor rather than to a payroll checklist.

LOP Reversal, Regularisation and Arrears

No attendance system is perfect, so your LOP process needs a clean way to undo LOP. Two mechanisms matter.

Regularisation (before payroll closes)

Regularisation is the employee-initiated correction of an attendance record — a missed punch, a field visit, a work-from-home day, an approved late start. The design questions are:

• Window. How many days does an employee have to raise a regularisation? A common design is "within 7 days of the exception, and in all cases before the attendance cut-off date". A window that is too short creates unfair LOP; a window with no end creates a payroll that never closes.
• Approver. Almost always the reporting manager, because they are the only person who actually knows whether the employee was working.
• Limits. Some organisations cap regularisations at, say, 3 per month so the mechanism does not become a substitute for punching in. If you do, make sure field roles are not penalised — those days should be tagged as on-duty, not regularised.
• Auto-escalation. If a manager does not act within a set number of days, the request should escalate rather than expire. An expired-by-default regularisation is an LOP created by managerial inaction, and employees are right to be angry about it.

Reversal (after payroll closes)

Sometimes LOP is applied and later found to be wrong — a leave approval that did not sync, a biometric outage, a shift roster that was changed verbally. The correction path should be an arrear in the next payroll cycle, not an off-cycle cash payment and not a quiet edit to a closed period.

Why arrears rather than reopening the month? A closed period has already generated payslips, statutory filings, accounting entries and bank files, and reopening invalidates all of them. A clean arrear line — "LOP reversal, previous month, 2 days" — preserves the audit trail and is easy to follow.

A workable arrears policy:

1. Employee or manager raises a payroll query within a defined window after salary credit (say 10 days).
2. Payroll validates against the attendance and leave records as they stood at cut-off.
3. If the LOP was incorrectly applied, an arrear is raised with a reason code and an approver.
4. The arrear appears as a distinct earning line in the next payslip, referencing the original period.
5. The original month is never edited; the correction is always additive and always traceable.

The same discipline works in reverse. If LOP was missed — an absence that should have been unpaid was paid — recovering it needs care. Recovering from a subsequent salary is a deduction, and deductions from wages are regulated. At minimum: notify the employee in writing before the recovery, explain the basis, allow a response, and consider spreading the recovery rather than taking it in one month. Where the amount is significant or the employee disputes it, take advice before proceeding.

Effect on Statutory Contributions and Leave Accrual

Keep this section general and verify specifics — the rules change, and they differ by scheme and by establishment.

Statutory contributions. In broad terms, contributions to statutory social security schemes in India are computed on the wages actually payable for the period, so a reduction in payable wages from LOP generally flows through to the contribution base. There are scheme-specific nuances — wage definitions differ between schemes, some have ceilings, and treatment in a zero-wage month is its own question. Do not hard-code assumptions; configure contributions on the post-LOP payable wage per each scheme's own definition and have it reviewed against current rules.

Professional tax and income tax. Professional tax slabs are state-specific and typically keyed to salary actually paid in the month, so LOP can move an employee across a slab boundary. Income tax withholding runs on projected annual income, so material LOP mid-year should trigger a re-projection rather than being ignored until March.

Leave accrual. Most organisations accrue paid leave monthly on the basis of service rendered. The design questions are whether accrual is suspended in months with substantial LOP, whether there is a threshold, and whether accrual resumes automatically. Statutory entitlements have their own qualifying-service rules sitting underneath your policy. Whatever you decide, apply it uniformly and show the logic in the leave balance screen.

Payslip Presentation and Transparency

A large share of LOP disputes are not really disputes about money. They are disputes about not being able to check the number. The fix is presentation.

The single highest-return change most payroll teams can make is publishing the specific dates of LOP alongside the payslip, in the self-service portal if not on the payslip itself. An employee who sees "LOP: 3 days" has to reconstruct their month from memory to check it. An employee who sees "LOP on 4th, 11th, 26th" either recognises those dates immediately or has a precise, resolvable question. The volume of vague, adversarial queries drops sharply.

Two more presentation rules are worth adopting. Show LOP as a reduction in earnings rather than a line under deductions — the employee did not earn those days, so the money was never a wage that was then taken away. And never net off unrelated items: if there is an LOP, a canteen recovery and an arrear, show three lines.

The Attendance-to-Payroll Data Pipeline

LOP is where attendance data meets money, and it is the only place in HR where a data quality problem converts directly into a bank transaction. That deserves a designed pipeline, not an ad hoc monthly scramble.

The Five Stages

1. Capture. Raw attendance events arrive — biometric punches, mobile geo-tagged check-ins, web clock-ins, access-control logs, shift roster assignments, or manual muster entries for sites without devices.
2. Normalise. Raw events become daily attendance states per employee: present, half day, absent, weekly off, holiday, on-duty, work-from-home, on-leave. This stage applies shift definitions, grace periods, break rules and night-shift date-attribution logic.
3. Reconcile. Attendance states are matched against approved leave records and holiday calendars. Exceptions are surfaced to employees and managers for regularisation.
4. Freeze. At the cut-off, the attendance month is locked. Unresolved exceptions resolve to their policy default (usually LOP), and the LOP day count per employee becomes an input to payroll.
5. Compute and publish. Payroll applies the divisor and component rules, produces payslips with LOP detail, and files the supporting register.

A Workable Monthly Calendar

Illustrative, for a payroll cycle running the 1st to the last day of the month with salary credit at the start of the following month:

The lagged-days question — what to do about the 25th to month-end when your cut-off is the 24th — has two clean answers. Either estimate and true-up (assume presence, correct any LOP as an arrear next month) or lag the cycle (this month's payroll covers the 25th of last month to the 24th of this month). Estimating is more employee-friendly because it never creates an LOP the employee has not had a chance to contest; lagging is more accurate but means an absence on the 26th surfaces five weeks later. Pick one, state it in policy, and never mix the two.

Attendance Exception Types and Resolution Owners

Two rows in that table say "never LOP" or "hold LOP", and they are the important ones. A system failure must never become an employee's pay cut. If a device was down, the network dropped, or a leave approval failed to sync, the default must be to hold the LOP and investigate rather than apply it and wait for a complaint. Build that as an explicit rule, with a flag that suppresses LOP for any day covered by a declared system incident.

Approval Workflow and Audit Trail

For LOP to be defensible, you need to be able to answer, months later, three questions about any single LOP day: who decided it, on what basis, and when.

The minimum audit trail per LOP day:

• The raw attendance record and its source (device ID, app, manual entry).
• The leave record checked against it, including balance at the time.
• Any regularisation request raised, its content, and its outcome.
• The approver's identity and the timestamp of the decision.
• The policy rule applied (which threshold, which divisor, which sandwich option).
• The freeze timestamp and the user who executed the freeze.
• Any subsequent reversal or arrear, with reason code and approver.

Three controls make this trail meaningful rather than decorative:

1. Immutability after freeze. Once the attendance month is frozen, records are read-only. Corrections happen as forward-dated adjustments, never as edits.
2. Separation of duties. The person who approves attendance regularisation should not be the person who executes the payroll run. On small teams where the same person does both, add a second-pair-of-eyes review of the LOP register before payroll computation.
3. Variance review. Before every run, review the LOP register for outliers — anyone above a threshold, anyone with LOP for the first time, any team with a sudden spike. Most genuine payroll errors are visible in a variance report before they become disputes.

Writing a Defensible LOP Policy Clause

If your policy does not describe the mechanics, your payroll team is inventing them monthly and no two months will match. Here is sample wording you can adapt. Treat it as a drafting starting point only — have it reviewed against your contracts, standing orders and applicable law before adoption.

Loss of Pay (LOP) 1. Definition. Loss of Pay applies to any scheduled working day, or part of a working day, on which an employee does not render service and for which no paid leave entitlement, holiday, weekly off, or approved paid absence is available or applicable. 2. Per-day salary. For all LOP computations, per-day salary is calculated as the employee's LOP-applicable monthly gross salary divided by a fixed divisor of thirty (30) days, irrespective of the number of calendar days in the month. The same divisor is used for pro-rata computation on joining and separation. 3. LOP-applicable salary. LOP-applicable monthly gross comprises basic salary, house rent allowance, and all fixed monthly allowances. Reimbursements against submitted claims, overtime, and payouts under variable pay or incentive schemes are excluded and are governed by their own rules. 4. Fractional LOP. Recorded working time of less than [4.5] hours on a scheduled working day, without approved leave, is treated as one full day of LOP. Recorded working time between [4.5] and [8] hours, without approved leave, is treated as half a day of LOP. 5. Weekly offs and holidays. Weekly offs and declared holidays are paid and are not counted as LOP, except where they fall within a continuous period of approved unpaid leave, or where an absence on both the preceding and succeeding working days is unauthorised. 6. Regularisation. Attendance exceptions may be regularised by the employee within seven (7) calendar days of occurrence and in all cases before the monthly attendance cut-off date notified by HR. Requests not actioned by the reporting manager within three (3) working days escalate automatically to the next level. 7. Cut-off and freeze. The attendance month is frozen on the date notified by HR each month. Exceptions unresolved at freeze are treated in accordance with the default outcomes published in the Attendance Exception Schedule. 8. System failure. Where attendance data is unavailable due to a declared device, network or system failure, LOP shall not be applied for the affected period; affected days will be regularised in bulk by HR. 9. Correction. LOP incorrectly applied will be reversed by way of an arrear in the next payroll cycle. Payroll periods once closed will not be reopened. 10. Notice period. LOP days availed during the notice period shall [extend the notice period by an equivalent number of days / not extend the notice period], as provided in the employment agreement. 11. Transparency. LOP days, the applicable per-day rate, and the specific dates on which LOP was applied will be made available to the employee with each payslip.

Clause 11 is the one people skip and the one that saves the most time. Clause 8 is the one that saves the most goodwill.

Configuring an HRMS for LOP: A Step-by-Step Setup

If you are setting this up in an HRMS or payroll system — CozyHR or any other — this is a sensible order of operations. Doing it in this sequence avoids the rework that comes from configuring payroll rules before attendance rules exist.

1. Define the working calendar. Shifts, weekly-off patterns (including alternate-Saturday patterns), and location-specific holiday lists. Everything downstream depends on knowing which days were scheduled working days for each employee.
2. Define attendance rules. Grace period, half-day and full-day hour thresholds, late-mark rules and monthly allowances, night-shift date attribution, and the precedence order when two rules could apply to the same day.
3. Define leave types and mark which are unpaid. Every leave type needs an explicit paid or unpaid flag. Never let a leave type inherit a default.
4. Set the LOP divisor. Choose calendar days, fixed 30, or working days. Set the same divisor for pro-rata joining and exit unless you have documented a reason not to.
5. Flag components as LOP-applicable or exempt. Go through every component in every salary structure, including ones used by a single grade. Reimbursements and overtime are the ones most often mis-flagged.
6. Configure the sandwich rule. Pick the option, and confirm the system evaluates it against scheduled working days rather than calendar adjacency.
7. Set regularisation windows and approval chains. Include auto-escalation, and set the default outcome for each exception type at freeze.
8. Set the cut-off and freeze dates. Publish them in the shared HR calendar so managers know when their inaction becomes someone else's pay cut.
9. Configure the LOP cap. Total LOP in a month must never exceed the LOP-applicable monthly salary. This matters most under a fixed-30 divisor in 31-day months.
10. Configure payslip fields. Payable days, LOP days, divisor, per-day rate, and a link or annexure with LOP dates.
11. Run a parallel month. Compute LOP both in the system and in a spreadsheet for a sample of 20 to 30 employees, deliberately including half days, sandwich cases, a mid-month joiner, a mid-month leaver, and a notice-period case. Reconcile to the rupee before going live.
12. Publish the rules. A one-page explainer with two worked examples, sent to all employees and included in onboarding. Most people accept a rule they understood in advance and contest one they discovered on a payslip.

Common Mistakes and Disputes

The patterns below account for the large majority of LOP escalations.

1. The divisor was never written down. Payroll uses fixed 30, the offer letter implies working days, and nobody notices until an employee does the arithmetic. Fix: state the divisor in the policy and repeat it on the payslip.

2. Reimbursements got scaled by the LOP factor. A blanket LOP factor applied across all components. Fix: component-level LOP flags, audited annually.

3. Approved leave did not sync to attendance. The leave system approved it; the attendance system never saw it; LOP was applied. Fix: single source of truth, and a hard rule that any conflict between an approval record and an attendance record holds LOP for manual review.

4. Managers did not action regularisations. Requests sat unapproved until freeze and defaulted to LOP. Fix: auto-escalation plus a manager-level pending-actions report before cut-off.

5. A sandwich rule was applied without notice. The employee lost four days for a two-day absence and had never seen the rule. Fix: disclose it at the point of leave application, not after.

6. Late-mark LOP was double-counted. A day already treated as a half day also incremented the late-mark counter that later converted to another half day. Fix: explicit rule precedence.

7. Pro-rata was labelled as LOP. A mid-month joiner's payslip showed 15 LOP days. Fix: separate the two concepts in the payslip template.

8. The month was reopened to fix an error. Payslips, filings and bank files went out of sync. Fix: correct forward via arrears, never backward via edits.

9. Full-month LOP exceeded monthly salary. A fixed-30 divisor applied to 31 absent days. Fix: an explicit cap.

10. Statutory contributions were computed on pre-LOP wages. The employee's contribution base did not match the wage actually paid. Fix: compute on payable wages per each scheme's own wage definition, and get the configuration reviewed.

11. Device downtime became LOP. A biometric outage at one site created LOP for an entire shift. Fix: the system-failure clause, plus a bulk-regularisation tool.

12. Nobody could show the dates. The employee asked "which days?" and the payroll team took three days to answer. Fix: publish LOP dates with the payslip.

A Dispute-Handling Runbook

When an LOP query lands, work it in this order. It resolves most cases in a single exchange.

1. Acknowledge within one working day with a case reference. Do not defend the number before you have checked it.
2. Pull the LOP date list for the employee and share it. Roughly half of all queries end here, because the employee recognises the dates.
3. Pull the attendance record for each disputed date, including raw punch data and its source.
4. Pull the leave ledger — balance at the time of the absence, requests raised, approvals, timestamps.
5. Check for a system incident covering those dates. If one exists, reverse immediately without further debate.
6. Check the rule applied — which threshold, which divisor, which sandwich option — and confirm it matches published policy.
7. Decide and communicate in writing, showing the calculation line by line: LOP-applicable gross, divisor, per-day rate, days, amount.
8. If reversal is due, raise the arrear in the next cycle with a reason code, and tell the employee the exact payslip it will appear on.
9. If the LOP stands, explain the specific rule and point to where it is published. "It is system-generated" is not an explanation and will escalate the matter.
10. Log the root cause. Categorise every case — data gap, manager inaction, policy ambiguity, employee error, system failure. Review the categories quarterly. If manager inaction is a third of your cases, the fix is a manager reminder workflow, not more payroll effort.

Frequently Asked Questions

1. Is LOP a deduction from salary? Conceptually, no. LOP is a reduction in earnings for days on which service was not rendered, whereas a deduction is an amount taken out of wages that were earned. The distinction matters for payslip presentation and for how the treatment is characterised in audits and disputes. Deductions from wages in India are a regulated area, so if you are structuring anything that looks like a penalty rather than a non-earning, take advice first.

2. Which divisor is legally correct — 30 days, calendar days, or working days? There is no single universal answer that applies to every employer and every employee category. What matters operationally is that the divisor is defined in your policy or contract, applied consistently across employees and months, and disclosed to employees. If your employment contracts or standing orders specify a method, that governs. Verify your specific position with your legal or compliance advisor rather than adopting a rule of thumb.

3. Should weekly offs and holidays be counted as LOP? Under most modern policies, no — they are paid days and are not counted unless they fall inside a continuous period of approved unpaid leave. Sandwich rules that count intervening offs for adjacent absences exist and can be adopted, but they need to be written down, disclosed at the point of leave application, and checked for consistency with your contractual and statutory position.

4. Can LOP exceed an employee's monthly salary? It should not, and your system should cap it. The overshoot arises specifically with a fixed-30 divisor in a 31-day month with full-month absence, where 31 x (salary/30) exceeds monthly salary. Configure an explicit cap at the LOP-applicable monthly gross.

5. Does LOP affect statutory contributions and leave accrual? Generally, contributions are computed on the wages actually payable, so reduced wages flow through to the contribution base — but each scheme has its own wage definition, ceilings and edge-case rules, particularly for zero-wage months. Leave accrual policies commonly suspend or reduce accrual for months with substantial unpaid absence, subject to statutory minimums. Both areas need verification against current rules for your establishment rather than a general assumption.

6. How do we handle LOP when someone joins or leaves mid-month? That is pro-rata salary, not LOP. The employee was not in service on the other days, so no absence occurred. Compute pro-rata using the same divisor as your LOP method for consistency, and label it correctly on the payslip. If the person also had unpaid absence during their partial month, that LOP is applied on top of the pro-rata computation and shown as a separate line.

7. What is a reasonable regularisation window? Seven calendar days from the exception, with a hard stop at the monthly attendance cut-off, is a common and workable design. Pair it with manager auto-escalation after three working days, because most unfair LOP comes from approval inaction rather than employee negligence. Publish the cut-off date so nobody is surprised by it.

8. What should we do if LOP was applied wrongly and payroll has already closed? Correct it forward as an arrear in the next cycle rather than reopening the closed period. Reopening invalidates payslips, filings and accounting entries that have already been issued. Raise the arrear as a distinct, labelled earning line referencing the original period, and tell the employee exactly which payslip it will appear on.

Bringing It Together

Loss of pay calculation is one of the few HR processes where a small configuration choice — a divisor, a component flag, a default outcome at freeze — turns directly into money in or out of someone's bank account. That is why the organisations with the fewest LOP disputes are rarely the ones with the most generous policies. They are the ones where the rules were decided before the month started, written where employees can read them, applied by a system rather than by memory, and shown transparently on the payslip.

If you want a short checklist to act on this week: write down your divisor and put it on the payslip; audit every salary component for its LOP flag; publish LOP dates with every payslip; add auto-escalation to regularisation approvals; and add a system-failure clause so an outage never becomes someone's pay cut. Those five changes will remove most of the friction without changing a single entitlement.

The technology part is straightforward once the policy part is settled. An HRMS like CozyHR connects attendance capture, leave balances, regularisation workflows and payroll computation in one system, so the LOP number that reaches the payslip is the same number the employee saw in their portal before cut-off — with the divisor, the per-day rate and the specific dates visible to both sides. That single-source-of-truth property is what actually prevents disputes; the rest is arithmetic.

If your attendance data currently lives in one place, leave in another, and payroll in a spreadsheet that gets rebuilt every month, that gap is where your LOP errors are coming from. Closing it is usually a one-month project. You can explore CozyHR to see how attendance, leave and payroll fit together in a single workflow — and run a parallel month against your existing process before you switch anything over.

---

This article is intended as general operational guidance for HR and payroll teams. All figures are illustrative and do not represent statutory entitlements or prescribed rates. Statutory requirements relating to wages, deductions, leave and social security contributions in India vary by legislation, state, establishment type and contract, and change over time. Verify all statutory and contractual matters with official sources and with your own legal or compliance advisor before implementing any policy described here.