TDS on Foreign SaaS Subscriptions

TDS on SaaS subscriptions like AWS, Zoom, Adobe or Google Workspace usually turns on whether the payment is for accessing a service (often not royalty) or effectively licensing underlying technology.

FY 2026-27 · Section 393(2)

Quick answer

Indicative rate

Often NIL to 20%, depending on classification

Section & code

Section 393(2), Sl. No. 17, Code 1057

Forms typically needed:

Form 15CA Form 15CB if treated as taxable

Cross-Border TDS Decision Helper

Nature of payment

Payee has valid PAN?

TRC + Form 41 furnished?

Indicative Act rate

20%

Domestic Act rate under Section 393(2) for royalty/FTS to a non-resident non-company — doubled from 10% by Finance Act 2023 (effective 1 April 2023), unchanged since. Classify carefully: royalty and FTS have different treaty definitions.

Without a TRC and Form 41, the treaty rate can't be applied — the Act rate above governs until documentation is furnished.

This is a decision aid, not a filing determination — always confirm classification and the exact treaty article with a professional before remitting.

SaaS doesn't fit neatly into the old 'software licence' framework

Cloud subscriptions — AWS, Azure, Zoom, Adobe Creative Cloud, Google Workspace — are structurally different from traditional software licensing. There's no installation, no local copy, and no EULA granting rights to a piece of software the customer possesses. Instead, the customer is paying for ongoing access to infrastructure or a hosted application running on the vendor's servers, which raises its own classification question rather than a straightforward extension of the Engineering Analysis software-licence position.

Tax authorities and practitioners are still working through exactly how SaaS payments should be classified, and the answer can differ by the specific service — pure infrastructure access (like AWS compute) is argued differently than a bundled software-plus-support product.

The 'service, not a copyrighted right' argument

The strongest argument for NIL TDS on many SaaS payments is that the customer isn't acquiring any right to the underlying software's copyright at all — not even a licence to use a copy, since there's no copy involved. They're purchasing a service (compute time, storage, an application interface), similar to renting a fully serviced office rather than buying a copy of blueprints. Under this view, the payment is business income to the foreign vendor, not royalty, and taxable in India only if the vendor has a business connection or permanent establishment here — which most large cloud providers structure carefully to avoid.

Where the classification gets genuinely harder

Some SaaS arrangements blur the line — a platform that gives the customer meaningful control over configuration, embedded proprietary algorithms central to the value delivered, or an arrangement closer to hosting the customer's own use of licensed technology can be argued as closer to a royalty-like payment by a tax authority looking to assess. Bundled products (software plus significant technical support, customization, or training) can also have a mixed character requiring apportionment between a services component and a potential royalty component.

There's no single settled answer covering every SaaS product — this remains a genuinely contested area, with reasonable arguments on more than one side depending on the specific product and contract terms.

A practical approach pending more settled guidance

Given the genuine uncertainty, many practitioners take a documented, product-by-product approach: review the actual terms of service for each major recurring SaaS vendor, form a considered position on classification (with supporting rationale), and apply it consistently rather than defaulting reflexively to either NIL or a flat 20% across every subscription. Where the amounts are material and the classification is genuinely unclear, obtaining a lower/nil deduction certificate under the Section 197-equivalent route removes ambiguity for that specific vendor relationship going forward.

Worked example

A ₹6 lakh annual AWS cloud infrastructure bill

An Indian SaaS startup pays ₹6,00,000 annually to a US cloud provider for compute, storage and networking services with no proprietary software licence element beyond standard infrastructure access. Classified as a service payment (business income to the vendor), and the vendor has no permanent establishment in India, this is generally treated as not taxable in India, and no TDS is deducted — though Form 15CA is still typically filed to support the remittance, and the classification rationale is kept on file.

Common mistakes & litigation traps

Treating every SaaS payment identically

AWS infrastructure access, Zoom's video service, and a bundled software-plus-heavy-support product are different fact patterns — a single blanket policy across all foreign SaaS spend risks getting some of them wrong.

Ignoring bundled support/customization components

Where a SaaS contract bundles meaningful technical support or customization with the subscription, that component may need separate classification as FTS, even if the core subscription itself is treated as a service payment.

Assuming NIL treatment removes the need for Form 15CA

A NIL tax position still generally requires Form 15CA to be filed to support the remittance — it isn't a reason to skip documentation entirely.