Dayzen HRMS + Project Management System — people ops and delivery in one product family.

See all modules
Dayzen

Payroll

Prorating pay for joiners and leavers

Published 9/23/2026 · Updated 9/23/2026 · Dayzen

Proration is paying only the days of the month the person was employed, using a written day-count method. Joiners and leavers both need it. This is not the Full & Final settlement workflow — that stays on the FNF guide. Do not present one divisor as Indian law. Attendance status and last working day must match the employee record payroll will use.

Key takeaways

  • Partial-month math ≠ FNF process.
  • Write the divisor.
  • Do not invent FNF timing law.

Proration is paying only the portion of the month the person was employed, using a written day-count method. A joiner who starts on the twelfth and a leaver whose last working day is the twelfth are both partial-month people. They are not the same process as Full and Final settlement. Settlement is the exit package: remaining pay, recoveries, leave treatment as you have defined it, documents, and handover. That workflow stays on the full and final settlement process. This page owns the arithmetic of the incomplete month.

Do not present one divisor as Indian law. Calendar days in the month, paid days, or a fixed thirty-day month are company methods until a binding instrument you have reviewed says otherwise. Do not invent a statute for how many days after exit you must pay, or by which date FNF must complete. Those timing questions are not this article. Verify any legal deadline that applies to your establishment on official materials for that period, with advice if you need it. Dayzen payroll calculates; it does not file returns or pay the bank. Joining dates that payroll will trust should match the employee record created in onboarding, not a chat “they came last Tuesday.”

What you are actually counting

Partial-month pay needs three facts before any rupee formula: the period start and end you call “this month,” the person’s employment start (for joiners) or last working day (for leavers), and the divisor you will use to turn a monthly figure into a day rate. If any of those three is missing, people argue about the result even when the calculator is honest.

Employment start is the date the person is on payroll, not the date the offer was accepted and not the date the laptop was issued. Last working day is the last date you will treat as employed for salary, which should match the attendance and exit record — not the date the resignation letter was written, and not a manager’s preferred story. If the person is on notice and still working, they are not yet a leaver for this arithmetic. If they have stopped work but you have not recorded last working day, payroll will either overpay a full month or underpay a gap you cannot explain.

Unpaid absence inside the partial month is a separate input. A joiner who starts on the tenth and is unpaid-absent on the twentieth needs both proration of the month and LOP treatment of that day, using the methods you published. Do not “net it out” by shrinking payable days in an undocumented way. Days payable from employment span, and unpaid days from attendance and leave, should be visible as two steps.

The divisor is a policy choice

A day rate is monthly salary (or the earning head you prorate) divided by a number of days. Offices commonly choose among:

  • Calendar days in that month. February and a 31-day month produce different day rates for the same CTC. This tracks the actual month. It also means two joiners with the same CTC and the same number of employed days in different months will not receive identical rupees.
  • A fixed 30-day month. Every month uses the same divisor. This is simple to explain. It does not match calendar length. In a 31-day month a full-month employee paid on 30 can look slightly inconsistent next to a leaver paid on calendar — unless you apply the same 30-day rule to everyone, including full-month staff, which most offices do not.
  • Paid days or working days in that month. The divisor excludes weekly offs and holidays, or uses rostered working days. This can feel fair to shop-floor teams. It is harder to explain when rosters differ by site, and it must not be confused with “only count days they punched.” Employment span and attendance are still different facts.

Write the choice in the payroll policy, with one sentence on whether all earning heads use the same divisor. Some offices prorate basic and HRA and pay a full-month statutory or benefit line; others prorate everything that is a monthly earning. There is no single correct mix on this page. There is only a requirement that the mix is named, and that statutory configuration follows official rules you have checked for the period — not a remembered fraction.

Do not switch divisors employee-by-employee to “make the number nice.” If you ever use a different method (a sign-on guarantee, a holdover from a previous employer’s practice), record it as a written exception for that person and period, then return to the default.

Joiners: first month only

For a joiner, payable employment days usually run from the joining date through the last date of the pay period, inclusive, unless policy says joining day is unpaid (rare, and it must be in the offer). If they join on the first, they are not a proration case. If they join on the last calendar day, they are still a proration case: one day, using the same divisor.

Worked example of the idea, not a legal formula. If the month has 30 calendar days and the person joins on the 16th, calendar-day policy that counts the 16th through the 30th inclusive yields 15 employed days, and the prorated earning is the monthly amount times 15 divided by 30. Do not mix a 31-day count with a 30-day divisor unless that mix is written. Inclusive dates and the divisor must exist before anyone calculates. Variable first-month lines follow their own owner: a joining bonus may be a full one-off even if salary is prorated. Incomplete punches in week one are not unpaid days until attendance policy and regularization cutoff have run. Late activation is an operations defect, not a second proration method.

Leavers: last working day, not a mood

For a leaver in a normal pay cycle (not the FNF package), payable employment days usually run from the period start through last working day, inclusive. If last working day is the last calendar day, they are not a proration case for that month. If they worked one day in the month and exited, they are still a proration case.

Last working day must match attendance. If the calendar shows present after the recorded LWD, either the date is wrong or the punches are wrong. If the calendar shows absence before LWD, those days may be leave, weekly off, holiday, or unpaid — each with its own rule. Proration does not replace that classification. It only limits the month to the employment span.

Notice served, notice waived, and garden leave change whether a day is still employed. They do not tell you the divisor. Do not fold notice recovery into prorated salary as a silent haircut — name that recovery. The FNF guide owns how settlement assembles those lines. A mid-month leaver still in a regular run needs this arithmetic so the month is not paid in full by inertia. Do not invent a legal number of days by which settlement must finish, or a mandatory hold-back of the last month. Holding the last cycle until assets return is a process choice with risk you should review — not a formula this article will mint.

Same method for both, then freeze

Use the same divisor for joiners and leavers unless you have a documented reason not to. Employees compare notes. A joiner paid on calendar days and a leaver paid on a fixed 30 in the same company will produce a grievance that is expensive to unwind. Publish a one-page note: inclusive dates, divisor, which heads prorate, how unpaid days stack, and where last working day is stored.

Sequence with the rest of the month. Attendance and leave close so unpaid days are known. Employee master shows joining date or LWD. Payroll applies the proration method, then statutory lines as configured on the prorated (or written alternative) bases. Then you review and lock. The happy-path order of a run remains the payroll-run checklist; this page only supplies the partial-month money rule inside that calculation. Product capability for running those calculations, including LOP, advances, and payslips, lives on Dayzen payroll.

If joining date or LWD is corrected after lock, that is not a new proration theory. It is a draft-versus-lock problem: hold and recalculate this cycle under a written exception, or post a next-cycle adjustment. Do not quietly reopen a locked month because someone found a wrong date in email. Fix the master data going forward either way.

What not to mix into this page

Leave encashment, asset recovery, gratuity eligibility, and tax on settlement can share a month with prorated salary. They are not proration. A joiner’s first-month statutory treatment follows configured methods and official rules — this page will not invent a first-month exemption. Daily-wage people paid on days worked are not this article’s case. This page is for monthly-salaried joiners and leavers.


Proration is inclusive employment days in the pay period, divided by a divisor you named, applied to the earning heads you named. Joiners use joining date; leavers use last working day. It is arithmetic, not the settlement workflow, and not a substitute for attendance status. Keep FNF process on its guide, keep joining identity on onboarding, and keep calculation in payroll — without minting a timing law this page does not have.

See Dayzen in a walkthrough

Book a demo to evaluate Dayzen HRMS with your own processes.