E-Invoicing in India 2026: The Complete Guide

1. What is e-invoicing under GST?

E-invoicing under India's Goods and Services Tax (GST) regime is the process of submitting every B2B tax invoice in a standard JSON schema to a government-authorised Invoice Registration Portal (IRP) — primarily einvoice1.gst.gov.in — to receive a unique 64-character Invoice Reference Number (IRN) along with a digitally signed QR code, before the invoice is delivered to the customer. Without these two artefacts on the printed or PDF invoice, the document is not a valid tax invoice under Rule 48(5) of the CGST Rules.

If you are new to the topic, here are the acronyms that recur throughout this guide:

• IRP — Invoice Registration Portal, the GSTN-run validator that issues IRNs
• IRN — Invoice Reference Number, a unique SHA256 hash returned by the IRP
• GSP — GST Suvidha Provider, a private company licensed to offer API access to the IRP and GSTN
• GSTIN — 15-character GST identification number of a registered taxpayer
• ITC — Input Tax Credit, what your customer claims against the GST you charged
• E-way bill — separate document required for movement of goods worth above Rs 50,000
• GSTR-1 — monthly outward supply return that an e-invoice auto-populates
• CBIC — Central Board of Indirect Taxes & Customs, the policy authority

Crucially, an e-invoice is not a different kind of invoice. It is the same tax invoice you already issue, but routed through the IRP first so that the government has a real-time, immutable record of every B2B transaction. The IRP returns the IRN and signs the JSON, after which you embed the QR code on your existing invoice template and dispatch as usual.

How is it different from a regular GST invoice?

A regular GST invoice carries your GSTIN, the buyer's GSTIN, HSN/SAC codes, tax breakup, and an internal invoice number. An e-invoice adds three things: an IRN, a signed QR code, and a guarantee that the invoice has been validated by the GSTN. From a printing perspective the only visual difference is the QR code box.

Why did the government introduce it?

E-invoicing was rolled out to plug input tax credit fraud, which the CBIC estimated at thousands of crores annually before 2020. By making the IRP the single source of truth, fake invoices stop generating IRNs, ITC chains become traceable, and GSTR-1 auto-fills directly from validated invoices, removing manual reconciliation between a seller's books and the buyer's view of supplies. It also creates a foundation for instant analytics on B2B trade flows.

A quick history of the threshold

E-invoicing rolled out in phases under successive CBIC notifications since 2020, with the threshold steadily lowering. The progression below shows how quickly the net widened to bring small and medium businesses into scope.

2. Who must comply with e-invoicing in 2026?

The current threshold is Rs 5 crore aggregate annual turnover (AATO), in force since 1 August 2023 under CBIC notification 10/2023-Central Tax. The crucial nuance: AATO is checked against any financial year from 2017-18 onwards, not just the most recent year. Once your business has crossed Rs 5 crore in any past year, the e-invoicing mandate applies permanently — even if your current year turnover has dropped below it.

Common scenarios

• You crossed Rs 5 crore in FY 2023-24: e-invoicing applies for FY 2024-25 onwards, and continues forever even if turnover drops.
• You are currently below Rs 5 crore but crossed it in FY 2018-19: still in scope. The rule is sticky.
• You crossed Rs 5 crore mid-year: mandate kicks in from the first day of the financial year following the year of crossing, per CBIC clarification.
• New business: the mandate applies from the date you cross Rs 5 crore in any FY going forward.

Who is exempt?

Even if turnover crosses the threshold, the following categories are explicitly excluded from e-invoicing under CBIC notifications:

• SEZ developers (SEZ units are covered for outward supplies; only developers are exempt)
• Banking and financial institutions, including NBFCs
• Insurance companies
• Goods Transport Agencies (GTAs)
• Passenger transport service providers
• Multiplex cinema operators (admission tickets only)
• Government departments and local authorities supplying services where consideration is recovered as a fee

B2B vs B2C — only B2B is in scope

E-invoicing is mandated only for transactions where the recipient is a registered taxpayer. That means:

• In scope: B2B sales, B2G (sales to government with valid GSTIN), exports (with or without payment of IGST), deemed exports, and supplies to Special Economic Zones
• Out of scope: B2C sales (sales to retail consumers without a GSTIN), nil-rated supplies, and exempt supplies

Note that businesses with turnover above Rs 500 crore have a separate obligation to print a dynamic QR code on B2C invoices, but this is not the same as e-invoicing — there is no IRN involved.

For a full deep dive on threshold mechanics, edge cases around joint ventures, branch-level GSTINs, and what to do when your turnover fluctuates, see our companion blog post on the e-invoicing turnover threshold 2026.

3. How IRN generation works — step by step

At a high level, IRN generation is a six-stage round trip between your billing software and the IRP. The whole loop typically completes in 1 to 3 seconds when done via API, or 2 to 5 minutes via manual portal entry.

The 6-step IRN flow

1. Prepare the invoice in your billing software. Capture all mandatory fields: supplier and recipient GSTIN, document type and number, invoice date, place of supply, HSN/SAC codes (8 digits for taxpayers above Rs 5 crore), unit, quantity, unit price, taxable value, and CGST/SGST/IGST/Cess amounts.
2. Validate the JSON schema. The IRP rejects any payload that does not conform to the latest e-invoice schema (currently version 1.1 with backward compatibility). Your software should validate locally before submission to avoid round trips.
3. Submit to the IRP. Either via direct API call through a registered GSP, manual upload at einvoice1.gst.gov.in, or Excel bulk upload using the GSTN-provided offline tool.
4. Receive the IRN, signed JSON, and QR code. The IRP computes a SHA256 hash of supplier GSTIN + document number + financial year + document type, returns it as the IRN, and sends back a digitally signed JSON plus a 350-byte QR payload.
5. Embed on the customer invoice. Print the IRN string and the QR code image on your invoice PDF. Most billing software places the QR code in the top-right corner.
6. Auto-push to GSTR-1 and (optionally) e-way bill. The IRP forwards e-invoice data to the GSTR-1 system the next day and, if you flag it, generates an e-way bill in the same call.

Three integration paths

Pick the path that fits your invoice volume and IT capability. Most businesses migrate up the ladder as they grow.

The IRN format

The IRN is a 64-character hexadecimal string — a SHA256 hash of SupplierGSTIN_DocumentNumber_DocumentType_FinancialYear. Two consequences flow from this:

• Two invoices with the same number in the same FY produce the same IRN — that's why duplicate IRN errors happen if you retry without changing the document number.
• The IRN contains no business-sensitive data. It's safe to print, email, and share.

What's in the QR code?

The QR code carries: supplier GSTIN, recipient GSTIN, invoice number and date, invoice value, number of line items, main HSN code, and the IRN itself. Anyone with a QR scanner app (or the IRP's online verifier) can confirm an invoice's authenticity in seconds.

The 30-day rule

Effective 1 November 2023, businesses with AATO above Rs 100 crore must submit invoices to the IRP within 30 days of the invoice date. Any submission older than 30 days is rejected outright. This rule is widely expected to be extended to Rs 5 crore taxpayers within the next 12-18 months, so smaller businesses should treat the 30-day window as best practice today.

For a hands-on walkthrough of every API field, sandbox credentials, and example JSON payloads, see our detailed IRN generation step-by-step guide.

4. E-invoice vs e-way bill — what is the difference?

One of the most common points of confusion is whether e-invoicing replaces the e-way bill. It does not. They are two separate documents triggered by two different events under GST.

• E-invoice is triggered by the issuance of a B2B tax invoice, credit note, or debit note (above the Rs 5 crore turnover threshold). It exists for ITC integrity and GSTR-1 auto-fill.
• E-way bill is triggered by the movement of goods worth above Rs 50,000, regardless of whether the consignor's turnover crosses any threshold. It exists for transit verification by tax officers.

They overlap in one common scenario: a B2B sale that also moves goods worth more than Rs 50,000. In that case both documents are required, and the IRP can auto-generate the e-way bill from the e-invoice in a single API call — removing duplicate data entry.

For exhaustive scenarios — same-state vs interstate, multi-vehicle, transhipment, branch transfers, return shipments, and the Part-A/Part-B mechanics of e-way bill — see our full e-invoice vs e-way bill comparison.

5. Penalties for non-compliance

Penalties for missing, incorrect, or late e-invoices come from three sources: Section 122 of the CGST Act, late fees under Section 47, and indirect commercial penalties from your customers losing ITC. Combined, they make casual non-compliance very expensive.

Section 122 — primary penalty

Issuing an invoice without an IRN, or with an incorrect IRN, attracts a penalty of Rs 10,000 per invoice or the tax amount involved, whichever is higher, under Section 122(1) of the CGST Act. For a business issuing 100 such invoices in a quarter, the exposure can easily exceed Rs 10 lakh.

Section 47 — late filing of GSTR-1/3B

If missing IRNs cause downstream delays in GSTR-1 filing, you face Rs 50 per day (Rs 25 CGST + Rs 25 SGST), capped at Rs 5,000 per return. For nil returns the cap is Rs 500. This is on top of any Section 122 penalty.

ITC denial — the customer pressure point

This is often the most painful penalty in practice. Under Rule 36(4) and the GSTR-2B mechanism, your customer can claim ITC only against invoices that have valid IRNs reflected in their auto-populated GSTR-2B. If you issue an invoice without an IRN, your customer's ITC is blocked. They will deduct the GST amount from your payment, demand re-issuance, and quickly stop doing business with you. Several large enterprise buyers now reject any incoming invoice that does not have a verifiable IRN at the procurement stage.

GSTIN suspension

Repeated default — typically three or more cycles of non-compliance — can trigger Rule 21 suspension of your GSTIN by the proper officer. Suspension means you cannot issue any tax invoice at all, effectively halting business until restored.

For a deeper look at exact penalty calculations, real-world case studies, and how to structure customer communications when you've issued an invoice without an IRN by mistake, read our e-invoicing penalties under GST playbook.

6. Top 10 IRP errors and how to fix them

Across thousands of IRN submissions, ten error patterns account for over 90% of all rejections. Here are the codes, root causes, and fixes — file this as a desk reference for your accounts team.

Building a self-healing retry pipeline

Rather than fixing each error reactively, the best defence is a queue-based retry layer in your billing software that:

• Catches the IRP error code, parses the human message, and pattern-matches it to one of the ten cases above
• Auto-fixes safe cases (re-fetching the existing IRN on duplicate, re-submitting with corrected HSN length)
• Escalates ambiguous cases to a designated accounts user with the exact field at fault
• Tracks failure rate by error code and alerts when any single cause exceeds 2% of submissions

Our customers using Softwaller's GST billing module see IRN submission success rates above 99.4% by month two of go-live. For an in-depth fix playbook with sample API responses and screenshots, read our top 10 IRP errors and fixes guide.

7. Free GSTN portal vs paid software — which to choose?

Once you cross the threshold you have four realistic options for generating IRNs. The right one depends on your monthly invoice volume, IT readiness, and how tightly you need e-invoicing tied to inventory and sales workflows.

The real cost-benefit calculation

For a business issuing 200 invoices a month, manual portal entry consumes roughly 8-10 person-hours per month. At a junior accountant cost of Rs 25,000/month, that's about Rs 1,500-2,000/month in labour. A paid tool at Rs 250-500/month saves roughly Rs 12,000-18,000 per year and reduces error rates by 70-80% based on customer surveys.

Paid tools also reduce indirect costs: fewer customer disputes over missing IRNs, faster GSTR-1 filing (because data is already validated), and compliance peace of mind during department audits.

When custom ERP makes sense

Custom-built billing software becomes the better economic choice when you have any two of: multiple branches with separate GSTINs, >500 invoices a month, integration with inventory/sales/POS, multi-user role-based access needs, or industry-specific edge cases (textile, pharma, automotive). The upfront investment is higher but recurring costs converge with paid SaaS within 18-24 months and you keep full data ownership.

For a side-by-side comparison of free vs paid for businesses just crossing Rs 5 crore, see our breakdown free GSTN portal vs paid software for small business. For pricing on a custom ERP, see our custom ERP cost guide.

8. The 30-day implementation playbook

If you've just received an alert that your turnover crossed Rs 5 crore in the last FY, you have roughly 30 days to be e-invoicing live. Here is a tested day-by-day roadmap that hundreds of Softwaller customers have followed without missing a deadline.

Days 1-3 — Audit

• Pull a full list of B2B customers from the past six months from your books
• Validate every recipient GSTIN on the GST portal "Search Taxpayer" — flag inactive, cancelled, or wrong-format GSTINs
• Document your current invoice flow: who creates, who approves, who dispatches
• List all document types you raise: tax invoice, credit note, debit note, export, SEZ, advance receipt

Days 4-7 — Choose path

• Calculate average monthly B2B invoice volume over the last 12 months
• Pick the integration path: portal (under 50/month), Excel bulk (50-300/month), or API (300+/month)
• If API: shortlist 2-3 GSPs, request demos and pricing
• If your billing software has built-in IRP integration, skip GSP shortlisting

Days 8-14 — Configure

• Register your GSTIN on einvoice1.gst.gov.in, complete OTP verification
• If using API: obtain GSP credentials (client ID, client secret) and sandbox keys
• Configure your billing software with: GSTIN, branch series, place-of-supply rules, default HSN/SAC, e-way bill auto-trigger flag
• Update HSN master to 8-digit codes for all goods (mandatory above Rs 5 crore)

Days 15-20 — Sandbox testing

• Generate at least 30 test IRNs covering every document type and edge case
• Test deliberate failures: invalid GSTIN, wrong HSN, duplicate, future date
• Confirm error handling, retry logic, and user notifications work end-to-end
• Print sample invoices and verify QR code scans correctly

Days 21-25 — Master data clean-up

• Reconcile customer master: refresh GSTINs, addresses, state codes, place-of-supply
• Reconcile vendor master: same checks for incoming reverse-charge transactions
• Train accounts staff on the new flow, error codes, and escalation paths
• Document a 1-page runbook for common issues

Days 26-28 — Parallel run

• For 2-3 days, run the new e-invoicing flow alongside the old process for every B2B invoice
• Reconcile counts daily: invoices issued vs IRNs generated vs GSTR-1 entries
• Fix any failures, retrain staff on recurring mistakes

Days 29-30 — Go-live

• Switch e-invoicing to primary; retire the manual flow
• Email a customer advisory: your invoices will now carry IRN and QR code
• Set up daily monitoring of failure rate (target: under 1%)
• Schedule a 30-day post-go-live review

9. How Softwaller helps

Softwaller Technologies is a Salem-based custom software house that has been building GST-compliant billing and ERP systems for Indian SMEs since the GST regime began. Our Custom GST Billing Software ships with end-to-end e-invoicing baked in — not as a bolt-on, but as part of the core invoice creation flow.

What's included by default

• Built-in IRP integration via registered GSPs — no third-party plugins, no extra subscription per IRN
• Automatic IRN retry on errors with the self-healing pipeline described in section 6
• 30-day rule monitoring — invoices nearing the 30-day cutoff trigger automatic alerts
• GSTR-1 auto-fill from generated IRNs, including JSON export ready for upload
• E-way bill auto-trigger when goods movement value exceeds Rs 50,000
• Multi-GSTIN, multi-branch with separate invoice series and place-of-supply rules
• Tally Prime two-way sync via XML or ODBC for businesses keeping accounting in Tally
• Audit trails and role-based access covering DPDP and CBIC audit needs

For broader business operations beyond billing, our Custom ERP with e-invoicing integrates the same compliance core with sales, inventory, manufacturing, HR, and dashboards. See case studies from customers in distribution, manufacturing, and retail, or read more about the team.