GST e-Invoicing

Since October 2020, the Invoice Registration Portal has been the legal checkpoint for B2B invoices in India. If your aggregate turnover crossed ₹5 crore in any financial year from FY 2017-18 onwards, every B2B tax invoice, credit note, and debit note must carry a valid Invoice Reference Number (IRN) before it leaves your business. Without that IRN, the invoice has no legal standing under Rule 48(4) of the CGST Rules — and your buyer cannot claim input tax credit (ITC) on it.

The technical side is harder than it looks. Your ERP or billing software creates the invoice; a GSP or API bridge submits it to the IRP; the IRP validates the schema, stamps it with a QR code and IRN, and returns the signed document — ideally in under three seconds. If that chain is set up incorrectly, every B2B sale becomes a friction point. Set it up right once and it runs without anyone noticing.

At a Glance

• Who must comply: Any taxpayer whose aggregate turnover exceeded ₹5 crore in any FY from FY 2017-18 onwards, computed across all GSTINs under the same PAN.
• Governing law: Section 31 and Rule 48(4) of the CGST Rules 2017; Notification 13/2020-Central Tax and its subsequent amendments.
• Documents in scope: B2B tax invoices (INV), credit notes (CRN), debit notes (DBN), SEZ supplies with or without payment, exports with or without IGST, and deemed exports — all require an IRN.
• Documents excluded: B2C invoices, bills of supply for exempt goods, and nil-rated supply invoices are not covered by e-invoicing obligations.
• IRP options: NIC IRP (free, government-run) or any GSTN-approved private IRP including ClearTax, IRIS, and Cygnet — each with different API capabilities and SLAs.
• GSTR-1 impact: IRN-issued invoices auto-populate GSTR-1 outward supply tables — no separate data entry is required for those transactions.
• eWay Bill link: Including transport details at IRN stage auto-generates eWay Bill Part A; Part B (vehicle and transporter details) must still be added separately before goods move.

What's New for FY 2026-27

Three platform changes directly affect e-invoicing workflows in FY 2026-27.

• IMS is live: The Invoice Management System now lets your buyers accept, reject, or hold invoices pending inside the GST portal. Your IRN data feeds IMS in real time — mismatches surface as buyer actions within days, not at year-end reconciliation.
• GSTR-1A introduced: Suppliers can now amend GSTR-1 data before the corresponding GSTR-3B is filed using the new GSTR-1A form. IRN-auto-populated entries with errors can be corrected within the same period, without waiting for the next monthly cycle.
• ₹5 crore threshold stable — for now: No further reduction was announced for FY 2026-27, but the policy direction continues downward. Businesses with ₹2-5 crore turnover should treat integration readiness as a near-term priority, not a future consideration.
• Private IRP ecosystem matures: Multiple GSTN-approved private IRPs now compete on SLA, cost, and ERP compatibility. If your rejection rate on the NIC IRP is consistently above 0.5%, a private IRP with better API documentation may be worth evaluating.
• E-invoice schema updates: HSN codes must be reported at 6-digit level for supplies above ₹1 lakh per line item. HSN mismatches between your ERP master and the IRP schema validation are now the leading cause of rejection errors in FY 2026-27.

Why e-Invoicing Compliance Matters

E-invoicing determines whether your B2B invoices are legally valid — it is not a filing formality that can be deferred.

• You crossed ₹5 crore in any prior year: The obligation is permanent once triggered. A drop in turnover in a later financial year does not remove it — this is explicitly stated in Notification 13/2020-CT.
• You sell to registered businesses: B2B sales are squarely in scope. A non-IRN invoice means your customer's ITC claim is blocked under Section 16(2)(c) — a commercial dispute that traces directly back to your compliance gap.
• You export goods or services: Export invoices — with or without payment of IGST — need an IRN. SEZ supplies with or without payment are also covered; both are common sources of missed compliance for manufacturing and software exporters.
• You issue credit notes or debit notes: Each credit note and debit note needs its own IRN linked to the original document. These are legal amendments to a reported transaction, not internal accounting adjustments.
• Your ERP generates invoices at volume: Without API integration, every invoice requires a manual portal upload. At 200+ invoices a month, that is unsustainable — and data-entry errors produce a rejection rate that compounds quickly.
• Your customers require it: Large corporate buyers check GSTR-2B for IRN-backed invoices as part of their ITC reconciliation. Missing IRNs appear in their portal and trigger payment holds or formal vendor compliance notices.

How It Actually Works

The integration runs in six phases, from threshold confirmation through to ongoing monthly reconciliation.

Step 1: Threshold & Applicability Mapping (Day 1)

We pull the full GSTIN list under your PAN and compute aggregate turnover for each FY from FY 2017-18 onwards. This confirms your trigger date — the first year in which your turnover crossed ₹5 crore — and identifies which GSTINs are in scope. We also map any exclusions: government entities, certain financial institutions, and a small set of other notified categories remain outside the e-invoicing obligation even above the threshold.

Step 2: IRP & GSP Selection (Days 2-4)

You choose between the NIC IRP, which is free and government-operated, and the GSTN-approved private IRPs such as ClearTax, IRIS, or Cygnet. We compare each option on API documentation quality, rejection-handling support, per-IRN cost, and compatibility with your ERP or billing software. For Tally Prime or Zoho Books at moderate volumes, NIC works well. For SAP or Oracle environments, private IRPs with enterprise-grade support typically deliver lower rejection rates and faster issue resolution.

Step 3: ERP Schema Mapping & API Integration (Days 5-14)

This is where most of the project time is spent. Your ERP's invoice fields must map correctly to the e-invoice JSON schema: GSTIN format, HSN code digit count, place of supply by destination state, document type (INV, CRN, or DBN), ship-to versus bill-to address, and tax breakdowns by component. We write the transformation rules, set up the API connection — directly via the IRP API or through a GSP intermediary — and validate every mapped field before a single live invoice is submitted.

Step 4: Pilot Run & UAT (Days 15-18)

We run 20-50 real invoices through the IRP sandbox, then a controlled batch on production. Every rejection code is logged, the root cause identified, and the ERP mapping corrected. QR code printing is verified against your physical and digital invoice formats. We target zero rejections in the UAT phase before recommending the full production cut-over.

Step 5: Production Go-Live (Day 19 or 20)

The switch to full production happens on a single day. Your team generates invoices in the ERP as normal; the API bridge handles IRP submission in the background; the IRN and QR code stamp back automatically onto the invoice record. We monitor the first 48 hours closely and resolve any API latency issues or rejection spikes immediately.

Step 6: Monthly IRN Reconciliation (Ongoing)

Each month, we match the IRN-issued register against GSTR-1 auto-populated data, eWay Bill records, and your books. Any IRN issued but absent from GSTR-1 — or an ERP invoice carrying no matching IRN — generates a short-cycle correction before the GSTR-1 filing deadline. IMS action items from buyers are reviewed and responded to in the same cycle. This monthly discipline stops period-end gaps from becoming penalties in the following quarter.

A Real Example: Auto-Parts Manufacturer, Mumbai

A manufacturing business in Mumbai — ₹7.2 crore aggregate turnover, running Tally Prime, issuing around 280 B2B invoices a month to dealers and distributors across 11 states — came to us after a major corporate buyer flagged missing IRNs in its GSTR-2B reconciliation.

• The problem: The accounts team was uploading invoices manually to the NIC portal one by one. At 280 invoices a month, that meant 2-3 hours of daily data entry and a running rejection rate of around 4% — almost entirely caused by HSN code mismatches between the Tally master and the IRP schema.
• Threshold history: Aggregate turnover had crossed ₹5 crore in FY 2021-22 — three financial years before they engaged us. The manual NIC uploads had produced valid IRNs throughout, so there was no back-dated penalty exposure; however, the process was unsustainable at their current invoice volume.
• What we did: We connected Tally Prime to the NIC IRP through a Tally-compatible GSP. The HSN master was corrected from 4-digit to 6-digit codes across 340 product line items. Place-of-supply logic was mapped for all 11 destination states. Total setup time: 14 working days.
• The outcome: IRN generation dropped from 2-3 hours per day to under 30 seconds per invoice batch. GSTR-1 auto-population replaced manual outward data entry entirely. The rejection rate fell from 4% to under 0.2% in the first full month of live operation.

The time recovered in the first two months more than offset the integration cost, and the business now has a documented IRP downtime fallback procedure — something the old manual process had never included.

Monthly Reconciliation — What Keeps You Clean

Going live on e-invoicing is step one. The monthly discipline that follows is what prevents ITC disputes and penalties.

• IRN register vs GSTR-1: Every IRN issued during the month should appear as an auto-populated entry in GSTR-1 Table 4 (B2B) or Table 6A (exports). Any IRN that doesn't auto-populate signals an API sync gap that must be fixed before GSTR-1 is filed.
• IRN vs eWay Bill register: Where goods were despatched, the eWay Bill should reference the same IRN. A mismatch — IRN issued but no EWB, or EWB with no matching IRN — creates Section 68 exposure during transit inspection.
• Cancellation log: Cancelled IRNs must be excluded from GSTR-1 and matched with replacement invoices or a documented decision not to replace. Orphan IRNs — cancelled with no replacement and no explanation — are a common audit flag.
• IMS buyer actions: Under the IMS framework live from FY 2026-27, buyer rejection or pending status for your IRN-backed invoice is visible in your GST portal. Responding before the GSTR-3B cut-off is now part of the monthly cycle, not an optional check.
• Recipient ITC disputes: Where a buyer raises an ITC denial citing a missing IRN, we verify whether the IRN was generated and correctly reported in GSTR-1. If it was, we provide the signed e-invoice JSON as proof. If it wasn't, we issue a corrected invoice with a fresh IRN.

GSTR-1A, introduced in FY 2026-27, lets you correct outward supply data before GSTR-3B is filed. IRN-populated entries with schema or value errors can now be fixed in the same period — use this window before it closes each month.

Where It Goes Wrong

Most e-invoicing problems trace to a handful of setup or process errors that compound quietly over time.

• Aggregate turnover miscalculated: Turnover must be summed across all GSTINs under the same PAN — not per GSTIN. Businesses with multiple registrations sometimes compute per-GSTIN figures and incorrectly conclude they are below the ₹5 crore threshold.
• IRN generated but QR code missing from the invoice: The IRN exists in the IRP system but is absent from the physical or emailed invoice. The buyer has no verification; the invoice can be challenged during audit without the QR code present.
• 24-hour cancellation window missed: An incorrect invoice must be cancelled at the IRP within 24 hours, provided no eWay Bill has been generated. Missing this window forces a credit note plus fresh invoice workflow, which must be reported differently in GSTR-1 and requires additional documentation.
• EWB generated before IRN: Generating the eWay Bill before obtaining the IRN is a sequencing error. The correct order is always IRN first, then EWB using the IRN as reference. Reversing this order causes portal rejection and transit compliance gaps.
• HSN codes at the wrong digit count: Supplies above ₹1 lakh per line require 6-digit HSN codes. Using 4-digit codes triggers IRP rejection error 2283 — the single most common rejection code in multi-state B2B operations with legacy ERP masters.
• B2C invoices accidentally pushed to IRP: B2C invoices don't require an IRN. Pushing them to the IRP creates phantom IRNs that appear in GSTR-1 auto-population and introduce reconciliation gaps that take several months to clean up.
• No IRP downtime contingency: The IRP goes offline periodically. Without a documented fallback procedure following CBIC circular guidance, the choice during downtime is between halting despatch or issuing invoices without IRNs — both create audit exposure.
• Stale ERP customer master: Customer GSTIN changes, HSN reclassifications, or updated state codes not reflected in the ERP master produce rejection errors that appear only when that customer's next invoice is processed.

What You Receive at the End

• Live IRP integration with your ERP or billing software, tested and signed off on production
• IRN generation in under three seconds per invoice with automated QR code stamping
• GSTR-1 outward supply tables auto-populated each period directly from IRN data
• eWay Bill Part A auto-generation where transport details are supplied at invoice stage
• Monthly IRN reconciliation report covering IRN register vs GSTR-1 vs eWay Bill vs books
• Cancellation log and credit note workflow documented with step-by-step SOPs
• Schema mapping document for your ERP, version-controlled for future updates
• IRP downtime contingency procedure aligned with current CBIC circular guidance
• Staff training guide covering QR code verification, IRN exception handling, and IMS responses
• Ongoing schema update service as GSTN publishes new e-invoice JSON schema versions

How to Get Started

Share your GSTIN, the ERP or billing software you use, and an approximate monthly B2B invoice count. We run a threshold check across all GSTINs under your PAN, confirm your trigger date, and prepare an IRP comparison for your volume and system profile. You will have a clear integration plan — scope, timeline, and what we need from your IT team — before any work begins.

From that point, our team handles sandbox setup, schema mapping, UAT, and production cut-over. Most integrations go live within 15 working days. Once live, monthly reconciliation runs as a managed service — we deliver the gap report before your GSTR-1 deadline, not after. If your team wants to own the process internally, we train them fully and hand over the complete integration documentation.