How to structure India-US technology licensing agreements

1. Choosing the structure before choosing the template

India-US technology arrangements take a small number of recognisable shapes, and the right documentation follows from which one you are in. A pure product licence gives an Indian customer the right to use standard software or technology on defined terms. A distribution or reseller arrangement adds the right to market and sublicense to end customers, with all the pricing, territory and channel-conflict questions that follow. A technology transfer conveys know-how, documentation and sometimes source code so that the Indian party can manufacture, deploy or develop. A development and licence-back structure has the Indian entity building technology that the US party owns or takes rights in. And a captive arrangement licenses the parent's platform into an Indian subsidiary that also provides services back.

These structures are not merely commercial labels. They drive the tax characterisation of payments, the transfer pricing analysis where the parties are related, the exchange-control documentation the bank will demand, and the question of who owns what is created in India. A single agreement that tries to be a product licence, a services contract and a development agreement simultaneously usually produces an unfavourable answer on all three.

The practical starting point is therefore a short structuring conversation before drafting: who is contracting with whom, what is actually being provided, what money flows in which direction, and where value is created. Half an hour of this saves weeks of redrafting when the tax adviser sees the first draft.

Almost every troubled cross-border licence we are asked to fix began as a US template that was localised after the commercial terms were agreed.

2. Grant, scope and restrictions

The grant clause is where ambiguity is most expensive. It should state the licensed subject matter with precision, including versions, modules and documentation; the permitted field of use; the territory; exclusivity or its absence; whether sublicensing and affiliate use are permitted and on what conditions; whether the licence is transferable on a change of control; and the term and renewal mechanics. Vague grants such as a right to use the technology for business purposes invite disputes precisely when the relationship is under strain.

Restrictions deserve equal care. Reverse engineering, decompilation, benchmarking, source-code access, use with competing products and use outside the field should be addressed expressly, along with the consequences of breach. Where the licensee is an Indian operating company with its own product roadmap, the residual-knowledge and non-compete language will be negotiated hard, and it is better to reach a precise compromise than to leave a broad restriction that is unlikely to be enforced.

Commercial terms should be drafted with the tax and remittance position in mind. A single blended fee covering licence, support, implementation and training makes withholding analysis harder and gives the tax authority room to characterise the whole payment unfavourably. Splitting consideration by component, with defensible allocation, is generally the better structure, provided the allocation reflects reality and the deliverables are actually separable.

3. IP ownership and improvements created in India

Indian intellectual property law does not mirror US assumptions, and the difference bites hardest on ownership. Under the Copyright Act, the author of a work is the first owner unless there is a written assignment or the work was made in the course of employment under a contract of service in circumstances the Act recognises. Independent contractors retain ownership absent a written assignment. The US concept of work made for hire does not do the same work in India, so an agreement that relies on it and nothing else can leave ownership with the individuals who wrote the code.

The fix is mechanical but must be done properly: a present-tense assignment of all rights in deliverables and improvements, executed by the entity and backed by executed assignments from each employee and contractor who contributes; waiver of moral rights to the extent permissible under Indian law; obligations to execute further documents and assist with registrations; and diligence on prior work, open-source components and any inbound licences that carry obligations. For patents, note the requirement of a foreign filing licence where an invention is made in India and the applicant intends to file abroad first.

Improvements need a commercial decision, not a default. If the Indian entity develops enhancements, the parties can agree that the licensor owns them with a licence back to the developer, that the developer owns them with a licence to the licensor, or that they are jointly owned, which is usually the worst of the three because joint ownership rules differ between jurisdictions and produce deadlock. Whichever route is chosen, if the parties are related, the arrangement must be priced at arm's length.

4. Tax characterisation, withholding and treaty relief

Characterisation determines everything downstream. Payments may be royalty, fees for included services, or business profits not taxable in India in the absence of a permanent establishment. The Supreme Court's decision in Engineering Analysis established that payments for the resale or use of standard software, where no copyright in the underlying work is transferred, are not royalty under the treaty, which materially changed the position for distribution and end-user licences. Licences of the copyright itself, of source code rights, or of know-how and processes generally remain royalty, and technical services with a make-available element can fall under fees for included services under the India-US treaty.

Where withholding applies, treaty rates are available only with the right documentation: a valid tax residency certificate, Form 10F, a declaration on the absence of a permanent establishment and beneficial ownership, and the recipient's Indian tax registration where required to avoid a higher default rate. These are practical prerequisites that should be contractual obligations with delivery deadlines, because a missing certificate at payment time either delays remittance or forces withholding at the domestic rate that the licensor will then try to gross up.

The agreement should state clearly who bears withholding, whether amounts are grossed up, how tax credit certificates will be issued and by when, how the parties will cooperate in an assessment or appeal, and who bears the cost if characterisation is later challenged. Indirect tax also needs an express home: import of services attracts integrated GST on a reverse-charge basis for the Indian recipient, and 'all taxes are for the other party's account' clauses drafted in the abstract rarely survive contact with an actual demand.

Draft the payment clause and the grant clause together. A tax position that contradicts the licence language is a position you will argue without evidence.

5. FEMA, remittance and the bank's file

Royalty and technical fee payments abroad are current account transactions and are generally permitted through an authorised dealer bank without prior Reserve Bank approval, provided the underlying transaction is genuine and documented. In practice the bank is the gatekeeper: it will want the executed agreement, invoices matching its terms, the online Form 15CA and the chartered accountant's certificate in Form 15CB, board approvals where relevant, and satisfactory answers on the nature of the payment. Where the arrangement sits alongside a foreign direct investment structure, entity-level reporting obligations such as the annual return on foreign liabilities and assets continue in parallel.

Payments that look like something other than what they are attract scrutiny. Lump-sum fees paid before any technology is delivered, escalating royalties disconnected from usage, payments to a group entity in a jurisdiction unrelated to where the technology was developed, and set-off arrangements against receivables all invite questions. Where a set-off or netting is commercially necessary, address it expressly and check that it is permissible rather than assuming it.

Build the remittance pathway before the first invoice. Confirm with the bank what it will require, agree the documentation obligations in the contract with deadlines, and align invoice narration with the agreement's defined terms. The most common cause of a stalled first payment is not a legal impediment; it is an invoice that describes a service the contract does not mention.

6. Related-party licences and transfer pricing

Where the licensor and licensee are associated enterprises, the licence is an international transaction subject to arm's length pricing, with contemporaneous documentation, benchmarking and the prescribed accountant's report. The rate must be supportable by comparable arrangements, the benefit to the Indian entity must be demonstrable, and the documentation should explain the value the licensed technology contributes to the Indian business.

Two structures attract particular attention. The first is a nil or nominal royalty, which tax authorities may treat as an understated transaction where the Indian entity clearly derives significant benefit, or conversely may probe as evidence that the Indian entity is the real developer. The second is a licence layered on top of a cost-plus services arrangement, where the same value is arguably compensated twice or where the Indian entity's development contribution is not reflected in either agreement.

The remedy is coordination. Draft the licence, the intercompany services agreement, the cost allocation policy and the transfer pricing documentation as one exercise, and revisit them when the business changes. An Indian subsidiary that grew from a support centre into a product development site is very likely operating under agreements that no longer describe what it does, which is the classic profile for a large adjustment.

7. Data protection, security and export control

If the licensed technology touches personal data, the agreement needs processing terms that work under the Digital Personal Data Protection Act, 2023: which party is the data fiduciary and which the processor for each data set, purpose limitation, security safeguards, sub-processor approval and flow-down, breach notification within timelines that allow the Indian entity to meet its own intimation obligation and CERT-In's six-hour incident reporting requirement, assistance with data principal rights, and deletion or return on termination. Where the platform is hosted abroad, record where data is stored and accessed, and check whether any sector regulator imposes localisation.

Security obligations should be specific and testable rather than aspirational: control standards or certifications, vulnerability management and patching commitments, penetration testing cadence, access controls for support personnel, logging, and audit or assurance-report rights. For critical dependencies, add continuity terms and consider source-code escrow with defined release conditions.

US export control and sanctions law applies to a good deal of technology leaving the United States, and the agreement should allocate responsibility for classification, licences where required, and screening of end users and destinations. Indian counterparties sometimes treat these clauses as boilerplate; they are not, and breach exposes both parties. Add mutual anti-bribery representations covering the Foreign Corrupt Practices Act and the Prevention of Corruption Act, with audit and termination rights.

8. Governing law, arbitration and enforcement

Choose the governing law, the dispute forum and the enforcement route as a single decision, working backwards from where the assets are. A New York-law contract with exclusive jurisdiction in a US court is comfortable to negotiate and difficult to enforce against an Indian company, because foreign court judgments from non-reciprocating territories must be pursued through a fresh suit in India. Foreign arbitral awards, by contrast, are enforceable under Part II of the Arbitration and Conciliation Act as a New York Convention award, subject to narrow grounds of refusal.

For most India-US technology deals the practical answer is institutional arbitration with a carefully chosen seat: Singapore or London where both parties want neutrality and the amounts justify the cost, India-seated arbitration where the counterparty, the assets and the likely dispute are all Indian and speed of interim relief matters. Specify the institution and rules, the number of arbitrators, the language, the seat as distinct from the venue, and confidentiality. Preserve access to interim relief from Indian courts, which is available in aid of foreign-seated arbitration in defined circumstances and matters when source code, data or an injunction against continued use is at stake.

Finally, make the remedies match the harm. Injunctive relief for IP misuse and confidentiality breach, defined liability caps with carve-outs for IP infringement, confidentiality, data breach and wilful misconduct, indemnities that a counterparty can actually satisfy, and an escalation clause that gets senior commercial people talking before positions harden. A dispute clause that only produces a damages award, years later, in a forum where the defendant has no assets, is a clause that was never really negotiated.

9. A working negotiation sequence

Start with a short term sheet covering structure, licensed subject matter, field and territory, consideration and its split, ownership of improvements, term and termination, and the dispute forum. Getting these agreed in two pages prevents the familiar pattern where a sixty-page draft is redlined three times before anyone notices that the parties disagree about what is being licensed.

Run tax, transfer pricing and IP diligence in parallel with drafting rather than after it. Tax characterisation shapes the payment and grant clauses. Transfer pricing shapes the rate. IP diligence determines whether the licensor can grant what it promises and whether the Indian entity's contributions are properly assigned. Each of these can require commercial renegotiation, which is cheap early and expensive at signature.

Close with an implementation checklist rather than a signature page: board and shareholder approvals where required, tax documentation collected, the authorised dealer bank briefed, invoicing templates aligned to the contract, data processing annexures executed, and calendar reminders for renewals, rate reviews and reporting. Contracts fail in administration more often than in drafting.

Frequently asked questions