Why has the centre of gravity in GST moved from rate policy to enforcement?

Most companies engage the Government on GST where policy is made: the Tax Research Unit, the Fitment Committee, the Council. The Government's own record of action points elsewhere: biometric checks at registration, drives against fake registrations, detection by data analytics, Track and Trace on goods, credit blocking for a year. The financial consequences of GST now arrive mostly through this second architecture: blocked credits, notices, summonses, rather than rates. What does the enforcement build reveal about how the state now polices GST, and what does it ask of a Government Affairs function?

Read the enforcement list slowly and a pattern appears. Biometric checks guard the entry into the system, before a single invoice exists. E-invoicing watches the transaction the moment it is issued. The Invoice Management System watches the invoice when the buyer receives it. Data analytics watches patterns across thousands of firms at once. Track and Trace follows the goods themselves. Credit blocking freezes money while a chain of transactions is examined. None of this is the old tax audit, where an officer opened one company's books. The state has stopped auditing taxpayers one by one and started policing the chain of transactions; a company is examined as a link in that chain, not on its own record.

That changes where a company's risk comes from. A buyer with perfect filings loses credit because a supplier kept the tax. A manufacturer finds its credit frozen because an investigation is running somewhere upstream among its vendors. A finance head receives a summons because a counterparty two links away is under investigation. The company's own clean record does not protect it, because its own record is not what is being policed. A company's GST risk is set by the compliance health of its supply chain, and that risk is acquired when a vendor is onboarded, not when a return is filed.

This is why the Government Affairs brief on GST has split into two different jobs. The first is the familiar one: the policy side, where rates and rules are made, through the Tax Research Unit, the Fitment Committee, the Groups of Ministers, the Council. A good argument, carried at the right time, can move this side. The second is the enforcement side: the GST intelligence directorate, the local commissionerates, the portal advisories, the Board's instructions to its own officers. Arguments and association letters carry no weight here; what matters is the quality of the record, the discipline of the timeline, and the limits the Board's own instructions place on the officer. Most GA teams are staffed for the policy side and meet the enforcement side for the first time when a summons arrives, after the positions that mattered have already been taken.

The useful news is that the enforcement side announces itself. The registration drives are press-released before they run. New instruments arrive by notification, with lead time. The portal publishes its tightenings weeks in advance. The Board's instructions to officers, on summons restraint, on recorded reasons before blocking credit, are public, and they are the compliant company's procedural shield when the knock comes. Even the Government's own progress reports are a signal: what a department lists as its achievement is what it intends to do more of. The enforcement machinery telegraphs its next move in its own publications; the GA team that reads that paper trail every quarter stays a quarter ahead of the team that reads only Council press releases.

What the shift asks of the function is presence at both doors, with different postures. Keep the policy doors for design asks; that work remains real. Add a standing watch on the enforcement stream, and treat the client's supply chain as part of its regulatory perimeter, screened and contracted accordingly. A rate representation, won, protects the client once. Reading where the policing is going protects it every quarter, before the matter ever has a file number.