TallyPrime can generate an IRN in one click. The one-time registration decides whether it ever will

e-Invoicing under Rule 48(4) isn't a TallyPrime feature so much as a legal reporting step TallyPrime happens to automate. The mechanics inside Tally are simple once it's wired up. The registration in front of it — two separate credential sets, on two different screens, easy to treat as one — is where most businesses lose the first few weeks.

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 feature GSTN designed around TallyPrime. 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 September 2026, 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. The "any preceding year" wording is the part worth sitting with: once you cross Rs 5 crore in a single year, e-invoicing applies to you permanently — it does not 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.gst.gov.in family of sites, "managed by the Goods and Services Tax Network"), not a term Rule 48(4) itself uses. The consequence for 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 gets to a reconciliation screen.

The one-time registration: two credentials, easy to conflate

Per TallyPrime's own setup documentation, getting e-invoicing working is not one registration — it's two, on two different parts of the e-invoice portal, and TallyPrime's screens don't loudly distinguish them. Both assume the GSTIN has already completed e-Invoice Enablement on the e-invoice portal — GSTIN, OTP, turnover and financial year — a prior, separate step from either credential below:

• An IRP login — your ordinary registration on the e-invoice portal (einvoice1.gst.gov.in), the credential you'd use if you logged in through a browser yourself.
• A separate API user profile — created specifically for machine-to-machine access, where you select a GST Suvidha Provider and set a distinct username and password for that channel. For TallyPrime's own direct integration, that means choosing "Tally (India) Private Ltd" as the GSP.

These are not the same login used two ways — they are two separate credential sets, the API one created inside your IRP account. Which one TallyPrime asks for is the counter-intuitive part. The GSP API profile exists so Tally's channel is authorised against your GSTIN, but the credentials you type into TallyPrime's e-Invoice login screen are the IRP ones. Tally's documentation is explicit: "The API user credential is different from the IRP credential. You will need to use the IRP credentials whenever you need to log in to the e-Invoice screen in TallyPrime." Entering the API username and password at that prompt is the commoner mistake.

Turning e-invoicing on inside TallyPrime

Once both registrations exist, the in-app configuration, per TallyPrime's own one-time setup guide, is a short F11 sequence:

TallyPrime's documentation is also specific about two things that break e-invoicing later even when this setup is correct: HSN/SAC codes and tax rates have to be correctly entered in ledgers and stock items, and party masters need a complete address, pincode and GSTIN/UIN before the first e-invoice against that party — the IRP validates these fields on upload and rejects the document, not the voucher, if they're wrong. Exporters additionally need ISO currency codes updated under Alt+G > Alter Master > Currency. Access itself is a separate lever: TallyPrime's user-rights settings can restrict which users are allowed to upload e-invoices to the IRP at all, which is worth deciding deliberately rather than leaving open by default.

Generating an IRN, voucher by voucher

With setup done, TallyPrime's IRN generation flow runs inside the ordinary sales voucher:

1. Record the GST sales voucher as usual — party, sales ledger, item, GST ledger. TallyPrime's own guidance flags one formatting rule worth checking before you're deep into a filing period: avoid starting invoice numbers with a zero, a slash or a hyphen, since the IRP's own document-number validation rejects them.
2. Set "Provide e-Invoice details" to Yes. On the first transaction with a given party, the e-Invoice Details screen asks for Bill To and Ship To places; press Ctrl+A to save.
3. Press Ctrl+A to save the voucher itself — a prompt appears asking whether to generate the e-invoice now.
4. Confirm, and enter the e-invoice login credentials at the prompt — this is the IRP login from the first registration, not the GSP API profile.
5. On success, TallyPrime writes the IRN details back into the voucher and shows a confirmation message. Printing the invoice at that point includes the IRN and QR code.

A related F12 setting is worth knowing if e-way bills are also part of your workflow: "Send e-Way Bill details with e-Invoice" lets the same voucher generate both in one step, instead of a second, separate e-way bill registration and API call — that's a different GSP credential set again, covered in our e-way bill GSP setup guide, though Tally's e-invoice page notes the reverse direction: if you already have an e-Way Bill profile and are using it to generate e-way bills in TallyPrime, you need not create another API user profile for e-invoicing.

Video walkthrough by Accounts Advice — embedded with credit; the guide above is our own.

What happens when IRN generation fails silently — and whose credit it costs

The registration step above is easy to treat as an internal Tally problem: if it's not done right, IRN generation errors out and someone in accounts eventually notices and fixes it. That's true for the supplier. It is not the whole story for the supplier's customer. e-Invoicing data is designed to flow straight into the supplier's GSTR-1 and, from there, into the recipient's GSTR-2B — but that only happens once an invoice actually clears the IRP. An invoice that never gets a valid IRN — because the API registration was never completed, the GSP profile pointed at the wrong provider, or a rejected upload was never retried — does not auto-populate into the supplier's GSTR-1. GSTN's advisory on auto-population of e-invoice details into GSTR-1 (30 November 2020) is explicit that this is not the end of the road: auto-populated records can be edited or deleted, and "taxpayers can add invoices not appearing in GSTR-1 in respective tables of GSTR-1". So a failed IRN does not by itself keep the invoice out of the buyer's GSTR-2B — it does that only where the supplier never adds it manually either. Two distinct failures follow, and they bite differently. Where the supplier reports nothing, the invoice never reaches the recipient's GSTR-2B under Rule 60(7), and the recipient's ordinary vendor-credit claim fails under Section 16(2)(aa) read with Rule 36(4)(b). Where the supplier does key it in manually, it reaches 2B and matches cleanly — but it is still an invoice that "shall not be treated as an invoice" under Rule 48(5), so the exposure moves to Section 16(2)(a) instead, and a 2B match will not surface it at all. Where the supplier never adds it back, it costs the customer real, blocked credit on the very next return, with nothing in the customer's own workflow to explain why. 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 that actually matter here

TallyPrime's own rejection-and-resolution reference lists a long set of IRP validation errors — most are data-quality issues (address fields too short, an invalid pincode, a document number that fails the IRP's own format check) rather than registration problems. A handful are worth knowing before they show up mid-filing-period:

Where this sits next to the rest of the filing chain

Getting IRN generation working is table stakes, not the finish line. GSTN had separately proposed making Ship-to GSTIN conditionally mandatory on the e-Invoice and e-Way Bill APIs — only where ship details are provided and an e-way bill is required — that change remains on hold as at September 2026, per GSTN's Advisory No. 668, with no replacement date announced. Nothing in the setup above needs to change for it. And once your own outward invoices are clearing the IRP reliably, the inward side of the same problem — matching what lands in your GSTR-2B against your purchase register — is a separate, ongoing exercise, covered in our GSTR-2B reconciliation workflow for TallyPrime and, at the level of the whole reconciliation cycle, in our GST reconciliation guide.

Related guides