ITC on cloud hosting AWS Azure IT companies: domestic billing and import rules

Cloud infrastructure is the single largest operational cost after payroll for most Indian software firms and SaaS startups. Every month, engineering leads provision computing instances, managed databases, and storage buckets across Amazon Web Services, Microsoft Azure, or Google Cloud Platform. Finance teams face a split compliance workflow depending on whether billing originates from an Indian corporate subsidiary or directly from an overseas parent entity. For multi-branch engineering setups, review our companion guides on GSTR-2B reconciliation for multiple GSTINs and the statutory differences in cross charge vs input service distributor ISD.

Domestic billing versus foreign entity billing

The first step in reconciling cloud hosting expenditure is inspecting the issuing supplier on the tax invoice. Major hyperscalers operate under two distinct contractual models in India:

1. Domestic Indian billing entities: For Amazon Web Services, this is frequently Amazon Internet Services Private Limited (AISPL). For Microsoft Azure, it is Microsoft Corporation (India) Private Limited or authorized cloud solution providers. These domestic subsidiaries hold Indian GST registrations, levy CGST plus SGST for intra-state supplies or IGST for inter-state supplies, and file monthly Form GSTR-1 returns.
2. Foreign entity direct billing: Accounts configured through international portals or legacy agreements are billed directly by overseas entities such as Amazon Web Services Inc. (USA) or Microsoft Regional Sales Pte Ltd (Singapore). Invoices arrive denominated in US Dollars or Euros without Indian CGST or SGST line items.

Under Section 16(1) of the Central Goods and Services Tax Act, 2017, a registered person is entitled to take credit of input tax charged on supplies of services used or intended to be used in the course or furtherance of business. The statutory provisions are published on the official legal repository at Section 16, CGST Act. Official procedural instructions and return user manuals are maintained on the GST Common Portal.

Domestic cloud invoice compliance under Section 16(2)

When an Indian reseller or subsidiary issues the cloud hosting invoice, the credit claim must satisfy all four conditions of Section 16(2):

1. Possession of tax invoice: The buyer must hold a valid tax invoice issued under Section 31 containing mandatory details including recipient GSTIN, name, address, and SAC code (typically 998315 for hosting and IT infrastructure).
2. GSTR-2B reflection: Under Section 16(2)(aa) and Rule 36(4), the supplier must furnish the invoice in Form GSTR-1 or IFF, communicating it to the recipient in Form GSTR-2B. Unreflected invoices cannot be claimed provisionally.
3. Actual receipt of service: The cloud computing and database services must be received and utilized for business operations per Section 16(2)(b).
4. Tax payment and return filing: The supplier must pay the collected tax to the government, and the recipient must furnish Form GSTR-3B under Section 39.

Foreign cloud billing: OIDAR services and reverse charge mechanism

When an Indian business receives cloud hosting from an entity located outside India, the transaction constitutes an import of service. Section 2(17) of the Integrated Goods and Services Tax Act defines Online Information and Database Access or Retrieval (OIDAR) services as services whose delivery is mediated by information technology over the internet or an electronic network. Cloud hosting, digital data storage, and server virtualization fall squarely under this definition. Statutory definitions can be examined on the official portal at Section 2, IGST Act.

Section 13(12) of the IGST Act establishes that the place of supply of OIDAR services is the location of the recipient. When the recipient is located in India, the place of supply is within the taxable territory. Detailed place of supply rules are available at Section 13, IGST Act.

Under Section 14 of the IGST Act, overseas OIDAR providers must register and collect IGST only when supplying services to a non-taxable online recipient (NTOR), which denotes an unregistered person or individual receiving services for personal consumption. When an Indian registered business purchases foreign cloud hosting, the NTOR mechanism does not apply. Instead, the transaction is governed by Entry 1 of Notification No. 10/2017-Integrated Tax (Rate) under Section 5(3) of the IGST Act. The Indian business recipient is legally mandated to pay integrated tax on a reverse charge basis.

Step-by-step reverse charge workflow for foreign cloud invoices

Finance departments handling direct overseas cloud hosting bills should follow this structured compliance sequence every month:

1. Convert foreign currency: Retrieve the foreign currency cloud invoice. Convert the US Dollar or Euro taxable value to Indian Rupees using the exchange rate prevailing on the date of invoice.
2. Issue a self-invoice: Under Section 31(3)(f) of the CGST Act and Rule 36(1)(b), issue a self-invoice referencing the foreign vendor invoice, cloud service description, SAC code, Rupee conversion value, and 18% integrated tax liability.
3. Declare liability in Form GSTR-3B: Report the taxable value and integrated tax amount in Table 3.1(d) (Inward supplies liable to reverse charge). Guidance on table entries is detailed in the GSTN GSTR-3B User Manual.
4. Pay tax in cash: Discharge the Table 3.1(d) liability by debiting the electronic cash ledger during monthly return offset in Table 6.1.
5. Avail full input tax credit: In the very same Form GSTR-3B return, claim the entire integrated tax paid under Table 4(A)(3) (Inward supplies liable to reverse charge). Because the cloud hosting is utilized for business operations, the credit becomes immediately available to offset future outward tax liabilities.

Worked example: domestic versus foreign cloud hosting

For example, consider Vector Labs Private Limited, a software product company based in Bengaluru, Karnataka. In September 2026, the company incurs two distinct cloud infrastructure expenses: an AWS India domestic invoice and a direct foreign database service invoice.

In this worked case, Vector Labs pays ₹90,000 directly to AISPL on the domestic bill. For the foreign bill, Vector Labs pays ₹3,00,000 to the overseas vendor without tax, deposits ₹54,000 integrated tax into the government treasury using cash, and recovers the ₹54,000 as credit in the same tax return. The effective tax cost on both transactions is zero, provided all procedural steps are executed correctly.

Multi-GSTIN architecture and input service distributor requirements

Established technology companies frequently operate development branches across multiple states, such as engineering hubs in Karnataka, Telangana, and Maharashtra. A typical architectural pattern involves maintaining a single consolidated master cloud account managed from corporate headquarters.

When the central office in Bengaluru receives a single monthly AWS or Azure invoice of ₹25,00,000 that hosts production workloads developed by engineers across all three states, claiming the entire input tax credit solely in Karnataka is legally vulnerable. Tax authorities during audit can disallow the credit under Section 16(1) on grounds that services were consumed by distinct persons in other states.

Under Section 20 of the CGST Act (as substituted by the Finance Act, 2024) read with Rule 39 of the CGST Rules, an office receiving invoices for input services on behalf of distinct persons must mandatorily register as an Input Service Distributor (ISD). The ISD mechanism distributes central tax, state tax, and integrated tax pro rata across operating states based on turnover ratios, preventing credit accumulation bottlenecks.

Common reconciliation traps in cloud hosting ITC

In practice, accounts teams auditing technology expenses regularly uncover four recurring errors:

1. Personal credit card payments without GSTIN: Developers paying monthly subscriptions on personal credit cards and submitting expense reimbursement vouchers. Cloud platforms issue receipts without the corporate GSTIN. Credit is entirely lost.
2. Payment delays past 180 days: Under the second proviso to Section 16(2) and Rule 37, if domestic cloud invoices are disputed or withheld beyond 180 days from the invoice date, availed credit must be reversed along with 18% interest under Section 50.
3. Omission of self-invoicing for RCM: Paying foreign vendors through bank wire but omitting self-invoices under Section 31(3)(f). During GST audits, officers question the documentary validity of RCM credit availed in Table 4(A)(3).
4. Supplier filing timing lags: Cloud resellers filing Form GSTR-1 after the 11th of the month. The invoice spills into the subsequent month GSTR-2B, forcing finance teams to defer ITC claims to avoid DRC-01C mismatch notices.

Related guides

• Blocked credit under GST: section 17(5) list with examples
• Restaurant ITC blocked under GST 5 percent
• ITC on club, health and fitness centre corporate memberships
• ITC eligibility on employee term insurance and mandatory gratuity

Frequently asked questions

Last checked: 19 October 2026. Sources: Section 16, CGST Act, Section 2, IGST Act, Section 13, IGST Act, Notification No. 10/2017-Integrated Tax (Rate), GSTN GSTR-3B User Manual, GST Common Portal.