Cloud hosting is usually one of the larger recurring technology line items, and its GST treatment depends on something most buyers never check: which legal entity issues the invoice.
An Indian invoice is the simple case
Where the provider bills from an Indian entity with a GSTIN, tax is charged on the invoice, and a business with taxable output claims it as input credit in the ordinary way. Nothing unusual — provided your own GSTIN appears correctly on the invoice.
That last point is worth stating because it is the most common avoidable loss in this category. Hosting is frequently signed up for by a developer using a personal card, with no GSTIN on the account. The invoice is then not in the company's name, and the credit is gone. Over a year of cloud spend this is a real amount.
A foreign invoice does not mean no tax
Where the provider bills from outside India, no Indian tax appears on the invoice. That is not the end of the matter: on import of services, the recipient in India is generally liable under reverse charge — you account for the tax yourself, then claim it as credit if your output is taxable.
For a registered business with taxable output this is usually cash-neutral overall, but it is not optional, and the failure mode is systematic. Cloud invoices are paid by card, booked as an expense, and never reach whoever computes the monthly liability. Twelve months later there is an unreported reverse charge liability that nobody intended to create.
Whether the provider bills from an Indian or an overseas entity can also change over time as providers restructure. Check the entity name on the invoice periodically rather than assuming it is the same as when you signed up.
Where credit is not available
The reverse charge mechanism works well for businesses whose own output is taxable. It works much less well where output is exempt — an educational institution or certain other exempt activities cannot claim the credit, so the tax on foreign cloud spend becomes a real cost rather than a wash.
For those organisations the comparison between an Indian-billed and a foreign-billed provider is not just about price and latency. It is worth running the numbers inclusive of tax.
Place of supply, and why data location is a separate question
For services supplied to a registered recipient, place of supply generally follows the recipient's location. Where your servers physically sit does not determine the tax position.
Data residency is a real consideration for other reasons — sectoral regulation, latency, and client contracts that require Indian storage — but it should be argued on those grounds rather than on tax.
A short checklist for cloud spend
- Every cloud account registered in the company name with the GSTIN on file, not a personal card.
- Know which entity bills you, and re-check when a provider restructures.
- Foreign-billed services flagged to whoever computes the monthly liability, every month.
- Credit-blocked or exempt output identified upfront, because it changes the real cost.
- Annual reconciliation of cloud spend against credit actually claimed — the gap is usually accounts opened outside the process.
GST rates, turnover thresholds and reporting windows change. Verify the current position on the GST portal or with your tax advisor before making a decision based on this.
About the author. Kislay Chandan has worked with schools since 2014. Rather than gathering requirements from the outside, he worked inside a school to see what actually goes wrong day to day, and built what he found into the software. He still works with Shemrock Glitters in Patna — most changes to the product start with something that came up there.
Gallery
