Skip to main content
How-To · 13 min read

New TDS and TCS Provisions FY 2026-27: What Indian Auto-Component Suppliers Must Reconfigure

On 1 April 2026 the Income Tax Act 2025 replaces the Income Tax Act 1961, and every TDS / TCS provision an auto-component supplier has worked with — Section 194C on conversion charges, Section 194Q on buyer-side purchase TDS, Section 206C(1H) on seller-side scrap TCS, Section 195 on non-resident commission, Section 194-IB on rent, Section 194J on professional fees — moves to new Sections 393, 394 and 413 with payment codes 1001 to 1092. Nine distinct payment streams across a typical ₹400 crore Tier-1 each need an ERP remapping, a Tally chart-of-accounts update, a deductee master refresh, and a quarter-by-quarter cross-era reconciliation through FY 2026-27.

Terra Insight
Terra Insight Reconciliation Infrastructure

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

Published 12 June 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

A ₹400 crore Indian Tier-1 auto-component supplier transitioning from the Income Tax Act 1961 to the Income Tax Act 2025 on 1 April 2026 must remap nine distinct TDS / TCS payment streams from legacy 194x / 195 / 206C section references to new Sections 393, 394 and 413 with payment codes 1001 to 1092 — across inbound freight (1002), conversion charges (1002), buyer-side raw-material purchase (1012), seller-side scrap TCS (1071), professional fees (1032), forwarder commission (1032), rent (1042), foreign-agent commission (1062), and interest (1022). The ERP and Tally chart of accounts, deductee masters, return-output templates, deposit calendars, deductee-credit reconciliation, and cross-era handling through FY 2026-27 all need a coordinated reset before 1 April 2026, with Form 168 / 131 / 141 replacing Form 26AS / 26Q / 27EQ.

How It's Resolved

Build a code-mapping master that pairs every legacy 194x / 195 / 206C section with its new Section 393 / 394 / 413 counterpart and the new payment code, applying it consistently across ERP, Tally, deductee masters and return templates. Drive each payment stream through (a) the section determination, (b) the rate matrix, (c) the threshold logic per deductee per FY, (d) the form output (168 for deductee credit, 131 for deductor non-salary statement, 141 for collector TCS statement). Run a parallel cross-era reconciliation register from Q4 FY 2025-26 through Q1 FY 2026-27, holding legacy 194x deductions on legacy 26AS / 26Q lineage and new 393 / 394 / 413 deductions on new 168 / 131 / 141 lineage without netting. Verify ERP and Tally code masters point to the new codes by 31 March 2026 and to the legacy codes for all pre-1-April-2026 entries.

Configuration

Code-mapping master with legacy-to-new pairs across nine auto-component payment streams, ERP and Tally chart-of-accounts update calendar, deductee master refresh with section code and rate per PAN, monthly TDS challan calendar (7th), monthly TCS challan calendar (7th), quarterly Form 168 / 131 / 141 calendar, cross-era reconciliation register, deposit-and-deductee-credit reconciliation per payment code, and a controller-level dashboard of remapping completeness pre-1-April-2026.

Output

A nine-stream remapping dashboard showing pre-1-April-2026 readiness, code-mapping master integrity, ERP and Tally configuration verification, deductee master section-code coverage, monthly deposit and form-output completeness through FY 2026-27, cross-era reconciliation register running Q4 FY 2025-26 alongside Q1 FY 2026-27, and an audit-defensible trail of the transition.

A ₹400 crore Tier-1 auto-component supplier in Pune — making transmission gears, axle assemblies and propshafts for Tata Motors, Mahindra and Daimler India Commercial Vehicles — runs nine distinct TDS / TCS payment streams across its annual ledger. On 1 April 2026, the Income Tax Act 2025 replaces the Income Tax Act 1961, and every one of those streams needs a section-reference update, a payment-code remapping, an ERP chart-of-accounts adjustment, a Tally voucher-template update, a deductee-master refresh, and a Form output migration from the 26AS / 26Q / 27EQ family to the Form 168 / 131 / 141 family. On 28 March 2026 the CFO is reviewing the readiness scorecard with the head of indirect taxes, the head of finance shared services, the ERP team lead, and the company’s tax CA. The remapping master is built, the deductee files are updated for 142 active vendor PANs, the chart of accounts has fresh ledger codes for each of the nine streams under the new section references — but the controller’s biggest worry is the cross-era window through Q1 FY 2026-27 where legacy and new entries will coexist in Form 168 / 26AS for every deductee.

This is new TDS TCS provisions FY 2026-27 auto component India at the operational level — not a tax-law commentary but the day-one transition playbook a Tier-1 needs to walk into Q1 FY 2026-27 without breaks. The article maps the nine streams, the ERP / Tally remapping checklist, the cross-era handling for Form 168 reconciliation, and a worked example on the ₹400 crore Tier-1.

Quick reference — the nine streams an auto Tier-1 carries

StreamLegacy section (1961 Act)New section (2025 Act)New payment codeTypical rate
Inbound freightSection 194CSection 393(1)(a)10021% / 2%
Job-work conversion chargesSection 194CSection 393(1)(a)10021% / 2%
Buyer-side purchase TDS (raw-material above ₹50 lakh per FY)Section 194QSection 393(1)(k)10120.1%
Seller-side scrap TCSSection 206C(1) / 206C(1H)Section 394(1)10711% / 0.1%
Professional / technical feesSection 194JSection 393(1)(d)1032 (subtype)10% / 2%
Commission / brokerage (forwarder split)Section 194HSection 393(1)(j)1032 (subtype)2%
Rent (godown, warehouse)Section 194-I / 194-IBSection 393(1)(e)104210% (building) / 2% (plant)
Foreign-agent commission (non-resident)Section 195Section 4131062DTAA rate or 20%+
Interest on supplier credit facilitiesSection 194ASection 393(1)(c)102210%

What changes on 1 April 2026, and what does not?

The substantive economic outcome — rates, thresholds, deposit cadence, deductee credit — is preserved across the nine streams. Three things change in lockstep:

  1. Statute and section reference. Every section reference moves from the Income Tax Act 1961 family (194x / 195 / 206C) to the Income Tax Act 2025 umbrella sections — 393 for most resident-payee deductions, 394 for TCS, 413 for non-resident payments
  2. Payment code on the challan and the return. Every payment-code lookup moves from the legacy 194x identifiers to the 1001-1092 range. The ERP, Tally, banking-system payment-instruction templates, and return-output templates all need this remap
  3. Form output. Form 26AS (deductee tax-credit statement) moves to Form 168. Form 26Q (quarterly non-salary deductor statement) moves to Form 131. Form 27EQ (quarterly TCS collector statement) moves to Form 141. The TRACES portal infrastructure is preserved with the new form templates

What does not change: the per-PAN threshold logic, the cumulative tracking discipline, the deposit due dates (7th of the following month for both TDS and TCS), the deductee-credit reconciliation cycle, the substance-over-form principle on classification questions, the Section 40(a)(ia) disallowance consequence for under-deduction, the Section 201(1A) interest for late deposit, and the Section 206AA / 206CC equivalent missing-PAN fallback rates.

The wider statutory shift is set out in TDS payment codes 1001-1092, the contractor-leg detail in Section 393(1)(a) TDS on auto-component job work, and the seller-leg TCS in TCS on scrap sale under Section 394.

Stream-by-stream remapping for a ₹400 crore Tier-1

Stream 1 — Inbound freight. ₹4.2 crore annual freight across 38 transporter PANs. Legacy 194C → Section 393(1)(a) code 1002. ERP freight-bill posting template updated to code 1002; Tally voucher template for freight TDS updated. Small-truck declaration register re-collected for FY 2026-27.

Stream 2 — Job-work conversion charges. ₹40 lakh annual across four plating, heat-treatment and machining job-workers. Same legacy 194C → Section 393(1)(a) code 1002 mapping. The conversion-charge ledger picks up the new code; per-PAN cumulative threshold tracker resets on 1 April 2026.

Stream 3 — Buyer-side purchase TDS. ₹240 crore annual raw-material purchase across 18 active suppliers, six of whom cross the ₹50 lakh aggregate threshold per FY. Legacy 194Q → Section 393(1)(k) code 1012. 0.1% TDS on purchase value above ₹50 lakh per supplier per FY. ERP procurement-payment template updated; supplier master tagged with Section 393(1)(k) applicability per FY.

Stream 4 — Seller-side scrap TCS. ₹6 crore annual scrap-sale revenue across stamping skeleton scrap, turning scrap from machining lines, casting runners and risers. Legacy 206C(1) → Section 394(1) code 1071 at 1%. Buyer-declaration exemption preserved (legacy Form 27C, new form reference). The seller-side TCS register migrates from Form 27EQ output to Form 141 output.

Stream 5 — Professional fees. ₹3.8 crore annual across statutory auditor, tax CA, legal counsel, design consultants, IT services consultants. Legacy 194J → Section 393(1)(d) code 1032 (with subtype distinguishing professional from technical services). Rate matrix preserved (10% on professional, 2% on technical pure-service-only). Per-vendor cumulative tracker reset.

Stream 6 — Commission / brokerage. ₹50 lakh annual across freight-forwarder commission split (see Stream 1 freight forwarder treatment). Legacy 194H → Section 393(1)(j) code 1032 (commission subtype). 2% rate preserved.

Stream 7 — Rent. ₹2.4 crore annual on godown and finished-goods warehouse leases. Legacy 194-I → Section 393(1)(e) code 1042. Building 10%, plant and machinery 2%, preserved. Where the company also pays small rent on rural land where the legacy 194-IB applied, the equivalent under the new section reference handles individual / HUF deductors.

Stream 8 — Foreign-agent commission. ₹1.4 crore annual paid to overseas sales agents in Germany, the US and Japan on export programmes. Legacy 195 → Section 413 code 1062. DTAA Article 7 / no-PE handling preserved; Form 15CA / 15CB infrastructure preserved. See TDS on foreign agent commission under Section 413.

Stream 9 — Interest. ₹85 lakh annual interest paid on supplier credit facilities and intercompany advances. Legacy 194A → Section 393(1)(c) code 1022. 10% rate preserved.

ERP and Tally remapping checklist

Six configuration objects need explicit updates before 1 April 2026:

  1. Chart of accounts. Every legacy 194x / 195 / 206C ledger code needs a new sibling ledger under the new Section 393 / 394 / 413 reference. Most Tier-1s run both sets in parallel through Q1 FY 2026-27 to handle cross-era postings cleanly
  2. Payment templates. ERP and Tally payment-voucher templates must default to the new payment code when the invoice date is 1 April 2026 or later, and to the legacy code for earlier invoices. The date-of-payment-governs rule on the substantive deduction trigger must be embedded
  3. Deductee master. Every active deductee PAN (typical Tier-1 has 142 to 280 PANs) must have its applicable section code and rate updated under the new framework
  4. Return-output templates. Form 168 / 131 / 141 templates replace Form 26AS / 26Q / 27EQ in the return-generation toolkit. The XML / JSON schemas of the new forms are different and need fresh validation
  5. Deposit-challan templates. The banking integration that posts the monthly TDS / TCS challan must use the new payment code in the challan reference; legacy codes flag for pre-1-April-2026 entries
  6. Cross-era reconciliation register. A parallel register that carries both legacy and new code lineages, with the date-of-payment as the discriminator, runs through at least Q1 FY 2026-27
Interactive Tool

TDS payment code lookup

Confirm the new payment code for each of your nine auto-component payment streams across Sections 393, 394 and 413 — and verify the legacy 194x mapping for cross-era entries.

Open the TDS payment code lookup →

Form 26AS migration to Form 168 / 131 / 141

The deductee-side reconciliation moves from Form 26AS to Form 168 — same conceptual role, new code taxonomy, continuous (rather than lagged) update from deductor filings. The supplier downloads Form 168 monthly from the TRACES portal and reconciles each OEM TAN line against the supplier’s own books — matching gross invoice value, deduction percentage, deduction amount, deposit reference and payment code. For the detailed reconciliation discipline see Form 26AS / Form 168 reconciliation for auto-component suppliers.

The deductor-side filing moves from Form 26Q (non-salary TDS) to Form 131 filed quarterly, and from Form 27EQ (TCS) to Form 141 filed quarterly. The deductor’s quarterly statement carries every deduction made in the period, identified by payment code, deductee PAN, gross amount, TDS deducted, dates of deduction and deposit. Cross-era handling in the form: legacy 194x deductions on FY 2025-26 invoices reported on legacy Form 26Q / 27EQ, new code deductions on FY 2026-27 invoices reported on Form 131 / 141.

Worked example — the ₹400 crore Tier-1 Q1 FY 2026-27 close

The Pune supplier closes its first quarter under the new regime — three months of nine-stream operation. Quarterly totals:

  • Inbound freight (code 1002): ₹1.05 crore freight payments; TDS deducted ₹1,68,000 across all transporter PANs (excluding declaration-exempt). Form 131 carries 38 deductee lines
  • Job-work conversion (code 1002): ₹10 lakh conversion charges; TDS deducted ₹15,000 across four job-workers. Form 131 carries 4 deductee lines
  • Buyer-side purchase TDS (code 1012): ₹60 crore raw-material purchase from 18 suppliers; six suppliers crossed ₹50 lakh aggregate in Q1; 0.1% TDS on the above-₹50-lakh portion = ₹2,40,000 across the six. Form 131 carries 6 deductee lines
  • Seller-side scrap TCS (code 1071): ₹1.5 crore scrap-sale revenue; 1% TCS = ₹1,50,000 collected from scrap merchants. Form 141 carries the deductee lines
  • Professional fees (code 1032): ₹95 lakh professional fees; TDS at 10% = ₹9,50,000 across 8 active professional vendors. Form 131 carries 8 deductee lines
  • Forwarder commission (code 1032): ₹12 lakh forwarder commission; 2% = ₹24,000 across 3 forwarders. Form 131 carries 3 deductee lines
  • Rent (code 1042): ₹60 lakh quarterly rent; 10% on building portion = ₹6,00,000 across 3 landlords. Form 131 carries 3 deductee lines
  • Foreign-agent commission (code 1062): €30,000 quarterly commission to German agent; DTAA Article 7 / no-PE — no TDS. Form 15CA Part D filed. Form 131 carries no line
  • Interest (code 1022): ₹21 lakh interest paid; 10% = ₹2,10,000 across 2 lenders. Form 131 carries 2 deductee lines

Q1 FY 2026-27 TDS deposited: approximately ₹22 lakh across the seven deducting streams; TCS collected: ₹1.5 lakh on scrap. Deductee credit appears in each deductee’s Form 168 within 4-6 weeks of deductor filing.

Cross-era cross-reference. Q4 FY 2025-26 entries (1 January 2026 to 31 March 2026) sit on legacy Form 26Q / 27EQ under 194x / 206C codes. The Q4 ₹6.5 lakh TDS on conversion charges, ₹35 lakh on professional fees, and ₹1.4 lakh on scrap TCS continue to reconcile against legacy Form 26AS for each deductee. The cross-era register holds both lineages without netting through FY 2026-27.

Where the FY 2026-27 transition breaks in practice

Four recurring failure modes across the ₹400 crore Tier-1 scale:

  1. ERP default-code lag. The ERP payment template doesn’t switch defaults on 1 April 2026, and the first week of April invoices get posted to legacy 194x codes. The cross-era register has to absorb these as one-off mismatches and re-route them
  2. Tally voucher template fragmentation. Tally voucher templates configured separately per finance team member don’t all get updated at the same time. Some entries land on legacy codes through April even after the central chart of accounts is updated
  3. Deductee master section-code drift. A new vendor onboarded in April gets the new section code, but a vendor already in the master at 31 March retains its legacy section-code tag, leading to inconsistent deduction logic across the master
  4. Form 131 / 141 schema validation surprises. The XML / JSON schemas for the new forms reject entries that pass legacy 26Q / 27EQ validation. The first quarterly filing in late July 2026 surfaces schema issues that the parallel-run testing should have caught
Interactive Tool

TDS mismatch estimator

Estimate the value at risk from cross-era TDS / TCS misclassification across the nine auto-component payment streams during the FY 2026-27 transition.

Open the TDS mismatch estimator →

How this rail ties into the wider auto stack

The FY 2026-27 transition affects every TDS / TCS surface a Tier-1 carries. It sits alongside the Section 393(1)(a) job-work TDS leg, the Section 394 scrap TCS leg, the Form 26AS / Form 168 reconciliation discipline, and the broader automotive component manufacturing reconciliation sub-pillar. For the consolidated code map see TDS payment codes 1001-1092. For statutory text and form schemas see the Income Tax portal.

What automated reconciliation changes

Manual nine-stream remapping across 142+ deductee PANs, ERP and Tally code-master drift, cross-era 194x / 393 / 394 / 413 reconciliation, monthly Form 168 download against each OEM TAN, and quarterly Form 131 / 141 generation is where transition-year exposure compounds invisibly. Purpose-built auto component reconciliation software India holds the code-mapping master, drives the payment-code remap into ERP and Tally outputs, runs the parallel cross-era register through FY 2026-27, generates Form 131 / 141 quarterly with code-segregated totals, and reconciles each deductee against Form 168 monthly. TransactIG carries 24+ industry presets including a transition-year configuration for the new TDS / TCS regime. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the broader deductee-side reconciliation see TDS reconciliation software.

Primary reference: Income Tax Department of India — for Sections 393, 394 and 413 of the Income Tax Act 2025, the full payment-code map 1001 to 1092, Forms 168 / 131 / 141 and the cross-era mapping framework with legacy 194x sections of the Income Tax Act 1961.

Frequently Asked Questions

Which sections of the new Income Tax Act 2025 replace the auto-component-relevant TDS provisions of the 1961 Act?
Three new umbrella sections cover the auto-component supplier's TDS / TCS surface. Section 393 covers most resident-payee deductions — Section 393(1)(a) replaces Section 194C for contractor / job-work TDS at payment code 1002, Section 393(1)(j) replaces Section 194H for commission and brokerage at payment code 1032, Section 393(1)(k) replaces Section 194Q for buyer-side purchase TDS at payment code 1012, Section 393(1)(d) replaces Section 194J for professional and technical services at payment code 1032 (with subtype). Section 394 covers TCS — Section 394(1) handles seller-side scrap TCS at payment code 1071 and Section 394(2) handles other TCS categories. Section 413 replaces Section 195 for payments to non-residents, with payment code 1062 covering most non-resident commission and service remittances. Rent payments by individuals and HUFs (legacy Section 194-IB) move to a new section with payment code 1042. The economic effect of the change is broadly neutral; the statute, the section reference, the payment code and the return form are all new.
Which new Forms replace Form 26AS and Form 26Q?
Three Forms replace the legacy infrastructure. Form 168 is the new consolidated tax-credit statement (the deductee-side view replacing Form 26AS), continuously updated as deductors file their quarterly statements. Form 131 is a quarterly statement filed by deductors for non-salary TDS (broadly replacing Form 26Q). Form 141 is a quarterly statement filed by collectors for TCS (broadly replacing Form 27EQ). The substantive content is similar across the eras — TAN, deductee PAN, gross amount, deduction amount, deposit reference, payment code — but the code taxonomy in the new forms uses the 1001-1092 range instead of the legacy 194x / 195 / 206C references, and the forms carry a coherent cross-era mapping section for FY 2026-27 to allow legacy entries to be reconciled against new entries during the transition window. The deposit cadence (7th of the following month for deductions, 7th of the following month for collections) is preserved.
What does Section 394(1) do that legacy Section 206C did not, especially for auto-component scrap sales?
Section 394 of the Income Tax Act 2025 reorganises TCS into a single umbrella with payment codes in the 1071-1085 range, mirroring the substantive coverage of legacy Section 206C. Section 394(1) carries scrap-sale TCS at payment code 1071 — preserving the 1% rate on sale of scrap by a manufacturer to a buyer, with a buyer-declaration exemption where the scrap is purchased for further manufacture (legacy Form 27C, preserved under a new form reference). The substantive change is the procedural integration — the same Form 141 captures all TCS streams under Section 394 with code-segregated reporting, instead of the legacy Form 27EQ structure. For an auto-component Tier-1 selling stamping skeleton scrap, turning scrap, casting runners and risers, and end-of-life tooling, Section 394(1) is the daily provision; the analysis runs the same as it did under Section 206C(1) on the substantive scrap-sale leg. Section 394 also picks up the buyer-side counterpart that was historically split across Section 194Q and Section 206C(1H) — see Section 393(1)(k) at payment code 1012 for buyer-side purchase TDS.
Which auto-component payment streams need an ERP / Tally remapping before 1 April 2026?
At a typical ₹400 crore Tier-1, nine payment streams need code remapping in the ERP or Tally chart of accounts: (1) inbound freight at code 1002 (was 194C), (2) job-work conversion charges at code 1002 (was 194C), (3) buyer-side purchase TDS on raw-material procurement above ₹50 lakh per supplier per FY at code 1012 (was 194Q), (4) seller-side scrap-sale TCS at code 1071 (was 206C(1H) / 206C(1)), (5) professional fees and technical services at code 1032 (was 194J), (6) commission and brokerage on freight-forwarder splits at code 1032 (was 194H), (7) rent on godown / warehouse leases at code 1042 (was 194-I / 194-IB), (8) foreign-agent commission at code 1062 (was 195), (9) interest on supplier credit facilities at code 1022 (was 194A). Each stream needs the section code, the rate matrix, the threshold logic and the form-output mapping updated. Most Tier-1s run a parallel set of code masters from Q4 FY 2025-26 to allow side-by-side reconciliation through Q1 FY 2026-27.
How does Section 393(1)(k) buyer-side TDS interact with Section 394(1) seller-side TCS on the same auto-component transaction?
The two provisions cover opposite sides of the same transaction. Section 393(1)(k) at payment code 1012 requires a buyer with annual turnover above ₹10 crore to deduct 0.1% TDS on purchase of goods from a seller where the aggregate purchase value from that seller exceeds ₹50 lakh in the FY. Section 394 at payment codes 1071-1085 requires a seller to collect TCS on certain categories of sale (notably scrap at code 1071). For an auto-component Tier-1 buying raw steel coils above ₹50 lakh from Tata Steel, the Tier-1 is the buyer and Section 393(1)(k) at code 1012 bites — 0.1% TDS deducted by the Tier-1 on Tata Steel's invoice. For the same Tier-1 selling stamping-skeleton scrap to a scrap merchant, Section 394(1) at code 1071 bites — 1% TCS collected by the Tier-1 on the scrap merchant's payment. The two provisions do not stack on the same transaction — buyer TDS under Section 393(1)(k) and seller TCS under Section 394 cover opposite-direction flows. Legacy Section 194Q and Section 206C(1H) had a specific overlap rule (TDS prevails over TCS when both could apply) that is preserved into the new framework — Section 393(1)(k) takes precedence over Section 394(2) collateral provisions on the same goods purchase.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.