An invoice without an IRN is not a valid tax invoice. Your buyer loses their input tax credit, and they will find out before you do.
The name misleads people. E-invoicing does not mean emailing a PDF, and it does not mean the government generates your invoice.
You continue to raise the invoice in your own billing software. Before it is valid, that invoice must be reported to the Invoice Registration Portal (IRP), which validates it and returns two things:
An invoice without an IRN is not a valid tax invoice under GST. That single sentence is the whole reason this matters commercially: your buyer cannot claim input tax credit against it.
The obligation is tied to aggregate annual turnover (AATO) across all GSTINs on the same PAN, and the threshold has ratcheted down in stages since 2020 — from ₹500 crore at the start to ₹5 crore since August 2023.
Two things distributors get wrong here:
Certain categories are excluded regardless of turnover — banks and financial institutions, insurers, goods transport agencies, passenger transport, and cinema exhibition among them. For an FMCG distribution business, none of these apply, so assume you are covered and verify the threshold against your own PAN-level turnover.
Reporting is not open-ended. Larger taxpayers face a hard limit on how old an invoice can be when it reaches the portal — a window measured in days from the invoice date, after which the IRP will not accept it at all.
The window has been tightened progressively and applied to successively smaller turnover bands, so the specific number and who it binds is worth confirming on the GST portal for your current turnover band before you design a process around it.
The operational conclusion does not change with the details: report at the point of billing, not in a month-end batch. Batching is how invoices age past the window, and there is no retrospective fix once they do.
Step 5 is the underrated one. Once e-invoicing is running properly, your GSTR-1 is largely assembled for you, and the reconciliation work at month-end drops sharply. Distributors who report diligently through the month get this benefit; those who batch do not.
Wrong HSN, or the wrong number of digits. The IRP validates HSN codes, and the digit requirement scales with turnover — six digits above ₹5 crore, four on B2B invoices below that. A wrong code either rejects the invoice or, worse, passes with the wrong rate and creates an ITC dispute for your buyer months later. The HSN Code & GST Rate Finder covers the common FMCG categories.
Applying pre-reform rates. The GST 2.0 reform of 22 September 2025 withdrew the 12% and 28% slabs, leaving 5% and 18% as the main rates plus 40% for sin and luxury goods. Most FMCG staples moved down to 5%, while detergent and cosmetics stayed at 18%. Billing biscuits at the old 18% is now simply wrong, and it is a mistake that survives in a lot of masters that were never updated. Check yours.
Batching to month-end. Covered above, and it is the single most common cause of invoices that can never be reported.
Treating cancellation as an edit. An IRN can only be cancelled in full and only within a short window. After that, corrections go through credit or debit notes. Teams used to freely editing invoices in Tally get caught by this in the first month.
Discounts applied after the invoice. A discount shown on the invoice reduces taxable value cleanly. A post-sale discount via credit note follows separate conditions and is a frequent audit finding. Where you can, put the discount on the invoice — the Trade Discount Ladder Calculator will give you the net figure to bill.
Do not wait for the turnover to tick over.
For the arithmetic around the invoices themselves, the GST Calculator handles the CGST/SGST split and the Reverse GST Calculator works backwards from an inclusive price — the direction most people get wrong on purchase bills. If a return has already slipped, the GST Late Fee & Interest Calculator will tell you what it costs before you log in to find out.
Connecting all of this to how you actually communicate invoices to retailers is covered in connecting Tally to WhatsApp.
The transition is where errors cluster, because the process is new and volume is unchanged.
Week 1 — parallel running. Generate IRNs but keep your existing invoice checks. Compare every e-invoice against what you would have issued manually. You are looking for classification mismatches and rate errors, not portal failures.
Week 2 — watch the rejections. Every rejection is telling you something specific about your master data. Log the reason codes rather than fixing them one at a time; the same three causes will account for most of them.
Week 3 — reconcile GSTR-1. Check that auto-population matches what you believe you billed. Gaps here are usually invoices that never reached the portal at all, which is precisely the failure that is invisible until filing.
Week 4 — tighten the timing. Move reporting as close to billing as you can. Anything batched is a candidate for ageing past the window.
E-invoicing feels like pure administrative burden, and for the first month it is. After that it starts paying back in two ways worth naming.
GSTR-1 largely assembles itself. Once invoices are reported through the month, the return is populated from data you already submitted. The reconciliation work that used to consume the first week of every month mostly disappears — but only for businesses reporting continuously. Batch at month-end and you keep all the old work plus the new obligation.
Disputes get shorter. A signed IRN is an authoritative record of what you reported and when. Arguments with buyers about what was billed, at what rate, on what date, stop being arguments.
Neither benefit arrives if you treat reporting as a monthly chore. Both arrive automatically if you report at the point of billing.
Worth resolving precisely, because getting this wrong in either direction is expensive.
The obligation follows aggregate annual turnover across every GSTIN on the same PAN — not per branch, not per state. Two units at ₹3 crore each are a ₹6 crore business for this purpose.
Three consequences distributors miss:
If you are anywhere near the threshold, compute it properly at PAN level before assuming you are out of scope.
Understanding what gets checked changes what you keep.
Keep the signed payload the IRP returns, not just your printed invoice. It is the authoritative record of what you actually reported.
Three situations and what to do:
You missed the reporting window. There is no retrospective IRN. Consult your CA about the correct treatment — a credit note and fresh invoice is the usual route, and doing it promptly is better than discovering it at filing.
You billed the wrong rate. Correct it through a credit or debit note. Tell the buyer, because their input tax credit is affected and they will find out either way. Then fix the master so it does not recur.
The portal is down at month-end. This is why batching is dangerous. If you report daily, an outage costs you a day; if you report monthly, it can cost you the window on a whole month's invoices.
For the arithmetic itself, the GST Calculator handles the CGST/SGST split and the GST Late Fee & Interest Calculator tells you the cost of a delay before you log in.
The questions that come up in the first month of e-invoicing.
The IRN requirement covers B2B supplies, exports and supplies to SEZs — not ordinary B2C sales. Larger taxpayers do have a separate dynamic QR code requirement on B2C invoices, which is a different obligation from IRN. For a distributor billing retailers, effectively all of your invoicing is B2B and in scope.
The portal simply refuses the invoice once the window has passed, and there is no workaround — you cannot back-date an IRN. That leaves you holding a document that is not a valid tax invoice, and your buyer without input tax credit. The practical fix is to report at the point of billing rather than batching at month-end.
The e-way bill obligation is separate from e-invoicing, but the systems are connected — you can generate Part A of the e-way bill along with the IRN if you supply transport details. Validity still runs on distance, which the E-Way Bill Validity Calculator will work out for you.
An IRN can be cancelled on the portal only within a short window after generation, and only in full — there is no partial edit. After that window, the correction has to go through a credit or debit note. This is why getting the invoice right the first time matters more under e-invoicing than it did with manual billing.
The FlowKartAI team builds WhatsApp-native ordering for Indian B2B distributors and the kirana stores they serve. We write about distribution economics, GST compliance, and the practical side of putting AI in front of retailers who have never opened an app.
FlowKartAI parses natural language WhatsApp messages into ERP-ready orders in seconds.
Try Free Demo