Captive R&D Centers in India: IP, Tax, and Transfer Pricing

Here is a question that catches out more legal teams than it should. Your India team invents something genuinely new. Who owns the patent, and can you even file for it in the United States first?

The answers are not the ones most US and UK companies assume, and getting either one wrong can cost you the invention entirely.

That is what this guide is about. Captive R&D centers in India get written up as a cost story, and the cost part is the easy part. The hard part is ownership, patent procedure, and how a cost-plus research entity gets taxed. Plenty of global companies already run captive centers in India, and these are the questions each of them had to answer first.

If you are still weighing up whether to build an owned center at all, our guide to captive centers in India covers the business case, the working models, the city choice, and setup costs. This article picks up after that decision.

What makes a captive R&D center different from an engineering center?

An engineering center builds and operates what you have already decided to build. An R&D center decides what is worth building, and produces inventions, patents and research output on the way. The org charts look similar, and the operating model names get used loosely. The legal and tax consequences are not similar at all.

If what you are really building is a delivery organization, you want our playbook for captive engineering centers in India instead, which covers pods, coverage windows and delivery metrics.

Still here? Then the first thing to settle is ownership, because in India it does not work the way it works at home.

Who owns the IP your India R&D team creates?

It depends on what kind of IP it is, and this is the detail that surprises people. Under Indian law, copyright in work made during employment generally vests in the employer automatically. Patent rights do not. The inventor is treated as the first owner, so an invention only becomes yours through an express assignment.

Put plainly, two different statutes are doing two different things:

• Copyright, which covers your source code: Section 17 of the Copyright Act 1957 vests copyright in the employer for work made in the course of employment, unless the contract says otherwise. Your code is usually yours by default.
• Patents, which cover your inventions: the Patents Act 1970 contains no equivalent work-for-hire rule. Without a signed assignment, the employee inventor retains the right to apply. Your inventions are not yours by default.

Unlike Section 17 of the Copyright Act 1957, the Patents Act 1970 does not give employers a right to apply for a patent on an employee's invention created in the course of employment. Assignment by contract is what fills that gap.

So the assignment clause is not boilerplate in an R&D center. It is the mechanism. Two things make it work, and both belong in the employment agreement from day one rather than bolted on later:

• A present-tense assignment of future inventions: drafted so rights pass as work is created, rather than a promise to assign something later when the inventor may have left.
• A duty to cooperate on filings: patent prosecution needs inventor signatures, sometimes years afterwards. An obligation to sign forms after employment ends saves real pain.

Our guide to the IP chain for India developers walks through the full document set. Once ownership is settled, though, a second and much less known rule decides where you are allowed to file.

Can you file a patent abroad on an invention made in India?

Not freely, and this is the rule that trips up the most companies. Under Section 39 of the Patents Act 1970, a person resident in India cannot file a patent application outside India for an invention unless they either file in India first and wait six weeks, or obtain written permission from the Indian Patent Office in advance.

It applies whether the applicant is an individual, a startup, or a multinational, and it catches direct foreign filings, PCT applications, and priority filings where India was not first. So there are exactly two compliant routes, as of July 2026:

1. File in India first: lodge the Indian application, wait at least six weeks, confirm no secrecy direction has been issued, then file abroad. No permission needed.
2. Get a foreign filing license: apply on Form 25 with a disclosure of the invention. The Patent Office typically responds within about three weeks, which lets you file abroad first.

Why does India do this? The screening exists for national security reasons, so inventions touching defense and atomic energy get reviewed before they leave the country. Most software and product inventions clear routinely. The problem is never the review, it is forgetting the step.

What happens if you skip it

The consequences are severe enough to be worth a calendar reminder:

• The Indian application can be treated as abandoned: under Section 40, and any patent already granted becomes liable to revocation under Section 64.
• There are criminal penalties: Section 118 provides for imprisonment of up to two years, a fine, or both, for contravening the requirement.

An invention made by your India team is not simply yours to file wherever you like. Either India sees it first, or India licenses it out. There is no third option.

Procedure and forms are published by the Office of the Controller General of Patents, Designs and Trade Marks. Use Indian patent counsel for the filing strategy itself, because the six week route and the license route have quite different consequences for your priority date.

With ownership and filing settled, the remaining question is the one your finance team will ask: how does the money flow, and what does India tax?

How is a captive R&D center in India taxed?

Almost always as a cost-plus service provider. Your India entity does not sell research to customers. It performs research for its parent and invoices the parent for costs plus a margin. That makes transfer pricing, not the headline corporate tax rate, the number that decides your tax bill.

Three things follow from the cost-plus structure:

• The margin has to be defensible: Indian tax authorities test whether the markup your parent pays reflects what an independent provider would charge. Set it too low and it gets adjusted upward, with interest.
• Documentation is not optional: transfer pricing study, intercompany agreement, and cost allocation records. Reconstructing these three years later during an audit is painful and expensive.
• Characterization matters: a genuine contract researcher bearing little risk is taxed differently from an entity treated as owning the IP economically. This also interacts with permanent establishment risk in India.

India does offer a way to take the argument off the table in advance, and it is underused by companies at this size.

What are the safe harbor margins for R&D services in India?

India's safe harbor regime lets an eligible company declare a minimum operating margin on its operating expenses and have that transfer price accepted without a detailed audit. As of July 2026, the margins in force across the software development, IT-enabled services, knowledge process outsourcing and contract R&D categories run from around 17% up to 24% of operating expenses, depending on the category and the size band.

Three practical points, and the third one is the reason to read this section twice:

• It is an election, not a default: you opt in by filing the prescribed form for the year. Skip the filing and you are back to defending your margin the hard way.
• The eligibility ceiling rose: the transaction value threshold moved from about $21 million (₹200 crore) to about $31 million (₹300 crore), applying to assessment years 2025-26 and 2026-27.
• A much larger change is proposed but not yet law: draft rules released by the CBDT would merge software development, ITeS, KPO and software R&D into a single IT services category at one 15.5% margin, and lift the threshold to about $208 million (₹2,000 crore). As of July 2026 these remain draft and open for comment, so do not plan on 15.5% yet.

That last bullet matters commercially. If the consolidation is notified, a mid-sized R&D captive that is currently outside the threshold could become eligible, and at a lower margin than it pays today. It is worth asking your advisers to model both cases now.

One caution on section references. The Income Tax Act 2025 took effect on April 1, 2026 and renumbers provisions inherited from the 1961 Act, so confirm the current numbering with your advisers rather than citing older sections from memory. Our India tax compliance guide tracks the wider picture.

Which leads to the question everyone asks next, usually hopefully: are there R&D tax breaks to claim?

Does your India R&D center qualify for R&D tax deductions?

Probably not, if you are a software company, and it is better to know that now than to build it into a business case. India's headline in-house R&D deduction is tied to recognition by the Department of Scientific and Industrial Research, and it applies only to a list of specified industries that does not generally extend to software services.

Two things have changed that people still get wrong:

• The weighted deduction is gone: it was 200%, dropped to 150% from April 2017, and has stood at 100% since April 2020. Older articles promising a super-deduction are describing a regime that expired.
• The sector list is narrow: it covers areas such as drugs and pharmaceuticals, biotechnology, electronic equipment, computers, telecommunication equipment, and aircraft and aerospace. A pure software research unit usually sits outside it.

If you do build hardware, devices, pharma or aerospace R&D in India, DSIR recognition is worth pursuing, and it is a formal application with its own guidelines and reporting forms. If you build software, plan the business case on the cost and talent advantage instead, because that is where the return actually sits. Our FAQs on hiring in India without an entity cover the practical starting point.

None of this works without the right people, and hiring researchers is a different exercise from hiring engineers.

How do you staff a research team rather than a delivery team?

You hire for depth instead of throughput, and you accept a longer search. India has roughly 250,000 AI and machine learning professionals working across more than 250 AI centers of excellence, and its engineering R&D market is around $63 billion, per Wisemonk's India GCC research. The specialists exist. They are simply not on the same hiring funnel as product engineers.

Research talent also clusters differently from delivery talent, so the choice of GCC hub city matters more here. Four differences worth planning for:

• Longer searches: a research specialist can take two to three times as long to hire as a mid-level engineer. Build that into the India hiring timeline rather than discovering it in quarter two.
• A publication and conference policy: researchers expect to publish, and publication interacts with patent timing. Decide the rule before the first paper, not after.
• Equity as a retention tool: senior research hires weigh long-term upside heavily, so understand granting ESOPs to India employees before you make the first senior offer.
• Named inventors on record: patents list inventors permanently, which is a genuine career asset for the researcher and a strong reason for them to stay and file more.

What does a captive R&D center in India cost?

Running costs land at $25,000 to $80,000 per person per year fully loaded, and a research center sits at the upper half of that range because the roles are senior and specialized. Total operating costs typically come in 40% to 60% below the US equivalent, and 50% to 70% below at senior levels. For the one-time build number, see our guide to GCC setup costs in India.

Salary is only part of it, as our breakdown of the true cost of employment in India shows. Three cost lines are specific to R&D and get missed in first drafts of the budget:

• Patent prosecution: Indian and foreign filing fees, attorney time, and the foreign filing license step for every invention originating in India.
• Transfer pricing compliance: an annual study and documentation set, which is a recurring professional fee rather than a one-off.
• Research infrastructure: compute, licences, datasets or lab equipment, which can rival salaries in an AI-heavy team. Size individual hires with our employee cost calculator.

If those recurring costs look heavy for a team of eight researchers, that is a signal, not a problem. Compare the models in EOR vs GCC in India before committing to an entity.

How does Wisemonk help you set up an India R&D team?

Wisemonk is an India-native Employer of Record. We help global companies hire, pay, and manage employees in India, and we handle the compliance work behind every payroll cycle so your research leaders are not spending their weeks on statutory filings.

More than 300 global clients work with us, we manage over 2,000 employees, we process $20M+ in annual payroll, and we hold a 4.8 out of 5 rating on G2 across verified customer reviews. EOR pricing starts from $99 per employee per month.

For a research team specifically, five things tend to matter:

• Employment without an entity: as your India Employer of Record we become the legal employer, so you can test a small research team before incorporating.
• IP assignment in the contract: employment agreements carrying assignment and confidentiality terms that protect your intellectual property in India from the first day of employment.
• Specialist recruitment: India recruitment support for senior and hard-to-fill technical roles across the major research hubs.
• Payroll and statutory compliance: managed India payroll with contributions, deductions and filings handled on time, every cycle.
• Benefits and equity support: competitive benefits plus guidance on equity compensation in India so senior research offers actually land.

We provide EOR services in India, and we are expanding rapidly into the US and UK markets. If you are starting smaller, our guide to hiring remote developers in India is a good first step.