SaaS and OIDAR GST

Quick View

Why It Matters

OIDAR generally covers services delivered over the internet that are essentially automated and involve minimal human intervention.

Foreign suppliers of taxable OIDAR to specified unregistered or non-taxable online recipients in India can have Indian registration and tax obligations.

Indian businesses receiving taxable overseas SaaS commonly assess import-of-services RCM, while exports require the separate export-of-services test.

Control Framework

Action Checklist

1. Map product features.
2. Measure human intervention.
3. Collect customer location evidence.
4. Validate GSTIN.
5. Configure B2B and B2C invoices.
6. Reconcile foreign payments and RCM.

Practical Example

Evidence to Keep

• Terms of service.
• System-delivery description.
• Customer GSTIN and location data.
• Invoices.
• Payment records.
• RCM or registration working.

Warning Signs

Detailed Review

A defensible GST position must connect the commercial transaction, statutory rule, notification or circular, invoice, books, portal return and electronic ledger. A conclusion supported by only one layer is fragile.

Prepare an issue sheet that records GSTIN, period, tax head, amount, legal provision, effective date, evidence owner and approval. This is especially important where rates, thresholds or portal advisories changed during the year.

Reconcile by CGST, SGST, IGST and cess instead of only by total. An equal total can conceal tax paid to the wrong jurisdiction or credit recorded under the wrong registration.

Maintain original downloads and signed documents. Portal screenshots are useful context but should not replace JSON, returns, bills of entry, e-way bills, IRNs, ledgers, contracts and acknowledgements.

For judgemental matters, document competing interpretations and why one was selected. A short approval note created before filing is more credible than a justification written after a notice.

Run a monthly exception report and assign each difference to business, vendor, customer, tax or system owner. Close only when the corrected document or acknowledgement is retained.

Test one high-value transaction from contract to return every month. Sampling identifies master-data and evidence failures before annual reconciliation.

Transaction Test

Before filing, restate the transaction in one sentence using the legal parties, GST registrations, product or service, value, place, date and consideration. This often exposes hidden assumptions.

Test the result under an alternative fact: different customer GSTIN, delayed invoice, changed vehicle, partial vendor payment, exempt recipient or later cancellation. The control should explain why the tax outcome changes.

Create a gross-to-net bridge from commercial value to taxable value, tax, credit, payment and ledger effect. Avoid unexplained balancing figures.

Reconcile the counterparty’s likely records. Customer ITC, vendor GSTR-1, operator settlement, customs bill of entry and transport documents can contradict internal accounting.

Record the correction route before an error occurs: cancellation, credit note, amendment, reversal, re-availment, refund, DRC-03, representation or appeal.

Capture customer status and location evidence at onboarding. Digital-product configuration should not depend only on payment-card country.

Keep B2B, B2C, domestic, import and export logic separate in the billing engine.

Escalation Route

Start with the commercial record, GST portal data and statutory working. Correct system or document errors through the prescribed process and retain the acknowledgement.

Where the matter is judgemental, disputed or enforcement-related, obtain a reasoned GST and legal review before payment, reply, refund, statement, appeal or restructuring.

Final Control

Management should record the financial exposure, cash-flow consequence, counterparty impact and statutory deadline for every unresolved GST issue. A tax difference can affect customer ITC, pricing, bank limits or business continuity even before an order is issued.

The control is complete only when the corrected invoice, portal filing, ledger entry, payment, refund, ruling, registration or authority communication is received and stored. An internal email saying that the issue is resolved is not closure evidence.