· 9 min read
By Correct Editorial — Compliance Research Desk
E-invoice vs Regular Invoice: Key Differences
Published on: July 29, 2026
Most Indian businesses use the words invoice and e-invoice interchangeably, and that confusion is expensive. An e-invoice is not a PDF emailed to a customer. It is an invoice whose particulars were reported to a government Invoice Registration Portal (IRP) before issue, and which came back stamped with an Invoice Reference Number (IRN) and a digitally signed QR code.
The distinction has a hard legal edge. Rule 48(4) of the CGST Rules, 2017 requires notified taxpayers to prepare invoices through the IRP, and Rule 48(5) says that any invoice issued by such a taxpayer without an IRN is not an invoice. The threshold has fallen steadily — from ₹500 crore in October 2020 to ₹5 crore since 1 August 2023 under Notification No. 10/2023-Central Tax — and remains at ₹5 crore for FY 2026-27. Every business that crossed that turnover even once since FY 2017-18 is inside the net.
This article sets out the differences that actually change your process: who is covered, which documents need an IRN, how the IRP workflow runs, the 30-day reporting limit for larger taxpayers, what you can and cannot correct, and the consequences of getting it wrong.
What is the core difference between an e-invoice and a regular invoice?
A regular invoice is created and issued entirely inside your own billing system. An e-invoice is the same commercial document, but its particulars are first reported to an IRP in FORM GST INV-01, validated, and returned with a unique IRN and a signed QR code. Only then can it be issued to the customer.
Everything else follows from that single change:
- Authentication moves outside your system. The government, not your software, confirms the document exists
- The content is standardised. A prescribed schema replaces free-form templates, so field names, code lists and data types are fixed
- Reporting becomes automatic. IRN data auto-populates GSTR-1, the buyer's GSTR-2B and the e-way bill Part A
- Editing stops at generation. A regular invoice can be corrected before filing; an e-invoice can only be cancelled in full within 24 hours or adjusted later through a credit or debit note
How do the two documents compare, field by field?
The commercial content is identical — both must satisfy Rule 46. The differences sit in authentication, timing, correction rights and downstream reporting. This table is the version worth circulating to a billing team.
| Dimension | Regular invoice | E-invoice |
|---|---|---|
| Legal basis | Section 31, Rule 46 | Section 31, Rule 46 plus Rule 48(4) |
| Who generates the number | Your billing system | Your system, validated and stamped by the IRP |
| Unique identifier | Your serial number only | Serial number plus a 64-character IRN |
| QR code | Not required (dynamic QR applies only to notified B2C cases) | Mandatory signed QR code under Rule 46(r) |
| Signature | Physical or digital signature required | Not required where a valid IRN exists |
| Format | Any template | Prescribed INV-01 schema |
| GSTR-1 population | Manual or software upload | Auto-populated from IRN data |
| E-way bill | Part A keyed in separately | Part A auto-filled from the IRN |
| Cancellation | As per your internal process | 24 hours on the IRP, full cancellation only |
| Amendment | Before filing GSTR-1 | Only through GSTR-1 amendment or a credit or debit note |
| Validity if the mandate is missed | Valid | Not an invoice under Rule 48(5) |
Who must issue e-invoices in FY 2026-27?
E-invoicing applies to every GST-registered business whose aggregate annual turnover (AATO) crossed ₹5 crore in any financial year from FY 2017-18 onwards. The test is historical and PAN-wide: cross the threshold once and the obligation applies to all GSTINs under that PAN, and it does not lapse if turnover later falls.
How to test your own position:
- Compute aggregate turnover as defined in Section 2(6) — taxable, exempt, export and inter-State supplies across all GSTINs on the PAN, excluding taxes
- Check every year since FY 2017-18, not just the last one
- A business that crossed ₹5 crore in FY 2025-26 became covered from 1 April 2026
- Verify your status on the e-invoice portal's enablement search, but remember that enablement is a facility, not a legal determination — the turnover test governs
Notified exclusions continue to apply, including:
- Special Economic Zone units (SEZ developers are covered)
- Insurers, banks, financial institutions and NBFCs
- Goods transport agencies for transport of goods by road
- Passenger transport services and multiplex cinema admissions
- Government departments and local authorities
For registration mechanics and turnover computation, see our GST registration guide.
Which documents and supplies require an IRN?
Only B2B and export-side documents need an IRN. That means tax invoices to registered persons, invoices for exports and supplies to SEZ developers, and the associated credit notes and debit notes. Business-to-consumer invoices, bills of supply, delivery challans and payment vouchers are outside the mandate.
| Document | IRN required? |
|---|---|
| Tax invoice to a registered person (B2B) | Yes |
| Export invoice, with or without payment of IGST | Yes |
| Supply to an SEZ developer | Yes |
| Deemed export invoice | Yes |
| Credit note and debit note under Section 34 | Yes |
| Invoice to an unregistered consumer (B2C) | No |
| Bill of supply for exempt or composition supplies | No |
| Delivery challan, payment voucher, receipt voucher | No |
| Self-invoice for reverse charge purchases from unregistered suppliers | No |
Two practical notes. Reverse-charge supplies made to a registered recipient are reported by the supplier as an e-invoice with the reverse-charge flag set. And even where B2C invoices are outside e-invoicing, notified large taxpayers must still print a dynamic QR code for B2C supplies under the separate Rule 46(r) requirement.
How does the IRP workflow actually run?
Your billing system converts the invoice into the INV-01 JSON schema and sends it to an IRP through a GSP, an API integration or the offline utility. The IRP validates the schema and mandatory fields, checks for duplicates, generates the IRN, digitally signs the payload and returns the signed invoice with a QR code.
The sequence in practice:
- Create the invoice in your ERP or billing software with complete, validated master data
- Generate the JSON in the prescribed schema, including HSN, UQC, place of supply and State codes
- Report to an IRP — the NIC portals and the notified private IRPs all provide the same service, and you may use any of them
- De-duplication check: the IRP rejects a repeat combination of supplier GSTIN, document type, document number and financial year
- Receive the IRN and signed QR code, then print or share the invoice with both on the face of the document
- E-way bill, where required, can be generated in the same call, with Part A auto-populated
- Verify downstream: IRN data flows into GSTR-1 and appears in the buyer's GSTR-2B and IMS dashboard
Access controls have tightened alongside the mandate. Two-factor authentication is now the norm on the e-invoice and e-way bill portals, so build OTP or authenticator app handling into your operating procedure rather than sharing a single login across a team.
What is the 30-day reporting limit, and who does it affect?
Taxpayers with AATO of ₹10 crore and above must report each invoice, credit note and debit note to the IRP within 30 days of the document date, effective from 1 April 2025. After 30 days the portal refuses to generate an IRN. There is no appeal, no late fee and no workaround: the document can never become a valid invoice.
What that means operationally:
- An invoice dated 1 July cannot obtain an IRN after 31 July
- The blocked document cannot support your buyer's ITC, and cannot back an e-way bill
- Recovering the position usually means cancelling the transaction commercially and re-invoicing on a current date, which shifts revenue between periods
- Taxpayers between ₹5 crore and ₹10 crore must still generate e-invoices, but are not subject to the 30-day cap — same-day reporting remains best practice
- Backdated invoicing at year end is the highest-risk pattern, because the 30-day clock and the financial year cut-off interact badly
Treat IRN generation as part of invoice creation, not as a monthly compliance task. Businesses that batch-upload weekly are the ones that discover expired windows during the GSTR-1 run.
Can you cancel or amend an e-invoice?
You can cancel an e-invoice on the IRP within 24 hours of IRN generation, and only if no active e-way bill exists against it. Cancellation is all-or-nothing — the portal does not support partial edits. After 24 hours, the only routes are a credit note or debit note under Section 34, or an amendment while filing GSTR-1.
The correction hierarchy to follow:
- Within 24 hours, error in the document: cancel on the IRP, then report a fresh invoice with a new number. Never reuse the cancelled number
- After 24 hours, value or rate error: issue a credit note or debit note with its own IRN
- After filing, reporting error only: amend the invoice in GSTR-1 for a later period
- Wrong recipient GSTIN: a credit note plus a fresh invoice, since GSTIN cannot be amended on the IRP
Remember that your customer now acts on these documents in the Invoice Management System. A credit note that the recipient does not accept, or accepts without reversing the corresponding credit, creates a mismatch that surfaces at return filing. Our guide to Input Tax Credit rules explains the buyer's side of that process.
What are the consequences of issuing the wrong document?
If a covered taxpayer issues a regular invoice where Rule 48(4) applied, the document is not an invoice under Rule 48(5). The supply is treated as made without an invoice, attracting a penalty of ₹10,000 or the tax evaded, whichever is higher, under Section 122(1), and the buyer's ITC is exposed under Section 16(2)(a).
The knock-on effects extend beyond the penalty:
- Goods in transit can be detained under Section 129 where the accompanying document is invalid
- E-way bill generation fails, stalling dispatch
- Customer disputes and payment holds, because large buyers now validate the IRN and QR code before releasing payment
- Return mismatches, since invoices without IRNs do not auto-populate GSTR-1 and must be added manually, inviting scrutiny
- Repeat defaults can affect your risk profile on the portal and invite departmental verification
Practical recommendations for covered businesses
- Confirm your status against the turnover test, year by year since FY 2017-18, and record the conclusion in writing with the working
- Automate IRN generation at the point of billing so no invoice can be issued without an IRN. Manual portals should be a fallback, not the process
- Clean master data first — GSTINs, HSN and SAC codes, UQC values, State codes and place of supply. Schema rejections are almost always master data failures
- Set an internal same-day reporting rule, with an exception report for any document older than 48 hours
- Build a credit note discipline so post-24-hour corrections never happen through manual invoice edits
- Enable and document two-factor authentication for portal users, with named owners and a backup
- Reconcile three sources monthly — your sales register, the IRN register downloaded from the portal, and GSTR-1
- Brief customers and vendors, because your buyers will ask for the QR code and your covered vendors must give you one before you claim ITC. For format fundamentals, see our GST invoice format guide
References
- e-Invoice Portal — Schema, IRN and enablement — Official INV-01 schema and taxpayer utilities
- CBIC — Notification No. 10/2023-Central Tax — ₹5 crore e-invoicing threshold from 1 August 2023
- CBIC — CGST Rules, 2017, Rule 48 — Manner of issuing invoices and Rule 48(5) validity
- GST Portal — Taxpayer advisories — 30-day IRN reporting limit and portal notices
- ClearTax — E-invoicing under GST — Applicability, exclusions and implementation guidance
- TaxGuru — E-invoice compliance and penalties — Practitioner analysis of common defaults
- NIC — E-way bill and e-invoice system — Integration and two-factor authentication notices
- Taxmann — CGST Act, Sections 31, 34 and 122 — Bare provisions and commentary
Frequently asked questions
- What is the difference between an e-invoice and a regular invoice?
- A regular invoice is generated entirely within your own billing system. An e-invoice is the same document reported to a government Invoice Registration Portal before issue, which returns a unique Invoice Reference Number and a digitally signed QR code. Under Rule 48(5) of the CGST Rules, a covered taxpayer who issues an invoice without an IRN has not issued a valid invoice at all.
- Who must generate e-invoices in FY 2026-27?
- Any GST-registered business whose aggregate annual turnover crossed ₹5 crore in any financial year from FY 2017-18 onwards must generate e-invoices for B2B supplies, exports and SEZ supplies. The test is historical and PAN-wide, so the obligation continues even if turnover later falls below ₹5 crore. B2C invoices are outside the mandate.
- Can an e-invoice be cancelled or amended after the IRN is generated?
- An e-invoice can be cancelled in full on the Invoice Registration Portal within 24 hours of IRN generation, and only if no e-way bill is active against it. Partial amendment on the portal is not possible. After 24 hours you must correct the position through a credit note, a debit note, or an amendment while filing GSTR-1.
- What happens if a covered taxpayer issues a regular invoice instead of an e-invoice?
- The document is not treated as a valid invoice under Rule 48(5). The buyer cannot claim Input Tax Credit because Section 16(2)(a) requires a valid tax invoice, an e-way bill cannot be generated against it, and a penalty of ₹10,000 or the tax evaded, whichever is higher, can apply under Section 122(1).