Leave without pay versus attendance LOP

Leave without pay (LWP) and attendance loss of pay (LOP) can hit the same rupee line. They are not the same fact. LWP is usually an approved unpaid leave type: someone applied, a named approver said yes, and no paid balance was spent. Attendance LOP is unpaid absence from the time record after punches, regularisation, and leave are applied. Confusing the two words in a WhatsApp thread is how the same day is deducted twice, or how an unapproved gap is dressed up as leave after freeze.

This page names the two inputs and how they should map. It does not restate the attendance-to-payroll handoff. That pipeline — close attendance, close leave, produce unpaid days as an input — belongs to attendance to payroll LOP. Once unpaid days are known, turning them into rupees belongs to the sibling LOP days to payroll amount. Leave applications live in leave management. The pay run that consumes the mapped code lives in payroll.

Two facts, one possible payroll code

Input	What happened	Who decided	Typical system home
LWP	Unpaid time away was requested and approved as leave	Employee plus leave approver	Leave ledger
Attendance LOP	The time record still shows unpaid absence after leave and regularisation	Attendance rules plus close	Attendance outcome

Payroll does not need two philosophies. It needs a mapped unpaid code (or a documented pair that cannot overlap on the same date). If LWP days and attendance LOP days both flow as “unpaid days” into the same deduction, that is fine — as long as a calendar date cannot appear in both lists. If they flow as two deduction lines with no uniqueness rule, you will double-cut people who applied for unpaid leave on a day attendance also marked absent.

Write the uniqueness rule in one sentence: a date is either LWP, or attendance LOP, or paid presence / paid leave — not two unpaid stories at once.

LWP is a leave decision

LWP (or an equivalent unpaid leave code you actually use) is a policy option. Someone may apply for it when paid balances do not apply, are exhausted, or are not allowed for those dates. The application should name dates, half-day if used, and that the type is unpaid. The approver is deciding coverage and eligibility, not inventing a punch. After approval, the leave calendar should show unpaid leave, and attendance should not still treat the same day as unexplained absence waiting for a second deduction.

LWP is not “HR will fix payroll later.” If the person needed unpaid time and nobody applied, you do not have LWP. You have a gap in the time record. Forcing a backdated LWP after freeze to hide auto-absent is a different operating choice — write whether you allow it, until when, and who may post it. Silent backdating is how unpaid leave becomes a month-end patch instead of a type.

Who may take LWP, notice, and documentation are handbook questions. This page does not invent a statutory unpaid-leave quota. Some establishments treat unpaid absence under applicable rules that this article will not quote from memory. Verify those with a reviewer. For software, the job is: approved unpaid leave is visible, spends no paid balance, and reaches payroll once.

Attendance LOP is a time-record outcome

Attendance LOP is what remains unpaid after the attendance policy has done its work: expected working day, no qualifying presence, no approved leave covering the day, and regularisation either refused or never raised in time. It is not a leave type. The person did not apply to be away; the system (or the clerk) concluded they were not paid-present.

Do not walk the full punch-to-input pipeline here. The owner guide already covers how days become an unpaid input. This page only needs the boundary: if leave already covers the date as LWP, attendance should not also emit LOP for that date. If leave covers the date as paid casual or earned leave, attendance should not emit LOP either. If nothing covers the date, attendance LOP is the honest leftover.

Half-day presence, late marks, and weekly offs are attendance topics. They create or avoid unpaid outcomes; they are not LWP. Do not let a manager relabel a missed punch as LWP because “LOP sounds worse.” The label is a fact type, not a courtesy.

Why teams mix the words

In many Indian offices, people say “LOP” for any unpaid day. Spreadsheets used one column. Managers learned one phrase. Then you introduced a real unpaid leave type and kept using the same slang. Payroll still has one deduction name. The collision is linguistic until it is numeric.

Symptoms:

• An approved LWP day also appears on the attendance exception list as absent.
• Someone is deducted twice: once from the leave export, once from the attendance export.
• Someone is deducted zero times: leave thinks attendance will send it; attendance thinks leave already did.
• A backdated leave type is used to cancel LOP after payslips, with no unique-date check.

The fix is not a new slogan. It is a map: leave unpaid codes, attendance unpaid codes, payroll deduction codes, and a date-level uniqueness test before the pay run.

Map before the pay run, not during it

Name three lists you will actually export or screen:

1. Approved LWP (and any other unpaid leave types) for the period, by employee and date.
2. Attendance unpaid days for the period, by employee and date, after leave has been applied.
3. The payroll unpaid-days input you will actually use.

If list 3 is a union of 1 and 2, prove there is no duplicate date. If list 3 is only list 2 because attendance already consumed leave, prove every approved LWP date is absent from the unpaid attendance leftover (because it was covered) and present as leave on the calendar. If list 3 is only list 1, you have decided that unapproved absence will not reach payroll — which is a coverage hole, not a mapping win. Write which design you run.

Dayzen payroll can consume attendance and LOP as a verified calculation input. That does not choose your uniqueness rule for you. Configuration should follow the map, not the reverse.

Half-days and mixed days

A morning of approved LWP and an afternoon of presence is one calendar date with two outcomes. A morning of missed punch and an afternoon of earned leave is a different mix. Uniqueness is about not charging the same slice twice, not about forbidding mixed days. Use the same half-day language leave and attendance already share. Do not invent a third “unpaid half” unit that only payroll understands.

If policy converts a short punch into half-day unpaid time without a leave application, that conversion is attendance LOP (or an attendance code), not LWP. If the employee applied for unpaid half-day leave, that is LWP. The payslip line might look identical. The audit trail should not.

Approvals, freeze, and backdating

LWP pending at leave freeze is like any other pending leave: decide it, or it is not a leave fact for this period. Attendance LOP at freeze is the leftover absence. Do not keep both pending and hope they cancel. Chat approval of unpaid leave that never hits the queue is not LWP; if the day stays uncovered, it may become attendance LOP — which is the correct outcome of a missing record, not a betrayal.

After freeze, changing LWP to paid leave, or inserting LWP to erase LOP, is an exception path. Name who may do it, whether this cycle or next, and that the date uniqueness test is re-run. Endless relabelling is how unpaid math becomes a negotiation.

What this page will not do

• Will not restate how punches become unpaid days. Use the LOP handoff guide.
• Will not choose your day-rate divisor or paste a rupee formula. Use the payroll-amount sibling.
• Will not invent a nationwide unpaid-leave statute or a required LWP product name.
• Will not treat LWP as a kindness code that avoids recording absence.

LWP is an approved unpaid leave type. Attendance LOP is unpaid absence left on the time record. Map both to one payroll unpaid story per date. Skip the map and you will double-cut or under-cut.

---

A practical test: pick last month’s unpaid days for five people. For each date, say whether a leave application exists, whether attendance still called the day unpaid, and which single payroll code was used. If two systems both claim the date, fix the map before the next run. If neither claims a day everyone remembers as unpaid, you have a hole in close, not a vocabulary problem. Keep the handoff guide as owner of the pipeline, keep rupee math on its sibling, and keep this page as the dictionary that stops managers from using one word for two facts.

Train managers to approve or refuse LWP as leave, and to send punch disputes to regularisation — not to relabel attendance outcomes in a spreadsheet column titled LOP. Employees should see unpaid leave on the leave screen and unpaid absence on the attendance screen, with an explanation of which one will hit pay. When the screens disagree, named close wins until corrected. That is operations, not a slogan about fairness.