TDS on Cotton/Yarn Freight under Section 194C Code 1001 for Textile

A Karur home-textiles principal running an export-order weeklong dispatches yarn from Coimbatore spinners at 45 truck loads per quarter — 32 loads via individual truck-owner-operators, 13 loads via mid-tier transport LLPs. Quarterly freight spend ₹8.5 lakh. The finance team’s Form 26Q for the quarter must classify every load correctly under Section 393(1) Sl. 4 — code 1001 at 1 percent for the owner-operators, code 1002 at 2 percent for the LLPs — track the ₹1,00,000-aggregate threshold on each transporter’s PAN, apply the transport-contractor 10-vehicle exemption where a declaration is on file, and reconcile every deduction against the transporter’s Form 26AS credit after filing. A single mis-classification — code 1001 against an LLP transporter, or a missing 10-vehicle declaration on an exempt owner-operator — becomes a short-deduction default at the CPC-TDS screen and a Section 201(1) exposure at year-end assessment. This is TDS cotton yarn freight Section 194C code 1001 textile as the operational discipline that keeps a mid-market textile principal out of TDS trouble.

Quick reference

The reconciliation in one paragraph

Section 393(1) of the Income-tax Act 2025 — the successor provision to Section 194C of the Income-tax Act 1961 — requires a resident payer to deduct TDS on any payment to a resident contractor for the performance of work, including transport work. The payment code taxonomy splits the deduction rate by the contractor’s constitution: Sl. 4 code 1001 applies to Individual or HUF contractors at 1 percent, and Sl. 4 code 1002 applies to all other resident contractors (partnership, LLP, private limited, cooperative, AOP) at 2 percent. The deduction is triggered when a single payment exceeds ₹30,000 or aggregate payments to the same PAN cross ₹1,00,000 in the FY. A statutory exemption applies to transport contractors who own 10 or fewer goods carriages at any time during the previous year, provided PAN and a written declaration are furnished to the deductor. For cotton and yarn road freight between a spinner and a weaver, the operational reality is a mix of exempt owner-operators, non-exempt owner-operators past the aggregate threshold, and transport LLPs — each requires a different Form 26Q line-item treatment, and every treatment must reconcile to Form 26AS credit at the transporter’s PAN.

What cotton and yarn road freight looks like in India — safe illustrative brands

The cotton-and-yarn freight corridor between Coimbatore or Erode spinners and Tiruppur, Karur, or Bhilwara weavers is one of the highest-volume road-freight lanes in the Indian textile sector. Illustrative principals whose operating shape includes heavy inbound yarn freight from the Coimbatore-Erode belt or the Vidarbha-Aurangabad belt include Vardhman Textiles (with own spinning at Baddi and Ludhiana but heavy inbound cotton yarn at its Punjab weaving units), Trident Ltd (Punjab home-textiles, heavy yarn inbound), Welspun India (Anjar and Vapi towel and terry works, cotton yarn from Gujarat and Maharashtra), KPR Mill (vertically integrated spinning at Sathyamangalam feeding weaving at Perundurai and garmenting at Arasur), Indo Count Industries (Kolhapur bedsheets and home textiles), Himatsingka Seide (Doddaballapur), and specialist tier-2 firms such as Sutlej Textiles, Banswara Syntex, Bombay Dyeing, and Filatex India. Regional geography dictates the freight profile — Tiruppur knitwear draws yarn from Coimbatore and Erode within 100 to 150 kilometres, Karur home-textiles draws from Coimbatore at 150 to 300 kilometres, Panipat home furnishing draws from Ludhiana and North-India spinners within 200 kilometres, Bhilwara suiting draws from Kota and Ratlam spinners within 200 kilometres, and Solapur draws from Vidarbha spinners.

The freight vendor mix on any of these lanes is dominated by individual truck-owner-operators — a driver-owner running one to three trucks under a proprietorship PAN, paid per load, no formal agreement. These operators typically qualify for the Section 393(1) transport exemption because their fleet count is well below the 10-carriage threshold. Alongside sit mid-tier transport LLPs — regional carriers running 15 to 40 trucks under an LLP or partnership PAN, offering scheduled slots and organised pickup-delivery discipline. These operators do not qualify for the exemption and are subject to code 1002 at 2 percent. National LTL carriers (Delhivery cargo, DTDC, VRL Logistics, TCI Freight, Safexpress) are a smaller share of pure cotton-and-yarn intra-cluster freight because full-truckload economics favour local operators, but they show up on inter-state high-value shipments and on courier-parcel freight for sample rolls and small consignments.

The regulatory overlay — Section 393(1), code 1001 versus 1002, and the transport exemption

Section 393(1) of the Income-tax Act 2025 carries forward the substance of Section 194C of the Income-tax Act 1961 into the new payment-code taxonomy. The section requires any person responsible for paying a resident contractor for carrying out any work — including the transport of goods — to deduct income-tax at source at the rate applicable to the contractor’s constitution. Sl. 4 payment code 1001 applies where the contractor is an Individual or Hindu Undivided Family and the rate is 1 percent of the gross payment. Sl. 4 payment code 1002 applies where the contractor is any other resident — a partnership firm, an LLP, a private limited company, a cooperative society, or an association of persons — and the rate is 2 percent of the gross payment. The threshold trigger is unchanged from legacy Section 194C: a single payment exceeding ₹30,000 or aggregate payments to the same deductee PAN crossing ₹1,00,000 in the FY.

The transport contractor exemption is the operationally dominant provision. Where the transporter owns 10 or fewer goods carriages at any time during the previous year, and furnishes to the deductor (a) the transporter’s PAN and (b) a written declaration to that effect, no TDS is deductible. The declaration must be preserved by the deductor for the standard TDS record-retention period (six years from the end of the relevant assessment year is the common audit horizon) and reported in Form 26Q against the transporter’s PAN with the nil-deduction reason code applicable to Section 393(1) transport exemption. If the exemption breaks — the transporter’s fleet crosses 10 carriages during the year, the PAN or declaration is not furnished, or the declaration expires without renewal — the exemption is lost prospectively (and, in strict reading, retrospectively for the year), and TDS becomes payable on the gross freight paid to that transporter at code 1001 or 1002 as applicable, with Section 201(1A) interest running from the date the deduction was due.

The CIF-versus-FOB freight-invoice-recipient rule sets the deduction obligation before the payment code question. TDS under Section 393(1) is deductible only by the person who makes the payment to the contractor. Under FOB (Free On Board) or ex-works Incoterms, the consignee (the weaver or brand) engages the transporter, receives the freight invoice, pays the transporter directly, and is the deductor. Under CIF (Cost, Insurance, Freight) Incoterms, the consignor (the spinner) engages the transporter, receives the freight invoice, and pays the transporter — the freight cost is embedded in the yarn purchase price, and the brand has no direct freight vendor payment, hence no Section 393(1) obligation on the freight leg. The critical operational trap is the hybrid case — where the spinner arranges transport and pays the transporter, then re-bills the freight as a separate line on the yarn invoice or as a separate freight invoice to the brand. Every such re-bill requires a documentation walk-through: is this the brand paying the transporter through the spinner (a Section 393(1) transaction requiring the brand to deduct at source on the freight component), or is it a reimbursement of the spinner’s cost (no separate 393(1) obligation)? The distinction turns on whether there is a contract for transport services between the brand and the spinner (reimbursement, no TDS) or between the brand and the transporter via the spinner as agent (Section 393(1) applies). The safer discipline is to route freight through separate invoicing where the brand deducts directly, and to preserve the yarn invoice as pure goods cost.

Alongside runs the Section 393(1) Sl. 4 code 1014 provision — the successor to Section 194-IA — which applies where the transporter is a specialised carrier engaged separately by the consignee for the transport of specific commodities including cotton or yarn. In routine road-freight cotton-and-yarn movement between a Coimbatore spinner and a Karur weaver via individual truck-owner-operators or transport LLPs, code 1014 is rarely invoked — the operational default is code 1001 or 1002 as applicable. Code 1014 becomes relevant where a specialised bulk-cotton carrier is engaged under a separate contract (typically for rail-linked movement or containerised export freight), and the classification affects both the Form 26Q line-item treatment and the e-way-bill documentation. The reconciliation platform’s classification logic must default to 1001 or 1002 based on the vendor entity type and escalate to 1014 only where the freight contract explicitly falls within the specialised-carrier category.

A worked example — a Karur mill’s quarterly freight

Illustrative — the following figures represent the operating pattern of a representative Karur home-textiles principal of the scale that a specialist tier-2 firm operates. Public disclosures do not reveal internal freight-ledger values; cross-verify against your own freight register or Form 26Q draft before action.

A Karur home-textiles principal running approximately ₹200 crore turnover ships combed cotton yarn from Coimbatore spinners at 45 truck loads per quarter — a steady weekly cadence of 3 to 4 loads. Total quarterly freight spend is approximately ₹8.5 lakh. The load mix splits as follows: 32 loads via individual truck-owner-operators (average ₹19,375 per load, quarterly total ₹6.2 lakh), and 13 loads via a mid-tier transport LLP called “Kongu Cargo LLP” for illustrative purposes (average ₹17,692 per load, quarterly total ₹2.3 lakh).

Owner-operator leg — 32 loads across 12 vendors. The vendor master lists 12 distinct owner-operators with PANs classified as Individual constitution. Of the 12, seven have a valid 10-vehicle declaration on file (dated within the preceding 12 months) and qualify for the Section 393(1) transport exemption. The other five either do not have a declaration on file or the declaration has expired without renewal. The seven exempt operators run 18 loads for ₹3.5 lakh in the quarter — no TDS is deducted; each load is reported in Form 26Q as a nil-deduction line-item under the transport exemption reason code, referencing the declaration PAN and date. The five non-exempt operators run 14 loads for ₹2.7 lakh in the quarter — TDS is deducted at code 1001 (1 percent). Running aggregate per PAN is tracked: the busiest non-exempt operator has run 6 loads totalling ₹1.17 lakh in the quarter, well above the ₹1,00,000 aggregate threshold; deduction on that operator’s payments is 1 percent of ₹1.17 lakh = ₹1,170. Across all five non-exempt operators, total TDS deducted on the owner-operator leg is approximately ₹6,200 (approximately 2.3 percent of ₹2.7 lakh, because five vendors cross the aggregate threshold within the quarter).

Transport LLP leg — 13 loads, single vendor. Kongu Cargo LLP invoices ₹2.3 lakh in the quarter across 13 loads at an average ₹17,692 per load. LLP is classified under code 1002 at 2 percent. TDS deducted at 2 percent of ₹2.3 lakh = ₹4,600, deposited by challan on the standard monthly deposit cycle (seventh of the following month).

Total quarterly Form 26Q filing — freight leg. The Q1 (April-June) Form 26Q filing due 31 July carries the following line-items on the freight leg: 18 nil-deduction lines against seven exempt owner-operators (₹3.5 lakh gross, ₹0 TDS, transport exemption reason code, PAN and declaration reference); 14 code 1001 deduction lines against five non-exempt owner-operators (₹2.7 lakh gross, ₹6,200 TDS, deposited via monthly challans); 13 code 1002 deduction lines against Kongu Cargo LLP (₹2.3 lakh gross, ₹4,600 TDS, deposited via monthly challans). Total gross freight ₹8.5 lakh; total TDS deducted ₹10,800; average blended rate 1.27 percent.

Post-filing Form 26AS reconciliation. Two weeks after Q1 filing, the reconciliation platform pulls Form 26AS extracts at each of the 13 transporter PANs (12 owner-operators plus Kongu Cargo LLP). Five owner-operator PANs show credit posted at code 1001 matching the deducted amounts. Kongu Cargo LLP’s PAN shows credit posted at code 1002 matching ₹4,600. Seven exempt owner-operator PANs show no credit posted, consistent with the nil-deduction line-item — but each has a corresponding declaration on file confirming the exemption.

The failure case. Suppose one of the “exempt” owner-operators — vendor number 8 in the master — has a declaration that expired on 15 May 2025, the mid-point of Q1. The vendor ran 2 loads on 22 April (before expiry) totalling ₹38,750 and 3 loads on 4 June, 18 June, and 26 June (after expiry) totalling ₹58,125. The pre-expiry loads were correctly treated as exempt. The post-expiry loads should have been treated as code 1001 with 1 percent TDS = ₹581. The reconciliation platform’s declaration-expiry alert would have flagged the expiry on 1 May 2025 (two weeks before), giving the operations team time to renew the declaration and preserve exempt status. Without the alert, the Q1 filing under-deducts ₹581 across three loads. At Q4 assessment or a CPC-TDS review, this surfaces as a Section 201(1) short-deduction default of ₹581 plus 201(1A) interest at 1 percent per month from the deduction date (approximately ₹40 for a 6-month lag), plus Section 271H penalty exposure if the corrective revision is not filed within the year.

Common reconciliation breakages

Five breakages recur across textile principals running steady inbound cotton and yarn freight, and each maps to a specific vendor-master or Form 26Q discipline failure.

• Missing or expired 10-vehicle declaration on owner-operator exempt vendors. The most common miss. Vendors sign the declaration at onboarding and no one renews it. The exemption breaks silently, and Form 26Q keeps filing nil-deduction lines for a vendor who no longer qualifies. The fix is a vendor-master declaration flag with an expiry date and a 30-day-pre-expiry alert; renewal cadence should be annual on a consistent calendar month (typically April, at the start of the FY).

• Entity-type mis-classification — 1001 versus 1002. A vendor invoicing as “Kongu Cargo” without an LLP or partnership suffix on the invoice header is presumed to be an individual proprietorship; a subsequent audit reveals it is registered as an LLP with the same trading name. The Q1 filing has been deducting at code 1001 (1 percent) instead of code 1002 (2 percent). The gap surfaces at Form 26AS when the vendor sees the credit at the wrong code but does not report it, and at the CPC-TDS default screen at year-end. The fix is PAN-based verification of entity type at vendor onboarding — the fourth character of the PAN encodes the holder type (P for Individual, F for Firm/LLP, C for Company, T for Trust, A for AOP/BOI, H for HUF).

• CIF/FOB mis-attribution on hybrid re-billed freight. The spinner arranges transport, pays the transporter, and re-bills the brand as a separate freight line on the yarn invoice. The freight is treated as goods cost (no TDS) but the audit position at year-end is that the brand is the beneficial payer for a transport service via agent, and TDS should have been deducted. The fix is a documentation walk-through on every freight re-bill: is there an agreement between the brand and the transporter (via the spinner as agent) or purely between the brand and the spinner? The safer discipline is to require the spinner to invoice pure goods on FOB terms and to route freight through direct brand-transporter invoicing where TDS can be deducted at source cleanly.

• Aggregate threshold miss across quarters. The ₹1,00,000 aggregate threshold runs at the PAN level for the full financial year, not for a single quarter. A vendor invoicing ₹28,000 in Q1, ₹28,000 in Q2, ₹28,000 in Q3, and ₹28,000 in Q4 is below the single-payment threshold each time but the FY aggregate crosses ₹1,00,000 in Q4. The Q4 payment onwards should carry TDS deduction from the payment that crosses the threshold. Many principals treat the threshold at the quarterly filing level rather than the FY-cumulative level and miss the Q4 crossing. The fix is a running FY-level aggregate table per PAN maintained by the reconciliation platform, refreshed on every freight invoice booking.

• Nil-deduction reason code errors on Form 26Q. Where the transport exemption applies and a nil-deduction line is reported, the correct reason code must be used — the transport-exemption code specifically, not a generic below-threshold code. Wrong reason codes trigger CPC-TDS validation failures at the return-processing stage and can trigger a request for the underlying declaration; if the declaration is not preserved or produced, the exemption is disallowed retrospectively. The fix is a reason-code lookup keyed to the vendor master’s exemption status and a document repository linking each Form 26Q line to the underlying declaration PDF.

How a reconciliation platform handles this

A purpose-built textile TDS reconciliation platform ingests the freight vendor master, the freight ledger, every load-level invoice, and the Section 393(1) Sl. 4 code lookup table, and produces a per-invoice classification decision that carries the correct payment code, the correct threshold check, the correct exemption treatment, and the correct Form 26Q line-item output. The platform tracks the ₹1,00,000 aggregate threshold at the PAN level across all four quarters of the FY, not at the quarterly cut-off, and flips the deduction obligation at the exact invoice that crosses the threshold. It maintains the 10-vehicle-declaration status at the vendor level with expiry-date monitoring and 30-day-pre-expiry alerts to preserve exempt status through timely renewal. It applies a documentation walk-through to every re-billed freight line to classify CIF versus FOB versus hybrid, and preserves the audit trail linking every freight invoice to the underlying yarn dispatch challan and the Incoterms declared in the yarn purchase contract. Post-filing, the platform reconciles Form 26Q against Form 26AS credit at each transporter PAN, surfaces code-classification defaults for corrective 26Q revision, and produces the audit-ready pack that satisfies the statutory audit team and, if required, the CPC-TDS assessment officer. Match rate improvement of 51 to 88 percent on the freight-invoice-to-Form-26Q-line 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 manual Form 26Q filing exercise.

Cross-cluster bridges and where to read next

The freight-TDS discipline in this article sits alongside the broader cotton and yarn supply-chain reconciliation surface. For the deep dive on the job-work TDS boundary between principal-supplied and non-principal-supplied material (codes 1023 versus 1024), read TDS Section 393 textile job-work codes 1023 vs 1024. For the upstream cotton procurement reconciliation, Cotton supply chain reconciliation textile India and CCI cotton corporation India procurement reconciliation walk through the CCI MSP procurement pattern and the bale-level receiving discipline. For the sibling e-invoicing rule that triggers on the same freight-invoice threshold, E-invoicing textile 5 crore threshold and IRN reconciliation covers the IRN generation and Form GST INS-01 handling.

Within the Wave T4 closer set, the freight-TDS discipline pairs with the Karur home-textiles cluster reconciliation and the Tiruppur knitwear cluster reconciliation MSME 43B(h) — the MSME 45-day payment rule under Section 43B(h) that runs alongside the TDS deduction obligation on the vendor payment cycle. For customs and BCD exposure on imported cotton and MMF that also enters the freight-TDS reconciliation on inbound haulage, Customs BCD cotton MMF textile import reconciliation covers the landed-cost build-up. For the tax treatment of PLI claim receipts under MAT and AMT that closes the year-end pack, MAT AMT PLI textile claim tax treatment reconciliation is the closer.

The multi-hop job-work chain — from yarn to grey to dyed to cut to stitched — is covered in Multi-hop job-work reconciliation for textile manufacturing in India, which sets up the Rule 55 delivery challan, ITC-04 quarterly return, and Section 143 CGST 1-year deemed-supply mechanics that run alongside the freight TDS discipline. 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 implementing structured cotton and yarn freight TDS reconciliation.

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