Power to make regulations

Section 165 Regulation compliance — checklist (19 items)

☐ Has the operative Regulation been identified (notification, date, provision)?

☐ Has it been confirmed as a Regulation under s. 165 (not a Rule / Notification)?

☐ Has the Regulation been mapped to the parent Act-provision?

☐ Has the Regulation been mapped to applicable Rules under s. 164?

☐ Has Act-conformity been verified?

☐ Has Rules-conformity been verified?

☐ Has notification compliance been verified (Gazette publication, date)?

☐ Has the Board (CBIC) issuing authority been confirmed?

☐ Has the Regulation-amendment cycle been tracked (current operative version)?

☐ Has Vatika prospective-operation presumption been applied for amendments?

☐ Has the distinction from Instructions under s. 168 been observed?

☐ Has cross-coordination with parallel SGST / UTGST Regulations been verified?

☐ For challenges, has ultra-vires foundation been built?

☐ For Government defence, has intra-vires position been documented?

☐ Has Mohit Minerals framework on Council-recommendation distinction been applied?

☐ Has Mafatlal procedural-fairness framework been observed in Regulation-making?

☐ Has Calcutta Discount Co. delegation-limits been observed?

☐ Has the Regulation-compliance audit trail been documented?

☐ Has the file been reviewed for audit-defensibility?

Example 1 — Identifying applicable Regulation

Facts: A taxpayer's compliance team is researching a specific technical FORM requirement under the GST framework. The team finds a CBIC notification prescribing technical specifications.

Analysis: First — categorise the notification. Is it under s. 164 (Rule), s. 165 (Regulation), or s. 168 (Instruction)? If technical specifications, often it is under s. 165 Regulation or under specific section's notification framework. Verify the legal basis cited in the notification. Apply appropriate framework discipline.

Result: Clean identification clarifies legal effect — Regulation binding, Instruction persuasive.

Example 2 — Regulation inconsistent with Rule

Facts: A Regulation prescribes a 60-day timeline for a specific operational matter. A Rule under s. 164 prescribes a 90-day timeline for the same matter. Department applies the 60-day Regulation timeline.

Analysis: Inconsistency between Rule and Regulation. Section 165 requires Regulation to be consistent with Rules. Regulation prescribing shorter timeline contradicts Rule. Regulation is ultra vires to that extent. Taxpayer's writ challenge sustains the 90-day Rule-given timeline.

Result: Regulation invalid to extent inconsistent with Rule. Rule's 90-day timeline applies.

Example 3 — Regulation amending operational FORM

Facts: Board issues a Regulation amending a specific FORM specification — adding a new column for additional taxpayer disclosure. Taxpayer challenges as ultra vires.

Analysis: Test intra-vires. Operational FORM amendments are within Regulation scope IF they do not create new substantive obligation. Adding a disclosure column may or may not be substantive. If the new disclosure is procedural (rephrasing of existing required information), intra vires. If it creates new substantive disclosure obligation (e.g., disclosing information beyond Act's scope), ultra vires.

Result: Outcome depends on substantive vs procedural character. Calcutta Discount Co. framework guides the analysis.

Example 4 — Regulation vs Instruction distinction

Facts: Department invokes 'CBIC Regulation' in support of a procedural position. On inspection, the document is titled 'CBIC Circular' and cites s. 168 of the Act.

Analysis: Document is an Instruction under s. 168, not a Regulation under s. 165. Legal effect differs — Instruction is administrative guidance; binds Department; taxpayer can take Instruction-based legitimate-expectation defence; Instruction does not create operational obligation enforceable against taxpayer with the same vigour as Regulation.

Result: Clean classification clarifies legal effect. Misclassification by Department invites challenge.

Example 5 — Regulation amendment retrospective effect

Facts: Board issues amendment to Regulation effective retrospectively from 6 months prior. Amendment increases procedural compliance burden. Taxpayer challenges retrospective effect.

Analysis: Vatika prospective-operation presumption. Regulation amendments adversely affecting vested rights operate prospectively unless expressly retrospective and constitutionally justified. Procedural compliance burden may be argued as substantive. Practitioner challenge anchored in Vatika; Government defence — express retrospectivity in notification.

Result: Outcome depends on express language of notification and constitutional justification. Vatika framework is the operative defence.