FORM GST REG-22 — Order revoking cancellation of registration
Reviewed by CA Nikhil Gupta and Kajri Singh · Last Reviewed 12 September 2026
2-minute answer
FORM GST REG-22 — Order revoking cancellation of registration explained with current GST law, filing/response steps, evidence checklist, official CBIC/GST sources.
How to use this page
FORM GST REG-22 — Order revoking cancellation of registration is most useful when you first identify the transaction or procedural trigger, then match the statutory provision/form to the correct tax period and portal step. Keep the notice, return, invoice or application data tied to the exact GSTIN and period.
Practical checklist
- Confirm the taxpayer/GSTIN, tax period and the legal trigger before filing or replying.
- Reconcile the page with the current CGST Act/Rules, notifications and portal instructions.
- Preserve ARN/acknowledgement, working papers, invoices/notices and any reply or order.
- Do not treat portal acceptance as proof that the legal classification or amount is correct.
Worked use case
Example: if two periods or two GSTINs are involved, prepare separate fact packs before using the form/provision. That prevents a correct legal rule from being applied to the wrong registration or tax period.
Official-source checks
Related Finin2min guidance
Reviewed for currentness: 12 September 2026. Educational/professional reference; the controlling law, notification, order or official filing instruction prevails.
Official sources
Use the official source for the controlling wording, footnotes, effective date and amendment history.
Official sources checked: 12 September 2026. Historical-period questions require the version applicable to the transaction date.
Form in 2 Minutes
FORM GST REG-22 is used for order revoking cancellation of registration. It belongs to the Registration workflow. Never select the form by filename alone: first identify the legal trigger, operative Rule, tax period and current portal version.
Legal trigger and mapped Rules
- Family rule framework: Rules 8–26 and current registration amendments.
- Primary user/system owner: Applicant / proper officer / common portal.
- Check whether the form is taxpayer-filed, officer-issued, system-generated or a ledger/register rather than a filing form.
- Check effective date and any amendment substituting the form or its instructions.
Field-by-field control checklist
- GSTIN / legal identity and jurisdiction
- Correct tax period, financial year or proceeding reference
- Authorised signatory / verification
- Version-controlled attachments and supporting evidence
- PAN/constitution and promoter or authorised-person particulars
- Principal/additional place of business and address evidence
- Aadhaar/biometric/document verification where the applicable rule requires it
The list is a control checklist, not a reproduction of the official blank form. The current GST portal / notified appendix controls the exact field schema.
Portal and filing workflow
- Identify the exact statutory trigger and current form version.
- Prepare a reconciled offline working before portal entry.
- Upload only prescribed and relevant evidence; cross-check names, periods and amounts.
- Preview the generated form/PDF and obtain signatory approval.
- Submit through the current portal channel; preserve ARN/acknowledgement and generated PDF.
- Track deficiency, notice, order, payment or appeal consequence until closure.
Before you click Submit — 10 checks
- Correct GSTIN/PAN/UIN and jurisdiction.
- Correct tax period / financial year / order reference.
- Correct legal form for the trigger.
- Current version of the form and portal utility.
- Amounts tie to books, returns, ledgers and notices/orders.
- All statutory conditions tested separately from portal validation.
- Attachments are legible, complete and relevant.
- Signatory and authorisation are current.
- Payment / pre-deposit / fee is correctly linked where applicable.
- Final preview and evidence pack are archived before and after submission.
Practical case study
A user reaches FORM GST REG-22 only after fixing the legal trigger. The preparer first reconciles the underlying books/return/order, checks the operative Rule and current version of the form, completes the portal submission from the approved working, then stores the generated form, ARN/acknowledgement, supporting documents and any later notice or order as one evidence pack.
Evidence and retention file
- Official form/version or portal-generated PDF used.
- Underlying statutory notice, order, invoice, ledger, return or registration evidence.
- Reconciliation/computation supporting each material figure.
- Attachments and approval/signatory record.
- ARN, acknowledgement, payment proof and subsequent communications.
- Snapshot/link to the controlling Rule/notification relied upon.
Common mistakes
- Using a legacy saved form after the Rule or portal schema changed.
- Entering portal values before reconciling the books and statutory trigger.
- Assuming portal acceptance proves legal eligibility.
- Missing limitation, response, payment or pre-deposit dates.
- Failing to retain the exact submitted version and attachments.
Finin2min Q&A
What is FORM GST REG-22 used for?
Order revoking cancellation of registration. Confirm the current Rule and portal version before use.
Which Rule should I read before using this form?
Rule 23(2) of the CGST Rules, 2017. The Act and effective amendment notification also prevail.
Can I use a PDF saved last year?
Not safely without checking whether the form or instructions have been substituted. Use the current notified/portal version.
What should I archive?
The final submitted/issued form, working papers, attachments, authorisation, ARN/acknowledgement, payment proof and final notice/order or certificate.
Does portal acceptance mean the tax position is correct?
No. The portal validates system rules; legal entitlement and consequences remain governed by the Act, Rules and valid instruments.