Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian Tier-1 auto-component manufacturer with ₹3.6 crore of annual TDS receivable across 6 to 8 OEM TANs — Maruti, Hyundai, Tata Motors, Mahindra, Ashok Leyland, Daimler India — must reconcile every monthly Form 168 download against the supplier's invoice ledger across seven mismatch classes (deductor-deposit gap, wrong section code, wrong PAN, amount difference, period difference, Section 393(1)(k) versus Section 394(1) confusion, timing) on multiple payment codes (1002 contractor, 1012 purchase, 1062 foreign commission, 1071 scrap TCS), during the FY 2026-27 cross-era window where legacy 194x deductions and new 1001-1092 deductions coexist on the same deductee Form 168 view. Manual reconciliation at this scale leaks 8 to 15% of TDS receivable into never-claimed credit, with the cross-era complication doubling the risk through FY 2026-27.
Run a monthly Form 168 download routine on the 12th to 15th of every month, segregate entries by deductor TAN and payment code, match each line against the supplier's books on invoice-number / gross-billing / deduction-rate / deduction-amount / period, classify mismatches into the seven recurring classes, route each mismatch into a deductor-correction-required dispute register with TRACES correction tracking, hold legacy 194x lineage and new 1001-1092 lineage on parallel tracks without netting, file a quarterly controller-level reconciliation summary, and close the cross-era overlap through FY 2026-27 with separate dispute columns for legacy and new lineages.
Deductor master with TAN and PAN, applicable payment-code matrix per OEM, supplier invoice ledger with gross-value / GST-split / pre-GST-value / section-code mapping, monthly Form 168 download calendar with TRACES login automation, monthly Form 26AS download for cross-era FY 2025-26 entries still in correction, mismatch classification taxonomy (seven classes), dispute register with deductor-correction-action flag and TRACES tracking, cross-era reconciliation rule routing pre-1-April-2026 deductions to legacy 194x / Form 26AS and post-1-April-2026 deductions to Form 168 / 131 / 141, and a controller-level dashboard of reconciliation health per OEM TAN.
A monthly Form 168 reconciliation dashboard segmented by OEM TAN and payment code, a TDS mismatch dispute register ranked by deductor-action-required status across the seven mismatch classes, a quarterly Form 168 / Form 26AS versus books variance summary for controller-level review, a cross-era register flagging any deduction with code-mismatch during the FY 2026-27 transition, and an audit-defensible trail linking every Form 168 entry to its source invoice, payment code, and TRACES correction history.
A Sriperumbudur-based Tier-1 auto-component manufacturer — making engine-bracket and chassis-bracket stampings for Hyundai Motor India, Kia India, Renault-Nissan and Royal Enfield — runs ₹3.6 crore of annual TDS receivable from 6 OEM TANs. On 14 May 2026 the finance controller opens the May Form 168 download, the first full month under the Income Tax Act 2025 framework. ₹28 lakh of fresh deductions appear across the 6 OEM TANs at new payment codes 1002 (contractor, conversion charges and tooling) and 1012 (buyer-side purchase, where each OEM has crossed ₹50 lakh purchase of finished components from the supplier). Eleven of the 84 individual Form 168 lines this month do not match the supplier’s books — a 13% first-pass mismatch rate that the controller knows will compound through Q1 if not worked aggressively.
This is 26AS Form 168 vs books reconciliation auto manufacturer at the live operational edge — seven recurring mismatch classes, two parallel form lineages (Form 168 for new-Act entries, Form 26AS still alive for FY 2025-26 corrections), multi-OEM TAN segregation, multi-code reporting (1002 / 1012 / 1062 / 1071), and the cross-era window through FY 2026-27 where legacy 194x and new code entries coexist. This article walks the monthly reconciliation routine, the seven mismatch classes with worked resolutions, the cross-era handling, the TRACES correction protocol, and the worked example on the ₹3.6 crore annual receivable.
Quick reference
| Element | Under new framework (FY 2026-27 onwards) | Legacy / cross-era reference |
|---|---|---|
| Deductee tax-credit statement | Form 168 (continuous update from TRACES) | Form 26AS for FY 2025-26 and earlier |
| Deductor non-salary quarterly statement | Form 131 | Form 26Q for legacy |
| Collector TCS quarterly statement | Form 141 | Form 27EQ for legacy |
| Contractor / conversion / freight TDS code | 1002 (Section 393(1)(a)) | 194C legacy |
| Buyer-side purchase TDS code | 1012 (Section 393(1)(k)) | 194Q legacy |
| Seller-side scrap TCS code | 1071 (Section 394(1)) | 206C(1) / 206C(1H) legacy |
| Foreign-agent commission TDS code | 1062 (Section 413) | 195 legacy |
| Monthly reconciliation cadence | 12th to 15th of every month | Unchanged |
| Mismatch class count | 7 recurring classes | Same classes apply to legacy era |
| TRACES correction window | Open continuously | Same |
| Cross-era reconciliation requirement | Through FY 2026-27 | n/a |
The monthly Form 168 download routine
The discipline starts on a fixed date each month. Most Tier-1s schedule Form 168 download between the 12th and the 15th — after the deductor 7th-of-the-month deposit cycle has completed and the TRACES portal has refreshed against deductor filings. The download is keyed by the supplier’s PAN, covering all deductor TANs that have filed deductions against that PAN in the most recent month and across the FY-to-date.
The five-step routine:
- Download Form 168. Single TRACES portal session, download CSV / XML for the most recent month and the FY-to-date. Where any FY 2025-26 lineage is still in correction (legacy 194x dispute open at the OEM end), also download Form 26AS for the relevant period
- Segregate by deductor TAN. A typical Tier-1 has 4 to 8 OEM TANs (multiple plants of the same OEM sometimes operate under different TANs) and 1 to 3 large customer TANs. Each TAN reconciles separately
- Match each Form 168 line against the supplier’s books. Invoice number, gross billing, TDS deduction percentage, deducted amount, payment code, period of deduction
- Classify mismatches. Every unmatched line gets routed into the seven-class dispute register with the appropriate deductor-correction-required flag
- Quarterly controller-level summary. End of each quarter, the controller reviews matched / mismatched / under-investigation / closed positions per OEM TAN, with year-to-date totals and projected exposure
The wider monthly Form 168 routine in the auto-supplier context is set out in Form 26AS reconciliation for auto-component suppliers, and the supplier’s broader operational reconciliation in automotive component manufacturing reconciliation.
The seven mismatch classes
Class 1 — Deductor deposited but not filed. The OEM has deducted TDS on the supplier’s invoice and deposited the amount on the monthly challan by the 7th, but has not yet filed the quarterly Form 131 (or hasn’t completed the filing for the quarter the entry belongs to). The deduction does not appear in Form 168 until the deductor’s filing reaches TRACES. Resolution: wait for deductor filing, recheck after Form 131 due date.
Class 2 — Wrong section code. The OEM’s AP system has deducted at the wrong code — code 1002 (contractor) when the underlying transaction was a goods purchase (code 1012), or code 1012 when the transaction was a tooling supply that should not have attracted TDS at all. Resolution: dispute filed with deductor, TRACES correction statement requested with corrected section code reference.
Class 3 — Wrong PAN. The OEM has used a historical PAN (sister-concern, restructured-entity, or a PAN from a 2023-vintage master that should have been deactivated), or a typo’d PAN. The supplier’s current PAN does not see the credit at all. Resolution: dispute with PAN evidence (PAN card, latest TDS certificate showing supplier PAN), TRACES correction to update PAN.
Class 4 — Amount difference. The OEM has deducted on a value that includes GST when the contract specifies TDS on pre-GST value, or vice versa. For a ₹1 crore invoice with 18% GST, deducting on ₹1.18 crore versus ₹1 crore swings the deduction amount by 18%. Resolution: contract reference cited, dispute filed with deductor for amount correction.
Class 5 — Period difference. The OEM has booked the deduction in a different quarter from the supplier’s invoice recognition — supplier’s books show the invoice in Q1 (April-June), but the deductor’s Form 131 reports the deduction in Q2 (July-September) because payment was actually made in July. This is not a substantive mismatch but a timing one. Resolution: usually no correction needed, but the reconciliation register must show the period-difference explanation so the year-end position closes cleanly.
Class 6 — Section 393(1)(k) versus Section 394(1) confusion. On a goods purchase where the contract includes return-scrap recovery, the buyer-side TDS (Section 393(1)(k) code 1012) and the seller-side TCS (Section 394(1) code 1071) cover separate legs of the same gross transaction. The OEM’s Form 131 may combine the two into a single entry, or split them incorrectly. Resolution: contract-leg analysis, dispute filed with correct buyer-leg / seller-leg split.
Class 7 — Timing. Quarter-end straddles. An invoice raised on 28 June 2026 paid on 4 July 2026 — supplier may book the receivable in Q1, deductor books deduction in Q2 because payment is in July. Cross-FY straddles (28 March 2026 invoice paid 4 April 2026) are the most operationally important class because they cross the era boundary too — and the deduction quarter and Act-era determination both turn on the date of payment.
Cross-era handling through FY 2026-27
The cross-era window starts on 1 April 2026 and runs through at least FY 2026-27 — possibly longer if legacy 194x corrections are still being worked at the OEM end. The reconciliation register must hold two parallel lineages without netting:
- Legacy 194x lineage: any deduction made on or before 31 March 2026 (date of payment governs). Reports on legacy Form 26Q (deductor) and Form 26AS (deductee). TRACES corrections under legacy 194x identifiers
- New 1001-1092 lineage: any deduction made on or after 1 April 2026. Reports on Form 131 (deductor) and Form 168 (deductee). TRACES corrections under new section identifiers
A 28 March 2026 invoice paid 5 April 2026 — date of payment governs, so the deduction sits on the new lineage. A 28 March 2026 invoice paid 31 March 2026 — both pre-1-April, deduction sits on legacy lineage. The dispute register holds both lineages in separate columns; an OEM correcting a legacy 194x entry in May 2026 does not netting against a new code-1002 deduction in the same month, even though both relate to the same supplier-OEM pair.
The annual ₹1,00,000 aggregate threshold (for Section 393(1)(a) contractor TDS) does not carry forward — a fresh cumulative starts on 1 April 2026 under the new framework. The Section 393(1)(k) ₹50 lakh aggregate also resets. The buyer-side / seller-side code map (1012 versus 1071) needs the OEM and the supplier to align on the leg classification.
The wider statutory shift is set out in TDS payment codes 1001-1092, and the comprehensive transition framework in New TDS and TCS provisions FY 2026-27 for auto-component suppliers.
TDS mismatch estimator
Estimate the value of TDS credit at risk across the seven mismatch classes for your OEM-TAN portfolio — segregated by code 1002 / 1012 / 1062 / 1071 and by cross-era lineage.
Open the TDS mismatch estimator →Worked example — ₹3.6 crore annual TDS receivable for a Hyundai Tier-1
The Sriperumbudur supplier ships engine-bracket stampings to Hyundai Motor India (Sriperumbudur and Talegaon plants), Kia India (Anantapur), Renault-Nissan (Oragadam), Royal Enfield (Oragadam), Ashok Leyland (Hosur), and Daimler India Commercial Vehicles (Oragadam). FY 2026-27 annual TDS receivable profile across 6 OEM TANs:
| OEM TAN | Annual TDS receivable | Primary code | Secondary code |
|---|---|---|---|
| Hyundai Motor India — Sriperumbudur | ₹1,12,00,000 | 1002 (conversion / tooling) | 1012 (purchase) |
| Hyundai Motor India — Talegaon | ₹68,00,000 | 1002 | 1012 |
| Kia India — Anantapur | ₹54,00,000 | 1002 | 1012 |
| Renault-Nissan — Oragadam | ₹48,00,000 | 1002 | 1012 |
| Royal Enfield — Oragadam | ₹38,00,000 | 1002 | 1012 |
| Ashok Leyland — Hosur | ₹24,00,000 | 1002 | 1012 |
| Daimler India CV — Oragadam | ₹16,00,000 | 1002 | 1012 |
| Total | ₹3,60,00,000 |
May 2026 reconciliation results. The supplier’s controller works the 84 individual Form 168 lines downloaded on 14 May 2026:
- 73 lines match cleanly across invoice number / gross billing / deduction percentage / deduction amount / period — 87% first-pass match
- 11 lines mismatch:
- 3 Class 1 (Hyundai Sriperumbudur — deductor deposited but Form 131 for Q1 not filed yet, will resolve at end of July) — ₹1.8 lakh value
- 2 Class 2 (Kia — code 1002 used on a tooling lump-sum that should have been no-TDS reimbursement) — ₹3.6 lakh over-deduction, dispute filed
- 1 Class 3 (Renault-Nissan — wrong PAN on a fresh deduction, used a 2023 historical PAN of the supplier’s sister concern) — ₹1.2 lakh value, dispute filed with PAN evidence
- 2 Class 4 (Royal Enfield — deducted on GST-inclusive value when contract specifies pre-GST) — ₹0.6 lakh value, contract-reference dispute filed
- 1 Class 5 (Ashok Leyland — period difference, April invoice deduction shown in May due to payment timing) — ₹0.4 lakh value, period-explanation noted, no dispute
- 1 Class 6 (Hyundai Talegaon — purchase plus return-scrap leg combined into one Form 168 entry under code 1012, should have been split between code 1012 and code 1071) — ₹0.8 lakh value, leg-split dispute filed
- 1 Class 7 (Daimler India CV — Q4 FY 2025-26 invoice paid 8 April 2026, sits on new lineage code 1002 but OEM’s books show it on legacy 194C) — ₹0.4 lakh value, cross-era correction dispute filed
Quarterly summary at end of Q1 (30 June 2026). Controller reviews matched / mismatched / under-investigation / closed positions. Of the 11 May mismatches: 4 closed (Class 1 resolved on Form 131 filing, Class 2 corrected via TRACES, Class 3 corrected, Class 5 explanation accepted), 7 still under investigation. Q1 cumulative match rate: 88%. Cross-era register: 12 entries on legacy 194x lineage (Q4 FY 2025-26 entries still in correction at the OEM end), 84 entries on new 1001-1092 lineage.
Cross-era cross-reference. A Q4 FY 2025-26 ₹4.8 lakh dispute against Renault-Nissan from February 2026 (legacy Section 194C wrong-PAN class) is still open at the deductor end; the supplier’s Form 26AS dispute register tracks it on legacy lineage. The same Renault-Nissan TAN has fresh May 2026 deductions at code 1002 in Form 168; the new-lineage register tracks those separately. No netting between the two.
How the TRACES correction protocol runs
For each mismatch in classes 2 / 3 / 4 / 6 / 7 where a deductor-correction is needed:
- Supplier raises a written dispute. Email to OEM’s tax team with invoice number, Form 168 entry, supplier’s books position, requested correction
- Supporting documentation. Original invoice, contract reference, payment advice
- OEM files TRACES correction statement. Under the appropriate provision (legacy 194x for FY 2025-26 entries, new section for FY 2026-27 entries)
- Correction reflects in Form 168. Typical TAT 2 to 6 weeks
- Supplier verifies and closes. Dispute register entry closed; year-to-date reconciliation refreshed
For Class 1 (no correction needed, just deductor filing pending) and Class 5 (period difference, no substantive correction), the dispute register holds the entry until the natural resolution and then closes.
Where Form 168 reconciliation breaks at scale
Four recurring failure modes at the ₹3.6 crore receivable scale:
- Late download cadence. Tier-1s that download Form 168 only quarterly miss the early-warning on Class 1 deductor-filing gaps and Class 2 wrong-code disputes — by the time the quarter closes, the volume of mismatches is unmanageable
- Single-PAN download missing TAN-segregation. Form 168 downloaded as a single supplier-PAN view without TAN segregation makes it impossible to reconcile against the 6 to 8 OEM-side books — every line has to be re-segregated manually
- Cross-era netting. Legacy 194x corrections netted against new code-1002 deductions in the same register entry — the cross-era discipline gets compromised and the Form 26AS / Form 168 trails diverge in audit
- Section 393(1)(k) versus Section 394(1) leg confusion. On goods-purchase contracts with return-scrap clauses, the two legs end up in the same Form 168 line and the supplier-side books cannot reconcile against a combined entry. The leg split has to be insisted on contractually
Section 393(1)(k) vs 394 threshold determiner
Resolve Class 6 mismatches at source — determine which provision bites and at what code on transactions that carry both purchase and scrap legs.
Open the threshold determiner →How this rail ties into the wider auto stack
Form 168 versus books reconciliation is the deductee-side discipline that completes the TDS / TCS rail. It sits alongside the Form 26AS reconciliation for auto-component suppliers reference framework, the Section 393(1)(a) job-work TDS outbound leg, and the broader automotive component manufacturing reconciliation sub-pillar. For the consolidated code map see TDS payment codes 1001-1092. For statutory text and TRACES correction infrastructure see the Income Tax portal.
What automated reconciliation changes
Manual Form 168 reconciliation across 6 to 8 OEM TANs, 84+ monthly deduction lines, seven mismatch classes, four payment codes (1002 / 1012 / 1062 / 1071), and the cross-era 194x / 1001-1092 overlap through FY 2026-27 is where 8 to 15% of annual TDS receivable leaks into never-claimed credit. Purpose-built auto component reconciliation software India holds the monthly Form 168 download routine, segregates by TAN and code, runs the invoice-level match against the supplier’s books, classifies mismatches into the seven classes, routes each into the TRACES correction protocol, holds the cross-era register on parallel lineages without netting, and surfaces the controller-level quarterly summary. TransactIG carries 24+ industry presets including an OEM-TAN reconciliation 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.