How-to · e-Invoicing & e-Way Bill continuity

One IRP configured, invoices to raise. GSTN already built you a second one

The short answer

GSTN runs six live e-invoicing IRPs — NIC-IRP 1 and 2, plus Cygnet, Clear, EY and IRIS — and two e-way bill portals, with NIC's own pair interoperable by design. Registering a backup means holding working, tested credentials on a second IRP, or confirming your GSP supports cross-portal switching, before an outage — not while invoices are stuck waiting on the first one.

Every e-invoicing walkthrough treats "register with an IRP" as a one-time, one-portal task. GSTN's own continuity advisory says otherwise — it names six live Invoice Registration Portals and two e-way bill portals precisely because any one of them can go down, and tells taxpayers to coordinate with their IRPs, GSPs and ASPs to wire in the alternates before that happens.

Six portals, not one

GSTN's own advisory on the subject — "Advisory on Business Continuity for e-Invoice and e-Waybill Systems" (gst.gov.in News & Updates, 24 January 2025) — opens by telling taxpayers who haven't integrated the alternate mechanisms to coordinate with their "system integrators, IRPs, ERPs, GSPs, or ASPs" to enable redundancy. The advisory then lists what already exists:

IRPURLOperator
NIC-IRP 1einvoice1.gst.gov.inNIC (government)
NIC-IRP 2einvoice2.gst.gov.inNIC (government)
Cygnet IRPeinvoice3.gst.gov.inCygnet
Clear IRPeinvoice4.gst.gov.inClear
EY IRPeinvoice5.gst.gov.inEY
IRIS IRPeinvoice6.gst.gov.inIRIS

This isn't six vendors competing for the same job — it's the legal architecture itself built for more than one. Rule 48(4) of the CGST Rules doesn't name an IRP at all — "IRP" is GSTN's own vocabulary, not a statutory term — it just requires reporting to "the Common GST Electronic Portal". Notification 69/2019-Central Tax notifies einvoice1 through einvoice10.gst.gov.in as that portal, "managed by the Goods and Services Tax Network" — ten numbered slots were reserved from the start; six are live as of this advisory, with no later GSTN advisory revising that count as of 28 October 2026.

What "registering a backup" actually means

GSTN's advisory draws a clear line between the two government-run NIC portals and the four private ones. NIC-IRP 1 and NIC-IRP 2 are "interoperable, allowing seamless switch-over between them during service disruptions", and a single authentication token generated on either one — the advisory says the same token also spans both e-way bill portals — "is valid across all NIC portals, eliminating the need for separate tokens for each platform." For the government pair, there is nothing extra to register: the same e-invoice portal login works on both (GSTN advisory of 16 July 2024 on integrated NIC-IRP 1/2 services), and the advisory's own recommended action is to verify your ERP or GSP actually exercises that, not to assume it.

The four private IRPs — Cygnet, Clear, EY and IRIS — are separate commercial operators, and the advisory is explicit that "if NIC-IRP is down, any of the other e-Invoice IRPs listed above could also be used." But it stops at naming them as available; it does not publish a step-by-step onboarding flow for each one. Each private IRP runs its own sign-up and credential process, which GSTN doesn't document — confirm the steps directly with the provider you're onboarding rather than assuming they mirror NIC's. What the advisory does give you for free is a place to rehearse the switch before you need it: the NIC sandbox at einv-apisandbox.nic.in, where the NIC-IRP 1 ↔ NIC-IRP 2 switch-over can be tested without touching production invoices.

For a system wired to call the government IRP directly by API, the advisory also documents the actual interoperability mechanism between the NIC pair: pass "NIC1" in the irp header to call NIC-IRP 1's services via NIC-IRP 2's API base (api.einvoice2.gst.gov.in), or "NIC2" the other way via api.einvoice1.gst.gov.in. Supported cross-operation calls are Get IRN Details, Cancel IRN, Get IRN Details by Document Details, Generate e-Way Bill by IRN, and Get e-Way Bill Details by IRN — a narrower set than everything each IRP can do on its own, notably excluding generating a new IRN, so confirm with whoever built your integration that it actually uses this header rather than hard-coding one base URL.

The e-way bill side has the same design

Redundancy isn't only an e-invoicing concern. GSTN provisions two e-way bill portals — eWaybill1 and eWaybill2 — released, per GSTN's advisory of 28 May 2024, on 1 June 2024 with a limited set of critical services, using the main e-way bill portal's login credentials; GSTN's 24 January 2025 advisory adds that a single authentication token works across both e-way bill portals and the NIC e-invoice pair. GSTN's follow-up advisory of 16 June 2025 describes a broader set of cross-portal services — e-way bill generation from Part-A, consolidated e-way bills, validity extension and transporter-detail updates — from 1 July 2025, in addition to the generation, vehicle-update and printing cross-functions already available; GSTN said the same services would also be made available via API. If your e-way bill workflow only ever talks to one of the two hosts, that's the equivalent gap to a single-IRP e-invoicing setup — same architecture, same fix.

Multi-portal redundancy doesn't override a filing-status block. Rule 138E stops a registered person from furnishing Part A of an e-way bill for their own outward movements once they've defaulted on filing — two consecutive tax periods of the main return, GSTR-1 for any two months or quarters, or CMP-08 for two consecutive quarters under composition. That block sits at the GSTN system level, not on any one portal, so switching IRPs or e-way bill hosts does nothing for it. It's a separate problem with a separate fix: file the outstanding returns, or apply to your jurisdictional Commissioner in FORM GST EWB-05 (Rule 138E, first proviso).

Where the GSP sits in this picture

Most ERPs and accounting platforms don't talk to an IRP directly — they go through a GST Suvidha Provider. GSTN's own description of the architecture, from its advisory on upcoming security enhancements (17 July 2025): an Application Suvidha Provider (ASP) "uses GST System authorised API channel partners that are called GST Suvidha Providers (GSP)", and "the role of a GSP is to provide API access between GST System and ASP." In practice, the first step is confirming your GSP's own integration can route to more than one IRP or e-way bill host — the redundancy GSTN built at the portal level is only useful to you if the layer in between is configured to use it.

One thing worth saying plainly, because it circulates as settled fact in GST forums and it isn't: no GSTN or NIC advisory publishes an invoice-volume or turnover threshold that determines eligibility for direct API access to the e-invoice or e-way bill systems — as of 24 August 2026, GSTN's News & Updates feed (items 380–669) carries no such criterion. Treat any vendor-quoted cutoff for "you qualify for direct API access" as unconfirmed until you see it on a GSTN or NIC page yourself.

What happens with only one IRP configured

This isn't theoretical. A thread on CAclubindia's experts forum — "E Invoice Portal Not Working Urgent" (24 February 2023) — shows the shape of the problem: a business with goods to move, the e-invoice portal down. The expert's advice was to wait if the consignment could wait, and he noted that legally, goods sold can't move without an e-invoice. Under Rule 48(5), an invoice that should have gone through the IRP but didn't "shall not be treated as an invoice." That thread predates GSTN's multi-IRP setup. Today the better answer to "the portal is down" is a second IRP you've already tested, not a choice between waiting and shipping on an invoice that doesn't count.

Recoup doesn't register IRPs or route e-invoice traffic — that's the ERP, GSP and IRP layer's job. Recoup works on the purchase side: it continuously reconciles your purchase register against GSTR-2B and names the vendor and invoice behind every ITC gap — the kind of check that's painful to do manually. It's a different problem from portal downtime, but it compounds the same way: the longer either goes unnoticed, the more it costs to unwind.

A continuity checklist

  • Confirm both NIC IRPs work with your current login — the 16 July 2024 advisory says they share login credentials, and the 24 January 2025 advisory says one token works across both; test it rather than assume your ERP's integration actually calls the second one.
  • Register at least one private IRP (Cygnet, Clear, EY or IRIS) as a named fallback, through that provider's own onboarding — don't wait for an outage to start that process.
  • Test the NIC-IRP 1/2 switch-over in the NIC sandbox (einv-apisandbox.nic.in) before relying on it in production; test any private IRP through that provider's own test environment.
  • Check your e-way bill side the same way — confirm your system can reach both eWaybill1 and eWaybill2, not just the one it was originally configured against.
  • Ask your GSP directly whether its own integration supports routing to more than one IRP or e-way bill host — the portal-level redundancy is wasted if the layer in between is pinned to one.
  • Separately, keep an eye on filing status — Rule 138E stops Part A of your outward e-way bills once returns or GSTR-1 go unfiled, however many portals you've configured. An unanswered DRC-01B or DRC-01C intimation doesn't block e-way bills directly, but it does bar your next GSTR-1 (Rule 59(6)). Leave that unfixed and you can end up in a Rule 138E block.

Continuity on the purchase side, too

Recoup reconciles your purchase register against GSTR-2B continuously and names the vendor and invoice behind every ITC gap — before you file, not after.

Book a demo →

Related guides