The FnF process, end to end
From resignation to the final rupee: what enters a full and final settlement, the sequence it actually follows, the timeline the law expects, and where the process breaks in practice.
Rates and thresholds re-verified 27 July 2026. Statutory figures change by notification, so always confirm against the current official source before acting.
What the settlement comprises
A full and final settlement nets everything owed in both directions when employment ends. Owed to the employee: salary to the last working day, approved but unpaid reimbursements, leave encashment per policy, gratuity where five years of continuous service are complete (last drawn basic+DA × 15/26 × years), and any earned incentive instalments per scheme terms. Owed by the employee: notice-pay shortfall where notice was underserved, outstanding advances and loans, and documented asset recoveries. Statutory treatment applies across it — PF on final wages, ESI where covered, professional tax, and TDS trued up against the year's actuals, and the net figure pays as its own run with an itemised statement.
The timeline the framework expects
The Code on Wages framework points at prompt settlement, commonly read as wages due within two days of exit where rules are in force, with state practice varying and other components following their own clocks (gratuity within thirty days of becoming payable). Practice has historically lagged at 30-45 days, mostly consumed by input-gathering: the last attendance, the pending claim, the clearance checklist. The honest read: the computation was never the bottleneck: the inputs were. A process that closes inputs with the last working day can settle in days, and the settlement date becomes a policy choice rather than an arithmetic backlog.
The process, resignation to payment
-
1
Date the exit and start both clocks
Record resignation date, contractual notice and agreed last working day. The notice-shortfall computation becomes visible immediately, while it can still influence whether notice is served or bought out.
-
2
Run offboarding in parallel
Handovers, asset returns and access revocation proceed as a checklist alongside (not in series before) the financial settlement. Serialising the two is where the classic 45-day drift comes from.
-
3
Freeze inputs at the last working day
Final attendance closes, pending claims approve or lapse per policy, advance balances confirm, and the leave balance fixes as of the exit date. From here the computation has everything it needs.
-
4
Compute, review, approve
Every line derives from records — earnings, encashment, gratuity, recoveries, statutory true-ups. HR adds only policy decisions (a waived recovery, a discretionary payment) as documented entries, then approves the statement.
-
5
Pay, share, archive
The settlement pays as its own run; the itemised statement reaches the employee through self-service; the month's statutory files carry the final contributions; and the record archives with the employment — settlement-grade evidence if the exit is ever contested.
A worked example
A resignation on the 3rd with 60 days' notice and a last working day agreed at 45 days: the statement computes 12 worked days of final-month salary, 18 days of leave encashed on the policy basis, gratuity at 6 years (rounding from 5 years 8 months), less 15 days of notice shortfall at the contract's basis and a ₹4,000 advance balance, with PF on the final wages and TDS trued against the year. Inputs froze on the last working day; the statement was ready the next morning; payment followed on the establishment's three-day standard. The employee questioned one line (the notice recovery) and the statement's citation of the clause and calendar closed the question in one reply.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
Where FnF processes actually break
Four breakpoints account for most late settlements. Input-chasing: the site's last attendance sheet arrives a fortnight late, so everything waits. Serial clearances: finance will not compute until admin clears assets, admin waits on IT, and the employee's money queues behind a laptop return. Reconstructed tenure: gratuity eligibility argued from appointment letters in a cupboard rather than a system record. And the absconder file: no resignation, no process, dues computed never. Each breakpoint is structural, and each disappears when records are live and the financial computation runs parallel to, not behind, the clearances.
The employer's interest in a fast, clean FnF
Slow settlements are commonly defended as leverage; they are actually liability. Delayed wages accrue interest exposure under the framework, disputed exits poison referrals and reviews in hiring markets that read them, and the leverage rarely recovers anything a documented netting would not have. The clean posture wins on every axis: compute fast, net what is documented, pay promptly, and let the statement's completeness (not the delay) protect the establishment. Alumni who were paid correctly and quickly are the cheapest employer-brand asset there is.
Relieving letters and the settlement
The relieving letter and experience certificate ride the same timeline as the money, and withholding them as leverage carries the same risks as withholding wages: the employee's next employer reads delay as dysfunction, yours. The clean pattern: documents issue when the checklist completes, the settlement pays on the standard, and neither hostage-takes the other. Establishments with computed settlements issue both together because nothing is waiting on arithmetic.
How payroll software applies this
PeopleDeck runs this exact sequence: exits dated in the system start the visible notice computation, offboarding checklists run in parallel, inputs freeze at the last working day, and the settlement statement computes from records with every line's working shown — paying as its own locked run and archiving with the employment. The FnF computation itself is covered in depth on the full & final settlement use-case page.
Go deeper: FnF settlement software · Gratuity calculator · Onboarding & exits
Primary sources: Ministry of Labour & Employment · EPFO
Maintained by Databus Technology Solutions against the source notifications; the verification date above is refreshed whenever a figure changes. This guide explains rules and mechanics; it is not legal or tax advice. PeopleDeck applies statutory rates and generates upload-ready files; it never files returns on your behalf, and positions on contested questions belong with your consultant.
Frequently asked questions
What is the legal deadline for FnF settlement?
The wage-code framework points to two days for wages where rules are notified, thirty days for gratuity, with state rollout varying. Whatever the binding date in your state, the defensible posture is a documented, prompt standard, and a computed statement makes promptness cheap.
Can the employer withhold FnF for pending clearances?
Recoveries that are documented (advances, assets per policy) net into the statement lawfully. Blanket withholding of earned wages as leverage is the pattern that loses disputes; the clean path is computing what is owed, netting what is documented, and paying the difference.
Is notice-pay recovery legal?
Where the contract provides notice and the employee serves less, recovering the shortfall per the contract's wage basis is standard and enforceable: the key is that the basis and the day count appear on the statement, cited to the contract clause.
How is leave encashment on exit taxed?
Per the current exemption framework (limits differ for government and other employees) with the taxable portion entering the final TDS true-up. The statement should itemise exempt and taxable portions so Form 16 reconciles.
What happens to PF and ESI on exit?
Final-month contributions compute on final wages and enter the normal monthly files. Afterwards, PF transfer or withdrawal is the employee's own portal action against their UAN — made painless by complete contribution history. ESI coverage simply ends with the employment.
What if the employee disputes the settlement?
The statement is the defence: every line carrying its formula, dates and citations turns a dispute into a line-item check. Undocumented deductions and reconstructed tenure are what turn it into litigation instead.
Should FnF be paid with the regular payroll run or separately?
Separately, as its own off-cycle run; it keeps the exit's statutory lines and TDS true-up cleanly attributable, pays the ex-employee without waiting for month-end, and leaves the monthly run's reconciliation undisturbed. Payroll systems treat settlement runs as first-class for exactly this reason.
Exits settled in days, documented for years.
Applied on every payslip, files generated for upload — per employee, per month.
Start free