Loss of pay (LOP) is the amount cut from salary for days an employee was not paid for. The idea is simple. The argument starts with the divisor: do you divide monthly pay by 30, by the actual days in the month, or by 26 working days? Each is used by real companies, each gives a slightly different number, and the wrong choice is the one you did not tell your employees about.
Figures here reflect the rules as we understand them at the time of writing. Verify against the current rules and notifications before relying on them.
What counts as an LOP day
Before any maths, decide which days reduce pay:
- Unapproved absence. The employee did not attend and no leave was approved.
- Approved unpaid leave. Leave without pay, taken with approval.
- Leave balance exhausted. Paid leave types have run out and the extra days are unpaid.
- Half days. A half day absent is half an LOP day.
- Late-mark policies. Some companies convert a number of late marks into a half day. If you do, document it, because it needs to be consistent.
Weekly offs and declared holidays are normally paid. Whether a weekly off sandwiched between two LOP days is also unpaid is a policy choice. Decide it and write it down.
The three common methods
| Method | Daily rate | Behaviour |
|---|---|---|
| Calendar days | Monthly pay / days in the month (28 to 31) | Daily rate changes every month; February deductions per day are higher |
| Fixed 30 days | Monthly pay / 30 | Constant rate; simple to explain; slightly off in 31-day months |
| 26 working days | Monthly pay / 26 | Higher daily rate, assumes four Sundays off; common in some sectors and used for overtime and leave encashment bases |
There is no single correct choice in general. Your appointment letter, company policy and any applicable state law decide it. Check your Shops and Establishments rules and ask your consultant if you are unsure.
A worked example
Employee gross: Rs 39,000 a month. Absent 3 days in a 31-day month, with no approved leave.
| Method | Daily rate | LOP deduction | Pay for the month |
|---|---|---|---|
| Calendar days (31) | 39,000 / 31 = Rs 1,258.06 | 3 x 1,258.06 = Rs 3,774 | Rs 35,226 |
| Fixed 30 | 39,000 / 30 = Rs 1,300 | 3 x 1,300 = Rs 3,900 | Rs 35,100 |
| 26 working days | 39,000 / 26 = Rs 1,500 | 3 x 1,500 = Rs 4,500 | Rs 34,500 |
The difference between the 26-day and calendar-day methods on three days of absence is Rs 726. Across 40 people with an average of two LOP days each, that can add up to a noticeable amount, and a visible inconsistency if two managers use different methods.
Another way to think of it is as paid days. In a 31-day month with 3 LOP days, the employee has 28 paid days. Pay is the monthly figure multiplied by 28/31 under the calendar-day method. That is the same answer as above, reached from the other direction.
Prorating the components
LOP does not hit only the gross. It prorates each earning that is paid per day worked:
- Basic and HRA are reduced in proportion to paid days.
- PF is computed on the reduced basic, so contributions fall.
- ESI is computed on the reduced gross, which matters near the Rs 21,000 limit.
- Fixed allowances prorate the same way, unless your policy says a particular allowance is paid in full.
In the PF return the number of non-contributory days should match the LOP days. If your attendance data and your payroll disagree here, the mismatch shows up in your ECR. Our PF ECR checklist covers this.
Half days
A half day is 0.5 of an LOP day. If your attendance has codes such as P, A, HD, L and WFH, map them carefully:
- P (present) and WFH (work from home): paid.
- A (absent): 1 LOP day, unless covered by approved leave.
- HD (half day): 0.5 LOP day, plus 0.5 of whatever leave the employee applied for the other half.
- L (leave): paid or unpaid depending on the leave type.
Joiners and leavers
An employee who joins on the 11th of a 30-day month has not lost pay for the first ten days. They simply were not employed. Likewise an exit on the 20th covers 20 days. In most systems the first and last months are prorated by days of employment rather than treated as LOP, which keeps the compliance data right: PF non-contributory days are not the same thing as days before joining.
Be careful about the divisor here too. A joiner in a 31-day month, paid on the 30-day method, can look odd: 21 days worked out of 30 still gives less than a full month’s pay for a month in which they worked 21 of 31 days. Choose one method, and check the joiner and leaver numbers against it before the payroll is approved.
Overrides and exceptions
Real life breaks rules. Examples:
- An employee was present, but the biometric device failed. The attendance correction is approved late.
- A manager approves unpaid leave for personal reasons.
- A one-time waiver is agreed by HR.
You need a way to override LOP for one person, with a reason and a record. Silent edits to the payroll register are the worst version. Corrections should come back through attendance, approved by the right person, before the month is locked.
How Saralix calculates it
In Saralix, LOP comes from approved attendance and approved unpaid leave. An absent day counts as 1 day, a half day counts as 0.5, and approved unpaid leave is added. Pay is prorated for the paid days, and LOP can be overridden for an individual employee. Joiners and leavers are prorated. Payroll approval is blocked while attendance corrections are pending, and days in an approved payroll month are locked against bulk upload, so numbers cannot change under you after the run.
If you have never decided on a divisor, check your company settings and your own policy before the first run so that what the system does matches what you have told employees.
A checklist for your LOP policy
- Divisor chosen: calendar days, 30, or 26
- Which days are LOP written down (absent, unpaid leave, exhausted balance)
- Half-day rule defined
- Weekly offs and holidays between LOP days treated consistently
- Late-mark rule defined, or explicitly not used
- Joiner and leaver proration defined
- Override process with a named approver and a reason field
- Attendance corrections closed before cut-off
- Policy communicated in writing to employees
Practical tips for HR
- Send a pre-payroll LOP list to managers two days before cut-off, so disputes happen before the run, not after.
- Sample five employees with LOP every month and recompute by hand.
- Keep leave and attendance in one place. LOP disputes mostly come from two records that disagree. The attendance and leave features show how one record can feed payroll.
- Do not reverse LOP in the next payroll without a note. It confuses the PF and tax records.
For the end-to-end monthly flow, see how to run payroll in 7 steps, and use the salary breakup calculator to see how components move when pay is prorated.
Related: payroll features and payroll mistakes startups make.
Closing thought
Whichever divisor you choose, the rule that keeps employees calm is consistency and a written policy. If you want attendance, leave and loss of pay to live in one record so the numbers agree, the attendance and leave module in Saralix is built for that.



