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.
