Loss of Pay (LOP) in Indian Payroll: 2026 Guide

Loss of Pay (LOP) in Indian Payroll: Rules, Calculation & Best Practices (2026)

Loss of Pay (LOP) is one of the most common — and most misunderstood — components of Indian payroll. When an employee runs out of paid leave but still stays away from work, those unpaid days have to be deducted from salary. Get the loss of pay calculation right, and your payroll is clean, your statutory filings reconcile, and employees trust their salary slips. Get it wrong, and you create under- or over-payments, wrong PF and ESI contributions, frustrated staff, and avoidable disputes.

This 2026 guide explains exactly how loss of pay works in Indian payroll: what LOP is, how it is calculated, which salary components it touches, how it interacts with PF, ESI, professional tax and TDS, and the policies and controls that keep LOP fair and accurate. Whether you run payroll for a 15-person startup or a 1,500-person enterprise, the principles below will help you process LOP confidently and consistently.

What is Loss of Pay (LOP)?

Loss of Pay, often abbreviated LOP and sometimes called "leave without pay" (LWP), is a payroll deduction applied when an employee is absent from work without an available paid leave balance to cover that absence. In simple terms, no work and no paid leave means no pay for those days.

LOP is not a punishment in itself. It is an accounting mechanism. An employer pays a monthly salary in exchange for an expected number of working days in that month. When an employee does not work and has no paid leave to draw on, the salary for those unworked days is simply not earned. The payroll system reduces the gross salary proportionately for the LOP days.

It helps to separate three related but distinct ideas:

• Paid leave is time off the employee has earned or been granted (earned/privilege leave, casual leave, sick leave). The employee is away but still paid.
• Loss of Pay (LOP) is time off that is unpaid because no paid leave balance is available, or because the leave taken is explicitly designated as unpaid.
• Absconding or unauthorised absence is a disciplinary matter. It often results in LOP for the unpaid days, but it also triggers a separate HR process that may lead to a show-cause notice or termination.

The key point for payroll teams: LOP only affects pay. The reason behind the absence — approved unpaid leave, exhausted balance, or unauthorised absence — is an HR and policy question that determines whether LOP should apply at all.

When does LOP apply?

LOP typically arises in a handful of recurring situations:

• An employee has exhausted all paid leave balances and takes additional days off.
• An employee takes leave that the company policy classifies as unpaid (for example, leave beyond a sabbatical cap, or extended personal leave).
• An employee is absent without prior approval and the absence is regularised as LOP rather than treated purely as misconduct.
• A new joiner takes leave before accruing any leave balance, and the policy does not allow advance or negative leave.
• An employee on a long, unpaid block — such as extended medical leave beyond entitlement — where statutory paid leave and any company buffer have run out.

Equally important is knowing when LOP should not apply. LOP should generally not be triggered for statutory paid leave the employee is legally entitled to (such as eligible maternity leave or earned leave the employee actually holds), for company holidays, or for weekly offs that fall within an otherwise-worked period. Misapplying LOP to protected leave is both a compliance risk and a trust-eroding error.

The core LOP calculation: per-day salary

At the heart of every LOP deduction is a per-day salary figure. The LOP amount is simply:

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

The complexity — and the source of most disputes — lies entirely in how you define "per-day salary" and "number of days." Indian companies commonly use one of three methods to derive the per-day rate.

Method 1: Calendar days

Divide the monthly gross (or the LOP-applicable salary) by the total number of calendar days in that month.

• Per-day salary = Monthly salary ÷ Calendar days in the month (28, 29, 30, or 31)

Because the divisor changes month to month, the same one day of LOP produces a slightly different deduction in February than in March. Some employees find this confusing, but it is mathematically clean: every day of the month, including weekly offs and holidays, carries equal weight.

Method 2: Fixed days (e.g., 30 days)

Divide the monthly salary by a fixed number — almost always 30 — regardless of the actual calendar length.

• Per-day salary = Monthly salary ÷ 30

This is popular because it is predictable: one LOP day always costs the same proportion of salary. The trade-off is the odd edge cases in 31-day and 28-day months, where the arithmetic can mean a fully absent employee is not reduced exactly to zero, or where a single present day in a long month is valued slightly differently.

Method 3: Payable (working) days

Divide the monthly salary by the number of payable days — typically the calendar days minus weekly offs, or some companies use "days the employee was expected to work."

• Per-day salary = Monthly salary ÷ Payable days in the month

This method makes each working day carry the salary, treating weekly offs as already "baked into" the monthly wage. It can be the most intuitive for employees ("I missed 2 of my 22 working days") but requires careful, consistent definition of what counts as a payable day.

Worked example

Assume a monthly gross salary of ₹60,000 and 3 LOP days in a 30-day month with 4 weekly offs (26 payable days).

Notice how the payable-days method produces a larger deduction per LOP day, because the salary is spread across fewer days. None of these methods is universally "correct." What matters is that your method is defined in policy, applied consistently to every employee, and clearly reflected on the salary slip.

Which salary components does LOP reduce?

A frequent source of payroll errors is applying LOP to the wrong base. Salary in India is usually a structure of multiple components, and not all of them necessarily move with attendance. The most common approaches are:

• LOP on gross salary: Every earning component (basic, HRA, special allowance, and other fixed allowances) is reduced proportionately for LOP days. This is the simplest and most common approach.
• LOP on basic only (rare): Some legacy structures reduce only basic pay, leaving allowances untouched. This is uncommon today and can create distortions, so most modern HRMS configurations avoid it.
• Component-by-component proration: Each earning is prorated for present days, while certain reimbursements or one-off payments (like a fixed mobile reimbursement or a joining bonus) are excluded from LOP proration by design.

The cleanest, most defensible default is to prorate all regular monthly earnings on gross, while keeping genuine reimbursements and one-time payments out of the LOP calculation. Whatever you choose, document it, configure it once in your payroll software, and apply it uniformly.

How LOP interacts with statutory deductions

LOP does not just reduce gross pay — it ripples through statutory contributions, because those are calculated on the actual wages paid in the month. Handling this correctly is essential for clean PF, ESI, and tax filings.

Provident Fund (PF/EPF)

Provident Fund contributions are calculated on the PF wage actually paid for the month. When LOP reduces the wage, the PF wage typically reduces too, and so does the contribution — subject to the wage ceiling and your organisation's policy on the ceiling. If an employee's PF wage normally sits above the statutory ceiling, modest LOP may not change the capped contribution; if the wage is at or below the ceiling, LOP will reduce the PF wage and the contribution accordingly. The number of LOP days is also reported in the monthly ECR, so the days and the reduced wage must agree. Always verify against the current EPFO rules and your configured ceiling policy.

Employees' State Insurance (ESI)

ESI is calculated on wages paid during the contribution period for employees within the ESI wage threshold. LOP reduces the wages paid, so the ESI contribution reduces in step. Crucially, LOP days affect "number of days worked" and the average daily wage that can matter for ESI benefit eligibility, so the days must be recorded accurately. If LOP pushes an employee's pay around the ESI threshold within a contribution period, take care to follow the contribution-period continuity rules rather than dropping someone mid-period. Verify against current ESIC rules.

Professional Tax (PT)

Professional tax is a state-level slab tax. In most states it is based on the gross salary actually earned in the month, so a large LOP that pushes monthly earnings into a lower PT slab can reduce the PT deducted. Because PT slabs and rules vary by state, confirm the slab for the relevant state and let your payroll system map the post-LOP gross to the correct slab automatically.

TDS on salary

Income tax deducted at source is based on projected annual income. A month of LOP lowers that month's taxable salary, which slightly lowers projected annual income and therefore the TDS for the month, assuming you recompute the projection. Most payroll systems re-estimate TDS each month, so LOP is absorbed smoothly across the year. The annual reconciliation at year-end (and in Form 16) should reflect the actual, LOP-reduced salary.

The overarching principle: LOP changes actual wages paid, and every statutory contribution that is a function of actual wages must be recomputed on the reduced figure — not on the original full salary.

Step-by-step: processing LOP in a monthly payroll run

A disciplined monthly process prevents the vast majority of LOP errors. Here is a reliable sequence.

1. Freeze attendance and leave data. Pull the month's attendance, approved leave, and weekly-off/holiday calendar as of the payroll cut-off date. Lock it so late changes don't silently alter the run.
2. Reconcile leave balances. For each employee, confirm the paid leave actually available. Days taken beyond the available balance become candidate LOP days.
3. Apply policy rules. Check exceptions: protected statutory leave, approved special cases, half-day rules, and any sandwich-leave policy (whether weekly offs or holidays falling between LOP days are counted). Convert candidate days into final LOP days.
4. Compute per-day salary using your defined method (calendar, fixed 30, or payable days). Keep the method identical for everyone.
5. Prorate earnings. Reduce the LOP-applicable components by per-day salary × LOP days.
6. Recompute statutory contributions (PF, ESI, PT) on the reduced wages, and re-estimate TDS.
7. Generate and review the salary register. Spot-check employees with LOP: do the days, deduction, and net pay reconcile? Are any reductions implausibly large?
8. Reflect LOP transparently on the payslip. Show LOP days and the corresponding deduction so the employee can see exactly what happened.
9. Reconcile and archive. Tie the LOP totals back to attendance, store the locked inputs, and keep an audit trail for queries later.

LOP and attendance: getting the source data right

LOP is only as accurate as the attendance data feeding it. Many "LOP disputes" are really attendance-capture problems in disguise — a missed biometric punch, an unsynced regularisation, or a leave request approved after the cut-off. To keep LOP clean:

• Integrate attendance, leave, and payroll so data flows automatically rather than via manual spreadsheets that drift out of sync.
• Define and publish a payroll cut-off date, and a clear window for regularisations and leave approvals before that cut-off.
• Use attendance regularisation workflows so genuine missed punches don't become wrongful LOP.
• Reconcile biometric/app punches with the roster before the run, especially for shift and field staff whose patterns are irregular.

When attendance, leave, and payroll live in one connected HRMS, LOP becomes a calculated output of trustworthy data rather than a manual guess.

Common LOP mistakes (and how to avoid them)

Even experienced teams trip on the same recurring issues. Watch for these:

• Mixing per-day methods across employees or months. Pick one method and apply it everywhere, every month. Inconsistency is the fastest route to disputes.
• Forgetting to recompute PF/ESI/PT on reduced wages. LOP must flow through to statutory contributions, or your filings won't reconcile.
• Applying LOP to protected statutory leave. Never convert legally entitled paid leave into LOP.
• Sandwiching weekly offs or holidays without a policy. Whether a weekend between two LOP days counts as LOP must be a written, consistent rule — not an ad-hoc decision.
• Ignoring half-days. Half-day LOP must be supported by your system; rounding it to a full day overcharges the employee.
• Negative or advance leave confusion. If you allow employees to go into negative leave, decide clearly when that becomes LOP versus a recoverable advance.
• Opaque payslips. If the employee can't see LOP days and the deduction, expect tickets. Transparency prevents disputes.
• Late attendance changes after cut-off. Lock inputs; handle genuine corrections through a documented adjustment in the next cycle.

Building a clear LOP policy

A short, written LOP policy resolves most ambiguity before it becomes a payroll ticket. A practical policy should state:

• Definition and triggers: what counts as LOP, and the situations in which it applies (exhausted balance, designated unpaid leave, unauthorised absence regularised as LOP).
• Calculation method: the exact per-day basis (calendar days, fixed 30, or payable days) and the components LOP reduces.
• Half-day handling: whether and how half-day LOP is supported.
• Sandwich rule: whether weekly offs/holidays between LOP days are counted.
• Approvals and regularisation: who approves unpaid leave, and the window to regularise attendance before payroll cut-off.
• Interaction with statutory benefits: a note that LOP affects PF/ESI/PT/TDS, recomputed on actual wages.
• Payslip transparency: a commitment to display LOP days and the deduction on the salary slip.

Keep the policy concise, publish it in the employee handbook, and make sure managers and the payroll team interpret it the same way.

LOP for specific scenarios

New joiners and exits. In the joining and exit months, employees are paid only for the days in service, and any unpaid days within that window are handled as LOP or simple proration depending on your configuration. Be careful not to double-count: proration for partial-month service and LOP for unpaid leave should be reconciled, not stacked incorrectly.

Shift and field staff. For employees on rotating shifts or in the field, "payable days" and weekly offs can vary, so the per-day basis and roster must be tightly defined. Roster-aware attendance is essential here.

Long unpaid leave. For extended unpaid periods, decide in advance how PF and ESI continuity, insurance, and benefits are handled during the unpaid stretch, and document it so there are no surprises on return.

Maternity and other protected leave. Eligible statutory paid leave must not be treated as LOP. Only days genuinely outside the paid entitlement — and only where policy and law permit — may attract LOP. When in doubt, verify the current statutory position before deducting.

A fuller worked example across three months

Per-day methods behave differently as the calendar changes, so it pays to see the same employee across several months. Take an employee on ₹62,000 gross, with 4 weekly offs each month, who takes 2 LOP days in February (28 days), 2 in March (31 days), and 2 in April (30 days).

Two lessons jump out. First, the calendar-day method makes a February LOP day "cost" more than a March one, because February's salary is spread over fewer days — employees sometimes question this, so explain it proactively. Second, the payable-day method consistently produces a larger deduction per LOP day than the calendar method, because weekly offs are excluded from the divisor. Neither is wrong; both are internally consistent. The danger is switching between them, which makes deductions look arbitrary. Lock one method per organisation and keep it stable across the year.

LOP versus other salary deductions

Employees often lump every reduction on their payslip into one mental bucket, so it helps payroll teams to keep the categories clean and distinct:

• LOP reduces earnings before statutory contributions are calculated. It changes the gross on which PF, ESI, and PT are computed.
• Statutory deductions (employee PF, ESI, PT, TDS) are taken from the post-LOP gross. They are not LOP and should never be confused with it.
• Recoveries — salary advances, loan EMIs, notice-period recovery, asset recovery — are deductions from net pay for amounts the employee owes. They are not earnings reductions and do not change PF/ESI/PT.
• Fines or penalties are a separate, tightly regulated category and should never be disguised as LOP.

Keeping LOP in the "reduced earnings" column, and recoveries in the "deducted from net" column, makes payslips readable and keeps your statutory base correct. A common error is to net an advance recovery against earnings and accidentally shrink the PF/ESI base — always recover from net, deduct statutory on the true earned wage.

Negative leave, leave encashment, and LOP

Many companies allow limited "advance" or negative leave so that a valued employee isn't pushed into LOP for a single unavoidable day. If you do this, define precisely when negative leave converts to LOP — for example, "negative balance up to 3 days is carried and recovered against future accrual; anything beyond becomes LOP in the current month." Without that rule, negative leave quietly accumulates and surfaces as a painful lump-sum LOP later.

At exit, the interaction between LOP and leave encashment matters too. An employee who took unpaid days during the year has fewer paid-leave days available to encash, and the encashment base should reflect the policy-defined components. Reconcile the leave ledger before computing full-and-final settlement so that LOP already taken and leave being encashed are never double-counted.

Handling LOP reversals and arrears

LOP errors happen — a leave approved after cut-off, a biometric sync that landed late, a manager's regularisation that missed the window. The clean way to fix them is an adjustment in the next payroll cycle rather than reopening a closed run. When you reverse an LOP:

• Add back the previously deducted amount as a clearly labelled arrear or adjustment line.
• Recompute the affected statutory contributions, because adding earnings back changes the PF/ESI/PT base for the adjustment.
• Re-estimate TDS so the year-to-date projection stays accurate.
• Annotate the payslip so the employee sees both the original deduction and its reversal.

The same discipline applies to retrospective increments that create arrears alongside an earlier LOP — process them as transparent, separately labelled lines so the audit trail stays readable.

Guidance for managers and employees

LOP runs more smoothly when managers understand their role. Encourage managers to approve or reject leave before the payroll cut-off, to use attendance regularisation for genuine missed punches rather than letting them lapse into LOP, and to flag planned long absences early so PF/ESI continuity and benefits can be arranged. For employees, a short explainer — how the per-day rate is derived, how to read LOP on the payslip, and the deadline to regularise attendance — prevents the majority of month-end tickets. Most LOP disputes are really communication gaps, and a little upfront clarity removes them.

Automating LOP with an HRMS

Manual LOP calculation in spreadsheets is slow and error-prone, especially across calendar-day variations, statutory recomputation, and half-days. A modern HRMS removes most of the risk by:

• Pulling attendance and leave automatically, so LOP days are derived, not typed.
• Applying your chosen per-day method and proration rules consistently for every employee.
• Recomputing PF, ESI, PT, and TDS on the reduced wages automatically.
• Showing LOP days and deductions transparently on each payslip.
• Maintaining a locked audit trail of inputs for every run.

This is exactly the kind of repetitive, rules-based work software handles best — freeing the payroll team to focus on exceptions and employee questions rather than arithmetic.

Frequently asked questions about Loss of Pay

1. Is Loss of Pay the same as leave without pay (LWP)? In everyday usage, yes — both describe unpaid days deducted from salary because no paid leave balance applies. Some organisations use LWP specifically for pre-approved unpaid leave and LOP more broadly, but the payroll effect is identical: those days are not paid.

2. How is the per-day salary for LOP calculated? By dividing the monthly salary by a defined number of days — calendar days in the month, a fixed 30, or payable working days — and multiplying by the number of LOP days. The method must be set in policy and applied consistently to everyone.

3. Does LOP reduce my Provident Fund contribution? Generally yes, because PF is based on actual wages paid in the month. If LOP reduces your PF wage, the contribution usually reduces too, subject to the wage ceiling and your employer's ceiling policy. Check current EPFO rules and your configuration for specifics.

4. Will LOP affect my income tax? LOP lowers your taxable salary for that month, which slightly lowers projected annual income and therefore the TDS deducted, assuming the projection is recalculated. Over the year it balances out, and your Form 16 reflects the actual LOP-reduced salary.

5. Can LOP be applied to weekly offs or public holidays? Only if your "sandwich leave" policy says so. Whether a weekly off or holiday falling between two LOP days counts as LOP must be a clearly written, consistently applied rule. Without such a policy, weekly offs and holidays are normally paid.

6. What happens to LOP if I have a half-day absence? A half-day of LOP should be deducted as half of one day's per-day salary, provided your payroll system supports half-day LOP. Rounding a half-day up to a full day over-deducts and should be avoided.

7. Can an employer reverse an LOP after payroll is processed? Yes. If an LOP was applied in error — for example, a leave approved after the cut-off — the correction is typically made as an adjustment in the next payroll cycle, with a clear note on the payslip. Maintaining locked inputs and an audit trail makes these corrections clean and traceable.

8. Does LOP affect gratuity or other end-of-service benefits? LOP affects the wages paid in specific months, but long unpaid periods can also have implications for continuous service and benefit calculations depending on the applicable rules and your policy. For end-of-service computations, verify the current statutory position and treat each case carefully.

Conclusion

Loss of Pay looks simple — multiply a per-day rate by the number of unpaid days — but doing it accurately means defining your per-day method, prorating the right components, recomputing PF, ESI, professional tax and TDS on the reduced wages, handling half-days and sandwich rules consistently, and keeping the salary slip transparent. Above all, LOP is only as reliable as the attendance and leave data behind it. Lock your inputs, document your policy, and apply it the same way for everyone.

If LOP is eating up your payroll team's time or generating recurring queries, this is precisely the kind of work that a connected HR and payroll platform handles cleanly. CozyHR brings attendance, leave, and payroll together so LOP days are derived automatically, statutory contributions are recomputed correctly, and every payslip shows employees exactly what was deducted and why. If you'd like to see how much smoother LOP and monthly payroll can be, it's worth taking CozyHR for a quick spin.

This article is for general guidance only and does not constitute legal or tax advice. Statutory rates, thresholds, and rules change over time and vary by state; always verify the current government provisions or consult a qualified professional before finalising payroll decisions.