OIDAR GST in India:
A Guide for Singapore Companies

Executive summary

Of every jurisdiction we cover, Singapore-based companies start from the strongest position — you likely already run a structurally similar regime at home. That's genuinely useful, and also exactly where the risk of a wrong assumption lives.

The concept you already know: Overseas Vendor Registration

If your company is Singapore-incorporated and sells digital services, there's a good chance you've already built compliance processes for exactly this kind of regime — just aimed at Singapore itself.

If your company already administers OVR obligations for its own Singapore-facing digital sales — or even just monitors whether it needs to — that internal process and mindset transfers directly to assessing your OIDAR position for India. The core question ("are we supplying digital services to consumers in another jurisdiction, and does that create a registration obligation there") is identical; only the specific mechanics differ.

The difference that matters most: thresholds

This is the single most important thing for a Singapore company to get right, precisely because your home regime trains you to think in thresholds.

Rate and filing cadence differences

Beyond the threshold question, two operational differences are worth planning around specifically.

Rate: 9% vs 18%

Singapore's GST rate — 9% since 1 January 2024, confirmed stable through Budget 2026 — is exactly half India's 18% IGST rate on OIDAR B2C supplies. If your pricing model was built assuming a Singapore-equivalent tax burden, India's rate needs to be modelled separately, not extrapolated from your Singapore experience.

Filing cadence: quarterly vs monthly

Singapore GST returns are filed quarterly. India's GSTR-5A is a monthly return, due by the 20th of the following month, with mandatory nil returns even in months with no India activity. This is a real operational cadence change — a compliance calendar built around Singapore's quarterly rhythm will under-serve India's monthly requirement if not adjusted specifically.

The marketplace deeming parallel

If you operate a platform rather than a direct-to-consumer service, Singapore's own rules give you a genuine head start on understanding India's equivalent.

India's approach is structured differently in its specifics — a four-condition test determines whether a platform remains a genuine intermediary or becomes the deemed supplier, covered in full on our Marketplaces & Advertising guide — but the underlying principle is the same one Singapore already applies to you: operating a platform doesn't automatically shield you from being treated as the supplier of what moves through it.

Practical points

Local agent requirement — a familiar concept

Singapore's GST Act requires foreign businesses without a local office to appoint a Section 33(1) agent to handle GST registration and compliance. India's OIDAR framework allows (but doesn't strictly require) appointing an Indian authorised representative for the same purpose. If your company already works with a Singapore GST agent, the concept of delegating local compliance to a specialist representative is one you're already comfortable with.

Enforcement detection — also a familiar pattern

IRAS has documented, publicly-stated capability to detect true turnover through bank transaction records, payment platform data, and customs data — regardless of whether a business has issued invoices. India's enforcement approach, covered in our enforcement guide, relies on materially the same kind of data (payment processors, app stores, RCM disclosures). If your compliance culture already assumes IRAS-style data visibility, extending that same assumption to India's tax authorities is the right instinct.

Checklist

Glossary