Friday, May 29, 2026

Consolidated SCN for Multiple Financial Years is Valid Under Sections 73 & 74 of GST Act

Consolidated SCN for Multiple FYs Under GST — Valid, Says Karnataka HC | Chimney Hills Education Society | 2026
Karnataka High Court · Division Bench  ·  23 April 2026  ·  GST Demand Proceedings  ·  Sections 73 & 74 CGST Act
⚖️ Landmark GST Judgment — April 2026

Consolidated SCN for Multiple
Financial Years is Valid
Under Sections 73 & 74 of GST Act

The Karnataka High Court (Division Bench) overturns the Single Judge and holds that a common show cause notice spanning several financial years is not only permissible but aligned with the plain statutory language of the GST demand provisions.

Case
Commissioner of Central Tax v. Chimney Hills Education Society
Date
23 April 2026
Bench
Justice K.V. Aravind & Justice S.G. Pandit
Writ Appeal
No. 1751/2024 (T-RES) & Connected Matters
The Core Holding
"Show cause notices issued under Sections 73/74 of the CGST Act do not prohibit coverage of multiple financial years. Such notices are neither tax period-specific nor financial year-specific. There is no statutory bar to the issuance of a common show cause notice covering multiple tax periods or financial years."
§ 01 — Background

The Legal Question That Divided India's High Courts

Since GST's rollout on 1 July 2017, the tax department has routinely faced situations where fraud, wilful misstatement, or suppression of facts spanning multiple consecutive financial years is discovered in a single investigation or audit. The natural operational response — issuing one consolidated Show Cause Notice (SCN) covering the entire non-compliant period — has been fiercely challenged by assessees across the country, creating a question that has now escalated all the way to the Supreme Court.

The legal question is deceptively simple but commercially enormous: Can a single SCN under Sections 73 or 74 of the CGST Act lawfully cover multiple financial years — or must the department issue a separate notice for each financial year? The answer determines whether the Revenue can pursue years of alleged evasion in one integrated proceeding, or must fragment its enforcement into separate annual actions.

§ 02 — Facts of the Case

What Happened — The Journey Through the Courts

The Revenue — comprising officers of the Central Tax, Central Excise, and Commercial Taxes departments — issued a single consolidated show cause notice under Section 74 of the CGST Act for the period from July 2017 to March 2023, alleging defaults attributable to fraud, wilful misstatement, or suppression of facts. The notice was issued to multiple assessees in a batch of connected matters, of which Chimney Hills Education Society was the lead respondent.

At the Single Judge Stage

The assessees immediately filed writ petitions before a Single Judge of the Karnataka High Court challenging the consolidated SCN. Their primary argument: the GST Act's scheme — built around monthly returns and annual assessments — mandated that demand proceedings under Sections 73/74 be conducted and notified separately for each financial year. A combined multi-year notice, they argued, was not authorised by statute and caused serious prejudice.

The learned Single Judge agreed with the assessees and quashed the consolidated SCNs. The Single Judge also set aside two Original Orders-in-Original (OIOs) that had been passed on the basis of those SCNs, while granting the department liberty to issue fresh year-wise notices. This effectively forced the Revenue to restart the entire proceedings from scratch on a FY-wise basis.

Revenue's Intra-Court Appeal to the Division Bench

The Revenue appealed the Single Judge's order before a Division Bench of the Karnataka High Court. The Division Bench — comprising Justice K.V. Aravind and Justice S.G. Pandit — heard the matter in a batch of connected cases and delivered a comprehensive judgment on 23 April 2026, allowing the Revenue's appeals in full.

§ 03 — Competing Arguments

Assessees vs. Revenue — The Full Argument Map

⚖️
Assessee Argument 1 — FY-Specific Scheme

The entire architecture of the GST Act is built around the financial year — GSTR-1, GSTR-3B, and annual returns are all FY-anchored. Section 73(10) and Section 74(10), which prescribe the limitation period for passing orders, use financial year as the benchmark. This FY-specific structure necessarily implies that demand proceedings must also be FY-specific. A multi-year SCN violates this scheme.

🏛️
Revenue Counter — "Any Period" is Broader Than One FY

Section 73(1) and Section 74(1) both use the expression "any period" in authorizing the issuance of SCNs. This expression is wider and more flexible than "financial year" or "tax period." The legislature deliberately chose "any period" to give the adjudicating authority flexibility, especially in fraud cases where a single scheme of misstatement may span multiple years. No statutory provision expressly bars consolidation.

⚖️
Assessee Argument 2 — Prejudice from Clubbing Fraud & Non-Fraud Periods

Consolidating periods involving alleged fraud (Section 74, extended limitation of 5 years) with periods where no fraud is alleged (Section 73, normal limitation of 3 years) in a single SCN creates prejudice. It artificially extends the limitation framework for non-fraud periods and blurs the evidentiary burden on the department. The assessee cannot properly defend against diffuse multi-year allegations in one notice.

🏛️
Revenue Counter — Consolidation Does Not Erase Limitation

Issuing a consolidated SCN does not override or extend the limitation period applicable to each period within it. The limitation for each year within the notice must independently satisfy the applicable standard — Section 73 for non-fraud periods, Section 74 for fraud periods. Time-barred portions must simply be excluded from the final adjudication order. The assessee suffers no additional prejudice; the limitation safeguard continues to operate period-wise.

⚖️
Assessee Argument 3 — DRC-01 Form & Pecuniary Jurisdiction

The DRC-01 prescribed form for SCNs contains a "tax period" field, signaling legislative intent that each SCN should pertain to a specific, discrete tax period. Further, combining multiple financial years in one SCN may result in the aggregate demand exceeding the pecuniary jurisdiction of the issuing officer, creating a jurisdictional infirmity.

🏛️
Revenue Counter — DRC-01 Field is Non-Mandatory; Jurisdiction Circular Covers It

The "tax period" field in DRC-01 is a non-mandatory data field. Its existence does not create a statutory compulsion to restrict each SCN to one period. On pecuniary jurisdiction, the CBIC has issued circulars that specifically address the allocation of jurisdiction in consolidated demand proceedings. The assessee has no right to choose the adjudicating officer; jurisdictional allocation is the department's prerogative governed by those circulars.

§ 04 — Statutory Analysis

Reading the Law — "Any Period" vs "Tax Period" vs "Financial Year"

The Division Bench undertook a careful, contextual textual analysis of the demand provisions. The central statutory distinction the Court drew was between three phrases that the GST Act uses in different contexts with distinct meanings:

// Three Distinct Temporal Expressions in the CGST Act "Tax Period" → Defined under Section 2(106) CGST Act = Period for which GST return is required to be furnished = Monthly (for regular taxpayers) or quarterly (QRMP) = Directly linked to GSTR-1, GSTR-3B filing obligations // Used primarily in: return provisions, ITC matching, GSTR framework "Financial Year" → April 1 to March 31 of any year = Referenced in S.73(10), S.74(10) for ORDER limitation = Sets the deadline by which adjudication ORDER must be passed // Used primarily in: limitation for passing orders, annual return "Any Period" → Used in Section 73(1) and Section 74(1) for SCN issuance = Broader than both "tax period" and "financial year" = No numerical or temporal constraint imposed by the legislature // This is what governs the SCOPE OF THE NOTICE → NOT FY-specific Court's Finding: The legislature used DIFFERENT terms deliberately. "Any period" in SCN provisions is WIDER than "financial year" in limitation provisions. Using FY-specific limitation for orders does NOT import FY-specificity for notice issuance.

The phrase 'any period' in demand provisions governs SCN scope, distinct from 'tax period' tied to returns. Reference to the financial year in the limitation sub-section only sets the timeline for orders and does not confine the notice to a financial year.

Karnataka High Court Division Bench — Chimney Hills Education Society, 23 April 2026

The Limitation Provisions Are About Orders, Not Notices

A critical textual insight the Court offered is that Sections 73(10) and 74(10) — which reference "financial year" — govern the deadline by which the adjudication order must be passed, not the scope of the initial SCN. The provisions read:

// Section 73(10) CGST Act — Limitation for Orders (Non-Fraud) S.73(10): "The proper officer shall issue the order under sub-section (9) within THREE YEARS from the due date for furnishing of annual return for the financial year to which the tax not paid or short paid... pertains." // Section 74(10) CGST Act — Limitation for Orders (Fraud) S.74(10): "The proper officer shall issue the order under sub-section (9) within FIVE YEARS from the due date for furnishing of annual return for the financial year to which the tax not paid or short paid... pertains." Key Observation: Both provisions speak to when the ORDER must be issued. Neither provision speaks to whether the NOTICE must be restricted to one financial year. "Financial year" sets the CLOCK for completion. "Any period" sets the SCOPE of the notice. These are logically SEPARATE and independent constraints.
§ 05 — The Ratio Decidendi

The Court's Detailed Findings & Ratio

Division Bench — Key Findings (Ratio Decidendi)
  • The expression "any period" in Sections 73(1) and 74(1) governs the scope of SCN issuance and is deliberately broader than "tax period" or "financial year." It cannot be read down to mean a single FY.
  • Reference to "financial year" in Sections 73(10)/74(10) sets the timeline for passing the adjudication order — not the period covered by the notice. The two sub-sections operate at different stages of the proceeding and serve distinct purposes.
  • The DRC-01 "tax period" data field is non-mandatory. Its presence in the form does not impose a statutory obligation to restrict each SCN to one tax period or FY.
  • Combining multiple FYs in a single SCN causes no prejudice to the assessee: (a) pecuniary jurisdiction concerns are addressed by the CBIC jurisdictional circular; (b) the assessee has no vested right to choose the adjudicating officer; (c) the consolidated notice clearly sets out the entire factual basis, allowing a meaningful reply.
  • A consolidated SCN does not efface or extend the limitation period. Each period within the notice must independently satisfy the limitation applicable to its category — Section 73 (3 years) for non-fraud, Section 74 (5 years) for fraud. Time-barred portions must be excluded from the final order; proceedings may continue for the balance period.
  • The fraud jurisdiction under Section 74 can be invoked only on the basis of specific material evidence incorporated in the SCN. If such evidence is absent for a particular period, that period falls under the Section 73 non-fraud regime and attracts the shorter 3-year limitation — automatically and without amendment to the notice.
  • The new provision operative from FY 2024-25 onwards (Section 74A, inserted by Finance (No. 2) Act, 2024, merging the fraud and non-fraud regimes) does not alter the interpretation of "any period" in the pre-existing provisions nor convert the pre-2024-25 exercise into a FY-specific one.
  • Appeals allowed. Consolidated SCNs and the two Original Orders-in-Original restored in their entirety. The Single Judge's order quashing the consolidated SCNs is set aside.
§ 06 — Limitation Nuances

How Limitation Works in a Consolidated SCN

The Court's handling of the limitation issue is arguably the most practically important aspect of the judgment. The Revenue's most vulnerable point in defending consolidated SCNs is precisely this: does combining periods allow the department to apply the longer fraud limitation (5 years under Section 74) to periods where it cannot actually prove fraud, thereby effectively extending the limitation for those periods? The Division Bench addressed this with surgical precision.

Section 73 — Non-Fraud Regime
3 Years

Applicable where tax has not been paid or short-paid due to genuine mistake, inadvertence, or negligence — without any element of fraud or wilful misstatement. Time runs from the due date of filing the annual return for the relevant financial year.

Section 74 — Fraud Regime
5 Years

Applicable where tax has not been paid due to fraud, wilful misstatement, or suppression of facts. The extended limitation is conditioned on the department producing specific material evidence of such conduct incorporated into the SCN itself.

⚖️
The Critical Protection — Fraud Cannot Be Automatically Extended

The Court made clear that the extended 5-year limitation under Section 74 is not automatic. It can only be invoked upon determination that fraud, wilful misstatement, or suppression actually existed for that specific period, based on material evidence explicitly incorporated into the SCN. If a consolidated SCN covers both periods where fraud evidence exists and periods where it does not, the limitation for each period is assessed independently — periods lacking fraud evidence are evaluated under Section 73's 3-year rule. Time-barred portions for any period must be excluded from the final order even if the rest of the notice proceeds.

// How Limitation Applies in a Consolidated SCN — Practical Framework Consolidated SCN issued for: July 2017 → March 2023 (spanning ~6 FYs) FY 2017-18: Fraud evidence in SCN → Section 74 applies → 5-year window → Valid if within time FY 2018-19: Fraud evidence in SCN → Section 74 applies → 5-year window → Valid if within time FY 2019-20: Fraud evidence in SCN → Section 74 applies → 5-year window → Valid if within time FY 2020-21: No fraud evidence → Section 73 applies → 3-year window → Check if time-barred FY 2021-22: Fraud evidence in SCN → Section 74 applies → Valid FY 2022-23: Fraud evidence in SCN → Section 74 applies → Valid // Result: FY 2020-21 portion, if time-barred under S.73, must be EXCLUDED from the Order. // SCN itself remains valid. Only the time-barred portion is excluded at the Order stage. // The consolidated notice is NOT quashed in its entirety merely because one period is barred.
§ 07 — National Judicial Landscape

India's High Courts Divided on This Question

The Chimney Hills judgment does not exist in isolation. It is the latest — and arguably the most comprehensive — addition to a national judicial split on the consolidated SCN question that has been building since 2023. The Karnataka High Court expressly surveyed and chose sides in this inter-High Court debate.

Consolidated SCN Permissible — Courts Aligned with Karnataka HC
  • Delhi HC — Mathur Polymers v. Union of India [(2026) 154 GSTR 443]: Consolidated SCN permissible; "any period" broader than FY.
  • Delhi HC — Ambika Traders v. Commissioner [(2025) 33 Centax 189]: Common notice covering multiple periods upheld.
  • Allahabad HC — SA Aromatics Pvt. Ltd. v. Union of India [2026 SCC OnLine All 191]: Aligned with Delhi HC approach; consolidation valid.
  • J&K HC — New Gee Enn & Sons v. Union of India [2025 SCC OnLine J&K 1180]: Common SCN for multiple periods held permissible.
  • Kerala HC (Earlier) — Held that Section 74(3) uses "period" broadly; bunching not illegal. (Note: Kerala is referenced as "declined" in the headnote — position may have evolved.)
Consolidated SCN Impermissible — Contrary Views (Not Followed)
  • Bombay HC — Milroc Good Earth Developers v. Union of India (2025): Single SCN cannot cover multiple FYs.
  • Bombay HC — Paras Stone Industries v. Union of India (2026): Proceedings must be FY-specific.
  • Bombay HC (DB) — Rollmet LLP v. Union of India: Division Bench flagged the conflict and referred to Larger Bench — matter sub judice.
  • Madras HC — Titan Company Ltd. v. Joint Commissioner: Section 73/74 proceedings must track FY structure.
  • Andhra Pradesh HC — Sahiti Agencies & Others: Single SCN spanning multiple FYs impermissible; year-wise notices required.
  • Himachal Pradesh HC — Contrary view adopted; FY-wise notice requirement affirmed.
🔭
Supreme Court Will Settle This Definitively

Given the irreconcilable split between High Courts of Karnataka, Delhi, Allahabad, and J&K on one side, and Bombay, Madras, Andhra Pradesh, and Himachal Pradesh on the other, the matter is now heading to the Supreme Court for a final authoritative resolution. The Bombay High Court's Larger Bench reference in Rollmet LLP further accelerates this inevitability. This is one of the most consequential open procedural questions in GST enforcement law.

§ 08 — 2025-26 Amendment

Section 74A — The New Unified Demand Provision from FY 2024-25

The Finance (No. 2) Act, 2024 inserted a new Section 74A into the CGST Act, operative from FY 2024-25 onwards. Section 74A merges the previously separate Section 73 (non-fraud) and Section 74 (fraud) frameworks into a single, unified demand provision with a common limitation period of two years from the due date of the annual return — irrespective of whether fraud is involved or not.

Provision Applicable Period Fraud/Non-Fraud Distinction Limitation for Orders
Section 73 (Non-Fraud) FY 2017-18 to FY 2023-24 Non-fraud, genuine error 3 years from due date of annual return
Section 74 (Fraud) FY 2017-18 to FY 2023-24 Fraud, wilful misstatement, suppression 5 years from due date of annual return
Section 74A (Unified) FY 2024-25 onwards Single regime — fraud distinction preserved for penalties only 2 years from due date of annual return
📌
Section 74A Does Not Change the "Any Period" Question

The Division Bench expressly held that the introduction of Section 74A for FY 2024-25 onwards does not alter the interpretation of "any period" in the pre-existing Section 73/74 provisions. The new provision's unified structure does not retrospectively convert earlier proceedings into FY-specific exercises. For all periods up to FY 2023-24, Sections 73 and 74 (as interpreted in Chimney Hills) continue to govern.

§ 09 — Practical Impact

What This Judgment Means for Businesses, CAs & Litigants

🏛️
For Revenue & Department

The ruling significantly strengthens enforcement capabilities. Investigations uncovering multi-year fraud schemes can now be prosecuted through a single, comprehensive proceeding — reducing administrative duplication and closing the tactical window assessees used to buy time through procedural challenges.

🏢
For Businesses (Assessees)

Taxpayers facing consolidated SCNs can no longer challenge validity on grounds of multi-year coverage in Karnataka, Delhi, Allahabad, and J&K jurisdictions. Defence must now focus on the substance — fraud evidence, correct limitation analysis for each period, and the exclusion of time-barred portions.

📋
For Tax Practitioners & CAs

Advising clients on consolidated SCN challenges requires jurisdiction-specific analysis. In Bombay, Madras, and AP, year-wise notice arguments still hold. Nationally, the Supreme Court ruling will be the definitive reference. Period-wise limitation analysis inside a consolidated SCN is now a core skill requirement.

Key Takeaways for Assessees Facing Consolidated SCNs

  • Validity challenge alone will fail in Karnataka, Delhi, Allahabad, and J&K — focus your reply on the merits, fraud evidence, and limitation analysis for each period.
  • Demand a period-wise limitation analysis in your reply — the department cannot apply Section 74's extended 5-year period to any period for which it has not specifically incorporated fraud evidence in the SCN.
  • Identify and explicitly flag time-barred portions in your reply — the Court has held that time-barred periods must be excluded from the adjudication order even within a valid consolidated SCN.
  • Assess jurisdiction — which High Court governs? In Bombay, Madras, and AP courts, consolidated SCN challenges may still succeed under the prevailing High Court view in those jurisdictions (pending SC clarification).
  • Monitor the Supreme Court proceedings — the definitive national ruling is imminent given the Bombay HC's Larger Bench reference and the active inter-HC conflict.
  • Check the DRC-01 for specificity — even within a valid consolidated SCN, each allegation must be sufficiently specific to enable a meaningful reply. A SCN that lumps all periods in generic terms without period-specific allegations may be challenged on natural justice grounds even if multi-year coverage itself is valid.
  • Section 74A applies from FY 2024-25 — for any SCN covering periods from FY 2024-25 onwards, the unified Section 74A regime (2-year limitation, regardless of fraud) governs. This dramatically shortens the department's window and changes the enforcement calculus significantly.
The Natural Justice Safeguard Remains Intact

Even where a consolidated SCN is procedurally valid under Chimney Hills, the principles of natural justice continue to apply in full. The SCN must give the assessee adequate and specific notice of the allegations for each period, sufficient to enable a meaningful and informed reply. A consolidated SCN that sets out only sweeping, non-specific allegations across all periods without period-wise particulars may still be challenged on the ground of inadequate opportunity to be heard — a challenge that operates entirely independently of the multi-year coverage question.


Conclusion — A Significant Enforcement Clarification, Pending Supreme Court Finality

The Karnataka High Court's Division Bench ruling in Commissioner of Central Tax v. Chimney Hills Education Society is one of the most substantive GST procedural judgments of 2026. By holding that a consolidated SCN covering multiple financial years is valid under the plain language of Sections 73 and 74 of the CGST Act, and by aligning with the Delhi, Allahabad, and J&K High Courts against the Bombay, Madras, and AP positions, the Division Bench has given the Revenue a powerful procedural tool for comprehensive enforcement in fraud and misstatement cases.

The judgment's most nuanced contribution, however, is its treatment of limitation: a consolidated SCN does not erase limitation safeguards — it merely consolidates the notice stage, leaving each period's limitation to be independently verified at the order stage. This balanced approach protects both the Revenue's enforcement interests and the assessee's substantive limitation rights.

The key legal propositions established by the Division Bench:

"Any period" in Sections 73(1)/74(1) governs SCN scope — broader than both "tax period" and "financial year."
Reference to "financial year" in Sections 73(10)/74(10) sets the deadline for orders — not the scope of notices.
DRC-01's "tax period" field is non-mandatory — its presence does not compel FY-wise notice issuance.
Consolidated SCN causes no prejudice — limitation operates period-wise within the consolidated notice.
Fraud jurisdiction under Section 74 requires specific material evidence for each period — not assumed from consolidation.
Time-barred portions must be excluded from the order; the balance proceeds — SCN not quashed entirely.
Section 74A (from FY 2024-25) does not alter the interpretation of "any period" in Sections 73/74 for earlier periods.
Views of Delhi, Allahabad, and J&K HCs approved; views of Bombay, Madras, AP, and HP HCs not followed.

With the Bombay High Court's Larger Bench reference and an active Supreme Court challenge, the final word on this question is yet to come. Until then, Chimney Hills stands as the most comprehensive judicial analysis of the consolidated SCN question under GST — and a ruling that every tax practitioner, in-house legal team, and GST officer in India must have in their working library.

Commissioner of Central Tax v. Chimney Hills Education Society
Karnataka HC · Writ Appeal No. 1751/2024 (T-RES) · 23 April 2026
Justice K.V. Aravind & Justice S.G. Pandit · Sections 73 & 74 CGST Act, 2017 / KGST Act, 2017
This blog is for informational and educational purposes only.

Thursday, May 28, 2026

The Bonafide Recipient Doctrine Substantive Business Rights vs. Procedural Bottlenecks

The Bonafide Recipient Doctrine — ITC Protection Under GST | Section 16(2)(c) | Filco Trade Philosophy | 2025-26
GST Jurisprudence · Section 16(2)(c) CGST Act · Bonafide Recipient Doctrine · Updated May 2026
⚖️ GST Tax Law | ITC Rights | Constitutional Challenge

The Bonafide Recipient Doctrine
Substantive Business Rights
vs. Procedural Bottlenecks

How courts are drawing the line between innocent buyers and defaulting suppliers — and why the legal battleground over Section 16(2)(c) is the most consequential GST dispute of this decade.

§16(2)(c)The Central Battleground
2026Active Judicial Split
FilcoFoundational Philosophy
SCNotice Issued 2026
The Core Tension

Few provisions of Indian tax law have generated as much litigation, commercial anxiety, and constitutional challenge as Section 16(2)(c) of the CGST Act, 2017. In its bare operation, this provision makes a buyer's right to Input Tax Credit entirely contingent on whether their supplier — an independent third party over whom the buyer has zero control — actually deposits the collected GST with the Government. Since 2017, tax authorities across India have used this provision to raise massive demands against genuinely honest buyers simply because an upstream supplier defaulted. The result: a nationwide statutory Catch-22 that has paralysed working capital and triggered one of the most consequential jurisprudential splits in GST history.

§ 01 — The Statutory Foundation

What Does Section 16(2)(c) Actually Say?

Section 16(2) of the CGST Act sets out the conditions a registered taxpayer must satisfy before claiming Input Tax Credit (ITC) on an inward supply. The provision lists four cumulative conditions, each linked to a specific aspect of the transaction:

// Section 16(2) CGST Act, 2017 — Four Cumulative ITC Conditions Condition (a): Recipient possesses a valid tax invoice or debit note Condition (b): Recipient has received the goods or services (or both) Condition (aa): Invoice details appear in recipient's GSTR-2B [added Finance Act 2021] Condition (c): Tax actually paid to Government by the SUPPLIER ← This is the problem // The Catch-22: // Conditions (a), (b), (aa) are 100% within buyer's control and verifiable. // Condition (c) is entirely OUTSIDE buyer's control, knowledge, or ability to monitor. // A buyer CANNOT access the supplier's Electronic Cash Ledger, GSTR-3B, or payment details.

The practical consequence is stark. A buyer who has:

Within Buyer's Control — Fully Met
  • Verified the supplier holds an active, valid GSTIN
  • Received a tax-compliant invoice with all prescribed particulars
  • Actually received the goods or services contracted for
  • Verified the supply in their GSTR-2A and GSTR-2B
  • Paid the full consideration + GST through banking channels
  • Maintained stock records, transport documents, delivery challans
Beyond Buyer's Control — The Fatal Gap
  • Cannot access supplier's Electronic Cash Ledger
  • Cannot access supplier's GSTR-3B to verify actual payment
  • Cannot determine supplier's ITC utilization pattern
  • Cannot monitor supplier's internal tax deposit timelines
  • Has no legal or contractual mechanism to compel supplier compliance
  • Has no investigative or enforcement power over the supplier
⚠️
The Second Proviso — A Legal Trap Within a Trap

Section 16(2)'s second proviso mandates that the recipient must pay the supplier the full value of goods/services including the tax component within 180 days. Failure triggers mandatory ITC reversal with interest. The law thus first compels the buyer to transfer the tax to the supplier — and then allows that same supplier's default to strip the buyer of the very credit they funded. Courts have described this as a "legal trap" that compounds the injustice of Section 16(2)(c).

§ 02 — The Filco Trade Philosophy

The Judicial Doctrine That Protects Honest Buyers

The legal philosophy that has emerged to protect bonafide recipients draws from a deeper constitutional principle: that the state cannot weaponize third-party defaults to strip a compliant taxpayer of legitimately earned financial assets. This doctrine — crystallized through the Supreme Court's landmark intervention in Union of India v. M/s Filco Trade Centre Pvt. Ltd. — has organically evolved to govern standard ITC disputes, particularly Section 16(2)(c) cases involving supplier non-compliance.

The Core Constitutional Principle
If a taxpayer acts in verified good faith and fulfills every obligation directly within their administrative control, the State cannot weaponize technical barriers or third-party non-compliance to strip that business of its working capital. Substantive equity must prevail over mechanical procedure.
Judicial philosophy underlying Filco Trade Centre and its progeny — 2022 to 2026

The Three Pillars of the Bonafide Recipient Shield

📐 Judicial Framework — Why Bonafide Buyers Cannot Be Held Liable
Pillar 01
Absence of Police Power
A buyer holds no investigative machinery to audit a supplier's internal tax compliance. Their duty ends at verifying active registration, holding a valid invoice, and actually receiving the supply.
Pillar 02
Enforcement Burden on the State
The tax department possesses sweeping recovery powers: asset attachments, bank freezes, anti-evasion tools. Penalising an innocent buyer for the state's failure to collect from a registered vendor is systemic overreach.
Pillar 03
ITC as a Vested Right
Once conditions within the buyer's control are met, ITC becomes a vested right — akin to "property" protected under Article 300A. Deprivation through third-party default is an unconstitutional expropriation without due process.

It was not disputed that the recipient had no mechanism to verify whether the supplier discharged tax liability to the Government and that the supplier was not normally under the control of the purchaser.

Tripura High Court — Sahil Enterprises v. Union of India, January 2026
§ 03 — A Specific Abuse

The Illegality of Retrospective Cancellation

One of the most pernicious enforcement tools deployed against bonafide recipients is the practice of retrospective cancellation of supplier registration. The mechanism works like this: a supplier defaults on GST payments over a period; tax authorities later cancel the supplier's registration and back-date the cancellation to a point before the transactions occurred. This maneuver is then used to retroactively invalidate the ITC of every business that legitimately transacted with that supplier when the registration was fully active, publicly visible on the GSTN portal, and legally valid.

🚨
Why Retrospective Cancellation Cannot Invalidate Prior ITC

High Courts have consistently struck down this practice. The foundational reasoning is simple: at the time of the transaction, the GSTN portal publicly displayed the supplier as a registered, active taxpayer. The buyer's due diligence obligation was fulfilled. A subsequent administrative order cannot retroactively alter the legal character of a transaction that was valid when it occurred — that would amount to imposing liability based on facts that were not merely unknowable, but literally non-existent at the relevant time.

// Retrospective Cancellation — Why It Cannot Invalidate ITC Date of Transaction : Supplier Registration ACTIVE on GSTN Portal Buyer's Verification : Registration status — Active ✓ Tax Invoice Received : Valid in all respects ✓ Supply Received : Goods/services actually delivered ✓ GST Paid to Supplier : Through banking channels ✓ GSTR-2B Reflection : Invoice appears in buyer's GSTR-2B ✓ [Later] — Tax Authority cancels supplier registration RETROSPECTIVELY Effect on Buyer's ITC : LEGALLY IMPERMISSIBLE Judicial Position : Transactions valid when executed cannot be voided retroactively Correct Remedy : Department to recover from defaulting SUPPLIER, not innocent buyer
§ 04 — 2025-26 Judicial Landscape

A Nation Divided — The High Court Split

The most striking feature of the current GST landscape on Section 16(2)(c) is that multiple High Courts have examined the same provision and arrived at diametrically opposite conclusions. This judicial split — unprecedented in its scale and commercial significance — has created a situation where a bonafide recipient's ITC rights depend, perversely, on which state their business happens to operate in.

Courts Reading Down § 16(2)(c) — Pro-Taxpayer
  • Karnataka HC — Instakart Services v. Union of India (Feb 2026): Section 16(2)(c) and Rule 36(4) read down to protect bonafide recipients from supplier defaults.
  • Tripura HC — Sahil Enterprises v. Union of India (Jan 2026): Provision must be read down; denial of ITC to bonafide buyers leads to double taxation and arbitrariness.
  • Gauhati HC — National Plasto Moulding v. State of Assam (2024): Aligned with pro-recipient approach; impossible burden cannot be imposed on buyers.
  • Delhi HC — On Quest / Arise India (pre-GST DVAT, attained finality): Department's remedy lies against defaulting seller, not innocent purchaser absent collusion or fraud.
Courts Upholding § 16(2)(c) — Revenue Position
  • Gujarat HC — Maruti Enterprise v. Union of India (May 2026): Constitutional validity upheld; ITC is a conditional benefit, not a vested right; purchaser bears the burden of proving actual tax payment.
  • Kerala HC — Consistent position upholding Section 16(2)(c) without reading down.
  • Patna HC — Upheld Section 16(2)(c) without modification.
  • Madras HC — Upheld the provision; recipients must bear the risk of supplier non-compliance.
  • Andhra Pradesh HC — Section 16(2)(c) not read down; statutory framework is clear and valid.
§ 05 — Landmark Rulings

Key Cases Decided in 2025-26

Instakart Services Pvt. Ltd. v. Union of India
Karnataka High Court
WP No. 4917/2021 · 09 Feb 2026
Background

Instakart Services (a logistics arm of the Flipkart ecosystem) faced massive ITC denial because its suppliers — from whom it had received genuine services — had not remitted the collected GST. The authorities confirmed demand under Section 73 with interest and penalty. Instakart challenged both the demand and the constitutionality of the provision.

Justice S.R. Krishna Kumar Held

Section 16(2)(c) and Rule 36(4) are read down to allow ITC to bonafide recipients that have complied with all other conditions despite supplier non-payment. The Court surveyed the entire jurisprudential landscape — including pre-GST Karnataka VAT decisions in Rajesh Jain, Onyx Designs (2019), and Jain Steels (2019) — all of which had consistently protected bonafide recipients. ITC denial was set aside; show-cause notices quashed.

Pro-Taxpayer ✓
Sahil Enterprises v. Union of India
Tripura High Court
W.P.(C) No. 688/2022 · 06 Jan 2026
Background

Petitioner, a rubber products trader, purchased goods from a supplier during July 2017 – January 2019 and paid GST of ₹1,11,60,830. The supplier filed GSTR-1 reflecting the sales but filed nil GSTR-3B and did not deposit tax. The department blocked credit and confirmed demand under Section 73 against the innocent recipient.

Court Held

Section 16(2)(c) is constitutionally valid but must be read down in its application. It cannot be applied to deny ITC to bonafide purchasers. A buyer has no mechanism to verify whether the supplier deposited GST. Denial in such cases would lead to double taxation and arbitrariness. The Court expressly observed: the supplier was not under the control of the purchaser.

Pro-Taxpayer ✓
Maruti Enterprise v. Union of India
Gujarat High Court (Revenue-Favorable)
R/SCA No. 18080/2023 · 01 May 2026
Background

A large batch of writ petitions challenged the vires of Section 16(2)(c). Petitioners argued that bonafide recipients had no statutory, contractual, or factual means of verifying the supplier's GSTR-3B actual tax payment or ITC utilization, and that the provision violated Articles 14, 19(1)(g), 265, and 300A of the Constitution.

Gujarat HC Held (Contra)

Constitutional validity of Section 16(2)(c) upheld in full. The Court declined to read it down. ITC is not an absolute or vested right but a conditional statutory benefit. "Section 16(2)(c) is clear, self-explanatory and unambiguous." The GST framework links ITC to actual tax payment; this allocation of risk to the buyer is a policy choice within legislative competence. Section 155 places the burden of proving ITC eligibility on the taxpayer — invoices and payment to supplier alone are insufficient.

Revenue Position ✗
Civil Appeal Nos. 2042–2047/2015 & 9902/2017
Supreme Court of India
Decided · 09 Oct 2025
Context

This Supreme Court decision arose from DVAT-era disputes (Delhi VAT) but carries direct doctrinal authority for GST Section 16(2)(c) litigation. The Court examined ITC rights where selling dealers were registered at the time of transaction but subsequently defaulted.

Supreme Court Held

ITC upheld for bonafide purchasing dealers where the selling dealer was registered at the time of the transaction and the genuineness of invoices and transactions was not disputed. The Department's remedy lies against the defaulting seller — not against an innocent purchaser absent collusion or fraud. This decision expressly adopted the Delhi HC approach in On Quest / Arise India, lending stronger precedential authority to pro-taxpayer arguments under GST.

Pro-Taxpayer ✓ — Supreme Court
Supreme Court Issues Notice on Constitutionality of Section 16(2)(c)
Supreme Court of India — Direct Constitutional Challenge
SLP · May 2026 · Ongoing
Background

Following the Rajasthan High Court's dismissal of a writ petition challenging Section 16(2)(c) as ultra vires (invoking alternative remedy doctrine), the matter was escalated to the Supreme Court. The petitioner sought a declaration that Section 16(2)(c) is constitutionally void, along with quashing of show-cause notice and adverse order.

Status: Supreme Court Notice Issued

The Supreme Court has issued notice to the Government, signaling that it considers the constitutional challenge to Section 16(2)(c) to be a question of sufficient importance to be examined at the highest judicial level. With the Gujarat vs. Karnataka split, a final authoritative ruling from the Supreme Court has become inevitable and is now likely to define the future of ITC law in India.

Pending — Apex Court
§ 06 — Constitutional Battleground

The Four Constitutional Arguments Against Section 16(2)(c)

The constitutional challenge to Section 16(2)(c) is built on four distinct, reinforcing legal pillars. Each attacks the provision from a different angle of fundamental rights and taxation law principles.

Constitutional Ground The Argument Judicial Treatment
Article 300A
Right to Property
ITC earned through prior tax compliance is a "property" right. Depriving a taxpayer of this vested right due to a third party's unilateral default amounts to unconstitutional expropriation without due process of law. Accepted — Karnataka, Tripura HCs
Article 14
Equality Before Law
Singling out bonafide buyers for a supplier's failure while giving the department multiple recovery tools against the actual defaulter is arbitrary, unreasonable, and discriminatory — violating the guarantee of equality. Partially Accepted — Tripura HC
Article 265
No Tax Without Authority
Requiring the buyer to effectively pay tax twice — once to the supplier (who doesn't remit) and again via ITC reversal to the government — amounts to double taxation, which is constitutionally impermissible absent explicit legislative mandate. Raised — Awaiting SC ruling
Proportionality Test
Doctrine of Proportionality
Even if the state has a legitimate anti-evasion objective, the means are disproportionate: punishing all buyers — bonafide and fraudulent alike — for the default of a third party is a blunt instrument that overreaches the legitimate policy goal. Accepted in principle — Karnataka HC
⚖️
The Gujarat Counter-Argument — Why the State Disagrees

The Gujarat HC and the Revenue's position articulate a coherent counter: ITC is not a right but a conditional legislative benefit. The GST framework is designed as a chain — each link must contribute before the next benefits. Allowing buyers to claim credit without actual tax payment disrupts this chain and incentivizes collusion. Section 155 places the burden of proof on the claimant. The impossibility argument does not justify judicial rewriting of unambiguous statutory text.

§ 07 — Practical Framework

What Does "Bonafide" Mean in Practice?

The courts have not protected all buyers indiscriminately. The protection flows specifically to bonafide recipients — those who acted in genuine good faith without collusion or prior knowledge of the supplier's evasion. Courts have been clear: the Department remains entirely free to deny ITC where transactions are not genuine, where fraud or collusion exists, or where the buyer had constructive notice of the supplier's non-compliance.

Establishing bonafide status requires a robust documentary chain. Here is what courts and practice indicate a protected buyer must demonstrate:

📋 Bonafide Recipient Documentation Checklist
1
Verified Supplier GSTIN at Transaction Date — Screenshot or record of the GSTN portal showing the supplier's registration as active and valid on the date of the transaction. This is your first line of defence against retrospective cancellation claims.
2
Valid Tax Invoice in Prescribed Form — Invoice containing all mandatory particulars under Section 31 of the CGST Act — supplier GSTIN, recipient GSTIN, HSN/SAC, taxable value, GST rate, GST amount, and place of supply.
3
Proof of Actual Receipt of Goods/Services — Delivery challans, LR copies, gate entry registers, weighment slips, e-Way Bills, service completion reports — any documentation establishing that the underlying supply physically occurred.
4
Payment Through Banking Channels — Bank transfer records, RTGS/NEFT confirmations, cheque payment acknowledgments — proving that consideration plus the full GST amount was actually transferred to the supplier, not paid in cash or via barter.
5
Reflection in GSTR-2B — Confirmation that the supplier filed GSTR-1 and the invoice appears in the buyer's GSTR-2B for the relevant period — establishing that at least the supplier reported the sale in their outward supply return.
6
Commercial Records Establishing Genuine Business Purpose — Purchase orders, contracts, board approvals, inventory records, production data — documents demonstrating that the procurement had a genuine commercial rationale, not a circular arrangement engineered to generate fictitious ITC.
7
Absence of Prior Adverse GSTN Intelligence — Records showing you checked the supplier's e-Invoice compliance, GSTR-2A historical filing pattern, and did not ignore publicly available red flags about the supplier's compliance history.
💡
The Judicial Bright Line

Courts have drawn a sharp line: where the buyer has no connection to the supplier's default and transactions are genuinely commercial, ITC cannot be denied. Where there is evidence of collusion, pre-arranged circular trading, fictitious invoices, or the buyer had actual or constructive knowledge of the supplier's evasion, the bonafide shield evaporates. The Department's power to investigate the genuineness of the underlying transaction is preserved in full.

§ 08 — What's Next

The Road Ahead — Supreme Court, GSTAT & the Final Answer

The constitutional challenge to Section 16(2)(c) is now squarely before the Supreme Court. With a direct and irreconcilable split between the Gujarat High Court (upholding the provision in full) and the Karnataka and Tripura High Courts (reading it down for bonafide recipients), a definitive ruling from the Apex Court has become legally inevitable.

As GSTAT becomes operational, with state benches being established and a 4.8 lakh appeal backlog to clear by June 2026, Section 16(2)(c) will be among the first and most significant interpretative questions the Tribunal faces.

TaxGuru Analysis — May 2026

Three Possible Outcomes at the Supreme Court

ScenarioWhat It Means for BusinessProbability Assessment
Section 16(2)(c) Read Down for Bonafide Buyers
Aligned with Karnataka/Tripura approach
Bonafide recipients who can establish good faith and complete documentation chain are protected. ITC denial limited to fraud and collusion cases. Department's recovery focus shifts to suppliers. Higher — SC Oct 2025 Decision Signals
Section 16(2)(c) Struck Down as Unconstitutional
Radical but possible
Provision declared ultra vires; ITC restored to all compliant buyers. Government required to recover tax only from defaulting suppliers. Massive refund/credit implications. Lower — But Raised Before SC
Section 16(2)(c) Upheld in Full
Aligned with Gujarat approach
All recipients bear the risk of supplier non-compliance. ITC system operates as a strict chain — credit only available when actual payment confirmed. Severe working capital implications across industries. Less Likely — Given SC Oct 2025 Decision
🔭
Practical Significance of the SC's October 2025 Decision

The Supreme Court's October 2025 ruling in Civil Appeals 2042-2047/2015 and 9902/2017 — though technically in a DVAT context — is being widely read as a strong signal of the Apex Court's inclination. By expressly endorsing the Delhi HC's position in On Quest/Arise India and reiterating that the department's remedy lies against the defaulting seller, the Supreme Court has effectively telegraphed its doctrinal direction on Section 16(2)(c) under GST as well.


Conclusion — The Enduring Principle: Substantive Equity Over Mechanical Procedure

The judicial story of Section 16(2)(c) and the bonafide recipient doctrine is ultimately about a fundamental constitutional question: can the State impose financial liability on a compliant citizen for the acts or omissions of a third party over whom they have no control and no legal authority? The emerging judicial consensus — reflected in the Supreme Court's own signaling — suggests the answer is no.

The structural legacy of the Filco Trade philosophy in day-to-day ITC disputes is the consistent judicial prioritisation of substance over form, and equity over mechanical procedure. Where a buyer acts in verified good faith, fulfills every obligation within their direct administrative control, and can demonstrate the genuine commercial character of the underlying transaction, the courts have repeatedly found that stripping that buyer of their ITC — simply because the state's own enforcement machinery failed to collect from the registered vendor — amounts to systemic overreach that no constitutional legal system can sanction.

For businesses navigating this landscape right now, the practical imperatives are clear:

Build and maintain a complete documentary chain for every high-value procurement — registration verification, invoice, delivery proof, bank payment, GSTR-2B match.
Keep screenshots of supplier GSTIN status on the GSTN portal at the date of each transaction — this is your primary defence against retrospective cancellation.
If ITC denial notices are received, immediately contest on bonafide grounds — cite the Karnataka, Tripura HC rulings and the SC's October 2025 decision.
Monitor the Supreme Court's ruling on the constitutional challenge to Section 16(2)(c) — this will be the most consequential GST judgment since the system's launch.
Avoid accepting ITC reversal demands without litigation — the law is actively in flux and courts are increasingly favouring genuine taxpayers.
The Department's remedy lies against the defaulting supplier — insist, in every response, that recovery proceedings be initiated against the actual non-compliant party first.

Wednesday, May 27, 2026

ISD Under GST — Meaning, GSTR-6 Filing, Due Dates & Penalties

ISD Under GST — Complete Guide to Input Service Distributor, GSTR-6 Filing, Due Dates & Penalties 2025-26
CGST Act 2017 · Section 2(61) & Section 20  ·  ISD & GSTR-6 · Mandatory from 01 April 2025 · Updated 2025-26
GST Compliance — Input Service Distributor

ISD Under GST —
Meaning, GSTR-6 Filing,
Due Dates & Penalties

Everything a business, CA, or tax professional needs to know about Input Service Distributors — from the statutory definition to step-by-step GSTR-6 filing and the complete penalty framework.

13thMonthly Due Date
₹50/dayLate Fee (Non-NIL)
18%Interest p.a. (Sec. 50)
Apr '25Mandatory Effective
🚨
Mandatory from 01 April 2025

Vide Notification No. 16/2024-Central Tax dated 06 August 2024, the ISD mechanism has been made mandatory for all eligible businesses effective 01 April 2025. Prior to this, ISD registration was optional. Any business distributing common input service ITC across branches must now mandatorily register as an ISD and file GSTR-6 every month.

§ 01 — Meaning & Definition

What Is an Input Service Distributor?

An Input Service Distributor (ISD) is a specific type of GST registrant — typically the Head Office or central procurement unit of a business — that receives tax invoices for input services used by multiple branches or units, and distributes the corresponding Input Tax Credit (ITC) to those branches in accordance with the prescribed rules under GST law.

Statutory Definition — Section 2(61) CGST Act, 2017
"Input Service Distributor means an office of the supplier of goods or services or both which receives tax invoices issued under Section 31 towards the receipt of input services and issues a prescribed document for the purposes of distributing the credit of central tax, State tax, integrated tax or Union territory tax paid on the said services to a supplier of taxable goods or services or both having the same Permanent Account Number as that of the said office."
Source: Section 2(61), CGST Act, 2017 (as amended by Finance Act 2024)

In simpler terms: when a company's Head Office (HO) pays for services — like IT support, software subscriptions, audit fees, legal services, or telecom — that are actually used across multiple branch offices in different states, the HO cannot retain all the ITC. Instead, it registers as an ISD and distributes the ITC to each branch through ISD invoices, which the branches then use to claim credit in their respective GSTR-3B returns.

💡
Key Identifier: Same PAN, Different GSTINs

ISD is specifically designed for entities where multiple GST registrations exist under the same PAN. For example, a company with a Head Office in Mumbai and branches in Chennai, Hyderabad, and Delhi — all with separate GSTINs but the same PAN — is a classic ISD scenario.

🏢 Illustrative Example — How ISD Works

ABC Ltd. has its Head Office in Mumbai with branches in Chennai and Delhi. It pays ₹10 lakh + GST ₹1.8 lakh for an annual IT services subscription used by all three offices.

Supplier
IT Vendor
ISD (Head Office)
ABC Ltd. Mumbai
Branches
Chennai · Delhi

The HO receives the invoice, claims ITC of ₹1.8 lakh as ISD, and distributes proportionate credit to Chennai and Delhi branches via ISD invoices. Each branch reports the received ITC in their GSTR-3B. The HO reports the entire distribution in GSTR-6.

§ 02 — Core Characteristics

Key Features & Characteristics of ISD

🏢
Head Office / Central Office

An ISD is typically the Head Office, registered office, or a dedicated central procurement unit of the business — not the branch offices themselves.

🪪
Separate GST Registration Required

ISD must obtain a separate GST registration as "Input Service Distributor" — different from its regular taxpayer GSTIN, even in the same state.

📦
Input Services Only — Not Goods

ISD mechanism applies exclusively to input services. ITC on goods or capital goods cannot be distributed through the ISD mechanism under GST.

🔗
Same PAN Mandatory

The distributing ISD and all recipient branches must have the same Permanent Account Number (PAN). Cross-PAN ITC distribution is not permitted under this mechanism.

🚫
No Electronic Credit Ledger

Unlike regular taxpayers, an ISD registrant does not maintain an Electronic Credit Ledger. It can only distribute the ITC received — not utilize it for its own tax payment.

🔄
No Reverse Charge Liability

Reverse Charge Mechanism (RCM) does not apply to an ISD. If RCM applies to a supply, the ISD must separately register as a regular taxpayer for that purpose.

§ 03 — Distinction

ISD vs Regular GST Taxpayer

Input Service Distributor (ISD)
  • Separate GST registration as ISD
  • Receives invoices for services used by branches
  • Distributes ITC to branches via ISD invoices
  • Files GSTR-6 monthly (by 13th)
  • No Electronic Credit Ledger
  • Cannot pay its own output tax liability from ISD registration
  • No RCM liability under ISD registration
  • ITC can be eligible or ineligible — both types distributable
Regular GST Taxpayer
  • Standard GSTIN registration
  • Receives invoices for own business use
  • Claims ITC in its own Electronic Credit Ledger
  • Files GSTR-1, GSTR-3B monthly
  • Maintains full Electronic Credit Ledger
  • Pays output tax using ITC or cash
  • RCM applicable on notified supplies
  • ITC only for eligible supplies under Section 16
§ 04 — Distribution Mechanics

ITC Distribution Rules — How Credit Is Apportioned

The ISD distributes ITC to recipient branches using ISD invoices or ISD credit notes. The apportionment rules under Section 20 of the CGST Act (as amended effective 01 April 2025) and Rule 39 of the CGST Rules govern how credit must be allocated.

Distribution Formula — Proportionate Turnover Method

// ITC Distribution Formula — Rule 39, CGST Rules 2017 ITC for Branch = Total ITC × (Turnover of Branch / Total Turnover of All Branches) // Example: Total ITC to distribute : ₹1,80,000 Branch A Turnover : ₹50 lakh → Share: 50% → ITC: ₹90,000 Branch B Turnover : ₹30 lakh → Share: 30% → ITC: ₹54,000 Branch C Turnover : ₹20 lakh → Share: 20% → ITC: ₹36,000 Total : → 100% → ITC: ₹1,80,000// For services used ONLY by specific branches: ITC Attributed = 100% to that branch only (no apportionment required)

Types of ISD Documents

Document TypeWhen IssuedEffect on Recipient
ISD InvoiceWhen distributing ITC of original invoiceRecipient gets ITC credited in their GSTR-2B
ISD Credit NoteWhen original ITC is reduced (supplier issues credit note)Recipient ITC reduced; may add to output liability if negative
ISD Debit NoteWhen additional ITC becomes distributableRecipient gets additional ITC
📌
Finance Act 2025 Expansion — RCM ITC Now Distributable

Sections 20(1) and 20(2) of the CGST Act were amended, effective 01 April 2025, to explicitly permit distribution of ITC on inter-State supplies under Reverse Charge (Section 5(3) and 5(4) of IGST Act) through the ISD mechanism. This closes a significant earlier gap where cross-border RCM IGST credits could not be routed through ISD.

§ 05 — Return Form

What Is GSTR-6?

GSTR-6 is the monthly GST return that every registered Input Service Distributor is mandatorily required to file. It is the official mechanism through which an ISD reports to the Government:

  • 1
    Which invoices (inward supplies of services) were received by the ISD during the month, and the ITC available thereon.
  • 2
    Total eligible and ineligible ITC available for distribution, segregated by IGST, CGST, and SGST/UTGST.
  • 3
    How the ITC was distributed to each recipient branch — the GSTIN-wise, invoice-wise allocation of ISD invoices and ISD credit notes.
  • 4
    Any amendments, corrections, or redistribution of ITC distributed in earlier return periods.
  • 5
    Details of any refund claimed from the Electronic Cash Ledger by the ISD.
🔄
Auto-Population via GSTR-6A

The GST portal auto-populates GSTR-6A for the ISD — a read-only form that contains invoice-wise details of inward supplies as reported by the ISD's suppliers in their GSTR-1. The ISD must verify GSTR-6A data and then file GSTR-6 by accepting, modifying, or adding missing details. Matching with GSTR-2B is critical before filing.

§ 06 — Applicability

Who Must File GSTR-6?

CriteriaGSTR-6 Applicable?Reason
Registered as ISD under GSTMandatoryPrimary condition for filing GSTR-6
No ITC received or distributed in the monthMandatory (NIL)NIL return is still compulsory
Regular taxpayer (not ISD)Not ApplicableFiles GSTR-1 and GSTR-3B instead
Composition taxpayerNot ApplicableFiles GSTR-4 only
Business with multi-state branches (post Apr 2025)Mandatory to register & fileISD mechanism now mandatory for eligible entities
⚠️
NIL Return is Compulsory

Even if an ISD has no ITC to distribute in a particular month, it must still file a NIL GSTR-6. Non-filing of a NIL return will attract late fees just like any other missed return. There are no exceptions to the monthly filing obligation.

§ 07 — Return Format

GSTR-6 Format — All 11 Tables Explained

GSTR-6 consists of 11 tables (sections) that together capture the complete picture of ITC received and distributed by the ISD during the month. Understanding each table is essential for error-free filing.

Table
1–2Auto
GSTIN, Legal Name & Tax Period

Basic identification details of the ISD — GSTIN and legal name as per GST registration, and the tax period (month-year) for which the return is being filed.

Auto-Populated
Table
3Key
ITC Received for Distribution — Inward Supplies

Invoice-wise details of all inward supplies received by the ISD during the month where ITC is available for distribution. Auto-populated from GSTR-6A (supplier's GSTR-1). The ISD must verify, accept, or correct before submitting. Contains GSTIN of supplier, invoice number, date, taxable value, and IGST/CGST/SGST amounts.

Auto-Populated from GSTR-6A Manual Additions Allowed
Table
4
Total ITC Available and Eligible / Ineligible ITC Summary

A summary view of the total ITC available to the ISD for the period, split between eligible ITC (for distribution to branches) and ineligible ITC (blocked under Section 17(5) or otherwise not distributable). Auto-populated from Table 3 data.

System Computed
Table
5Critical
Distribution of ITC — ISD Invoices (Eligible & Ineligible)

The most critical table. The ISD reports the actual distribution of ITC to each recipient branch via ISD invoices. For each ISD invoice, the table captures: recipient GSTIN, ISD invoice number & date, and IGST/CGST/SGST amounts distributed. Both eligible and ineligible ITC distribution is reported here. Once filed, this data flows to the recipient branch's GSTR-2B.

Critical — Manual Entry Required
Table
6A/6B/6C
Amendments to Earlier Returns

Used to correct or amend details reported in earlier GSTR-6 returns. 6A: Amendment to inward supply invoices. 6B: Amendment to debit notes received. 6C: Amendment to credit notes received. GSTR-6 cannot be revised after filing — all corrections must be made through these amendment tables in subsequent months.

Manual — Amendment Only
Table
7
ITC Mismatch and Reclaim

Reports ITC mismatches identified between the ISD's GSTR-6 and supplier's GSTR-1. Any mismatch liability is added to the ISD, which must then issue an ISD credit note to reduce distributed credit. Also used for reclaiming ITC previously reversed due to mismatch.

Manual Review Required
Table
8
Distribution via ISD Credit Notes

Where credit is to be reduced (because the original supplier issued a credit note), the ISD issues ISD credit notes and reports them here. The apportionment of credit reduction follows the same ratio as the original ISD invoice distribution.

Manual Entry
Table
9
Redistribution of ITC Distributed in Earlier Returns

Used when previously distributed ITC needs to be redistributed — for example, when a branch is deregistered, or the original apportionment ratio needs correction based on revised turnover data. Redistributed ITC is allocated among the remaining or corrected set of recipient branches.

Conditional Use
Table
10
Late Fee Payable

Auto-computed by the GST portal. Displays the late fee payable if the return is being filed after the due date (13th of the subsequent month). Late fee must be paid before the return can be submitted. This table is accessible only after the return is filed.

System Computed
Table
11
Refund Claimed from Electronic Cash Ledger

If the ISD has any balance in the Electronic Cash Ledger (from earlier payments) and wishes to claim a refund, the details are entered here. Filing a refund claim through Table 11 results in a debit entry in the Electronic Cash Ledger of the ISD.

Optional
§ 08 — Filing Process

Step-by-Step GSTR-6 Filing Guide

📅
Filing Window

GSTR-6 for a tax period (month M) can only be filed on or after the 10th day of month M+1 and must be filed on or before the 13th day of month M+1. Example: For April 2026, filing window is 10 May 2026 to 13 May 2026.

1

Login to GST Portal

Visit gst.gov.in and log in using the ISD GSTIN credentials (not the regular taxpayer GSTIN). Navigate to: Services → Returns → Returns Dashboard.

2

Select Tax Period & Access GSTR-6

From the Returns Dashboard, select the financial year and the tax period (month). Click on GSTR-6 to open the return. Select "Prepare Online" for manual entry or "Prepare Offline" if using the GST offline tool.

3

Verify GSTR-6A Auto-Populated Data (Table 3)

Review all auto-populated inward supply details in Table 3 (sourced from suppliers' GSTR-1 via GSTR-6A). Verify each invoice — accept correct entries, modify incorrect ones, and manually add any missing invoices not reflected in GSTR-6A.

4

Review Total ITC Summary (Table 4)

Verify the auto-computed total ITC available, split between eligible and ineligible. Confirm the segregation aligns with your books — particularly the Section 17(5) blocked credit classification.

5

Enter ISD Invoice Distribution Details (Table 5)

This is the most critical step. For each ISD invoice issued during the month, enter: recipient branch GSTIN, ISD invoice number and date, and the IGST/CGST/SGST amounts distributed. Apply the turnover-based proportionate apportionment or specific attribution as applicable under Rule 39.

6

Enter ISD Credit Notes (Table 8) — If Applicable

If any supplier has issued a credit note reducing ITC during the period, report the corresponding ISD credit notes issued to branches in Table 8. Apportion the reduction in the same ratio as the original ISD invoice distribution.

7

Enter Amendments or Redistributions (Tables 6A/6B/6C & 9) — If Required

If any earlier period data needs correction, use Tables 6A/6B/6C for invoice amendments. Use Table 9 for redistribution of ITC from earlier periods (e.g., due to branch deregistration or ratio correction).

8

Preview Return & Verify Totals

Use the Preview function to generate a PDF of the return. Cross-verify: (a) total ITC received matches books, (b) total ITC distributed equals total ITC received, (c) each branch's allocation is correct. Total IGST+CGST+SGST available must always equal total distributed (including any negative distribution adjustments).

9

Pay Late Fee (If Applicable)

If filing after the 13th, the portal auto-computes the late fee in Table 10. Pay the late fee through the Electronic Cash Ledger before proceeding. GSTR-6 cannot be filed without clearing the outstanding late fee.

10

Submit & File Using DSC or EVC

Click Submit to freeze the return data. Then proceed to File using either DSC (Digital Signature Certificate) for companies and LLPs, or EVC (Electronic Verification Code) for other taxpayers. Once filed, an Acknowledgment Reference Number (ARN) is generated.

💻
Offline Filing Available

GSTR-6 can also be filed using the GST Offline Utility Tool available for download from the portal. The following sections can be populated offline: Invoice Details (Table 3), Credit/Debit Note Details, Distribution of ITC (Tables 5 & 8), Redistribution of ITC (Table 9), and Amendments (Tables 6A, 6B, 6C). The JSON file generated offline is then uploaded to the portal for final submission.

§ 09 — Due Dates

GSTR-6 Due Dates — Monthly Calendar

The statutory due date for filing GSTR-6 is the 13th day of the month immediately following the tax period. This is fixed under the CGST Act and applies uniformly to all ISD registrants regardless of turnover or state.

Jan 2026
13February 2026
Feb 2026
13March 2026
Mar 2026
13April 2026
Apr 2026
13May 2026
May 2026
13June 2026
Jun 2026
13July 2026
Jul 2026
13August 2026
Aug 2026
13September 2026
Tax PeriodDue DateFiling Window OpensRemarks
Each Calendar Month13th of following month10th of following monthFixed statutory date
No annual returnN/AN/AOnly monthly filing; no GSTR-9 equivalent for ISD
Extension by GovernmentNotified dateAs notifiedCBIC may extend via notification in specific situations
📌
No Annual Return for ISD

Unlike regular taxpayers who file GSTR-9 annually, there is no annual return prescribed for ISD registrants. GSTR-6 filings are exclusively monthly. This makes timely monthly compliance especially important — there is no annual reconciliation opportunity to catch errors.

§ 10 — Penalties & Consequences

Penalties for Late Filing & Non-Compliance

Late Fee — Normal Return
₹50
/day
₹25 CGST + ₹25 SGST
Late Fee for Non-NIL GSTR-6

Where there is ITC to be distributed and the return is filed late, a late fee of ₹25 per day under CGST + ₹25 per day under SGST = ₹50 per day total is levied under Section 47 of the CGST Act. This accrues from the day after the due date (14th) until the actual date of filing.

Late Fee — NIL Return
₹50
/day
Same rate applies
Late Fee for NIL GSTR-6

Unlike GSTR-3B where NIL returns attract a reduced late fee of ₹20/day, no specific reduction has been notified for NIL GSTR-6 returns by the CBIC. Therefore, the standard ₹50/day late fee applies even for NIL GSTR-6 filings. The system automatically blocks filing until the fee is paid.

Interest — Wrong ITC
18%
p.a.
Section 50 CGST Act
Interest on Wrongly Availed ITC by Recipients

If ITC is incorrectly distributed by the ISD and wrongly availed by recipient branches, interest at 18% per annum under Section 50 of the CGST Act is levied on the recipient for the period of wrong availment. If the error involves fraud, the interest rate rises to 24% per annum under Section 50(3).

Demand & Penalty
Up to
100%
Of ITC involved
Demand Proceedings & Penalty Under Section 122

Recovery proceedings under Section 73 (non-fraud) or Section 74 (fraud/suppression) may be initiated. For FY 2024-25 onwards, proceedings are governed by the newly inserted Section 74A (Finance (No.2) Act, 2024). Penalty under Section 122 can extend up to 100% of the ITC wrongly distributed or availed in fraud cases.

ITC Impact
ITC
Lost
Branch level impact
ITC Disruption for Recipient Branches

When GSTR-6 is not filed on time, the distributed ITC does not reflect in the recipient branches' GSTR-2B for that period. Branches cannot claim the ITC they are entitled to, leading to cash flow stress at the branch level, incorrect GSTR-3B filing, or delays in ITC availment.

Penalty Summary Table

DefaultPenalty / ConsequenceLegal Provision
Late filing of GSTR-6₹50 per day (₹25 CGST + ₹25 SGST)Section 47, CGST Act
Wrong ITC distributionInterest @ 18% p.a. on wrongly availed ITCSection 50(1), CGST Act
Fraud / suppressionInterest @ 24% p.a. + penalty up to 100%Sections 50(3) & 74/74A
Delayed payment by recipient post-notice10% of tax or ₹10,000 (whichever higher)Section 73, CGST Act
Non-filing continuouslyCompliance notice + possible registration suspensionSection 29(2), CGST Act
ITC mismatch not resolvedAdded to ISD liability; ISD must issue credit notesRule 39, CGST Rules
§ 11 — Compliance Pitfalls

Common Errors & How to Avoid Them

#Common ErrorConsequenceHow to Avoid
1 Incorrect recipient GSTIN in Table 5 ITC not reflected in correct branch's GSTR-2B Maintain verified branch GSTIN master list; validate on GSTN portal before entry
2 Wrong apportionment ratio applied Branches receive incorrect ITC; redistribution needed later Calculate turnover-based ratio from latest audited financials; update quarterly
3 Using regular GSTIN instead of ISD GSTIN to log in Return filed in wrong entity; creates compliance mess Clearly label ISD credentials; use separate browser profile for ISD login
4 Missing invoices not in GSTR-6A ITC for those invoices not distributed Reconcile GSTR-6A with purchase register before Table 3 verification
5 Forgetting NIL return for months with no ITC Late fee accumulates; portal blocks future filings Set calendar reminder for 13th of every month regardless of ITC activity
6 Not issuing ISD credit notes when supplier issues credit note Branches retain excess ITC; mismatch liability Monitor supplier credit notes monthly; issue ISD credit notes in same period

Conclusion — ISD Compliance Is Now Non-Negotiable

With the mandatory activation of the ISD mechanism from 01 April 2025, every multi-branch business that receives common input service invoices at its Head Office must now register as an ISD, issue ISD invoices for every distribution, and file GSTR-6 every month without exception.

The ISD mechanism — when implemented correctly — ensures seamless, audit-proof distribution of ITC across the enterprise. But when ignored or implemented sloppily, it creates compounding problems: branches lose ITC, demand notices arrive, interest accrues, and audit risk escalates. The key compliance actions every ISD must take:

Register separately as ISD if not already done — mandatory post April 2025.
File GSTR-6 by the 13th every month — NIL returns are also mandatory.
Verify GSTR-6A data against purchase register before Table 3 acceptance.
Apply the correct turnover-based apportionment ratio for ISD invoice distribution.
Issue ISD credit notes promptly when supplier credit notes reduce ITC.
Track GSTR-2B of recipient branches monthly — confirm ITC reflected correctly.
Maintain a dedicated ISD documentation file: invoices, ISD registers, distribution workings.
Coordinate with branches — late GSTR-6 blocks their ITC availment in GSTR-3B.
Input Service Distributor (ISD) Under GST — Section 2(61) & Section 20, CGST Act 2017
GSTR-6 Filing · Notification No. 16/2024-CT dated 06.08.2024 · Mandatory from 01 April 2025
This blog is for educational purposes only.

Consolidated SCN for Multiple Financial Years is Valid Under Sections 73 & 74 of GST Act

Consolidated SCN for Multiple FYs Under GST — Valid, Says Karnataka HC | Chimney Hills Education Society | 2026 Karnataka High C...