Most of the commentary written this summer told corporate taxpayers to file before 31 July 2026. That deadline has passed, and the commentary has moved on. It should not have. A large cohort of appellants did not file by 31 July — they generated a token, and their appeals are now sitting on a 60-day clock that nobody is watching.
For tokens generated on the last day, that clock runs out around 29 September 2026. When it does, the appeal is not late. It is dead.
This note sets out where limitation now stands, why the condonable window may be a month longer than the published commentary says, and what remains when the Tribunal's door has closed.
1. The instrument everyone missed
On 10 July 2026, the Principal Bench issued Order No. 156/2026 (F.No. ADM-ADMI/40/2026-AR-PRGSTAT 601), under Rule 123 of the GSTAT (Procedure) Rules, 2025, referencing a Department of Revenue letter of 9 July 2026.
The mechanism is simple and the exposure is not. An appellant unable to complete filing — portal upload failures, DSC/EVC validation errors, payment gateway failures — could generate a Token ID by furnishing minimum particulars: GSTIN, Temporary ID, UIN or TDS registration, plus either the 16-digit ARN/CRN of the first appellate order or the order number, reference number and tax period.
A token generated on or before 31 July 2026 is treated as sufficient compliance with the statutory filing deadline. The substantive appeal must then be completed within 60 days of token generation. Only then is it, in the Tribunal's words, considered validly filed within the due date prescribed under the Act.
Four features of that mechanism deserve more attention than they have received:
One token, one appeal. A token is a 1:1 mapping. It is not a blanket placeholder for a group of appeals against related orders — a distinction that matters for any taxpayer carrying multi-year demands across periods.
The 60 days are hard. A lapsed token cannot be revived. There is no cure provision, no extension mechanism, and no application to restore.
Voidance is retrospective. The Tribunal expressly reserved the right to treat a token as void where it was generated with incomplete or inaccurate particulars. Voidance operates backwards. Because 31 July has passed, a token declared void in September leaves the appellant with no limitation protection at all — not a defective appeal, but no appeal.
The consequence is immediate, not eventual. Section 112(9) stays recovery only where an appeal is on foot. If the token fails, there is no appeal, no stay, and no obstacle to Section 79 recovery — bank attachment included.
What to do this month. For every token generated: diarise the exact 60-day expiry date; reconcile the token particulars against the appeal as it will actually be filed, line by line; and preserve the contemporaneous evidence of portal failure — timestamped screenshots, network logs, the token acknowledgement itself. That evidence is worthless to gather in October and decisive to have gathered in July.
2. How limitation actually stands
The transitional architecture is more complicated than the single date most advisers are quoting, and one common description of it is simply wrong.
Notification S.O. 4220(E) dated 17 September 2025 was issued under Section 112(1) alone. It notified 30 June 2026 as the last date for appeals against orders communicated before 1 April 2026, with the ordinary three-month period applying to orders communicated on or after that date.
That notification no longer exists. By notification dated 30 June 2026 (F.No. A-50/7/2025-GSTAT-DoR, reported as S.O. 3502(E)), the Government acted in supersession of S.O. 4220(E) — not by amendment or extension — and under Section 112(1) read with Section 112(3). The new position:
Appeals (s.112(1)): orders communicated before 1 May 2026 → 31 July 2026. Orders communicated on or after 1 May 2026 → three months from communication.
Applications (s.112(3)): orders passed before 1 February 2026 → 31 July 2026. Orders passed on or after 1 February 2026 → six months from the date the order was passed.
The second limb matters more than it appears. Until 30 June 2026, the departmental timeline under Section 112(3) had never been notified. Anyone assessing cross-appeal exposure from pre-July material is working from an instrument that has been superseded and a departmental position that did not previously exist.
A caution on the 31 December 2026 date. The Principal Bench order of 14 May 2026 extended the relaxed scrutiny and defect-management guidelines of 20 January 2026 and 10 March 2026 through 31 December 2026. It is being read in some quarters as a limitation extension. It is not. It governs registry scrutiny of appeals already filed. It does not touch Section 112, and it does not supersede a notification issued under it.
3. The condonation cap — and the question nobody is asking
Section 112(6) permits the Tribunal to admit an appeal within three months after the expiry of the period referred to in sub-section (1), and an application within three months after the expiry of the period referred to in sub-section (3), on satisfaction of sufficient cause. The cap applies to both limbs, expressly and separately.
That the cap is absolute is well settled by read-across. The CGST Act is a special fiscal statute with a self-contained appellate code. By prescribing a specific, bounded condonable period, the legislature has expressly excluded Section 5 of the Limitation Act, 1963, within the meaning of Section 29(2) of that Act. The Supreme Court line is unbroken: Singh Enterprises v. CCE, Jamshedpur (2008); CC & CE v. Hongo India (P) Ltd. (2009); Asst. Commr. (CT), LTU, Kakinada v. Glaxo Smith Kline Consumer Health Care Ltd. (2020). A tribunal that is a creature of statute cannot condone beyond the ceiling the statute fixes, however genuine the cause.
But here is the question the commentary has not confronted.
Section 112(1) fixes the period as three months from communication or such date as may be notified by the Government, whichever is later. Section 112(6) runs its three months from "the expiry of the period referred to in sub-section (1)."
For backlog appeals, the period referred to in sub-section (1) is the notified date. That date is now 31 July 2026. On the plain reading, the condonable window therefore expires on 31 October 2026 — not 30 September 2026.
The 30 September figure in circulation was correctly reasoned in May 2026, off the then-notified date of 30 June. It has been carried forward without adjustment for the supersession. If the reading above is right, a substantial cohort of advisers is telling clients their window shuts a month before it does.
The argument is untested, and the counter is real. The department may say a notified date is a substitute deadline rather than "the period referred to in sub-section (1)", leaving Section 112(6) with nothing to attach to for backlog cases. There is no authority either way — GSTAT is under a year old and no reported decision addresses Section 112(6) at all. Anyone relying on 31 October should file on the footing that 30 September governs and preserve the longer argument in the alternative. It is not a date to plan around. It is a date to plead.
A second open question, on the token order itself. Order No. 156/2026 is an administrative order under Rule 123 — a procedural rule — with the practical effect of extending a statutory limitation period by up to 60 days. When the same Bench issued its staggered-filing order on 24 September 2025, also under Rule 123, it recorded that the timelines were not in conflict with Section 112(6). Order 156/2026 goes considerably further than that disclaimer contemplates. Whether Rule 123 can bear the weight has not been tested, and a taxpayer whose entire limitation protection rests on a token has an unhedged exposure to the answer.
4. "Communication" — the one argument that resets the clock
Where limitation has run, the most productive line is usually not condonation. It is that limitation never started.
Section 112(1) runs from communication, not from the date an order was passed, signed or dispatched. The Revenue's routine position is that uploading to the common portal is valid electronic service under Section 169 and instantly starts the clock. The courts have been less willing.
The Allahabad High Court in M/s Bambino Agro Industries Ltd. v. State of U.P. held that while portal service is permissible under Section 169, mere uploading does not conclusively establish actual communication — the portal lacks a reliable automated acknowledgement showing when an order was downloaded or viewed. Where the assessee asserts a later date of actual knowledge, the evidentiary burden shifts to the Revenue to produce cogent proof of earlier communication.
The same instinct appears elsewhere. Where a statute permits several modes of service, ineffective service by one cannot be used to defeat the right of appeal. The Madras High Court in Tvl. Deepa Traders condoned a delay of 285 days where an order was uploaded but never physically served or adequately notified. The Bombay High Court has intervened where ex parte orders were posted under obscure portal tabs without accompanying alerts.
Where this succeeds, the court is not condoning delay. It is holding that time never began to run — which is a materially stronger position than asking for indulgence, and one that survives Glaxo Smith Kline.
5. When the writ is the only door
For practitioners in Maharashtra, the Bombay High Court has already marked the boundary with some precision.
In Map Overseas v. Union of India & Ors. (Writ Petition No. 8229 of 2025), the petitioner had filed a Section 107 appeal beyond the 120-day outer limit and, on rejection, invoked Article 226 — arguing merits and asserting non-communication. The Division Bench refused relief and made three points that now govern any time-barred GST writ in this jurisdiction:
Article 226 cannot be exercised to displace the legislative intent behind a maximum condonable period. The High Court is not a substitute appellate forum.
The strength of the case on merits is irrelevant where the appeal is outside the outer limit.
The burden of proving non-communication rests on the assessee. Bare assertion will not do.
That third holding is the operative one. The communication argument in §4 is available, and it is not cheap to run. It requires an evidentiary matrix built before the writ is filed — portal audit trails, absence of email or SMS alerts, the date and circumstances of actual discovery, and a filing made immediately upon discovery rather than after recovery began to bite.
The surviving exceptions to the alternate-remedy bar remain narrow: total absence of jurisdiction rendering the order void ab initio; a fundamental breach of natural justice, such as an order against a deceased assessee or a hearing denied despite request; and demonstrable failure of statutory communication.
One category is not yet on that list, and will be by October. A taxpayer who relied on Order No. 156/2026, generated a token, and lost the statutory remedy because the token was voided or lapsed through administrative or clerical failure stands differently from the petitioner who simply slept on rights. That appellant complied with a mechanism the Tribunal itself created to preserve limitation. The argument engages legitimate expectation, and the "no jurisdictional error, no breach of natural justice" answer does not obviously meet it. No such case has been decided. The first will be filed within weeks.
6. Two procedural traps worth naming
Pre-deposit quantum. Section 112(8) requires 100% of the admitted liability plus 10% of the remaining tax in dispute, capped at ₹20 crore per enactment — reduced from 20% and ₹50 crore by the Finance (No.2) Act, 2024. Cumulative exposure across both tiers is 20%, not 10%. The base is tax in dispute only: disputed interest and disputed penalty do not attract the 10%, save under the penalty-only proviso inserted by the Finance Act, 2025 with effect from 1 October 2025. That proviso is not retrospective — the Hyderabad Bench so held on 28 July 2026 where the entire lis predated it. Over-deposit is common and it is recoverable working capital.
The ledger question, and a warning about generic advice. Whether the Section 112(8) pre-deposit may be discharged from the Electronic Credit Ledger is genuinely contested — the Orissa High Court in Jyoti Construction said no; the Bombay High Court in Oasis Realty said yes. Commentary circulating nationally advises taxpayers to avoid the ECL entirely. For a Maharashtra assessee that advice is at best over-cautious and at worst wrong, since Oasis Realty is the binding authority in this jurisdiction. The real risk is not legal but operational: portal backend validation may reject ECL mapping, and a rejection flagged as non-payment lifts the Section 112(9) stay. The answer is to check the position for the jurisdiction and the portal behaviour for the matter — not to apply a national rule of thumb to a question the High Courts have divided on.
Where this leaves corporate tax functions in August
The tribunal-less era rewarded patience. The current regime punishes it.
Audit every token generated between 10 and 31 July. Expiry date, particulars reconciliation, evidence file. This is the only work with a hard deadline inside the next six weeks.
For backlog appeals not filed: file the condonation application now, on the footing that the window closes 30 September, pleading the 31 October construction in the alternative. Do not wait to see which is right.
For orders where communication is doubtful: build the evidentiary record before filing anything. Map Overseas decides these cases on evidence, not on argument.
Recompute pre-deposits where interest or penalty was included in the 10% base.
Re-examine departmental exposure under the newly notified Section 112(3) timeline. It did not exist before 30 June 2026.
The merits of a GST dispute have never mattered less at the threshold than they do now. What decides the second appellate tier in the next quarter is arithmetic, evidence and diarised dates.
This article identifies questions on which no authority currently exists, including the outer limit of the Section 112(6) condonable window for backlog appeals and the vires of the token mechanism under Rule 123. Those are set out as arguments, not as settled positions. Nothing here is advice on any particular matter, and the position should be verified against the instruments and the record in each case.