How LOP days become a payroll amount

Once unpaid days are known, payroll still has to turn them into rupees. That step is arithmetic: a day rate times the unpaid quantity, using a divisor your policy named. It is not a second copy of how attendance and leave become those days. The attendance-to-payroll LOP guide owns the handoff — punches, regularisation, leave close, then an unpaid-day input. This page owns the money step after that input exists.

There is no single Indian legal formula published here. Calendar days in the month, paid days, and a fixed 30 are common policy choices. Treat them as methods you must write down, not as a statute. This is not legal advice. Dayzen payroll can calculate loss of pay from attendance-linked inputs; it does not invent your divisor, and it does not file or bank-pay.

Days are an input, rupees are a method

If the unpaid quantity is still a debate, stop. Do not run rupee math on a moving day count. Close attendance exceptions and leave decisions first, derive unpaid days under policy, freeze, then calculate. The payroll-run checklist is the happy path after inputs are locked. Arguing LOP rupees on payslip day usually means the day count was not frozen.

Name the unpaid code the rupee engine will read. Leave without pay and attendance-derived unpaid absence can be different facts that map to one deduction line — or to two, if you insist on seeing them separately. The naming split lives on LWP versus attendance LOP. Do not deduct the same calendar day twice because two teams used two slang words.

Half-days and other fractions are still quantities. If policy yields 0.5 unpaid, the rupee step multiplies the day rate by 0.5. Do not round the days in a hallway and the rupees in another.

What the day rate is taken from

Write which earnings LOP applies to. Many offices apply unpaid days to a defined set of monthly earnings (for example the lines that make up the monthly gross you treat as attendance-linked). Others apply it only to basic, or to basic plus named allowances. That choice affects every rupee. It is template design until a binding rule you have reviewed says otherwise. This page does not pick a wage definition for you.

Do not silently apply LOP to one-off bonuses that were never meant to be daily-rated, or skip it on a line employees thought was monthly. If a component is outside LOP, say so in the structure notes so payroll and HR do not reverse-engineer it from a surprise net.

Statutory components are calculated from bases your configuration defines. Changing the earning that LOP reduced will change those bases for the period. That is a consequence of the method, not a separate “LOP tax.” Verify statutory rules on official materials; do not invent rates here.

Three common divisors (policy, not law)

A divisor is the number of days you pretend the monthly earning represents. The day rate is (amount subject to LOP) ÷ (divisor). Unpaid rupees are day rate × unpaid days. The same unpaid days produce different rupees under different divisors. That is why two employees with the same unpaid days and the same monthly amount can see different nets if you mixed methods across entities or months.

Calendar days in the month

The divisor is 28, 29, 30, or 31 according to that month. February and 31-day months do not share a day rate. Employees notice this when two unpaid days in February cost more than two unpaid days in a 31-day month, for the same salary line. If you use this method, say so in the SOP so the “why is March cheaper per day?” ticket has an answer.

Paid days (or working days) in the month

The divisor is the count of days your policy treats as payable in that period — often rostered working days, sometimes after subtracting weekly offs and holidays your policy does not pay as working days. This needs a calendar that attendance already uses. If “paid days” is a different list from the shift calendar, you will fight about the divisor after you already fought about the unpaid count.

Paid-day divisors move when a month has more holidays. Write whether that is intended. Do not switch to calendar days in a festival month because someone disliked the rupee result.

A fixed 30

Every month uses 30 as the divisor, including February. The day rate is stable across months for a stable salary line. The trade-off is that the method does not match the actual length of the calendar month. Teams pick it for simplicity. It is still not presented here as Indian law.

Other divisors exist in the wild (fixed 26, and so on). If you use one, write it. Do not copy a number from a forum because it “sounds standard.”

Hypothetical illustration (not law, not a payslip template)

The figures below are an illustration to show how the divisor changes rupees. They are not a recommended salary, not a legal wage, and not Dayzen’s default. Assume, for this example only:

• Monthly amount subject to LOP: 30,000 rupees (hypothetical).
• Unpaid days already frozen: 2.
• Month used for calendar-day comparison: a 31-day month.
• Paid-day count used for the third column: 22 (hypothetical roster count for that month).

Method (policy choice)	Divisor in this illustration	Day rate (30,000 ÷ divisor)	LOP rupees for 2 unpaid days
Calendar days in that month	31	967.74 (rounded here only for display)	1,935.48
Fixed 30	30	1,000	2,000
Paid days in that month	22	1,363.64 (rounded here only for display)	2,727.27

Same person, same unpaid days, three different LOP amounts. Rounding in a live run must follow your written rounding rule; the decimals above exist only to show the split. Do not paste this table into an employee handbook as a right. Do not tell an inspector this is the national formula.

If your unpaid quantity were 0.5 instead of 2, each LOP rupee column would be one-quarter of the two-day figure under the same divisor. The method does not change; only the quantity does.

Joiners, leavers, and unpaid days in the same month

Partial-month employment is a different arithmetic problem (which days of the month were employed). Unpaid days during the employed stretch are this page. Do not use LOP rupees as a substitute for proration of a mid-month joiner who was never in the roster for the first half. Do not “LOP” a leaver for days after last working day if the status change already stopped pay. Status and last working day belong on the employee record payroll will read.

If both proration and LOP apply in one period, write the order: typically pay only employed days, then apply unpaid days that fall inside those employed days, without double-counting the same date as both “not employed” and “unpaid absence.”

What to write in the SOP so the run is repeatable

1. Which unpaid codes payroll reads (one mapped deduction, or labelled splits).
2. Which earning lines are subject to LOP.
3. Which divisor applies, including how February and 31-day months work if you use calendar days.
4. How half-days and other fractions enter the quantity.
5. Rounding: per line, on the LOP total, or on net — pick one.
6. Whether a revision this cycle or a next-cycle adjustment is used when a day count was wrong after lock.

Publish that SOP where payroll and HR both look. If only the implementer knows the divisor, every new payroll admin will “fix” February.

Payslip presentation

Employees should see either unpaid days, LOP rupees, or both. Days without rupees produce “why was I cut.” Rupees without days produce “what did I miss.” The payslip is still a calculation document, not a punch calendar. Point disputes at the frozen attendance and leave records first, then at the divisor if the days are agreed and the money is not.

Do not hide LOP inside a generic “other deduction” if you can name it. Named lines reduce tickets and make the next-cycle correction easier to explain.

What this page will not do

It will not restate sandwich-leave mechanics, regularisation queues, or how absence becomes an unpaid code. Those stay on the LOP handoff guide and attendance/leave articles. It will not publish a lawful-deduction cap, a minimum-wage interaction, or a labour-code wage formula. If those questions matter to your establishment, take them to SME review with your actual structure and divisor in hand.

It will not claim Dayzen files statutory returns or pays the bank. Calculation can reduce earnings for unpaid days and then compute configured statutory amounts on the result. Filing and disbursement remain separate owners.

---

Know the unpaid days, name the earnings LOP applies to, name the divisor, multiply, round as written. Calendar days, paid days, and fixed 30 are methods, not a nationwide legal constant. The illustration above is hypothetical. How days become an input stays on the attendance-to-payroll LOP guide. How a pay run is executed stays on the payroll-run checklist. Dayzen calculates; it does not file or bank-pay.

If two entities in the same group use two divisors, say so on each entity’s SOP. Silent mixing is indistinguishable from a bug, and employees will not believe the PDF until you can show the method in one paragraph.