Loss of Pay in Payroll: LOP Calculation and Controls

Loss of Pay in Payroll: LOP Calculation and Controls

Every payroll team in India has had this conversation. An employee opens their payslip, sees a number smaller than last month, and walks over to HR asking why. Nine times out of ten the answer is a loss of pay calculation — a deduction triggered by days the employee was absent without an approved, paid leave to cover them. The arithmetic is usually simple. The disagreement almost never is, because the employee and the payroll system were working from different assumptions about how many days a month has, which components of salary get reduced, and whether that Saturday in the middle of the absence should have counted.

Loss of Pay, or LOP, is the point where attendance data physically becomes money. Biometric punches, leave balances, regularisation requests and manager approvals all flow into one field on a payslip, and if any upstream step is sloppy, the error shows up as a rupee figure in someone's bank account. For small and mid-sized businesses in India, this is the single most common source of salary disputes — more common than increment confusion, more common than reimbursement delays, and considerably harder to explain after the fact because the deduction has already happened.

This guide walks through LOP end to end: what triggers it, the three per-day-salary conventions Indian employers actually use and how each produces a different number, which salary components LOP should and should not touch, how to reverse it when a leave is approved late, how it interacts with statutory deductions, and — most importantly — the operational controls that stop LOP disputes from happening in the first place. The numbers in every example are illustrative and clearly labelled. The statutory guidance is deliberately general, because rates, ceilings and thresholds change and you should verify the current position with the relevant authority or your compliance advisor before you configure anything.

What Loss of Pay Actually Means

Loss of Pay is a payroll treatment, not a punishment. It means the employee did not render service on a given day and does not have an entitlement — a paid leave balance, a holiday, a weekly off, a compensatory off — that covers the absence. Because salary in India is generally paid for the month rather than by the hour, the employer reduces the monthly salary by a proportionate amount for the uncovered days.

The distinction that matters is between unpaid absence and paid leave. Paid leave is a benefit the employee has already earned or been granted; taking it does not reduce salary. LOP applies only after that entitlement runs out, was never granted, or was never applied for.

A second distinction matters just as much: LOP is not a fine, and it is not a disciplinary penalty. Deductions from wages in India are governed by wage-payment law, which distinguishes between deductions for absence from duty and deductions of a penal nature. Absence-based reduction is a recognised category; arbitrary fines are treated very differently and come with their own conditions. Keep the two separate in your policy, your payroll configuration and your payslip labels.

LOP versus "leave without pay"

Most HRMS products use these terms interchangeably, and in practice they describe the same financial outcome. The useful difference is intent:

• Leave Without Pay (LWP) is usually applied for and approved in advance. The employee knows salary will be reduced and the manager has agreed to the absence.
• Loss of Pay (LOP) is often derived by the system — an absence with no matching approved leave, discovered during payroll processing.

Approved LWP is a planned event. Derived LOP is an exception that needs investigation before it turns into a deduction. Treating them as the same thing operationally is how companies end up deducting salary from someone who filed leave correctly but whose manager forgot to click approve.

When LOP Applies: The Common Triggers

Your policy should enumerate the triggers explicitly. Vague policies produce inconsistent payroll, and inconsistent payroll produces disputes. These are the situations that come up repeatedly in Indian SMBs.

Unapproved or unrecorded absence. The employee did not report to work and there is no leave application, no regularisation request, and no approval on record. This is the default LOP case.

Leave balance exhausted. The employee applied for leave correctly, the manager approved it, but the balance in that leave type had already run out. Depending on your configuration, the system either blocks the application or converts the excess days to LOP. Converting silently is a bad idea — the employee should see the conversion at the time of application, not at the time of payslip.

Unpaid leave and sabbaticals. Extended personal leave, study breaks and sabbaticals are typically unpaid by design. These are the cleanest LOP cases because everyone agreed in advance. Document the start and end dates and whether benefits continue during the period.

Late joining. An employee who joins mid-month is paid only for the days from the date of joining. Some payroll systems model this as LOP for the pre-joining days; others compute a pro-rata salary directly. The financial outcome should be identical, but the payslip presentation differs and employees find the LOP framing confusing. Pro-rata is usually the clearer label.

Mid-month exit. The mirror image. Salary is paid up to the last working day, and the remaining days of the month are either shown as LOP or handled as pro-rata in the full-and-final settlement. Notice-period shortfalls are a separate recovery and should never be merged into the LOP line.

Suspension pending inquiry. Suspension is not the same as absence. In many cases a suspended employee is paid a subsistence allowance rather than full salary, and the treatment depends on your standing orders, employment contract and the applicable rules. Do not configure suspension as ordinary LOP without checking the position for your establishment — take advice on this one.

Strikes, lockouts and collective stoppages. Wage treatment during industrial action is a legally sensitive area that depends on the nature of the stoppage, whether it was legal, and which establishment-specific rules apply. The general principle of "no work, no pay" is often invoked, but the exceptions and procedural requirements are real. Handle these case by case with legal input rather than through a payroll switch.

Partial-day shortfalls. Half-day absence, short hours against a minimum-hours policy, or a missed punch that cannot be regularised. These should be governed by explicit rules, not manager discretion, because discretion is where inconsistency creeps in.

How LOP Is Calculated: The Core Formula

Every LOP calculation, regardless of convention, reduces to the same shape:

LOP deduction = Per-day salary × Number of LOP days

And per-day salary is:

Per-day salary = LOP base salary ÷ Divisor days in the month

All the complexity lives in two choices: what goes into the LOP base (which components are reduced) and what you use as the divisor (calendar days, a fixed 30, or working days). Two employers can deduct wildly different amounts for the same single day of absence at the same CTC purely because they answered these two questions differently.

Both answers must be written into policy, configured once in your payroll system, applied uniformly across the organisation, and disclosed to employees. Changing the divisor mid-year without communication is one of the fastest ways to generate a wave of tickets.

The Three Per-Day-Salary Conventions

Indian employers overwhelmingly use one of three conventions. None of them is universally "correct." Each is defensible, each has a characteristic failure mode, and the important thing is to pick one deliberately and stick to it.

Convention 1: Calendar days in the month

The divisor is the actual number of days in that specific month — 28 or 29 in February, 30 in April, 31 in March. Every day of the month, including weekly offs and holidays, carries an equal share of salary.

This is arguably the most philosophically consistent approach: monthly salary covers the whole month, so each of the month's days is worth the same fraction of it. It is also the most common configuration in Indian payroll software.

The characteristic quirk: the same absence costs more in February than in March. One LOP day in a 28-day February costs 1/28th of salary; the same day in a 31-day March costs 1/31st. Employees notice this and it feels arbitrary to them even though it is internally consistent.

Convention 2: Fixed 30 days

The divisor is always 30, regardless of the actual length of the month. Per-day salary is constant across the year, which makes it easy to explain, easy to verify mentally and easy to build into offer letters and cost models.

The characteristic quirk: in a 31-day month, 31 days of full-month salary are paid using a 30-day divisor, so an employee absent for the entire month on LOP would theoretically end up with a small negative balance. In February, the reverse. Most systems handle this by treating full-month LOP as a special case and zeroing the net rather than letting the arithmetic run to a negative. You must configure that guardrail explicitly.

Convention 3: Working days only

The divisor is the number of days the employee was actually expected to work — calendar days minus weekly offs minus declared holidays. Per-day salary is higher because the same monthly salary is spread across fewer days.

This convention appeals to intuition ("I was absent on a working day, so deduct a working day") but it produces the largest deduction per day of the three, and the divisor changes every month with the holiday calendar. It also forces you to answer the sandwich-leave question head on, because weekly offs are excluded from the divisor by definition.

Side-by-side comparison (illustrative numbers)

Assume a monthly LOP base of Rs 60,000 and 2 LOP days. All figures below are illustrative and rounded to the nearest rupee.

Three observations worth internalising:

1. The spread between the cheapest and most expensive convention for the same two days is over Rs 1,000 in February on a Rs 60,000 base. Scale that across a workforce and it is a real number.
2. Fixed 30 is the only convention where per-day salary never moves. That stability is its main selling point.
3. In a 30-day month, calendar-days and fixed-30 converge exactly. This is why configuration errors often go undetected in April, June, September and November and then explode in February.

Choosing a convention

If you are setting this up for the first time and have no strong reason otherwise, calendar days or fixed 30 will give you fewer arguments than working days. Whichever you choose, write it into the employment contract or the payroll policy document, state it on the payslip or in an employee-facing FAQ, and do not change it mid financial year.

Which Salary Components LOP Should Touch

Choosing a divisor is only half the decision. The other half is deciding what sits in the numerator — the LOP base. This is where employers differ most and where the money is.

The gross-salary approach

Every earning component that forms part of the monthly fixed salary is reduced proportionately: basic, dearness allowance (where applicable), house rent allowance, conveyance, special allowance, and any other fixed monthly allowance.

The logic is straightforward: the entire monthly salary is consideration for a month of service, so all of it scales with the days served. This is the most widely used approach in Indian SMB payroll and the easiest to defend when an employee asks why HRA also went down.

The basic-only approach

Only basic (and DA, where it applies) is reduced; allowances stay whole. Some employers do this because allowances are framed as facility-linked rather than attendance-linked.

It produces a smaller deduction, which employees like, but it creates a strange result: an employee on LOP for most of the month still draws the full allowance stack. It also distorts the relationship between components. Unless you have a specific contractual or structural reason, gross-proportionate is cleaner.

Component-by-component guidance

The one rule worth writing in bold in your own policy: reimbursements are never subject to LOP. If an employee spent money on a claimable expense and submitted a bill, the absence has nothing to do with it. Reducing reimbursements pro-rata is a configuration mistake that looks, to the employee, like the company clawing back their own money.

The four labour codes and why the base is moving

India's four labour codes took effect in late 2025, and the consolidated definition of "wages" they introduced has pushed many employers to revisit how salary is split between basic and allowances. Where the structure changes, the base on which LOP is calculated changes with it — sometimes materially, if basic moves as a share of gross.

Two practical implications. First, if you are restructuring components, recheck your LOP configuration at the same time rather than assuming it will carry over unchanged. Second, if you use the basic-only approach, a structural shift toward a larger basic will increase LOP deductions for the same number of absent days, and employees will notice without understanding why.

None of this changes the arithmetic in this guide; it changes the numbers you feed into it. Verify the current requirements and any state-specific position with the relevant authority or your compliance advisor before you re-cut your salary structures.

Worked Examples (Illustrative Numbers)

These examples use invented figures purely to show mechanics. Do not treat any number here as a rate, threshold or benchmark.

Example 1: Straightforward two-day LOP

An employee has a monthly gross of Rs 45,000, structured as basic Rs 18,000, HRA Rs 9,000, conveyance Rs 3,000 and special allowance Rs 15,000. The employer uses the calendar-days convention. The month has 30 days. The employee has 2 LOP days.

• Per-day salary = 45,000 ÷ 30 = Rs 1,500
• LOP deduction = 1,500 × 2 = Rs 3,000
• LOP-adjusted gross = 45,000 − 3,000 = Rs 42,000

Under the gross approach, each component scales by 28/30:

Statutory deductions are then computed on the LOP-adjusted figures, not the full-month figures.

Example 2: The same absence in February

Same employee, same 2 LOP days, but the month is a 28-day February.

• Calendar-days convention: 45,000 ÷ 28 = Rs 1,607 per day → deduction Rs 3,214
• Fixed-30 convention: 45,000 ÷ 30 = Rs 1,500 per day → deduction Rs 3,000
• Working-days convention (24 working days): 45,000 ÷ 24 = Rs 1,875 per day → deduction Rs 3,750

A difference of Rs 750 between the gentlest and harshest convention for an identical absence. This is exactly the gap that generates tickets when employees compare notes with friends at other companies.

Example 3: Half-day LOP plus a full day

An employee with a Rs 72,000 monthly gross, fixed-30 convention, has one full LOP day and one half-day LOP in a 31-day month.

• Per-day salary = 72,000 ÷ 30 = Rs 2,400
• LOP days = 1.0 + 0.5 = 1.5
• Deduction = 2,400 × 1.5 = Rs 3,600

Half-days must be supported as a first-class quantity in your LOP register. Systems that only store whole days force payroll into manual adjustments, and manual adjustments are where errors live.

Example 4: Mid-month joiner

An employee joins on the 18th of a 30-day month at a monthly gross of Rs 50,000, calendar-days convention.

• Days paid = 30 − 17 = 13
• Per-day salary = 50,000 ÷ 30 = Rs 1,667
• Salary payable = 1,667 × 13 = Rs 21,667

Show this on the payslip as "Days paid: 13 of 30" with a pro-rata label rather than "LOP: 17 days." Both produce the same number; only one causes a panicked email on day one of employment.

Example 5: LOP reversal in the following month

The same employee from Example 1 had 2 LOP days deducted in the month. In the following cycle, the manager approves a backdated leave application covering both days. The employee's leave balance is debited by 2 days and payroll processes an LOP reversal of Rs 3,000 as a separate earning line labelled "LOP Reversal — prior month."

Statutory contributions for the reversal month are computed on the higher total, and the payslip shows both the reversal amount and the period it relates to. Do not hide the reversal inside the regular basic line — an unexplained increase is nearly as confusing as an unexplained decrease.

LOP Reversal and LOP Arrears

Late approvals are a fact of life. A manager is travelling, an employee was hospitalised and filed leave after returning, or a regularisation request sat unactioned past the cut-off. When the approval finally lands, the deduction must be undone.

The rule: never edit a locked payroll period. Once a month is processed, paid and its statutory filings are prepared, going back and rewriting it corrupts your audit trail and creates reconciliation nightmares. Process the correction forward as an arrear line in the next open cycle.

A workable reversal process:

1. Capture the trigger. The late approval, medical certificate, or corrected attendance record is recorded with a date and an approver identity.
2. Verify the leave balance. Converting LOP to paid leave consumes balance. If the employee has none, the reversal is not valid and the LOP stands — this is the check teams most often skip.
3. Compute the reversal at the original month's per-day rate. If the LOP was taken in a 28-day February at Rs 1,607 per day, reverse at Rs 1,607 per day — not at the current month's rate. Mismatched rates produce small, persistent, maddening discrepancies.
4. Post as a distinct earning line labelled with the originating month.
5. Adjust the leave ledger in the same transaction so balances and payroll stay consistent.
6. Recompute statutory contributions on the revised total for the payment month.
7. Notify the employee with a short note explaining what was reversed and why.

Backdating limits

Allow reversals within a defined window — one or two payroll cycles is typical — and require a higher level of approval beyond that. Without a limit, you will receive a request in December to reverse an LOP from April, and by then the leave balance, the salary structure and the statutory filings have all moved.

Your policy should state the window explicitly, along with who can approve exceptions.

LOP and Statutory Deductions

LOP reduces wages, and statutory deductions are computed on wages, so LOP flows through to everything downstream. Keep this section general and verify current rules — thresholds, rates and ceilings change, and state-level items vary.

Provident fund. PF contributions are computed on PF wages for the month. When LOP reduces those wages, contributions reduce correspondingly. Where an employee's wages fall below a threshold because of a long absence, or where the wages cross a ceiling in one month but not another, the treatment needs care. Some employers have internal rules about maintaining contributions during extended unpaid leave. Check the current rules and your own practice with your PF advisor rather than assuming your payroll software's default is right for you.

ESI. Where an establishment and employee are covered, contributions are computed on wages paid for the period. LOP reduces the wage base. Eligibility itself depends on wage thresholds that are prescribed and revised from time to time, and a month with heavy LOP can push an employee's wages around in ways that affect coverage determination within a contribution period. Verify the current position before configuring automatic behaviour.

Professional tax. PT is a state subject. Rates, slabs, frequency and the treatment of part-month salary all vary by state, and some states have specific rules about months with reduced wages. Do not apply one state's logic across a multi-state workforce. Check each state's current schedule.

Income tax (TDS). TDS is generally computed on projected annual income and spread across remaining months. A month with significant LOP reduces actual income against the projection, so the system should re-project rather than mechanically deducting the previously computed monthly figure. Good payroll software re-runs the projection each cycle; if yours does not, employees end up over-deducted mid-year and chasing refunds later.

A practical control: after any month with unusually high aggregate LOP, review the TDS re-projection before releasing payslips. A single re-projection check catches more employee complaints than any other single review step.

Labour welfare fund and other state levies. Where applicable, these follow their own periodicity and rules. Treat them like PT — state-specific, verified, not assumed.

General principle. Statutory deductions follow reduced wages; they are not separately "reduced for LOP." Configure the system so that LOP adjusts the wage base and everything downstream recomputes from that base. Hard-coded statutory amounts that do not respond to a changed wage base are a common and expensive misconfiguration.

Edge Cases That Break LOP Calculations

Two situations cause more payroll rework than any other: an LOP month heavy enough to wipe out net pay, and absences that are smaller than a full day. Both need explicit rules rather than case-by-case judgement.

Negative LOP and protecting net pay

A heavy LOP month can drive computed net pay to zero or below — especially when fixed deductions (loan EMIs, salary advances, insurance premiums, canteen recoveries) continue against a reduced gross.

Negative net pay is not merely an aesthetic problem. It is an operational failure: banks reject negative transactions, the payslip is incomprehensible, and the recovery has to be tracked manually thereafter.

Build these guardrails:

• Floor the net at zero. Never issue a payslip with a negative net. Where deductions exceed earnings, cap them and carry the excess forward.
• Create a "carry-forward recovery" line. The uncollected portion should appear as a visible balance the employee can see, recovered in subsequent months per a stated schedule.
• Define a deduction priority order. Statutory deductions first, then employer-mandated recoveries, then optional ones. Write the order into policy so it is applied consistently.
• Flag high-LOP cases before processing. Any employee whose LOP days exceed a set threshold — say more than a third of the month — should appear on an exception report for manual review before payroll runs.
• Suspend voluntary deductions during long absence. For sabbaticals and extended unpaid leave, agree in advance whether voluntary items pause and how arrears will be recovered on return.
• Check the full-month LOP case under a fixed-30 divisor. In a 31-day month this is the classic arithmetic trap. Explicitly configure full-month absence to produce a zero net rather than letting the formula run.

For long planned absences, have the conversation before the leave starts. An employee who understands that four months of unpaid sabbatical means four months of zero salary and a deferred EMI recovery will plan accordingly. One who discovers it from a payslip will not.

Half-days, partial days and short hours

Full-day LOP is easy. Fractional LOP is where policies get vague and payroll gets inconsistent.

Your policy needs written answers to these:

• What defines a half day? Hours worked, or presence during a defined core window? Half-day thresholds based on hours are easier to automate and harder to argue with.
• Is there a grace period for late arrival? State the number of minutes and how many instances per month are tolerated.
• What happens on the fourth late arrival? Some employers convert a defined number of late marks into a half-day LOP. If you do this, say so explicitly, and make the running count visible to the employee in their self-service view.
• Does early departure count? Treat symmetrically with late arrival unless there is a reason not to.
• What about a missed punch on a day the employee clearly worked? This must be regularisable, and the regularisation window must be long enough to be realistic.
• How are half-days handled for employees on flexible or hybrid schedules? Presence-based rules do not translate to output-based roles. Either exempt those roles explicitly or define an alternative standard.
• Do you allow quarter-day granularity? Most SMBs should not. It multiplies edge cases for very little money.

Then state the smallest unit your payroll supports. If your system handles 0.5 but not 0.25, do not write a policy that implies quarter days exist.

LOP, Weekly Offs and the Sandwich Rule

This is the most argued-about topic in Indian leave administration, and the cause is almost always a policy that never addressed it.

The scenario: an employee is absent on Friday and the following Monday, with Saturday and Sunday as weekly offs. Is the LOP two days or four?

The "sandwich" treatment counts the intervening weekly offs as LOP, producing four days. The reasoning is that the employee was continuously absent across the whole span.

The "actual days" treatment counts only the scheduled working days, producing two days. The reasoning is that the employee was never expected to work on the weekly off, so nothing was lost on those days.

Both approaches exist in Indian workplaces. Neither is inherently wrong as a matter of general practice, but a sandwich rule applied without clear prior communication feels punitive to employees and reliably produces escalations.

How to handle it

1. State the rule explicitly in the leave policy. Use exact language: "Weekly offs and declared holidays falling between two LOP days will / will not be counted as LOP."
2. Apply it uniformly. Selective application by manager or department is the fastest route to a fairness complaint.
3. Distinguish paid leave from LOP. Many employers apply sandwich logic only to unpaid absence, not to approved paid leave. If that is your rule, write it as a separate clause.
4. Show the computation at application time. When an employee applies for leave spanning a weekend, the system should display exactly how many days will be charged before they submit.
5. Consider a leading/trailing rule. A common middle path: weekly offs are counted only when the absence is unapproved on both the preceding and succeeding working days. Approved absences do not sandwich.
6. Remember the interaction with your divisor. Under a working-days divisor, weekly offs are already excluded from the denominator, which changes the fairness calculus of also counting them as LOP days. Under a calendar-days divisor, sandwiching adds days at a lower per-day rate. Think through the combination rather than setting each independently.

Holidays inside an absence span

Declared holidays raise the same question and deserve the same explicit answer. If an employee is absent on the working days either side of a national holiday, does the holiday become LOP?

The prevailing approach in most SMBs is to not convert declared holidays to LOP, on the basis that the holiday is an entitlement independent of attendance. But once again — write it down. Silence is where disputes grow.

Illustrative comparison

Assume Rs 60,000 monthly gross, calendar-days convention, a 30-day month. Employee absent Friday and Monday with Saturday and Sunday as weekly offs.

The spread between the top and bottom row is four times the deduction for what an employee experiences as the same two days off. This is why the sandwich clause deserves its own paragraph in your policy, not a footnote.

The Attendance-to-Payroll Data Flow

An accurate loss of pay calculation is downstream of a clean data pipeline. If the pipeline leaks, payroll inherits the leak. Here is the flow that works, stage by stage.

Stage 1: Capture

Attendance enters the system through biometric devices, geofenced mobile check-ins, web punches, access-card readers, or manual muster entries for field staff. Each capture method has a characteristic failure:

• Biometric fails on device downtime, network drops and unreadable fingerprints.
• Geofence fails on GPS drift, low battery and legitimate off-site work.
• Web punch fails on shared devices and forgotten logouts.
• Manual muster fails on transcription delay and, occasionally, on optimism.

Design for failure rather than pretending it will not happen. Every capture method needs a documented fallback, and the fallback must produce a record with the same audit fields as a normal punch.

Stage 2: Raw-to-daily conversion

Raw punches become a daily attendance status: Present, Absent, Half Day, Weekly Off, Holiday, On Leave, On Duty, or Exception. This conversion applies shift definitions, grace periods, minimum-hours rules and break rules.

This is the stage where configuration errors hide. An employee on a night shift whose punches straddle midnight, or a shift roster that was updated after the fact, can produce an Absent where a Present belongs. Review night-shift and rotational-shift conversions separately each cycle.

Stage 3: Exception surfacing

Every day that is not cleanly Present or cleanly accounted for should be surfaced to the employee and the manager daily, not at month end. An employee who sees "missed punch on the 4th" on the 5th can fix it in seconds. The same employee on the 28th has forgotten what happened.

Daily exception visibility is the single highest-leverage control in this entire article. Most LOP disputes are not disagreements about policy — they are late discovery of a data problem.

Stage 4: Regularisation

The employee submits a correction: I was present, here is why the punch is missing; I was on client site; the device was down. The regularisation request carries a reason code, optional evidence and a timestamp.

Define a regularisation window — commonly a few days from the date in question, closing before the payroll cut-off. Requests outside the window need a higher approval level. Without a window, regularisations arrive after payroll has run and you are back in reversal territory.

Stage 5: Manager approval

Managers approve or reject regularisations and pending leave applications. Approval must be an explicit act with an identity and a timestamp attached.

Two controls matter here. First, auto-escalation: if a manager does not act within a defined period, the request escalates to their manager or to HR, so no employee loses pay because someone was on vacation. Second, rejection reasons: a rejection with no reason generates an immediate dispute. Require a reason code.

Stage 6: Payroll lock

At the cut-off, attendance for the period is frozen. No further edits are possible without a formal exception process. The lock is what makes the month auditable — and what makes reversal-as-arrears necessary instead of optional.

Stage 7: LOP register generation

The system generates an LOP register: one row per employee per LOP day (or half day), with date, reason code, source status, approval trail and the computed deduction. This register is the artifact HR uses to answer questions, the artifact finance uses to reconcile, and the artifact an auditor asks for.

If your process cannot produce this register in one click, that is the gap to close first.

Stage 8: Payroll computation and payslip

LOP days feed the per-day-salary formula, deductions are applied to the configured components, statutory items recompute on the revised base, and the payslip renders with LOP shown transparently.

A Workable Payroll Cut-Off Calendar

Cut-off discipline prevents most LOP problems. Below is an illustrative monthly rhythm for a company paying salary at the end of the month. Adapt the dates to your own cycle — the sequence matters more than the specific numbers.

Two notes. First, verify statutory remittance and filing due dates with the relevant authority each year — they are prescribed and can change, and the last thing you want is a calendar built on a remembered date. Second, publish this calendar to all employees at the start of the year. A cut-off that only payroll knows about is not a control; it is a trap.

Handling the gap between cut-off and month end

Absences occurring between the cut-off (say the 21st) and month end cannot be processed in the current cycle. You have two options:

• Arrear method: pay the full month, process LOP for the tail days in the following month as a deduction. Simpler, and the most common approach.
• Shifted period method: define the attendance period as, for example, the 21st of the previous month to the 20th of the current month. LOP is always current within that shifted window.

Both work. The shifted period is cleaner for high-absence workforces; the arrear method is easier to explain. Pick one and document it, because employees will eventually ask why a deduction for the 29th appeared on the following month's payslip.

The LOP Reconciliation Checklist

Run this before every payroll release. It takes under an hour once it is routine and prevents the overwhelming majority of post-payroll corrections.

1. Headcount tie-out. Does the number of employees in the attendance system match the number in payroll? Investigate every difference — a missing employee is an unpaid employee.
2. New joiners. Every employee with a joining date in the period has correct days-paid and is flagged pro-rata, not LOP.
3. Exits. Every exit has correct days-paid, and notice recoveries are on their own line, not merged with LOP.
4. Total LOP days. Compare aggregate LOP days to the same month last year and to last month. A sudden spike usually means a device outage or a configuration change, not a sudden outbreak of absenteeism.
5. Zero-LOP employees. Confirm the list of employees with no LOP is plausible. An entire department at zero can mean their attendance feed failed.
6. High-LOP exceptions. Every employee above your threshold (say more than a third of the month) has been individually reviewed and the reason is documented.
7. Unapproved pending items. No leave application or regularisation for the period remains in pending status at lock. Pending means someone forgot, and forgetting costs an employee money.
8. Sandwich application. Spot-check a sample of absences spanning weekly offs to confirm the policy rule was applied as configured.
9. Holiday spans. Spot-check absences spanning a declared holiday for the same reason.
10. Half-day totals. Confirm fractional LOP days are stored as fractions and not rounded to whole days anywhere in the chain.
11. Reversals and arrears. Every LOP reversal has a leave-balance debit, an original-month reference, and the original month's per-day rate.
12. Component application. Verify LOP touched the components your policy says it should — and did not touch reimbursements.
13. Statutory recomputation. Confirm PF, ESI, PT and TDS recomputed on LOP-adjusted wages rather than full-month wages.
14. Negative net check. No employee has a computed net at or below zero without an approved carry-forward recovery entry.
15. Variance review. Any employee whose net pay moved more than a set percentage from the prior month appears on a variance report with an explanation.
16. Payslip render check. Open three payslips at random and read them as an employee would. If you cannot explain the LOP line in one sentence, neither can they.

Assign each item an owner and require sign-off. A checklist nobody signs is a checklist nobody runs.

Communicating LOP on the Payslip

A well-built payslip eliminates most LOP tickets before they are raised. A poorly built one generates them.

Show the days. Every payslip should carry a days summary: total days in the period, days paid, LOP days, leave days, weekly offs and holidays. When these add up visibly, the employee can verify the deduction themselves.

Show the per-day rate. State the convention and the resulting per-day figure. "Per-day salary (based on 30 calendar days): Rs 1,500" removes the entire "how did you get that number" category of question.

Show the deduction separately. LOP should be its own line, not netted silently into basic. If components are reduced proportionately, show the reduced component values alongside the full-month values.

Label reversals clearly. "LOP Reversal — February" is understandable. "Other Earnings" is not.

Link to the LOP detail. In self-service, the LOP line should be clickable, opening a date-wise view: which dates were LOP, what the source status was, whether a leave application existed, and who approved or rejected what.

Include a dispute link. A visible "Raise a query on this payslip" action routes the question into a tracked workflow instead of a WhatsApp message to a manager at 11pm.

An illustrative payslip days block

An employee who sees this block does not need to ask anyone anything. That is the standard to aim for.

Disputes and the Correction Workflow

Even with good controls, disputes happen. What separates a calm HR function from a chaotic one is having a defined path rather than an improvised one.

1. Intake. The employee raises a query through self-service, with the payslip and the disputed dates attached automatically. Every query gets a ticket ID.
2. Acknowledgement. Auto-acknowledge with a stated resolution timeline. Silence is what escalates disputes, not disagreement.
3. Triage. HR Ops classifies: data issue (missed punch, device failure), process issue (approval not actioned, regularisation missed), policy issue (employee disagrees with the sandwich rule or the divisor), or genuinely correct deduction.
4. Evidence review. Pull the LOP register row, the raw punch data, the leave ledger, and the approval trail for the disputed dates. Decide on the record, not on recollection.
5. Decision and explanation. Communicate in writing with the specific dates, the rule applied, and the arithmetic. "Policy says so" is not an explanation.
6. Correction, if warranted. Process as a reversal in the next open cycle following the reversal process above. Never edit a locked period.
7. Closure and confirmation. Confirm with the employee that the correction appeared on the subsequent payslip. An uncommunicated fix is, from the employee's side, no fix at all.
8. Root cause. Tag the ticket with a cause code and review causes monthly. If three tickets in a row trace to one biometric device, the fix is the device, not the tickets.

Turning disputes into process improvements

Track a small set of metrics: LOP disputes per hundred employees per month, share of disputes upheld, average resolution time, and the top three cause codes. A high upheld rate means your upstream data is wrong. A high dispute rate with a low upheld rate means your communication is wrong. Both are fixable, and the fixes are different.

Audit Trail and Record Keeping

LOP decisions affect wages, so the underlying records need to survive scrutiny — from an internal audit, a due-diligence exercise, an employee claim, or an inspection.

What to retain, at minimum:

• Raw attendance capture data with device or source identifiers and timestamps
• Daily attendance status per employee with the shift and rules applied
• Leave applications with submission, approval and rejection timestamps and identities
• Regularisation requests with reason codes, evidence and outcomes
• The LOP register for each payroll period
• The payroll register and published payslips
• Policy versions with effective dates, so you can show which rule applied in a given month
• Approval logs for any exception or out-of-window correction

Key principles:

• Immutability. Historical records should not be silently editable. Corrections create new records that reference the original.
• Identity on every change. Who did what, when, and why. "System" is not an acceptable actor for an approval.
• Policy versioning. When you change your divisor or your sandwich rule, keep the old version with its date range. Answering a query about a deduction from eighteen months ago requires knowing what the rule was then.
• Retention periods. Wage and attendance records have prescribed retention requirements under applicable law. Verify the current requirements for your establishment type and state — do not rely on a default in your software.
• Access control. Salary and attendance data are sensitive. Restrict access by role, log access to salary registers, and avoid circulating payroll spreadsheets over email.

A practical test. Pick a random employee and a random past month. Can you produce, within ten minutes, the dates on which LOP was applied, the raw attendance evidence, the approval trail, the policy version in force, and the exact computation? If yes, your audit trail is adequate. If no, you know what to build.

A Policy Template Outline for Your LOP Clause

Use this as a skeleton for the LOP section of your leave and attendance policy. Fill each item with your own decision rather than copying someone else's.

1. Purpose and scope. What the clause covers, which employee categories it applies to, and which are excluded (for example, employees on output-based arrangements).

2. Definitions. Loss of Pay, Leave Without Pay, working day, weekly off, declared holiday, half day, regularisation, payroll cut-off, attendance period.

3. When LOP applies. The enumerated trigger list — unapproved absence, exhausted balance, approved unpaid leave, sabbatical, late joining, mid-month exit, unregularised missed punches, and any others specific to your business.

4. When LOP does not apply. Approved paid leave, weekly offs (subject to the sandwich clause), declared holidays, compensatory offs, on-duty and travel days, and any statutorily protected leave your establishment provides.

5. Per-day salary convention. State the divisor explicitly — calendar days, fixed 30, or working days — with a worked example.

6. Components affected. List which earnings are reduced and which are not. Name reimbursements as excluded.

7. Half-day and partial-day rules. Thresholds, grace periods, late-mark aggregation, and the smallest unit supported.

8. Sandwich clause. Explicit language on weekly offs and holidays falling within an absence span, including whether the rule differs for approved versus unapproved absence.

9. Regularisation. Window length, permitted reasons, evidence requirements, approval levels, and what happens to out-of-window requests.

10. Payroll cut-off. The attendance period, the cut-off date, and the treatment of absences occurring after cut-off.

11. Reversal and arrears. Conditions for reversal, the backdating window, the rate used, approval requirements, and how reversals appear on the payslip.

12. Negative net pay. The deduction priority order, the zero floor, and how carry-forward recoveries are scheduled and communicated.

13. Extended unpaid absence. Treatment of benefits, voluntary deductions and statutory contributions during sabbaticals and long leave, with a pointer to verify current rules.

14. Disputes. How to raise a query, the resolution timeline, the escalation path, and the evidence that will be considered.

15. Records and access. What is retained, for how long, and who can see it.

16. Version history. Effective dates for each version of the clause.

Circulate the policy at induction, republish it whenever it changes, and require an acknowledgement. A policy nobody has read is indistinguishable from no policy at all when a dispute reaches escalation.

Common LOP Mistakes in Indian SMBs

A short list of the patterns that recur, drawn from how these processes typically break:

• Applying LOP to reimbursements. The most common configuration error and the most resented one.
• Using different divisors for LOP and for arrears. Produces small mismatches that compound over time.
• Silent conversion of excess leave to LOP. The employee finds out from the payslip.
• No daily exception visibility. Everything surfaces at month end when it is too late to fix cheaply.
• Unwritten sandwich rules applied inconsistently. Guarantees a fairness complaint eventually.
• Editing locked payroll periods. Destroys the audit trail and breaks statutory reconciliation.
• Hard-coded statutory deductions that ignore the reduced wage base. Under- or over-deducts, and both are problems.
• Manual LOP registers in spreadsheets. No approval trail, no immutability, and a single wrong cell reference away from paying someone incorrectly.
• No auto-escalation on pending approvals. Employees lose pay because a manager was travelling.
• Treating full-month absence as a formula edge case rather than a configured rule. Especially under a fixed-30 divisor in a 31-day month.
• Merging notice-period recovery into the LOP line. Two different things with two different justifications; keep them separate.
• Changing the convention mid-year without notice. Legally awkward and organisationally expensive.

Frequently Asked Questions

What is the standard formula for loss of pay calculation in India?

The formula is per-day salary multiplied by the number of LOP days, where per-day salary is the LOP base salary divided by a divisor. There is no single standard divisor prescribed for all employers; the common conventions are calendar days in the month, a fixed 30 days, and working days only. What matters is that your organisation picks one convention, states it in policy, applies it uniformly, and discloses it to employees.

Should LOP be calculated on gross salary or only on basic?

Most Indian employers reduce all fixed monthly earnings proportionately — the gross approach — because the whole monthly salary is consideration for a month of service. Some reduce only basic and DA. The gross approach is more common and easier to defend. Whichever you use, reimbursements should be excluded, and the choice should be written into your policy rather than left to payroll's discretion.

Do weekly offs and holidays count as LOP days?

That depends entirely on your sandwich-leave policy. Some employers count weekly offs and holidays that fall between two days of unapproved absence; others count only scheduled working days. Both approaches exist in Indian workplaces. The important thing is that the rule is stated explicitly in your leave policy, applied consistently to everyone, and shown to the employee at the time they apply for leave rather than discovered on the payslip.

How do I reverse an LOP deduction when leave is approved late?

Do not reopen the closed payroll period. Instead, process a reversal in the next open cycle as a clearly labelled earning line referencing the original month. Verify the employee has leave balance to consume, compute the reversal at the original month's per-day rate rather than the current month's, debit the leave ledger in the same transaction, and let statutory contributions recompute on the revised total for the payment month.

Does LOP affect PF, ESI and professional tax?

Yes, indirectly. These are computed on wages, and LOP reduces wages, so contributions reduce correspondingly. The specifics — thresholds, ceilings, coverage rules and state-level professional tax schedules — are prescribed and revised from time to time, and professional tax in particular varies by state. Configure your system so that LOP adjusts the wage base and everything downstream recomputes, and verify the current rules with the relevant authority or your compliance advisor.

Can net salary go negative because of LOP?

Arithmetically it can, when fixed deductions such as loan EMIs continue against a heavily reduced gross. Operationally it should never be allowed to. Floor the net at zero, cap deductions, and carry the uncollected balance forward as a visible recovery line with a stated schedule. Flag employees above a defined LOP threshold for manual review before payroll runs, and have the conversation with the employee before a long unpaid absence begins.

How do the four labour codes change LOP calculation?

They do not change the arithmetic. What they change is the inputs. The consolidated wage definition introduced by the codes, which took effect in late 2025, has prompted many employers to restructure the split between basic and allowances, and that shifts the base on which LOP is computed — particularly for employers using a basic-only approach. If you are revising salary structures, revisit your LOP configuration at the same time and verify the current requirements, including any state-specific position, with the relevant authority.

Conclusion

Loss of pay calculation looks like arithmetic and behaves like governance. The formula fits on one line, but getting the right number onto the right payslip depends on a dozen upstream decisions: which divisor you use, which components you touch, how quickly exceptions surface, whether managers approve on time, what your sandwich rule says, and whether an employee can see the workings without asking anyone.

The organisations that rarely have LOP disputes are not the ones with the most generous policy. They are the ones where attendance exceptions appear the next day, where the leave policy answers the awkward questions in writing, where the payslip shows days paid alongside the per-day rate, and where a reversal takes one cycle instead of one argument. None of that requires a large team — it requires the decisions to be made once, written down, and enforced by the system rather than by memory.

If your attendance data lives in one place, your leave balances in another and your payroll in a spreadsheet, the reconciliation work will keep eating your month end. CozyHR connects attendance, leave and payroll so LOP is derived from a single source of truth — daily exceptions, regularisation windows, manager approvals, a clean LOP register and payslips employees can read for themselves. If LOP queries are a recurring drain on your HR time, it is worth a look.