Compliance Audit Checklist and SOP for Tamil Nadu GST Adjudication Controls

Comprehensive Compliance Audit Checklist and Standard Operating Procedure for Tamil Nadu GST Adjudication Controls| Prior-Approval Discipline for Suo Motu Notices, Section 61 Return Scrutiny, and Ex Parte Orders in Tamil Nadu: A Compliance Audit Checklist, Practitioner SOP, and Administrative Reform Note for Wider State Adoption

Summary: Tamil Nadu’s Commercial Taxes administration has publicly been reported as having introduced a control-oriented framework through Circular No. 07/2026-TNGST dated 25 June 2026, emphasising prior approval before issuing suo motu notices, commencing Section 61 return scrutiny, and passing ex parte orders. The article explains the statutory scrutiny framework under Section 61 and Rule 99 and Forms GST ASMT-10, ASMT-11 and ASMT-12, including the 30-day response period for discrepancies communicated through ASMT-10. It sets out an audit verification matrix for suo motu notices, scrutiny initiation and ex parte orders; practical diary controls; safeguards against arbitrary adjudication; a compliance audit checklist; and an eight-step Standard Operating Procedure for practitioners and registered persons. The article emphasises verification of approval trails, service, discrepancy particulars, reconciliation, hearing records and speaking-order discipline. It further argues that Karnataka should consider a similar prior-approval architecture involving supervisory screening, service and hearing controls and auditable approval records to reduce arbitrary assessments and strengthen procedural fairness.

Overview

Tamil Nadu’s Commercial Taxes administration has publicly been reported as having introduced a control-oriented framework through Circular No. 07/2026-TNGST dated 25 June 2026, with particular emphasis on prior approval before issuing Suo motu notices, commencing return scrutiny under Section 61, and passing ex parte orders. Although the full circular text could not be directly retrieved from the department website in the sources reviewed here, the existence of a Tamil Nadu GST notification series for 2026 and the reported subject-matter of this circular are reflected in tax reporting sources and public Tamil Nadu tax-department portals.

The compliance significance of the reported circular lies not merely in one more internal instruction, but in its attempt to insert supervisory review before coercive or high-impact statutory action begins. For tax practitioners and registered persons, the practical value is that approval checkpoints can be audited, documented, and, where absent, raised as procedural objections at the reply, hearing, rectification, appellate, or writ stage.

This article therefore serves three purposes at once:

1. first, it sets out a detailed compliance audit checklist for Tamil Nadu taxpayers and advisors;
2. second, it provides a working Standard Operating Procedure for managing scrutiny and adjudication risk; and
3. third, it argues that the Karnataka Commercial Taxes Department should adopt an equivalent approval architecture as a governance best practice to reduce arbitrary assessments and improve defensibility of departmental action.

Statutory setting

The legal base for return scrutiny remains Section 61 of the GST law, under which the proper officer may scrutinise returns and related particulars to verify correctness and, upon noticing discrepancies, inform the registered person and seek an explanation in the prescribed manner. The operative procedural rule is Rule 99, under which discrepancy communication is made in Form GST ASMT-10, the taxpayer’s response is furnished in Form GST ASMT-11, and closure upon acceptance is communicated in Form GST ASMT-12.

The core statutory timeline presently reflected in publicly available GST materials is that the explanation to ASMT-10 must be furnished within 30 days from service of the notice, or within such further time as may be permitted by the proper officer. The service date matters because the 30-day period runs from communication of the notice, and portal availability is recognised in GST commentary as the usual deemed date of communication for such scrutiny notices.

The same framework also clarifies the next procedural fork:

• if the explanation is found acceptable, no further action is to be taken in that scrutiny proceeding;
• if no satisfactory explanation is furnished, the proper officer may initiate action under other substantive demand provisions.

That is precisely why the reported Tamil Nadu instruction on prior approval is important: it appears designed to ensure that the very decision to trigger scrutiny or to escalate toward adverse adjudication is not left entirely to unguided field discretion.

What the Tamil Nadu circular reportedly changes

A published report on the June 2026 Tamil Nadu circular states that Suo motu scrutiny notices should not ordinarily be issued and that prior approval is mandated before certain categories of notices and ex parte orders are issued. The same report specifically links the circular to three control points:

• issuance of Suo motu notices,
• initiation of scrutiny under Section 61, and
• ex parte adjudication.

On the materials presently available, the safest way to state the position is this: the circular is reported to have introduced a mandatory prior-approval hierarchy, but the exact designations in each approval layer should be cross-verified from the circular text before being quoted in a formal opinion, notice reply, or appeal memo. A careful practitioner should therefore treat the hierarchy below as a compliance-control matrix based on the reported circular theme and on standard departmental command structures, while insisting on production of the actual internal approval note or circular extract wherever procedural legality is contested.

Mandatory prior-approval hierarchy

Because the directly accessible source presently confirms the existence and subject focus of the circular but does not reproduce the full text, the hierarchy below is framed as an audit verification matrix rather than as a verbatim extraction. In litigation or advisory work, this distinction matters.

A. Suo motu notices

Where the department proposes to issue a Suo motu notice without a system-generated discrepancy trigger, the file should be checked for documented reasons showing the source of discrepancy, the material relied upon, and the authority level that granted prior approval before notice issuance. The practitioner should insist that the approval record identify:

• the taxpayer,
• tax period,
• statutory provision invoked,
• discrepancy basis, and
• the approving supervisory officer.

Audit checkpoint: no Suo motu notice should be treated as procedurally clean unless the file contains a written pre-notice approval trail and a recorded reason why ordinary data-driven scrutiny was insufficient. In a defensive representation, absence of such approval should be argued as evidence of arbitrary initiation and violation of internal binding instructions.

B. Section 61 scrutiny initiation

Section 61 scrutiny is statutorily valid only when discrepancy communication is issued in the prescribed manner through ASMT-10. If Tamil Nadu has mandated prior approval before invoking this scrutiny route, the compliance file should disclose not only the ASMT-10 itself but also the superior officer’s sanction note or electronic approval authorising the scrutiny initiation.

Audit checkpoint: before replying on merits, confirm:

• whether the scrutiny was data-backed,
• whether all returns for the relevant financial year were considered in a consolidated manner as contemplated in GST scrutiny guidance, and
• whether prior approval exists before the ASMT-10 was uploaded or served.

C. Ex parte orders

An ex parte order is the most litigation-prone category because it combines tax demand, civil consequence, and the allegation that the taxpayer did not properly respond or appear. The reported Tamil Nadu circular states that prior approval is also mandated for ex parte orders, which, if followed in substance, creates an internal safeguard against mechanical disposal merely because the file is old or the hearing response is incomplete.

Audit checkpoint: verify whether the adjudicating officer recorded:

• service history,
• response history,
• adjournment history,
• reasons for rejecting written submissions if any, and
• supervisory approval before passing the ex parte order.

If any of these elements are missing, challenge both violation of natural justice and non-compliance with departmental control instructions.

Timelines for ASMT-10 and ASMT-11

The statutory and rule-based position available in the retrieved material is clear on the taxpayer side: ASMT-10 communicates discrepancies and seeks an explanation within a period not exceeding 30 days from the date of service, unless a further period is allowed. The taxpayer’s reply is furnished in ASMT-11 within that 30-day period or within the extended period granted by the officer.

A useful administrative timeline reflected in the scrutiny guidance cited in the search results is that, where the explanation is accepted, ASMT-12 may be issued within 30 days from receipt of reply, and where no reply is furnished, further action under demand provisions may be initiated within 15 days after expiry of the reply period or permitted extended period. While that guidance is not itself the Tamil Nadu circular, it is consistent with the scrutiny architecture under Section 61 and Rule 99.

Practical diary control for practitioners

• Record the portal upload date or other valid service date on the same day the ASMT-10 is noticed.
• Compute the 30-day reply deadline immediately and place a reminder at 10 days, 20 days, and 5 days before expiry.
• If reconciliation is document-heavy, file an extension request before expiry, not after expiry, and preserve acknowledgment evidence.
• If part liability is acceptable, consider calibrated payment through DRC-03 while preserving objection on the disputed balance.
• Do not assume silence by the officer means closure; track ASMT-12 and follow up until a formal closure order is recorded.

Safeguards against arbitrary adjudication

The reported Tamil Nadu circular is important because it recognises, at least in administrative design, that coercive tax action requires supervision before it matures into legally consequential proceedings. Internal approval does not replace statutory compliance, but it helps demonstrate that the officer did not act purely on suspicion, convenience, or revenue pressure.

The main safeguard mechanisms that should be demanded or documented in every scrutiny or adjudication file are the following:

• Written discrepancy note, identifying the exact return period, data source, and calculation basis before any notice is issued.
• Prior supervisory approval for Suo motu notice, Section 61 scrutiny commencement, and ex parte disposal, where the Tamil Nadu circular so requires.
• Proof of valid service under recognised modes, because the reply clock and later adverse action depend on lawful communication.
• Reasoned ASMT-10 content, preferably quantifying tax, interest, and other dues where possible, rather than vague or template allegations.
• Fair opportunity to reply in ASMT-11, including reasonable extension where documents are voluminous or reconciliation depends on third-party data.
• Speaking order discipline, meaning the officer must engage with the taxpayer’s explanation instead of merely reproducing departmental allegations.
• Supervisory review before ex parte order, to test whether the default is genuine non-cooperation or simply defective service, portal failure, or incomplete hearing management.

From a litigation perspective, these safeguards should be pleaded cumulatively, not separately. A defective approval trail, vague discrepancy narration, and denial of adequate opportunity together create a stronger challenge than any one ground taken in isolation.

Compliance audit checklist

The following checklist is designed for internal audit by registered taxpayers, accountants, GST managers, and external consultants in Tamil Nadu.

Pre-notice control review

• Has the business activated a daily notice-monitoring protocol on the GST portal and the Tamil Nadu portal, where relevant?
• Is a responsible officer designated to download, diarise, and circulate every departmental communication on the same day?
• Are reconciliations for GSTR-1, GSTR-3B, books, e-way bill exposure, and ITC support papers updated period-wise?
• Are prior years’ scrutiny replies and closure orders archived for precedent use in current matters?

Notice validity review

• Does the notice clearly mention the statutory section, tax period, discrepancy description, and quantified amount, if ascertainable?
• Is the notice in the correct form, namely ASMT-10 for Section 61 scrutiny?
• Is there an indication, endorsement, or obtainable evidence that prior approval was taken as required under the Tamil Nadu circular?
• Is the discrepancy system-driven, intelligence-driven, or entirely suo motu, and does the file disclose that distinction?

Reply preparation review

• Has the service date been identified and the reply limitation diarised correctly?
• Are reconciliations annexed in a form that a departmental officer can verify without guesswork?
• Are legal objections on jurisdiction, approval, limitation, natural justice, and mismatch methodology taken expressly where available?
• Has extension been sought before expiry if the record is not ready?

Hearing and order review

• Were hearings actually granted, and are hearing notices, attendance, written submissions, and adjournment requests preserved?
• If the matter is being pushed toward ex parte disposal, has the taxpayer demanded disclosure of the supervisory approval required under the Tamil Nadu circular?
• Does the final order discuss each material reply or merely repeat the notice allegations?
• Has the taxpayer evaluated rectification, appeal, and writ remedies immediately on receipt of an adverse order?

Standard Operating Procedure

This SOP is drafted for tax practitioners and registered persons handling scrutiny or adjudication exposure in Tamil Nadu.

Step 1: Notice capture and docket creation

The moment an ASMT-10 or any pre-adjudication communication is seen on the portal, create a digital and physical docket containing the notice, download date, service date, tax period, officer details, and response deadline. A missed first day is often what later causes rushed replies and weak natural justice grounds.

Step 2: Approval-trail verification

Send a measured letter or portal reply request asking for the basis of discrepancy and, where relevant, the prior approval under Circular No. 07/2026-TNGST for Suo motu initiation, Section 61 scrutiny commencement, or proposed ex parte disposal. This request is not merely defensive; it creates a written record that procedural legality was questioned at the earliest stage.

Step 3: Reconciliation assembly

Prepare a discrepancy-wise pack matching return data with books, invoices, e-way bill facts, vendor data, and payment trail, as the case may be. Avoid narrative replies unsupported by ledgers, turnover mapping, rate analysis, or ITC trail documents.

Step 4: Legal issue framing

Separate factual corrections from legal objections. If approval is absent, service is defective, discrepancy narration is vague, or the officer has moved mechanically toward an adverse view, each point should be set out under a separate heading in the reply.

Step 5: ASMT-11 filing within time

File ASMT-11 within 30 days from service or within the formally extended time granted. Where the reconciliation is substantial, file an interim response preserving objections and seek short additional time with reasons.

Step 6: Hearing management

After filing ASMT-11, monitor whether the matter is proposed for closure in ASMT-12 or for escalation. Attend hearings with indexed submissions and insist that any oral clarification be followed by a short-written note placed on record the same day.

Step 7: Ex parte prevention protocol

If hearing notices are irregular, inaccessible, short-dated, or issued despite a pending reply, write immediately objecting to ex parte disposal and refer to the Tamil Nadu approval requirement for such orders. This step is especially important because many ex parte orders are later defended on the ground of taxpayer non-cooperation unless the record shows prompt objection.

Step 8: Post-order remediation

On receipt of an adverse order, carry out a 48-hour review covering service validity, approval-trail deficiency, reply non-consideration, computation error, and available remedial route. Do not wait until the appeal limitation is nearly exhausted.

Flowchart of approval checkpoints

The following text flowchart can be adopted as an internal office control sheet.

1. Discrepancy identified -> source noted (system data / intelligence / officer analysis).
2. Preliminary note prepared -> tax period, issue, quantum, evidence base recorded.
3. Is the action Suo motu? If yes, prior supervisory approval must be obtained before notice issuance as reported under the Tamil Nadu circular.
4. Is Section 61 scrutiny being invoked? If yes, approval checkpoint to be completed before ASMT-10 is generated or served.
5. ASMT-10 served -> 30-day reply clock starts from valid communication date.
6. ASMT-11 received / extension sought -> officer evaluates explanation and supporting documents.
7. Explanation acceptable? If yes, issue ASMT-12 and close scrutiny.
8. Explanation not acceptable / no reply -> before adverse disposal, evaluate whether further proceedings are warranted and whether ex parte route is being considered.
9. Ex parte proposed? If yes, prior supervisory approval should exist under the reported Tamil Nadu framework.
10. Speaking order issued -> order should record service, reply status, reasons, and computation basis.
11. Remedy stage -> rectification / appeal / writ review with emphasis on approval deficiency and natural justice.

Why Karnataka should adopt similar controls

Karnataka’s Commercial Taxes administration would benefit from a formally published approval protocol of the Tamil Nadu type because GST adjudication quality now depends not only on statutory authority but on visible procedural discipline. A prior-approval model reduces the risk of indiscriminate notices, strengthens supervisory accountability, and improves the state’s position when orders are challenged for arbitrariness or breach of natural justice.

For Karnataka, an effective reform model would include:

• prior written sanction for non-system-generated notices,
• compulsory supervisory screening before Section 61 scrutiny for high-value or multi-period cases, and
• mandatory approval before ex parte disposal.

It should also require a discrepancy template, a service checklist, hearing logs, and a closure-review note so that quality control happens before, not after, litigation begins.

Draft administrative recommendations

The following recommendations are suitable for article writing, professional representation, or policy advocacy:

• Every State GST department should publish a taxpayer-facing circular on approval discipline for scrutiny and ex parte action.
• The approval note should be digitally traceable and capable of later production in appeal or judicial review where procedural fairness is disputed.
• ASMT-10 notices should be standardised to disclose the exact mismatch logic and computation source instead of generic allegations.
• Ex parte orders should carry a mandatory certification on service, hearing opportunity, and supervisory approval before final issue.
• State departments, including Karnataka, should adopt auditable dashboards that flag cases where adverse orders are passed without prior reply review or without supervisory sanction.

Closing analysis

Even on the presently available public material, one conclusion is secure: Tamil Nadu’s reported Circular No. 07/2026-TNGST represents a noteworthy shift from officer-centric initiation toward supervisor-reviewed initiation in sensitive GST proceedings. That shift deserves close attention from taxpayers because procedure is often the only effective shield against avoidable demands built on incomplete reconciliation or hurried ex parte disposal.

For practitioners, the most useful response is not merely to cite the circular, but to operationalise it through checklists, docket controls, approval-trail demands, deadline diaries, and structured objections wherever the administrative safeguards appear to have been bypassed. For policymakers, the larger lesson is equally clear: Karnataka and other States should institutionalise similar approval architecture so that revenue administration is both legally sustainable and visibly fair.