E-Invoicing Below ₹5 Crore: What Actually Changes in Your Billing Flow

When the e-invoicing threshold dropped from ₹10 crore to ₹5 crore in August 2023, roughly 180,000 more Indian businesses became e-invoice-mandatory overnight. The technical plumbing - JSON schemas, IRN, QR codes - got most of the attention. What got missed was the operational rewiring nobody warned CFOs about.

The three changes nobody talks about

1. You can’t cancel an invoice after 24 hours

Once an IRN is generated, you have 24 hours to cancel it on the IRP. Miss that window and you must issue a credit note - which shows up on your customer’s 2B, which shows up in their reconciliation, which turns into a call.

Old workflow: draft invoice → customer asks for a change → edit invoice → save. Gone. The new workflow requires you to either:

• Generate the IRN only after the customer confirms, OR
• Pair invoice creation with a 24-hour internal QA step

2. E-way bill is now auto-generated (sometimes)

If you have transport details (vehicle number, transporter ID) on the invoice, the IRP will auto-generate the e-way bill alongside the IRN. Sounds nice. The catch: if transport details change later (vehicle swap, different route), you have to cancel the e-way bill separately from the IRN. Some ERPs tie them together incorrectly and end up orphaning the e-way bill.

3. Month-end close got faster

The upside: your GSTR-1 is now auto-populated from IRNs. Instead of uploading JSON, you review what the portal has already pre-filled. For most businesses, this shaves 2-3 days off the filing cycle. It also shifts reconciliation earlier - books must match IRNs throughout the month, not just at filing time.

The threshold itself

• ₹5 crore aggregate turnover (PAN-level, all-India) in any financial year from 2017-18 onwards triggers e-invoicing.
• Once triggered, e-invoicing applies permanently - even if turnover drops below ₹5 crore later.
• Applies to B2B, SEZ, exports, and credit/debit notes. B2C is excluded (for now).

What breaks most often

In our first 100 implementations, the most frequent breakage was surprisingly simple: vendor codes mapped to the wrong GSTIN. The IRP rejects invoices where the seller/buyer GSTIN doesn’t match the registration. If your master data has stale GSTINs from pre-registration days, you’ll see IRN failures every hour until you clean it up.

Budget a week to audit your GSTIN master before e-invoicing go-live. Second-most-common breakage: HSN codes on the invoice are 4 digits when they need to be 6 or 8 depending on turnover. The IRP is pickier than the GST portal.

What we automate

OneFinOps ingests your ERP invoices, normalizes GSTINs and HSNs against live government masters, hits the IRP with retry logic for rate-limits, and reconciles IRN ↔ GSTR-1 monthly. The IRN failures that used to page your tax team at 11 PM are now a Slack alert with an auto-retry.