E-invoicing is not a billing-software feature; it is a statutory invoice-control process. Once your business crosses the notified turnover threshold, finance must ensure eligible documents are reported to the Invoice Registration Portal, IRNs are generated, QR codes are carried, and GSTR-1/e-way bill data does not drift away from books.
Who should watch the threshold?
Finance teams should monitor aggregate turnover at PAN level, not merely branch-wise GSTIN turnover. Notification 10/2023-Central Tax implements e-invoicing for taxpayers having aggregate turnover exceeding ₹5 crore from 1 August 2023. That threshold should be checked before year-end, before onboarding new billing software, and whenever a group entity or new GSTIN is added to the invoicing process.
Do not wait for customer disputes. If e-invoicing applies and an eligible B2B/export invoice is issued without IRN, the buyer may challenge the invoice and ITC support. Build the control before the first invoice crosses the workflow.
Applicability control table
| Control area | What to check | Owner |
|---|
| Turnover trigger | Whether aggregate turnover exceeds the notified e-invoice limit in any relevant year. | Tax lead / CFO |
| Document coverage | B2B invoices, debit notes, credit notes and export invoices in the ERP workflow. | Billing + GST |
| IRN generation | IRN, acknowledgement number/date and QR code captured before sharing invoice. | Billing ops |
| Non-applicable cases | Exempted persons/classes and B2C invoices segregated correctly. | GST reviewer |
| Return linkage | IRP data, GSTR-1 and books reconciled every return cycle. | GST compliance team |
Finance-team checklist before go-live
- Tag every GSTIN and invoice series that will need IRN generation.
- Validate customer GSTIN, state code, HSN/SAC, place of supply and reverse-charge flag before upload.
- Map e-invoice fields to Rule 46 invoice particulars and Rule 48 e-invoice workflow.
- Create an exception queue for failed IRN, duplicate document number, wrong GSTIN and export endorsement errors.
- Block invoice dispatch until IRN/QR code is available wherever e-invoicing is mandatory.
- Keep a separate process for credit notes and debit notes linked to original invoices.
Common mistakes to avoid
- Monitoring turnover GSTIN-wise instead of at PAN-level.
- Assuming exports are outside the e-invoice workflow without checking applicability.
- Letting sales teams manually edit PDF invoices after IRN generation.
- Not reconciling IRP data with GSTR-1 and books.
- Not testing cancellation, credit note and amendment flows before go-live.
Finin2min publishing checklist before upload
- Re-check the e-invoice threshold and any time-limit advisories on the official e-invoice portal.
- Do not quote a new turnover threshold unless supported by a current notification.
- Add an SME example: SaaS, D2C, manufacturer, exporter or professional services firm.
- Cross-link to e-invoice cancellation, export invoice and GSTR-1 reconciliation articles.
Official References Used
This draft uses official GST law, rules, GST Council, CBIC/GST portal and e-invoice/e-way bill portal sources only. Before publishing, re-check whether any notification, circular, rule text or portal workflow has changed after the draft date.
Frequently Asked Questions
Is e-invoicing based on GSTIN turnover or PAN-level aggregate turnover? ▼
The notified threshold is linked to aggregate turnover. Finance teams should monitor PAN-level turnover across GSTINs and then apply e-invoicing controls to the relevant registered persons/document flows.
Does e-invoicing replace GSTR-1 filing? ▼
No. E-invoicing helps populate/report invoice data, but return filing and reconciliation controls continue separately.
Should exporters generate e-invoices? ▼
If e-invoicing applies to the registered person and the document type is covered, export invoices must be included in the workflow with the required export endorsement and details.