CozyHR
Menu
Products
Docs
Resources
Compliance
Company
Support
Blog
PayrollAttendanceLeave ManagementHR Policy

Loss of Pay (LOP) Calculation in India: Formula & Policy

Learn how to calculate loss of pay in India, choose a divisor, handle half-days and the sandwich rule, and build a fair LOP policy.

CozyHR editorial team 12 October 2026 19 min read
CozyHR Blog
Loss of Pay (LOP) Calculation in India: Formula & Policy

Few payroll topics generate as many employee queries as loss of pay (LOP). A missed punch, a half-day, an unapproved absence or a leave balance that ran out can all quietly reduce a salary, and the first time most employees notice is when the payslip arrives. For HR and payroll teams, getting LOP right is about more than arithmetic. It is about fairness, clarity and a clean connection between attendance, leave and payroll.

This guide explains how to calculate loss of pay in India, how to choose a divisor, how to handle half-days, holidays, weekly offs and mid-month joiners, and how to build a policy and workflow that keeps disputes low. It is written for HR managers, payroll specialists and founders at small and mid-sized businesses.

Note: Rules on deductions from wages, notice requirements and wage definitions vary by state, industry and the applicable labour law. Use this guide as a practical framework and confirm legal points with a qualified professional.

What Is Loss of Pay?

Loss of pay (also called LOP, leave without pay or LWP) is the portion of an employee's salary that is not paid because the employee was absent without available paid leave. Put simply: if an employee did not work and was not covered by a paid leave type or a paid holiday, the employer does not pay for that day.

Some organisations use "LOP" and "LWP" interchangeably. Others make a distinction, treating LWP as approved unpaid leave and LOP as unapproved or unplanned absence that results in a salary deduction. Whichever term you choose, define it in your policy so everyone reads it the same way.

Common situations that lead to LOP

  • Absence without approval and without leave balance
  • Approved leave taken after paid leave balances are exhausted
  • Unpaid personal leave, sabbatical or extended leave
  • Late arrivals or early exits beyond permitted limits, if your policy converts them into half-day LOP
  • Unresolved missed punches that are never regularised
  • Unauthorised absence after a notice has been served, subject to disciplinary rules

What is usually not LOP

  • Paid holidays and weekly offs, subject to your policy
  • Approved paid leave such as casual, sick or earned leave
  • Maternity and other statutory paid leave
  • Approved work-from-home or on-duty days
  • Compensatory off, when used within its validity

Why Getting LOP Right Matters

An incorrect LOP deduction is more than an administrative error. It can lead to:

  • Employee dissatisfaction and a flood of payroll tickets.
  • Compliance concerns, since deductions from wages are regulated and should follow your policy and applicable law.
  • Reconciliation headaches in PF, ESI and TDS computations.
  • Manager conflict, when attendance records and leave approvals do not match.

A clear, documented and automated LOP process protects both the employer and the employee.

The Basic LOP Formula

The standard formula is simple:

LOP deduction = (Monthly salary ÷ Divisor) × Number of LOP days

The two judgement calls are which salary and which divisor.

Which salary should you use?

You have a few options.

  1. Gross salary: Deduct LOP from the entire gross. This is common and straightforward, and it reduces all earnings proportionally.
  2. Basic plus dearness allowance only: Used by some organisations for specific components, though it can create complexity.
  3. Component-wise proration: Each earning component (basic, HRA, special allowance) is prorated for the days actually payable. This is the cleanest approach for payslip transparency and is what most modern payroll systems do.

Choose one approach, document it and apply it consistently.

Which divisor should you use?

The divisor is the number of days you divide monthly pay by to get a per-day rate. Common choices:

Divisor methodHow it worksProsCons
Calendar daysDivide by the actual days in the month (28–31)Matches how most people think; weekends are includedPer-day rate varies month to month
Fixed 30 daysDivide every month by 30Simple and stableFebruary and 31-day months feel uneven
Working daysDivide by actual working days in the monthReflects days workedRate changes with holidays and weekly offs
Fixed 26 daysDivide by 26Common in some manufacturing and contract setupsNeeds consistent weekly-off assumptions

There is no single correct answer, but there is a wrong one: switching methods without notice. Pick a method and state it in the employment policy.

A quick worked example

Assume a monthly gross of ₹60,000 and an employee absent for 2 days with no leave balance.

  • Calendar days (30-day month): Per-day rate = 60,000 ÷ 30 = ₹2,000. LOP = 2 × 2,000 = ₹4,000.
  • Calendar days (31-day month): Per-day rate = 60,000 ÷ 31 ≈ ₹1,935.48. LOP ≈ ₹3,870.97.
  • Fixed 30 days: LOP = ₹4,000 in any month.
  • Working days (22 working days): Per-day rate ≈ 60,000 ÷ 22 ≈ ₹2,727.27. LOP ≈ ₹5,454.55.

Same absence, four very different deductions. This is why a clear divisor policy is vital. Employees quickly notice when LOP differs between months for the same absence.

Calendar-Day vs Working-Day Method: Which Is Better?

Why many SMBs prefer calendar days

Monthly salary is paid for the whole month, including weekly offs and paid holidays. Dividing by calendar days treats weekends and holidays as paid days that sit inside the monthly figure. It is also easy to explain: "You are paid for every day of the month, so each unpaid day reduces pay by one day's share."

An important wrinkle appears here: if an employee takes LOP on a Friday and the following Monday, do the intervening Saturday and Sunday also become LOP? That depends on your sandwich rule, covered below.

When working days make sense

Working-day divisors can be useful in businesses that pay by daily rate, run six-day weeks or have variable weekly-offs. They are also common in contract and factory environments. However, the per-day rate will fluctuate, so communicate it clearly.

Recommendation

For salaried office-based staff, calendar-day or fixed-30 are usually easiest to defend and explain. For daily-wage or shift-based teams, working-day or fixed-26 may fit better. Whatever you choose, write the formula in the offer letter or policy.

Half-Day LOP, Short Leave and Late Marks

Not every absence is a full day. Modern attendance policies often include:

  • Half-day LOP: Counted as 0.5 days when the employee works less than a defined minimum (for example, under half the shift).
  • Short leave or permission: A limited number of hours per month that does not count as LOP.
  • Late marks: After a defined number of late arrivals, a half-day is deducted from leave balance or converted to LOP.

Setting thresholds

State clearly:

  1. The minimum hours for a full day, a half day and an absent day.
  2. How many late marks convert to a half-day.
  3. Whether the half-day is deducted from leave balance first and converted to LOP only if the balance is zero.

Without thresholds, managers and employees interpret the same attendance very differently.

Weekly Offs, Holidays and the Sandwich Rule

The sandwich rule says that weekly offs or holidays falling between two absence days are also counted as leave or LOP. For example, if an employee is absent on Friday and Monday, the Saturday and Sunday in between are treated as absent too.

Pros of a sandwich rule

  • Discourages extending weekends with unplanned leave
  • Reflects that the employee was away for the whole stretch

Cons of a sandwich rule

  • Can feel harsh, especially for genuine illness
  • Creates confusion if applied inconsistently
  • Needs clear exceptions (for example, medical leave certified by a doctor)

How to apply it fairly

If you adopt the sandwich rule, state:

  • Whether it applies to weekly offs, holidays or both
  • Whether it applies to all leave types or only to LOP and casual leave
  • What exceptions exist (medical, bereavement, statutory leaves)

If you do not want a sandwich rule, say so explicitly. Silence invites disputes.

Joiners and Leavers: Prorating the First and Last Month

New joiners and exits rarely line up with month boundaries, so you need a proration rule.

Mid-month joiners

Typical approach: pay from the date of joining. With a calendar-day method, per-day pay is monthly salary ÷ days in the month, multiplied by days from joining date to month-end.

Example: Monthly gross ₹45,000, joining on the 11th of a 30-day month. Payable days = 20. Pay = 45,000 ÷ 30 × 20 = ₹30,000.

Mid-month leavers

Prorate to the last working day. Remember that final settlement involves more than the month's salary: leave encashment, notice recovery, gratuity (if eligible), bonus and other dues may apply. Your final-settlement process should draw from the same attendance and leave data used for LOP.

Watch for the notice period

If an employee stops attending during notice, LOP rules, recovery of notice pay and disciplinary provisions may interact. Handle these cases through a documented process and seek legal advice for contested situations.

How LOP Affects Statutory Deductions

LOP changes the wages actually paid, and that can ripple into statutory calculations.

Provident Fund

Where PF is computed on actual earned wages, LOP days reduce the PF wage and, therefore, the contribution. The treatment of days of non-contributory service and the related reporting in monthly returns needs care. Make sure your payroll system captures "days of LOP" so your filings reflect them accurately.

ESI

ESI contributions depend on wages payable for the period. If an employee's wages fall because of LOP, the contribution will follow, subject to the rules for contribution periods. Be careful with employees near the eligibility threshold.

Income tax (TDS)

LOP reduces taxable salary for the month and, over the year, the projected annual income. Payroll should recompute projected tax each month so TDS stays accurate.

Professional tax

Professional tax slabs in many states depend on gross monthly salary. A salary reduced by LOP might fall into a different slab, so confirm how your state treats it.

Bonus and gratuity

Where the bonus law applies, it counts days worked. Gratuity depends on continuous service, and genuine LOP does not usually break continuity, though extended unauthorised absence may raise separate issues. Seek advice for edge cases.

Building an LOP Policy: A Practical Template

A good policy is short, specific and examples-driven. Include the following sections.

  1. Purpose and scope: Who the policy applies to.
  2. Definitions: LOP, LWP, half-day, full day, sandwich rule.
  3. Attendance standards: Minimum hours for full day and half day.
  4. Leave hierarchy: Order in which leave types are used (for example, casual, then earned, then LOP).
  5. Calculation method: Salary basis and divisor, with a worked example.
  6. Regularisation window: Last date to regularise missed punches or apply for leave before payroll cut-off.
  7. Approval workflow: Who approves leave and regularisation.
  8. Dispute process: How to raise a query and the timeline for resolution.
  9. Corrections: How over- or under-deductions will be fixed in the next payroll.
  10. Review: How often the policy is reviewed.

Have the policy reviewed by legal counsel, share it with all employees, and keep an acknowledgement on file.

The Attendance-to-Payroll Workflow

LOP is the output of a chain: attendance capture, leave application, approval, regularisation, lock, and payroll. Weakness at any link produces errors.

Step 1: Capture attendance reliably

Whether through biometric devices, mobile check-ins or web punches, ensure you collect accurate in and out times. Missing punches are the single biggest source of avoidable LOP.

Step 2: Encourage timely leave applications

Make it easy to apply for leave from a phone. Remind employees to apply before or immediately after the absence.

Step 3: Run a pre-cut-off review

A few days before the payroll cut-off, produce an exceptions report listing:

  • Missing punches
  • Absences without leave
  • Half-day candidates
  • Negative leave balances

Send reminders to employees and managers to resolve them.

Step 4: Lock attendance

After the cut-off, lock attendance. Changes after the lock should follow a controlled exception process, with approvals and clear next-month adjustments.

Step 5: Run payroll and review the LOP register

Generate a LOP register that lists each affected employee, number of days, reasons and amount. Have HR or a payroll reviewer sign off before disbursal.

Step 6: Publish payslips with visible LOP details

A payslip that shows "LOP days: 2" and the corresponding deduction line prevents many questions.

Handling Corrections and Reversals

Errors happen. Plan for them.

  • Over-deduction: Refund in the next payroll, clearly marked as an LOP reversal.
  • Under-deduction: Recover only through a transparent process, with prior intimation to the employee and consideration of legal limits on deductions.
  • Retrospective leave approvals: If a manager approves leave after payroll closed, reverse the LOP in the next cycle.
  • Audit trail: Keep a log of who changed which attendance record and why.

A reversal workflow in your HRMS saves a lot of manual spreadsheets.

LOP for Different Employee Types

Monthly salaried staff

Calendar-day or fixed-30 proration generally works. Apply component-wise proration for transparent payslips.

Daily-wage and contract workers

Pay is based on days worked, so there is no separate LOP deduction; they are simply paid for attendance. Keep accurate daily registers, particularly where minimum wage laws apply.

Shift workers

Shift patterns may create partial days. Define the minimum hours that make up a shift and how night shifts crossing midnight are counted.

Remote and hybrid employees

Track attendance through logins, check-ins or output-based approaches. Define what counts as present for remote days and how unreachable days are treated.

Field staff

Use GPS or mobile check-ins, and allow for client-visit days. Review exceptions weekly rather than monthly.

Statutory and Special Leave That Should Not Become LOP

Make sure your payroll never converts the following into LOP by mistake:

  • Maternity and related statutory leave
  • Paternity or adoption leave where your policy grants it
  • Statutory holidays
  • Approved paid sick leave
  • Bereavement or compassionate leave under your policy
  • Compensatory offs within validity

Maintain a clear mapping of leave types to paid or unpaid status in your system, and review it whenever policy changes.

Metrics to Track

If you analyse LOP, you can fix root causes instead of firefighting. Consider tracking:

  • LOP days per 100 employees per month
  • Percentage of LOP caused by missing punches versus true absence
  • LOP by department, manager or location
  • Number of LOP reversals after payroll
  • Average time to resolve LOP queries

A falling reversal rate is a strong signal that your process is improving.

Common Mistakes

  • Using different divisors for different employees without a policy basis.
  • Deducting LOP from only basic while paying other components in full, creating inconsistent logic.
  • Ignoring missing punches, which turn into unfair absences.
  • Late leave approvals that arrive after payroll lock.
  • No visibility on payslips, leading to avoidable queries.
  • Applying the sandwich rule inconsistently across teams.
  • Forgetting statutory impacts on PF, ESI and professional tax.
  • Manual spreadsheets with no audit trail.

A Mini Checklist for Payroll Day

  • Attendance locked and approved
  • Leave balances validated, with no unexpected negatives
  • Exception report cleared
  • LOP register reviewed
  • Joiners and leavers prorated correctly
  • Statutory impacts checked
  • Payslip previews tested for a few sample employees
  • Reversals from the previous month processed

Worked Scenarios: Five Real-World LOP Cases

Policies look tidy on paper and messy on payday. These scenarios show how a clear rule resolves common situations. The numbers are illustrative.

Scenario 1: Leave balance runs out mid-month

Meera has one casual leave left and takes three days off. The first day is covered by casual leave, and the next two become LOP. With a monthly gross of ₹48,000 and a fixed 30-day divisor, her per-day rate is ₹1,600 and the deduction is ₹3,200. The payslip should show one day of leave taken from balance and two days of LOP, so she can see exactly why the deduction occurred.

Scenario 2: A forgotten punch

Arjun worked a full day but forgot to punch out. The system marks the day as incomplete. If your policy has a regularisation window, Arjun raises a request, his manager approves it, and the day is restored before the cut-off. If he misses the window, the day may convert to a half-day LOP or an absence. This is why a pre-cut-off exception report is so valuable: it turns a likely deduction into a quick fix.

Scenario 3: Sandwich rule on a long weekend

Priya is absent on the Friday before a long weekend and on the Tuesday after it. Saturday, Sunday and Monday (a paid holiday) sit between those absences. Without a sandwich rule, only two days are affected. With a sandwich rule covering both weekly offs and holidays, five days are affected. Whichever rule applies, the policy must say so, and the system must apply it automatically, not depend on a payroll executive remembering.

Scenario 4: Joiner who takes unplanned leave in the first month

Karan joins on the 8th and is absent for two days later in the month. He has no leave balance yet because accrual starts after probation. Payable days are first prorated for the period from the 8th, and then LOP is applied for the two days. Payroll teams often double-count here, so test this combination before go-live.

Scenario 5: Retrospective leave approval

Sana was ill, could not apply for leave in time, and her manager approves sick leave three days after the payroll cut-off. The month's payroll has already closed with LOP. The right response is a reversal in the next payroll, clearly labelled, with the leave balance adjusted. Avoid reopening a closed payroll, which risks errors in statutory filings.

Designing a Payslip That Explains LOP

A payslip is the final communication of your LOP policy. Small design choices reduce queries dramatically.

  • Show days payable and days of LOP near the top.
  • Display each earning component as prorated, with the full-month amount alongside where space permits.
  • Add a one-line note when a reversal or correction appears.
  • Link or point to the policy so employees can read the formula.
  • Make the payslip available on mobile, since many employees check it on their phones.

When employees can see the working, they are less likely to raise a ticket and more likely to trust the process.

Technology Checklist for LOP Automation

If you are evaluating or configuring an HRMS, check that it can do the following:

  1. Define leave types as paid or unpaid with configurable rules.
  2. Support multiple divisor methods and apply the one you select.
  3. Auto-convert late marks and short hours into half-days based on your policy.
  4. Apply sandwich rules with exceptions.
  5. Prorate joiners and leavers automatically.
  6. Generate an exception report before cut-off.
  7. Lock attendance and track post-lock changes with approvals.
  8. Pass LOP days to PF, ESI, professional tax and TDS calculations.
  9. Create reversals and arrears without manual spreadsheets.
  10. Keep an audit trail for every change.

Run a parallel payroll for at least one cycle after any configuration change to compare results with your previous method.

Communicating the Policy to Managers and Employees

Policies fail when only HR understands them. Consider the following communication habits.

  • Brief managers first, since they approve leave and handle the first questions.
  • Share two or three examples of LOP calculation in the employee handbook.
  • Send a reminder two to three days before each payroll cut-off.
  • Hold a short onboarding session for new joiners explaining attendance, leave and LOP.
  • Review queries quarterly and update the FAQ based on what people actually ask.

A clear, friendly tone matters. LOP can feel punitive, so frame it as a transparent rule that applies equally to everyone.

Special Cases Worth Documenting in Advance

  • Strikes, lockouts or natural disasters: Decide in advance whether affected days are paid, adjusted or treated under a specific policy.
  • Employee in custody or under suspension: These cases involve legal procedures and standing orders; seek advice before applying LOP.
  • Training or travel days: Define them as on-duty so they never become LOP.
  • Public transport disruption or office closure: Decide whether the company treats such days as paid.
  • Leave during probation: If leave accrual is delayed, say whether leave taken in that period is LOP.

Writing these down before they happen prevents ad hoc decisions that feel unfair later.

A Note on Fairness and Trust

Loss of pay is one of the few places where payroll directly touches an employee's sense of fairness. Three habits build trust over time. First, apply rules the same way for everyone, including managers and senior staff. Second, give people a realistic chance to fix honest mistakes, such as missed punches, before a deduction becomes final. Third, fix errors quickly and visibly when they happen. An employee who sees an over-deduction reversed within one cycle usually forgives the mistake; one who has to chase for three months does not.

Frequently Asked Questions

1. Should LOP be calculated on gross salary or basic salary?

Most employers calculate LOP on gross or prorate each component. Whichever method you choose, apply it consistently and state it in the policy. Component-wise proration gives the clearest payslip.

2. Is it legal to deduct salary for unapproved absence?

Employers generally may withhold pay for days not worked, but deductions from wages are regulated and procedures matter. Follow your written policy and confirm current legal requirements with a professional.

3. Do weekly offs count as LOP if the employee is absent before and after?

Only if your policy includes a sandwich rule. If it does, state which days it covers and any exceptions. If it does not, weekly offs remain paid.

4. How do I calculate LOP for a half-day?

Divide the per-day rate by two, or count the absence as 0.5 days in your formula. Define the minimum hours that qualify as a half-day.

5. Can an employee use paid leave to cover LOP after the fact?

Many companies allow retrospective leave application within a set window, after which the LOP is reversed. Specify the window in your policy.

6. How does LOP affect PF contributions?

When PF is based on actual earned wages, LOP lowers the PF wage and contribution, and the days of non-contributory service should be reported correctly. Check your PF practice and consult a professional if unsure.

7. What if an employee joins mid-month?

Prorate from the date of joining using your chosen divisor. Communicate the calculation in the first payslip.

8. How can we reduce LOP disputes?

Provide clear policies, easy leave and regularisation tools, a pre-cut-off exception report, visible LOP details on payslips and a quick reversal process.

Conclusion: Make LOP Predictable, Fair and Boring

The best LOP process is one that nobody talks about. Employees understand the rules, managers approve on time, attendance data is clean and the payslip shows exactly what happened. Achieving that comes down to a few decisions: choose a divisor and stick to it, define half-days and sandwich rules, set a firm cut-off with a regularisation window, and automate the flow from attendance to payroll.

If you want to remove manual spreadsheets from this process, you can try CozyHR to connect attendance, leave and payroll in one place, view LOP registers before you run payroll, and handle reversals with a clear audit trail. Predictable payroll builds trust, and trust is worth far more than any single deduction.

A final word on consistency

The single most useful habit in loss-of-pay management is consistency. Use the same formula every month, apply the same rules to every team, publish the policy where everyone can find it and review exceptions on a fixed schedule. When the rules are predictable, employees plan around them, managers stop improvising and payroll teams spend payday verifying results instead of debating them. Predictability is the quiet foundation of payroll trust.

Disclaimer: This article provides general information, not legal or tax advice. Labour regulations, wage-deduction rules and statutory rates vary and change; verify current requirements with official sources and qualified professionals.