Tiruppur Knitwear Cluster Reconciliation — MSME and Section 43B(h)

A Tiruppur knitwear exporter closes the payables ledger on 31 March with 187 unpaid bills against 34 micro and small job-workers spread across a 6-hop conversion network — Tier-1 garment factory, dyeing, embroidery, cutting, stitching, and final packing. Of those 187 bills, 22 sit past the Section 43B(h) 45-day statutory window. The aggregate outstanding on the 22 breached bills is ₹1.42 crore. The deduction for the underlying job-work charges — booked as normal trade-work expense during the year — is now disallowed in the current year and allowed only in the year of actual payment. On top of the disallowance, Section 16 of the MSMED Act 2006 puts the exporter on the hook for compound interest at three times the RBI bank rate from the appointed day (Day 46 after acceptance) until the principal is paid, and that interest is itself non-deductible under Section 23 of the MSMED Act read with Section 37 of the Income-tax Act. This is Tiruppur knitwear cluster MSME Section 43B(h) exposure at operating scale, and the discipline that closes the year cleanly is what separates an export-oriented Tiruppur exporter from a Section 143(3) mismatch or a CARO 2020 adverse disclosure on trade payables to micro and small enterprises.

Quick reference

The reconciliation in one paragraph

Section 43B(h) of the Income-tax Act, inserted by the Finance Act 2023 and carried into the Income-tax Act 2025 successor codification, permits a deduction for a payable to a micro or small enterprise only in the previous year in which the sum is actually paid, unless the payment is made within the time limit specified in Section 15 of the MSMED Act 2006 — 45 days from acceptance of goods or service where an agreement in writing exists, or 15 days from acceptance where no written agreement exists. Section 15 sets a statutory ceiling of 45 days that overrides any longer contractual term. Section 16 MSMED Act then layers compound interest at three times the RBI bank rate with monthly rests on any principal outstanding past the appointed day. In a Tiruppur knitwear cluster where the conversion sequence runs across 6 sequential MSME hops — Tier-1 garment factory, dyeing, embroidery, cutting, stitching, and final packing — every bill from every micro or small job-worker at every hop starts an independent 45-day clock, and the reconciliation must maintain a Udyam register per vendor, a per-invoice acceptance date, a payment date register, a 43B(h) disallowance schedule for year-end, and a Section 16 interest accrual computation for every breached bill.

What the Tiruppur cluster looks like in India — safe illustrative brands

The Tiruppur knitwear cluster is India’s largest knitted-garment export ecosystem, concentrated across roughly 60 square kilometres in the Tiruppur district of Tamil Nadu. The cluster comprises approximately 10,000-plus MSME garment exporters at the top of the value chain and a supporting job-work network of roughly 30,000-plus MSME units performing dyeing, printing, embroidery, cutting, stitching, and packing. Cotton yarn feed comes from nearby spinning hubs in Erode, Coimbatore, and Palladam; combed cotton yarn is the dominant input, though blends with polyester (feeding into MMF-linked GST codes) and viscose are common for premium categories.

The illustrative principal names visible in the Tiruppur ecosystem — as owners of Tier-1 garment factories, as brand buyers, or as private-label suppliers — include vertically integrated tier-1 firms such as KPR Mill (spinning to garment), Arvind Ltd, Vardhman Textiles (yarn supply into knitwear chains), Raymond, Welspun India, and Aditya Birla Fashion and Retail (Pantaloons, Allen Solly, Van Heusen for private-label knitwear sourcing); and specialist tier-2 firms such as Page Industries (Jockey), Shahi Exports, Gokaldas Exports, Lux Industries, Rupa & Co, Dollar Industries, and Pearl Global Industries. Branded apparel buyers pulling private-label from Tiruppur include Trent Ltd (Westside, Zudio), Reliance Retail (Reliance Trends, AJIO), Myntra, Flipkart Fashion, and Nykaa Fashion. The Tiruppur cluster also serves overseas brand buyers, but for this article’s focus on Section 43B(h) the domestic private-label supply chain is where the MSME cascade risk materialises most sharply.

The 6-hop cascade shape typically plays out as: brand buyer places order with Tier-1 garment factory (may itself be a small enterprise under the Udyam thresholds — investment ≤ ₹10 crore, turnover ≤ ₹50 crore), Tier-1 factory dispatches yarn to a dyeing MSME, dyed fabric moves to an embroidery MSME (for value-added categories), fabric moves to a cutting MSME, cut panels move to a stitching MSME, and final garments move to a packing MSME that ships to the brand. In value-added categories with embroidery, the chain runs six hops; in commodity T-shirts and basics, embroidery is omitted and the chain runs five hops. Every hop below the brand — dyeing, embroidery, cutting, stitching, packing — is overwhelmingly micro or small by Udyam classification and therefore inside Section 43B(h) coverage.

The regulatory overlay — 43B(h), Section 15, Section 16, and Udyam classification

Section 43B(h) was inserted by the Finance Act 2023 with effect from AY 2024-25 and reads in substance: any sum payable by the assessee to a micro or small enterprise beyond the time limit specified in Section 15 of the MSMED Act 2006 shall be allowed as a deduction only in the previous year in which the sum is actually paid, notwithstanding that the assessee follows the mercantile system of accounting. The Income-tax Act 2025 successor codification carries the same rule at the same operational effect. The provision is unforgiving in three respects: it is not restricted by any threshold amount; it does not have a contractual override — even a written agreement for 90-day payment terms cannot extend the 45-day statutory ceiling; and it does not permit netting against amounts recoverable from the same MSME vendor.

Section 15 of the MSMED Act 2006 sets the liability rule. Where a supplier supplies goods or renders services, the buyer must make payment on or before the date agreed in writing (subject to the 45-day ceiling) or, if there is no agreement in writing, before the appointed day — defined as the 15th day from the day of acceptance or deemed acceptance. Section 2(b) provides that acceptance means the day of actual acceptance of the goods or service, and deemed acceptance is triggered where no objection is raised in writing by the buyer within 15 days of delivery. The 45-day maximum overrides any longer contractual term — even a signed agreement specifying 60-day or 90-day payment cannot extend the statutory ceiling for 43B(h) purposes.

Section 16 of the MSMED Act 2006 provides the interest consequence. Where a buyer fails to make payment within the Section 15 window, the buyer is liable to pay compound interest with monthly rests at three times the bank rate notified by the Reserve Bank of India, from the appointed day. Compound interest with monthly rests means the interest is capitalised at the end of each month and interest thereafter accrues on the compounded amount. The interest is payable to the supplier and is not deductible under Section 23 of the MSMED Act read with Section 37 of the Income-tax Act — the buyer cannot claim the Section 16 interest as an expense in its own P&L.

Udyam classification is the gating test for 43B(h) applicability. Notification S.O. 2119(E) of 26 June 2020 replaced the legacy Entrepreneur Memorandum registration with Udyam Registration effective 1 July 2020, and set the current thresholds: micro means investment in plant and machinery or equipment not exceeding ₹1 crore and turnover not exceeding ₹5 crore; small means investment not exceeding ₹10 crore and turnover not exceeding ₹50 crore; medium means investment not exceeding ₹50 crore and turnover not exceeding ₹250 crore. Section 43B(h) attaches only to micro and small — medium enterprises are outside the rule even where they hold valid Udyam registration. The buyer’s payables system must therefore not treat a medium vendor as MSME 43B(h) — doing so wrongly disallows a valid deduction. The Udyam certificate carries the classification on its face and the classification is re-tested when investment or turnover crosses a threshold; the register must track the effective-from date.

TDS on job-work charges at every hop of the chain is governed by Section 8 Sl. 4 code 1023 of the Income-tax Act 2025 (the successor to legacy Section 194C) where the principal supplies the raw material — the standard Tiruppur pattern because yarn, grey fabric, dyed fabric, and cut panels remain principal-owned throughout the hop sequence. TDS is deducted on the conversion charge only, at 1 percent for Individual or HUF job-workers and 2 percent for other resident job-workers. Section 43B(h) and TDS operate independently — TDS compliance on the conversion charge does not release the Section 43B(h) clock on the underlying payable.

A worked example — illustrative numbers for a Tiruppur exporter

Illustrative — the following figures represent the operating pattern of a representative mid-size Tiruppur knitwear exporter. Public disclosures do not reveal internal payables ageing; cross-verify against your own AP register or Udyam-linked payables report before action.

A Tiruppur knitwear exporter with approximately ₹65 crore turnover operates a 6-hop MSME job-work network. For Q3 (October to December) of the previous fiscal, the exporter engaged 22 micro and small job-workers across the six hops — 4 dyeing units, 3 embroidery units, 3 cutting units, 6 stitching units, and 6 packing units (some units perform packing plus finishing). All 22 units are Udyam-registered; 15 are classified micro (investment ≤ ₹1 crore, turnover ≤ ₹5 crore), 7 are classified small (investment ≤ ₹10 crore, turnover ≤ ₹50 crore). All 22 are inside Section 43B(h) coverage.

Aggregate Q3 payables to the 22 job-workers came to ₹4.2 crore, spread across 138 invoices with an average bill value of ₹3.04 lakh. Of the 138 invoices, 118 were paid within the 45-day window from acceptance date — aggregate ₹3.5 crore — and are deductible in the year of accrual as normal. The remaining 20 invoices — aggregate ₹70 lakh — were paid beyond 45 days. Four representative breach cases from that set illustrate the mechanics:

For each of the 4 bills the underlying deduction shifts from the year of accrual (AY 2026-27, previous year 2025-26) to the year of payment — but because payment happened before 31 March 2026, all 4 fall within the same AY 2026-27, so the year-end 43B(h) disallowance zeroes out at consolidation. The consequential exposure is the Section 16 MSMED interest, which is a hard cash liability to the supplier regardless of the tax-year effect.

Section 16 compound-interest computation at an illustrative RBI bank rate of 6.0 percent per annum (verify against the current RBI notification at the time of computation — the bank rate has moved between 5.15 percent and 6.75 percent over the past six years, so this figure is a placeholder for the illustrative calculation only). Three times the bank rate is 18.0 percent per annum; compounded monthly, the effective monthly rate is 1.5 percent. On the 4 breached bills:

Scaled to all 20 breached bills at ₹70 lakh aggregate, the Section 16 interest exposure for the quarter runs approximately ₹1.8 lakh to ₹2.4 lakh depending on the delay distribution. That interest is a Section 16 cash liability to the suppliers, is not deductible under Section 37 read with MSMED Section 23, and typically triggers CARO 2020 reporting requirement (Clause 3(vi) — MSMED delayed payments disclosure) in the statutory audit report.

Now consider the cascade failure mode. In a bad Q3, a brand-side receivable from Trent Ltd or Reliance Retail slips from 45-day contractual terms to 75 days. That upstream slip forces the exporter to fund downstream payables from working capital rather than customer receipts. The exporter, under pressure, delays payment to the Tier-1 stitching partner from Day 42 to Day 58 — Section 43B(h) triggers on 6 bills. The stitching partner, in turn, delays payment to its cutting sub-vendor by 10 days — Section 43B(h) triggers again on 4 bills at that hop. The cutting vendor delays payment to the dyeing sub-vendor by 8 days — Section 43B(h) on 3 more bills. In one bad quarter the cascade can double the number of 43B(h)-breached bills from a baseline 20 to 40 or more, and the Section 16 interest exposure scales proportionally.

Common reconciliation breakages

Five breakages recur across Tiruppur exporters running MSME job-work networks, and each maps to a specific control failure.

• Missing or stale Udyam classification on the vendor master. Vendors are onboarded years ago with an old MSME Entrepreneur Memorandum reference rather than the Udyam URN (mandatory since 1 July 2020). The classification is never refreshed, and a vendor that has since crossed the small-to-medium threshold is still treated as small — triggering false 43B(h) disallowance on a valid medium-vendor deduction. The fix is a documented annual Udyam re-verification cycle with a stored PDF of the current certificate and a review-date field on the vendor master.

• Acceptance-date confusion between GRN and invoice date. The 45-day clock starts from acceptance (or deemed acceptance) of goods or service, not from invoice date. In practice the goods received note (GRN) date at the receiving warehouse is the trigger for a goods delivery, and the service acceptance date is the trigger for a job-work service. AP systems that default the clock start to invoice-receipt date frequently under-count breach days by 5 to 15 days — because vendors often invoice a week or two after delivery. The fix is a mandatory GRN-date or service-acceptance-date field separate from invoice-receipt date, and the earlier of the two drives the clock.

• Cascade-blindness in receivable-payable planning. Treasury reviews receivables and payables independently — receivables in one dashboard, payables in another. The connection between a slipping brand receivable and the downstream MSME payables it funds is not surfaced until it is too late. The fix is a cascade view that projects the payables impact of every stretched receivable in the same 30 to 45-day window and pre-flags the MSME hops likely to breach.

• Section 16 interest not being computed or accrued. Many finance teams treat Section 43B(h) as a year-end tax-adjustment exercise only and do not accrue Section 16 interest during the year. When the statutory auditor asks for the Clause 3(vi) CARO 2020 MSMED disclosure, the interest number is computed ad-hoc from spreadsheets, misses compound-monthly-rest calculation, and typically under-states exposure. The fix is a live Section 16 accrual on every breached bill from the appointed day, with compounding at monthly rests.

• Wrong classification of medium enterprises as MSME. A dyeing unit or a stitching partner that crosses the ₹50 crore turnover or ₹10 crore investment threshold graduates from small to medium classification and drops out of Section 43B(h) coverage. If the vendor master still flags it as small, the payables system runs a spurious 43B(h) clock and the year-end tax pack wrongly disallows a valid deduction. The fix is the Udyam re-verification cycle (previous bullet) plus an explicit medium-vendor flag on the master.

How a reconciliation platform handles this

A purpose-built textile reconciliation platform ingests the vendor master with Udyam URN, PAN, GSTIN, and classification, and cross-verifies each vendor’s current classification against the Udyam Registration portal at onboarding and at the annual review cycle. The platform runs an independent 45-day clock on every posted payable to a micro or small vendor from the acceptance-date trigger (GRN date or service-acceptance date, not invoice-receipt date), surfaces pre-breach exposure at Day 30, 40, and 44, and locks in a year-end 43B(h) disallowance schedule at Day 46 that ties the deduction shift to the ITR schedule. On breached bills, the platform computes Section 16 MSMED compound interest at three times the RBI bank rate with monthly rests from the appointed day to date-of-payment, feeds the accrual into the P&L, and produces the CARO 2020 Clause 3(vi) disclosure pack for the statutory audit report. The platform also runs a cascade view where a slipping receivable from a brand buyer projects the payables funding gap and pre-flags the downstream MSME hops likely to breach, giving the treasury team the runway to draw on working-capital facilities or negotiate an interim brand payment before the 45-day mark is missed. Match rate improvement of 51 to 88 percent on the vendor-bill-to-payment matching cycle, 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.

Cross-cluster bridges and where to read next

The Section 43B(h) 45-day cascade in this article is one arm of the Tiruppur cluster’s compliance surface. For the powerloom-side procurement variant of the 45-day rule, read Section 43B(h) MSME 45-day powerloom procurement. For the physical-goods 1-year clock that runs in parallel to the payables clock, Multi-hop job-work reconciliation textile India covers Section 143 CGST and Rule 55 delivery challans across the same 5- and 6-hop chains. For the export-side revenue mechanics of Tiruppur, Tiruppur knitwear export reconciliation sets up RoDTEP and RoSCTL claim reconciliation. For the TDS-side of the job-work chain, TDS Section 393 textile job-work codes 1023 and 1024 covers the material-supplied test. For adjacent cluster patterns, Ludhiana hosiery and woollen cluster reconciliation covers the northern winter-wear equivalent, and Panipat home-textile recycled yarn reconciliation covers the home-furnishings hub. For the e-invoicing surface that overlaps with every ₹5-crore-plus MSME vendor in the chain, e-invoicing textile ₹5 crore threshold IRN reconciliation. 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 Tiruppur exporters ask most often when implementing structured Section 43B(h) reconciliation across a 6-hop MSME job-work network.

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