AWS Cloud Fees Not Taxable: What the Supreme Court Ruling Means

If you run a business in India and pay for AWS, Azure, or Google Cloud, there's a good chance your chartered accountant has told you at some point to deduct TDS on those payments. Many finance teams have been quietly withholding 10% or even 20% on cloud invoices, treating the money as "royalty" or "fees for technical services." The result: cash locked up, awkward conversations with foreign vendors who don't accept net-of-TDS payments, and a compliance headache that never quite goes away.

Here's the number that should make you sit up. In dozens of tribunal and High Court cases over the last decade, the Income Tax Department has argued that AWS cloud payments royalty tax India rules apply, meaning your Mumbai startup or your Pune manufacturer owed withholding tax on every dollar sent to Amazon Web Services. Businesses have paid, contested, and appealed. The recent Supreme Court position on software and cloud payments has now settled a lot of this argument in favour of taxpayers.

In this post I'll break down what the courts actually decided, what it means for your monthly cloud bill and TDS obligations, and the exact steps to fix your treatment if you've been over-deducting. I've helped SMBs across Gurgaon, Bengaluru, and Ahmedabad clean up this mess, so this is practical, not theoretical.

Key Takeaways

• The Supreme Court's reasoning in the software royalty cases means standard AWS/cloud subscription payments are generally not royalty or fees for technical services (FTS), so no TDS under Section 195 is required in most cases.
• If you've been deducting 10–20% TDS on cloud invoices, you may be over-withholding and can stop, subject to a proper review of your specific contract.
• The distinction turns on whether you get a copyrighted product to use (not taxable as royalty) versus the copyright itself (taxable). Standard cloud services fall in the first bucket.
• GST still applies. Import of cloud services attracts 18% IGST under reverse charge, which you claim as input tax credit. This is unchanged.
• Keep your AWS agreement, invoices, and a note from your CA on file. If the department queries you, documentation wins.
• Review past filings with your consultant. Excess TDS deposited in earlier years may be recoverable or adjustable.

Why were Indian businesses paying tax on AWS payments at all?

To understand the ruling you need to understand the fight. Under the Income Tax Act, when an Indian entity pays a foreign company, Section 195 requires you to withhold tax at source if that payment is chargeable to tax in India. Two categories caused all the trouble:

• Royalty under Section 9(1)(vi) and the relevant tax treaty (usually the India-USA DTAA for AWS, since Amazon Web Services bills through its US or Ireland entities).
• Fees for Technical Services (FTS) under Section 9(1)(vii), which covers managerial, technical, or consultancy services.

The tax department's view for years was simple and aggressive: when you pay AWS for EC2 compute, S3 storage, or RDS databases, you're using their proprietary software and infrastructure. Therefore, they argued, you're paying for the right to use copyrighted software and equipment, which is royalty. Deduct 10% under the treaty (or higher without a valid Tax Residency Certificate and PAN).

This created real pain. A SaaS company I worked with in Hyderabad was sending roughly ₹8 lakh a month to AWS. Their CA insisted on 10% TDS. But AWS bills you the full amount and expects payment in full. So the company was effectively "grossing up" the tax, paying an extra ₹80,000+ a month out of pocket that they could never recover from Amazon. Over a year that's nearly ₹10 lakh gone.

What did the Supreme Court actually rule on AWS cloud payments and royalty tax India?

The landmark decision came in the batch of appeals decided as Engineering Analysis Centre of Excellence Pvt Ltd v. CIT in 2021. The core question was whether payments for shrink-wrapped and licensed software to non-resident suppliers were "royalty."

The Supreme Court held that the sale or licensing of software where the end user only gets the right to use the product, without any transfer of copyright, is not royalty. There's a critical legal distinction the Court drew:

• Right to use a copyrighted article (a product): You buy or subscribe to software and use it as intended. This is a sale of goods or a service. Not royalty.
• Right to use the copyright itself: You get the right to reproduce, modify, or commercially exploit the underlying code. This is royalty.

Because standard AWS services, Microsoft 365, Google Workspace, and similar cloud subscriptions give you access to use the platform, not the right to copy or resell the underlying software, they fall squarely into the first bucket. The reasoning has since been applied by tribunals directly to cloud computing and subscription fees, consistently holding that these are not royalty and not FTS.

On the FTS point, tribunals have taken the view that automated cloud services which do not involve human intervention or the transfer of technical knowledge to the customer do not qualify as "fees for technical services." When you spin up an EC2 instance, no AWS engineer is applying skill to your specific problem. The service is standardised and automated. So it isn't technical service income taxable in India either.

The practical upshot: for typical cloud subscriptions, there is no royalty and no FTS, therefore no income chargeable to tax in India, therefore no TDS obligation under Section 195. The department cannot use a domestic law amendment to override a treaty definition unless the treaty itself is amended.

Does this mean I can stop deducting TDS on my cloud bills?

In most standard cases, yes. But do this properly rather than just switching it off overnight. Here's the honest nuance.

The ruling applies cleanly when three things are true:

1. You're paying for a standard, automated cloud service (compute, storage, databases, managed services) as an end user.
2. You are not acquiring the right to reproduce, modify, or resell the underlying software or copyright.
3. The vendor is a tax resident of a country with a favourable DTAA, such as the USA, and you have the supporting documents.

Where you should pause and get advice: if your contract bundles significant professional or consulting services (like AWS Professional Services doing a custom migration for you, or a hands-on architecture engagement), that portion may still be technical service income and could attract TDS. Split the invoice components in your analysis.

Common Mistake: Businesses treat every foreign software invoice identically. But a ₹2 lakh AWS compute bill and a ₹2 lakh "cloud consulting and implementation" invoice from a foreign firm are legally different. The first is generally not taxable; the second may well be FTS. Always look at what you're actually paying for, not just who the vendor is.

A worked example: cleaning up TDS for a Gurgaon logistics SMB

Let me walk through a real-shape example. A 40-person logistics tech company in Gurgaon was running its tracking platform on AWS, spending about ₹6 lakh a month. Their previous accountant had been deducting 10% TDS on the AWS bills for two financial years.

Here's what the numbers looked like:

• Monthly AWS spend: ₹6,00,000
• TDS deducted and deposited: ₹60,000 per month
• Because AWS bills in full, the company grossed up, effectively paying ₹6,60,000 to keep AWS happy.
• Annual leakage from the grossed-up TDS: roughly ₹7.2 lakh they'd never get back.

When we reviewed the AWS Customer Agreement, it was a bog-standard subscription. No copyright transfer, fully automated services, US-resident billing entity. Under the Supreme Court's reasoning, no royalty, no FTS, no TDS.

The steps we took:

1. Documented the position. We got a written opinion from the CA citing the Engineering Analysis judgment and the relevant DTAA articles, and mapped each AWS service line to "standard subscription."
2. Obtained AWS's Tax Residency Certificate and confirmed PAN/No-PE declaration where available, to strengthen the treaty benefit claim.
3. Stopped withholding going forward from the start of the next quarter, saving ₹60,000 a month immediately.
4. Reviewed prior-year filings for whether excess TDS deposited could be corrected. Since they had deducted and deposited on their own account (the tax wasn't legally due), we looked at refund and adjustment options via revised returns and correction statements.
5. Set an internal SOP so any new foreign SaaS vendor gets a two-minute classification check before the first payment.

The upfront cleanup cost them a fraction of one month's leakage. That's the kind of quick win a proper IT and cloud consulting review pays for many times over.

What about GST on imported cloud services? (This didn't change)

This is where I see the biggest confusion. The Supreme Court ruling is about income tax and TDS. It has nothing to do with GST. Your GST treatment on AWS is unchanged.

When you import cloud services from AWS's overseas entity, this is an "import of services" and attracts 18% IGST under the reverse charge mechanism (RCM). You self-invoice, pay the IGST, and then claim it back as input tax credit in the same return, assuming the services are used for your business.

So on a ₹6,00,000 AWS bill:

• IGST under RCM: ₹1,08,000
• Input tax credit claimed: ₹1,08,000
• Net cash impact: broadly neutral, if you have output GST to offset against.

Note that AWS also has an India entity (AISPL) that bills many Indian customers directly with GST on the invoice. If you're billed by the India entity, the GST is charged upfront and there's no RCM to worry about. Check which entity is on your invoice, because it changes both your GST and your TDS analysis.

AWS vs Azure vs Google Cloud vs local hosting for Indian SMBs

Since we're talking cost and compliance, here's a practical comparison I use when advising SMBs on where to run workloads. The tax treatment of standard subscriptions is broadly similar across the big three foreign providers after this ruling.

Criteria	AWS	Microsoft Azure	Google Cloud	Local Indian host
India data centre regions	Mumbai, Hyderabad	Central & South India (Pune, Chennai)	Mumbai, Delhi NCR	Multiple metros
TDS on standard subscription (post-ruling)	Generally none	Generally none	Generally none	Domestic 194J/194C may apply
GST treatment	RCM or India entity GST	RCM or India entity GST	RCM or India entity GST	GST on invoice
Best for	Broadest services, scale	Microsoft-heavy shops, .NET	Data, AI/ML workloads	Simple sites, tight budgets
Typical SMB entry cost/month	₹15,000–₹80,000	₹15,000–₹80,000	₹12,000–₹70,000	₹2,000–₹15,000

If you're weighing local hosting against cloud, we've written a detailed comparison in Reseller Hosting vs Cloud for Indian Agencies. And for the bigger picture on why Amazon is expanding capacity here, see AWS Data Centre Workloads Shift to India.

How to review and fix your cloud TDS treatment: a step-by-step checklist

Here's the walkthrough I'd give any finance team or their vendor. You can run through most of this in an afternoon.

1. Pull your last 12 months of foreign cloud invoices. List each vendor: AWS, Azure, GCP, and any SaaS like Slack, Zoom, Atlassian.
2. Identify the billing entity. Is it a foreign entity (US, Ireland) or an Indian entity charging GST? This determines RCM vs TDS analysis.
3. Classify what you're paying for. Standard subscription/usage (likely not taxable) vs bundled professional services (may be FTS).
4. Check whether you've been deducting TDS. If yes, at what rate, and was it grossed up?
5. Get the vendor's Tax Residency Certificate and No-PE declaration to support treaty benefits.
6. Get a written CA opinion referencing the Supreme Court reasoning for your specific contracts. This is your defence file.
7. Stop over-withholding going forward once the opinion supports it.
8. Assess recovery of past excess deductions with your consultant, considering correction statements and refund routes.
9. Confirm GST/RCM is correctly filed and input credit claimed.
10. Document a standing SOP for new foreign vendors.

Pro Tip: Don't wait for a scrutiny notice to build your documentation. The department can reopen assessments, and a clean file with the vendor agreement, TRC, and a dated CA opinion turns a stressful notice into a five-minute reply. I've seen well-documented SMBs close queries without a single follow-up.

What this means for your cloud strategy and budget

Removing an unnecessary 10% grossed-up cost changes the maths of running on cloud. Workloads that looked expensive when you were quietly bleeding TDS suddenly look a lot healthier. For a company spending ₹5 lakh a month, that's up to ₹6 lakh a year back in the budget.

Reinvest that saving smartly. Optimise your compute commitments (our guide on Reserved Instances vs Savings Plans can cut your bill another 30–50%). Or use the headroom to fund the migration itself if you're still on ageing on-prem servers.

This is also a good moment to think about whether to build in-house cloud skills or bring in help. Our take on the cloud skills gap in India lays out when hiring beats outsourcing. If you'd rather hand the whole thing off, eDarpan's cloud migration and managed services team handles architecture, cost optimisation, and the compliance paperwork end to end.

And if your cloud plans tie into new software or apps, our custom software development and mobile app development teams build cloud-native from day one, so you're not paying to rework things later.

Frequently asked questions

Do I need to deduct TDS on AWS payments in India?

For standard AWS subscriptions and usage-based charges, generally no. Following the Supreme Court's reasoning that such payments are neither royalty nor fees for technical services, they aren't chargeable to tax in India, so Section 195 TDS usually doesn't apply. Confirm your specific contract and vendor entity with your CA.

Are AWS cloud payments treated as royalty tax in India?

No, not in the typical case. Because you get the right to use a service rather than the copyright itself, the payment isn't royalty under the tax treaty definitions the Supreme Court applied. Bundled professional services within a contract may need separate treatment.

Does the ruling apply to Microsoft 365 and Google Workspace too?

The same legal principle applies to standard software and SaaS subscriptions where you only get the right to use the product. This covers common tools like Microsoft 365 and Google Workspace. Get the analysis confirmed per contract, especially where enterprise agreements add services.

Do I still have to pay GST on imported cloud services?

Yes. GST is separate from income tax. Import of cloud services attracts 18% IGST under reverse charge, which you then claim as input tax credit if used for business. The Supreme Court ruling does not change GST at all.

Can I recover TDS I wrongly deducted on cloud bills in earlier years?

Possibly, depending on how and when it was deposited. Options may include correction statements, revised returns, or refund claims, subject to time limits. This needs a case-by-case review with your consultant, since the mechanics vary based on whether you grossed up the tax.

What documents should I keep to defend my no-TDS position?

Keep the vendor's service agreement, the invoices, the Tax Residency Certificate, a No-PE declaration where available, and a dated written CA opinion mapping your services to the ruling. This file makes any department query straightforward to answer.

Does AWS billing through its India entity change anything?

Yes. If the AWS India entity (AISPL) bills you, the invoice usually carries GST directly and there's no reverse charge, and the foreign-payment TDS question doesn't arise in the same way. Check which entity issues your invoice before deciding your treatment.

Getting it right, without the guesswork

The bottom line on AWS cloud payments royalty tax India is genuinely good news for SMBs: the courts have removed a costly and confusing withholding burden that many businesses were carrying unnecessarily. If you've been deducting TDS on cloud bills, you're probably leaving money on the table every single month, and you can fix it with a clean review and proper documentation.

Don't treat this as a one-off. Bake the classification check into your vendor onboarding, keep your paperwork tidy, and revisit your cloud spend for other optimisations while you're at it. The tax saving alone often justifies a full cost review.

If you want a hand reviewing your cloud contracts, cleaning up TDS treatment, or optimising the underlying architecture, eDarpan does exactly this for Indian SMBs. Explore our full range of services, dig into cloud migration and managed services, or just get in touch and we'll tell you honestly whether there's money to be saved. If you're also setting up a new entity and need a compliant registered address, our virtual office for GST and company registration can help there too.

Image credit: Innovate Maryland Emerging Technology Center by MDGovpics via flickr (BY 2.0), sourced through Openverse.