Turning on GST e-invoicing in ERPNext is one setting. What happens after it is what protects your buyer's input tax credit. On submit, the India Compliance app (Resilient Tech's GST app for ERPNext) sends your B2B invoice to the Invoice Registration Portal, gets back a 64-character IRN and a digitally signed QR, and stores both on the document. Only then is it a valid tax invoice. This guide walks the round-trip, the five ways it fails without telling you, and the period-close check that finds invoices that never got an IRN.
An invoice that needs an IRN and doesn't have one is not a technicality: under Rule 48(5) it is not treated as an invoice, and your buyer's ITC depends on it. I am Manoj, and I lead ERPNext and Frappe work at MithTech, a team of Frappe specialists in Bengaluru. This round-trip is one of the first things we check on an Indian implementation, and part of our ERPNext GST and e-invoicing setup.
Are you even in scope?
Before the mechanics, confirm which rules apply to your turnover: e-invoicing and the 30-day reporting limit have different thresholds.
Calculator
e-Invoice Applicability Checker
Enter your aggregate annual turnover and whether you raise B2B documents to see whether e-invoicing is mandatory and whether the 30-day reporting rule applies.
How does the round-trip work, step by step?
When you submit a B2B Sales Invoice on a configured instance, the india_compliance app runs a sequence that ends with a legally valid invoice — or does not:
- Build the JSON. The app assembles the invoice into the IRP's schema: supplier and recipient GSTINs, line items with HSN, taxable value, tax breakup, place of supply.
- Send to the IRP. It authenticates with the API user saved in GST Settings, through India Compliance's API service, and submits the JSON to the Invoice Registration Portal.
- Receive the IRN + signed QR. The IRP validates and returns a 64-character SHA-256 IRN plus a digitally signed QR embedding the mandated parameters (supplier GSTIN, recipient GSTIN, invoice number and date, invoice value, line-item count, main HSN, and the IRN/hash).
- Stamp the document. The app stores the IRN, QR, acknowledgement number and date on the Sales Invoice.
- Render on the PDF. The Print Format shows the IRN and QR on the face of the invoice.
Only after step 4 is the document an invoice under Rule 48(5). If any step fails, you have a booked sale without a valid tax invoice, and your buyer's ITC under s.16(2)(a) is exposed.
Where the round-trip breaks
Five failure points cover most real cases. Each fails differently and needs a different fix.
Interactive
IRN Round-Trip Failure Decider
Select where the IRP round-trip broke to get the underlying cause and the correct fix — retry, data correction, template fix, or credit note.
The one that surprises people is the PDF that has an IRN in the system but doesn't show it, common when a custom Print Format drops the QR block. The invoice is valid, but the copy you send doesn't show it, and a careful buyer will reject it. The other trap is treating a missed cancellation as an ERPNext cancel: after 24 hours the IRP won't cancel the IRN, so cancelling only in ERPNext leaves your books and the portal out of step. The e-invoice deadlines guide covers that window.
Configure, verify, reconcile
Code recipe
Configure · Verify · Reconcile · Prevent
Copy-paste the configuration steps, the per-document verification, the period-close reconciliation report india_compliance omits, and the habits that keep the round-trip healthy.
0 of 4 steps done
Tick a step’s number when it is done; the ticks stay on this device.
Confirm applicability, then configure
Establish which rules apply to your turnover, then enable e-invoicing in GST Settings, add the API credentials (GST Settings → Credentials) and your India Compliance account, and confirm that submitting a Sales Invoice generates the IRN and signed QR. Test the flow in sandbox mode first; the sandbox rejects the same data the live portal will.
Verify every B2B document
On each submitted B2B invoice, confirm the IRN (64 characters), the signed QR, the acknowledgement number, and an e-invoice status of Generated. If it reads Pending or Failed, open the e-invoice log for the exact IRP error. Most are GSTIN, HSN or place-of-supply checks that the portal enforces more strictly than ERPNext does on submit.
Render IRN and QR on the buyer's PDF
Use the e-invoice-aware Print Format, or add the IRN and QR block to your custom template. Both must appear on the face of the invoice. Lock this into your template review so a bespoke format never ships without them.
Reconcile at period close
Build a Query Report of every B2B Sales Invoice in the period whose e-invoice status is not Generated. Run it before every GST return. Each row is a booked sale without a valid invoice and with your buyer's ITC exposed. The GST return filing guide covers where these surface in GSTR-1. Resolve all of them before you file.
When accounts submit and IT owns the portal
The person submitting the invoice is in accounts; the person who set up the API connection and owns the e-invoice queue is in IT or with the implementer. The failure lives in that gap: an invoice submits, the IRP is briefly unreachable, and no IRN comes back. The accounts user sees a submitted invoice and sends the PDF. The customer's ITC now sits on a document that isn't an invoice, and nobody notices until reconciliation or a complaint.
The control is a queue nobody has to remember. Make the e-invoice reconciliation report a standing item on the pre-filing checklist, owned by whoever signs the GST return, and set a rule that no B2B PDF goes out until its status reads Generated. That turns a slow, unseen exposure into a same-day catch.
Draft policy for your finance and IT leads to ratify. No B2B invoice PDF is delivered to a customer until its e-invoice status is Generated and the IRN and signed QR appear on the document. The e-invoice queue is reviewed daily; any Pending or Failed document older than one working day is escalated. Before every GST return, the reconciliation report of non-Generated B2B invoices is run and cleared to zero. IRN cancellation is attempted only within the 24-hour window; beyond it, a credit note is raised. Confirm the reporting-period treatment with your CA before this enters an SOP.
Fix it now, or let it wait for period close?
| The buyer needs the invoice to claim ITC this period | Internal document, no immediate ITC pressure |
| The 30-day reporting window is close | Plenty of window remaining before the deadline |
| It is a high-value invoice | Immaterial value, low risk |
| The customer has already queried the missing QR | No downstream party is waiting |
| You are near a GST return filing date | Filing is weeks away |
At a glance
| Aspect | What to know |
|---|---|
| Who it applies to | AATO over ₹5 crore in any FY since 2017-18: B2B invoices, credit and debit notes, exports |
| What makes the invoice valid | IRN and signed QR from the IRP (Rule 48(4), 48(5)) |
| Cancel window | 24 hours from IRN generation; after that, a credit note |
| Check before filing | Report of B2B invoices whose e-invoice status is not Generated |
FAQ: what do people ask most?
Why is my e-invoice not generating in ERPNext?
Most often the IRP rejected the document on validation — an invalid recipient GSTIN, a missing or wrong HSN, or a place-of-supply mismatch — so no IRN was issued even though the Sales Invoice submitted. Open the e-invoice log for the exact IRP error, fix the data, and regenerate. Do not deliver the PDF until the IRN and QR are on it.
What turnover makes GST e-invoicing mandatory in ERPNext?
As checked on 12 October 2026, e-invoicing applies to B2B invoices, credit notes, debit notes and exports where aggregate turnover exceeded ₹5 crore in any financial year from 2017-18 (Notification 10/2023-CT), unless your entity type is exempt. The separate 30-day reporting limit applies at ₹10 crore AATO and above. Confirm the current notification for your period with your CA.
What happens to my buyer's ITC if the IRN fails?
Without a valid IRN the document is not treated as an invoice under Rule 48(5), and s.16(2)(a) makes ITC depend on holding a tax invoice, so your buyer's claim is at risk. It is your failure as the supplier, but it lands as a cash-flow problem on the buyer, who will chase you for a valid invoice.
Can I cancel an IRN in ERPNext after generating it?
Only within 24 hours of IRN generation, which maps to the standard Cancel action. After 24 hours the IRP will not cancel the IRN, and a credit note against the reported invoice is the only correction. Cancelling only in ERPNext beyond the window leaves your books and the IRP permanently inconsistent.
The IRN generated but the QR isn't on the printed invoice — why?
The IRN and signed QR are stored on the document, but your Print Format is not rendering them — almost always because a bespoke customer template overrides the standard e-invoice format and omits the QR block. Add the IRN and QR block to the custom template; a compliant invoice must show both on its face.
Does e-invoicing apply to B2C sales?
The IRP mandate covers B2B documents, exports and supplies to SEZ or deemed exports — not pure B2C sales, which have a separate dynamic-QR requirement for large taxpayers. If you raise any B2B document at all, the e-invoicing mandate applies to those regardless of your B2C volume.
What related issues might you also hit?
- The e-invoice 30-day and 24-hour deadline rules that decide whether a fix is a retry or a credit note.
- GST return filing in ERPNext — where a missing IRN shows up in GSTR-1.
- ERPNext GST 2026 readiness — the wider compliance checklist.
- The GST e-invoicing setup guide — first-time configuration.
What is the bottom line?
The e-invoice setting is easy to turn on; the round-trip behind it is where compliance lives. Confirm which rules your turnover triggers, check the IRN and QR on every B2B document before it goes out, and clear the failures at period close instead of hearing about them from a buyer.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 31 July 2026
Worked with us? Leave a Google review