Mon–Sat: 9:00 AM – 6:00 PM Support
GST E-Invoicing
GST E-Invoicing Registration
Fast Processing

GST E-Invoicing

Overview

What is a GST E-Invoicing?

GST e-invoicing is a digital validation framework under which specified categories of B2B and export invoices must be electronically reported to, and authenticated by, a government-notified Invoice Registration Portal (IRP) before they can be validly issued to the recipient.

Guide to GST e-Invoicing

Core Framework, Technical Specifications, Implementation Architecture, and Compliance Rules

1. Introduction

GST e-invoicing is a digital validation framework under which specified categories of B2B and export invoices must be electronically reported to, and authenticated by, a government-notified Invoice Registration Portal (IRP) before they can be validly issued to the recipient.

Introduced in a phased manner from 1 October 2020 for the largest taxpayers and progressively extended to smaller businesses, e-invoicing is governed by Rule 48(4) of the CGST Rules, 2017. Under this mandate, covered taxpayers report structural invoice data to the IRP, which validates the payload and returns a unique 64-character Invoice Reference Number (IRN) along with a digitally signed cryptographic QR code.

An invoice issued by a taxpayer covered under these provisions is not treated as a valid tax invoice under GST unless it carries this IRN and QR code. Issuing a covered invoice without a valid IRN renders the document completely invalid, severe penalties apply, and it jeopardises the recipient's ability to claim input tax credit on that supply.

2. Salient Features

Applicability Based on PAN-Level Turnover As of 2026, e-invoicing is mandatory for any registered person whose aggregate annual turnover (computed globally across all active state-level GSTINs held under the same PAN) exceeded ₹5 Crore in any financial year from FY 2017-18 onwards. Once this threshold has been crossed even once, e-invoicing remains applicable in all subsequent years, even if turnover later drops.
Covers B2B and Export Transactions E-invoicing applies strictly to Business-to-Business (B2B) supplies, Business-to-Government (B2G) transactions, supplies routed into Special Economic Zones (SEZ), and direct export operations. It natively covers commercial tax invoices, credit notes, and debit notes. Routine Business-to-Consumer (B2C) retail bills bypass the IRP engine.
Standardised Schema (GST INV-01) Every e-invoice must conform strictly to the standard format schema layout (Form GST INV-01). This structural standardization ensures data interoperability, allowing files generated by any billing software or ERP to be easily parsed and matched by the GST common network.
Multi-Portal Infrastructure To balance system loads, ensure continuous availability, and reduce latency, the government provides multiple authorized Invoice Registration Portals (IRPs) run by NIC along with private e-way bill/e-invoice service providers, ensuring stable, real-time automated data processing.
GSTR-1 Integration and E-Way Bill Auto-Population Once authenticated by the IRP, invoice data automatically flows into the supplier's draft Form GSTR-1 return. For physical goods movement, the same data auto-populates Part-A of the E-Way Bill workspace, dramatically eliminating duplicate data entry and administrative overhead.

Notified Sectoral Exemptions

Certain sectors remain exempt from the mandatory e-invoicing framework under Rule 48(4), regardless of their aggregate annual turnover:

  • Insurers, banking companies, financial institutions, and non-banking financial companies (NBFCs).
  • Goods Transport Agencies (GTA) transporting goods by road.
  • Suppliers providing passenger transportation services.
  • Suppliers providing services by way of admission to exhibition of cinematograph films in multiplex screens.

3. Data Fields and Schema Inputs Required

Filing or pushing an invoice to the IRP depends on structural accounting elements aligned to the system validation engines.

Category Mandatory Structural Elements
3.1 Supplier & Recipient Profiles • Supplier valid GSTIN profile, legal name, and physical office location pincode.
• Recipient valid GSTIN profile, commercial legal name, billing destination, and delivery address.
• Explicit State Code mapping to determine appropriate tax treatment (CGST/SGST vs. IGST).
3.2 Invoice Metadata • Explicit Document Type code (INV for Invoice, CRN for Credit Note, DBN for Debit Note).
• Unique, sequential alphanumeric invoice number matching the syntax rules of the GST portal.
• Strict invoice issuance date string.
3.3 Line Item Architecture • Description of goods/services alongside mandatory HSN codes (harmonized systemic structure).
• Quantities, per-item units of measure, base prices, discounts, and taxable value totals.
• Applicable GST tax slabs (0%, 5%, 12%, 18%, 28%) and exact matching figures for CGST, SGST, IGST, or Cess.
3.4 Transport Identifiers
(Optional for e-invoice; required for e-way bill)
• Distance in kilometers (verified by portal auto-distance checker).
• Transporter ID or specific vehicle registration string for active road delivery tracking.
• Transport document references (Bill of Lading, Railway Receipt, or Airway Bill numbers).

4. The E-Invoicing Generation and Validation Lifecycle

Step 1: Invoice Generation within Internal ERP

The taxpayer creates the standard billing record in their business ERP or accounting software. The application validates that all fields match the official JSON schema layout (Form GST INV-01).

Step 2: Uploading the JSON Payload to the IRP

The ERP system communicates with the Invoice Registration Portal (IRP)—either directly via secure API nodes, through a GSP connector, or via bulk offline JSON upload tools—to pass the invoice data.

Step 3: Verification and IRN/QR Cryptographic Generation

The IRP runs deduplication algorithms to check for duplicate entries. It creates the unique 64-character IRN hash using the SHA-256 algorithm (built from Supplier GSTIN + Invoice Number + Financial Year), signs the invoice payload with the IRP’s private key, and generates a dynamic QR code.

Step 4: System Data Sync and ERP Printing

The IRP passes the signed JSON data back to the taxpayer's ERP system. The ERP reads this data and automatically prints the secure QR code and IRN directly onto the physical invoice document sent to the customer. Concurrently, the portal shares this validated record with the core GST portal to update the supplier's GSTR-1 and the recipient's GSTR-2B log files.

Operational Timelines and Restrictions 24-Hour Cancellation Limit: An active IRN can be cancelled on the IRP dashboard within 24 hours of generation, provided no valid E-Way bill is linked to it. Partial data modifications are blocked. Beyond 24 hours, updates must be handled manually via Form GSTR-1.
Reporting Deadlines: Taxpayers with turnovers touching or exceeding ₹10 Crore must upload documents to the IRP within exactly 30 days of the printed invoice date. Late attempts are rejected by the validation rules.

5. Frequently Asked Questions (FAQs)

Collapsible FAQs (or accordions) let visitors browse questions and click to expand answers, keeping pages uncluttered

Does e-invoicing completely replace the need to file GSTR-1? +
No, it does not replace GSTR-1, but it simplifies it significantly. Validated e-invoice data automatically populates the supplier's draft GSTR-1 tables. However, the taxpayer must still log into the portal, review the pre-populated figures, add any non-e-invoiced lines (such as B2C sales), and file the return manually in the usual manner.
Can a business below the ₹5 Crore threshold use e-invoicing voluntarily? +
Yes. Businesses whose aggregate annual turnover falls below the mandatory limit can choose to enable and use the e-invoicing framework voluntarily on the portal. However, once enabled, they must follow all standard schema validation rules and compliance guidelines for their B2B transactions.
Does generating an e-invoice also create the corresponding E-Way Bill automatically? +
Where the supply involves the physical movement of goods, Part A of the E-Way Bill is auto-populated using the data submitted for the e-invoice, reducing duplicate entries. However, the taxpayer or vehicle operator must still provide transporter details and complete Part B of the E-Way Bill to make it valid for transit.
What are the exact consequences of issuing a covered B2B invoice without an IRN? +
Under Rule 48(5) of the CGST Rules, any document issued by a covered taxpayer without an authenticated IRN is not legally treated as a valid tax invoice. This exposes the supplier to penal provisions for incorrect invoicing, causes transit delays if goods are intercepted, and completely prevents the buyer from claiming Input Tax Credit (ITC).
Can an invoice number be reused if the original e-invoice was cancelled? +
No. The IRP architecture runs strict deduplication checks. If an IRN is generated and subsequently cancelled within the 24-hour window, that specific invoice number is permanently logged as used. It cannot be reused for another upload. Future entries must use a completely fresh invoice number format.
Are dynamic QR codes required on invoices issued directly to end consumers (B2C)? +
No, standard B2C transactions are exempt from the Rule 48(4) IRP upload framework. However, large retail taxpayers with turnovers exceeding ₹500 Crore face a separate legal requirement to print a dynamic B2C QR code on bills. This lets retail customers scan and complete digital payments directly via UPI at checkout.


Start Your GST E-Invoicing

Complete registration with expert CA support

By submitting you agree to our Terms of Service
Related Services

Also popular with new entrepreneurs