Cloudera Inc., USA vs ACIT (ITA No .- 917/Del/2023)
The Growing Complexity of Software-Based Revenue
The taxation of cross-border software payments has become increasingly difficult as technology businesses have moved away from selling packaged products and towards subscription-based platforms. A single customer agreement may now cover access to software, cloud-based functionality, implementation assistance, training, technical support, migration, consulting and continuing professional services. Although these offerings may appear commercially integrated, they do not necessarily have the same legal character for income-tax purposes.
This distinction was examined by the Delhi Bench of the Income Tax Appellate Tribunal in a case involving a US tax-resident enterprise engaged in providing data software solutions. During the financial year 2021–22, the taxpayer received payments for software subscriptions as well as professional services supplied to certain customers. The central question was whether these receipts were taxable in India as royalty or fees for technical services under the Income-tax Act, 1961, and as fees for included services under the India–US Double Taxation Avoidance Agreement.
The Tribunal’s decision is significant because it did not treat the entire commercial arrangement as a single indivisible supply. Instead, it examined the nature of the rights granted under the subscription agreement, the restrictions imposed on customers, the absence or otherwise of any transfer of technology, and the actual character of the professional services separately charged to customers.
The result was a split conclusion. The software subscription receipts, excluding amounts charged for professional services, were held not to constitute royalty or fees for technical services. The professional service receipts, however, were held taxable as fees for technical services under the Act and as fees for included services under the India–US treaty.
The decision therefore provides a useful reminder that the tax treatment of technology revenue depends not on the sophistication of the product alone, but on what the customer actually receives and what the supplier actually performs.
The Subscription Agreement and the Rights Granted
The taxpayer supplied its software solutions under an Enterprise Subscription Master Agreement, or ESMA. The Revenue argued that the arrangement went beyond the mere provision of standard software access. According to the Revenue, the taxpayer supplied a customised data platform that was configured to meet the specific operational requirements of individual customers.
The taxpayer, however, relied upon the contractual limitations contained in the ESMA. Customers received only a non-transferable and limited right to access and use the software for their own business purposes. They were not permitted to modify, alter, sub-license or transfer the software. The agreement did not give them ownership of the underlying software or the right to exploit the intellectual property commercially.
The taxpayer also accepted that its software could be modified or customised to suit a customer’s particular requirements. Its argument was that such modification did not amount to a transfer of technology. Customisation of the supplier’s own platform, it contended, was materially different from transferring the source code, technical know-how or proprietary rights to the customer.
The taxpayer relied heavily on the Supreme Court’s judgment in Engineering Analysis Centre of Excellence Pvt. Ltd. v. Commissioner of Income-tax, along with other judicial precedents. In Engineering Analysis, the Supreme Court had examined payments for software and held that a payment for the right to use copyrighted software, without the transfer of rights contemplated under the relevant royalty provisions, could not automatically be treated as royalty.
The taxpayer’s position was that its customers were merely granted restricted access to the software platform. They could use the platform for their internal business purposes, but could not reproduce, commercially exploit, modify, transfer or sub-license it. There was consequently no transfer of copyright or equivalent proprietary rights, and no transfer of technology.
The professional services were described as relating principally to migration from an older version of the taxpayer’s software to a newer version, as well as assistance intended to help customers derive greater value from implementing and using the software subscriptions. The taxpayer argued that these services were ancillary to the software arrangement and did not involve the making available of technical knowledge, skills or know-how in the manner required by the India–US treaty.
The Revenue’s Case: This Was More Than a Standard Software Product
The Revenue sought to distinguish Engineering Analysis on the ground that the software involved in the present case was not ordinary shrink-wrap software. In a shrink-wrap arrangement, the customer generally receives a standard product in object-code form and does not receive the source code or any right to alter the software.
According to the Revenue, the taxpayer’s data platform was different. It was customised and configured for individual customers and operated through programming languages such as Java, Python and C++. The Revenue argued that the operation and customisation of such a platform necessarily involved access to, or transfer of, source code and technical knowledge.
The Revenue also referred to the ESMA provisions dealing with software access, technical support, training, consulting and other assistance. It contended that the taxpayer was not simply licensing a standard software product. Instead, it was supplying a broader subscription package that enabled customers to perform various business functions through a specialised technological platform.
On this basis, the Revenue argued that the customers were receiving specialised skills, knowledge, know-how and technical assistance. It further contended that the knowledge and expertise were enhanced through the taxpayer’s continuing support services. The Revenue therefore maintained that the “make available” condition under the India–US treaty had been satisfied.
This argument reflected a broader concern in international tax disputes involving technology businesses. A supplier may not formally transfer its source code or intellectual property, yet its employees may provide extensive assistance in implementing, configuring, maintaining and optimising the platform. The Revenue’s position was that the substance of the arrangement, rather than the restrictive language of the contract, should determine whether technical knowledge had been made available.
The Tribunal was therefore required to distinguish between three different situations: access to software, the supplier’s internal customisation of its own software, and the provision of specialised professional services to the customer.
Access to Software Is Not the Same as Transfer of Technology
After examining the ESMA and the relevant judicial precedents, the Tribunal held that the software subscription receipts, excluding the separately identified professional service receipts, did not constitute royalty or fees for technical services.
The contractual restrictions were important. Customers were given limited and non-transferable access to the software for their own business purposes. They did not receive the right to reproduce, modify, transfer, sub-license or commercially exploit the software. The underlying intellectual property remained with the taxpayer.
The Tribunal also accepted that there had been no transfer of technology to the customers. The fact that the taxpayer customised or configured its own platform to meet customer requirements did not, by itself, establish that the customer had acquired the technical knowledge or means to independently develop, reproduce or exploit the technology.
This distinction is critical. A supplier may perform substantial technical work behind the scenes without transferring the underlying technology to its customer. The customer may receive the benefit of a functioning platform, but that does not necessarily mean that the customer has obtained the technology itself.
The Revenue’s emphasis on the programming languages used by the platform was therefore insufficient. The fact that software is written in Java, Python, C++ or another programming language does not, without more, prove that source code or technical know-how has been supplied to the customer. What matters is whether the customer has received rights or knowledge that go beyond restricted access to the supplier’s product.
The Tribunal’s reasoning is consistent with the principle that taxability cannot be determined solely by the complexity of the technology involved. A technologically advanced subscription remains a subscription unless the rights granted or services supplied bring it within the statutory definition of royalty or fees for technical services.
Why Engineering Analysis Remained Relevant
The Revenue attempted to distinguish Engineering Analysis by arguing that the software in the present case was customised and technically more sophisticated than the standard software considered by the Supreme Court. The Tribunal nevertheless found the decision relevant.
The central principle emerging from Engineering Analysis is that the mere use of software does not automatically involve the use or transfer of copyright. A customer may be permitted to operate software without acquiring the legal rights associated with ownership or exploitation of the copyright in that software.
The same reasoning applies where a customer receives restricted access to a software platform under a subscription model. The customer’s right is limited to using the platform for its own business purposes. Unless the arrangement grants rights in the copyright, or otherwise involves the transfer of technology or technical know-how, the payment cannot automatically be characterised as royalty.
The Tribunal did not treat customisation as irrelevant. Rather, it examined what the customisation produced from the customer’s perspective. If the taxpayer merely configured or modified its own platform internally, while retaining control over the software and preventing the customer from accessing or exploiting the underlying technology, the activity did not necessarily amount to a transfer of technology.
The decision thus resists a potentially expansive theory of royalty taxation under which every customised or technically complex software arrangement is treated as a transfer of intellectual property. The contractual rights and the actual nature of the supply remain central.
Professional Services Were a Different Matter
The Tribunal drew a clear distinction between the software subscription receipts and the receipts from professional services. It found that the professional services were not automatically included in every subscription arrangement.
Only six out of twelve customers had availed themselves of the professional services. The remaining customers had purchased software subscriptions without obtaining those services. This fact indicated that the professional services were separately identifiable and were not an unavoidable or inseparable part of the subscription product.
The Tribunal also noted that the amount charged for professional services varied considerably from customer to customer. Certain customers paid substantial amounts over and above the subscription fees. This variation suggested that the charges were not merely nominal amounts for routine migration or ordinary technical assistance. Instead, they reflected specialised, customer-specific services.
The Tribunal accordingly rejected the taxpayer’s characterisation of the professional services as merely assistance for migration from an old version to a new version of the software application. On the facts, the services were found to involve specialised consultation and assistance tailored to the particular needs of individual customers.
This was important for treaty purposes. The India–US treaty contains a “make available” requirement for fees for included services. Under that standard, it is not enough that a service provider uses technical knowledge or performs a technical service. The service must also make available technical knowledge, experience, skill, know-how or processes to the recipient, in a manner that enables the recipient to apply them independently in the future.
The Tribunal concluded that the professional services met this threshold. The services were sufficiently specialised and customer-specific to qualify as fees for technical services under the Act and fees for included services under the treaty.
The “Make Available” Test and Customer-Specific Expertise
The distinction between the subscription and professional services illustrates the operation of the “make available” test.
A routine software subscription may provide the customer with access to a technological outcome without transferring technical knowledge. The customer uses the supplier’s platform, but does not necessarily learn how to reproduce, modify or independently operate the underlying technology outside the supplier’s system.
Professional services are different where they involve specialised consultation, detailed implementation guidance, customer-specific problem-solving or the imparting of expertise that the customer can apply independently. In such circumstances, the customer may not merely receive a result; it may acquire knowledge or skills through the service.
The Tribunal’s conclusion appears to have been driven by the factual indicators surrounding the professional service charges: their separate availability, their restricted uptake among customers, and the significant variation in amounts charged. These factors suggested that the services were not simply incidental support automatically accompanying every subscription. They were distinct engagements requiring additional work and expertise.
This aspect of the ruling is particularly relevant to technology businesses that combine recurring subscription revenue with implementation or consulting fees. The existence of a single master agreement does not necessarily mean that all receipts under it must receive identical tax treatment. A contract may provide the framework for multiple supplies, each of which must be examined according to its actual character.
The Importance of Separating the Revenue Streams
The Tribunal’s approach places considerable emphasis on revenue segmentation. The taxpayer had receipts from two broad sources: software subscriptions and professional services. The Tribunal did not allow the tax treatment of one category to determine the treatment of the other.
This is commercially and legally significant. Technology enterprises frequently offer customers a package that includes software access, updates, technical support, implementation, training and consulting. From a business perspective, these components may be marketed together. For tax purposes, however, their legal character may differ.
A payment for restricted access to software may not be royalty. A separate payment for specialised consulting may qualify as fees for technical services. Routine support may raise different questions from implementation services. Training may have to be examined according to its content and whether it transfers technical knowledge. The label used in the invoice or the fact that the services are covered by a single agreement cannot settle the issue.
The Tribunal’s decision therefore underscores the importance of clear contracts, separate invoicing and accurate identification of the services actually supplied. Where professional services are genuinely distinct, the taxpayer should be able to demonstrate their scope, pricing, deliverables and customer-specific nature. Conversely, where services are merely incidental to software access, the Revenue cannot assume that their presence transforms the entire subscription payment into royalty or fees for technical services.
A Caution for Both Taxpayers and the Revenue
The ruling offers useful guidance to taxpayers, but it should not be understood as a blanket exemption for all software-related receipts.
For taxpayers, the decision demonstrates the importance of documenting the precise rights granted to customers. Agreements should clearly state that customers receive limited access rather than ownership of the software, and that they cannot reproduce, modify, transfer, sub-license or commercially exploit the underlying intellectual property. Where customisation is performed, the documentation should clarify whether the supplier is modifying its own platform or transferring any technology to the customer.
Taxpayers should also maintain a clear distinction between subscription access and separately provided professional services. The scope of each service, the pricing methodology, the customer-specific deliverables and the nature of any training or consultation may become decisive in determining whether the “make available” test is satisfied.
For the Revenue, the ruling is a reminder that technical sophistication cannot be treated as a substitute for the statutory test. The use of advanced programming languages, the customisation of a platform or the provision of technical support does not automatically establish royalty or fees for technical services. The authorities must identify the precise right, technology, knowledge or service that has been supplied.
At the same time, the decision shows that the Revenue may succeed where the evidence establishes that the supplier provided specialised services beyond ordinary software access. The taxpayer’s success on subscription receipts did not carry over to the professional service receipts because the factual character of those services was different.
Conclusion: One Agreement, Different Tax Consequences
The Delhi Tribunal’s decision illustrates why software taxation cannot be resolved by broad labels such as “subscription,” “licence,” “cloud service” or “technical support.” The correct analysis requires a close examination of the rights granted, the technology transferred, the services performed and the knowledge made available to the customer.
The Tribunal found that the software subscription receipts were not royalty or fees for technical services because customers received only restricted access to the taxpayer’s platform. There was no transfer of technology, copyright rights or equivalent proprietary interests. Customisation performed by the taxpayer for its own platform did not, by itself, change that conclusion.
The professional services stood on a different footing. They were availed of by only some customers, were separately charged and varied significantly in value. These features indicated that they involved specialised, customer-specific consultation rather than merely incidental assistance. The Tribunal therefore held them taxable as fees for technical services under domestic law and as fees for included services under the India–US treaty.
The larger lesson is that commercial bundling does not necessarily produce tax uniformity. A single technology agreement may contain several legally distinct supplies. Software access may not be royalty; professional consultation may be taxable as fees for technical services; and the outcome will depend on the actual substance of each component.
For businesses operating across borders, the ruling reinforces the need for precise contractual drafting, separate pricing and careful documentation. For the tax administration, it confirms that the complexity of a technological product cannot eliminate the need to prove the statutory ingredients. The question is not simply whether the customer benefited from sophisticated technology, but whether the customer received a taxable right, a transfer of technology or specialised knowledge that was made available within the meaning of the Act and the applicable treaty.