GST E-Invoicing is the mandatory system of reporting specified invoices to a designated Invoice Registration Portal (IRP) in a standardised JSON format to obtain a unique Invoice Reference Number (IRN) along with a digitally-signed QR code — governed by Rule 48(4) of the CGST Rules, 2017 read with Notifications issued by CBIC from time to time, and operating under the Schema INV-01 prescribed by GSTN. An e-invoice is not an invoice generated on the government portal; it is an invoice generated in the taxpayer's own accounting / ERP system that is then validated and registered on an IRP (such as einvoice1.gst.gov.in, einvoice2, and additional IRPs rolled out by CBIC) and returned with IRN, QR code, and signed JSON. A right e-invoicing software is therefore not a nice-to-have but a mission-critical component of the taxpayer's billing workflow — directly affecting invoice validity, GSTR-1 auto-population, E-Way Bill generation, buyer's ITC, and exposure to penalty under Rule 48(5) and Section 122.
Robust GST E-Invoicing Software must handle a wide range of responsibilities — applicability monitoring across the turnover threshold as notified from time to time (currently Rs. 5 crore and above, subject to CBIC updates), schema-compliant JSON creation for B2B invoices, exports, SEZ supplies, credit and debit notes, real-time IRN generation via IRP API with multiple-IRP failover, QR code embedding on invoice PDFs, cancellation within the permitted 24-hour window, 30-day reporting discipline for notified taxpayer classes, downstream feeds to GSTR-1, E-Way Bill portal, ERP / accounting system, and buyer systems, plus deep reconciliation between IRP, GSTR-1, GSTR-2B (on the buyer side), and books. The right software converts what would otherwise be a painful compliance burden into a clean, auditable, exception-driven process.
Our "GST E-Invoicing Software" offering combines a powerful IRP-integrated platform with end-to-end accountant-led support — from applicability assessment, ERP / accounting system integration, IRP registration and master data setup, bulk & API-based IRN generation, QR code embedding, E-Way Bill auto-generation, multi-GSTIN rollout, reconciliation with GSTR-1 and books, and handling of exceptions, cancellations, and error codes — so that every e-invoice is generated correctly, on time, and with a full audit trail that stands up to departmental scrutiny.
Rs. 5 Cr+
Current applicability threshold
64-Digit IRN
Unique hash & QR code
24 Hours
IRN cancellation window
30-Day Rule
Reporting limit (notified)
Laws & Frameworks We Work Under
CGST Rules – Rule 48(4)
CGST Rules – Rule 48(5)
CGST Act – Sec 31 / 34
CGST Act – Sec 122
Schema INV-01
IRP APIs (NIC / GSTN)
CBIC E-Invoicing Notifications
GSTR-1 / E-Way Bill Linkage
FAQs on GST E-Invoicing Software
What is GST e-invoicing and who is required to comply?
GST e-invoicing is the process of reporting specified invoices to a designated Invoice Registration Portal (IRP) in a standardised JSON format (Schema INV-01), and receiving back a unique Invoice Reference Number (IRN) and a digitally-signed QR code that must be printed on the invoice. It is governed by Rule 48(4) of the CGST Rules. E-invoicing applies to registered persons whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds the threshold notified by CBIC — currently Rs. 5 crore (subject to CBIC amendments) — for B2B invoices, exports, SEZ supplies with or without payment, credit notes, and debit notes. Exempt entities such as banks / insurers / GTAs / passenger transport / multiplex admission have been notified as being outside the scope under current rules; applicability should always be confirmed against the latest CBIC notifications.
Do I need separate software or can I generate e-invoices directly on the government portal?
The government provides a free offline utility and a web interface on the NIC-IRP portal which can be used to generate e-invoices manually one at a time or through a basic Excel upload. This works for very low-volume taxpayers — perhaps 5 to 10 invoices a day. For any meaningful volume, dedicated e-invoicing software integrated with the taxpayer's ERP or billing system is strongly recommended because it eliminates duplicate data entry, enforces schema validation before submission, handles exceptions and cancellations systematically, auto-generates E-Way Bills alongside IRN, and creates clean audit trails. The cost of dedicated software is typically dwarfed by the cost of manual errors, IRN mismatches with GSTR-1, and downstream disputes with buyers over ITC eligibility.
Can an IRN be cancelled or modified once generated?
An IRN can be cancelled on the IRP within 24 hours of its generation, provided no E-Way Bill linked to it has been generated and acted upon. Once cancelled, the same invoice number cannot be reused for a fresh IRN — a new invoice number has to be used. After 24 hours, the IRN cannot be cancelled on the IRP itself; any correction must flow through a credit note or debit note, which is itself reported to the IRP and linked to the original IRN. An IRN is never modifiable — field-level corrections require cancellation and fresh generation (within 24 hours) or credit / debit note treatment (after 24 hours). Good e-invoicing software captures this workflow with guardrails and an audit trail.
What is the 30-day reporting rule and does it apply to everyone?
CBIC has, through advisories on the GSTN portal, introduced a reporting time limit on the IRP for notified taxpayer classes — currently taxpayers with aggregate turnover above a higher threshold (periodically revised). Under this rule, invoices cannot be reported to the IRP beyond a specified number of days (commonly 30 days) from the date of invoice. The exact threshold and day limit are subject to change through periodic advisories, so the latest notification must always be referred to. For taxpayers outside this category, there is no hard cut-off on the IRP, but reporting should still be done contemporaneously to ensure GSTR-1 auto-population, E-Way Bill generation, and clean reconciliation. Good software enforces internal cut-offs well before the statutory limit.
How does e-invoicing connect with GSTR-1 and E-Way Bills?
Once an IRN is generated, the IRP shares the invoice data with the GSTN and E-Way Bill systems. For GSTR-1, the reported B2B invoices, credit and debit notes auto-populate the relevant tables — the taxpayer can then review, edit if necessary, and file GSTR-1. For E-Way Bills, Part A of the E-Way Bill is pre-filled from the IRN data, and the taxpayer needs only to add Part B transport details (vehicle number, transporter ID, mode) to complete generation. This integration is one of the strongest commercial arguments for integrated e-invoicing software — data entered once at IRN generation flows into both GSTR-1 and the E-Way Bill system without re-keying, eliminating the single biggest source of downstream mismatches.
What happens if an invoice that required e-invoicing does not have an IRN?
Under Rule 48(5) of the CGST Rules, where a registered person is required to issue an invoice under Rule 48(4) but does so without an IRN, that invoice is not to be treated as a valid invoice. The downstream consequences are severe — the buyer may be denied ITC on the basis that the document is not a tax invoice, and the supplier may face penalty under Section 122(1)(i) for issuing an incorrect or non-compliant invoice. Beyond the legal consequences, commercial friction is real — sophisticated buyers routinely reject invoices without valid IRN and QR code, and in many cases refuse payment until IRN is provided. Disciplined e-invoicing, therefore, is not just a compliance requirement; it is a precondition for smooth working-capital management.
Is e-invoicing applicable to B2C invoices and exports?
E-invoicing under the current framework is applicable to B2B tax invoices, exports, SEZ supplies (with and without payment of tax), deemed exports, and credit / debit notes issued under Section 34 against such invoices. B2C invoices (supplies to unregistered consumers) are currently outside the mandatory IRN requirement, though covered taxpayers are required to print a dynamic QR code on B2C invoices under a separate notification. Exports, whether with payment of IGST or under LUT, are squarely covered — the IRN is actually used in downstream refund claims and shipping-bill validation on ICEGATE. Good e-invoicing software supports all these document types natively, with schema validation tuned to each.
How does e-invoicing software help with audit and reconciliation?
Robust e-invoicing software does three things that are invaluable during audits and scrutiny. First, it maintains an immutable audit trail of every IRN generated, cancelled, or failed — with timestamps, user identity, error codes, and system response payloads. Second, it provides reconciliation dashboards that reconcile IRN data with GSTR-1 (ensuring every B2B invoice reported in GSTR-1 has a matching IRN), with E-Way Bills (ensuring IRN and EWB align where goods are moved), and with the books of account (ensuring revenue booked equals revenue reported). Third, it provides on-demand reports that can be handed over to departmental auditors during ADT-01 / ADT-02 proceedings, or used to respond to DRC-01B / 01C intimations. Clean e-invoicing infrastructure dramatically reduces audit friction and defendability.