EOR Employee Offboarding in India: What Employers Must Know

Offboarding is the part of the employment lifecycle that global teams plan for last and regret most. When the employee sits in India and is employed through an Employer of Record, the picture gets harder: you make the decision, but a different company is the legal employer, and the rules that govern the exit are Indian rules you probably have not read.

The practical problem is not usually the decision itself. It is sequencing. Indian law puts a very short deadline on final wages, a longer one on gratuity, and different protections on different categories of staff. Miss the order and you create a claim out of an exit that was otherwise reasonable.

This guide sets out what has to happen, who does which part, and where the process changes depending on the contract, the role, and the state the employee works in. It is written for founders, People and Operations leads, and HR teams managing an India team without a local entity.

One caveat up front. India's employment framework was consolidated into four Labour Codes that took effect on 21 November 2025, and state level rules under them were still being finalised through 2026. Several points below therefore depend on your state and your contract. For the wider compliance picture, see Payroll Compliance in India: A Guide for Foreign Companies.

What does EOR employee offboarding in India involve?

EOR offboarding in India is the coordinated closure of an employment relationship where your EOR is the legal employer and you are the client directing the work. It covers the exit decision and its evidence, notice, final pay, statutory filings, benefit closure, return of property, revocation of access, and the handling of the employee's personal data.

It is useful to separate three things that often get merged into one word:

• The employment decision: why the relationship is ending, whether it is a resignation, a mutual separation, or an employer initiated termination, and what evidence sits behind it.
• The legal process: notice, final settlement, and the statutory filings that follow from Indian law and from the employment contract your EOR signed with the employee.
• The operational process: handover, equipment recovery, access removal, and the internal records you keep afterwards.

The EOR owns most of the second, you own most of the third, and the first is shared. Getting that split explicit before you start is the single most useful thing you can do.

If you are new to the model itself, our guide to How Employer of Record Works: The Complete Guide 2026 explains where the legal employer boundary sits.

Why does an India exit need more planning than most markets?

Because the deadline for paying final wages is measured in working days, not weeks. In much of the world an exit settles on the next payroll run. In India, the Code on Wages, 2019 requires all wages due to be paid within two working days of the employee leaving, whether the exit is a resignation, a dismissal, or a termination.

The Ministry of Labour and Employment states the rule in its own compliance handbook for employers in plain terms: when an employee leaves an establishment, whether by resignation, dismissal, or termination, the employer is required to pay all due wages within two working days.

Three consequences follow, and they are the reason planning matters:

• Your normal payroll cycle will not meet it: a Friday exit means the money must land by Tuesday, so the calculation has to be finished before the last working day, not after it.
• Clearances have to run in parallel: if IT, finance, and the reporting manager sign off one after another, the window closes before the last one starts.
• Gratuity is on a different clock: it is payable within 30 days of becoming payable, so it does not have to be inside the two day window and usually cannot be.

This is the most common compliance gap we see on India exits, and it comes from applying a US or European settlement habit to an Indian deadline. The termination mechanics themselves are covered in How to Terminate Remote Employees in India: Notice and Pay.

Who is responsible for what: you or your EOR?

Your EOR is the legal employer, so every statutory obligation sits with it. You are the client, so every business decision and every piece of context sits with you. Neither side can push its half across by contract, and the failures we see almost always happen in the handoff rather than inside either column.

Two rows in that table deserve a flag. Equipment recovery depends entirely on who bought and shipped the device, which is a contract question rather than a legal one. And revoking access to your own systems is yours alone, because your EOR cannot see your identity provider.

For the global version of this division of labour, EOR Employee Termination: What Global Employers Must Know covers how the same split works across other markets.

Where the boundary is unclear more generally, Employer of Record vs Own Entity: Which Is Right for You? sets out what changes when you are the employer yourself.

What statutory timelines govern an India exit?

Three deadlines matter on a normal exit, and they run in parallel rather than in sequence. The wage deadline is the tight one, gratuity is the one people forget to fund, and the tax certificate is the one employees chase months later when they file their return.

Two cautions on reading that table. Gratuity is capped at a maximum amount notified by the Central Government rather than a figure written into the Code itself, so confirm the current notified ceiling at the time of the exit instead of relying on the older statutory number many guides still print. And the retrenchment row only applies to some staff, which is the next question.

What counts as wages for these calculations is defined in the Code and is narrower than gross pay, which our guide to Salary Structure in India: CTC Breakup Guide unpacks.

Do India's retrenchment protections apply to your employee?

Often they do not, and this is the most misunderstood point in Indian exit planning. The Industrial Relations Code, 2020 attaches notice and retrenchment compensation to a person who is a worker. That word is defined, and the definition excludes two groups that are common on EOR payroll.

Under the Code, a worker is a person employed to do manual, unskilled, skilled, technical, operational, clerical or supervisory work, but does not include a person:

• Managerial or administrative: a person employed mainly in a managerial or administrative capacity.
• Supervisory above the wage threshold: a person employed in a supervisory capacity drawing wages above eighteen thousand rupees a month, or such other amount as the Central Government may notify.

Read carefully, because the wage threshold is easy to get wrong. It attaches only to the supervisory limb. A senior individual contributor doing technical work is still a worker no matter how much they earn, because no salary cap applies to the technical limb. A team lead in a genuinely managerial role is not a worker even on a modest salary.

So the analysis is about the substance of the role, not the job title on the offer letter and not the salary alone. Where someone is a worker with at least a year of continuous service and the exit is employer initiated, notice and retrenchment compensation of 15 days' average pay for each completed year come into view. Where they are not, the exit is governed mainly by the contract and by the shops and establishments law of their state.

Getting a classification wrong carries its own exposure, which we set out in Employee Misclassification Penalties in India: What It Costs to Get It Wrong.

A further limit is worth knowing. The heavier machinery that requires prior government notice or permission before retrenchment is directed at industrial establishments such as factories, mines and plantations above certain worker counts, so it will not usually reach a small software or services team. Confirm the position for your establishment type and state rather than assuming either way.

Practical takeaway: classify the role honestly before you plan the exit. The same last working day can carry very different obligations for two people sitting in the same team.

For the notice side of this specifically, see Notice Period Rules and Laws for Remote Employees in India (2026), which covers the contractual and state law position in detail.

How do you run an EOR offboarding step by step?

The sequence below assumes a normal exit with a notice period. Compress it for a short notice exit, but do not reorder it, because the wage calculation depends on inputs that only exist once handover is scoped.

Step 1: Agree the decision and the record with your EOR

Tell your EOR what is happening and why, before you tell the employee. Ask them to confirm the contractual notice, whether the role is likely to be a worker role, and whether the reason as documented is sufficient. This is the step that prevents a rushed exit becoming a disputed one.

Step 2: Confirm the last working day and who communicates

Fix the date against the contract rather than the calendar you would prefer. Decide who speaks to the employee, in what order, and what each side will say. In practice the client manager should deliver the business message and the EOR should deliver the employment mechanics, because only one of you is the employer.

Step 3: Issue notice or acknowledge the resignation formally

Your EOR issues the letter, because it is the employer of record on the contract. Keep the written trail complete from here on, including any agreement to waive or buy out part of the notice period.

Step 4: Scope handover and start clearances in parallel

Name the receiving person for each responsibility and set a date for each transfer. At the same time, open the finance, IT, and asset clearances together rather than in series, so that nothing waits on the last working day. Our general Offboarding Process and Best Practices for HR (2026) guide covers the handover mechanics in more depth.

Step 5: Finalise the settlement calculation before the final day

The calculation needs the final attendance, any leave balance to be encashed, any recoveries, and any notice adjustment. Because payment is due within two working days of leaving, this has to be signed off in advance.

The component level detail sits in our guide to Full and final settlement in India: 2026 compliance guide, so we do not repeat the arithmetic here.

Step 6: Close access and recover property on the final day

Revoke single sign on, email, code repositories, customer systems, and privileged credentials on the last working day rather than afterwards. Log what was returned and what was not, because an unreturned device becomes a recovery question and sometimes a data question.

Step 7: Pay, file, and issue documents

Wages inside two working days, gratuity inside its own 30 day window where payable, date of exit filed with EPFO and ESIC, and the exit paperwork issued to the employee. Ask your EOR to confirm each of these in writing rather than assuming them.

Step 8: Run a short post exit review

A fortnight later, check that the provident fund exit date was filed, that the employee received their documents, and that no access remains open. This is a five minute check that catches most of what goes wrong.

What happens to provident fund, ESI, and gratuity on exit?

These three behave differently, and conflating them causes avoidable anxiety for a departing employee. Provident fund continues, employee state insurance stops with a short run off, and gratuity is a one off payment that may or may not be due.

Provident fund

The employee's provident fund balance is theirs and does not need to be withdrawn. Each member holds one universal account number that carries across employers, and on joining a new covered employer they file an online transfer claim to move the previous balance into the new account.

The step that matters to you is administrative and often missed. The employer must file the employee's date of exit in the EPFO system, and until that is done the member cannot transfer or withdraw the balance. If a former employee tells you they are stuck, this is almost always the reason.

Employees' State Insurance

ESI applies where the employee's monthly wages fall at or below the coverage ceiling and the establishment is covered. Contributions stop with the last wage payment, and the scheme provides a limited continuation of certain benefits after employment ends. Whether an individual was covered at all depends on their wage level and the state notification that applies. Current rates sit in Payroll Tax in India: Employer Rates, TDS, and Deadlines.

Gratuity

Gratuity is payable on termination of employment after five years of continuous service, where the exit is by superannuation, retirement or resignation, death, or disablement. There is an important exception: a fixed term employee is entitled to gratuity on the expiry of the contract term after one year of service, on a pro rata basis.

It is calculated at 15 days' wages for each completed year of service, subject to a maximum amount notified by the Central Government, and it must be paid within 30 days of becoming payable. Note the phrasing on the ceiling. The Code does not fix the number itself, so check the current notification rather than quoting a figure from the superseded Act.

For how these sit inside the wider benefit picture, see Employee Benefits in India: Employer Guide 2026.

How should you handle company property, access, and employee data?

Treat these as three separate workstreams with three different owners. Property recovery is contractual, access removal is yours, and data handling is now a regulatory question in India as well as a good practice one.

On property and access, the working rules are short:

• Inventory before you need it: you cannot recover a device you never recorded issuing, so keep the asset list current rather than reconstructing it at exit.
• Separate personal from company data: give the employee a defined window to remove genuinely personal files before the account closes.
• Revoke on the day, not after: and include the systems people forget, such as code repositories, cloud consoles, customer tools, and shared credentials.
• Record what was not returned: and agree with your EOR how any recovery will be handled, because deductions from final wages are restricted to what the law authorises.

That last point is worth emphasising. You cannot simply net an unreturned laptop off the final settlement, because the Code on Wages permits only authorised deductions. Route any recovery through your EOR rather than assuming it can be withheld.

Departing engineers raise a related question about work product rather than devices, which we answer in Does Your US Company Own the IP Your India EOR Developer Writes?.

For the security controls behind all of this, see EOR Data Security: A Global Compliance & Protection Guide.

On employee data, India's Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 are now on the statute book, with the substantive obligations phased to take effect eighteen months from the November 2025 notification. Two points follow for offboarding: personal data should not be kept beyond the purpose it was collected for unless a law requires retention, and employment records generally do carry their own retention requirements, so exit is not a signal to delete everything.

We cover the framework and what it means for a foreign employer in India's DPDP Act for Foreign Employers: A Practical Guide.

What are the most common EOR offboarding mistakes in India?

These are the failures we see repeatedly, and each one is a process gap rather than a legal subtlety:

• Settling on the normal payroll cycle: which quietly breaches the two working day wage deadline on almost every exit.
• Assuming a notice period the contract never specified: employer side notice in India comes from the contract, the applicable state law, and the Industrial Relations Code where it applies, not from a market convention.
• Treating every employee as protected, or none of them: both are wrong, and the answer depends on the worker analysis set out above.
• Forgetting to file the date of exit with EPFO: which blocks the employee's transfer or withdrawal and generates avoidable follow up months later.
• Deducting recoveries from final wages informally: only authorised deductions are permitted, so this has to be handled properly rather than netted off.
• Leaving access live after the last working day: the most common security finding on any offboarding audit, and entirely preventable.
• No written record of the reason: the exit may be perfectly reasonable, but without contemporaneous documentation it is hard to defend if challenged.
• Quoting a gratuity ceiling from the superseded Act: the maximum is set by government notification under the current Code, so verify it at the time.

If you fix only two of these, fix the settlement timeline and the exit date filing. They cause the most trouble for the least reason.

If exits are becoming frequent rather than occasional, the underlying pattern is worth reading against Attrition Rate in India 2026: Trends & Industry Data.

What should you ask your EOR, and what should you do next?

Before your first India exit, put these questions to your provider in writing, because the answers tell you whether their process is built for the Indian deadline or for a generic global one:

• Settlement timing: how do you meet the two working day wage deadline, and what inputs do you need from us, by when?
• Worker classification: who assesses whether an employee is a worker under the Industrial Relations Code, and will you put that view in writing?
• Notice period: what is the contractual notice period for each of our employees, and does any state law add to it?
• Gratuity: who funds and pays it, and how do you confirm the currently notified maximum?
• Statutory filings: when do you file the date of exit with EPFO and ESIC, and how will you confirm it was done?
• Employee documents: what does the employee receive on exit, and how quickly?
• Record retention: how long do you keep employment records after exit, and on what legal basis?
• Data after retention: what happens to the employee's personal data once the retention period ends?

Use the short checklist below as your working template for each exit, and adapt it to your contract and state.

Your next step is narrow and worth doing before you need it. Take one employee on your India payroll, walk their exit on paper against this checklist, and note every question you cannot answer. That list is your actual gap, and it is far cheaper to close now than during a live exit.

If the answers you get are weak, that is a provider question rather than a process one, and How to Choose an Employer of Record: A 2026 Buyer's Guide sets out what to test for.

Where you conclude you need to move provider entirely, How to Switch EOR Providers in India: A Migration Checklist walks through the India specific mechanics.

Where can you verify these rules yourself?

Every statutory point above comes from a primary source, and we would rather you checked them than took our word for it. These are the documents to read, all official and all free:

• Code on Wages, 2019: the two working day rule on final wages sits in section 17, and record retention in sections 19 and 21.
• Code on Social Security, 2020: gratuity entitlement and calculation in section 53, nomination in section 55, and the 30 day payment deadline in section 56.
• Industrial Relations Code, 2020: the definition of worker, and the lay off, retrenchment and closure provisions.
• Compliance Handbook for Employers Under the Four Labour Codes: published by the Ministry of Labour and Employment, which states the exit obligations in plain language.
• EPFO member and employer guidance: the universal account number, the online transfer claim, and the date of exit requirement.
• ESIC contribution and coverage pages: current contribution rates and the wage ceiling for coverage.
• Digital Personal Data Protection Act, 2023 and Rules, 2025: for the employee data points, including the phased commencement dates.

Where a figure carries a currency symbol or a notified ceiling, check the date on the source before you rely on it. Those are the values most likely to have moved since publication.

How does Wisemonk support employee offboarding in India?

Wisemonk is an India native Employer of Record that helps global companies hire, pay, and manage employees in India without setting up a local entity. Offboarding is part of that service rather than an afterthought, because the Indian settlement deadline does not leave room for one.

Here is how we help teams close an India exit properly:

• Exit planning: we confirm contractual notice, role classification, and the last working day before anything is communicated.
• Settlement inside the statutory window: the calculation is completed before the final day so wages are paid within two working days of leaving.
• Statutory closure: provident fund exit date filing, ESI closure, and gratuity assessment and payment where it is due.
• Documentation: relieving letter, settlement statement, and tax certificate issued to the employee.
• Records and data: employment records retained for the periods Indian law requires, and no longer than the purpose supports.

We work with 300+ global clients, support over 2,000 employees, and process more than $20M in annual payroll, with a 4.8/5 rating on G2. EOR pricing starts from $99 per employee per month. If you are still deciding on the model, How to Hire Employees in India Without an Entity: A Guide is the place to start.

Teams that want the full lifecycle view, from hiring through exit, can read India Hire-to-Retire (H2R) Framework for Global Companies.