How-to · BUSY & e-invoicing

BUSY can generate an IRN the moment you save a voucher. One skipped voucher series and it never asks at all

The short answer

BUSY e-invoicing setup needs a GSP ID created on a government portal — BUSY's e-way-bill FAQs document Registration > For GSP on the e-Way Bill portal, while a separate e-invoice FAQ documents API Registration on the e-invoice portal, so confirm which applies to your version — pasted into BUSY's own GST/VAT configuration under Administration, and two further settings on top of that — a voucher-series toggle and a per-voucher transport-details confirmation — before the IRN prompt appears at all. For a business covered by Rule 48(4), an invoice that never gets a valid IRN isn't a legal tax invoice, so the buyer can't claim ITC on it.

BUSY's own FAQ pages document a working e-invoicing setup — GSP registration, a GST/VAT configuration screen, a voucher-series toggle that fires the IRN prompt on save. What they don't flag clearly is that the GSP registration step is documented on the e-Way Bill portal rather than inside BUSY, and that the IRN prompt itself needs four separate settings — a company-level GST/VAT toggle, two per-voucher-series toggles, and a per-voucher transport-details confirmation — so a second sales voucher type added later, missing any one of the four, saves silently with no IRN and no error at all.

What Rule 48(4) actually requires, and what "IRP" means

e-Invoicing is a reporting mechanism under Rule 48(4) of the CGST Rules, not a BUSY feature. The rule itself fixes no threshold — it delegates the coverage test to a notification. Under Notification 13/2020-Central Tax dated 21 March 2020, as amended — most recently, as at 16 July 2026 (CBIC notification database), by Notification 10/2023-CT w.e.f. 1 August 2023 — any registered person, other than a government department, a local authority, an SEZ unit, and insurers, banks/NBFCs, goods transport agencies, passenger transport suppliers and multiplex-cinema suppliers covered by Rule 54(2)-(4A), whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds Rs 5 crore must report B2B invoices, credit and debit notes, and exports, through the portal. That "any preceding year" wording matters more than it looks: once turnover crosses Rs 5 crore in a single year, e-invoicing applies permanently — it doesn't switch off if turnover later falls back below the line.

"IRP" — Invoice Registration Portal — is GSTN's own vocabulary for the notified system (Notification 69/2019-CT names the einvoice1-10.gst.gov.in family of sites, "managed by the Goods and Services Tax Network"), not a term Rule 48(4) itself uses. The consequence of a missed or invalid registration sits in the neighbouring rule, not 48(4): under Rule 48(5), an invoice that should have gone through this process but didn't "shall not be treated as an invoice" at all — which is why a buyer's ITC claim on it fails under Section 16(2)(a), long before anyone reaches a reconciliation screen.

GSP registration for BUSY happens on a government portal, not inside BUSY

Per BUSY's own FAQ pages, BUSY supports two named GSP (GST Suvidha Provider) options for automatic e-invoice and e-way bill generation: "BUSY support both GSP server Webtel Electrosoft Private Limited and Pinnacle Finserv Advisors Private Limited for automatic E way bill and E invoice." Where BUSY's documented flow departs from a pattern you may recognise from other accounting software: the GSP ID isn't created inside BUSY itself, and BUSY's own FAQs point at two different government portals for doing it (more on that below). The route BUSY's e-way bill FAQs document runs through the e-Way Bill portal:

  1. Log in to the e-Way Bill portal, click Registration, then For GSP.
  2. Click Send OTP and enter the OTP received on your registered phone or email.
  3. Click Add/New and repeat this for each of the two providers BUSY supports — Webtel Electrosoft Private Limited and Pinnacle Finserv Advisors Private Limited — entering a short suffix (BUSY's FAQ says to enter 3 characters) each time, generating a password, and saving the ID.

That ID and password are then entered in BUSY's own GSP Configuration: they are API credentials, separate from the portal login you used to create them. BUSY's FAQs are not consistent on whether the same GSP ID covers both systems: its e-way bill FAQ documents creating the GSP ID on the e-Way Bill portal (Registration > For GSP, as above), while a separate BUSY e-invoice configuration FAQ instead directs you to log in to the e-invoice portal and use its own API Registration menu for the same two providers. Confirm with BUSY support which applies to your version before assuming one registration covers both (BUSY FAQs, as at 21 September 2026).

Turning on e-invoicing inside BUSY

Once a GSP ID exists, the in-app configuration runs through Administration > Configuration > Features & Options > GST/VAT, per BUSY's own FAQ pages:

StepWhereWhat you're doing
1. Enable e-invoicingAdministration > Configuration > Features & Options > GST/VATSet E-Invoice Required to Y
2. Location detailsSame screenEnter Place and Pincode
3. GSP configurationGSP Configuration (same screen)Set GSP Configuration to Automatically, then paste the GSP User ID and password for each provider from the registration above and click Validate
4. SaveSame screenCommits the configuration

The voucher-series settings that actually fire the IRN prompt

Turning e-invoicing on at the GST/VAT level doesn't, by itself, make any individual voucher prompt for an IRN. That's a second layer, and it is two separate settings in the same screen — Administration > Configuration > Voucher Series Configuration — plus one confirmation at voucher entry:

  1. Select the relevant voucher type, then Series > Voucher Configuration.
  2. Enable Input Transport Details (this is the setting that makes the Transport Details window appear at voucher entry) and "Generate E-Invoice after saving voucher", and save — they are two different toggles on the same screen.
  3. At voucher entry, in the Transport Details window, set E-Invoice Required to Y and fill in the transport details before confirming. Selecting Yes to the e-invoice prompt on the bill alone is not enough.

This is the step that's easy to miss precisely because it's configured per series, not once for the company. A business that adds a second sales voucher type later — a separate series for exports, or a branch-specific series — has to repeat these settings for that series specifically. BUSY's documented flow gives no separate warning if you don't: a voucher saved under a series where the toggles aren't set simply saves, with no e-invoice prompt and no IRN, and nothing in that save flow flags it as unusual — including if the Transport Details window was never enabled for that series, or is answered No when it appears.

With all four settings in place, per BUSY's FAQ, the ordinary save flow of a sales voucher opens the prompt itself: record the voucher as usual, save it, and BUSY asks whether you want to generate the e-invoice. Confirming writes the IRN back into the voucher. In the generation window that opens after you save and choose to generate the e-invoice, BUSY's Check All Possible Error window (its FAQs also call it "check possible error") — a window you click into to check whether there are any errors — is worth running on anything unusual, since most of the rejection reasons below are data problems the IRP catches on upload, not registration problems.

Video walkthrough by BUSY Accounting Software — embedded with credit; the guide above is our own.

This guide is written from BUSY's own FAQ pages, not from the video.

Where IRN generation fails silently — and whose credit it costs

Skipping a voucher-series setting isn't the only way this goes quiet. Even with all four settings correctly configured, a voucher can fail the IRP's own validation — an address field too short, a mismatched state, a duplicate invoice number — and BUSY's documented flow leaves that failure inside the save-time prompt, easy to dismiss without registering what it means. Either way, the result on the outward side looks the same: a voucher that saved fine, printed fine in BUSY's own layout, and simply never picked up a valid IRN. That's an internal problem for the supplier until it isn't. e-Invoice data is designed to flow into the supplier's GSTR-1 and from there into the buyer's GSTR-2B — but only once an invoice actually clears the IRP. An invoice that never gets a valid IRN doesn't auto-populate into the supplier's GSTR-1 at all; if the supplier never keys it in manually either, it never reaches the buyer's GSTR-2B under Rule 60(7), and the buyer's ordinary vendor-credit claim fails under Section 16(2)(aa) (the GSTR-2B condition itself runs through Rule 36(4)) — real, blocked credit on the next return, with nothing on the buyer's side to explain why. If the supplier does add it manually, it can still reach 2B and match cleanly — but it remains an invoice that "shall not be treated as an invoice" under Rule 48(5), so the exposure moves to Section 16(2)(a) instead, a failure a clean 2B match won't surface at all. Catching that gap — a supplier whose invoices keep landing without a corresponding, valid entry in 2B — before it becomes a missed ITC claim is exactly the kind of continuous, invoice-by-invoice check that's painful to do by hand across a purchase register with any real vendor count.

The rejection reasons BUSY documents

BUSY's own FAQ pages record a handful of specific error states worth knowing before they show up mid-filing-period:

Error / messageWhat it means, per BUSY's FAQ
"To state does not match"The state code in the account doesn't match the first two digits of the recipient's GSTIN. Fix: Administration > Masters > Account, correct the account's state, and save.
"Invoice IRN number is already available"An IRN already exists for that invoice number. BUSY's FAQ resolution: generate using a different invoice number — re-submitting the same number doesn't produce a second IRN.
Portal unreachablePer BUSY's FAQ, "BUSY is directly linked to the portal" for e-invoice generation, so BUSY's documented advice for a portal-side outage is simply to retry after some time; its FAQs describe no offline queue or retry buffer.
Old-invoice reporting errorBUSY documents a 30-day reporting window to the IRP. See the note below — this restriction is not universal.
The 30-day reporting-age restriction doesn't apply to every taxpayer. Per GSTN's advisory of 5 November 2024, restated on the IRP portals on 27 March 2025, taxpayers with AATO of Rs 10 crore or more cannot report an invoice, credit note or debit note on the IRP if it is more than 30 days old, effective 1 April 2025 — and GSTN states there is no such reporting-age restriction below Rs 10 crore turnover "as of now" (position as at 16 July 2026 per the CBIC/GSTN check on file; IRP configuration is changeable by advisory without notice). A tighter figure — a 3-day window — circulates in secondary coverage and isn't traceable to any GSTN advisory or CBIC notification; treat it as unverified. Separately, a claim that the underlying e-invoicing threshold itself drops to Rs 2 crore also circulates widely; no notification does this as of the register's most recent check (16 July 2026) — the only Rs 2 crore figures actually notified nearby are annual-return filing exemptions, an unrelated provision.

Where this sits next to the rest of the filing chain

Getting IRN generation working reliably in BUSY is table stakes, not the finish line. Once your own outward invoices are clearing the IRP without the silent-failure modes above, the inward side of the same problem — matching what actually lands in your GSTR-2B against your purchase register — is a separate, ongoing exercise, covered in our GSTR-2A/2B reconciliation guide for BUSY and, at the level of the whole reconciliation cycle, in our GST reconciliation guide.

An IRN that never generated doesn't show up anywhere in BUSY. It shows up as your buyer's missing credit.

Recoup reconciles your purchase register against GSTR-2B continuously and names the specific supplier and invoice behind credits that never arrived — including the ones stuck because a vendor's own e-invoicing setup quietly failed.

Book a demo →

Related guides