Structuring IP Ownership When Your India Entity Builds Product for a Foreign Parent

Almost every foreign company that sets up an Indian entity to write code, design hardware, or run R&D eventually runs into the same question: who actually owns the intellectual property that team creates? It sounds like a formality that can be sorted out later with a standard employment contract. In practice, it's one of the most consequential structuring decisions a company makes, and getting it wrong can be expensive to unwind once the entity is operational, employees are hired, and the first product releases are already in the market.

This guide walks through how IP ownership actually works when an Indian entity is doing product development for a foreign parent, the structuring options available, the tax and compliance consequences of each, and where founders and CFOs tend to go wrong.

Why This Question Comes Up So Often

When a foreign company sets up in India — whether as a subsidiary, a Global Capability Centre, or a smaller engineering team under an Employer of Record arrangement — the default assumption is usually that anything built by the Indian team automatically belongs to the parent company. That assumption isn't wrong exactly, but it glosses over a genuinely important structuring choice: does the IP get created and owned directly by the Indian entity, or does the Indian entity build it as a service provider while ownership sits entirely with the foreign parent?

This isn't just a legal nicety. It determines how profits get taxed in India versus the parent's home jurisdiction, what happens if the Indian operation is ever sold or spun off, how transfer pricing rules apply to the arrangement, and whether the company can meet local ownership requirements for certain government contracts or regulated sectors.

The Two Core Structuring Models

Broadly, foreign companies choose between two approaches when their India entity is doing genuine product development rather than routine support work.

Model 1: India as a Cost-Plus Service Provider

Under this model, the Indian entity performs development work but assigns all resulting IP to the foreign parent, typically as it's created. The Indian entity is compensated on a cost-plus basis — its operating costs plus an agreed markup — rather than owning any commercial upside from the IP itself.

This is the more common structure, particularly for companies still validating how central the India team will be to their long-term product strategy. It keeps things simple: one IP owner, one place where the commercial value sits, and comparatively straightforward transfer pricing documentation since the arrangement mirrors a standard contract R&D relationship.

Model 2: India as the IP Owner

Here, the Indian entity itself owns the intellectual property it develops, either outright or by taking an assignment of pre-existing IP from the parent so all future development builds on IP that's already onshore. The parent may then license that IP back for use in other markets, or the Indian entity might sub-license it to other group companies.

This model tends to make sense in a handful of specific situations: when India is genuinely the primary R&D hub building the next generation of the product, when certain government contracts or defence-sector work require Indian ownership of the resulting IP, when the parent views the India operation as a permanent and largely self-sustaining business rather than a satellite office, or when centralising ownership in India offers a genuine tax efficiency once double taxation treaty implications are properly analysed.

It also removes some ongoing administrative burden — no need to calculate royalties, apply withholding tax, or maintain transfer pricing documentation for a licensing arrangement that wouldn't otherwise exist.

Why Transfer Pricing Sits at the Centre of This Decision

Whichever model you choose, transfer pricing rules apply the moment your Indian entity transacts with a related foreign entity, and it's worth understanding why this matters so much for IP structuring specifically. Under Indian tax law, entities are treated as "associated enterprises" once one holds a meaningful stake or exercises common control over the other, which covers essentially every wholly owned subsidiary relationship. Once that threshold is crossed, every transaction between the Indian entity and its foreign parent — service fees, royalties, cost recharges — must be priced at arm's length, meaning the same price two unrelated companies would agree to in an open market.

This has a direct bearing on IP ownership because the pricing model you choose determines how much profit legitimately sits in India versus with the parent. A cost-plus service arrangement generally results in a lower, more predictable margin for the Indian entity, since it isn't sharing in the commercial success of the IP it built. An entity that owns and commercially exploits its own IP, by contrast, is expected to earn a return that reflects the value and risk of that ownership — which tax authorities on both sides will scrutinise closely if the numbers look inconsistent with the entity's actual role.

Indian tax authorities have also tightened documentation requirements in recent updates, consolidating IT services, software development, and contract R&D categories under a single safe harbour margin, alongside a higher eligibility threshold. This has made compliance somewhat more predictable for mid-sized captive centres, but it hasn't reduced the underlying requirement: if your India entity is doing genuine product development, you need contemporaneous transfer pricing documentation that reflects the real functions, assets, and risks sitting in India — not a generic template.

Getting the Intercompany Agreement Right

None of this structuring means much without a properly drafted intercompany agreement between the Indian entity and the foreign parent, executed before the relevant work begins rather than backdated after the fact. At minimum, this agreement should address:

• Which entity owns IP created during the engagement, and whether that ownership vests automatically or requires a formal assignment.

• How the Indian entity is compensated — cost-plus, royalty, revenue share, or a hybrid — and how that pricing will be benchmarked against comparable arm's length arrangements.

• What happens to pre-existing IP the parent brings into the relationship, and whether the Indian entity is licensing it, taking an assignment, or simply building on top of it without any transfer of rights.

• Employee invention assignment clauses, since Indian employment law doesn't automatically vest IP created by an employee in the employer the way some jurisdictions do — this needs to be addressed explicitly in employment contracts, not assumed.

• Termination and wind-down provisions, covering what happens to IP, data, and ongoing development if the relationship between the entities changes.

Contemporaneous evidence matters here. If tax authorities later question when an arrangement actually began, board minutes, signed agreements, and invoice dates all need to tell a consistent story.

Setting Up the Right Entity Before You Structure IP Ownership

Before any of this IP structuring becomes relevant, you need a legal entity in India in the first place, and getting company formation in India right from the outset avoids having to restructure ownership later. Most foreign companies doing product development in India use a private limited company, since it supports full foreign ownership in most sectors and gives you a clean legal vehicle to hold IP, employ developers, and enter into intercompany agreements.

If you're asking how to open a company in India for this purpose, the process for pvt ltd company registration in India typically follows this sequence:

1. Digital Signature Certificates (DSC) for the proposed directors, needed to sign incorporation documents electronically.

2. Director Identification Numbers (DIN) for each director.

3. Name reservation through the Ministry of Corporate Affairs portal.

4. SPICe+ filing, which bundles incorporation along with PAN, TAN, and typically GST and other statutory registrations into a single application.

5. Certificate of Incorporation, after which the entity legally exists and can sign the intercompany agreements that will govern IP ownership.

The mechanics of online registration of company formation in India have become considerably faster in recent years, and a standard private limited incorporation is often complete within one to two weeks. India incorporation itself is rarely the bottleneck — the real work is deciding, before you file, whether your Indian entity is going to be an IP owner or a service provider, because that choice shapes the intercompany agreements, transfer pricing documentation, and employment contracts you'll need from day one.

Common Mistakes Companies Make

• Treating IP ownership as an afterthought, drafting employment contracts and intercompany agreements only after the Indian team has already started building product.

• Assuming IP automatically belongs to the employer, without explicit invention assignment clauses that hold up under Indian law.

• Choosing a pricing model that doesn't match the entity's actual function, which creates transfer pricing exposure on both sides of the relationship.

• Backdating intercompany agreements without contemporaneous evidence to support the effective date, which invites scrutiny during a tax audit.

• Ignoring DTAA implications when licensing or sub-licensing IP through the Indian entity, missing treaty benefits that could meaningfully reduce withholding tax exposure.

Final Thoughts

IP ownership structuring isn't a box to tick after your India entity is up and running — it's a decision that should be settled before the first line of code is written or the first patent application is filed. Whether your Indian entity ends up as a cost-plus service provider or the genuine owner of the IP it creates, the choice needs to reflect where the real commercial risk and long-term strategic value sit, and it needs to be backed by intercompany agreements, transfer pricing documentation, and employment contracts that were built for that purpose from the outset. Get the entity formation and IP structuring aligned early, and everything downstream — tax filings, audits, and any future restructuring — becomes considerably easier to manage.