In a significant judgement, the Delhi High Court in Commissioner of Income Tax v. Amazon Web Service held that payments for cloud computing services to AWS do not constitute \u201croyalty\u201d(one of the reasons being the absence of any commercial exploitation of IP rights involved). Rupam and Kartik analyse this judgement, explaining how it marks a pivotal moment in India\u2019s approach to taxing cross-border digital transactions. Rupam is\u00a0a final-year law student at NLSIU, Bangalore, and a Foundation for International Tax Scholar 2024 with a deep-rooted interest in international tax. Kartik is a final-year student at the National Law School of India University. His previous posts can be accessed\u00a0here<\/a>.<\/p>\n By Rupam Dubey and Kartik Sharma<\/em><\/p>\n In a significant judgment<\/a> (Commissioner of Income Tax v. Amazon Web Service) that clarifies the tax treatment of digital services, the Delhi High Court has held that payments made by Snapdeal Pvt. Ltd. (formerly Jasper Infotech) to Amazon Web Services Inc. (AWS) for cloud computing services do not constitute \u201croyalty\u201d<\/em> or \u201cfees for included services\u201d<\/em> (FIS) under Article 12 of the India\u2013United States Double Taxation Avoidance Agreement<\/a> (DTAA). Nor, in the absence of a permanent establishment (PE) of AWS in India, are such payments taxable under Section 9(1)(vi) or 9(1)(vii) of the Income-tax Act, 1961<\/a> (ITA). This ruling by the Delhi High Court marks a pivotal moment in India\u2019s evolving approach to the taxation of cross-border digital transactions, where, it draws a critical line between the access<\/em> to digital resources and the ownership<\/em> or control<\/em> over them \u2014 a distinction that has become central in the digital economy.<\/p>\n The dispute arose when Snapdeal paid AWS for infrastructure-as-a-service (IaaS) \u2014 including access to virtual computing, data storage, and networking infrastructure \u2014 without deducting tax at source. The Assessing Officer reopened assessments and treated these payments as royalty, citing Explanation 2(iv) to Section 9(1)(vi) of the ITA and Article 12(3) of the DTAA. The Revenue argued that AWS customers accessed high-end computing infrastructure and proprietary software, which amounted to the \u201cuse of, or the right to use\u201d industrial equipment or copyrighted software. Additionally, it claimed that AWS\u2019s support materials and technical documentation effectively \u201cmade available\u201d technical knowledge to customers, thereby satisfying the FIS test under Article 12(4)(b) of the treaty.<\/p>\n AWS disputed this characterization, maintaining that it merely provided globally uniform, automated cloud services that allowed users to access computing resources on a pay-as-you-go basis. At no point did customers receive proprietary software or hardware, nor did they gain physical or legal control over AWS\u2019s infrastructure. The license provided was limited, non-exclusive, non-sublicensable, and revocable, with strict restrictions on reproduction, reverse engineering, or distribution. AWS asserted that the payments were for access to computing capacity\u2014not for any transfer of intellectual property or ownership in equipment.<\/p>\n The Income Tax Appellate Tribunal (ITAT) had earlier ruled in AWS\u2019s favour, concluding that mere access to software functionality or infrastructure does not equate to a transfer of copyright or proprietary rights required for royalty characterization. The Delhi High Court upheld this view and rejected the Revenue\u2019s claim that the payments constituted equipment royalty. The Court noted that AWS retained full control over its infrastructure throughout, and customers merely accessed resources over the internet without obtaining physical possession or control. This lack of \u201cpossession or control\u201d meant that there was no \u201cuse of, or right to use\u201d equipment as required under Explanation 2(iv) to Section 9(1)(vi).<\/p>\n Secondly, the Court dismissed the software-royalty argument. It referred to the landmark ruling in Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT<\/em><\/a> [(2021) 432 ITR 471 (SC)] which emphasized that a limited, purpose-specific license to access software does not constitute a transfer of rights akin to those of a copyright holder. Since AWS\u2019s license strictly barred such actions, the threshold was not met.<\/p>\n Third, the Court found no merit in the FIS characterization in AWS\u2019s case, the service was delivered through automated means without human intervention or transfer of know-how. Generic customer support and help documentation did not amount to a transfer of technical knowledge. Finally, the Court concluded that AWS\u2019s income was in the nature of business profits under Article 7 of the DTAA. In the absence of a PE in India, such income could not be taxed in India.<\/p>\n The Court\u2019s finding that AWS customers do not receive proprietary rights or control over the underlying software or hardware is especially important. It emphasizes that AWS retains exclusive control over its infrastructure and merely allows customers to interact with an automated, self-service platform. The decision highlights that incidental or functional access to computing resources \u2014 without a transfer of rights in the sense contemplated under the Copyright Act<\/a> \u2014 does not amount to a \u201cuse\u201d of software that triggers royalty taxation. The Court also clarified that technical materials like support guides or manuals, unless they result in the transfer of underlying expertise or technical capability to the user, are insufficient to meet the \u201cmake available\u201d requirement under Article 12(4)(b) of the treaty.<\/p>\n An understanding of the specific implications of this ruling for IP law should commence from a breakdown of the text of Article 12(3) of DTAA. A.12(3)(a)\u00a0 envisages royalties as consideration received for (i) the use of, or (ii) the right to use, any copyright of a literary, artistic, or scientific work<\/u><\/em>, and other kinds of IP such as trademark, patents, etc. Note that scientific work is not a recognized category of work in the Copyright Act. The software services that end up being the centrepiece of tax litigation would fall under the rubric of literary works, since computer programs are a subset of literary works under s. 2(o) of Copyright Act. Portions (i) and (ii) of the relevant article imply that royalty will accrue only in situations where the copyright as an IP asset is being utilized or a right to use it has been granted to the client. The Court, its analysis of AWS\u2019s concerned cloud computing service, noted that the customers do not acquire any rights or title or IPR in the assets that would in turn allow them to exploit them.<\/p>\n There is no transference of any skill, knowledge, technology, etc to the customers and do not have any control over the cloud computing hardware or software. The court also noted that the source code of the software is also not provided to the customers. Consequently, the expression \u201cuse\u201d or \u201cright to use\u201d as used in the treaty has to be construed in a narrow fashion. Such an interpretive approach stands in contrast to the usual interpretive canons applied to taxation statutes that stipulate the aim to be that of maximization of revenue.<\/p>\n There is yet another crucial yet very basic concept that completes the rationale behind the court\u2019s decision, one that finds judicial recognition in the SC\u2019s ruling in Engineering Analysis<\/em>: the distinction between copyright and the copyrighted article. Article 12(3)(a), to reiterate, uses the expression \u2018copyright of a literary work\u2019, and not just \u2018literary work\u2019. Therefore, what has to be involved is \u2018copyright\u2019, which as defined in section 14 of the Copyright Act, refers to exclusive the rights to reproduce, distribute, communicate to public, etc. (depending on the kind of work that is in contention) that are linked to the \u2018works\u2019. A fiction book, to take a simple illustration, is different from the copyright that subsists in it. When I purchase a page-turner thriller, I only become the owner of that copy of the book. The copyright still remains with the copyright holder, whoever it be, in that situation. The same logic is at play here when the court is reckoning with AWS\u2019 cloud computing services. The customer is not interacting with any of the copyright element of the service, but is merely availing of the features of what the service provider is placing at its use. To construe it otherwise would be like saying that when I read that fiction book, I am exploiting or using the copyright-holder\u2019s exclusive intangible rights in that literary work. Now this crude analogy is not to be taken to mean that there can be no situations where IP rights can be in question. What the court\u2019s reasoning definitely tells us is that the decision would be fact-specific and would hinge on a nuanced understanding of the software service\/infrastructure involved. For a more detailed exposition of the issue, the reader is most certainly advised to peruse Engineering Analysis Centre<\/em> and another Delhi HC ruling, DIT v Infrasoft<\/em><\/a>. <\/em>The takeaway rule remains that not any kind of commercial benefit\/exploitation stands to qualify as royalty; it has to be that of the intellectual property rights. To use the book analogy (I promise, for last time), the mere factum of I benefitting commercially from the insights derived from a book does not render it a situation covered by Article 12(3)(a).<\/p>\n The approach of the Delhi High Court aligns with the OECD Commentary<\/a> on Article 12, which states that royalty income arises only when there is a grant of rights akin to those enjoyed by the owner of intellectual property \u2014 such as the right to reproduce, modify, or distribute<\/em>. Merely accessing software or infrastructure on a consumption basis does not qualify. That being said, the ruling arrives at a time when international tax norms are in flux. Several bilateral treaties based on the UN Model Convention include broader definitions of royalty, potentially encompassing payments for software usage or digital access. The UN Tax Committee has gone further, proposing a new Article 12B that would allow source countries to levy tax on \u201cautomated digital services\u201d \u2014 a category that include cloud computing platforms like AWS. However, the UN Commentary<\/a> clarifies that Article 12B will not apply in situations where the income is already covered under existing treaty provisions relating to royalties, fees for technical services, or where it is attributable to a permanent establishment (PE). In other words, Article 12B functions as a residual taxing right\u2014applicable only when such income falls outside the scope of Articles dealing with royalties, FTS, or PE-linked profits.<\/p>\n(No) Royalty in the Clouds: Between Copyright and Consumption<\/h3>\n
Background of the Dispute<\/strong><\/h3>\n
The Delhi High Court\u2019s Rationale<\/strong><\/h3>\n
Doctrinal Analysis: What is Royalty?<\/strong><\/h3>\n
Policy Implications: OECD, UN Article 12B & the Future of Digital Taxation<\/strong><\/h3>\n
![\"\"](\"https:\/\/i0.wp.com\/spicyip.com\/wp-content\/uploads\/2025\/06\/image-17.png?resize=1024%2C613&ssl=1)