Implications of the New Withholding Tax Guidelines on SaaS Models

For years, Indian companies paying for cloud-based software — Salesforce, Adobe Creative Cloud, AWS, Notion — operated under a comfortable assumption: these are service payments, not royalties, and therefore attract no TDS under Section 195 of the Income Tax Act. That assumption is now legally unstable.

A series of tribunal and appellate decisions, culminating in sustained pressure from the Income Tax Department post-2022, has revived a dangerous interpretation: that a subscription to software — where the user never acquires source code but merely gains access — can constitute payment for the "use of, or the right to use" a copyrighted work, making it "royalty" under Section 9(1)(vi) of the Income Tax Act, 1961, read with the applicable Double Tax Avoidance Agreement (DTAA).

The war began with a definitional ambiguity baked into Indian tax law itself. When the original Income Tax Act was drafted, software — as a commercially distributed product — did not exist. The word "copyright" in Section 9(1)(vi) was understood to mean creative works (books, music, films). But technology licensing agreements increasingly grant access to works that indisputably carry copyright protection under the Copyright Act, 1957.

The OECD's official position, codified in its 2017 Commentary on Article 12 of the Model Convention (the Royalty Article), is clear: payments for "shrink-wrap" or standard commercial software are generally NOT royalties because the end-user receives no copyright rights — they acquire only the right to use the program for personal or business purposes. This position was adopted by the Supreme Court of India in Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT [2021] 432 ITR 471, which explicitly held that payments for software licenses do not constitute royalty under many Indian DTAAs.

Here is where SaaS complicates everything. In a traditional software purchase, you get a perpetual licence to a file installed on your machine. In a SaaS model, you access software hosted by the vendor on their servers. You never possess the software. You never see the code. You are — arguably — paying to access something that lives in a data centre in Virginia or Dublin. The question then shifts: are you paying for a "service" (access to servers) or for the "use of" a copyrighted work running on those servers? The Income Tax Department's Assessing Officers increasingly treat this as the latter.

The practical danger is this: if your company paid, say, ₹3 crore annually to a US SaaS provider without withholding tax, and the AO holds the payment to be royalty, you are liable not only for the unpaid TDS (potentially 10% under the DTAA or 20% under domestic law) but also for interest under Sections 201(1A) and penalty under Section 271C. On ₹3 crore over three assessment years, the total demand can easily exceed ₹1.5 crore.

One structural mitigation increasingly being used: restructuring the commercial agreement itself. When a contract is documented as a "Cloud Services Agreement" providing compute, storage, and access — with the software explicitly described as incidental to service delivery — the royalty characterisation weakens considerably. This requires vendor cooperation (not always forthcoming from US multinationals) but can be achieved through addendum agreements for Indian entities. The documentation burden is significant, but the penalty exposure is more so.

Companies should not wait for notices. Proactive TRC collection, contractual reclassification where feasible, and a clear disclosure strategy in the tax audit report (Form 3CA/3CB) will significantly reduce the risk of penalty-grade outcomes. The law is unsettled; your documentation should not be.