GST / Appeals

GSTAT Appeal Readiness

CA Nikhil Gupta·June 2026·4 min readGST / Appeals

An appeal should challenge specific findings in the order, not repeat the reply submitted during assessment.

Quick View

Decision

Start the appeal file on the order date and verify the current bench, portal and statutory pre-deposit before filing.

First action

Record order-service date.

Core evidence

Demand and first-appeal orders.

Main warning

Using outdated pre-deposit percentage.

Why It Matters

Section 112 governs appeals to the Appellate Tribunal. Limitation, condonation, pre-deposit and filing procedure must be checked against the law effective on the appeal date.

The appeal should separate jurisdiction, natural justice, factual errors, legal interpretation and computation grounds.

New evidence at appellate stage can face restrictions, so the record from notice and first appeal should be indexed carefully.

Control Framework

AreaWhat to establishOperating rule
OrderService date and findings.Calculate limitation.
GroundsEach error and relief sought.Avoid narrative only.
AmountAdmitted tax, disputed tax and pre-deposit.Reconcile ledgers.
RecordNotice, reply, hearing and orders.Create chronology.

Action Checklist

  1. Record order-service date.
  2. Obtain full lower record.
  3. Prepare issue-wise grounds.
  4. Calculate pre-deposit under current law.
  5. File through notified process.
  6. Preserve ARN and hearing updates.

Practical Example

An order confirms ₹50 lakh demand but addresses only two of five reply grounds. The appeal should identify the ignored submissions and natural-justice prejudice with record references.

Evidence to Keep

  • Demand and first-appeal orders.
  • Notice and replies.
  • Hearing records.
  • Tax and pre-deposit working.
  • Grounds and case-law file.
  • Appeal acknowledgement.

Warning Signs

  • Using outdated pre-deposit percentage.
  • Counting limitation from memory.
  • Generic grounds.
  • No proof of order service.
  • Adding unsupported facts.

Detailed Review

GST control should connect five records: commercial contract, tax invoice, movement or service evidence, accounting entry and portal return. A filing that cannot be traced back to all five records is difficult to defend.

Every reconciliation should have a clear opening balance, current-period additions, corrections, reversals, payments and closing balance. Avoid unexplained plugs that make the total match but do not identify the invoice or legal reason.

Portal data is important but not conclusive by itself. GSTR-2B, e-invoice, e-way bill and ledger data should be read with the statute, rules, notifications, contracts and actual supply evidence.

Keep original source files and final filed versions. Screenshots help explain a portal event but should not replace downloaded returns, JSON, signed invoices, acknowledgements or bank records.

For material exposure, prepare a written position memo stating facts, issue, law, alternatives, conclusion, amount and approval. The memo should record uncertainty rather than hide it.

The litigation file should contain the notice, relied-upon documents, reply, evidence index, hearing request, hearing record and order in chronological order. Missing procedural records can be as important as the tax computation.

Separate admitted liability from disputed liability. Payment of one issue should be expressly linked so it is not misunderstood as acceptance of every allegation.

Escalation Route

Start with the GST portal record, responsible business owner and tax working. Where the issue is operational, correct the source system and retain the acknowledgement. Where it is legal or disputed, obtain a reasoned professional position before payment, reply, refund or appeal.

Track the statutory or portal deadline separately from internal approval. Preserve helpdesk tickets, ARN, hearing requests, orders and payment records so a later reviewer can reproduce the entire path.

Transaction Test

Before filing or replying, prepare a one-page issue sheet showing GSTIN, tax period, transaction type, amount, applicable provision, portal form, evidence owner and due date. This prevents different teams from solving different versions of the same problem.

Reconcile tax by CGST, SGST, IGST and cess rather than only by total. A total can match even when the wrong tax head, state or period has been used, which can still create interest, cash-flow and customer-credit consequences.

Build an exception register with five statuses: identified, evidence pending, vendor or customer action, tax treatment approved and closed. Every exception should retain its original amount even after correction so the audit trail remains visible.

Test the position against the counterparty’s records. Customer ITC, vendor GSTR-1, transporter data, marketplace statements and bank receipts can expose differences that are invisible in the taxpayer’s own ledger.

The final approval should record who reviewed the legal position and who approved the return, reply, payment, refund or appeal. Material GST decisions should not remain buried in informal email chains.

Create a chronology beginning with the transaction and ending with the current proceeding. Include every notice, adjournment, hearing, payment, submission and portal acknowledgement.

For each ground, cite the supporting annexure number and the exact page or row. Authorities should not have to search a large unindexed attachment to find the evidence.

Frequently Asked Questions

What pre-deposit applies? â–¼
Use section 112 as effective on the filing date and current portal instructions.
Can delay be condoned? â–¼
Limited condonation may be available subject to law and reasons.
Can new evidence be filed? â–¼
Appellate rules restrict additional evidence; explain why it was unavailable earlier.
Is GSTAT procedure uniform? â–¼
Verify the notified bench and current electronic process.