GST Annual Return / GSTR-9 9C

GSTR-9 and GSTR-9C Readiness

CA Nikhil Gupta·June 2026·3 min readGST Annual Return / GSTR-9 9C

Annual return is a reconciliation of twelve monthly positions, not a thirteenth opportunity to rewrite every return.

Quick View

Decision

Lock monthly bridges and determine year-specific filing applicability early.

First action

Confirm filing threshold.

Core evidence

Year-specific notification.

Main warning

Using financial revenue as taxable turnover.

Why It Matters

GSTR-9 applicability and exemptions are notification-specific for each financial year. The business should not assume one threshold remains unchanged indefinitely.

GSTR-9C is a self-certified reconciliation statement for taxpayers above the notified turnover threshold, commonly exceeding ₹5 crore for the relevant years.

Annual disclosures should reconcile books, GSTR-1, GSTR-3B, ITC records, electronic ledgers and financial statements.

Control Framework

AreaWhat to establishOperating rule
ApplicabilityYear-specific notification and aggregate turnover.Document conclusion.
OutputBooks versus GSTR-1 and 3B.Bridge amendments.
ITCBooks, 2B, reversals and ineligible credit.Reconcile fully.
FinancialsGSTIN-wise extraction from audited accounts.Explain allocations.

Action Checklist

  1. Confirm filing threshold.
  2. Freeze monthly reconciliations.
  3. Prepare turnover bridge.
  4. Prepare ITC bridge.
  5. Review prior-year transactions.
  6. Approve annual disclosures and payment.

Practical Example

A multi-state company’s audited revenue is consolidated by entity, while GSTR-9C is GSTIN-specific. The business must allocate inter-branch and non-GST items before reconciliation.

Evidence to Keep

  • Year-specific notification.
  • Financial statements.
  • GSTR-1 and 3B data.
  • GSTR-2B and ITC registers.
  • E-invoice and e-way reports.
  • Annual-return workings.

Warning Signs

  • Using financial revenue as taxable turnover.
  • Ignoring GSTIN allocation.
  • Treating 9C as auditor certification.
  • No prior-period bridge.
  • Filing without payment decision.

Detailed Review

A defensible GST position must connect the commercial transaction, statutory rule, notification or circular, invoice, books, portal return and electronic ledger. A conclusion supported by only one layer is fragile.

Prepare an issue sheet that records GSTIN, period, tax head, amount, legal provision, effective date, evidence owner and approval. This is especially important where rates, thresholds or portal advisories changed during the year.

Reconcile by CGST, SGST, IGST and cess instead of only by total. An equal total can conceal tax paid to the wrong jurisdiction or credit recorded under the wrong registration.

Maintain original downloads and signed documents. Portal screenshots are useful context but should not replace JSON, returns, bills of entry, e-way bills, IRNs, ledgers, contracts and acknowledgements.

For judgemental matters, document competing interpretations and why one was selected. A short approval note created before filing is more credible than a justification written after a notice.

Run a monthly exception report and assign each difference to business, vendor, customer, tax or system owner. Close only when the corrected document or acknowledgement is retained.

Test one high-value transaction from contract to return every month. Sampling identifies master-data and evidence failures before annual reconciliation.

Transaction Test

Before filing, restate the transaction in one sentence using the legal parties, GST registrations, product or service, value, place, date and consideration. This often exposes hidden assumptions.

Test the result under an alternative fact: different customer GSTIN, delayed invoice, changed vehicle, partial vendor payment, exempt recipient or later cancellation. The control should explain why the tax outcome changes.

Create a gross-to-net bridge from commercial value to taxable value, tax, credit, payment and ledger effect. Avoid unexplained balancing figures.

Reconcile the counterparty’s likely records. Customer ITC, vendor GSTR-1, operator settlement, customs bill of entry and transport documents can contradict internal accounting.

Record the correction route before an error occurs: cancellation, credit note, amendment, reversal, re-availment, refund, DRC-03, representation or appeal.

Use year-specific notifications for GSTR-9 and GSTR-9C rather than copying the preceding year’s applicability.

Lock the source version of each monthly reconciliation used in the annual return.

Escalation Route

Start with the commercial record, GST portal data and statutory working. Correct system or document errors through the prescribed process and retain the acknowledgement.

Where the matter is judgemental, disputed or enforcement-related, obtain a reasoned GST and legal review before payment, reply, refund, statement, appeal or restructuring.

Final Control

Management should record the financial exposure, cash-flow consequence, counterparty impact and statutory deadline for every unresolved GST issue. A tax difference can affect customer ITC, pricing, bank limits or business continuity even before an order is issued.

The control is complete only when the corrected invoice, portal filing, ledger entry, payment, refund, ruling, registration or authority communication is received and stored. An internal email saying that the issue is resolved is not closure evidence.

Frequently Asked Questions

Is GSTR-9 compulsory for everyone?
Applicability and exemptions depend on the relevant year’s notification.
What is the common GSTR-9C threshold?
It has generally applied above ₹5 crore aggregate turnover, subject to year-specific law.
Can annual return revise monthly returns?
It reports reconciled information but is not a substitute for every correction mechanism.
Who certifies GSTR-9C?
It is a self-certified reconciliation statement under the current framework.