Skip to main contentSkip to content
GST Law Hub
CGST Rule 9: Rule 9 - Verification of the application and approval | Finin2min

CGST Rule 9 — Verification of the application and approval

CGST Rules, 2017
CURRENT CONTROLLEDRepository module RULE CONTROL
Source control: The text/status on this page is tied to the official source gateway and the Repository module legal-review register. Open official source.

Official sources

Use the official source for the controlling wording, footnotes, effective date and amendment history.

Source review date: 2026-07-28. Historical-period questions require the version applicable to the transaction date.

Finin2min Summary - Rule in 2 Minutes

The proper officer examines a registration application and either approves it within 7 working days, or issues a notice (REG-03) seeking clarification if it is deficient; failure to act within the prescribed time deems the registration granted.

official statutory reference

Paragraph-wise decode

If the application is found in order, registration is granted within 7 working days (30 days where Aadhaar authentication is not opted for/fails, requiring physical verification). If deficient, a notice in FORM GST REG-03 is issued within that period; the applicant replies in FORM GST REG-04 within 7 working days, after which the officer approves or rejects (FORM GST REG-05) within a further 7 working days.

Section-Rule-Form-Notification bridge

No direct Rule certified in Repository module. Check notifications, circulars, forms and corresponding State law.

The mapping is a legal concordance, not a round-robin related-link list. It is limited to instruments listed in this repository.

Practical example

An applicant who does not complete Aadhaar authentication has the physical-verification route apply, extending the approval timeline to 30 days from the date of application instead of the standard 7.

Professional alert

Do not assume every later amendment has the same effective date; each amending notification must be checked separately.

Implementation checklist

  1. Fix the transaction, taxable period and jurisdiction.
  2. Read every subsection, proviso, explanation and omission marker.
  3. Open the mapped Rule, form, notification and circular.
  4. Test State/UT variation and portal version.
  5. Preserve evidence, approvals, working papers and acknowledgements.
  6. Record the conclusion, assumptions, source date and reviewer.

Evidence and retention checklist

Practical Q&A

What does rule 9 regulate?
It regulates rule 9 - Verification of the application and approval. Read the exact text, conditions, exceptions and transaction date together.
Which subordinate law should be checked?
No direct CGST Rule has been listed in this repository. Notifications, circulars, forms and the corresponding SGST/UTGST layer may also apply.
What evidence should be retained?
Preserve the contract or transaction record, invoice or form, portal acknowledgement, payment/ledger evidence, correspondence, legal working and the official source version used.
Can portal behaviour override the statute?
No. Portal functionality is operational evidence; legal entitlement and liability remain controlled by the Act, Rules, notifications and binding decisions.

Repository module professional rule control

Legal state: Current controlled · Checked: 27 July 2026. Current legal/release state is controlled by the Repository module master; read the official statutory reference and amendment history together.

Why Rule 9 matters

Verification of the application and approval should be read with its enabling CGST Act provision, prescribed forms, amendment notification, transaction date and the live portal workflow. The operative-text block already released on this page remains the legal core; Repository module adds application controls without altering that block.

Rule → Form → evidence bridge

  • Confirm the Rule version that was operative on the relevant date.
  • Check every proviso, explanation, inserted/omitted sub-rule and commencement notification.
  • Use the current prescribed form/portal utility rather than a saved legacy template.
  • Preserve the Rule source, filing/approval evidence, computation and decision-maker trail.

Finin2min decision path

  1. Trigger: What transaction, registration event, return, credit, valuation, refund, appeal or enforcement event activates this Rule?
  2. Date: Which Rule version and amendment notification applied on that date?
  3. Conditions: Have every mandatory condition and exception been tested?
  4. Form/portal: Is the prescribed form or electronic workflow the correct current version?
  5. Evidence: Can the conclusion be reconstructed from books, invoices, portal records and official sources?

Practical cases

New registration

Identify the correct registration route, authentication requirement, supporting evidence and system/officer action.

Change or cancellation

Check whether the trigger is taxpayer-initiated, system-driven or officer-initiated and use the correct REG form sequence.

Evidence failure

A portal acceptance does not cure false premises, identity, bank or constitutional-document evidence.

Accounting, ERP and portal controls

  • Do not let an ERP default or portal auto-population override the legal Rule.
  • Map the Rule trigger to the correct tax period and retain before/after reconciliation where values change.
  • Archive ARN, acknowledgements, generated PDFs, payment/ledger records, notices and orders where applicable.

Notice and litigation risk

  • Separate a portal mismatch from a statutory breach; they are not automatically the same issue.
  • Identify whether a circular/instruction is clarificatory or whether an amendment changed the Rule itself.
  • Apply judicial hierarchy: Supreme Court → jurisdictional High Court → other High Courts → GSTAT; AAR/AAAR is not universal precedent.

Common mistakes

  • Using today's Rule for an older transaction without an effective-date test.
  • Reading a form instruction as if it overrides the Act or Rule.
  • Ignoring State/UT procedural overlays where the Rule requires a local notification or officer action.
  • Treating a source-gated local reproduction as cleared statutory text.

Finin2min Q&A

What does CGST Rule 9 deal with?
Verification of the application and approval. Start with the operative Rule version and then test the connected Act provision, forms and amendments.
Which GST form is connected to Rule 9?
REG-03, REG-04, REG-05 The Rule and live portal workflow control.
Can I rely only on the GST portal?
No. Portal functionality is execution infrastructure; legal eligibility and consequences come from the Act, Rules and valid instruments.
What should I keep on file?
The official Rule version used, amendment/effective-date evidence, underlying transaction records, computation, portal submission and resulting acknowledgement/order.