GST E-Invoice Turnover Test: PAN-Level Aggregation, Exclusions and Traps
Finin2min Summary
- Core answer: E-invoicing generally applies when aggregate turnover exceeds ₹5 crore in any preceding financial year from 2017-18 onward, tested across GST registrations under the same PAN. Applicability also depends on the supplier category and document/transaction type; the threshold is not a GSTIN-by-GSTIN test.
- Practical control: Compile PAN-level turnover from FY 2017-18 onward.
- Main risk: Testing each GSTIN separately.
Why This Topic Matters
People searching for GST e-invoice applicability turnover 5 crore usually need a decision, not a textbook definition. E-invoicing generally applies when aggregate turnover exceeds ₹5 crore in any preceding financial year from 2017-18 onward, tested across GST registrations under the same PAN. Applicability also depends on the supplier category and document/transaction type; the threshold is not a GSTIN-by-GSTIN test.
The Finin2min method separates the trigger, calculation, evidence and action so that a portal field, app label or viral headline cannot silently change the underlying conclusion.
The Two-Minute Answer
E-invoicing generally applies when aggregate turnover exceeds ₹5 crore in any preceding financial year from 2017-18 onward, tested across GST registrations under the same PAN. Applicability also depends on the supplier category and document/transaction type; the threshold is not a GSTIN-by-GSTIN test.
Date-sensitive rates, thresholds, forms, scheme terms and portal processes should be checked against the primary sources immediately before action.
How It Works
Aggregate the entire PAN
A group may operate through multiple states and GSTINs, but aggregate turnover is computed at PAN level. A small branch cannot opt out merely because its own state turnover is below ₹5 crore.
Look back across the notified years
Once the threshold was crossed in a relevant preceding financial year, a later fall in turnover does not automatically switch off the mandate. Preserve year-wise turnover evidence from FY 2017-18 onward.
Test person and transaction exemptions
Banks, insurers and other notified classes may have specific exclusions, and SEZ units must be distinguished from SEZ developers. The mandate generally targets B2B, export, debit-note and credit-note documents rather than ordinary B2C invoices.
Build an ERP gate before issue
The tax invoice should be reported to an authorised IRP and returned with a valid IRN and signed QR code before it is issued as an e-invoice. A month-end upload mindset creates invalid-document and ITC risk.
Finin2min Worked Example
A company has three GSTINs with turnover of ₹2.4 crore, ₹1.8 crore and ₹1.2 crore in a preceding year. No GSTIN individually crosses ₹5 crore, but PAN-level aggregate turnover is ₹5.4 crore. Subject to the notified exclusions, the e-invoice mandate can apply across the eligible registrations.
Illustrative numbers are used to explain mechanics unless expressly labelled as official data.
What Viral Explanations Usually Miss
The viral shortcut ‘₹5 crore per GST number’ is wrong. The mandate is built around aggregate turnover and then filtered by notified person and transaction categories.
A usable explanation distinguishes facts, assumptions, illustrations and judgement—and states what would change the answer.
Common Mistakes
- Testing each GSTIN separately
- Checking only the immediately preceding year
- Assuming every document needs an IRN
- Issuing the invoice before IRP validation
Finin2min Action Checklist
- Compile PAN-level turnover from FY 2017-18 onward
- Check notified person-level exclusions
- Map B2B, export, debit and credit documents
- Enable IRP validation in the billing flow
- Reconcile IRN data with GSTR-1 and e-way bills
Finin2min Q&A
Q1. What is the main rule in “GST E-Invoice Turnover Test: PAN-Level Aggregation, Exclusions and Traps”?
E-invoicing generally applies when aggregate turnover exceeds ₹5 crore in any preceding financial year from 2017-18 onward, tested across GST registrations under the same PAN. Applicability also depends on the supplier category and document/transaction type; the threshold is not a GSTIN-by-GSTIN test.
Q2. Why does “Aggregate the entire PAN” matter?
A group may operate through multiple states and GSTINs, but aggregate turnover is computed at PAN level. A small branch cannot opt out merely because its own state turnover is below ₹5 crore.
Q3. How should a reader handle “Look back across the notified years”?
Once the threshold was crossed in a relevant preceding financial year, a later fall in turnover does not automatically switch off the mandate. Preserve year-wise turnover evidence from FY 2017-18 onward.
Q4. What evidence or records should be retained?
At a minimum, retain the source documents that support the trigger, amount, classification and action described in the checklist. The exact pack is topic-specific: Compile PAN-level turnover from FY 2017-18 onward; Check notified person-level exclusions; Map B2B, export, debit and credit documents.
Q5. What is the most common avoidable error?
Testing each GSTIN separately. The safer approach is to complete the decision steps before relying on a headline, calculator or portal prefill.
Q6. When should this article be rechecked?
Recheck the threshold, exempt classes, reporting time limits and IRP advisories before publication.
Sources and Verification Trail
Primary and regulator sources take priority. Product-specific live terms must also be checked.
Visual Direction
PAN tree connecting multiple GSTINs to one turnover threshold and then to the exemption gate.
Third-party marks may be used only as neutral educational identifiers without implying endorsement.
Disclaimer
This material is educational and general. Tax, GST, investment, insurance, lending and regulatory outcomes depend on actual facts, documents, dates and current law. Market-linked investments can lose value.