From EOR to Entity: When a UK Enterprise Should Bring Its India Team In-House

Deciding when to move from an EOR to your own entity in India is a control-and-cost call, and one detail most UK enterprises miss shapes the whole exit: whether your EOR holds its own wholly-owned India entity or runs on a partner network. That single fact decides who holds the employer registrations, whether leaving is a contract novation or a termination-and-rehire, and who you negotiate the exit with. Everything else in this decision follows from it.

When should a UK enterprise switch from an EOR to its own entity in India?

Switch when staying costs more than the control it buys, which in practice means at least one of five triggers has fired: board or investor visibility, local customer contracting, equity on the entity's name, permanent establishment exposure, or your data posture. Until one of those holds and the economics agree, staying on the EOR is usually the right call.

The mistake we see most often is treating this as a spreadsheet exercise with one answer. It is a governance decision with an economic floor underneath it. The five triggers tell you whether control has become worth owning; the break-even formula tells you whether you can afford to own it yet. You need both to agree before you move.

The five-trigger test at a glance

The table below maps each condition to a stay, grey-zone, or switch signal. Read it as a diagnostic, not a scorecard: a single firm switch signal can outweigh four stay signals, because governance triggers are rarely about cost.

Why headcount is only one signal, not the whole test

Headcount is the number everyone reaches for first, and it is the weakest single predictor of when to switch. A thirty-person India team selling nothing locally, granting no equity, and making no decisions that create tax exposure can sit on an EOR indefinitely. A six-person team that signs Indian customer contracts and books revenue locally may need its own entity far sooner.

Cost tells you whether you can bring the team in-house affordably. The five triggers tell you whether you should. When those two answers point the same way, the decision is easy. When they conflict, the governance trigger almost always wins, because a PE assessment or an unbankable equity promise is not a line item you can wait out.

The rule in one line

Stay while the EOR's fees cost less than the control an entity would buy you. Move when a trigger makes that control non-optional, and the break-even formula says the fixed overhead is one you can carry.

For the India-specific version of this comparison, check out EOR vs entity in India.

What's the real difference between staying on an EOR and owning your India entity?

The one variable that actually changes is who holds legal employer liability. On an EOR you buy legal employer status while directing the work yourself; with your own entity you become the legal employer. Speed, cost, and control are all consequences of that single shift, not independent choices, which is why the model you pick is really a liability decision.

Everything a vendor comparison frames as a feature trade follows from where employer liability sits. The EOR can hire in days because it is already the registered employer; your entity is slower because you are building that status from scratch. The EOR fee is predictable because it carries the fixed overhead for you; your entity is cheaper per head at scale because you now carry that overhead yourself.

Buying employer status versus becoming the employer

Buying employer status means a registered India employer runs payroll, provident fund, ESI, professional tax, and TDS in its own name, while you keep every people decision: who to hire, what to pay, how to manage performance, and when to part ways. Becoming the employer means those registrations, filings, and liabilities move onto your own Indian company, and the administrative weight comes with them.

Neither model changes who runs the team. It changes who is legally answerable for employing them. That is the lens to read the whole comparison through.

What you keep either way

You keep the team, the roles, the reporting lines, and every management decision under both models. An EOR does not restrict who you hire or what work they do, and your own entity does not hand you better people. What moves between the two is paperwork and liability, not talent or control of the work.

To see how the EOR route works end to end, check out hiring through an EOR.

Owned-entity EOR versus partner-model EOR, and why it decides your exit

This is the distinction that shapes how hard your exit will be, and it rarely appears in a provider comparison. In our work at Wisemonk, we have seen the exit route hinge entirely on it.

An owned-entity EOR holds its own wholly-owned India entity and carries the employer registrations (EPF, ESI, professional tax, TDS) directly. A partner-model EOR runs on a third-party network, so those registrations sit with a partner you never contracted with. When you move to your own entity, the owned-entity route can often be a clean contract novation that keeps service continuous, while the partner model frequently forces a termination-and-rehire, because the exiting party cannot simply hand over registrations it does not hold. Ask any EOR which model it runs before you sign, because it decides whether your future exit is an administrative handover or a reset.

Because exit depends on who the legal employer is, check out co-employment vs joint employment in India.

What are the five triggers that justify bringing your India team in-house?

Five triggers justify the move, and each is a governance or risk event rather than a cost milestone: board and investor visibility, local customer contracting, equity on the entity's name, permanent establishment exposure, and your data posture. When one fires, the question stops being whether an entity is cheaper and becomes whether you can operate correctly without one.

Board, investor visibility, and group consolidation

Once investors or a board start diligence, "who legally employs the India team" becomes a question with a right answer. An owned India subsidiary consolidates cleanly into group accounts and sits well in an audit; an EOR arrangement can read as off-balance-sheet headcount a buyer or auditor wants explained. If a funding round, acquisition, or group audit is on the horizon, this trigger often fires before any cost argument does.

Procurement and local customer contracting

If you begin selling into India, many Indian customers and procurement processes require a locally registered supplier to contract with and invoice. An EOR employs people for you; it does not give you an India-registered entity to sign customer agreements or raise local invoices. The moment a deal stalls because the buyer needs a domestic counterparty, contracting capability, not employment, is driving the move.

Equity (ESOP) on the entity's own name

A senior hire who wants equity wants it on a share cap table they can actually join. Employee stock options generally need to sit on an Indian entity to be granted and administered correctly for India-based employees. You cannot grant entity equity through an EOR, because the EOR is the employer, not your company. When equity becomes part of a key offer, this trigger can force the decision regardless of headcount.

If equity is already on the table, check out granting ESOPs to India employees.

Permanent establishment exposure

PE exposure is reduced but not eliminated by using an EOR. The risk rises as your India team moves from executing work to making decisions, signing contracts, or booking revenue locally, which is where a UK parent can be treated as having a taxable presence in India. The framework is business connection under India's Income-tax Act 2025, read with the permanent establishment article (Article 5) of the applicable double tax treaty; the specific UK-India treaty thresholds are a question for your tax adviser and are not something we assert here. For a focused read, our permanent establishment risk material is the right starting point.

To test your own exposure in two minutes, take the permanent establishment risk quiz.

Data posture: UK GDPR to India's DPDP

As your India team processes more personal data, two regimes meet: your obligations when moving personal data out of the UK, and India's Digital Personal Data Protection Act (DPDP) once that data is processed locally. We do not state the specific UK international-transfer requirements here, because they turn on facts a data-protection adviser should confirm. The practical point is that heavier India data processing can make a local controller entity cleaner than a vendor-mediated arrangement, and this trigger is easy to overlook until a data map forces it.

For the Indian side of the data question, check out what is the DPDP Act.

When should a UK enterprise NOT switch, and stay on the EOR?

Stay on the EOR when none of the five triggers has fired and the economics still favour it, meaning the entity's fixed annual overhead would exceed what you pay in EOR fees. There is no explicit statutory cap we are aware of on how long you can run an India team through an EOR, so there is no deadline pushing you off it.

Most UK enterprises switch too early, persuaded by a headline headcount number that was never theirs. If the team is executing work, selling from the UK, paying in cash, and processing little personal data in India, the EOR is doing exactly what it should. Carrying fixed compliance overhead to save on per-head fees you can comfortably absorb is a net loss.

Break-even is a formula, not a number

Your crossover point is arithmetic, not a figure you copy from a blog. The formula is:

N = entity annual fixed cost / annual EOR fee per employee

At $99 per employee per month, the annual EOR fee per employee is $1,188.

Divide your entity's fixed annual overhead by that figure and you get the headcount at which the two models cost the same. The reason no single published number is right is that the numerator, your fixed overhead, varies widely by how your entity is run, so the crossover can land anywhere across the low-to-mid tens of employees on illustrative inputs. Treat any band as illustrative only, and run your own overhead through the formula rather than trusting a stated headcount.

To run your own numbers, check out the EOR vs entity calculator.

Transfer pricing, the hidden denominator

The cost most break-even spreadsheets miss sits in the numerator: transfer pricing compliance. An India subsidiary serving its UK parent is a related-party arrangement, which pulls in India's transfer pricing rules, benchmarking, and annual documentation, and those costs are recurring, not one-off. Leave them out and your fixed overhead looks smaller than it is, which drags your computed break-even down and makes an entity look cheaper, sooner, than it really is. Put transfer pricing into the denominator of the real decision and the crossover moves up.

For the full cost anatomy, check out transfer pricing for India, a guide for US companies.

The hybrid as a legitimate end state

Owning an entity is not all-or-nothing. A common and durable arrangement is to run your core India team on your own entity while keeping an EOR for satellite hires, new-state coverage, or short-term roles, so you own what you need to own and stay flexible on the rest. If you are an earlier-stage UK company still testing India, the hybrid can be the destination rather than a stop on the way to one. It is a legitimate end state, not a compromise.

For how UK businesses approach India hiring overall, check out UK companies hiring employees in India.

How much does owning an India entity actually cost a UK enterprise?

Owning an entity adds two costs an EOR never charges you: an upfront setup spend, and a fixed annual compliance overhead that continues whether you hire one person or fifty. The per-head fee disappears; the fixed burden arrives. Modelling the switch means comparing a variable cost you understand against a fixed cost that is easy to underestimate.

The decision-level categories matter more than any single quote at this stage. You are not scoping a vendor; you are deciding whether to take on a standing obligation.

Upfront setup and timeline

Incorporating the Indian company and obtaining its tax and employer registrations is the one-time cost, with a figure that varies by structure and advisers. Plan for a timeline measured in months rather than weeks, typically on the order of three to six months to incorporate and register; note that our own published timing ranges differ across contexts, so treat this as a planning estimate and confirm it for your structure.

For the mechanics of the build itself, check out how to set up a legal entity.

Ongoing overhead

The recurring overhead is where entities surprise people. It includes transfer pricing compliance and documentation, annual FEMA filings, a statutory audit, and GST on intercompany services, among others. As a rough planning figure, fixed compliance and overhead can add a meaningful percentage to your total India spend, and annual HR-plus-compliance costs scale with the size of the operation. These are the line items that make the break-even a real calculation rather than a slogan.

What the spreadsheet misses

The single most common omission is transfer pricing, the denominator we flagged earlier. A spreadsheet that counts incorporation and payroll but leaves out annual TP documentation, benchmarking, and intercompany pricing work understates the fixed overhead and overstates how soon an entity pays off. Build it in from the start, and the honest crossover moves to a higher headcount than the optimistic version suggests.

To price the per-head side of the comparison, check out the employee cost calculator.

Who inside a UK enterprise owns the EOR-to-entity decision?

No one function owns this decision; it is a three-function call. Finance owns the total cost of ownership and the break-even model, Legal and Compliance own permanent establishment, IP, and data exposure, and People own employee continuity through the transfer. When one function decides alone, the move usually reveals a cost, a liability, or a continuity gap the others would have caught.

The failure mode is a finance-led switch that models the per-head saving and misses the PE assessment, or a legal-led switch that fixes exposure and forgets the gratuity and provident fund mechanics. Run it as a committee from the start.

Finance and Operations

Finance owns the number. That means the break-even formula, the fully loaded total cost of ownership on both sides, and, critically, the transfer pricing line that most models omit. Their job is to say not just whether an entity is cheaper per head, but whether its fixed overhead is one the business should carry yet. They also own the modelling tooling and the sensitivity analysis behind the band.

Legal, Compliance, and Procurement

Legal owns the exposure. That is permanent establishment risk under India's business connection rules and the applicable treaty, IP assignment onto the new entity, the UK-GDPR-to-DPDP data posture, and the contracting capability procurement and customers may require. They also vet the exit mechanics, including whether your EOR's owned-entity or partner-model structure allows a clean novation.

People and HR

People own continuity. That is the transfer structure, gratuity and provident fund treatment, notice periods, and the employee communication that keeps a transfer from feeling like a layoff-and-rehire. Their test is whether every employee lands on the new entity with their service, benefits, and trust intact. Get this wrong and the strongest cost case still produces attrition.

Before you plan the employee communication, check out notice periods India actually enforces.

What happens to your India employees when you move from EOR to your own entity?

Done right, employees move by novation, which transfers the existing employment to your new entity and keeps service continuous, so entitlements carry over. Done as a termination-and-rehire, gratuity can reset because the continuous-service clock restarts, although provident fund continuity is preserved through the permanent UAN. The structure you choose decides what employees keep.

This is the part of the move employees feel directly, so it deserves as much planning as the cost model. The mechanics are not interchangeable.

Novation versus termination-and-rehire

Novation substitutes your new entity as the employer under the existing contract, preserving start dates, tenure, and accrued entitlements, and the new entity assumes the gratuity liability as part of the transfer. Termination-and-rehire ends the EOR employment and starts a fresh one, which is administratively simpler for some exits but resets service-linked entitlements. Whether novation is even available can depend on the owned-entity versus partner-model distinction covered earlier.

Gratuity and provident fund continuity

Gratuity in India accrues on continuous service, so a termination-and-rehire can restart that clock and cost employees accrued entitlement unless the transfer is structured to carry the liability across. Provident fund is different: the UAN is permanent and portable across employers, so provident fund records follow the employee regardless of how the transfer is done. This gratuity-resets-but-PF-does-not trap is covered in depth in our EOR versus own entity guide; here it is enough to plan the transfer so gratuity survives it.

IP re-assignment on the new entity

IP needs re-papering onto the new entity, and the two regimes behave differently. For copyright, work created by an employee in the course of employment generally vests first ownership in the employer by default under the Copyright Act 1957, so the right sits with whoever is the employer at creation. Patents carry no equivalent default; an invention needs an express assignment to the employer, so moving employees to a new entity means ensuring assignment agreements run to that entity, not the old one.

For the wider IP picture when you hire in India, check out protecting IP when hiring in India.

How should a UK enterprise time and sequence the move?

Decide six to twelve months ahead of when you want the entity live. Incorporation and registrations typically run three to six months, and the exit and employee handover add time on top, so the clock starts well before you file anything. Treating this as a quarter-long project is the most common scheduling error we see.

Why the clock starts before you incorporate

The long pole is rarely incorporation itself; it is sequencing the exit so no employee falls between two employers. You need the new entity registered as an employer, payroll stood up, benefits enrolled, and the novation papered before the EOR relationship ends. Start that planning while you are still on the EOR, not after you incorporate.

The owned-versus-partner exit difference

The exit you get depends on the EOR structure covered earlier. An owned-entity EOR that holds its own EPF, ESI, professional tax, and TDS registrations can often support a clean novation and a predictable handover. A partner-model EOR, where those registrations sit with a third party, more often forces a termination-and-rehire, which lengthens the timeline and reopens the gratuity question. Confirm which you are dealing with before you commit to a go-live date, and plan the full and final settlement for anyone who does not transfer.

Build-Operate-Transfer as the no-cliff-edge route

If the handover risk worries you, Build-Operate-Transfer removes the cliff edge. The provider stands up and operates your India entity, then transfers it to you once it is running, so you are not switching models and migrating people in the same stressful window. Our entity and capability-centre work supports this route, priced on a custom quote.

If you want the step-by-step version of the move itself, check out transition from EOR to legal entity.

How does Wisemonk support your India team through this decision?

Wisemonk is an India-native Employer of Record (EOR) that helps global companies hire, pay, and manage employees in India without setting up a local entity.

We support 300+ global clients, manage 2,000+ employees and process over $20M in annual payroll, with a 4.8/5 rating on G2, and EOR pricing from $99 per employee per month.

• EOR today, entity tomorrow: run your India team on our EOR now and move to your own entity when the triggers fire, with no gap in employment.
• Build-Operate-Transfer: we stand up and operate your India entity, then hand it over, priced on a custom quote.
• One compliant legal employer: payroll, PF, ESI, professional tax and TDS handled directly, so the transfer to your entity is clean.
• Employee continuity: novation-based transfers that protect gratuity and provident-fund continuity for your India team.
• A named India team, not a ticket queue: direct dealings with EPFO, GST and the tax authorities.

We provide EOR services in India, and we are expanding rapidly into the US and UK markets.

Red Hill Technology Solutions has run its India engineering team on Wisemonk for the past year and a half. They handle payroll and benefits end to end, so I can offer my employees good health insurance without having to master the idiosyncrasies of Indian benefits myself. Payroll cutoff reminders arrive every month before I need them, and off-cycle bonus runs have never been a problem. Even equipment purchasing, a real headache for a US company shipping to Indian addresses, is as simple as telling them what I need. Exchange rates are fair and the pricing is transparent. Deepika Elumalai, our point of contact, ties it all together. Whatever comes up, she pulls in the right people and sees it through. For any US company building a team in India, Wisemonk is an easy recommendation.

Tak Yamamoto, President at Red Hill Technology Solutions, Inc.