GST E-Invoicing in India: The 2026 Compliance Checklist

If you run a business in India and your turnover is anywhere above ₹5 crore, GST e-invoicing is no longer optional, no longer "the big company problem", and no longer something you can paper over with a clever Tally workaround. Every B2B invoice has to be registered with the IRP, get an Invoice Reference Number (IRN), and carry a QR code — before you send the invoice to your customer. Miss any step and your customer can't claim input tax credit, which means awkward conversations and broken payment cycles.

This checklist is what we walk our customers through when they cross the threshold for the first time, or when they realise their existing system isn't doing the full job. It's not legal advice — please talk to your CA before final implementation — but it covers the practical, mechanical questions you'll need to answer regardless of whether you're in distribution, manufacturing, or textiles.

A two-minute primer: who is in scope today

GST e-invoicing started in October 2020, applying only to businesses above ₹500 crore turnover. Since then the CBIC has stepped the threshold down repeatedly:

Effective From	Turnover Threshold
Oct 2020	₹500 crore
Jan 2021	₹100 crore
Apr 2021	₹50 crore
Apr 2022	₹20 crore
Oct 2022	₹10 crore
Aug 2023	₹5 crore

The direction of travel is clear: every Indian B2B business with material turnover is being pulled in, and the threshold is widely expected to come down further. If your aggregate turnover crossed ₹5 crore in any preceding financial year from 2017-18 onwards, you are required to generate e-invoices.

A few important nuances most businesses miss:

• Aggregate turnover means PAN-level — across all your GSTINs, exempt sales, exports, and supplies to SEZ count too.
• The threshold applies as soon as you cross it in any financial year — you cannot drop back out.
• Exemptions exist for SEZ developers, insurers, banks, NBFCs, GTAs and a few special categories — most operating businesses do not qualify.
• Both B2B supplies and exports are in scope. B2C is currently out, but a QR code is required for B2C invoices for businesses above ₹500 crore.

Volume vs complexity: distributors, manufacturers, and mills face different headaches

The compliance checklist below applies to every business in scope. But the kind of pain you'll feel differs sharply depending on what you do:

• Distributors typically face the highest volumes — fast-moving SKUs dispatch repeatedly through the day, each invoice with a similar pattern. The bottleneck is throughput at peak hours and reconciliation across daily transactions.
• Manufacturers generate fewer but more complex invoices — work-order-linked dispatches, job-work-out movements, partial shipments against the same purchase order, advances and proforma against the same job. Each has its own e-invoicing nuance.
• Textile mills, especially composite mills, sit in the most complex zone: inter-edition transfers (spinning to weaving to processing), customer-supplied job work, blended ownership of in-process inventory, and frequent credit notes for shade variations. A single dyeing job can produce three different e-invoices over its lifecycle.

Recognising which profile fits you helps you spot the failure modes you're most likely to hit. With that framing, here's the checklist.

The 2026 Compliance Checklist

Use this as a walkthrough with your finance head and ERP vendor.

1. Confirm your scope status — in writing

Have your CA give you a written confirmation of whether your business is in scope, based on the latest closed financial year's turnover. Keep this on file. Why this matters: tax notices often arrive 18 months after the fact; the audit trail is your defence.

2. Register on the Invoice Registration Portal (IRP)

You can use any of the multiple IRPs the government has authorised (NIC, ClearTax, Cygnet, etc.). NIC's portal at einvoice1.gst.gov.in is the default. If your ERP integrates with one IRP, you're functionally set.

3. Choose your IRP integration method

There are three:

• API integration — your ERP talks directly to the IRP. This is the only option that scales for any meaningful invoice volume and the only one we recommend for any business of scale.
• Bulk upload — Excel-based, periodic. Works for very small volumes but breaks the moment your customer wants the IRN on a same-day invoice.
• Manual entry — for absolute exception cases only.

If your current billing system can only do bulk upload, that is the single biggest sign you need an upgrade.

4. Verify your invoice schema is current

The e-invoice schema (INV-01 JSON) gets updated by GSTN periodically. Your ERP must validate against the current schema version every time it generates an IRN — otherwise you'll start getting rejections without warning. This is a vendor concern; ask your ERP vendor when they last updated the schema and how they roll out future updates.

5. Lock down the 30-day generation window

For businesses above ₹100 crore, an invoice older than 30 days cannot be registered. Below that threshold there is no time limit yet — but the direction is clear. Practical implication: if your finance team batches invoice posting weeks after the goods physically ship, you are building up risk. Tighten the cycle to T+1.

6. Wire IRN and QR code into your invoice PDF template

This is the most common implementation gap. Your ERP generates the IRN, but the invoice PDF that goes to your customer doesn't carry it. Your customer's accountant will reject the invoice, and the bill cycle resets. Verify on a real test invoice:

• IRN printed prominently (typically top of the invoice)
• 2D QR code embedded — generated from the signed JSON, not just any QR
• Acknowledgment number and Ack date present
• Digital signature visible (or signature certificate referenced)

7. Handle credit notes, debit notes, and cancellations correctly

Credit notes and debit notes are also in scope — they need IRNs. Cancellation of an e-invoice must happen within 24 hours on the IRP; after that, you must issue a credit note. Your ERP workflow should make this distinction unmissable. This matters especially for textile mills and manufacturers, where shade rejections, quality returns, and partial-acceptance scenarios are routine.

8. Reconcile IRN-generated invoices against your GSTR-1

E-invoices auto-flow into your GSTR-1. The ones that should have generated IRNs but didn't are your compliance gap. Run a weekly reconciliation report: invoices issued vs IRN-tagged invoices vs GSTR-1 auto-populated. Three numbers must match.

9. E-way bill generation: chain it to the IRN flow

For invoices that need an e-way bill (interstate goods movement over ₹50,000), generating it in the same workflow as the e-invoice avoids duplicate data entry and reduces errors. Your ERP should produce both from a single invoice posting. Job-work dispatches and inter-state stock transfers have their own e-way bill rules; make sure those flows are covered too.

10. Build the audit trail

Every e-invoice has an IRP-issued IRN, an acknowledgment number, a signed JSON, and a generation timestamp. All four must be stored — not just the IRN. In a GST audit, the assessing officer can ask for the signed JSON of any invoice; if you can't produce it, the invoice is treated as never having been e-invoiced.

The five places we see Indian businesses fail

After implementing this across distribution, manufacturing, and textile customers, the failure modes are remarkably consistent:

1. The shipping document goes out, the invoice goes out, and the IRN is generated days later. Goods physically leave the premises without a valid invoice — technically a GST violation. Distributors hit this at peak hours; mills hit it when a dyeing job finishes overnight.
2. Credit notes are issued from a separate accounting system that doesn't talk to the IRP. They never get IRNs. Six months later, the customer's books don't reconcile and the auditor asks why. Frequent in textiles, where credit notes against shade variations are part of routine business.
3. Bulk upload "works" until peak month-end. When a distributor is trying to push hundreds of invoices on March 31, the bulk upload portal is slow, files time out, and the team is up at midnight. The fix is real-time API integration, period.
4. The invoice PDF template is updated in one ERP module but not another. Sales generates compliant PDFs; the service department or the export module generates non-compliant ones, and nobody notices for months. Common when the IRN integration is a bolt-on rather than baked into invoice posting.
5. Token expiry and credential management. API tokens expire. Nobody set up monitoring. One day, every invoice silently fails to generate an IRN and the team only discovers it in week two.

What your ERP actually needs to do

A modern ERP that handles GST e-invoicing properly does not bolt the IRP integration on as a side feature. It treats the IRN flow as part of invoice posting itself. Specifically:

• Real-time API call to the IRP at the moment of invoice generation, not as a separate sync step.
• Automatic retry with exponential backoff when the IRP is slow or returns transient errors (which it does, especially at month-end).
• Hard-stop on the invoice if the IRN cannot be obtained — the user cannot proceed to print or dispatch until the IRN is in hand.
• Unified IRN flow for sales invoices, credit notes, debit notes, exports, and job-work dispatches — no second system to keep in sync.
• Embedded e-way bill generation for the same transaction.
• Daily reconciliation report of IRN-tagged invoices vs invoices posted vs GSTR-1.

This is what we've built into every Systech suite — Orbit for distribution, Precision for discrete manufacturing, and Texora for textile mills. The IRN flow is baked into invoice posting, the retries and reconciliation are automatic, and the audit trail is built without anyone having to remember to do it. The same compliance engine handles a distributor's high invoice volume and a composite mill's multi-stage job-work invoices — different operational scenarios, the same statutory rigour.

When to act

If you're already past ₹5 crore and your current system uses bulk upload or manual entry: this month. Every fiscal year you delay is a year of compliance risk piled on top of inefficient billing. If you're approaching ₹5 crore: have the conversation with your ERP vendor before you cross the threshold, not after — you do not want to be implementing this while also fielding tax notices.

If you'd like to see how an integrated IRN flow looks in real time — for distribution, manufacturing, or textile scenarios — book a 30-minute walk-through with our team. We'll show you the actual API logs, the retry behaviour, the audit trail, and a real reconciliation report from a Systech customer running high invoice volumes through one of our suites.

GST e-invoicing is not interesting. It is, however, unavoidable, and getting it right is the difference between a closing cycle that takes two days and one that takes three weeks every March. Worth doing properly.