GST e-invoicing, integrated properly
Generating an IRN should be something your system does, not something a person does on a portal.
E-invoicing is straightforward to comply with badly — by uploading on a portal — and only slightly harder to do properly, as part of the invoice being raised.
Typical timeline: Live in 3–5 weeks
The IRN arrives as the invoice is raised
These are the signs this is worth doing
If several of these are true, this is usually where the fastest return sits.
E-invoicing obligations have been extended downward in stages since 2020, each phase pulling in businesses at a lower aggregate annual turnover. If you are near the current threshold, assume you will be inside it rather than outside — the direction of travel has only gone one way. Confirm the figure that applies to you with your CA, because it has changed repeatedly and any number stated on a web page ages badly.
The compliance itself is not complicated. An invoice is reported to the Invoice Registration Portal, which returns an IRN and a signed QR code that must appear on the document. What varies enormously is how that happens in practice.
Two ways to be compliant
Both satisfy the law. Only one survives volume.
Portal upload
- A person exports, uploads, and copies the IRN back
- Works at low volume, fails quietly at higher volume
- Invoices can be issued before reporting, or missed entirely
- Cancellation windows get missed
- Reconciliation is a manual comparison
Integrated at the point of billing
- The IRN is obtained as the invoice is raised
- No document leaves without its QR code
- Failures are queued, retried, and visible
- Cancellation and amendment handled in the same flow
- Reported status is a field, not an exercise
The details that actually cause trouble
The happy path is easy. What causes problems is everything else, and it is worth knowing before you scope this work.
Cancellation has a limited window after IRN generation, after which the only remedy is a credit note — so the system has to know the difference and guide the user to the right one. Duplicate reporting must be prevented, because the same invoice reported twice is a reconciliation problem that surfaces months later. The IRP is not always available, so requests need queuing and retry rather than a failure message the user dismisses. And schema validation is strict about things people get casually wrong: HSN codes, place of supply, unit codes, and rounding.
We build these as part of the flow rather than as exceptions handled later, because every one of them is discovered eventually — the only question is whether it is discovered by your system or by an audit.
What the integration includes
- IRN and signed QR code obtained automatically at the point the invoice is raised.
- Queued, retried requests so an IRP outage does not stop billing.
- Duplicate prevention, so one invoice is never reported twice.
- Cancellation within the permitted window, and credit-note guidance outside it.
- E-way bill generated from the same data where the consignment requires it.
- A reported-status view and a reconciliation report against your books.
Compliance you can only demonstrate by exporting a spreadsheet and comparing it by hand is compliance you cannot really demonstrate.
We would rather tell you now than three weeks into a project. This work is usually the wrong call if any of the following describes you.
- Businesses genuinely below the threshold with no near-term prospect of crossing it. Do not build for an obligation you do not have.
- Very low invoice volumes where portal upload is honestly sufficient — a handful a week does not justify an integration.
- Anyone whose billing data quality is poor. Fix HSN codes and master data first; the IRP will reject what your current process tolerates.
The systems involved
We integrate rather than replace wherever it makes sense. These are the systems this work most commonly touches.
GST e-invoicing — questions we get asked
Do we need a GSP?
Usually yes. Direct IRP access has stricter onboarding requirements, so most businesses connect through a GSP or ASP. We are not tied to one and will integrate with whoever you choose, or help you choose.
What is the current turnover threshold?
It has been lowered several times since 2020, so we deliberately do not quote a figure here that would age badly. Confirm the current limit with your CA. If you are near it, build as though you are inside it.
What happens if the IRP is down when we invoice?
The request is queued and retried; billing continues. Once reported, the IRN and QR code attach to the invoice. What you must not do is issue the document as final without them, and the system enforces that.
Can this work with Tally?
Yes. Either through Tally's own e-invoicing features where they fit your process, or via an integration layer where the invoice originates in another system.
The services this work sits inside
Where this comes up most
The sectors where we most often do this work, and where the payback is usually clearest.
Others worth reading
E-way bill generation without the data entry
E-way bill data already exists in the invoice. Generating the bill from it — with validity, extension, and part-B updates handled — removes a step that regularly delays dispatch.
Read itIntegrationIntegrating Tally with the rest of your systems
Tally's XML and ODBC interfaces are awkward but dependable. Wrapped properly, they let your website, CRM, or operations system exchange data with Tally without anyone re-keying.
Read itThinking about gst e-invoicing?
Start with a short conversation. We will tell you honestly whether this is the right place to begin, or whether something else pays back faster.