One PAN, Multiple GSTINs: The GST Grey Zone Between Aggregation and Accountability

 By CA Surekha Ahuja

PAN for aggregation and intelligence. GSTIN for legal accountability. Digital administration to connect the two.

One PAN does not make every GST issue PAN-wise. Multiple GSTINs do not make every issue independent. The real question is: where does the law require aggregation, and where does it require separation?

A multi-State business may have one PAN, multiple GSTINs, one ERP, common management, common accounting policies and one tax function.

Yet two opposite approaches can create problems:

Taxpayer: “My GSTIN is below the threshold, so I independently get the benefit.”

Department: “The PAN has crossed the threshold, so every GSTIN should be treated alike.”

Neither proposition is universally correct.

The answer lies in the specific statutory provision.

PAN and GSTIN do different jobs

Section 2(6) of the CGST Act defines aggregate turnover with reference to persons having the same PAN, computed on an all-India basis, subject to specified exclusions. CBIC also clarifies that where a person's business operates across States, the relevant registration threshold is tested with reference to aggregate turnover.

PAN / enterprise lens	GSTIN / accountability lens
Aggregate turnover where prescribed	Registration in the relevant State/UT
PAN-based threshold tests	GSTIN-wise returns/compliance
AATO-linked tests	Particular supplies/transactions
Cross-GSTIN risk patterns	GSTIN-specific liability
Common business controls	Demand, recovery and proceedings
Enterprise-wide intelligence	GSTIN-wise facts and evidence

QRMP provides a useful illustration: eligibility is determined by aggregate turnover at PAN level, while the scheme operates through the relevant GST registrations.

The principle is simple:

**PAN determines aggregation where the law requires it.

GSTIN determines accountability where the law requires it.**

The biggest misconception: “My branch is below the threshold”

Suppose one PAN has:

GSTIN	Turnover
Delhi	₹12 lakh
Haryana	₹11 lakh
Maharashtra	₹9 lakh
Karnataka	₹8 lakh

If the applicable provision uses aggregate turnover, the taxpayer cannot divide the business into four GSTINs and independently apply the threshold.

But the reverse is equally important:

Crossing a PAN-level threshold does not automatically make every GSTIN subject to every GST consequence.

The particular provision, nature of supply, State/UT, exemption and other statutory conditions must still be examined.

Therefore:  Aggregate where the law says “aggregate”. Separate where the law says “separate”.

This is the line that prevents both taxpayer-side fragmentation and departmental over-aggregation.

The real grey zone

Taxpayer-side fragmentation

Treating GSTINs as completely independent even where the law deliberately looks at the same PAN.

Risk: wrongful threshold or eligibility claim.

Department-side over-aggregation

Treating the entire PAN as one indivisible unit even where the provision, transaction or liability requires GSTIN-wise examination.

Risk: repeated audits, duplicated documents, inconsistent views and avoidable litigation.

The answer is neither extreme.

PAN-level visibility without PAN-level overreach.

The smarter GST architecture

The objective should not simply be “One PAN = One Audit.”

It should be:

                         ONE PAN
                            ↓
                 PAN-WIDE DATA & RISK
                            ↓
                     ONE RISK MAP
                            ↓
        ┌───────────────────┼───────────────────┐
        ↓                   ↓                   ↓
     COMMON             CROSS-GSTIN           UNIQUE
      RISK                  RISK               RISK
        ↓                   ↓                   ↓
      MERGE              COORDINATE          SEPARATE
        └───────────────────┼───────────────────┘
                            ↓
                    GSTIN-WISE FINDING
                            ↓
                  DEMAND / RECOVERY
                            ↓
                APPEAL / LITIGATION
                            ↓
                       OUTCOME
                            ↓
                  PAN-LEVEL LEARNING

One PAN should mean one integrated risk picture—not one blanket audit.

What should merge—and what should remain separate?

Merge / coordinate	Remain GSTIN-specific where required
Common ERP/internal controls	Specific invoices
Common ITC methodology	Local transactions
Common accounting/valuation policy	GSTIN-specific facts
Cross-GSTIN risk patterns	GSTIN-specific liability
Common legal issues	Demand & recovery
Audit history	Statutory proceedings
Related litigation intelligence	Individual appellate rights

The golden rule

Merge the common question—not automatically the legal consequence.

Common facts → common examination

Common risk → coordinated audit

Common legal issue → connected litigation intelligence

Different facts/law → separate proceedings

Why this matters to both Centre and States

GST is a dual administration framework. Centre and States have legitimate interests in revenue, compliance, audit, intelligence and enforcement.

But a multi-State business may have:

1 PAN → 20 GSTINs → 1 ERP → 1 finance team → 1 tax policy

If every GSTIN is viewed in isolation:

The Department may know the pieces but miss the pattern.

PAN-level analytics can reveal:

common vendors + unusual ITC + cross-GSTIN transactions + recurring issues + litigation patterns

which may not be visible from one GSTIN alone.

The result can be:

Better risk selection → targeted audit → better evidence → stronger enforcement → better use of Centre/State resources.

This is not less control. It is smarter control.

But the safeguard is equally important: A risk flag should trigger verification—not become a presumption of evasion.

Same PAN ≠ evasion
Multiple GSTINs ≠ artificial splitting
Risk flag ≠ tax liability
Pending appeal ≠ confirmed demand

Audit and litigation must finally talk to each other

The need for better institutional memory is particularly visible today.

As reported on 23 August 2026, GSTAT data showed 75,155 cases filed, 5,819 registered and only 83 disposed, with 3,492 cases filed in August alone.

The lesson is not merely: “Dispose appeals faster.”

It is also:  “Know whether the same issue has already been examined or decided elsewhere under the same PAN.”

A connected litigation view should track:

Issue → GSTIN → Audit → Order → Appeal filed → Registered → Pending → Disposed → Outcome

This would not merge separate appeals or dilute GSTIN-wise legal rights.

It would create something GST increasingly needs:

Institutional memory.

A material judicial outcome should inform future risk assessment, while each subsequent case must still be decided on its own facts and applicable law.

The 360° solution

Pain point	Better control
GSTIN wrongly treated as independent for a PAN-based threshold	PAN-level statutory validation
Department sees only GSTIN silos	PAN-wide risk engine
Same documents repeatedly sought	Digital evidence repository
Same policy repeatedly examined	Common-issue examination
Cross-GSTIN risk missed	PAN analytics
Genuine local issue gets lost	GSTIN drill-down
Same issue repeatedly audited	Connected audit history
Litigation fragmented	PAN-level issue map
Appeal status scattered	Filed / registered / pending / disposed visibility
Judicial outcomes not reused	Legal-risk feedback loop
Centre/State information fragmented	Controlled intelligence sharing

What each stakeholder gains

Taxpayer: less duplication, cost and disruption.

CFO / Tax Head: one PAN-level compliance and litigation view.

Tax Professional: consistent positions and connected dispute intelligence.

Field Officer: complete facts before taking action.

States: GSTIN-wise jurisdiction and accountability remain protected.

Centre: enterprise-wide risk visibility.

Appellate system: better visibility of recurring issues and outcomes.

**The compliant taxpayer gets less friction. The risky taxpayer gets more visibility.**    That is the balance GST should seek.

The next phase of GST

PAN → Aggregation + Intelligence
GSTIN → Registration + Legal Accountability
Digital Platform → Coordination + Evidence + Litigation Memory

Therefore:  Aggregate where the law requires it.

Analyse risk at PAN level. Audit where risk justifies it.

Separate where facts or law require it.  Preserve GSTIN-wise liability and appeal rights. Feed audit and judicial outcomes back into the risk system.

The objective is not fewer controls. It is fewer disconnected controls.

One PAN. One Complete Risk Picture. GSTIN-wise Accountability.

Common issues together. Genuine exceptions separately. Audit, appeals and outcomes connected.

That is the next logical evolution of GST—not “One PAN, One Audit”, but “One PAN, Smarter GST Administration”.

Professional takeaway

Before claiming any threshold or exemption, identify the exact statutory trigger first—aggregate turnover, AATO, GSTIN-level turnover, nature of supply or another prescribed test.

Do not assume that PAN or GSTIN is universally controlling.

The better GST mindset is:  Understand the business at PAN level. Apply the law at the correct statutory level. And use technology to connect the two.

GST on Liquidation Loss Recovery — Part 2 - ITC Reversal, Scrap Sale & Audit Defence Doctrine

 By CA Surekha Ahuja

This Part operates independently. It addresses the GST consequences arising after inventory loss events — specifically ITC reversal under Section 17(5)(h), subsequent scrap disposal, and capital goods exit under Section 18(6).

Foundational Legal Doctrine — The GST Separation Principle

Under the CGST Act, the tax consequences of inventory loss events are governed by a strict three-layer legal separation framework:

1. Commercial layer → settlement / insurance / recovery
2. Accounting layer → write-off / impairment / destruction entry
3. Tax layer (GST) → ITC reversal or outward supply taxation

Core Legal Proposition

GST consequences are triggered only by the juridical status of goods, not by financial recovery or commercial settlement.

Accordingly:

• ITC reversal and settlement receipt are non-causal events
• One does not legally trigger, negate, or modify the other

Section 17(5)(h) — ITC Blockage: Statutory Trigger Doctrine

Under Section 17(5)(h), ITC is blocked where goods are:

• lost
• stolen
• destroyed
• written off in books of account
• disposed of as gifts or free samples

Interpretative Rule (Substantive Test)

The provision is triggered not by accounting narration, but by:

finality of goods exiting the taxable supply chain

Legally Determinative Question

For audit or litigation purposes:

“Has the goods ceased to exist as a usable taxable asset in the hands of the registered person through physical or accounting finality?”

Inventory Status Classification Matrix (Defence-Grade)

Status of Goods	GST Consequence
Physically available + not written off	No ITC reversal permitted
Written off in books	Mandatory reversal under Section 17(5)(h)
Destroyed / condemned / obsolete disposal	Mandatory reversal
Free samples / gifts	Mandatory reversal

Non-Trigger Principle (Critical Clarification)

A settlement or compensation entry is legally irrelevant for Section 17(5)(h).

• Settlement without write-off → no reversal
• Write-off without settlement → reversal mandatory
• Both co-existing → reversal governed only by write-off status

Scrap Sale .. Independent Supply Doctrine (Section 7 + Section 9)

Scrap disposal represents a fresh taxable event, independent of prior ITC determination.

Core Juridical Separation

Scrap sale is not a recovery mechanism.
It is a distinct supply transaction under GST law.

Therefore:

• ITC reversal logic remains untouched
• Scrap sale does not retroactively validate or invalidate ITC position

Tax Treatment Architecture

Scrap disposal requires:

• Tax invoice issuance under Section 31
• GST charged on transaction value under Section 9
• Reporting in GSTR-1 and GSTR-3B as outward supply

Critical Legal Boundary

Event	Legal Character
Write-off / destruction	ITC reversal event
Scrap sale	Independent taxable supply

These operate in mutually exclusive legal domains.

Capital Goods Exit — Section 18(6) Exclusive Charging Mechanism

Where assets qualify as capital goods, Section 18(6) overrides general inventory principles.

Statutory Computation Rule

Tax payable = higher of:

• ITC availed reduced by prescribed depreciation, OR
• GST on transaction value

Doctrinal Distinction

Provision	Legal Nature	Application
Section 17(5)(h)	ITC blockage	Inventory loss / consumption doctrine
Section 18(6)	Exit taxation	Capital goods disposal doctrine

These provisions are mutually exclusive and cannot be conflated.

Audit Risk Mapping — Litigation Hotspots

GST scrutiny in this area is typically driven by process failure rather than interpretative disputes.

Risk Area	Trigger Point
Inventory mismatch	Physical stock vs books/ERP divergence
ITC retention	Write-off recorded but reversal not done
Scrap leakage	Disposal without GST invoice
Capital goods misclassification	Section 18(6) not applied correctly
Temporal misalignment	Write-off and GST reporting in different periods

Judicial Reality Principle

GST disputes in this domain arise from evidentiary discontinuity, not legal ambiguity

Compliance Defence Architecture 

A defensible GST position requires real-time classification discipline at the moment of inventory change.

Mandatory Classification Protocol

At the point of inventory event:

1. Determine status:
   • active stock
   • written off
   • destroyed
   • scrapped
2. Apply correct tax consequence immediately:
   • Written off/destroyed → Section 17(5)(h) reversal in same tax period
   • Scrapped → GST invoice and outward supply reporting
   • Capital goods → Section 18(6) computation only

Evidentiary Integrity Requirements

Maintain contemporaneous audit-proof documentation:

• Authorised write-off approvals
• Scrap sale invoices and contracts
• Destruction certificates / third-party confirmations
• Inventory reconciliation statements
• ERP audit trail of status change

Core Legal Takeaways (Executive Litigation Summary)

• ITC reversal is triggered only by statutorily recognised inventory cessation events
• Settlement or compensation is legally irrelevant for Section 17(5)(h)
• Scrap sale is a fresh taxable supply, not an adjustment mechanism
• Capital goods disposal is governed exclusively by Section 18(6)
• Audit sustainability depends on temporal alignment of inventory status and GST reporting

Closing Principle — GST Juridical Finality Doctrine

GST operates on a foundational rule:

Tax liability attaches to the legal status of goods at the moment of classification — not the financial outcome thereafter.

Accordingly, the strongest defence is not post-facto justification, but:

• contemporaneous classification
• consistent accounting alignment
• and synchronized GST reporting discipline

ITC on Canteen Services: The Complete Decision Guide for Indian Businesses

By CA Surekha Ahuja

Whether your factory canteen qualifies for GST input tax credit (ITC) depends on a few critical facts—not assumptions. GST on canteen services remains one of the most litigated ITC issues for manufacturers. While Section 17(5) of the CGST Act generally blocks ITC on food, beverages, and catering services, a statutory factory canteen may qualify for credit where specific legal and factual conditions are satisfied.

The key is to determine whether the statutory exception applies and whether adequate documentation exists to support the claim during audit or assessment.

The Legal Framework

Under Section 17(5)(b)(i) of the CGST Act, ITC on food and beverages and outdoor catering services is generally blocked. However, the proviso to Section 17(5)(b) permits ITC where the inward supply is obligatory for an employer to provide to its employees under any law for the time being in force.

For factories, Section 46 of the Factories Act, 1948 and the applicable State Rules require certain factories employing the prescribed number of workers to provide and maintain a canteen facility. Where this statutory obligation exists, the restriction under Section 17(5)(b) may not apply, subject to fulfillment of all other conditions under GST law.

Further, Circular No. 172/04/2022-GST clarified that the proviso applies to the entire clause (b) of Section 17(5), including canteen services. This clarification has significantly strengthened the position of taxpayers claiming ITC on statutory canteens.

However, the exception under Section 17(5) does not automatically guarantee ITC. Taxpayers must still satisfy the conditions prescribed under Section 16 of the CGST Act, including possession of a valid tax invoice, receipt of services, payment of tax by the supplier, and compliance with return filing requirements.

Decision Framework: Four Questions Before Claiming ITC

Before claiming ITC on canteen services, evaluate the following:

Question	If Yes	If No
Is the canteen mandatory under applicable law?	Proceed to next test	ITC may remain blocked under Section 17(5)(b)
Is the canteen maintained primarily for employees in discharge of a statutory obligation?	Stronger ITC position	Additional evaluation required
Is the cost substantially borne by the employer?	Simpler ITC position	Employee recoveries require separate analysis
Are adequate records available to support the claim?	Defensible claim	Significant audit risk

A taxpayer should ideally satisfy all four tests before claiming ITC on canteen services.

Common Scenarios and Their Likely ITC Position

Situation	ITC Position	Key Action
Statutory canteen, regular employees only, employer bears full cost	Strongest position	Maintain complete statutory and GST records
Statutory canteen with employee contribution	Generally supportable, subject to position adopted	Document recoveries and supporting rationale
Statutory canteen serving employees and contract workers	Additional litigation risk	Maintain reasonable allocation methodology
Voluntary canteen without statutory requirement	Generally blocked	Evaluate carefully before claiming
Multi-location entity with centralized vendor invoice	Allocation required	Maintain location-wise workings
Canteen serving only contract workers	High litigation risk	Obtain specific legal evaluation before claiming

Employee Recoveries and Contract Workers

Many businesses recover a nominal amount from employees through salary deductions, meal coupons, or direct recoveries. While this does not necessarily defeat the ITC claim, it introduces additional GST considerations and documentation requirements. Many taxpayers adopt a conservative approach by restricting ITC to the employer-borne portion of the expenditure.

Where contract workers also use the canteen facility, the position becomes more litigative. While several rulings have adopted a restrictive approach in relation to contract labour, the issue is not entirely free from dispute. Businesses should therefore maintain separate records of employee and contract-worker usage wherever feasible and adopt a reasonable allocation methodology supported by documentation.

The objective should not be to maximize ITC, but to ensure that the claim remains sustainable under scrutiny.

Subsidy Model vs Recovery Model

Particulars	Employer Bears Full Cost	Employee Contribution Exists
ITC position	Generally simpler	Requires additional evaluation
Documentation burden	Lower	Higher
Reconciliation requirements	Minimal	Greater
Litigation exposure	Lower	Potentially higher
Employer cash outflow	Higher	Lower

From an ITC perspective, the strongest position generally exists where the employer bears the entire canteen cost and maintains clear supporting documentation.

Outsourced Caterers and Vendor Models

Today, most factories engage third-party caterers rather than operating canteens themselves. Where an external caterer or canteen contractor charges GST on the invoice, the charging of GST alone does not automatically make ITC available.

Eligibility continues to depend upon:

• Whether the canteen is mandatory under the applicable law.
• Whether the conditions of Section 16 are satisfied.
• Whether the exception under Section 17(5)(b) applies.
• The category of users availing the facility.
• The treatment adopted for employee recoveries, if any.

Accordingly, GST charged by the contractor is only one requirement for claiming ITC. It does not override the restrictions contained in Section 17(5) of the CGST Act.

Practical Position

Situation	ITC Position
External caterer charges GST for a statutory canteen maintained for employees	Generally the strongest case for claiming ITC, subject to Sections 16 and 17(5)
External caterer charges GST for a voluntary employee canteen	GST charged by the vendor alone does not make ITC eligible
Employees and contract workers use the same outsourced facility	Appropriate allocation and documentation required
Employee recoveries exist	GST implications and supporting documentation should be evaluated

Third-Party Vendor vs Self-Managed Canteen

Particulars	Third-Party Caterer	Self-Managed Canteen
GST documentation	Simpler	More complex
Audit trail	Stronger	Requires detailed internal controls
Compliance burden	Lower	Higher
Input tracking	Easier	More challenging
Suitability	Large and multi-location factories	Businesses seeking greater operational control

The Strongest ITC Case Looks Like This

✓ Factory covered by statutory canteen requirements.

✓ Canteen maintained primarily for employees.

✓ Employer bears the entire cost.

✓ GST charged by a registered caterer or canteen contractor under a valid tax invoice.

✓ Invoice reflected in GSTR-2B.

✓ Proper vendor agreement and supporting records maintained.

✓ Complete documentation establishing the statutory obligation.

✓ No material gaps in GST compliance or reconciliations.

Compliance Checklist

Before claiming ITC, ensure that the following records are available:

✓ Proof of applicability of statutory canteen requirements.

✓ Internal legal note documenting the basis of eligibility.

✓ Vendor agreement defining the scope of services.

✓ Valid GST invoices and GSTR-2B reconciliation.

✓ Employee and contract-worker headcount records.

✓ Details of canteen recoveries, if any.

✓ Allocation workings where multiple user categories exist.

✓ Attendance records, swipe logs, coupon records, or equivalent evidence.

✓ Monthly finance-approved ITC computation workings.

✓ Proper record retention for future audits and assessments.

Documentation Matrix

Document	Purpose
Factory registration and worker-count records	Establish statutory obligation
Applicable State Rule / legal note	Demonstrate legal requirement
Vendor agreement	Define service scope
GST invoice and GSTR-2B reconciliation	Support Section 16 compliance
Employee recovery records	Support treatment adopted
Contract-worker records	Support allocation methodology
Attendance or usage records	Evidence of actual utilization
Monthly ITC workings	Support quantum of credit claimed

Quick Reference

Position	Typical Scenario
Strongest ITC Position	Statutory canteen + employees + employer bears cost + GST charged by registered caterer
Position Requiring Additional Analysis	Employee recoveries from canteen users
Position Requiring Allocation	Employees and contract workers using the same canteen
Higher-Risk Position	Voluntary canteen or claims lacking adequate statutory and documentary support

Key Takeaway

The availability of ITC on canteen services depends less on the fact that GST has been charged and more on whether the canteen is being provided in discharge of a statutory obligation and whether the claim can be supported with proper records.

The smartest strategy is to claim only what is legally supportable, operationally traceable, and adequately documented. A well-structured and evidence-backed position is far more valuable than an aggressive claim that may later result in reversals, interest, penalties, and avoidable litigation.

GSTN E-Way Bill Changes 2026: Mandatory Ship-To GSTIN, EWB Closure Facility & GST Audit Impact

 By CA Surekha Ahuja

GSTN Advisory No. 661 Signals a Shift Towards Data-Driven GST Compliance

Key Message: GSTN Advisory No. 661 is not merely an E-Way Bill enhancement—it reflects GSTN's broader move towards GSTIN-based movement governance, stronger data analytics and more integrated compliance verification.

For years, GST compliance has largely been driven by documents—tax invoices, E-Way Bills, GST returns, delivery challans and transport records.

However, the future of GST compliance is no longer about whether documents exist.

It is about whether all available data tells the same commercial story.

An invoice may identify one recipient.

The goods may move elsewhere.

The transporter records may indicate a different destination.

The Input Tax Credit (ITC) may ultimately be claimed by another entity.

Individually, each record may appear compliant. Collectively, inconsistencies can raise significant compliance risks.

It is against this backdrop that GSTN Advisory No. 661 assumes importance.

The advisory introduces two important changes:

• Mandatory reporting of Ship-To GSTIN in qualifying Bill-To/Ship-To transactions; and
• Voluntary E-Way Bill Closure Facility after completion of delivery.

While these may appear to be operational changes, they are part of a much larger transition towards technology-driven GST enforcement and movement verification.

Executive Snapshot

Particulars	Key Change
Ship-To GSTIN	Mandatory in qualifying Bill-To/Ship-To transactions
EWB Closure Facility	Voluntary
Objective	Stronger movement traceability
Compliance Impact	Better reconciliation and audit trail
Enforcement Impact	Enhanced fake billing detection and analytics
Key Stakeholders	Manufacturers, traders, e-commerce operators, transporters and job workers

Why This Update Matters

GSTN's objective is no longer limited to facilitating tax compliance.

Increasingly, it is building a digital ecosystem where transactions can be independently verified through connected data.

Recent GST reforms all point in the same direction:

• E-Invoicing validates transactions.
• GST Returns report tax positions.
• ITC matching improves verification.
• Risk-based scrutiny relies on analytics.
• E-Way Bills monitor movement of goods.

The latest E-Way Bill enhancements further strengthen this framework by connecting movement data with actual destination GSTINs.

The Shift Is Clear

Earlier Focus	Emerging Focus
Document Availability	Data Consistency
Address-Based Reporting	GSTIN-Based Reporting
Reactive Verification	Predictive Analytics
Standalone Records	Connected Compliance Data

This is the real significance of the advisory.

Mandatory Ship-To GSTIN: What Has Changed?

Under the revised framework, qualifying Bill-To/Ship-To transactions will require reporting of the actual destination GSTIN.

Where goods are delivered to an unregistered recipient, URP (Unregistered Person) must be reported.

Why It Matters

Historically, E-Way Bills often relied heavily on delivery addresses.

Addresses can be interpreted.

GSTINs can be validated.

By capturing the actual destination GSTIN, GSTN gains a more reliable and verifiable movement trail capable of being matched with invoices, GST returns and ITC claims.

Example

A manufacturer invoices a distributor but dispatches goods directly to the distributor's customer.

Under the revised framework, the actual destination GSTIN becomes a structured and reportable element of the E-Way Bill record, significantly improving traceability.

Why GST Authorities Are Interested

The most significant aspect of the amendment is the analytical capability it creates.

Authorities can increasingly reconcile information from multiple systems:

Data Source	Information Available
GSTR-1	Invoice details
E-Way Bill	Ship-To GSTIN and movement trail
GSTR-2B	ITC claimant
Transport Records	Vehicle movement evidence
Physical Verification	Existence of recipient location

Professional Insight

The amendment does not create a new offence.

Nor does every mismatch imply wrongdoing.

However, it significantly enhances the ability of authorities to identify situations where invoice flow, movement of goods and ITC claims do not support the same commercial transaction.

Future scrutiny is likely to focus increasingly on consistency of data rather than merely the existence of documents.

A Significant Development for Job Work Compliance

The implications for manufacturing and job-work-intensive industries are particularly important.

Historically, job-work compliance relied heavily on:

• Delivery challans;
• ITC-04 reporting;
• Internal stock records; and
• Independently generated E-Way Bills.

The revised framework creates a stronger GSTIN-linked movement trail.

Movement	Ship-To GSTIN
Principal → Job Worker	Job Worker's GSTIN
Job Worker → Principal	Principal's GSTIN

This enables more effective reconciliation between:

• ITC-04 filings;
• Job-work challans;
• E-Way Bills; and
• Return movements.

Businesses engaged in job-work arrangements should review their documentation and movement tracking systems proactively.

Understanding the Voluntary E-Way Bill Closure Facility

GSTN has also introduced a facility allowing suppliers, recipients, transporters, drivers and authorised persons to voluntarily close an E-Way Bill after delivery.

Important Clarification

The closure facility is currently voluntary and not mandatory.

Nevertheless, businesses should not underestimate its practical value.

Potential benefits include:

• Better delivery confirmation;
• Stronger audit trails;
• Documentation of cancelled dispatches;
• Identification of duplicate EWBs;
• Improved governance and internal controls.

Should Businesses Adopt It?

From a compliance and governance perspective, early adoption is advisable, particularly for businesses with significant logistics and supply-chain operations.

What This Means for Future GST Audits

Perhaps the most important implication of the advisory lies in how GST audits may evolve.

Historically, GST verification focused primarily on:

• Tax invoices;
• Books of account;
• GST returns; and
• E-Way Bills viewed independently.

Going forward, authorities may increasingly evaluate:

✓ Bill-To vs Ship-To GSTIN consistency

✓ E-Way Bill vs ITC claim correlation

✓ Job-work movement chains

✓ Transport evidence

✓ ERP-generated audit trails

✓ EWB closure records

The question may no longer be whether documents exist.

The question may increasingly be whether all available datasets support the same commercial narrative.

Immediate Action Checklist for Businesses

Action Item	Priority
Review consignee master data	High
Introduce Ship-To GSTIN validation controls	High
Upgrade ERP and EWB workflows	High
Review job-worker GSTIN mapping	High
Strengthen reconciliation procedures	High
Evaluate EWB closure processes	Medium
Train logistics and dispatch teams	Medium

Businesses that utilise the implementation window effectively are likely to face fewer operational disruptions once validations become fully operational.

Beyond Compliance: What GSTN Is Really Building

Viewed narrowly, GSTN Advisory No. 661 introduces a new field and a new facility.

Viewed strategically, it reveals the future direction of GST compliance.

Consider the architecture gradually emerging:

Compliance Layer	Purpose
E-Invoicing	Identifies the transaction
GST Returns	Reports the tax position
E-Way Bills	Records movement
Ship-To GSTIN	Identifies destination
Closure Records	May help establish completion

Together, these elements create a connected digital trail capable of independently validating commercial activity.

The GST ecosystem is steadily moving:

From Document Verification to Data Validation

From Address-Based Reporting to GSTIN-Based Movement Governance

From Reactive Scrutiny to Predictive Analytics

That is the larger message behind GSTN Advisory No. 661.

Key Takeaways

Issue	Business Message
Ship-To GSTIN	Review ERP and master data immediately
Fake Billing Detection	Expect stronger GST analytics
Job Work Compliance	Strengthen movement documentation
EWB Closure Facility	Consider voluntary adoption
GST Audits	Focus on consistency across records
Future Readiness	Build stronger data governance controls

Conclusion

GSTN Advisory No. 661 is far more than an E-Way Bill portal enhancement.

The mandatory Ship-To GSTIN requirement strengthens traceability, improves movement verification and supports more reliable reconciliation across GST compliance systems.

The voluntary E-Way Bill Closure Facility enhances governance, documentation and operational visibility.

More importantly, both developments reinforce a clear regulatory direction: GST compliance is steadily evolving towards a framework where invoice data, movement records, recipient reporting and operational evidence are expected to align seamlessly.

For businesses, the message is clear—strengthen master data, upgrade ERP controls, improve reconciliation processes and prepare for a compliance environment where transparency is increasingly measured through connected data rather than isolated documents.

GST on Forfeiture of Token Money in a Proposed Lease

 By CA Surekha Ahuja

Whether Retention of Earnest Money Constitutes a Taxable Supply Under GST

A landlord forfeits a token deposit when a proposed lease falls through. Is that GST?

It's a scenario that plays out constantly in commercial real estate: a prospective tenant pays a token amount during negotiations, the deal collapses before the lease is ever signed, and the landlord keeps the money. The tenant's accountant asks the obvious question — does GST apply to this forfeiture? The landlord's accountant, unsure, often defaults to caution and charges GST "just to be safe."

That caution is frequently misplaced. The answer, in most such cases, is no. GST is a tax on supply, not on every rupee that changes hands or every commercial disappointment. Whether a forfeited token amount attracts GST depends entirely on what that money actually represents — and the answer can differ sharply depending on a handful of factual details that are easy to overlook.

Executive Summary

One of the most misunderstood areas under GST is the taxability of forfeited advances, token money, earnest money deposits, and cancellation-related receipts.

Where no lease deed is executed, possession is never handed over, tenancy never commences, and the amount represents forfeited earnest money due to failure of the proposed transaction, the stronger legal position is that such forfeiture falls outside the scope of GST.

However, where the amount instead represents a cancellation charge, termination fee, or consideration for permitting withdrawal from an existing arrangement, GST implications can arise. The distinction is subtle but extremely important — and it turns on facts and drafting, not on labels.

Understanding the GST Trigger: Section 7

Before examining forfeiture, one must first determine whether a taxable supply exists at all. Section 7 of the CGST Act, 2017 provides that GST applies only where three elements are simultaneously present:

Requirement	Meaning
Supply	Goods or services must actually be supplied
Consideration	The supply must be made against consideration
Business Nexus	The supply must be in the course or furtherance of business

If any one of these elements fails, GST cannot arise. So the real question is never "was money retained?" It is: was money retained as consideration for a supply?

What Counts as Consideration: Section 2(31)

Section 2(31) of the CGST Act defines "consideration" to include payments made for a supply, payments made in response to a supply, and payments made to induce a supply. The retained amount must therefore have a direct nexus with an identifiable supply — a mere commercial loss, compensation, damages award, or forfeiture does not automatically qualify as consideration just because money moved from one party to another.

The Most Misused Provision: Schedule II, Entry 5(e)

Tax authorities frequently reach for Entry 5(e) of Schedule II, which deems certain acts to be a supply of services: agreeing to refrain from an act, to tolerate an act or situation, or to do an act. This is the provision invoked to argue that a cancellation charge, exit fee, or "compensation" is really payment for a service — the service of letting someone off the hook. It covers situations such as cancellation facilities, early-exit arrangements, non-compete agreements, contractual permissions, and tolerance arrangements specifically agreed between the parties.

But the provision cannot be stretched to cover every contractual breach. If every breach were treated as a taxable supply, virtually every damages claim in commercial life would become liable to GST — an interpretation the legislature never intended. Many forfeitures are simply compensatory: money kept because a deal failed, not because a service was rendered.

CBIC's Clarification: Circular No. 178/10/2022-GST

The clearest official guidance on this point is CBIC Circular No. 178/10/2022-GST, dated August 3, 2022, which addresses the taxability of liquidated damages, penalties, compensation, and forfeitures. The Circular draws a clear line between two categories of receipt that look similar on the surface but are treated very differently.

Category A — amounts received as consideration for a facility or benefit. Examples include cancellation charges, early-termination charges, exit fees, and postponement charges. These are generally taxable, because the supplier is providing an independent contractual facility in exchange for the payment.

Category B — amounts received as compensation for breach or non-performance. Examples include liquidated damages, contractual penalties, earnest money forfeiture, and bid security forfeiture. These generally do not constitute consideration for any supply.

Crucially, the Circular specifically recognizes that earnest money may be forfeited to discourage non-serious participants, and that such forfeiture does not automatically amount to a taxable supply. This significantly weakens any argument that every forfeiture represents "toleration of an act."

Supreme Court Principles: Satish Batra v. Sudhir Rawal

Although decided under contract law rather than GST law, the Supreme Court's reasoning in Satish Batra v. Sudhir Rawal remains highly relevant. The Court held that earnest money serves as security for performance, that forfeiture is permissible where contractual conditions are satisfied, and — importantly — that earnest money is distinct from an ordinary advance payment toward price.

That distinction carries over neatly into the GST analysis:

Feature	Earnest Money	Advance / Part-Payment
Security for performance	Yes	No
Paid as commitment to complete the transaction	Yes	Often
Forms part of the eventual transaction value	No	Yes
Can be forfeited upon default	Yes	Rarely framed this way
Adjusted against rent or price once supply occurs	No	Yes
Generally consideration for a service	No	Potentially yes

Money paid as a pledge of performance, and forfeited because the deal fell apart, looks like compensation for breach. Money that forms part of the transaction value, or is paid as a fee for the privilege of walking away, looks far more like consideration for a supply.

Applying This to a Real Lease Negotiation

Consider a common fact pattern:

Particulars	Position
Token money paid	₹50,000
Lease deed executed	No
Possession handed over	No
Tenancy commenced	No
Rent became payable	No
Amount retained	Yes

On these facts, no renting service ever came into existence. There was no transfer of possessory rights, no right to occupy, no enjoyment of premises, and no supply of renting services — and therefore no principal supply on which GST could be levied. The ₹50,000 is best read as earnest money or a token advance, forfeited because the proposed transaction itself failed, not as a fee charged for a cancellation facility on an otherwise live lease. The forfeiture simply reflects the commercial consequences of a failed negotiation.

Seven Scenarios, Seven Different Answers

The same word — "forfeiture" — can describe transactions with very different GST consequences.

1. Negotiation stage only — no deed, no possession. The strongest case for non-taxability. The transaction never matured into a supply of renting services.

2. Lease deed signed, but possession never handed over. Fact-sensitive. If the amount is clearly earnest money forfeited for default, non-taxability remains defensible; if the agreement creates a separate, standalone obligation to pay for cancellation, risk arises under Schedule II, entry 5(e).

3. Lease commenced, then terminated early. Once possession has been handed over and the lease is operational, early-termination charges or exit fees look much more like consideration for tolerating a situation — and are more likely to be taxable.

4. Token amount adjusted against rent. Once applied against rent or lease consideration, it simply becomes part of the taxable value of the renting supply.

5. Purely refundable security deposit. Generally not consideration at all, unless and until it is adjusted, appropriated, or forfeited in a way that ties it to a supply.

6. An express cancellation fee. If the documentation explicitly labels the amount a cancellation fee, termination fee, or charge for permitting withdrawal, it's much harder to argue non-taxability.

7. Liquidated damages or compensation clauses. Not automatically taxable merely because they sit in a contract clause — the real test is whether the payment is genuinely compensatory or a disguised charge for an agreed facility.

Scenario Matrix at a Glance

Situation	GST Position
Negotiations fail before lease execution	Generally outside GST
Token money forfeited before possession	Generally outside GST
Earnest money forfeited due to default	Generally outside GST
Lease operational and exit charges collected	Likely taxable
Cancellation fee specifically agreed	Likely taxable
Amount adjusted against rent	Taxable
Refundable security deposit merely held	Not taxable
Deposit appropriated towards supply	Taxable

Why This Is Different From a Cancellation Charge

A common error is treating forfeiture and cancellation charges as the same thing. They are legally distinct.

With a cancellation charge, the supplier provides a contractual facility allowing the customer to cancel, and the payment is consideration for that facility — GST generally applies.

With earnest money forfeiture, no facility is supplied, no benefit is granted, and no service is rendered. The amount merely compensates the affected party for failure of the transaction, so GST generally does not apply.

Substance Prevails Over Accounting Treatment

Crediting the amount to "Other Income," "Miscellaneous Income," or "Forfeiture Income" in the books does not, by itself, determine GST liability. Authorities examine commercial substance (what was the purpose of the payment, why was it retained, was any service actually supplied), contractual language (was cancellation permitted for a fee, was breach tolerated for consideration, was it described as earnest money), and conduct of the parties (was possession delivered, did tenancy commence, did any lease rights arise). Substance always overrides nomenclature.

Advance Ruling Trends

Various advance rulings examining forfeiture of earnest money and security deposits have generally adopted the principle that mere forfeiture does not create a taxable supply unless a distinct supply can be identified. The consistent theme is that GST applies to supplies, not to every flow of money between contracting parties — the existence of consideration alone is insufficient; there must first be an identifiable supply.

Documentation That Strengthens the Non-Taxable Position

From a litigation perspective, documentation is often more decisive than legal argument. Useful records include:

Document	Purpose
Negotiation correspondence	Establishes the failed transaction
Non-execution confirmation	Shows the lease never materialized
Possession records	Demonstrates no occupation rights were transferred
Settlement communication	Clarifies the basis of forfeiture
Accounting note	Records the amount as earnest money forfeiture
Internal approval note	Justifies retention of the amount
Legal memorandum	Supports the GST position taken

Drafting Mistakes That Can Create GST Exposure

Avoid language such as "fee for cancellation," "amount charged for withdrawal," "payment for allowing exit," "consideration for terminating negotiations," or "charge for tolerating breach." Such wording can hand the department exactly what it needs to invoke Schedule II, entry 5(e).

Prefer expressions such as "earnest money forfeiture," "forfeiture due to non-performance," "compensation for failure to complete transaction," or "retention of security against contractual default." The wording chosen should accurately reflect commercial substance — not just hedge for convenience.

Compliance and GST Return Reporting

Where forfeiture genuinely falls outside GST: no reporting is required as taxable outward supply in GSTR-1, and no liability arises in GSTR-3B. In the books of account, the amount may still be recognized as Forfeiture Income or Other Income. For audit documentation, maintain a legal note explaining the absence of supply, the absence of consideration for any service, and the applicability of CBIC Circular No. 178/10/2022-GST — this becomes valuable during departmental scrutiny and GSTR-9C reconciliation.

The key compliance discipline is internal consistency: if the books record forfeiture income but the GST returns show nothing, the file should contain a clear, contemporaneous note explaining why Section 7 doesn't apply.

Key Legal Principles at a Glance

Principle	Position
GST is a tax on supply	Correct
Every forfeiture is taxable	Incorrect
Earnest money forfeiture automatically attracts GST	Incorrect
Cancellation fee may attract GST	Correct
Failed lease negotiations create a renting service	Incorrect
No possession + no lease + no tenancy	Strong non-taxable case
Contract wording influences the GST outcome	Correct
Substance prevails over nomenclature	Correct

The Bottom Line

GST taxes supply, not every commercial loss. A token amount forfeited because a prospective tenant backed out before a lease was ever executed is compensation for a failed transaction, not consideration for a service — and compensation is not the same thing as consideration for supply. The moment a business starts charging a price for a facility — cancellation, early exit, postponement, or tolerating a breach — that price becomes consideration, and GST follows.

On facts where the lease was never executed, possession was never handed over, and the tenancy never began, the stronger and more defensible position is that the forfeited amount sits outside GST. That conclusion can flip entirely if the documentation instead points to an express cancellation charge or a standalone arrangement to tolerate breach for a price. The decisive test is not whether money changed hands — it is whether the money was received for a supply. In GST, as in most tax questions, substance and paperwork decide the outcome, not the label sitting in the ledger.