Three Divisor Methods and When Each Is Used

Per-day salary is monthly salary divided by a divisor, and Indian payroll uses three different divisors. The calendar-day method divides by the actual days in the month (28 to 31). The fixed-30 method divides by 30 every month regardless of length. The 26-day method divides by 26, treating the month as 30 days less four weekly offs, so that each paid working day carries the weekly-off cost inside it.

The 26-day divisor is the expected practice for minimum-wage and daily-rated workers. State minimum wage notifications publish a monthly rate and a daily rate that is the monthly figure divided by 26, and inspectors compute shortfalls that way. Security guards, housekeeping staff, factory helpers and contract labour should therefore be on 26. Monthly-salaried office staff are commonly on calendar days or fixed 30, and either is acceptable if the appointment letter and policy say so.

The method also decides how you treat weekly offs during absence. Under the 26-day method a worker who is absent all six working days of a week loses six days of pay and the weekly off's value is lost with them because it was embedded. Under calendar-day methods the weekly off is a paid day in its own right, which is why sandwich rules exist. Whatever you choose, write it into the attendance and salary policy and use it for every employee in that category. See the loss of pay glossary entry for the vocabulary.

• Calendar days: monthly ÷ 28/29/30/31; common for salaried staff
• Fixed 30: monthly ÷ 30; simple and predictable, slightly overpays in 31-day months
• 26 paid days: monthly ÷ 26; expected for minimum-wage and daily-rated workers
• State the method per employee category in the policy and appointment letter

Worked Example: ₹26,000 Gross, 31-Day Month, 2 LOP Days

Take an employee on ₹26,000 gross per month in a 31-day month with two unpaid absences. Under the calendar-day method, per-day salary is ₹26,000 ÷ 31 = ₹838.71; LOP is 2 × ₹838.71 = ₹1,677.42; payable gross is ₹24,322.58. Under fixed 30, per-day is ₹866.67; LOP ₹1,733.33; payable ₹24,266.67. Under the 26-day method, per-day is ₹1,000; LOP ₹2,000; payable ₹24,000.

The spread is ₹322.58 between the most and least generous methods for the same two days. Multiply across a 300-person workforce with an average of one LOP day per person per month and the choice of divisor moves the wage bill by tens of thousands of rupees monthly. That is not an argument for the cheapest method; it is an argument for choosing deliberately and documenting it, because an employee who is deducted ₹1,000 per day when a colleague is deducted ₹838 will ask why.

The alternative to deduction is the earned-days method: pay = monthly salary × paid days ÷ divisor. For 26-day workers that is ₹26,000 × 24 ÷ 26 = ₹24,000, the same result as deducting 2 × ₹1,000. Payroll software usually computes both ways and reconciles them, and the salary per day calculator lets you compare the three methods for any salary and month.

• Calendar days: ₹838.71/day; 2 LOP = ₹1,677.42; payable ₹24,322.58
• Fixed 30: ₹866.67/day; 2 LOP = ₹1,733.33; payable ₹24,266.67
• 26 days: ₹1,000/day; 2 LOP = ₹2,000; payable ₹24,000
• Earned-days formula gives the same answer as deduction when the divisor matches

Half-Day and Late-Mark Deductions

A half-day deducts 50% of the per-day rate. On ₹26,000 under fixed 30 that is ₹433.33; under 26 days it is ₹500. Most policies mark a half-day when paid hours fall below a threshold (commonly four hours on an eight-hour shift) or when the first punch is after a fixed cut-off such as the shift midpoint. Define the trigger in hours or clock time, not in both, or two supervisors will produce two answers. The half-day glossary entry lists the common trigger definitions.

Late marks are usually a count-to-deduction rule: for example, three late marks in a calendar month equal one half-day LOP, and every further three late marks another half-day. The grace period (say 10 minutes) is applied before the late mark is recorded, and a late mark on a day already marked half-day should not be counted twice. Write the conversion explicitly: the deduction is a half-day LOP computed at the standard per-day rate, not a separate fine, because fines on wages are restricted by law.

Interaction with overtime is the trap. An employee who arrives at 13:10 on a 09:00 to 18:00 shift and stays until 22:40 has both a late trigger and hours beyond schedule. Decide once whether the day is hours-first (pay the hours, record the late) or status-first (half-day, extra hours only if approved), and apply the same rule every month. The detailed sequencing is in how to calculate half day and overtime.

• Half-day = 50% of the per-day rate under the employee's divisor method
• Convert late marks to half-day LOP at a fixed count (e.g. three per month)
• Apply grace before recording a late mark; never double-count on a half-day
• Publish one rule for days that trigger both half-day and overtime

LOP, Leave Without Pay and Unauthorised Absence Are Not the Same

Loss of pay is an outcome: a day for which no wage is paid. Leave without pay (LWP) is an approved absence when paid leave is exhausted; the employee applied, the manager approved, and the day is LOP by agreement. Unauthorised absence is an unapproved no-show; it is also LOP, but it may additionally trigger disciplinary steps and it usually breaks continuity for sandwich rules. Recording all three as one code hides information you will need later.

The difference matters for continuity of service too. Approved LWP generally counts as service for gratuity and leave accrual purposes; prolonged unauthorised absence may not, and some standing orders treat it as abandonment after a stated number of days. Keep separate attendance codes: LWP (approved), UA (unauthorised), and let payroll map both to zero pay while HR keeps the distinction. The attendance regularisation process explains how an unauthorised absence can be converted to approved leave before payroll cut-off.

Also separate LOP from deductions for damage or loss, fines and recovery of advances. Those are governed by their own limits under the Code on Wages and must appear as distinct payslip lines. LOP is not a deduction in the legal sense; it is wages not earned, and it should reduce gross rather than appear in the deductions block.

• LOP is the outcome; LWP and unauthorised absence are causes with different HR consequences
• Keep separate attendance codes even though payroll treats both as unpaid
• LOP reduces earned gross; it is not a deduction and should not sit with PF and PT
• Fines and damage recovery follow their own statutory limits and separate lines

Paid Holidays and Weekly Offs Inside an LOP Period

If an employee is on unpaid absence on Saturday and Monday, is Sunday paid? Under a sandwich rule, the intervening weekly off or holiday is treated as unpaid when both adjacent working days are unpaid, so the LOP becomes three days. Many companies apply the sandwich only to unauthorised absence and not to approved LWP, and some do not apply it at all. There is no single statutory rule for private establishments; it is a policy choice that must be written down and applied uniformly.

For workers on the 26-day divisor the question rarely arises, because the weekly off has no separate pay value: it is embedded in the 26 paid days. For calendar-day and fixed-30 methods the weekly off is a paid day and the sandwich rule is what decides its fate. Paid festival holidays are generally treated more generously; deducting a national holiday because the employee was absent the day before and after is legal only if the applicable state rules and your policy allow it.

Under the Factories Act and most Shops and Establishments Acts, a worker who has worked the qualifying days in the week is entitled to the weekly holiday, and some state rules state that the weekly off is paid if the worker has worked a minimum number of days that week. Check your state's Shops and Establishments Act before adopting a strict sandwich rule. The sandwich leave rule guide covers the variants and how to phrase the policy.

• Sandwich rule: weekly off between two unpaid days becomes unpaid, if the policy says so
• Irrelevant for 26-day workers; decisive for calendar-day and fixed-30 methods
• Apply differently to approved LWP and unauthorised absence if you wish, but write it down
• Check state Shops and Establishments rules on paid weekly holidays first

How LOP Affects PF, ESI and Other Statutory Figures

PF is payable on wages actually earned, so LOP reduces the PF base. If basic + DA is ₹13,000 and the employee has two LOP days in a 31-day month under the calendar method, earned basic is ₹13,000 × 29 ÷ 31 = ₹12,161.29 and PF is 12% of that, ₹1,459, not ₹1,560. The ECR must show the reduced wage and the number of non-contributory days (NCP days) for the month. Payroll that computes PF on contracted basic overpays PF and misreports NCP days.

ESI eligibility is unaffected by LOP: the ₹21,000 test is applied to the contracted wage at the start of the period, so an employee whose earned gross drops to ₹18,000 because of absence does not become newly covered. The contribution, however, is 0.75% and 3.25% of wages actually paid that month. Professional tax slabs are usually applied to gross actually paid, so a heavy-LOP month can drop an employee into a lower PT slab in slab states such as Maharashtra or West Bengal.

Statutory bonus is computed on wages earned in the year, so LOP months automatically reduce the bonus base, and the 30-working-day eligibility test counts days actually worked plus paid leave. Gratuity's continuous-service test looks at days worked and authorised leave, which is another reason to keep LWP and unauthorised absence as separate codes. The PF calculation guide covers the wage base in detail.

• PF on earned basic + DA after LOP; report NCP days in the ECR
• ESI eligibility fixed for the period; contribution on wages actually paid
• PT slab may change in a heavy-LOP month in slab states
• Bonus and gratuity tests use actual working days and authorised leave

Documenting the Rule and Automating LOP From Attendance

The policy should state, per employee category: the divisor; the half-day trigger; the late-mark conversion; whether the sandwich rule applies and to which absence types; the payroll cut-off date after which unregularised absences become LOP; and the regularisation window. Put a one-line worked example under each rule, because supervisors follow examples more reliably than clauses.

In practice LOP goes wrong at the hand-off between attendance and payroll. A paper register or WhatsApp roll-call gives payroll a count of absent days without the reasons, and the payroll executive applies a default. Late regularisations arrive after the salary sheet is locked and generate arrears next month. Both problems disappear when leave, attendance and payroll share one record.

Attend Mitra derives LOP from the same attendance records that hold punches, approved leave and regularisation requests, applies the configured divisor and half-day rules per shift, and passes the resulting paid days into the payroll run and payslip. Leave balances and LOP are visible to the employee in the self-service app before payroll closes, which cuts the after-the-fact disputes. The salary calculation attendance software page describes the flow end to end.

• Policy: divisor, half-day trigger, late-mark conversion, sandwich rule, cut-off, regularisation window
• Add a worked example under every rule
• Lock the payroll cut-off and route late corrections to arrears deliberately
• Let attendance, leave and payroll share one record so LOP is derived, not typed