48-hour FFS compliance in India

Most Indian full and final settlements are not slow because the maths is hard. They are slow because nobody starts them until the employee has already left. Gratuity gets computed after the last working day, clearance emails go out after that, and finance runs the payout whenever the next payroll cycle opens. That sequence worked for years. It does not survive a two-day statutory deadline, which is why 48-hour FFS compliance in India is an operational redesign problem before it is a legal one, and the redesign has to happen inside the notice period, not after it.

Before anything else, a clarification we now spend a surprising amount of time giving on calls. Search "48-hour compliance India" and you will get two unrelated rules tangled together: the two-working-day settlement of wages on exit, and the accident-reporting obligation employers owe under the ESI regulations. They share a rough number and nothing else. One is triggered by a separation. The other is triggered by an injury at the workplace. If your compliance calendar treats them as the same item, one of the two is being missed.

What the New Wage Code Rules Actually Require on Exit

The obligation sits in the Code on Wages, which consolidated the Payment of Wages Act, Minimum Wages Act, Payment of Bonus Act and Equal Remuneration Act into a single wage framework under the Ministry of Labour and Employment. Section 17(2) sets the settlement window: wages payable to an employee who is removed, dismissed, retrenched or who resigns must be paid within two working days.

Two working days. Not two payroll cycles.

According to Ascent HR's insight note on the two-day final settlement requirement, the Government of India brought the four Labour Codes into effect on 21 November 2025, activating the two-day wage-payment obligation at separation. Rule-making and enforcement practice at the state level is still settling, so treat state-specific procedural detail as live rather than fixed. The direction of travel, though, is not ambiguous. What was spread across 29 fragmented laws is now consolidated into 4 Labour Codes, and the operational impact on employers is heaviest exactly where old habits were slowest.

The consequence of missing it is not only the penalty. An unpaid or short-paid final settlement is a wage claim, and wage claims under the Code carry inspector-cum-facilitator scrutiny, employee recovery rights, and the reputational cost of an ex-employee posting the delay publicly. Since labour is a concurrent subject, national labour laws overlap with dozens of state-specific codes that differ by region, industry and company size, so a multi-state employer is defending the same two-day clock in several jurisdictions at once.

The Notice-Period Ledger: Treating F&F as a Live Balance, Not a Closing Task

Here is the organising idea we build exit processes around, and it is deliberately unglamorous. Stop treating the full and final settlement process as a document produced at the end. Treat it as a ledger that opens the moment a resignation is accepted and stays accurate every single day of the notice period.

A Notice-Period Ledger has four running balances, each owned by a named function, each updated as facts change rather than reconstructed at the end:

Earnings balance. Unpaid salary to the last working day, leave encashment against the live leave balance, pro-rata bonus, and notice pay if the company is paying in lieu. All of these are computable on day one of notice and only need re-basing if the last working day moves.

Statutory balance. Gratuity calculation using verified date of joining and continuous-service eligibility, plus the PF and ESI treatment for the final month. Gratuity is the single most common source of dispute because it depends on a joining date that is often wrong in the master record. Fix it during notice, not after.

Recovery balance. Loan and advance recovery, notice-period shortfall recovery, asset non-return recovery, income tax and professional tax. This is where finance and HR usually discover they disagree, and the discovery has to happen with weeks to spare.

Clearance balance. IT, finance, admin and department sign-offs, asset returns, and the exit interview. Not money, but it gates the money.

The test of a ledger is simple: on any given day of the notice period, can you produce a defensible net payable figure within an hour? If the answer is no, you do not have 48 hours of work left on the last working day. You have thirty days of work compressed into two.

The Notice-Period Ledger Checklist

Run this against your own exit workflow. Every item should have an owner and a system trigger, not a reminder email.

Day 1 of notice (resignation accepted) - F&F record auto-created and visibly linked to the resignation, not created manually later. - Clearance requests dispatched to IT, finance, admin and the reporting manager simultaneously. - Date of joining, last working day, current gross and PF/ESI/PT applicability verified against the master record. - Gratuity eligibility flag set and years of continuous service confirmed.

Mid-notice - Leave balance frozen for encashment purposes, with any pending applications resolved. - Variable pay and incentive treatment confirmed in writing by the business head, referencing the scheme document. - Loan, advance and asset registers reconciled against the employee's record. - Any notice-period buyout or waiver approved and quantified.

Last working day minus 3 - Clearance status reviewed; unresolved items escalated with a named owner and a deadline. - Draft settlement statement generated component-by-component and reviewed by payroll. - Employee shown the draft breakup, so disputes surface before payment, not after.

Last working day to plus 2 - Assets marked returned, exit interview marked complete. - Settlement moved to processed, approved, and paid outside the monthly payroll run. - Component-wise statement, transaction reference, Form 16 handling and relieving documentation issued together.

If any of this is currently living in a shared spreadsheet and three WhatsApp threads, we should talk.

Variable Pay and Buyouts: Where Two Days Genuinely Break

Every vendor checklist stops at leave encashment because leave encashment is easy. The two components that actually blow the deadline are variable pay and notice-period buyouts, and almost nobody writes about them.

Variable pay fails the clock because it depends on a business input that is not owned by HR. A quarterly incentive tied to collections cannot be computed until collections close. If your scheme document says "payable on declaration of results" and results are declared in the following quarter, you have a structural conflict with a two-day wage settlement. The clean fix is to define, in the scheme document itself, an exit-treatment clause: either a pro-rata payout computed on last-known achievement and released with the settlement, or an explicit separate payment schedule for performance-linked amounts that are not "wages" under the Code. Ambiguity here is a wage claim waiting to be filed.

Notice-period buyouts fail for a different reason. When an employee shortens notice, the last working day moves, and every date-dependent figure in the ledger moves with it: leave accrual, pro-rata bonus, gratuity service, the final month's PF wage. Teams that recompute manually get one of the four wrong. Something we see repeatedly in Indian payroll compliance work is that employees rarely argue with the net figure at all. They argue with the one component nobody explained, and recovery lines are the usual suspect.

Automating Exit Clearance: What a Digital FFS Compliance Workflow Looks Like

An automated FFS process earns its keep on the exception, not the happy path. So take the exception.

An employee resigns with a laptop, an outstanding advance, and eleven days of unused leave. In Human Maximizer, the resignation routes up the reporting chain; a single rejection stops it, unanimous approval creates the settlement record automatically in pending status and notifies HR. Clearances from IT, finance, admin and HR are tracked as separate states, and the laptop sits as an open asset until it is marked returned. Suppose IT never closes its clearance. The record cannot progress to processed, and it is visible as a blocked item to HR days before the last working day, rather than surfacing as a surprise on payout morning. When HR fills the settlement form, every component sits on its own line, and the system recomputes gross, total deductions and net payable on each save, so editing the advance recovery does not leave a stale total behind. Processed settlements are then batched in a separate payroll workspace with per-employee transaction IDs, released outside the monthly cycle, and marked paid and completed.

That last point is the one most teams underestimate when evaluating an employee exit management system. If your payroll can only pay in a month-end run, no amount of workflow automation gets you to two days.

Contract Versus Code, and Where Automation Stops

A statute beats a clause. If your employment agreement says settlement will be completed within 45 days, that clause is unenforceable to the extent it conflicts with the Code on Wages, and it should be amended at the next offer-letter revision rather than defended. The same applies to policies that make payment conditional on clearance: you may recover for unreturned assets, but you cannot indefinitely withhold earned wages while waiting for a sign-off.

Three honest limits on HRMS exit management, from our own deployments:

Our settlement workspace flags pending cases older than 45 days as overdue. That threshold was calibrated to the pre-Code norm and is a backstop, not your deadline. Under the two-day rule, an item sitting in that queue for a week is already a failure, so teams should be watching the daily pending list, not the overdue flag.

Disciplinary exits and cases involving alleged financial loss need legal judgement on what may lawfully be withheld. Software should hold the case and document the reasoning; it should not decide it.

And no automation repairs a bad master record. If the date of joining is wrong, the gratuity calculation is wrong, faster.

Understanding FFS: What the Term Actually Means in Payroll

In the context of Indian payroll and human resources, FFS stands for Full and Final Settlement. It refers to the comprehensive process of calculating and disbursing all outstanding dues to an employee upon their separation from an organization. This process is not merely a final salary payment; it is a reconciliation of the entire financial relationship between the employer and the departing staff member.

When an employee leaves, the FFS calculation must account for several distinct components. These include the pro-rata salary for the final month, encashment of any remaining earned leave, and the payment of statutory gratuity if the employee has completed the required years of continuous service. Additionally, the settlement must factor in any applicable bonus payments, recovery of outstanding loans or salary advances, and the adjustment of notice period pay if the employee is buying out their notice or if the company is paying in lieu of notice.

From a compliance perspective, the FFS is the final ledger of the employment contract. Because it involves the deduction of professional tax, income tax (TDS), and the final contribution to Provident Fund and ESI, it requires precise coordination between the HR and finance departments. Under the current labour codes, this settlement is no longer a back-office task to be completed at the convenience of the next payroll cycle. It is a statutory obligation that must be finalized within two working days of the employee's last working day. Treating the FFS as a live, ongoing calculation throughout the notice period is the only way to ensure that the final payout is accurate, compliant, and ready for disbursement within this strict legal window.

Frequently Asked Questions

Is the 48-hour full and final settlement mandatory, or just good practice? It is a statutory requirement under Section 17(2) of the Code on Wages, administered by the Ministry of Labour and Employment. Commentary from practitioners tracking the change notes that employers must complete full and final settlement within two working days of an employee's exit. Company policy stating a longer window does not override it.

Does it apply to terminations as well as resignations? Yes. The provision covers removal, dismissal, retrenchment and resignation alike. Practically this means one universal exit workflow is safer than separate voluntary and involuntary tracks, because the tighter timeline applies to both.

Is this the same as the 48-hour accident reporting rule? No, and conflating them is common. Accident reporting is a separate obligation owed under the ESI framework when an employment injury occurs. The settlement clock is triggered by separation and concerns wages.

What about PF and gratuity withdrawal, which take longer than two days? The two-day obligation is on wages payable by the employer. PF withdrawal runs on the member's claim through the EPFO and follows its own timeline. Gratuity payable by the employer, however, forms part of the exit dues you should be computing during notice.

Go back to that ledger. The organisations that will clear a settlement in two days are not the ones with faster calculators; they are the ones for whom the calculation was finished before the employee's badge stopped working. Since 21 November 2025, every exit your team processes the old way is a wage claim with a date stamp on it. If your last five settlements each took three weeks, the sixth one is the audit. See how Human Maximizer handles it.

---

Does the FFS amount include the final month's salary or is it separate?

The FFS amount includes the final month's salary along with all other terminal benefits like leave encashment and gratuity. It is a consolidated payment that settles all financial obligations between the employer and the employee at the time of exit.

About the Author & Reviewer

Nishant Tandon — Co-founder & Lead Partner, Razor Infotech
Nishant Tandon is Co-founder and Lead Partner at Razor Infotech, with over a decade in IT, customer support and business operations, helping SMEs achieve cost efficiency, stronger customer experience and scalable, sustainable growth.
Connect on LinkedIn

Reviewed & approved by Sameer Hameed — Founder & Chairman, Razor Infotech
Sameer Hameed is the Founder & Chairman of Razor Infotech, where he is guiding the creation of Human Maximizer. An entrepreneur across technology, real estate, mining and travel, he builds organisations on clarity, trust and responsible growth — on the belief that businesses grow only when the people behind them grow.
Connect on LinkedIn

Human Maximizer is built by Razor Infotech in New Delhi, India (founded 2019). About Human Maximizer.