Most companies put real effort into onboarding and treat offboarding as an afterthought. When someone resigns, there's a handover, a farewell lunch, and then the records scatter. Six months later a former employee's PF claim gets rejected, or the labor commissioner asks about a settlement, and nobody can find the paperwork because it lived in a departed manager's inbox.
Looking for HR software?
Check out Techimply's List of the Best HR Software in India for your business.
That gap has become considerably more expensive recently. India's four labor codes came into force on 21 November 2025, and one change in particular rewrote how exits have to work: the settlement timeline that most companies ran on for decades is no longer compliant.
This is a practical look at what offboarding software actually needs to handle, why the compliance clock now runs much faster than most processes were designed for, and which records you have to keep when someone leaves.
The Timeline Change That Broke Most Offboarding Processes
Under Section 17(2) of the Code on Wages, 2019, now in force, all wages owed to a departing employee must be paid within two working days of their last working day. This applies regardless of how the separation happened: resignation, termination, or retrenchment.
The old industry practice was 30 to 45 days. Many companies still run on it. That practice is no longer compliant, and the gap between "how we've always done it" and "what the law now requires" is where the risk sits.
Why two days is operationally hard
The difficulty isn't willingness. It's that payroll cycles are built around monthly calendars, not individual exit dates.
Consider the common case: an employee's last day is the 26th, payroll runs on the 1st, and the settlement clock expires on the 28th. The numbers don't align. You need final attendance, leave balance, any recoveries, TDS computed on full-year income, and a net figure, all before the payroll cycle that would normally produce them has run.
Meeting the window means restructuring the sequence rather than working harder at the old one. In practice, that means the clearance process has to start when the resignation is accepted, not when the last day arrives, and the settlement calculation has to be decoupled from the monthly payroll run.
What doesn't change
One important nuance: gratuity keeps its own clock. Under the Payment of Gratuity Act, 1972, gratuity is payable within 30 days of exit, and that hasn't changed. It's mandatory for employees with five or more years of continuous service, and under the new codes, fixed-term employees become eligible at one year.
So you're managing two timelines simultaneously: two working days for wages and leave encashment, 30 days for gratuity. Software that treats settlement as a single event with a single deadline will get one of them wrong.
What Full and Final Settlement Actually Includes
Settlement is broader than the last paycheck. The components:
- Unpaid salary for the final period worked
- Leave encashment for unused earned or privilege leave, calculated on the correct basic component with the right divisor
- Gratuity, where eligible, on the standard formula of last drawn salary times 15 times years of service, divided by 26, tax-exempt up to ₹20 lakh for non-government employees
- Pending bonuses or commissions
- Deductions: notice period shortfall, outstanding loans or advances, unreturned assets, and TDS
The calculation errors that cause disputes cluster in predictable places. Leave encashment computed on gross instead of basic. Gratuity rounding applied incorrectly. TDS deducted without accounting for the employee's full-year income and regime choice, which creates liability for both sides. Notice-period recovery applied when the policy didn't actually permit it.
Poor documentation, calculation errors, and unclear notice terms are the most common triggers for settlement disputes. All three are process failures, which means all three are addressable by software that enforces the process.
The EPFO Exit Marking Nobody Explains Correctly
Here's a detail worth getting right, because plenty of offboarding checklists state it incorrectly.
Marking an employee's date of exit in EPFO records matters enormously. Without it, EPFO's system treats the old employment as still active, which blocks the former employee's PF withdrawal and transfer claims. This is the single most common reason a departed employee contacts you angrily eight months later.
But the mechanic isn't what most checklists claim. EPFO generally allows the date of exit to be marked only after roughly two months from the last PF contribution, and the date must be consistent with your contribution record. A date that conflicts with the wage record gets rejected or creates a fresh mismatch.
What this means practically: exit marking is not a same-week task you can close on the last working day. It's a deferred obligation that sits about two months out, which is exactly the kind of thing that falls through the cracks when the person who handled the exit has moved on to other work. Software that schedules the task like task management software for the right date, rather than treating it as part of the exit-day checklist, is doing something a spreadsheet won't.
Also worth knowing: employees can now self-mark exit on the EPFO member portal under specific conditions, given an Aadhaar-verified UAN and the waiting period elapsed. That reduces your exposure, but it doesn't remove your obligation to keep the contribution record clean, because a mismatch on your side blocks their self-service too.
What Offboarding Software Should Actually Do
Trigger the sequence on resignation acceptance
The moment a resignation is approved, the system should notify the payroll system, IT, finance, and admin simultaneously. Sequential email chains are what cause the two-day window to fail, because each handoff adds a day nobody budgeted for.
Run clearance as tracked tickets, not paper forms
The "no dues" process is where exits stall. IT confirms device return and remote wipe. Admin deactivates the access card. Finance checks pending travel claims and advances. Manager confirms handover. Each of these should be a tracked item with an owner and a status, visible on one dashboard.
The failure mode with paper or email clearance is that nobody knows what's outstanding until someone asks, and by then the clock has run.
Compute settlement independently of the payroll calendar
The system needs to calculate the settlement from the exit date rather than waiting for month-end. That means pulling final attendance, verified leave balance, recoveries, and a TDS figure based on the employee's full-year income and declared regime.
Revoke access on a schedule tied to the last day
Access revocation is a security control, not an HR courtesy. Email, systems, VPN, shared drives, and any SaaS tool the employee had. The date this happens should be the last working day, not whenever IT gets to it, and the software should evidence that it happened.
Generate the documents
Relieving letter, experience letter, signed settlement statement, and eventually Form 16. These are the documents former employees request, sometimes years later, and the ones that protect you in a dispute.
The Records You Must Keep, and For How Long
This is the part the article title points at, and the part most companies get wrong by omission rather than intent.
Retain for every exit:
- The resignation letter or termination notice
- The full and final settlement statement, signed by the employee
- An acknowledgment receipt confirming payment
- Bank transfer proof
- TDS deduction details
- PF settlement or transfer filing receipt
- ESI notification, where applicable
- Any correspondence relating to the settlement
- The relieving letter and experience letter issued
Labor law record retention requirements generally run to at least three years, and for practitioners, longer is wiser because gratuity disputes and PF queries surface well beyond that window.
The signed settlement statement deserves emphasis. An unsigned statement is a calculation you performed. A signed one is an acknowledgment that the employee accepted it. When a dispute arrives eighteen months later, that signature is the difference between a closed matter and a labor commissioner conversation.
Why "we have it in email" fails
Email is not a record system. The specific failure: the person who handled the exit leaves, and their mailbox is deactivated under your own access-revocation policy. The records go with it.
A repository with defined retention, access controls, and search is what turns an audit request from a week of archaeology into a query. That's not a nice-to-have at the point an inspector asks; it's the whole difference between compliant and merely well-intentioned.
Where Exits Actually Go Wrong
The settlement is treated as a payroll task: If settlement waits for the monthly cycle, the two-day window is already missed on most exit dates. This is the single most common compliance gap right now, because it's a legacy of a process that was compliant until November 2025.
No single owner: HR handles the paperwork, IT handles access, finance handles payment, and the handoffs belong to nobody. Exits fail in the gaps.
Exit marking forgotten: Because the EPFO task sits two months after the last day, it falls outside every checklist that ends on the last working day.
Assets unrecovered: Laptops, phones, access cards. Easy to track in software, easy to forget in a spreadsheet, and expensive in aggregate.
Recoveries applied without basis: Deducting a notice-period shortfall when the appointment letter doesn't clearly support it invites a dispute you'll lose.
No exit interview record: Not a compliance item, but the one source of information about why people leave, discarded because nobody logged it.
A Practical Exit Sequence
- On resignation acceptance: trigger notifications to payroll, IT, finance, and admin. Confirm the last working day and notice-period treatment in writing. Open the clearance tickets.
- During notice period: run the handover, track asset return, compute a provisional settlement so there are no surprises in the final two days, and confirm the leave balance with the employee before it becomes contested.
- Last working day: revoke access, complete asset recovery, close clearance, and issue the relieving letter.
- Within two working days: pay wages, leave encashment, and other dues. Get the settlement statement signed and retain the acknowledgment.
- Within 30 days: pay gratuity where applicable.
- At roughly two months: mark the date of exit in EPFO once the contribution record permits it.
- Ongoing: retain the full document set for at least three years.
Conclusion
Offboarding stopped being an administrative courtesy and became a compliance deadline on 21 November 2025. Wages are now due within two working days of exit under the Code on Wages, while gratuity keeps its separate 30-day clock, and a monthly payroll cycle cannot meet the first of those without being restructured. The software's real job is threefold: trigger the whole sequence on resignation acceptance so the clock doesn't start already behind, compute settlement independently of the payroll calendar, and retain a complete, signed record set that survives the departure of everyone involved. Get the signed settlement statement. Schedule the EPFO exit marking for two months out rather than assuming it's an exit-day task. Keep the records for at least three years in a system rather than a mailbox. The exits that cause problems are rarely the contentious ones. They're the routine ones where everyone assumed someone else had it covered.
