Prior-Approval Controls in Tamil Nadu GST Adjudication: Practitioner-Focused Checklist, SOP, and Reform Blueprint

1. Background and Purpose

Tamil Nadu’s Commercial Taxes administration has reportedly moved towards a more control-based adjudication system through Circular No. 07/2026-TNGST dated **25 June 2026`. As reported in public tax information sources, this framework aims to:

  • Introduce prior supervisory approval before:
    • issuing Suo motu notices,
    • commencing scrutiny of returns under Section 61, and
    • passing ex parte orders; and
  • Build an audit trail that can later be tested for procedural fairness.

While the complete text of Circular No. 07/2026-TNGST was not available in the public domain reviewed here, its issuance and core subject matter are reflected in tax reporting platforms and State GST portals relating to Tamil Nadu.

This write-up is structured to serve three distinct but related needs:

  1. Compliance tool – A detailed audit checklist that assessee and advisors in Tamil Nadu can use to examine notices, scrutiny proceedings, and orders.
  2. Operational guide – A Standard Operating Procedure (SOP) for handling Section 61 scrutiny, Suo motu initiation, and ex parte risk.
  3. Policy input – A governance note suggesting that Karnataka and other States consider a similar prior-approval framework to improve quality, consistency, and defensibility of GST adjudication.

Note: The article builds its framework around the reported intent of the Tamil Nadu circular and the existing statutory scheme. Wherever exact internal instructions are crucial in litigation, the assessee should insist on production of the original circular or approval note from the department file.

2.1 Statutory base – Section 61

Under Section 61, the proper officer is empowered to:

  • Scrutinise returns and related records;
  • Verify correctness of declarations and computations; and
  • On finding discrepancies, inform the registered person and seek an explanation in the prescribed manner.

The scrutiny mechanism is not a demand provision in itself; it is a gateway for verifying return correctness and deciding whether further action (e.g., under demand sections) is warranted.

2.2 Procedural rule – Rule 99 and prescribed forms

Rule 99 operationalises Section 61 through:

  • Form GST ASMT-10 – Communication of discrepancies by the department;
  • Form GST ASMT-11 – Reply and explanation filed by the assessee; and
  • Form GST ASMT-12 – Intimation of acceptance of explanation and closure of scrutiny.

Key features under the current framework:

  • The explanation to ASMT-10 must be filed within 30 days from the date of service of the notice, or within such further time as the proper officer may allow.
  • If the explanation is found satisfactory, scrutiny ends there; if it is unsatisfactory or not furnished, the officer may proceed under relevant demand provisions.

Service date is therefore critical because the reply period runs from that date. In practice, portal availability and electronic communication often serve as the deemed date of service, subject to evidence on record.

2.3 Importance of prior approval in this context

Given that Section 61 scrutiny and ex parte orders can be the stepping-stones to significant tax demands, the reported Tamil Nadu circular appears to insert supervisory review at three crucial junctures:

  • Starting Suo motu action;
  • Initiating scrutiny via ASMT-10; and
  • Passing an ex parte order.

This prior-approval discipline is intended to limit purely discretionary or mechanical actions and to create a defendable record of why scrutiny or ex parte disposal was considered necessary.

3. Reported Changes Under the Tamil Nadu Circular

Public reports referring to Circular No. 07/2026-TNGST suggest the following thematic changes:

  • Suo motu scrutiny is not to be resorted to casually;
  • Prior approval is required before:
    • issuing certain Suo motu notices,
    • triggering Section 61 scrutiny, and
    • finalising matters ex parte.

Since the full circular text was not accessible in the reviewed sources, this article does not reproduce any internal hierarchy. Instead, it outlines an audit framework that practitioners can apply while always verifying actual departmental instructions where legally contested.

Practitioner Caution: When raising the circular in representations or writs, avoid asserting any exact internal rank designations unless the circular itself has been obtained. Instead, request production of the specific approval note or record that the department claims to have relied upon.

4. Mandatory Prior-Approval – An Audit-Oriented View

The prior-approval structure is best treated as an audit matrix that the assessee can use to check departmental compliance.

4.1 Suo motu notices

Where a notice has been issued without a system-generated trigger (for example, not based on standard analytics or automated mismatch reports), it likely falls in the Suo motu category.

Verification points for Suo motu notices:

  • Does the file show:
    • the source of information (e.g., specific third-party data, intelligence input, manual analysis);
    • the discrepancy computation and basis; and
    • the officer who granted prior approval to issue the notice?
  • Is there a recorded reference to:
    • the assessee’s identity,
    • the relevant tax period(s),
    • the section invoked, and
    • the approving supervisory officer?

Audit checkpoint: Treat a Suo motu notice as procedurally suspect where there is no traceable pre-notice approval record or no explanation as to why system-based scrutiny was not adequate.

4.2 Initiation of Section 61 scrutiny

Section 61 scrutiny is formally triggered through ASMT-10.