Quick Answer: What Is an E-Invoice?
An e-invoice under GST is not simply a PDF generated by accounting software. For notified taxpayers and notified documents, specified invoice data is reported to an Invoice Registration Portal (IRP), which validates the data and generates an Invoice Reference Number (IRN) and digitally signed QR code.
Core rule: Generate the IRN before using the document as a compliant e-invoice where e-invoicing applies. The IRP's role is to register/report the invoice data; it does not replace the supplier's responsibility to issue the underlying tax invoice.
30-day rule: From 1 April 2025, taxpayers with AATO of ₹10 crore and above must report invoices, credit notes and debit notes within 30 days from the document date; the IRP can reject reporting beyond the permitted window. citeturn0search0turn0search10
Do not assume: “invoice created in ERP” means “e-invoice completed.” Your control should verify IRN, Ack No., Ack Date and signed QR/IRN status.
1. Legal Framework
| Provision / system | Why it matters |
|---|---|
| CGST Act, Section 31 | Tax invoice and timing of invoice issuance. |
| CGST Rules, Rule 48(4) | E-invoice requirement for notified classes of taxpayers/documents. |
| CGST Rules, Rule 48(5) | Invoice issued in the prescribed manner; an invoice covered by Rule 48(4) without required IRN is not treated as valid for the statutory purpose. |
| IRP | Portal for reporting invoice data and obtaining IRN/QR. |
| GSTR-1 | E-invoice data is used for auto-population and reconciliation. |
| E-way bill system | Transport details can be generated/linked from e-invoice data where applicable. |
Practical distinction: Tax invoice, e-invoice, IRN, QR code and e-way bill are connected but are not the same thing. A finance team should track each separately.
2. Who Needs E-Invoicing?
E-invoicing applies to specified registered persons based on the notified aggregate annual turnover threshold and specified supplies/documents. The exact applicability should be checked for the relevant financial year and notification because the threshold and exclusions have changed over time.
B2B taxable invoices
Commonly covered when the supplier falls within the notified e-invoice framework.
Commonly covered when the supplier falls within the notified e-invoice framework.
Credit notes / debit notes
Specified documents can also be subject to IRN reporting.
Specified documents can also be subject to IRN reporting.
Exports
Export invoices are within the e-invoice framework where the supplier/document is covered.
Export invoices are within the e-invoice framework where the supplier/document is covered.
SEZ supplies
Analyse whether the transaction and supplier fall within the notified requirements.
Analyse whether the transaction and supplier fall within the notified requirements.
B2C
Do not automatically treat all B2C invoices as e-invoices merely because the supplier has an e-invoice registration.
Do not automatically treat all B2C invoices as e-invoices merely because the supplier has an e-invoice registration.
Exempt / non-taxable
Check whether the document is a tax invoice/document covered by the notification.
Check whether the document is a tax invoice/document covered by the notification.
Threshold control: AATO should be assessed using the applicable GST definition and relevant PAN-level turnover data. Do not decide applicability from the turnover of only one GSTIN without checking the prescribed methodology.
3. Complete E-Invoice Workflow
1. Create tax invoice2. Validate master data3. Send JSON/API/file to IRP4. IRP validates5. IRN generated6. Signed QR generated7. Store response8. Update ERP9. GSTR-1 reconcile
What should the ERP receive back?
| Field | Purpose |
|---|---|
| IRN | Unique Invoice Reference Number for the registered document. |
| Acknowledgement Number | IRP acknowledgement reference. |
| Acknowledgement Date | Time/date of successful registration. |
| Signed QR code | Machine-readable signed information used for verification. |
| Signed invoice / response | Evidence that should be retained with the invoice record. |
Best ERP control: Do not mark an invoice “E-Invoice Completed” merely because the API call succeeded. Mark it completed only after the IRP response contains a valid IRN and acknowledgement data.
4. Invoice Data & IRN – What Must Be Correct?
The IRP validates structured invoice data. Errors in GSTIN, document number, document date, supply type, place of supply, HSN, tax rate, taxable value or tax amounts can cause rejection or create downstream reconciliation problems.
| Data area | Practical check |
|---|---|
| Supplier GSTIN | Correct legal GST registration and state. |
| Recipient GSTIN | Validate GSTIN before posting. |
| Document number | Must match the ERP tax invoice and prescribed numbering controls. |
| Document date | Must match the issued invoice and is critical for reporting-window controls. |
| Document type | Invoice / credit note / debit note as applicable. |
| Supply type | Domestic, export, SEZ or other applicable category. |
| Place of supply | Critical for IGST vs CGST/SGST and GSTR-1 reporting. |
| HSN/SAC | Correct classification and applicable rate. |
| Taxable value | Should agree with accounting invoice. |
| Tax amount | CGST/SGST/IGST must reconcile to ERP calculation. |
5. QR Code – What Does It Prove?
The signed QR code is generated from the IRP response and is intended to provide a quick verification mechanism for key e-invoice information. It should not be treated as a substitute for checking the complete invoice.
IRN
Unique reference generated after successful registration.
Unique reference generated after successful registration.
QR
Signed information that can be scanned/verified.
Signed information that can be scanned/verified.
Invoice
Underlying tax invoice issued by the supplier.
Underlying tax invoice issued by the supplier.
Practical check: Before releasing an invoice to a customer, confirm that the printed/PDF invoice contains the required IRN/QR information and that the QR relates to the same invoice number, GSTIN, date and values.
6. 30-Day E-Invoice Reporting Rule
Effective 1 April 2025, taxpayers with aggregate annual turnover of ₹10 crore and above are required to report e-invoices within 30 days from the invoice date. The restriction covers invoices, credit notes and debit notes. If the document is older than the permitted period, the IRP can reject IRN generation. citeturn0search0turn0search10
| Invoice date | Last reporting date – practical example |
|---|---|
| 1 April 2025 | 30 April 2025 |
| 15 April 2025 | 15 May 2025 |
| 31 August 2026 | 30 September 2026 |
ERP implication: A system should not allow an old invoice to sit in “Pending IRN” indefinitely. Create an ageing report showing document date, days outstanding, applicability and last permissible reporting date.
Recommended dashboard
0–7 days8–15 days16–25 days26–29 days30-day breach risk
7. E-Invoice Errors & Corrections
The most important principle is to distinguish correction before IRN from correction after IRN.
| Situation | Practical action |
|---|---|
| ERP invoice wrong before IRN | Correct ERP data and submit the correct document. |
| IRP rejects request | Read validation error, correct the source data and resubmit. |
| IRN generated with wrong value | Follow the permitted cancellation/reissue route; do not simply edit the PDF. |
| Wrong GSTIN after IRN | Generally cannot be edited on the IRP; use cancellation/reissue where legally permitted. |
| Wrong HSN after IRN | Cannot be treated as an ordinary ERP edit; follow applicable cancellation/correction process. |
| Wrong document number | Do not create a second invoice with the same number expecting the old IRN to change. |
| GSTR-1 discrepancy | Reconcile IRP data with GSTR-1 and use the available GST return amendment mechanisms where permitted. |
Never do this: edit the PDF invoice after IRN generation and assume the government system has been amended. The IRP record remains based on the registered data.
8. Cancellation – What Happens After IRN?
An e-invoice that has already received an IRN cannot be freely edited. Where cancellation is permitted, the cancellation must be processed through the prescribed IRP mechanism within the applicable time window. A fresh invoice may then need to be issued with a new document number/date as appropriate.
Wrong amount
Do not overwrite the existing IRN. Evaluate cancellation and reissue.
Do not overwrite the existing IRN. Evaluate cancellation and reissue.
Wrong customer GSTIN
High-risk master-data error; use the prescribed cancellation/reissue route.
High-risk master-data error; use the prescribed cancellation/reissue route.
Supply cancelled
Cancel the e-invoice if eligible and also align accounting, e-way bill and GSTR-1 records.
Cancel the e-invoice if eligible and also align accounting, e-way bill and GSTR-1 records.
Invoice already reported
Reconcile the cancellation with return data and customer communication.
Reconcile the cancellation with return data and customer communication.
Important: Cancellation of an e-invoice and cancellation/adjustment of a GST return entry are related but not necessarily the same action. Always reconcile all systems.
9. E-Invoice and GSTR-1 / GSTR-1A
E-invoice data reported to the IRP is used for GST return auto-population. GSTN guidance states that taxpayers should review the auto-populated data and add other supplies not already auto-populated. citeturn0search24
ERP invoiceIRPIRNGSTN data flowGSTR-1 tablesGSTR-1A where applicableGSTR-3B
| Reconciliation | What to compare |
|---|---|
| ERP vs IRP | Invoice number, date, GSTIN, taxable value, tax and document type. |
| IRP vs GSTR-1 | Confirm auto-populated records and identify omissions/duplicates. |
| GSTR-1 vs GSTR-3B | Taxable turnover and output tax by tax head. |
| Credit/debit notes | Document number, original invoice reference, values and tax. |
10. E-Invoice and E-Way Bill
E-invoice and e-way bill serve different compliance purposes. An e-invoice registers the invoice/document; an e-way bill relates to movement of goods. Where system integration is available, transport information can be generated using e-invoice data.
Key point: Having an IRN does not automatically mean every transportation requirement has been satisfied. Check whether an e-way bill is required for the movement and whether vehicle/transport details are complete.
| Check | Question |
|---|---|
| IRN | Was invoice successfully registered? |
| Transport | Is movement of goods taking place? |
| E-way bill | Is e-way bill required for this movement? |
| Part B | Are vehicle/transport details complete where required? |
| Cancellation | Do e-invoice and e-way bill records remain aligned? |
11. Exports, SEZ, RCM & Special Transactions
Exports
Export invoice data can fall within e-invoice reporting where the supplier/document is covered. Validate export type, recipient details and port/code information.
Export invoice data can fall within e-invoice reporting where the supplier/document is covered. Validate export type, recipient details and port/code information.
SEZ supplies
Correctly identify SEZ status and supply type in the invoice data.
Correctly identify SEZ status and supply type in the invoice data.
RCM
RCM transactions require careful distinction between supplier-issued documents, recipient self-invoice/document requirements and e-invoice applicability.
RCM transactions require careful distinction between supplier-issued documents, recipient self-invoice/document requirements and e-invoice applicability.
Job work
Determine whether the document is a taxable invoice or another prescribed document and apply the applicable e-invoice rule.
Determine whether the document is a taxable invoice or another prescribed document and apply the applicable e-invoice rule.
Distinct persons
Inter-GSTIN supplies can require e-invoice reporting when covered; validate supplier/recipient GSTIN and place of supply.
Inter-GSTIN supplies can require e-invoice reporting when covered; validate supplier/recipient GSTIN and place of supply.
Credit notes
Covered credit notes should be reported within the applicable reporting window.
Covered credit notes should be reported within the applicable reporting window.
12. Construction, EPC, Mining & Large Project Contracts
| Scenario | E-invoice control |
|---|---|
| Monthly RA bill | Generate tax invoice/IRN according to statutory invoice timing and contract certification workflow. |
| Government project | Do not wait for department payment if invoice is required and e-invoice rules apply. |
| Mobilisation advance invoice | Determine whether a taxable invoice/document is required and whether it falls within the e-invoice framework. |
| Variation order | When additional taxable consideration is invoiced, ensure document and IRN data match the approved commercial record. |
| Retention release | Check whether a separate invoice/debit/credit document is required and report it correctly. |
| Subcontractor invoice | Validate subcontractor's GSTIN, IRN and invoice data before recording ITC. |
| Multiple project GSTINs | Do not mix IRNs between GST registrations; GSTIN is a critical key in reconciliation. |
13. 40 Practical E-Invoice Cases
| # | Case | Practical treatment |
|---|---|---|
| 1 | Invoice created in ERP but IRN pending | Keep in pending queue; invoice is not “completed” for e-invoice control until successful registration. |
| 2 | IRN generated successfully | Store IRN, acknowledgement data and signed QR response. |
| 3 | Wrong customer GSTIN before IRN | Correct ERP master/invoice and submit correct data. |
| 4 | Wrong GSTIN after IRN | Use permitted cancellation/reissue route rather than editing the PDF. |
| 5 | Wrong tax rate before IRN | Correct invoice and submit again. |
| 6 | Wrong tax rate after IRN | Evaluate cancellation/reissue and return impact. |
| 7 | Duplicate invoice submitted | Investigate duplicate validation/IRN and do not create uncontrolled duplicates. |
| 8 | Invoice number typo | Correct through the applicable process; do not assume IRN can be edited. |
| 9 | Credit note generated after original invoice | Report the credit note if covered and retain reference/reconciliation. |
| 10 | Debit note issued | Check document date and applicable reporting window. |
| 11 | Invoice 31 days old for AATO ₹10 Cr+ | IRP reporting restriction can prevent IRN generation. |
| 12 | Invoice 29 days old | Prioritise immediately; do not wait for day 30. |
| 13 | April 1 invoice | For covered ₹10 Cr+ taxpayers, report within 30 days under current restriction. |
| 14 | Export invoice | Validate export supply type and required invoice data. |
| 15 | SEZ invoice | Validate SEZ classification and recipient data. |
| 16 | Government contract invoice | Do not postpone IRN merely because payment is delayed. |
| 17 | Construction RA bill | Link certification, invoice date, IRN and accounting period. |
| 18 | Mining contractor invoice | Reconcile measurement, invoice and IRN data. |
| 19 | Inter-GSTIN transfer | Check whether taxable supply and e-invoice requirement apply. |
| 20 | Wrong place of supply | Correct before IRN; after IRN follow permitted correction process. |
| 21 | Wrong HSN | Do not edit only the PDF after IRN. |
| 22 | Wrong invoice date | High-risk error because it can affect reporting deadlines and returns. |
| 23 | GSTR-1 differs from IRP | Reconcile auto-populated data and return amendments available under current system. |
| 24 | IRP successful but ERP failed to update | Use IRP acknowledgement/IRN retrieval to update ERP rather than generating a second invoice. |
| 25 | API timeout after submission | Check IRP status before resubmitting to avoid duplicates. |
| 26 | Customer says QR does not scan | Verify print/PDF quality and compare QR data to IRP record. |
| 27 | Invoice cancelled commercially | Align e-invoice, accounting, e-way bill and GSTR-1 records. |
| 28 | Partial supply | Ensure each invoice/document reflects the actual taxable transaction and applicable e-invoice rule. |
| 29 | Annual AMC | Map invoice/document timing to the service arrangement and e-invoice applicability. |
| 30 | SaaS invoice | Validate recipient GSTIN, SAC, POS and tax calculation. |
| 31 | Imported service | Analyse RCM/document requirements separately; do not assume supplier's foreign invoice automatically becomes an Indian e-invoice. |
| 32 | RCM purchase from domestic supplier | Check applicable self-invoice/document and e-invoice rules rather than copying normal B2B workflow. |
| 33 | Credit note older than 30 days | For covered ₹10 Cr+ taxpayers, apply the reporting restriction from the credit-note document date. |
| 34 | Debit note older than 30 days | Same reporting-window control applies where covered. |
| 35 | Year-end invoice held for approval | Approval workflow should not create uncontrolled e-invoice delay. |
| 36 | Invoice generated on holiday | Use the document date and applicable reporting rule; do not rely on working-day assumptions unless the specific rule provides them. |
| 37 | Multiple branches using one ERP | Use GSTIN + document number as core reconciliation keys. |
| 38 | Supplier sends PDF without IRN | For a covered supplier/document, verify IRN before accepting it as compliant e-invoice. |
| 39 | IRN present but values differ from PDF | Treat as a high-risk mismatch; reconcile IRP response to the issued invoice and take corrective action. |
| 40 | Invoice approaching 30-day limit | Escalate through daily dashboard and obtain IRN immediately where applicable. |
14. ERP, Accounting & Reconciliation Controls
Control 1 – IRN status
Pending / Generated / Rejected / Cancelled.
Pending / Generated / Rejected / Cancelled.
Control 2 – Ageing
Days from document date to current date.
Days from document date to current date.
Control 3 – Duplicate check
GSTIN + document type + document number + FY.
GSTIN + document type + document number + FY.
Control 4 – Value check
Taxable value and tax amounts ERP vs IRP.
Taxable value and tax amounts ERP vs IRP.
Control 5 – Return check
IRP vs GSTR-1 vs GSTR-3B.
IRP vs GSTR-1 vs GSTR-3B.
Control 6 – Cancellation check
IRN cancellation vs accounting reversal.
IRN cancellation vs accounting reversal.
Recommended reconciliation key
Supplier GSTIN + recipient GSTIN + document type + document number + document date + financial year should be used as a strong matching key, with IRN retained as the government-registration reference.
15. E-Invoice Audit Checklist
| Audit question | Evidence |
|---|---|
| Is taxpayer within e-invoice applicability? | AATO/PAN-level working and GST registration data. |
| Are all covered invoices reported? | ERP-to-IRP reconciliation. |
| Are invoices within 30 days for ₹10 Cr+ taxpayers? | Ageing report and IRP status. |
| Are credit/debit notes reported? | CN/DN register vs IRP. |
| Are cancelled IRNs accounted for? | IRP cancellation report + ledger. |
| Do GSTR-1 values agree? | IRP/GSTR-1 reconciliation. |
| Do e-way bills agree? | Transport report and e-way bill data. |
| Are wrong GSTIN/POS cases controlled? | Exception report. |
| Are API failures monitored? | Integration logs. |
| Is signed QR retained? | Invoice archive. |
16. 15 Common E-Invoice Mistakes
1. Treating PDF as the e-invoice IRN registration is the critical additional step.
2. Delaying IRN generation Especially risky for covered ₹10 Cr+ taxpayers.
3. Wrong GSTIN Creates customer and ITC problems.
4. Wrong POS Can change tax head.
5. Wrong HSN/SAC Creates classification and return issues.
6. Editing PDF after IRN Does not change IRP data.
7. Duplicate API submission Check status after timeout.
8. No IRP-to-ERP sync Successful IRN may remain missing in books.
9. Ignoring credit/debit notes They may have their own reporting deadline.
10. Assuming IRN = e-way bill Separate movement compliance may apply.
11. Not reconciling GSTR-1 Auto-population still requires review.
12. Using wrong document date Can affect the 30-day reporting window.
13. Mixing GSTINs Particularly common in multi-project companies.
14. Ignoring export/SEZ flags Supply type affects reporting.
15. No exception dashboard Pending/rejected IRNs can remain unnoticed.
17. E-Invoice Decision Matrix
| Question | Decision |
|---|---|
| Is supplier within notified e-invoice applicability? | Yes → continue with document-level applicability check. |
| Is document a covered invoice/CN/DN? | Yes → report to IRP as applicable. |
| Is invoice date older than 30 days for AATO ₹10 Cr+? | IRP restriction may prevent generation; escalate immediately. |
| Is IRN generated? | No → invoice workflow remains incomplete for e-invoice control. |
| Is data wrong before IRN? | Correct ERP and submit again. |
| Is data wrong after IRN? | Use applicable cancellation/reissue/correction route; do not edit PDF alone. |
| Does goods movement occur? | Check separate e-way bill requirement. |
| Does GSTR-1 differ? | Reconcile IRP auto-population and return data. |
18. Month-End E-Invoice Checklist
| Control | Status |
|---|---|
| Applicability/AATO reviewed | ☐ |
| All covered invoices have IRN | ☐ |
| 30-day ageing report reviewed | ☐ |
| Credit notes/debit notes checked | ☐ |
| Rejected IRNs cleared | ☐ |
| IRP vs ERP reconciliation completed | ☐ |
| IRP vs GSTR-1 reconciliation completed | ☐ |
| GSTR-1 vs GSTR-3B reconciled | ☐ |
| E-way bill exceptions reviewed | ☐ |
| Cancelled IRNs reconciled | ☐ |
| QR/IRN retained with invoice archive | ☐ |
19. Frequently Asked Questions
Is e-invoice the same as an invoice?
No. The tax invoice is the commercial/tax document; e-invoicing is the prescribed electronic reporting/registration mechanism for covered taxpayers and documents.
What is IRN?
IRN means Invoice Reference Number generated after successful registration of the covered invoice/document on the IRP.
What is the current 30-day e-invoice rule?
From 1 April 2025, taxpayers with AATO ₹10 crore and above must report covered invoices, credit notes and debit notes within 30 days from document date. citeturn0search0turn0search10
Can an e-invoice be edited after IRN?
The IRP record is not an editable PDF. Errors generally require the permitted cancellation/reissue or return-correction mechanism.
Does IRN automatically create an e-way bill?
It can integrate with e-way bill generation where applicable, but IRN and e-way bill are separate compliance records.
Does e-invoice automatically mean GSTR-1 is correct?
No. E-invoice data is used for auto-population, but taxpayers should review and reconcile the return data. citeturn0search24
What if the API times out?
Check whether IRN was generated before resubmitting. Blindly sending the same invoice again can create duplicate-processing problems.
Should IRN be stored permanently?
The business should retain the invoice and supporting e-invoice response/records in accordance with applicable record-retention requirements and its audit controls.
Key Takeaway
GST E-Invoice Reference Map
Rule 48(4)
E-invoice requirement for notified persons/documents.
E-invoice requirement for notified persons/documents.
Rule 48(5)
Consequences relating to invoices covered by Rule 48(4).
Consequences relating to invoices covered by Rule 48(4).
Section 31
Tax invoice framework.
Tax invoice framework.
IRN
Invoice Reference Number generated by IRP.
Invoice Reference Number generated by IRP.
Signed QR
IRP-generated signed verification data.
IRP-generated signed verification data.
30-Day Rule
AATO ₹10 Cr+ reporting restriction from 1 April 2025.
AATO ₹10 Cr+ reporting restriction from 1 April 2025.
GSTR-1
Review auto-populated e-invoice details.
Review auto-populated e-invoice details.
E-Way Bill
Separate goods-movement compliance.
Separate goods-movement compliance.
ERP Controls
IRN status, ageing and reconciliation.
IRN status, ageing and reconciliation.