For many growing Indian businesses, e-invoicing arrives as an accountant's warning: "We have crossed the limit, from next month every B2B invoice needs an IRN." What follows is often a scramble of downloading JSON files from the billing software, uploading them to the portal by hand, and copying the IRN and QR code back. It works for twenty invoices a month. It breaks at two hundred.
This guide explains what changes when your turnover crosses the threshold, the three ways to connect your billing software to the Invoice Registration Portal (IRP), and the integration mistakes that cause rejections. Rules change often, so treat the dates below as a starting point and confirm current limits on the GST portal and with your CA.
Who must generate e-invoices under GST?
E-invoicing has been extended in stages by lowering the turnover threshold. CBIC Notification No. 10/2023 – Central Tax, dated 10 May 2023, extended mandatory e-invoicing to registered persons whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds ₹5 crore, with effect from 1 August 2023. It applies to business-to-business (B2B) supplies, not to ordinary sales to consumers.
The phrase "any preceding financial year" catches people out. If your turnover crossed ₹5 crore in any year since 2017-18, the obligation applies even if this year's sales are lower.
An invoice under the e-invoicing system is valid only once it is registered with an IRP, which validates it, assigns a unique Invoice Reference Number (IRN), digitally signs it and returns a signed QR code. The buyer relies on that registration to claim input tax credit, so a missing or late IRN is not a paperwork issue; it affects your customer's ITC and therefore your relationship.
What is the 30-day reporting limit?
A GSTN advisory dated 5 November 2024 extended a reporting time limit to taxpayers with aggregate annual turnover (AATO) of ₹10 crore and above, from 1 April 2025. Such taxpayers cannot report an invoice, credit note or debit note to the IRP if it is older than 30 days on the date of reporting.
In practice this means the old habit of "we will upload the month's invoices at month-end" is risky for anyone near or above ₹10 crore. A document that misses the window cannot get an IRN, and the business has to deal with the consequences with its CA. Automated, same-day IRN generation removes the problem.
API, GSP or manual: which route fits your business?
| Route | How it works | Suits | Watch out for |
|---|---|---|---|
| Manual / offline utility | Export JSON from billing software, upload on the IRP portal, copy IRN and QR back | Very low invoice volume, occasional use | Errors, delays, the 30-day limit, staff dependency |
| Built into accounting software | Your accounting product (for example TallyPrime or an ERP with an India compliance module) talks to the IRP directly | Businesses billing from one standard product | Only covers invoices raised in that product |
| Through a GSP or ASP | A GST Suvidha Provider offers an API; your custom software sends invoices to it, it handles IRP communication | Custom billing systems, multiple GSTINs, high volume | Per-invoice or subscription cost, vendor dependence |
| Direct API with the IRP | Your system calls the IRP API itself after registering for API access | Large taxpayers with in-house IT | Eligibility, security, credential management, upkeep |
For most mid-sized businesses with a custom billing app, e-commerce backend or ERP, the GSP route is the practical one. If you already use an open-source ERP such as ERPNext, community apps like India Compliance provide e-invoice and e-way bill integration with the IRP, plus GSTR reconciliation.
What does a proper integration look like?
- Invoice saved in billing system with a status of "pending IRN".
- Validation before sending: GSTIN format, state codes, HSN length, pincode, mandatory fields. Catch errors locally rather than at the portal.
- Send to IRP (directly or via GSP) and receive IRN, acknowledgement number, date and signed QR code.
- Store the response against the invoice and lock it from editing.
- Print the QR code on the invoice PDF and send it to the customer.
- Handle failures: put failed invoices in a queue visible to the accounts team with the exact error message, and retry automatically for timeouts.
- E-way bill, where needed, generated from the same data in the same flow.
- Daily reconciliation report: invoices raised versus IRNs received, so nothing older than a day or two sits unreported.
Which mistakes cause IRN rejections?
TallyPrime's own help documentation lists the rejection reasons its users run into. The recurring ones are a useful checklist for any integration:
- Duplicate IRN: the same document number sent twice. Often caused by a timeout on the first attempt; your system thinks it failed and resends. Fix: before resending, query the IRP for the existing IRN by document details and store it.
- Document date too old for taxpayers above the turnover limit for the 30-day rule.
- GSTIN inactive, cancelled or invalid, or state code mismatched with the GSTIN. Validate buyer GSTINs when the customer master is created, and re-check periodically.
- HSN problems: invalid codes, or fewer digits than required for your turnover. Keep an HSN master and validate item codes against it.
- Address and pincode errors: fields too short or long, invalid pincodes, pincode not matching state.
- Document number format: characters or lengths the schema does not allow.
- Rounding and value mismatches: line totals that do not add up to the invoice value because of rounding rules in your software.
Most of these are master-data problems, not API problems. Cleaning the customer and item masters before go-live prevents the majority of rejections.
How should you handle credit notes and cancellations?
Credit and debit notes also need IRNs and fall under the 30-day rule for taxpayers in scope. Cancellation of an IRN is allowed only within a short window and under conditions, so build a clear workflow: cancellation in the billing system must trigger cancellation at the IRP, and after the window closes the correction should be a credit note, not an edit. Confirm the current cancellation rules with your CA before you design this screen.
A go-live checklist
- Confirm applicability with your CA, GSTIN by GSTIN.
- Clean customer GSTINs, addresses, pincodes and HSN codes.
- Choose the route (built-in, GSP or direct) and register API access.
- Test in the sandbox with real-looking invoices, including credit notes and exports.
- Build the failure queue and daily reconciliation report before go-live, not after.
- Train the accounts team on what each error means.
- Keep an audit trail of every request and response; it helps in disputes and audits.
How Cehpoint can help
We build and integrate billing, ERP and CRM systems for Indian businesses, including automated IRN and e-way bill generation through a GSP or ERP compliance module, failure queues and reconciliation reports. See our CRM and ERP software development service. If you run an accounting or CA practice, our accounting practice software page covers tools for firms, and for broader process automation see business process automation.