The Core Narrative

Every month, the workforce changes shape. New faces arrive with onboarding paperwork, and familiar faces depart with relieving letters. For the payroll team, these 'Joiners and Exits' are the most sensitive inputs of the cycle—because getting them wrong means either overpaying (paying someone who has left) or underpaying (missing a new joiner's salary).

Joiners bring complexity because their first month is almost always prorated. If Priya joins on the 15th, she should be paid for 16 days (or 11 working days, depending on your proration method). But beyond proration, the payroll team must ensure that all master data is in place before the first salary run: bank account verified, PAN captured, UAN generated (or transferred), ESI registration completed, and the salary structure mapped in the system. A single missing field can delay the entire salary.

Exits are even more complex. The last month's salary must be prorated to the Last Working Day. Any pending leave must be encashed (or forfeited, per policy). Loans and advances must be recovered. Notice pay shortfall must be deducted. Assets must be returned. And the Full & Final settlement must be computed with all statutory components—gratuity, bonus, TDS—settled correctly.

For a payroll manager, having a clean 'Joiner-Exit Report' by the 20th of every month is non-negotiable. This report, validated by the HR team, is the starting point for the payroll cycle.

3.6.2

Key Takeaways

Joiner Cut-off: Define the latest date by which a new joiner's data must be in the system to be included in the current month's payroll (e.g., joiners after the 25th are processed in the next month).

Exit Cut-off: Clearly define whether an employee whose last day is the 15th gets paid up to the 15th in the regular run or in a separate F&F run.

Statutory Registration: New joiners must be registered for PF (UAN generation/transfer) and ESI (IP number) before the first salary run to avoid contribution gaps.

Exit Compliance: Update the EPFO portal with the exit date, de-register from ESI, compute final TDS, and ensure the Form 24Q filing reflects the exit.

3.6.3

Practical Scenarios

"A company processing salary for 3 employees who had already resigned a week earlier because the exit information never reached the payroll team—resulting in ₹2.1 Lakhs in overpayment that had to be recovered through legal channels."

"An HR team implementing a 'Payroll Handshake' process where the Recruitment team triggers an automated notification to Payroll the moment an offer is accepted, giving the payroll team a 2-week head start on data collection before the joining date."

Academy Pro-Tips

Create a 'Joiner-Exit Calendar Alert' that automatically notifies the payroll team of all confirmed joins and exits for the current month by the 18th.

Never process an exit employee's salary in the regular payroll run—always route it through a separate F&F process that accounts for all deductions and settlements.

Conduct a monthly 'Ghost Employee Audit'—compare the payroll headcount with the active employee list in the HRMS to catch any exited employees still on the payroll register.

Points to Remember

Overpayment to an exited employee is one of the hardest payroll errors to recover—once the money is in the former employee's account and they are no longer on payroll, recovery options are limited to legal action.
Many HRMS platforms now offer 'Pre-boarding' portals where future joiners can upload their KYC documents, bank details, and tax declarations before Day 1—eliminating the 'Missing Data' problem entirely.

3.6.1