How to Close an Indian Subsidiary Without Losing Your Team

Winding down an India subsidiary usually reads like a binary choice: keep the entity and its cost, or shut it down and lose the people. There is a third path. You can remove the legal entity and keep every employee by moving them to an Employer of Record (EOR), the organization that becomes their legal employer while your subsidiary goes through strike-off or liquidation. This guide walks through the transfer mechanics, the retention rules under India's labor law, and the closure filings, in the order they actually happen.

Can you close an India subsidiary without losing employees?

Yes. You close the India subsidiary without losing employees by transferring their employment to an Employer of Record before you file for closure. The EOR becomes the legal employer of record, the team keeps working in the same roles, and the entity winds down separately. Handled correctly, tenure, benefits, and payroll all continue without a break.

We have run this sequence for companies that wanted their India team intact but no longer wanted to carry an entity. The key is order: employment moves first, closure filings follow. When those two workstreams are sequenced properly, employees experience continuity, not a termination.

What "keep the team, remove the entity" means

Your India subsidiary is two separate things bundled together: a legal vehicle (a private limited company registered with the Ministry of Corporate Affairs) and a working team. Most people treat closing the company and letting go of the team as one event. They are not.

"Keep the team, remove the entity" means separating those two. The people stay employed in India, doing the same work, on continuous service. The registered company, with its filings, audits, and statutory obligations, is what you dissolve.

Why this differs from a standard shutdown

A standard shutdown terminates employees, pays them out, and closes the entity. Institutional knowledge walks out the door, and if you ever want an India presence again, you rebuild from zero.

The entity-to-EOR route keeps the working relationships. Instead of severance and goodbyes, the team signs new contracts with an EOR and continues. You still close the company, but the human cost, and the future rehiring cost, disappears.

Why do companies wind down their India entity but keep the team?

Companies wind down an India entity but keep the team when the entity's cost and compliance load no longer match the size or purpose of the operation. The talent is still valuable, so the goal is to shed the legal vehicle, not the people. Common triggers are cost reduction, global restructuring, and a team that has outgrown or undershot the entity model.

Cost reduction and compliance overhead

An Indian private limited company carries continuous obligations: statutory audits, annual filings with the Ministry of Corporate Affairs, board governance, monthly payroll compliance, and tax returns. For a small team, that fixed overhead is disproportionate.

Moving employees to an EOR shifts payroll, compliance, and statutory contributions to the EOR's own registrations. You keep the people and drop the entity's recurring administrative and professional-services spend.

Global restructuring, M&A, or acquisition

Restructuring often makes a standalone India subsidiary redundant. In a merger or acquisition, the buyer may not want to inherit a foreign legal entity along with its historical liabilities, but does want the India team.

An entity-to-EOR transition lets the deal close cleanly. The people move to an EOR the buyer contracts with, and the legacy company is dissolved rather than carried onto the new balance sheet.

A small India team that no longer justifies a full entity

Many entities were set up when growth plans were larger than what materialized. A five- or ten-person team does not need a full corporate structure to keep operating.

When headcount is modest, the EOR model fits better. You retain the specialists you spent years building, without maintaining a company just to employ them.

What happens to employees when a company closes in India?

In a straight closure, employees are terminated, and the closing company owes statutory dues. For workmen with at least one year of continuous service, that includes retrenchment compensation under the Industrial Relations Code 2020 (formerly the Industrial Disputes Act 1947), plus a full and final settlement of wages, leave, and vested gratuity. Beyond the cash cost, you lose the team itself.

Retrenchment compensation under IR Code 2020 (formerly Industrial Disputes Act 1947)

"Retrenchment" is India's term for terminating employment for reasons other than misconduct, including closure. Under the Industrial Relations Code 2020 (formerly the Industrial Disputes Act 1947), a workman with at least one year of continuous service is generally entitled to retrenchment compensation of 15 days' average pay per completed year of service, plus notice or pay in lieu, as of July 2026.

Notice to the appropriate government authority may also apply depending on establishment size and state rules. Because these rules sit at both central and state levels, the exact procedure varies by location.

Full and final settlement obligations

"Full and final settlement" (often written F&F) is the closing payment an Indian employer makes when employment ends. It clears everything owed: unpaid salary, encashment of accrued leave, any statutory bonus due, and vested gratuity.

In a closure, the entity must complete F&F for every departing employee before it can demonstrate a clean set of books for strike-off or liquidation. This is a real cash outflow, and it is separate from the ongoing compliance the entity carries until dissolution.

The hidden cost, losing institutional knowledge and rehiring

The line item nobody puts in the closure budget is the team you lose. People who understand your product, your customers, and your processes are expensive and slow to replace.

If you close and rehire later, you pay recruitment fees, onboarding time, and months of lost productivity while new hires ramp. The entity-to-EOR route removes that cost entirely, because nobody leaves.

What is an entity-to-EOR transition?

An entity-to-EOR transition is the process of moving your India employees off your subsidiary's payroll and onto an Employer of Record's payroll, so the EOR becomes their legal employer while your entity closes. The team's roles, pay, and service continuity are preserved. It reverses the usual sequence: instead of setting up an entity to hire, you dissolve one while keeping the hires.

How an EOR becomes the legal employer of record

An Employer of Record is a company that legally employs workers on behalf of another business. The EOR holds the employment contract, runs payroll, and remits statutory contributions under its own registrations, while the employee does day-to-day work for your business.

In a transition, each employee signs a new contract with the EOR. From that date, the EOR is the entity on record with the Provident Fund and ESI authorities (explained below), and your subsidiary is no longer the employer.

Transfer of undertaking (Section 73) in plain terms

Section 73 is the "transfer of undertaking" provision in the Industrial Relations Code 2020, which replaced Section 25FF of the Industrial Disputes Act 1947. It governs what happens to workers when a business or unit changes hands.

In plain terms, as of July 2026: if a workman is transferred on terms no less favorable than before, with continuity of service and no break in tenure, the transfer can proceed on that continuity basis. If those conditions are not met, the workman is treated as retrenched and owed compensation as if terminated. Recognition of prior service in the new EOR contract is what preserves the continuity.

How this reverses the usual "entity-first" playbook

The standard playbook says: incorporate an entity, then hire. Companies spend months and significant cost building a legal vehicle just to put people on payroll.

The entity-to-EOR transition runs that in reverse. You already have the people; you use the EOR so they stay employed, and you retire the entity you no longer need. The employees are the asset you keep, and the company is the overhead you release.

How do you transfer employees from your entity to an EOR?

You transfer employees by engaging an EOR, issuing new continuity-of-service contracts, obtaining written sign-off, running old-entity terminations in parallel, completing full and final settlement, and starting the EOR payroll on the same pay cycle so there is no gap. Closure filings for the entity begin once employees are off its books. The seven steps below run as one connected sequence.

1. Engage the EOR: select and contract your Employer of Record in India, and agree the transfer date and the list of employees moving across.
2. Draft new contracts with recognition of prior service: the EOR issues employment contracts that expressly recognize each employee's original start date and prior service, so tenure carries over with no break.
3. Obtain written employee sign-off: each employee reviews and signs their new contract, confirming acceptance of the transfer on continuity terms (treated as prudent practice, discussed below).
4. Issue old-entity termination or transfer notices in parallel: the subsidiary formally ends its employment relationship on the same effective date the EOR contract begins, documented as a transfer rather than a standalone dismissal.
5. Complete full and final settlement: the closing entity settles accrued dues, including leave encashment and vested gratuity where applicable, so its statutory obligations to employees are cleared.
6. Start the EOR contracts on the same pay cycle: the EOR runs the next payroll on the employee's normal monthly date, so there is zero payroll gap and no missed salary.
7. Proceed with entity closure filings: once employees are off the subsidiary's books and dues are settled, the entity can begin strike-off or voluntary liquidation.

Running transfer and closure in parallel

The transfer and the closure are two workstreams, not one after the other. The employment move needs to complete first, because a company cannot strike off while it still has active employees and open liabilities.

In practice, you begin closure preparation (asset settlement, clearing liabilities, final tax and statutory filings) while the transfer is underway, then file for strike-off or liquidation once the team is fully on the EOR. Sequencing them this way avoids a period where nobody is the employer.

What legal and HR issues arise when the legal employer changes?

Four issues matter when the legal employer changes: preserving continuity of service on no less favorable terms under Section 73, handling employee consent correctly, re-executing intellectual property and confidentiality clauses under the new contract, and confirming the closure's effect on permanent establishment risk. Each has a clean answer if you plan for it before the transfer date.

Continuity of service on no less favorable terms (Section 73)

The transfer must keep terms no less favorable than what employees had: same or higher pay, equivalent benefits, and unbroken service, as of July 2026. If terms drop, employees can claim they were effectively retrenched.

Practically, this means the EOR contract mirrors or improves the existing package and states the original start date. That single clause is what turns a "new job" into a "continued job" in the eyes of the law.

Do employees need to consent?

Written employee sign-off should be treated as prudent practice rather than assumed to be a hard statutory mandate in every case. Even where continuity terms are met, having each employee acknowledge and accept the new contract removes ambiguity and protects both sides.

We always collect signed acceptance. It confirms the employee understood the change, agreed to the terms, and moved voluntarily, which is far cleaner than relying on the transfer provision alone.

Re-executing IP-assignment and confidentiality clauses

Here is the step most guides skip. When the old employment contract terminates, its intellectual property assignment and confidentiality clauses generally terminate with it. Those protections do not automatically follow the employee to the new employer.

The new EOR contract must re-execute IP assignment and confidentiality (and any non-solicitation terms) so your business keeps ownership of work product and protection of confidential information. Skipping this leaves a gap where recent work may not be assigned to anyone.

Does closure change permanent establishment (PE) risk?

Permanent establishment (PE) is a tax concept: a foreign company can create a taxable presence in India through a fixed place of business or dependent agents, even without a subsidiary. Closing the entity does not by itself remove PE risk, and using an EOR does not automatically create or eliminate it.

What matters is how the team operates afterward: their functions, authority to conclude contracts, and where decisions are made. PE analysis should be done on the specific facts, ideally with tax advice, before and after the transition.

Does gratuity and tenure carry over when the employer changes?

Tenure carries over when the new contract recognizes prior service; gratuity depends on how you structure the move. Gratuity vests at five years of continuous service under the Code on Social Security 2020 (formerly the Payment of Gratuity Act 1972). Employees already past five years typically have vested gratuity settled by the closing entity. Those under five years keep their clock running only through contractual recognition of prior service.

Gratuity vesting at 5 years (Payment of Gratuity Act 1972, now Code on Social Security 2020)

Gratuity is a statutory lump-sum reward for long service, roughly comparable to a service-based severance benefit. Under the Code on Social Security 2020 (formerly the Payment of Gratuity Act 1972), it is payable at 15 days' pay per completed year, vesting after five years of continuous service, capped at ₹20 lakh (about $23,500), as of July 2026.

Because it vests at five years, the transition treats two groups differently: those who have already crossed five years, and those who have not.

Settling vested gratuity vs tripartite transfer

For employees past five years, the vested gratuity is a crystallized liability of the closing entity. The standard approach is for that entity to settle it as part of full and final settlement.

The alternative is a tripartite transfer, a three-way agreement among the old entity, the EOR, and the employee, to carry the gratuity liability across rather than pay it out. Absent an explicit tripartite arrangement, vested gratuity is settled by the closing entity.

Preserving the under-5-year clock via recognition of prior service

Employees with less than five years have not vested yet, so a clean break would reset their clock to zero and could cost them the benefit entirely. The fix is contractual: the EOR contract recognizes the original start date so the five-year count continues uninterrupted.

Without that recognition-of-prior-service clause, an employee at, say, four years would restart from zero under the new employer. Getting the clause right is the difference between preserving and forfeiting their gratuity path.

How do you keep payroll and benefits running with zero gap?

You keep payroll and benefits running with zero gap by timing the EOR's first payroll to the employee's normal monthly pay date, continuing Provident Fund contributions under the same UAN, re-registering for ESI promptly, and settling or carrying over leave balances by written agreement. The aim is that employees notice no interruption in salary or statutory benefits.

PF continuity via the same UAN

Provident Fund (PF) is India's mandatory retirement savings scheme, broadly comparable to a US 401(k), managed by the EPFO (Employees' Provident Fund Organisation). Each employee has a Universal Account Number (UAN), a permanent ID that stays with them across employers.

When the employer changes, PF contributions continue under the same UAN, now linked to the EOR's establishment code, so the employee's retirement account carries forward without interruption.

ESI re-registration to avoid a coverage gap

Employees' State Insurance (ESI) is India's contributory health and social-security scheme for lower-wage employees, applicable where monthly wages are at or below the statutory threshold. Coverage is tied to the employer's ESI registration.

When the employer changes, eligible employees generally need to be re-registered under the EOR's ESI registration promptly so medical and benefit coverage does not lapse.

Leave balances, pay out or carry over by written agreement

Accrued leave belongs to the current employer's books. At transition, you choose one of two treatments, documented in writing:

• Pay out: the closing entity encashes accrued leave as part of full and final settlement, and the employee starts fresh under the EOR.
• Carry over: by written agreement among the parties, the accrued balance transfers to the EOR contract so employees keep their days.

Either is defensible; what matters is that it is written down and consistent, not left implicit.

Hitting the same monthly pay cycle

Indian salaries are typically paid monthly, with wages due by the 7th of the following month under the Code on Wages 2019, as of July 2026. The transition should be timed so the EOR runs the next cycle on that same date.

We coordinate the transfer date and the payroll calendar so the first EOR salary lands exactly when the employee expects it. Zero payroll gap is not a bonus; it is the whole point of doing this in sequence.

What compliance steps close the entity after employees move?

After employees move to the EOR, the entity clears its statutory registrations and returns before dissolution: GST deregistration, final TDS returns, state professional tax deregistration, and closure of PF and ESI establishment registrations. Only once these are settled, and assets and liabilities are cleared, can the company file for strike-off or voluntary liquidation.

GST deregistration (Form REG-16, GSTR-10)

GST (Goods and Services Tax) is India's indirect tax registration. To deregister, the entity applies for cancellation via Form REG-16 and files a final return, Form GSTR-10, within three months of cancellation. This closes the entity's indirect-tax obligations.

TDS final returns and professional tax deregistration (state-level)

TDS (Tax Deducted at Source) is withholding tax on salaries and payments; the entity files its final TDS returns to close out the tax year's deductions. Professional tax is a state-level levy on employment, so deregistration is handled with the relevant state authority, and the procedure and forms vary by state.

PF/EPFO establishment closure and ESI deregistration

Once no employees remain on the entity's rolls, its EPFO establishment registration is closed and its ESI registration is deregistered. These steps confirm the company has no continuing social-security liabilities, which the closure route will require.

Strike-off, voluntary liquidation, or EOR-first: which route fits?

The route depends on the entity's finances and history. Strike-off (Companies Act 2013, Section 248) is the lighter route for dormant, clean companies. Voluntary liquidation (Insolvency and Bankruptcy Code 2016, Section 59) is the formal route for solvent companies with assets to distribute. The EOR-first transfer is not an alternative to either; it is the employee step that comes before both.

Legal references above are current as of July 2026.

When strike-off works

Strike-off is the route for a clean, dormant company. Under Companies Act 2013 Section 248, a company can be removed from the register in two ways: the Registrar of Companies (ROC) can initiate removal under Section 248(1) where the company has not carried on business for the two preceding financial years, or the company itself can apply for voluntary strike-off under Section 248(2) after extinguishing its liabilities and passing a special resolution, as of July 2026. Voluntary strike-off is filed on Form STK-2 through the C-PACE (Centre for Processing Accelerated Corporate Exit), the fast-track exit facility operating since May 2023.

It is lighter and cheaper than liquidation, but note that director liability survives strike-off under Section 248(7). Dissolution does not erase obligations that predate it.

When voluntary liquidation is required

Voluntary liquidation under Section 59 of the Insolvency and Bankruptcy Code 2016, governed by the IBBI (Voluntary Liquidation Process) Regulations 2017, is the route when the company is solvent but has assets to realize and distribute, or does not meet the strike-off conditions, as of July 2026.

A liquidator is appointed to settle affairs formally. It is more involved than strike-off, but it produces a clean, court-recognized closure for companies that need one.

Why the EOR transfer happens before either route

Both closure routes require the entity to be free of active employees and open employee liabilities. You cannot strike off a company that still employs a team, and a liquidator cannot close a company with unresolved payroll obligations.

That is why the EOR transfer always comes first. It moves the people to safety, clears the employment liabilities from the entity, and only then does the strike-off or liquidation clock begin.

Is entity-to-EOR cheaper than maintaining your India entity?

For a small to mid-size India team, entity-to-EOR is usually more cost-effective than maintaining the entity, because it removes the fixed compliance, audit, and governance overhead that a subsidiary carries regardless of headcount. Whether it is cheaper for you depends on team size, growth plans, and how much of the entity's cost is fixed versus variable.

Ongoing compliance and overhead removed

Maintaining an entity means recurring costs that do not scale down with a small team: statutory audits, annual MCA filings, corporate governance, payroll compliance, and professional-services fees. Those continue whether you employ five people or fifty.

An EOR converts that fixed overhead into a per-employee fee. The compliance, filings, and statutory contributions move to the EOR's registrations, and you pay for the headcount you actually have.

When does it make sense, and when should you keep the entity?

Entity-to-EOR makes the most sense when the team is small to mid-size, growth is flat or uncertain, or you are restructuring and the entity no longer serves a purpose. The overhead saved outweighs the per-employee EOR fee.

Keeping the entity can be the better call when you have a large team where per-employee fees add up, when you need capabilities an EOR does not cover (for example, holding certain licenses, local invoicing at scale, or specific regulatory registrations), or when the entity is central to a long-term India strategy. The decision is a genuine cost comparison, not a default.

How does Wisemonk support your India entity-to-EOR transition?

Wisemonk is an India-native Employer of Record (EOR) platform that helps global companies hire, pay, and manage talent in India without maintaining a local entity. For an entity-to-EOR transition, we handle the parts that keep your team intact: continuity-of-service contracts with recognition of prior service, PF and ESI continuity, full and final settlement coordination, and re-execution of IP and confidentiality terms under the new contract, all timed to a zero-gap payroll cycle.

We support 300+ global clients and manage 2,000+ employees across India, processing $20M+ in annual payroll, with a 4.8/5 rating on G2.

Our team coordinates the employment transfer while your entity proceeds toward strike-off or voluntary liquidation, so you keep the people and remove the overhead.