Foreign SaaS company subsidiary in India

SaaS Company Subsidiary
Setup in India

India Is Both a Growing SaaS Market and the World\'s SaaS Engineering Hub

India is one of the fastest-growing SaaS markets globally (estimated USD 20+ billion by 2026 in domestic spend) and simultaneously the talent base for many global SaaS unicorns — Postman, Freshworks, Zoho, BrowserStack, Druva, Innovaccer, MoEngage all built world-class engineering organisations in India. Foreign SaaS companies coming into India have two related but separable questions: how to sell into the Indian market (GST / OIDAR), and how to set up an India engineering organisation (WOS structuring + transfer pricing). This page covers both.

Selling SaaS into India — The GST / OIDAR Map
B2B (GST-registered customer)
  • Indian customer pays 18% GST under reverse charge.
  • Foreign SaaS provider does not need GST registration in India.
  • Customer claims input tax credit; tax neutral for them.
B2C (Indian consumer / unregistered)
  • Foreign SaaS must register under OIDAR (Form GST REG-10).
  • Collect 18% IGST on each subscription.
  • Monthly GSTR-5A return, payment by 20th of following month.
  • No physical presence in India required; remote registration permitted.
India Engineering Subsidiary — The Standard Structure

Most foreign SaaS companies that go beyond just selling and want to build product in India set up a Wholly Owned Subsidiary that acts as a Captive R&D / engineering centre, plus optionally India sales / customer success / partner alliances. Key design choices:

  • Captive R&D model: Indian subsidiary builds the product (or parts of it); IP ownership stays with the foreign parent via cost-plus / cost-sharing arrangement. Mark-up 17–25% depending on function.
  • IP-owning subsidiary: rare; Indian subsidiary owns IP it develops, charges parent royalty. More complex TP and FEMA implications.
  • Sales / marketing reimbursement: sales personnel on Indian payroll, costs reimbursed by parent on cost-plus 10–15% basis.
  • ESOPs: parent\'s stock plan extended to Indian subsidiary; perquisite tax at exercise; structuring around LRS limit for share purchase.
SaaS-Specific Compliance Touch Points
  • Customer agreements: govern-law and dispute-resolution clauses (Delaware vs Indian law for Indian customers); Indian Consumer Protection Act implications for B2C SaaS.
  • Digital Personal Data Protection Act 2023 (DPDPA): requires consent-based processing, data fiduciary obligations, and possibly DPIA / DPO designation for SaaS handling Indian users\' data.
  • Section 194-O (e-commerce TDS): applies to e-commerce platform facilitating sale of goods / services; SaaS marketplaces need to evaluate.
  • RBI data localisation: for payment data, RBI mandates storage of payment data in India; SaaS handling payment information falls under this.
  • SOC 2 / ISO 27001: often required by Indian enterprise customers; framework decided at parent level but operationalised at Indian subsidiary.

Whether you are just starting to sell into India or planning a full India engineering organisation, we cover both — OIDAR / GST registration on day one, WOS setup with TP structuring when you scale, ESOP rollout when you hire.