Technology Licensing Agreements in India
Your organisation licensed the technology because it solved a manufacturing problem. The licensing agreement defines whether you own the improvements you create, whether you can survive the licensor going insolvent, and whether the royalty rate is defensible when the Transfer Pricing Officer reviews your cross-border payments. The technology is only as valuable as the licence that governs it.
The Technology Licensing Landscape in India: IP Categories and Regulatory Framework
Technology licensing is the mechanism by which IP owners monetise their innovations without manufacturing or distributing products themselves. The licensor retains ownership while the licensee acquires defined rights to use, manufacture, or distribute. In India, the licensing landscape operates across four IP categories, each governed by distinct legislation and regulatory regimes.
Patent Licensing is governed by the Patents Act 1970. A patent grants the patentee the exclusive right to prevent others from making, using, selling, or importing the patented invention in India for 20 years from the filing date. Patent licensing can be exclusive, non-exclusive, or sole. The licensee must be registered as a licensee under Section 68 to establish enforcement rights. Cross-border patent licensing involves FEMA compliance for royalty payments and transfer pricing scrutiny for associated-enterprise transactions.
Software Licensing falls under the Copyright Act 1957, which grants copyright protection to computer programs as literary works. Software licensing ranges from end-user licences (limited right to use) to source code licences (right to modify and maintain). The distinction between a software licence (copyright) and SaaS (service) has significant tax implications — software royalties may be subject to withholding tax under Section 195, while SaaS fees may be treated as business income not subject to withholding (the characterisation is contested). Open-source licences (GPL, MIT, Apache) create additional compliance obligations.
Know-How Licensing covers unpatented technical knowledge — manufacturing processes, formulas, techniques, engineering data, and operational methods. Know-how has no statutory registration system; protection relies entirely on contractual confidentiality obligations and common law principles. Know-how licensing is common in manufacturing industries where the competitive advantage lies in process efficiency rather than product design.
Trademark Licensing under the Trade Marks Act 1999 permits the licensee to use the licensor trademarks in connection with licensed technology products. The registered user provisions under Section 49 provide the licensee with enforcement standing and protect the trademark validity.
Licence Scope Definition: Exclusivity, Territory, Field of Use, and Duration
The licence scope defines the boundary between what the licensee can do and what remains with the licensor. Every licence parameter — exclusivity, territory, field of use, duration, and permitted activities — must be precisely defined because ambiguity in scope is the primary source of licensing disputes.
Exclusivity: Exclusive (the licensee has sole rights in the territory — the licensor cannot grant additional licences or use the technology itself), sole (the licensee is the only licensee but the licensor retains its own rights), or non-exclusive (multiple licensees permitted). Exclusivity should be defined per field of use and per territory — a licensee may have exclusive rights for the automotive sector in India but non-exclusive rights for other sectors. Exclusivity is typically conditional on performance: if the licensee fails to achieve minimum commercialisation milestones, the licence converts from exclusive to non-exclusive, or the licensor may terminate the exclusivity and appoint additional licensees.
Territory: The geographic scope within which the licensee may exercise the licensed rights. For patent licences, the territory cannot exceed the patent jurisdiction — an Indian patent licence covers India only. For know-how licences, the territory is contractually defined and can be worldwide. For software licences, territory restrictions must be reconciled with the borderless nature of digital distribution. The agreement should address: manufacturing territory (where the licensee can produce), sales territory (where the licensee can sell), and digital distribution territory (particularly for software and digital products).
Field of Use: The industrial application or market segment for which the licence is granted. A pharmaceutical patent may be licensed for oncology applications but not for cardiovascular applications. A software platform may be licensed for financial services but not for healthcare. Field of use restrictions maximise the licensor value by enabling multiple non-competing licences for different applications of the same technology.
Duration: Patent licences cannot exceed the patent term (20 years from filing). Copyright licences can extend for the copyright term (author life plus 60 years for literary works). Know-how licences should have a defined term with renewal options — perpetual know-how licences are rare because the licensor loses negotiating leverage. The agreement should address what happens at expiry: does the licensee retain the right to use know-how that has become part of their general knowledge? Must the licensee cease manufacturing immediately, or is there a wind-down period for existing inventory?
Royalty Architecture: Upfront Fees, Running Royalties, and Milestone Payments
The royalty structure determines the economic allocation between licensor and licensee. A well-designed royalty mechanism aligns incentives: the licensor is rewarded when the technology generates commercial value, and the licensee cost is proportionate to the benefit received.
Upfront / Lump-Sum Fee: A one-time payment at licence execution. Functions as: compensation for the licensor R&D investment, a commitment signal from the licensee, and a minimum guaranteed return regardless of commercialisation success. Upfront fees are common in pharmaceutical and biotech licensing where the commercialisation timeline is long and uncertain. The fee is typically non-refundable, even if the licensee fails to commercialise. For tax purposes, a lump-sum payment may be treated differently from running royalties — it may be characterised as a capital payment rather than revenue, affecting depreciation and withholding tax treatment.
Running Royalty: A periodic payment calculated as a percentage of the licensee revenue, production volume, or other metric. Typical rates vary by industry: pharmaceutical (3-8% of net sales), software (10-25% of net revenue), manufacturing (2-5% of net sales), biotech (4-10% of net sales). The agreement must define: the royalty base (gross revenue, net revenue, or net sales — each defined differently), the deductions permitted from the royalty base (returns, discounts, freight, taxes), the calculation period (monthly, quarterly, or annually), the reporting obligations (detailed royalty statements with supporting documentation), audit rights (the licensor may audit the licensee books with 30 days notice, with the licensee bearing audit costs if discrepancies exceed 5%), and the payment currency and mechanism.
Milestone Payments: Payments triggered by the achievement of defined commercialisation milestones: first commercial sale, revenue thresholds (₹10 crore, ₹50 crore, ₹100 crore), regulatory approvals (drug registration, product certification), or technical milestones (successful integration, performance benchmarks). Milestone payments align the licensor compensation with the licensee progress and share the upside of successful commercialisation.
Minimum Annual Royalty (MAR): A floor on annual royalty payments regardless of actual commercialisation revenue. The MAR protects the licensor against licensees who obtain a licence (particularly an exclusive licence) but fail to commercialise aggressively. If actual royalties fall below the MAR, the licensee pays the difference. Failure to pay the MAR for two consecutive years should trigger the licensor right to convert the exclusive licence to non-exclusive or to terminate.
Know-How Transfer: Documentation, Training, and Ongoing Technical Support
Know-how transfer is the most operationally complex component of technology licensing. Unlike patents (documented in specifications) or software (delivered as code), know-how resides in people, processes, and institutional memory. The transfer must convert tacit knowledge into explicit, usable knowledge within the licensee organisation.
Transfer Methodology: Structured in phases: (1) Documentation delivery — the licensor provides all documented know-how: process flow diagrams, manufacturing specifications, equipment requirements, raw material specifications, quality control procedures, troubleshooting guides, and safety protocols. (2) On-site training at the licensor facility — the licensee personnel spend 2-8 weeks at the licensor manufacturing site, observing operations, working alongside experienced personnel, and receiving hands-on training. (3) On-site commissioning at the licensee facility — the licensor personnel visit the licensee site to commission equipment, validate process parameters, conduct test production runs, and verify output quality. (4) Production support — the licensor provides remote and on-site support during initial production ramp-up until the licensee achieves consistent quality and throughput targets.
Acceptance Criteria: Know-how transfer is complete when the licensee can independently produce goods meeting the licensor quality specifications at the target throughput rate for three consecutive production batches. The agreement should define: the quality specifications, the throughput target, the acceptance test methodology, and the consequences of failure (additional training at the licensor cost if the failure is due to inadequate training, at the licensee cost if due to the licensee facilities or personnel).
Ongoing Technical Support: After initial transfer, the licensor should provide: a dedicated technical contact person available during business hours, response time commitments for technical queries (24 hours for routine, 4 hours for urgent), periodic technology updates (new versions, process improvements, quality enhancements), and annual review meetings to assess licensee performance and identify improvement opportunities. Support should be included in the licence fee for a defined initial period (typically 2-3 years) and available on a paid basis thereafter.
FEMA Compliance and Tax Structuring for Cross-Border Technology Licences
Cross-border technology licensing triggers multiple regulatory and tax requirements. The structuring must address FEMA compliance, withholding tax optimisation, transfer pricing documentation, and GST treatment simultaneously.
FEMA Current Account Compliance: Technology licence royalty payments are current account transactions under FEMA 1999. There is no cap on royalty rates (the earlier caps were removed in 2009). The AD Bank processes the remittance upon receiving: the executed licensing agreement, the licensor invoice, the CA certificate confirming withholding tax compliance, the Form 15CA (undertaking by the remitter) and Form 15CB (CA certificate), and the debit instruction. The AD Bank may query payments that appear excessive relative to the licensed technology value — maintaining arm length documentation supports smooth processing.
Withholding Tax Optimisation: The effective withholding tax rate depends on the characterisation of the payment and the applicable DTAA. For software royalties, the Supreme Court in Engineering Analysis Centre of Excellence v. CIT (2021) held that payments for copyrighted software (where the buyer does not acquire rights in the copyright itself) are not royalties under most DTAAs — this reduces or eliminates withholding tax for standard software licences. For patent and know-how royalties, the DTAA rate (typically 10-15%) applies. Treaty shopping is scrutinised — the licensor must have substance in the treaty jurisdiction to claim DTAA benefits. The licence structure should be reviewed by a tax advisor to optimise the overall tax cost, considering: withholding tax in India, income tax in the licensor's jurisdiction, foreign tax credit availability, and GST cost.
Transfer Pricing: If the licensor and licensee are associated enterprises, the royalty rate must be at arm length. Documentation under Section 92D of the Income Tax Act must include: a functional analysis of the licensor contribution, a benchmarking analysis using the CUP method (comparing the royalty rate with comparable uncontrolled licensing transactions), the economic analysis of the licensee profitability at the agreed royalty rate, and the rationale for the royalty base, rate, and payment structure. The Transfer Pricing Officer may make adjustments if the royalty rate exceeds the benchmark range — such adjustments create double taxation if the licensor's jurisdiction does not provide corresponding relief.
IP Ownership of Improvements: Grant-Back, Licence-Back, and Joint IP
When a licensee uses licensed technology, they inevitably create improvements, modifications, and derivative works. The IP ownership of these improvements is one of the most consequential provisions in a technology licence because it determines whether the licensor's IP portfolio expands with the licensee's innovation or whether the licensee builds independent competitive advantage using the licensed platform.
Grant-Back: The licensee assigns ownership of all improvements to the licensor. The licensor's IP portfolio grows with every licensee innovation. This is the most licensor-favourable position and is appropriate when: the licensor is licensing core platform technology to multiple licensees, improvements by one licensee should benefit all licensees (and the licensor can incorporate improvements into the platform), and the licensee R&D investment in improvements is modest. The disadvantage: the licensee has reduced incentive to invest in innovation because the results belong to the licensor.
Licence-Back: The licensee owns improvements but grants the licensor a licence to use them. The licence-back terms are negotiated: non-exclusive and royalty-free (the licensor benefits from the improvement without cost), exclusive (the licensor has sole access to the improvement, which limits the licensee value proposition), or royalty-bearing (the licensor pays for access to improvements, which offsets the licensee R&D cost). Licence-back with non-exclusive, royalty-free terms is the market standard for most technology licensing transactions.
Joint Ownership: Improvements are jointly owned. Under Indian patent law, joint ownership of patents creates practical complications: either joint owner can use the patent without the other consent, but neither can licence to third parties without the other agreement. This fragmentation of rights can stifle commercialisation. If joint ownership is agreed, the agreement should include: a management protocol for jointly owned IP, decision-making authority for patent prosecution and enforcement, cost-sharing for patent prosecution and maintenance, and a buy-out mechanism if one party wants to acquire sole ownership.
Software Licensing: Open Source, Escrow, and SaaS Distinction
Software licensing in India presents unique challenges because the digital nature of software makes it difficult to control distribution, copying, and modification. The licensing structure must address the specific characteristics of software while complying with the Copyright Act 1957, the Information Technology Act 2000, and the evolving judicial interpretation of software taxation.
Proprietary Software Licences: Standard models include: perpetual licence (one-time fee, right to use indefinitely, often with annual maintenance fee for updates and support), subscription licence (periodic fee, right to use only during the subscription period — effectively a SaaS model delivered on-premise), and enterprise licence (unlimited deployment within the licensee organisation for a fixed fee). Each model has different revenue recognition, tax, and termination implications.
Open-Source Compliance: If the licensed software incorporates open-source components, the licensing agreement must address: the specific open-source licences applicable to each component (GPL, LGPL, MIT, Apache, BSD — each with different obligations), the copyleft obligations (GPL requires that derivative works be distributed under GPL — if the licensed software is combined with GPL code, the entire combined work may need to be distributed under GPL, which conflicts with proprietary licensing), the compliance process (SBOM — Software Bill of Materials listing all components and their licences), and the licensor warranty that open-source usage complies with applicable licence terms and does not create copyleft contamination of the licensee proprietary code.
Source Code Escrow: Essential for mission-critical software where the licensee needs assurance of continued access even if the licensor ceases operations. The escrow arrangement should include: current source code deposit (updated within 30 days of each release), complete build documentation, third-party dependency list, and annual verification of escrow completeness. Release triggers should be precisely defined: insolvency (not merely financial difficulty), cessation of maintenance for the licensed version, or material breach of support obligations.
SaaS vs. Licence Distinction: The Supreme Court's decision in Engineering Analysis Centre of Excellence v. CIT (2021) distinguished between: software licence (the licensee acquires a right in the copyright — potentially royalty for withholding tax purposes) and software use (the licensee merely uses the software without acquiring copyright rights — not royalty). SaaS is access to functionality, not a copyright licence. This distinction affects: withholding tax (royalty is subject to withholding; service fees may not be), GST classification (software licence may be goods; SaaS is a service), and FEMA characterisation (royalty vs. fee for technical services).
Compulsory Licensing: Risk Assessment and Contractual Mitigation
Compulsory licensing is a sovereign power that can override the exclusivity of a patent licence. For any technology licensing agreement involving Indian patents — particularly in pharmaceuticals, agriculture, and essential technologies — compulsory licensing risk must be assessed and contractually addressed.
Legal Framework: Section 84 of the Patents Act 1970 permits compulsory licence applications after 3 years from the date of patent grant. Grounds: the patented invention is not available to the public at a reasonably affordable price (assessed relative to Indian purchasing power), the patented invention is not worked in the territory of India (mere importation may not satisfy this requirement — local manufacturing or licensing for local manufacture is generally required), or the reasonable requirements of the public are not satisfied. Section 92 permits the Central Government to issue compulsory licences for any patent during a national emergency or in circumstances of extreme urgency or public non-commercial use (this provision was activated during COVID-19 discussions but was not ultimately invoked for vaccines).
Risk Assessment: Factors that increase compulsory licensing risk: the technology addresses an essential need (healthcare, food security, environmental protection), the licensor pricing is significantly above what is affordable for the Indian market, the patented product is not manufactured in India (imported only), the patent term has limited remaining life (potential applicants are motivated to act before expiry), and public interest groups or generic competitors have expressed interest in the technology. The 2012 Natco Pharma compulsory licence for Bayer's Sorafenib remains the only granted compulsory licence in India — but the precedent exists and shapes negotiating dynamics.
Contractual Mitigation: The licensing agreement should address: (1) the licensor obligation to price licensed products at levels that reduce compulsory licensing risk (tiered pricing for different market segments), (2) the licensee obligation to manufacture in India (satisfying the working requirement), (3) the allocation of compulsory licensing risk — if a compulsory licence is granted, how are the royalties adjusted? Does the exclusive licence convert to non-exclusive? Does the licensee have the right to terminate? (4) the cooperation obligation — both parties cooperate in opposing unjustified compulsory licence applications, and (5) the notification obligation — each party immediately notifies the other of any compulsory licence application or government inquiry.
IP Enforcement: Infringement, Licensee Standing, and Cooperation
The value of a technology licence depends on the enforceability of the underlying IP. If third parties can infringe the licensed patents or copy the licensed software without consequence, the licensee's competitive advantage from the licence is destroyed. The licensing agreement must allocate IP enforcement responsibilities and establish cooperation mechanisms.
Enforcement Responsibility: Default position — the licensor, as IP owner, has primary responsibility for enforcement. The licence should specify: the licensor obligation to take reasonable steps to enforce the licensed IP against third-party infringers, the notification process (either party notifies the other of suspected infringement), the licensor decision-making authority (the licensor decides whether to initiate proceedings, settle, or take no action), and the licensee right to initiate proceedings if the licensor declines to act within a specified period (typically 90 days). For exclusive licences, Section 109 of the Patents Act 1970 gives the exclusive licensee standing to initiate infringement proceedings — but the patentee (licensor) must be joined as a co-plaintiff.
Cost and Recovery Allocation: Enforcement is expensive. The agreement should specify: who bears the litigation costs (typically the party who initiates proceedings, or costs shared equally for licensor-initiated enforcement), how damages and settlements are allocated (licensor and licensee share based on their respective economic interests — the licensee receives compensation for lost sales, the licensor receives compensation for lost royalties), and the decision-making process for settlement (the licensor should not settle on terms that prejudice the licensee exclusive rights without the licensee consent).
Defensive Proceedings: If a third party challenges the validity of the licensed IP (patent opposition, revocation proceedings, declaratory action of non-infringement), the licensor has primary responsibility for defence. The licensee should: be notified immediately, have the right to participate in the defence, and have the right to take over the defence if the licensor fails to defend adequately. If the licensed IP is invalidated, the royalty obligations should adjust: the licensee should not pay royalties for an IP right that has been invalidated. The agreement should address whether already-paid royalties are refundable if the IP is subsequently found invalid.
Termination and Reversion: Wind-Down, Data Deletion, and Continuing Rights
Technology licence termination must be managed to ensure that the licensed IP reverts cleanly to the licensor while giving the licensee a reasonable period to unwind operations that depend on the licensed technology.
Termination Triggers: Material breach (failure to pay royalties for 60 days, quality violations that damage the licensor IP, unauthorised sublicensing, or violation of territory/field of use restrictions) with 30-60 day cure period. Insolvency of either party. Convenience termination by the licensee with 6-12 months notice (the licensor should not have a convenience termination right for exclusive licences during the committed term). Patent invalidity or expiry (the licence terminates automatically when the last licensed patent expires or is invalidated — but know-how obligations may continue). Compulsory licence grant (may not automatically terminate the voluntary licence, but the licensee may negotiate a royalty adjustment or termination right).
Wind-Down Period: The licensee should have a defined period to wind down licensed operations: 30-90 days for software (to migrate to alternative solutions), 6-12 months for manufacturing (to fulfil existing orders and reconfigure production lines), and 12-24 months for complex technology integrations (where the licensed technology is embedded in the licensee products). During the wind-down, the licence continues on existing terms, and the licensee pays royalties on wind-down sales.
Post-Termination Obligations: The licensee must: cease all use of the licensed technology (except during the wind-down period), return or destroy all licensed materials (documentation, software, samples, tools), delete all digital copies and provide destruction certification, stop using the licensor trademarks and branding, and continue to protect the licensor confidential information for the survival period specified in the agreement (typically 5-7 years for trade secrets). The licensor must: provide reasonable cooperation during the wind-down (particularly for customer transition), release any security deposits or escrow funds, and provide a final accounting of royalties due.
Dispute Resolution in Technology Licensing: Arbitration, Expert Determination, and IP Tribunals
Technology licensing disputes range from commercial disagreements (royalty calculations, scope interpretation) to technical disputes (was the know-how adequately transferred?) to IP disputes (is the patent valid? is the licensee product within the licensed scope?). The dispute resolution mechanism must route each type to the most appropriate forum.
Arbitration for Commercial Disputes: Royalty disputes, scope disputes, breach claims, and termination disputes are commercial matters suitable for arbitration. Recommended provisions: seat in Mumbai or Singapore (Singapore for cross-border licences), SIAC rules for international transactions, sole arbitrator for disputes below ₹10 crore, three-member tribunal for larger disputes, and final award within 12 months. The arbitrator should have IP or technology transaction expertise — generic commercial arbitrators may not fully understand the technical context of licensing disputes.
Technical Expert Determination: For disputes about whether the know-how transfer was adequate, whether the licensed product meets quality specifications, or whether the licensee product falls within the licensed scope, a technical expert is more appropriate than an arbitrator. The expert should be a qualified professional in the relevant technology field, mutually agreed or nominated by a technology industry body. The expert determination is binding on the technical question and fast (30-60 days).
IP-Specific Forums: Patent validity disputes must be determined by the Intellectual Property Appellate Board (now merged with the High Court under the Tribunal Reforms Act 2021) — the arbitration clause should expressly exclude patent validity from arbitration. Trademark disputes are adjudicated by the Commercial Division of the High Court. Copyright infringement claims can be arbitrated if the underlying dispute is contractual (licence scope) but not if the dispute involves statutory rights (fair use, compulsory licensing). The agreement should map each dispute type to its appropriate forum.
Interim Relief: Technology licensing disputes frequently require urgent interim relief: injunctions to prevent ongoing infringement, orders to preserve evidence (Anton Piller-type orders), and orders to prevent the licensee from destroying or removing licensed materials during a dispute. The agreement should preserve the right to seek interim relief from courts under Section 9 of the Arbitration Act and through emergency arbitrator provisions under institutional arbitration rules.
What You Need to Know
Is Your Technology Licence Structured to Protect Your Investment?
The technology licence that works during commercialisation is rarely the licence that protects you during a dispute, a compulsory licensing application, or a change in the FEMA regulatory landscape. Every licence provision must be stress-tested against the scenarios where the relationship breaks down.
[email protected]