How half-day leave deductions usually work

A half-day leave deduction is usually 0.5 of one unit from the leave type the employee chose, for either the first block or the second block of that day’s shift. The unit is typically a day of that type (casual, sick, earned, or another policy type). The block is morning or afternoon as your shift definition names them — not “before lunch in the canteen sense” unless the shift actually splits there. This is operational math most Indian offices use. It is not a statutory formula. Applicable rules and your policy still sit above the arithmetic.

Half-day leave is not the same as a half-day attendance mark that never touches a leave ledger. If someone worked a short day, arrived late, or left early, you may record attendance without spending leave — or you may require leave to cover the missing block. That fork is half-day attendance versus leave. This article stays on the deduction when the person did apply leave for a half shift.

What “half” is attached to

Define the split on the shift, not on the clock on the wall in isolation. A 9:30–18:30 shift with a 13:00–13:30 break might treat first half as 9:30–13:00 and second half as 13:30–18:30. A 6:00–14:00 factory shift will split somewhere you write down. Night shifts that cross midnight still have two blocks on that shift instance; do not invent a third “calendar date half” unless your policy really uses calendar dates instead of shifts.

• First half / morning: employee is on leave for the opening block; expected to work the closing block (if they are not on leave then too).
• Second half / afternoon: expected to work the opening block; on leave for the closing block.

If you never publish the split, managers will approve “half day” meaning whatever the employee meant, and payroll will deduct 0.5 against a punch pattern that looks like a full absence. Write the split next to the shift name in the same place people apply from.

Dayzen leave management lets employees apply leave with a half-day option and shows a deduction preview before submit. Use that preview as the shared number: type, 0.5, date, which half. Do not re-argue the 0.5 in chat after approval if the preview already showed it.

The usual ledger math

Approved first-half casual leave on Tuesday: casual balance decreases by 0.5. Approved second-half earned leave on the same Tuesday instead: earned decreases by 0.5, casual is untouched. The date still counts as a leave event for that type. You do not deduct 1.0 “because they came only after lunch” unless policy says a half application is invalid and a full day must be taken — some strict policies do that for certain types; most growing teams do not.

Application	Typical deduction	What attendance should show if they work the other block
First half, one type	0.5 of that type	Present (or on-duty) for second half, with punches or a mark that match the remaining block
Second half, one type	0.5 of that type	Present for first half
Two halves, same type, same day	1.0 of that type (0.5 + 0.5)	Not a working day; equivalent to one full-day leave if both halves are approved
Two halves, different types, same day	0.5 + 0.5 on two ledgers	Still not working; two half applications, not a free extra day

Rounding: keep halves as 0.5 in the ledger. Converting every two halves into a “forced full day” mid-month without showing 0.5 along the way is how employees think they were shorted. If you must round at cycle end, say so; do not round silently on each application.

Combination with punches

The deduction is from the leave approval. Punches tell you whether the other half was actually worked. Four common patterns:

1. Clean half leave: first-half leave approved; in-punch after the second-half start (within grace if you use grace). Leave 0.5; attendance present for second half.
2. Half leave plus missing other half: first-half leave approved; no punches and no regularisation for the afternoon. You still have 0.5 leave. The afternoon is a separate attendance problem — absent, LOP, or regularisation — not an automatic extra 0.5 leave unless someone applies it.
3. Worked both halves after applying: employee came for the full shift but forgot to cancel. Leave 0.5 (or 1.0) still sits until cancellation is approved. Attendance may show present. Fix with cancellation, not by ignoring the ledger.
4. No leave, short punches: not this article’s deduction. That is attendance policy: late mark, half-day attendance, or LOP. See also attendance management for punches, grace, and calendars.

Do not double-punish by deducting 0.5 leave and marking the same block absent as if no leave existed. The approved half should cover that block. The uncovered block is the only one left for attendance rules. Loss of pay, when it happens, should follow closed attendance and leave, as in the attendance-to-payroll LOP handoff — not a special half-day statute.

Working the other half

Policy should say the employee is expected to complete the remaining block, including any core hours you define. If second-half leave starts at 14:00, leaving at 13:00 is not “almost a half”; it ate into the worked block. Either extend the leave application, regularise, or accept a late-out / early-out rule you already wrote for attendance. Do not invent a third half.

Managers sometimes treat “they were in the office at 11” as proof the first-half leave should be cancelled. Only cancel if the employee agrees and the record is updated. Silent cancellation after payroll freeze is how next month’s balance fights start.

Remote or outdoor marks for the working half must follow the same attendance types you use on full days. A first-half leave plus a second-half work-from-home is two facts: 0.5 leave, and a WFH attendance code for the rest — if policy allows WFH that day at all.

Two half-days in one calendar day

Two approved halves on the same date are a full-day equivalent for presence: the person should not also be “present full day.” Deduct both 0.5 amounts. If both halves are the same type, the day’s leave consumption is 1.0. If they split types (sick morning, casual afternoon), both ledgers move. That split is useful when one type is exhausted; it is messy if sandwich or prefix/suffix rules look at “a leave day” without seeing two lines. Configure reporting so the date appears as leave, not as two unexplained 0.5 ghosts.

Block a third application on that date. There are only two halves. A second full-day application on top of two halves is a data error.

If your apply screen only allows one leave type per day, employees will pick one type for 1.0 instead of mixing. That is a product constraint, not a moral failure. Document it so people do not open a ticket for mixed types you cannot store.

Prefix, suffix, and weekly offs (not sandwich law)

A half-day leave on Friday plus a Saturday weekly off is two different objects: a 0.5 deduction, and a roster rest day that should not consume leave by itself. A half-day on Monday after a Sunday off is the same idea in the other direction. Prefix and suffix only become a special debate when intervening weekly offs or holidays are treated as leave — that treatment is owned by the sandwich explainer. If you need the intervening-day rules, read sandwich leave explained. Do not copy those mechanics here.

What this page will say: the half-day’s 0.5 still deducts on the leave date even if the next day is a weekly off. The weekly off does not become 0.5 leave because it touched a half-day, unless a sandwich policy you configured says intervening days are leave — and that is a sandwich configuration, not half-day arithmetic.

Approvals, cancellations, and the 0.5 that never came back

Cancellations must reverse 0.5, not 1.0, when the application was a half. Partial cancellation (“I will come in the afternoon after all”) is a change of application: cancel the half or convert it, with approval. If HR edits the ledger by hand and leaves the application standing, month-end reports will still show leave on that date.

Pending halves at freeze: treat like any other pending leave. Either they are in this period’s paid-day math or they are not. A half pending is not “too small to matter”; 0.5 LOP versus 0.5 paid leave is still a payslip line.

What to write so the 0.5 is boring

Five lines in the leave policy usually suffice:

1. Half-day leave is permitted on types [list], in first or second half as defined on each shift.
2. Deduction is 0.5 unit of the selected type per approved half.
3. The other half must be worked or covered by another approved code (leave, holiday, weekly off, on-duty).
4. Two halves on one date equal a full day away; both deduct.
5. Attendance exceptions on the uncovered block follow attendance policy, not a second leave deduction by default.

Keep half-day leave out of the casual/sick/earned primer except as a usage note. Keep it out of holiday calendar rules except to say holidays are not this deduction. If you need the full policy skeleton, use the leave policy template for section order and put this math in the half-day clause.

---

Half-day leave is a 0.5 debit on a named type for a named shift block. Punches cover the other block or they do not — that is attendance. Two halves fill the day. Weekly offs stay weekly offs unless sandwich policy, documented elsewhere, says otherwise. Preview the 0.5 at apply time so approval is not a surprise.