E-Invoicing for Textile under ₹5 Crore Threshold — IRN Reconciliation

A mid-tier Ludhiana hosiery brand’s finance controller closes the June IRN cycle with 447 B2B tax invoices issued in the month, 447 IRNs generated on the IRP portal, an average IRN generation lag of 8 seconds against a 15-second SLA, and three defective IRNs caught on day 25 that were credit-noted rather than cancelled because the 24-hour window had already closed. GSTR-1 auto-populated for the same period pulled all 447 IRNs plus three amendment rows for the credit-notes into Table 4A (B2B), and the IRP-reported turnover of ₹1.72 crore reconciles to the GSTR-1 outward supplies line within a ₹40,000 gap explained entirely by the three credit notes. This is e-invoicing textile 5 crore threshold IRN reconciliation at a mid-tier Ludhiana hosiery cadence — Notification 10/2023-Central Tax makes the threshold ₹5 crore aggregate from 1 August 2023, and every B2B document issued by a unit above the threshold must carry an IRN.

Quick reference

The reconciliation in one paragraph

A registered person whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeded ₹5 crore (effective 1 August 2023, Notification 10/2023-Central Tax) must prepare every B2B tax invoice, export invoice, credit note, and debit note in Form GST INV-01 and upload the invoice payload to the Invoice Registration Portal (IRP) before issuing the document to the counterparty. The IRP validates the payload and returns a 64-character IRN plus a signed QR code that must be printed on the physical or digital invoice. Under Rule 48(5), an invoice issued in any manner other than through the IRP is not treated as an invoice — the counterparty cannot claim input tax credit and the seller is exposed to defective-invoicing penalties. Once generated, the IRN can be cancelled on the IRP portal within 24 hours (subject to e-way bill state); beyond that, the only remedy is a credit note. IRNs auto-populate into the GSTR-1 e-invoice section on the following day, and the seller reconciles the internal IRN register against the GSTR-1 auto-populated data, the IRP-reported turnover against the GSTR-1 outward supplies, and the GSTR-1 outward supplies against GSTR-3B, at every return-filing cycle.

What the ₹5 crore threshold looks like in India — safe illustrative brands

The ₹5 crore aggregate turnover threshold is decisive for the mid-tier of Indian textile manufacturing. Tier-1 vertically integrated firms — Vardhman Textiles, Trident Ltd, Arvind Ltd, Raymond, Welspun India, KPR Mill, and Aditya Birla Fashion and Retail (which owns Pantaloons, Allen Solly, and Van Heusen) — all crossed the threshold years ago and have been on e-invoicing since the earlier ₹10 crore and ₹20 crore threshold rounds. Tier-2 specialist firms — Page Industries, Shahi Exports, Gokaldas Exports, Indo Count Industries, Himatsingka Seide, Lux Industries, Rupa and Co, Dollar Industries, Siyaram Silk Mills, Donear Industries, Garware Technical Fibres, Filatex India, Sutlej Textiles, Banswara Syntex, Bombay Dyeing, and Pearl Global Industries — are all comfortably above ₹5 crore and are on IRP. Branded apparel firms such as Trent Ltd (Westside and Zudio) and Reliance Retail (Reliance Trends and AJIO) are above the threshold on their B2B leg (supplier and vendor invoices raised on B2B counterparties in the supply chain); their B2C-heavy retail sales are separately handled outside the IRP scope.

The interesting reconciliation surface sits in the mid-tier — Ludhiana hosiery brands running annual turnover in the ₹8 to ₹25 crore band; Tiruppur knitwear job-work principals sending yarn out for conversion at ₹15 to ₹40 crore turnover; Panipat home-textile firms at ₹10 to ₹30 crore; Surat synthetic saree units at ₹6 to ₹20 crore; and Bhilwara suiting mills at ₹12 to ₹35 crore. Every one of these firms is above the ₹5 crore threshold, is on IRP, and typically runs 200 to 600 B2B invoices per month against a mix of domestic wholesale distributors, regional retailers, and export buyers. The Ludhiana hosiery cluster in particular is dense with mid-tier brands whose finance teams graduated to e-invoicing over the 2023 rollout wave and are still tightening the reconciliation discipline three financial years in.

Regional clusters — Tiruppur (knitwear), Karur (home textiles), Ludhiana (winter knitwear and hosiery), Panipat (home furnishings), Surat (man-made fibre and synthetic sarees), Bhilwara (suiting), Coimbatore and Erode (cotton), Solapur (jacquard) — set the counterparty mix. A Ludhiana hosiery unit selling to distributors across Punjab, Haryana, Delhi NCR, and Uttar Pradesh generates B2B invoices with a mix of intra-state (Punjab) and inter-state (Haryana, Delhi, UP) supplies, and every one of those invoices must carry an IRN. The B2C leg — factory outlet sales to walk-in customers and any direct-to-consumer online sales through the brand’s own website below the ₹500 crore Rule 46(r) threshold — sits outside the IRP scope and is documented on regular tax invoices without IRN.

The regulatory overlay — Rule 48(4), Rule 48(5), and the cancellation clock

Rule 48(4) of the CGST Rules 2017 requires that every registered person to whom the rule applies must prepare the invoice by including such particulars in Form GST INV-01 after obtaining an Invoice Reference Number by uploading information contained therein on the Common GST Electronic Portal. Notification 10/2023-Central Tax dated 10 May 2023 reduced the aggregate turnover threshold from ₹10 crore to ₹5 crore in any preceding financial year from 2017-18 onwards, effective 1 August 2023. Aggregate turnover is measured on a PAN basis — a taxpayer with multiple GSTIN registrations under the same PAN aggregates turnover across all registrations to test the threshold. Once a taxpayer crosses ₹5 crore in any single preceding FY, e-invoicing continues to apply in subsequent years even if turnover falls below the threshold — the rule tests preceding-FY turnover, not current-FY turnover.

Rule 48(5) is the enforcement lever. It states that every invoice issued by a person to whom sub-rule (4) applies in any manner other than the manner specified in the said sub-rule shall not be treated as an invoice. The commercial consequence: the counterparty cannot claim input tax credit on an invoice that lacks an IRN when the issuer is under Rule 48(4). The compliance consequence: the seller is exposed to Section 122(1)(i) penalty (₹10,000 or amount of tax evaded, whichever is higher, per invoice) for defective invoicing, and Section 122(1)(ii) penalty for supplies without the requisite documents. In practice, GST audit teams verify IRN coverage across the seller’s B2B outward supplies register at every Section 65 audit — a gap between the ERP invoice register and the IRP IRN register is the first red flag examined.

The IRN generation flow is technically simple but operationally exacting. The seller assembles the invoice payload in the JSON schema specified in the e-Invoice API standard — invoice number, invoice date, seller GSTIN, buyer GSTIN, HSN and quantity for every line item, taxable value, tax rate, tax amount, and (optionally) transporter details for e-way bill generation. The payload is uploaded to the IRP portal either directly by the seller (using the IRP’s own web portal for occasional invoicing) or via API integration (for volume operations) or via an offline utility (for legacy ERP systems). The IRP validates the payload against a defined ruleset — GSTIN validity, HSN validity, tax rate consistency with HSN, and duplicate-invoice checks against the seller’s own submission history — and either returns a successful IRN and QR code, or returns a validation error code. On success, the IRN is a 64-character hash string that uniquely identifies the invoice in the GST system.

The 24-hour cancellation window is where operational discipline is tested. From the moment the IRN is generated, the seller has exactly 24 hours to cancel it on the IRP if the invoice is defective (incorrect GSTIN, incorrect HSN, incorrect quantity or price, order cancelled by the buyer). Cancellation reasons must be selected from a limited list on the portal. If the invoice’s associated e-way bill has been used for physical movement, the cancellation is blocked — the invoice is treated as a completed supply. Beyond 24 hours, the IRP portal will not accept a cancellation request under any circumstances — the invoice is a completed supply in the GST system, and the seller’s only remedy is to issue a B2B credit note (which itself requires an IRN under Rule 48(4)) to reverse the invoice, and re-issue a fresh IRN for the corrected invoice.

The Rule 46(r) B2C dynamic QR code is a distinct regime that does not apply to mid-tier textile units. Notification 14/2020-Central Tax requires a dynamic QR code on B2C tax invoices only for registered persons whose aggregate turnover in a financial year exceeds ₹500 crore. For a Ludhiana hosiery unit at ₹18 crore, Rule 46(r) is inactive — the B2C leg (factory outlet sales, direct-to-consumer retail below the ₹500 crore threshold) is documented on regular tax invoices without IRN and without QR code. Only if the brand grows past ₹500 crore does the B2C QR code obligation kick in; the ₹5 crore IRN obligation on B2B invoices is independent and applies from the ₹5 crore threshold.

A worked example — a Ludhiana hosiery brand’s Q2 FY 2025-26

Illustrative — the following figures represent the operating pattern of a representative mid-tier Ludhiana hosiery brand of the scale that a typical Punjab hosiery cluster unit operates. Cross-verify against your own IRN register and GSTR-1 filing before action.

A mid-tier Ludhiana hosiery brand closes FY 2024-25 with aggregate turnover of ₹16 crore across a single Punjab GSTIN. FY 2025-26 opens with sustained order flow — Q1 (April to June 2025) closes at ₹5.2 crore, crossing the ₹5 crore threshold within the quarter. The brand was not previously on e-invoicing (FY 2023-24 turnover was ₹4.4 crore, below the threshold at the time). Under Notification 10/2023-Central Tax, once aggregate turnover in a preceding FY exceeds ₹5 crore, e-invoicing applies from the following FY — the brand must onboard to the IRP portal from FY 2026-27. In practice, the brand also chooses to onboard voluntarily from Q2 (July to September 2025) rather than wait for the mandatory date, so that Q1 lessons on defective invoicing are absorbed before Q3 volume ramps.

Q2 FY 2025-26 opens with the brand on IRP. July 2025 B2B invoice volume is 447 invoices across 42 distributor GSTINs in Punjab, Haryana, Delhi NCR, and Uttar Pradesh. The brand’s ERP is integrated with a GSP (GST Suvidha Provider) intermediary that handles the IRP API call — invoice creation in the ERP triggers a JSON payload upload to the GSP, which forwards to the IRP, receives the IRN and QR code, and returns them to the ERP. Median IRN generation lag is 8 seconds against a 15-second SLA; p95 lag is 22 seconds; three invoices in the month exceed 30 seconds (all attributed to intermittent GSTIN validation delays at the IRP).

Of the 447 IRNs generated in July, three are found defective within the same day on internal QC — a data-entry error in the HSN code on two invoices (used HSN 6109 for a T-shirt line that should have been HSN 6110 for a sweater line, wrong tax classification), and an incorrect GSTIN on the third (distributor’s Haryana GSTIN entered instead of Delhi GSTIN). All three are cancelled on the IRP within 4 hours of generation, and fresh IRNs are issued with corrected data. No credit-note routing was needed because the defective IRNs were caught inside the 24-hour window.

Two additional defective IRNs are caught on day 25 (25 July 2025) through a routine reconciliation against the distributor’s own purchase register — the distributor flagged that two invoices carried the wrong PO reference, causing an ITC-2A mismatch at their end. The IRNs were generated on 3 July and 7 July, so the 24-hour window closed on 4 July and 8 July respectively. The remedy is a B2B credit note for each — CN/25-26/0007 issued on 26 July against invoice HOS/25-26/00089 (IRN generated on 3 July), and CN/25-26/0008 issued on 26 July against invoice HOS/25-26/00147 (IRN generated on 7 July). Both credit notes are themselves uploaded to the IRP under Rule 48(4) and receive their own IRNs. Fresh invoices HOS/25-26/00318 and HOS/25-26/00319 are issued on 26 July with corrected data and receive fresh IRNs.

The July filing cycle IRN reconciliation pack surfaces the following:

Every layer of the reconciliation is aligned. IRN generation lag distribution stayed inside SLA. Cancellation compliance was 100 percent within the 24-hour window for internally-caught defects. Post-24-hour defects (caught externally by the distributor) were handled by credit-note issuance, and both credit notes appear in Table 9B against the original invoices. IRP-reported turnover of ₹171.2 lakh matches GSTR-1 net B2B outward supplies of ₹171.2 lakh, which matches GSTR-3B Table 3.1(a). The brand’s GSTR-1 filing is completed on 11 August (well ahead of the 13 August due date), and GSTR-3B on 18 August (ahead of the 20 August due date). Aggregate turnover for FY 2025-26 Q1 plus Q2 stands at ₹8.14 crore — the trajectory is toward the FY 2024-25 pattern (₹16 crore) with an upward drift on Q2 order flow.

Now consider the failure mode. Change the discovery timing on the two data-entry errors — instead of QC catching them on the same day, they surface only on day 12 (13 July) and day 15 (16 July) when a distributor’s finance team calls with ITC mismatch concerns. Both IRNs are beyond the 24-hour cancellation window (window closed on 4 July and 8 July). The remedy is a credit note. But now consider the impact if the two errors are HSN misclassifications that pushed the tax rate wrong — say, invoiced at 5 percent GST when the correct rate on HSN 6110 is 12 percent. Total tax under-collected on the two invoices is ₹42,000. The credit-note reverses the incorrectly-taxed original; the fresh invoice at the correct 12 percent rate collects the correct tax. The distributor is now working with three documents (original invoice, credit note, fresh invoice) instead of one, and the ITC claim on GSTR-2B for July has to reconcile across all three. The IRN reconciliation platform must surface every such multi-document chain in the reconciliation pack so the seller’s finance team can walk the distributor through the arithmetic at year-end audit.

Common reconciliation breakages

Five breakages recur across mid-tier textile brands running Rule 48(4) e-invoicing at the ₹5 crore threshold.

• Delayed IRN generation stalling physical dispatch. IRP portal latency spikes during peak days (typically the last week of a month or a quarter) push IRN generation lag past 30 seconds, causing dispatch trucks to wait at the loading dock. Some brands issue invoices without waiting for the IRN, which invalidates the invoice under Rule 48(5) and triggers Section 122 exposure. The remedy is a dispatch-gate control in the ERP that blocks the goods movement instruction until the IRN is received, plus a redundancy path (a fallback GSP or a direct-portal call) for peak-day IRP outages.

• Missed 24-hour cancellations for late-caught data errors. Defects caught between day 2 and day 30 of the invoice month cannot be cancelled on the IRP — the only remedy is a B2B credit note (itself carrying an IRN) plus a fresh invoice. Brands that do not track defect-caught-date against IRN-generated-date accumulate a backlog of un-canceled defective IRNs that surface only at return-filing time, forcing rushed credit-note issuance in the same GSTR-1 period.

• GSTR-1 e-invoice section drift against internal IRN register. The auto-populated e-invoice section on GSTR-1 pulls from the IRP database with a one-day lag. If the seller manually edits the auto-populated data during return preparation (correcting a typo, adjusting a rounded value), the GSTR-1 filed differs from the IRP database — and a Section 65 audit will flag the variance. The remedy is a return-cycle rule: no manual edits to auto-populated e-invoice rows; all corrections flow via credit-note IRN in the following period.

• IRP-reported turnover drift against GSTIN turnover. The IRP portal periodically publishes an aggregate-turnover report (total invoice value uploaded during the period) which must reconcile to the sum of GSTR-1 e-invoice section value plus adjustments. A gap typically arises where a batch of IRNs was generated for invoices that were later credit-noted — the IRP-reported turnover counts the gross value while GSTR-1 nets the credit-note against the invoice in the same period. The reconciliation pack must show the gross-to-net bridge explicitly.

• B2C invoices routed through IRP by mistake. Automation scripts that push every invoice above a value threshold to the IRP occasionally include B2C invoices (invoices to unregistered persons) and fail with invalid-GSTIN errors. The seller then wastes cycles debugging the IRP call when the correct answer is that B2C invoices should not be routed to IRP at all. The remedy is a document-type gate in the ERP: only B2B tax invoices, export invoices, B2B credit notes, and B2B debit notes are pushed to IRP; B2C invoices are documented on regular tax invoices without IRN.

How a reconciliation platform handles this

A purpose-built textile IRN reconciliation platform ingests the ERP invoice register, the IRP portal daily download, the GSTR-1 auto-populated e-invoice section, and the IRP aggregate-turnover report, and produces a per-invoice reconciliation view that closes the loop from ERP invoice creation to IRP IRN generation to GSTR-1 auto-population to GSTR-3B filing. The platform runs the 24-hour cancellation clock against every generated IRN and surfaces defective candidates at 12 and 20 hours from generation, giving the operations team time to act inside the window. It maps every IRN back to the source ERP invoice by invoice number, GSTIN, HSN, and taxable value; it surfaces GSTR-1 auto-populated variances against the IRN register at return-preparation time; it reconciles IRP-reported turnover against GSTR-1 outward supplies with a gross-to-net bridge that isolates credit-note adjustments; and it produces the audit-ready pack — IRN register, IRN-to-GSTR-1 reconciliation, cancellation compliance rate, defective-IRN root cause — that satisfies both the internal statutory auditor and the Section 65 GST audit team. Match rate improvement of 51 to 88 percent on the invoice-to-IRN and IRN-to-GSTR-1 reconciliation, combined with ISO 27001:2022 posture and DPDP Act 2023 aligned data handling, is what makes the platform an infrastructure investment rather than a spreadsheet substitute for the mid-tier textile brand crossing ₹5 crore for the first time.

Cross-cluster bridges and where to read next

The IRN discipline in this article completes the textile compliance cluster. For the Ludhiana cluster context and the winter-knitwear cycle that runs the same brand’s B2B invoicing at peak volume, read the Ludhiana hosiery and woollen cluster reconciliation walkthrough. For the September 2025 GST rate rationalisation impact on textile HSNs (many textile HSNs remained at 5 percent and 12 percent split), see GST textile rate rationalisation September 2025 impact. For the Tiruppur knitwear cluster and its Section 43B(h) MSME payment interaction with e-invoicing timelines, see Tiruppur knitwear cluster reconciliation with Section 43B(h). The multi-hop job-work discipline that generates the B2B credit-note IRNs at conversion charge invoicing is covered in Multi-hop job-work reconciliation for textile manufacturing in India. For the TDS taxonomy that runs in parallel to the invoicing cycle (payment codes 1023 and 1024 for job-work), see TDS Section 393 textile job-work codes 1023 and 1024. For the freight leg TDS reconciliation on cotton and yarn carriage, see TDS on cotton and yarn freight Section 194C code 1001. For the customs BCD reconciliation on cotton and MMF imports that feeds the same B2B invoice chain, see Customs BCD cotton and MMF textile import reconciliation. For the MAT and AMT treatment of PLI claims that intersects with the same aggregate-turnover threshold measurement, see MAT and AMT PLI textile claim tax treatment reconciliation. For the Surat synthetic saree cluster with its own B2B volume profile, see Surat synthetic saree domestic and export reconciliation; for the Panipat cluster with recycled yarn and home textile reconciliation, see Panipat home textile and recycled yarn reconciliation; and for the OEKO-TEX and GOTS compliance overlay on textile chemical safety and organic certification, see OEKO-TEX and GOTS compliance reconciliation textile India. The commercial pillar for the entire textile cluster is Textile reconciliation software India; the broader authority is reconciliation software India.

The five FAQs below address the operational questions Indian textile controllers ask most often when running Rule 48(4) e-invoicing at the ₹5 crore threshold.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 6 July 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024