Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian Tier-1 auto-component supplier transitioning across 1 April 2026 must reconcile two parallel TDS / TCS lineages through an 8 to 12-month cross-era window — legacy 194x deductions on FY 2025-26 invoices flowing through Form 26Q (deductor) and Form 26AS (deductee), and new Section 393 / 394 / 413 deductions on FY 2026-27 invoices flowing through Form 131 / 141 (deductor) and Form 168 (deductee). Straddling invoices (raised pre-1-April-2026 but paid post-1-April-2026) need the date-of-credit-or-payment-whichever-is-earlier test applied invoice by invoice; ITR cross-era credit claims need legacy and new lineages mapped to the correct assessment year; missing-deduction discoveries from Q4 FY 2025-26 stay under legacy lineage; and the supplier's reconciliation register must hold both lineages without netting through to roughly Q3 FY 2026-27 close.
Maintain dual-lineage reconciliation registers — one for legacy 194x entries on FY 2025-26 invoices (matched to Form 26Q deductor filings and Form 26AS deductee credits, with TRACES corrections raised under legacy identifiers), one for new section entries on FY 2026-27 invoices (matched to Form 131 / 141 deductor filings and Form 168 deductee credits, with TRACES corrections under new identifiers). For every straddling invoice, apply the time-of-deduction test — earlier of date of credit or date of payment — to assign to the correct lineage. Run monthly Form 168 download (and Form 26AS download for any open legacy lineage), reconcile against the supplier's books, route mismatches into the appropriate dispute register. Prepare the FY 2025-26 and FY 2026-27 ITRs separately, claiming legacy 194x credits against FY 2025-26 income and new 1001-1092 credits against FY 2026-27 income, with explicit cross-era schedules where the income year and deduction year diverge.
Cross-era register with date-of-credit-or-payment discriminator field, legacy-lineage register tagged with 194x section codes and Form 26AS / Form 26Q references, new-lineage register tagged with Section 393 / 394 / 413 codes and Form 168 / 131 / 141 references, straddling-invoice flag (1 January 2026 to 30 April 2026 invoices), ITR cross-era schedule preparation pack, deductor-correction tracking on both lineages, and a controller-level dashboard of cross-era reconciliation health through FY 2026-27.
A cross-era dashboard showing legacy and new lineage entries side-by-side without netting, straddling-invoice resolution log with the date-of-payment-governs determination on each, monthly Form 168 and Form 26AS reconciliation summary, ITR Schedule TDS / TCS preparation pack mapping legacy entries to FY 2025-26 and new entries to FY 2026-27, the deductor-correction dispute register on both lineages, and an audit-defensible trail of every cross-era decision.
A Bangalore-based Tier-1 auto-component supplier — making fuel-system components, plastic injection-moulded interiors and electronic housings for Toyota Kirloskar, Bosch India and Hyundai Motor India — runs its first full month under the new TDS / TCS regime in April 2026. The finance shared services team has prepared for the 1 April 2026 changeover for six months. ERP code masters are remapped, deductee files updated, the Q4 FY 2025-26 legacy 194x deductions have been reconciled clean through end-March, and the Q1 FY 2026-27 new section deductions at codes 1002 (contractor, conversion charges and freight) and 1012 (buyer-side raw-material purchase TDS) are being captured against fresh ledgers. But on 12 May 2026 the controller opens the Form 168 download for April and finds 14 deductions across the OEM TANs that straddle the era boundary — invoices raised in mid-to-late March 2026 paid in early-to-mid April 2026. Each one needs the date-of-credit-or-payment-whichever-is-earlier test applied. Each one then sits on either the legacy 194x lineage (Form 26Q / Form 26AS) or the new Section 393 lineage (Form 131 / Form 168). The reconciliation register must hold both without netting, and the ITR for FY 2026-27 needs the schedule prepared with explicit cross-era handling.
This is auto component TDS TCS cross-era reconciliation India at the live operational edge — an 8 to 12-month overlap window from 1 April 2026 to roughly Q3 FY 2026-27 close, during which two Acts, two sets of forms, two filing tracks and two TRACES correction protocols coexist on the same deductee’s tax-credit view. This article walks the time-of-deduction test, the dual-lineage register discipline, the ITR cross-era credit claim, the legacy-lineage missing-deduction handling, and the worked example on the 28 March 2026 invoice paid 15 April 2026.
Quick reference
| Element | Legacy lineage (FY 2025-26 invoices) | New lineage (FY 2026-27 invoices) |
|---|---|---|
| Statute | Income Tax Act 1961 | Income Tax Act 2025 |
| Contractor / conversion / freight section | Section 194C | Section 393(1)(a) at code 1002 |
| Buyer-side purchase section | Section 194Q | Section 393(1)(k) at code 1012 |
| Foreign-agent commission section | Section 195 | Section 413 at code 1062 |
| Seller-side scrap TCS section | Section 206C(1) / 206C(1H) | Section 394(1) at code 1071 |
| Deductee tax-credit statement | Form 26AS | Form 168 |
| Deductor non-salary quarterly statement | Form 26Q | Form 131 |
| Collector TCS quarterly statement | Form 27EQ | Form 141 |
| Time-of-deduction discriminator | Earlier of credit or payment | Same test, applied to 1 April 2026 boundary |
| TRACES correction infrastructure | Legacy 194x identifiers | New section identifiers |
| Practical cross-era window | n/a | 1 April 2026 to approx Q3 FY 2026-27 close |
| ITR assessment year for legacy deductions | AY 2026-27 (FY 2025-26 income) | n/a |
| ITR assessment year for new deductions | n/a | AY 2027-28 (FY 2026-27 income) |
What is the cross-era window and why does it run 8 to 12 months?
The regime change is statutory — on 1 April 2026, the Income Tax Act 2025 replaces the Income Tax Act 1961 for TDS and TCS provisions on transactions on or after that date. But operationally, deductions that happened on or before 31 March 2026 keep generating downstream activity for months — Q4 FY 2025-26 Form 26Q is due at end-July 2026, the resulting Form 26AS entries refresh for several weeks after that, TRACES corrections opened against any of those entries take 2 to 6 weeks each, and disputes raised by the deductee can stretch resolution into Q3 FY 2026-27 or beyond.
For a typical Tier-1, the cross-era window runs:
- Q1 FY 2026-27 (April-June 2026): legacy Q4 FY 2025-26 deductions still flowing into Form 26Q filing window, new Q1 FY 2026-27 deductions being made at new codes
- Q2 FY 2026-27 (July-September 2026): legacy Q4 FY 2025-26 Form 26Q filed (end-July), Form 26AS refresh, peak legacy correction activity; first new Form 131 filing for Q1 FY 2026-27 (end-July) and any resulting dispute volume
- Q3 FY 2026-27 (October-December 2026): legacy lineage winding down (residual corrections), new lineage normalising
- Q4 FY 2026-27 and Q1 FY 2027-28: residual legacy disputes only; new lineage fully operational
The wider regime-change context is set out in New TDS and TCS provisions FY 2026-27 for auto-component suppliers and the deductee reconciliation discipline in Form 26AS / Form 168 vs books reconciliation for auto manufacturers.
The date-of-credit-or-payment-whichever-is-earlier test
Both Acts use the same time-of-deduction test for contractor / conversion / freight / professional / commission payments — the deduction is required at the time of credit to the payee’s account or at the time of payment, whichever is earlier. For most OEM-supplier transactions, the OEM AP system credits the supplier’s account in the same accounting event as payment (combined credit-and-pay journal entry), so the date of payment is the practical discriminator. For some OEMs that run separate credit-then-pay accounting, the date of credit precedes payment by a few days and can change the era determination.
Applied to the 1 April 2026 boundary:
- Both credit and payment on or before 31 March 2026: legacy 194x lineage, reports on Form 26Q (deductor) and Form 26AS (deductee)
- Earlier of credit and payment on or after 1 April 2026: new Section 393 / 394 / 413 lineage, reports on Form 131 / 141 (deductor) and Form 168 (deductee)
- Mixed case — credit on or before 31 March, payment on or after 1 April: legacy lineage applies because the earlier event is pre-1-April-2026
- Mixed case — credit on or after 1 April, payment on or before 31 March: rare in practice (payment usually follows credit), but if it occurs the earlier event again governs — payment was earlier and pre-1-April-2026, so legacy lineage
For TCS, the analogous test is the time of receipt of consideration (for scrap-sale TCS under Section 394(1) / legacy 206C(1)). Receipts on or after 1 April 2026 sit on the new lineage; before that, legacy.
How does the dual-lineage register work?
The reconciliation register holds two parallel tracks. The discriminator field — date of credit or date of payment, whichever is earlier — assigns each entry to one track:
Legacy lineage track:
- Section codes: 194C / 194Q / 194H / 194J / 194-I / 194-IB / 194A / 195 / 206C
- Forms: Form 26Q (deductor non-salary quarterly), Form 27EQ (collector TCS quarterly), Form 26AS (deductee tax-credit consolidated)
- TRACES corrections under legacy identifiers
- ITR claim: FY 2025-26 income against AY 2026-27 ITR
New lineage track:
- Section codes: 393(1)(a) / 393(1)(c) / 393(1)(d) / 393(1)(e) / 393(1)(j) / 393(1)(k) / 394(1) / 413
- Payment codes: 1002 / 1012 / 1022 / 1032 / 1042 / 1062 / 1071
- Forms: Form 131 (deductor non-salary), Form 141 (collector TCS), Form 168 (deductee)
- TRACES corrections under new identifiers
- ITR claim: FY 2026-27 income against AY 2027-28 ITR
The two tracks do not net against each other. An OEM raising a legacy 194C correction in May 2026 (correcting a Q4 FY 2025-26 deduction) does not offset against a fresh code-1002 deduction in the same month, even though both relate to the same OEM-supplier pair. The audit trail keeps the lineages separate.
ITR cross-era credit claim mechanics
The supplier’s FY 2025-26 ITR (due in July 2026 for non-audit cases, October 2026 for audit cases) consolidates all TDS / TCS credits the supplier is entitled to claim against FY 2025-26 income — drawn from legacy Form 26AS. This includes Q4 FY 2025-26 deductions made up to 31 March 2026 (on the date-of-credit-or-payment test).
The supplier’s FY 2026-27 ITR (due in July 2027 or October 2027) consolidates all TDS / TCS credits drawn from Form 168 (and any residual Form 26AS entries that turned out to belong to FY 2026-27 income but reported on legacy lineage by mistake — these need an Annexure explanation).
The complication arises where the income year and the deduction year diverge. An invoice raised 28 March 2026 (income recognised in FY 2025-26 under accrual accounting) paid 15 April 2026 (deduction made under new Act, reports on Form 168 against FY 2026-27 entries). The supplier:
- Recognises the revenue in FY 2025-26 books
- Claims the TDS credit in the FY 2026-27 ITR (because the deduction is on FY 2026-27 lineage)
- Explains the cross-era mismatch in an ITR Annexure with the supporting invoice and Form 168 reference
This pattern repeats across many straddling invoices in a typical Tier-1’s ledger. The cross-era register the supplier maintains through the year feeds directly into the ITR Schedule TDS / TCS preparation, with the income-recognition year and the deduction-year cross-tagged per entry.
TDS payment code lookup
Map every legacy 194x section to its new Section 393 / 394 / 413 counterpart and payment code, with the date-of-payment-governs rule explicit for straddling invoices.
Open the TDS payment code lookup →Worked example — 28 March 2026 invoice, paid 15 April 2026
The Bangalore Tier-1 raises a conversion-charge invoice to Toyota Kirloskar Motor for fuel-system component assembly:
- Invoice date: 28 March 2026
- Gross invoice value: ₹18,40,000 (₹15,59,322 conversion charge + ₹2,80,678 GST at 18%)
- Pre-GST conversion charge value (TDS basis): ₹15,59,322
- Toyota Kirloskar credit-to-supplier entry date: 14 April 2026 (Toyota’s AP runs combined credit-and-pay)
- Payment date: 15 April 2026
Time-of-deduction test. Earlier of credit (14 April 2026) and payment (15 April 2026) is 14 April 2026. Both events are post-1-April-2026. New lineage applies.
Section determination. Conversion charge — Section 393(1)(a) of the Income Tax Act 2025, at payment code 1002. Toyota Kirloskar is the deductor; supplier is the deductee (a Pvt Ltd company, 2% rate).
TDS computation. 2% on ₹15,59,322 = ₹31,186 deducted at code 1002.
Deductor side. Toyota’s tax team deposits ₹31,186 on the monthly TDS challan by 7 May 2026 with payment code 1002 against the supplier’s PAN. The deduction reports on Toyota’s Q1 FY 2026-27 Form 131 filed at end-July 2026.
Deductee side. The supplier sees the deduction reflect in Form 168 by mid-to-late July 2026 (post-Form 131 filing), at code 1002, against Toyota’s TAN. The supplier’s books recognised the revenue of ₹15,59,322 in FY 2025-26 (28 March 2026 invoice date, accrual basis). The TDS credit of ₹31,186 belongs on the FY 2026-27 ITR (AY 2027-28) because the deduction is on the new lineage.
ITR Annexure. The FY 2026-27 ITR Schedule TDS captures the ₹31,186 credit from Form 168. An Annexure note explains: invoice 28 March 2026, revenue in FY 2025-26 books, TDS deducted 14 April 2026 under new framework reporting in Form 168, claimed in FY 2026-27 ITR.
Cross-era register entry. Tagged: new lineage, straddling-invoice flag, FY 2025-26 income recognition, FY 2026-27 TDS lineage. Held through reconciliation cycle to ITR filing.
Alternate case — same invoice paid 30 March 2026 instead. Date of payment 30 March 2026 — pre-1-April-2026. Legacy lineage applies. Section 194C, Form 26Q. Toyota deposits by 7 April 2026 (still under legacy framework because the deduction event was March), files revised legacy Form 26Q for Q4 FY 2025-26 by end-July 2026. The supplier sees the credit on Form 26AS, claims it in the FY 2025-26 ITR (AY 2026-27). No cross-era complication on the ITR.
Missing-deduction discoveries on legacy lineage
A Q4 FY 2025-26 deduction missing in Form 26AS (because the OEM did not deduct or did not deposit) and discovered during the May 2026 Form 26AS reconciliation stays on legacy lineage. The supplier disputes with the deductor referencing the original invoice, the OEM files a TRACES correction statement under legacy Section 194C / 194Q / 195 / 206C identifiers, deposits the missing TDS belatedly with legacy Section 201(1A) interest, files a revised Form 26Q. The corrected entry reflects in the supplier’s Form 26AS within 4 to 8 weeks. The deduction is not migrated to the new Section 393 / 394 / 413 framework because the underlying event predates the regime change.
The corollary: a deduction made on or after 1 April 2026 by mistake under a legacy 194x code (because the OEM AP system did not switch defaults) needs a TRACES correction under the new framework — the OEM withdraws the legacy 194x entry from Form 26Q and refiles the deduction under Section 393 / 394 / 413 on Form 131 with the correct new code. The supplier reconciles the legacy-lineage withdrawal and the new-lineage entry as a single corrective sequence.
Where cross-era reconciliation breaks at scale
Five recurring failure modes in the cross-era window:
- Cross-era netting in the dispute register. A legacy 194x credit dispute resolved in favour of the supplier in June 2026 is netted against a new code-1002 over-deduction discovered in May 2026, blurring the audit trail. The two should resolve independently
- Wrong-Act default on straddling invoices. The OEM AP system defaults to legacy 194C on a 28 March 2026 invoice paid 15 April 2026 (failing the date-of-payment-governs test), generating a wrong-lineage Form 26Q entry that needs withdrawal and refiling under new Form 131
- ITR Schedule TDS mismapping. Cross-era credits not Annexed properly in the FY 2026-27 ITR — Form 168 credits on FY 2025-26 income claimed without explanation, triggering assessment queries
- Legacy correction lifetime overrun. A legacy 194x dispute that should have resolved in 2 to 6 weeks stretches into Q3 FY 2026-27 because the OEM tax team is focused on the new framework and de-prioritises legacy corrections. The supplier may need to escalate through commercial relationships
- Form 26AS withdrawal after Form 168 entry. A deduction initially reported on legacy Form 26AS at Q4 FY 2025-26 but actually belonging to the new lineage (the date-of-payment test was misapplied) requires a legacy-side withdrawal plus a new-side re-entry — getting both legs synchronised in the supplier’s books is fiddly
TDS mismatch estimator
Estimate the cross-era reconciliation value at risk — straddling invoices, legacy-lineage corrections, ITR cross-era credit claims across both lineages.
Open the TDS mismatch estimator →How this rail ties into the wider auto stack
Cross-era reconciliation is the transitional discipline that the FY 2026-27 close turns on. It sits alongside the New TDS / TCS provisions FY 2026-27 transition framework, the Form 26AS / Form 168 vs books reconciliation routine, the Form 26AS reconciliation for auto-component suppliers reference framework, and the broader automotive component manufacturing reconciliation sub-pillar. For the consolidated code map see TDS payment codes 1001-1092. For statutory text and cross-era TRACES infrastructure see the Income Tax portal.
What automated reconciliation changes
Manual cross-era reconciliation across straddling invoices, dual-lineage dispute registers, legacy-lineage TRACES corrections, new-lineage Form 131 reconciliation, and ITR cross-era credit claim preparation is where the regime-change exposure compounds most. Purpose-built auto component reconciliation software India holds the date-of-credit-or-payment discriminator per invoice, assigns each entry to the correct lineage, runs the parallel legacy and new dispute registers without netting, drives the ITR Schedule TDS / TCS preparation with cross-era Annexures, and surfaces the controller-level cross-era health dashboard through the full FY 2026-27 cycle. TransactIG carries 24+ industry presets including a cross-era transition-year configuration. 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 discipline see TDS reconciliation software.