Withholding Tax on Cloud and SaaS Payments to Non-Resident Vendors

The framework, the Supreme Court's clarification in Engineering Analysis, and the practical workflow for paying foreign cloud and SaaS subscriptions.

The question of whether a payment to a non-resident vendor for cloud computing services or a SaaS subscription is taxable in India has been one of the longest-running uncertainties in cross-border tax. The answer determines whether withholding tax under Section 195 is required at the time of remittance and, by extension, whether the vendor's invoice can be paid in full or with a deduction.

This article explains the framework, the key judicial position, and the practical approach businesses can apply at the point of paying for foreign software, cloud, and platform subscriptions.

The two pathways to taxability

A payment to a non-resident is taxable in India if it is either income arising in India under the Income-tax Act read with the relevant double taxation avoidance agreement (DTAA), or if it falls within the deemed income provisions of Section 9.

For cloud and SaaS, the question almost always reduces to: is the payment royalty under Section 9(1)(vi) (and the relevant DTAA royalty article), or is it business profits that are not taxable in India in the absence of a permanent establishment?

The position under the Income-tax Act

Explanation 2 to Section 9(1)(vi) defines royalty to include consideration for the transfer of rights in respect of any computer software. The Explanation 4 inserted by the Finance Act, 2012 with retrospective effect clarified that royalty includes consideration for the use or right to use any computer software, including the granting of a licence.

The wide definition under domestic law has historically been used by Indian tax authorities to characterise most software payments, including off-the-shelf software, cloud subscriptions, and SaaS, as royalty, attracting withholding tax under Section 195.

The DTAA position and the Supreme Court's clarification

The Supreme Court's decision in Engineering Analysis Centre of Excellence (P.) Ltd. v. CIT (2021) clarified that where a DTAA applies and the DTAA royalty article does not include software or cloud subscriptions within its scope, the DTAA definition prevails and the payment does not constitute royalty.

The reasoning turns on the distinction between the transfer of a copyright in a work and the transfer of a copyrighted article. A typical SaaS subscription gives the customer the right to use the software functionality, not the right to commercially exploit the underlying copyright. Under most DTAAs, only the former amounts to royalty; the latter is a payment for a service or for the use of a copyrighted article that does not fall within the royalty article.

The current practical position

Where the non-resident vendor is in a jurisdiction whose DTAA with India does not bring software or cloud services within the royalty article — which is the case for most OECD-model treaties — withholding tax under Section 195 is not required at the time of remittance, provided the vendor furnishes a valid Tax Residency Certificate (TRC) and Form 10F.

Where the non-resident vendor is in a jurisdiction whose DTAA has a wider royalty article (some Indian treaties include use of equipment or use of process within royalty), the position needs to be assessed treaty by treaty.

Equalisation Levy — withdrawn from August 2024

The two per cent Equalisation Levy on non-resident e-commerce operators (which previously applied to many cloud and digital service payments) was withdrawn by the Finance (No. 2) Act, 2024 with effect from 01 August 2024. The six per cent Equalisation Levy on online advertisement payments remains.

The withdrawal removes one of the two compliance layers on cloud and SaaS payments to non-residents, but does not change the underlying income tax characterisation.

What to do at the point of remittance

The practical workflow at the time of paying a non-resident cloud or SaaS vendor:

• Obtain the vendor's TRC for the relevant calendar year and Form 10F (now required to be filed electronically by the vendor on the income tax portal)
• Review the DTAA between India and the vendor's country of residence — specifically Article 12 (royalties or fees for technical services) and Article 7 (business profits)
• Assess whether the payment falls within the DTAA royalty article based on the nature of the subscription — right to use versus right to reproduce or commercially exploit
• If the DTAA definition does not cover the payment and the vendor has no permanent establishment in India, no withholding tax under Section 195 is required
• File Form 15CA and obtain Form 15CB from a Chartered Accountant for the remittance — Form 15CB documents the analysis above
• Where the assessment is borderline or contested, file Form 15CA Part C with the appropriate justification

The pre-remittance documentation file

For each non-resident vendor relationship, the documentation file maintained at the time of the first remittance should include:

• The vendor's incorporation certificate and TRC
• Form 10F (current year)
• The applicable DTAA text — specifically the royalty article and the protocol
• A note recording the analysis of why the payment does or does not fall within royalty
• The vendor agreement and subscription terms
• Sample invoices showing the basis of the charge

Maintaining this file means that future remittances during the year can be processed quickly, and the analysis is available for inspection during any AO query.

When the analysis is more complex

The straightforward cases are off-the-shelf cloud subscriptions to vendors in OECD jurisdictions. The more nuanced cases include:

• Payments that bundle software with technical services or maintenance, which need unbundling
• Payments for equipment-as-a-service arrangements, where DTAA royalty may include equipment use
• Payments to vendors in jurisdictions with narrower DTAAs (or no DTAA)
• Customised software or implementation services bundled with the subscription

In these cases the analysis is fact-specific and the Form 15CB needs to record the basis for the chosen position.