Case studies

GSTN: the digital backbone of India's Goods and Services Tax

Case studies · Published 2026-09-25

Two goods lorries on a curving divided highway lined with trees in Gujarat, India
Goods traffic on a highway in Gujarat, India. Photo: TeshTesh, CC BY-SA 4.0, via Wikimedia Commons.

When India replaced a patchwork of central and state indirect taxes with the Goods and Services Tax (GST) on 1 July 2017, the reform depended on a single shared IT system serving the Union government, every state and millions of businesses. The company that runs it, the Goods and Services Tax Network (GSTN), is an instructive example of a sector platform: what it got right, what went wrong, and how its governance evolved.

Why GST needed a shared platform

GST is a destination-based tax levied concurrently by the Union and the states. A sale between two states involves two governments, and the input tax credit that a buyer claims must match tax that a seller actually declared. That requires, in near real time:

Building separate systems for the Union and for each state, and connecting them later, would have been slow and error-prone. A shared platform was chosen instead.

A company, not a department

GSTN was incorporated on 28 March 2013 as a not-for-profit private limited company (under what is now Section 8 of the Companies Act, 2013). Its original shareholding was split between the Union government, state governments and non-government financial institutions, the latter holding a majority of the equity. The structure was meant to give the platform operational flexibility, including the ability to hire technical staff outside government pay scales.

The private majority stake drew criticism over who controlled sensitive taxpayer data. On 4 May 2018 the GST Council, the constitutional body of the Union and state finance ministers that governs GST, decided to convert GSTN into a fully government-owned company, with equity split equally between the Union and the states. The Union Cabinet approved the change in September 2018, and the transfer process followed in 2019.

The API model: GST Suvidha Providers

The most "ecosystem-like" design choice was to avoid making the government portal the only way to interact with GST. GSTN published application programming interfaces and licensed private companies as GST Suvidha Providers (GSPs). These providers, including accounting software firms, banks and technology companies, integrate the APIs into their products, so a business can register, upload invoices and file returns from its own software.

The result is a layered system: GSTN runs the core (registration, returns, matching, payments), while a market of providers competes on user experience, accounting integration and support. Small businesses can still use the free government portal; larger ones rarely do.

E-invoicing: real-time reporting at scale

From 1 October 2020, India introduced mandatory electronic invoicing for large businesses (initially those with aggregate turnover above ₹500 crore). Under the system, an invoice is reported to an Invoice Registration Portal, which validates it, assigns a unique invoice reference number and returns a digitally signed QR code. The data then flows automatically into the GST return system and the e-way bill system used for moving goods. The turnover threshold was lowered in stages, to ₹5 crore from 1 August 2023.

E-invoicing turns the invoice, rather than a monthly return, into the unit of reporting. It reduces manual re-entry and makes fake invoices harder to use for credit fraud, at the cost of requiring businesses to integrate their systems with the portal through providers.

What went wrong

The GST launch was not smooth. In the first months after July 2017, the portal faced heavy load around filing deadlines, return formats were revised and simplified, and deadlines were repeatedly extended. The invoice-matching design originally planned was scaled back in favour of simpler returns while the system and taxpayers adapted. Small businesses in particular reported compliance costs and difficulties with credit reconciliation.

Two lessons stand out. First, the platform was asked to go live on a political deadline with formats that were still changing. Second, the burden of a complex tax design fell on the IT system, which became the visible face of problems that were partly policy choices.

Governance questions

Lessons for other sector platforms

  1. A shared core with open APIs lets private providers carry much of the user-facing work.
  2. Ownership and control of sensitive data must be settled before launch, not after public criticism.
  3. Do not launch a platform on a fixed political date with unstable specifications.
  4. Move toward event-level reporting (e-invoices) gradually, starting with the largest and best-equipped participants.
  5. Publish clear rules on which authorities can access platform data, and why.

Sources