Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
From April 1, 2026, every TDS challan, Form 131 (16A), and 26Q/27Q return must reference new Chapter XX section codes — Section 194C becomes 393(1)(a), 194J becomes 393(1)(b), 194H becomes 393(1)(f) — and ERPs still pointing to the 1961 Act codes will produce TRACES validation failures from day one.
Maintain a dual-code mapping master that links every legacy section (192–206CE) to its 2025 Act equivalent and the associated four-digit payment code. Classify each TDS transaction by deduction date — legacy codes for deductions up to March 31, 2026, new codes from April 1, 2026 — and apply the matching side's code set during reconciliation against Form 26AS (now Form 168) and deductor certificates.
Section mapping master with old code, new Section 393 sub-clause, payment code 1001–1092, and effective-date metadata. Cross-year matching mode (legacy, new, or dual) selected by transaction date.
Challans and returns that validate on the updated TRACES portal from day one, cross-year Form 26AS matching that handles both code sets simultaneously, and a clean audit trail showing each transaction against the section code in force on its deduction date.
From April 1, 2026, every TDS deduction your organisation makes, every challan you deposit, and every Form 16A you issue must reference section numbers from the new Income Tax Act 2025. The old section codes — 194C, 194J, 194H, 194I, and the rest — are being replaced by a new numbering under Chapter XX of the consolidated act. Finance teams that do not update their ERP configurations, reconciliation systems, and TRACES workflows before FY 2026-27 begins will generate challan mismatches and certificate errors from day one.
This guide gives you the complete mapping table, the document-by-document implications, and a cross-year reconciliation checklist.
What’s New in This Update
Since this guide was first published, three additional pieces of the FY 2026-27 transition have firmed up and are worth highlighting before the section-by-section detail below.
Payment codes 1001–1092. The new Income Tax Act 2025 introduces a numeric payment code system alongside the Section 393 sub-clause references. Every TDS transaction from April 1, 2026 will carry a four-digit payment code (for example, 1094 for Section 393(1)(a) contractor payments) in addition to the Chapter XX section reference. Reconciliation systems must be able to classify transactions by both identifiers. The full list is covered in the payment codes 1001–1092 reference.
Form renames (168, 131, 141). Three familiar TDS documents change names from April 1, 2026. Form 26AS becomes Form 168 (the annual TDS statement). Form 16A becomes Form 131 (the non-salary TDS certificate). Form 24G and related challan-cum-statement formats move to Form 141. The data structure is largely retained, but the document labels in your workflows, download scripts, and vendor communications need to be updated. See the Form 168 reconciliation walkthrough for the field-level changes.
Cross-era matching capability. Between April 2026 and approximately March 2029, every enterprise running TDS reconciliation will encounter mixed periods: FY 2025-26 entries with old section codes sitting alongside FY 2026-27 entries with new codes and payment codes. A dual-mode reconciliation configuration (legacy, payment_code, or dual) lets the same engine process both eras without manual intervention. Our cross-era TDS reconciliation guide covers how this dual-mode capability applies to FY 2025-26 corrections filed after April 2026, Form 16A certificates that span the transition, and variance codes for year-boundary deductions.
Why TDS Sections Are Being Renumbered
The Income Tax Bill 2025 (Bill No. 11 of 2025), introduced in Lok Sabha on February 13, 2025, proposes to replace the Income Tax Act 1961 entirely. The new act contains 536 clauses across 23 chapters. Chapter XX consolidates all Tax Deducted at Source and Tax Collected at Source provisions — sections that were previously scattered across Sections 192 through 206CE of the 1961 Act.
The renumbering is not a policy change. TDS rates, thresholds, deposit deadlines, and return filing requirements remain structurally identical. What changes is the section reference: the code that appears on challans, TDS certificates, and quarterly returns to identify the type of payment being subjected to TDS. Any system that stores or validates these codes needs a mapping table before April 1, 2026.
The Income Tax India e-filing portal is the authoritative source for the final enacted text once the Bill receives Presidential assent.
Complete TDS Section Mapping Table
The following table shows how major TDS sections from the 1961 Act map to their equivalents in the new act. This mapping is based on the Income Tax Bill 2025 as introduced. Confirm against the enacted text before implementation.
| Old Section (Act 1961) | Payment Type | New Section (Act 2025) | Rate (unchanged) |
|---|---|---|---|
| Section 192 | Salary payments | Section 401 | Per slab |
| Section 194A | Interest (non-bank) | Section 393(1)(c) | 10% |
| Section 194C | Contractor / sub-contractor | Section 393(1)(a) | 1% (individual), 2% (company) |
| Section 194D | Insurance commission | Section 393(1)(d) area | 5% |
| Section 194H | Commission and brokerage | Section 393(1)(f) | 5% |
| Section 194I | Rent (land / building) | Section 393(1)(e) | 10% |
| Section 194I | Rent (plant / machinery) | Section 393(1)(e) area | 2% |
| Section 194J | Professional / technical fees | Section 393(1)(b) | 10% (professional), 2% (technical) |
| Section 194N | Cash withdrawal | Section 393(1)(j) area | 2% / 5% |
| Section 194Q | Purchase of goods | Section 393(1)(k) | 0.1% |
| Section 195 | Non-resident payments | Section 413 | Treaty rate / 20–40% |
| Section 206C | TCS (specified goods) | Section 393(2) area | 0.1% on eligible turnover |
Sections 206AB and 206CCA (higher TDS/TCS for non-filers) map into the same Chapter XX framework. The specific sub-clause references for lower-frequency sections should be confirmed against the enrolled Bill text.
What This Means for Your TDS Challans from April 1
Every TDS challan (ITNS 281) deposited from April 1, 2026 onwards must carry the new section code for the type of payment being covered. A challan deposited for contractor TDS deducted in April 2026 must reference Section 393(1)(a), not Section 194C.
The TRACES portal is updating its challan validation system to accept new section codes from April 1, 2026. OLTAS (Online Tax Accounting System) will be updated in tandem.
For your finance operations, the implication is direct: the section code dropdown or text field in your TDS challan payment interface — whether through the bank’s online portal, your ERP’s payment module, or a direct NEFT to the income tax account — must present and accept the new codes. If your ERP auto-populates the challan section code from a master table, that master table needs to be updated before the first April payroll cycle or contractor payment run.
A challan with an old section code (194C) deposited for an April 2026 deduction may be accepted by the bank but will create a mismatch when the return is filed for Q1 FY 2026-27.
What This Means for TDS Certificates (Form 16/16A)
Form 16 (salary TDS) and Form 16A (non-salary TDS) generated for deductions made from April 1, 2026 onwards must show the new section codes. A Form 16A issued for a professional fee payment made in May 2026 should reference Section 393(1)(b), not Section 194J.
The certificate generation workflow on TRACES pulls section codes from the underlying quarterly return data. If the return is filed with the correct new section codes, the certificates generated from it will automatically reflect those codes. The critical dependency is the return filing — get that right and certificates follow.
Deductees receiving Form 16A for deductions made after April 1, 2026 should expect to see unfamiliar section references. Finance teams at companies that receive large volumes of Form 16A (IT services firms, consultants, agencies) should brief their TDS receivable teams on the new codes before April to avoid reconciliation confusion when certificates arrive.
What This Means for Quarterly TDS Returns (24Q/26Q/27Q)
Q1 FY 2026-27 returns (April–June 2026, deadline July 31, 2026) will be the first returns filed entirely under the new section numbering. The return file format (FVU validated) is expected to be updated to validate against the new code set.
The most immediate operational question is whether your return preparation software — Saral TDS, ClearTDS, or the ERP TDS module — will be updated before April. Most major software vendors are expected to release updates in March 2026. If your software uses a manually maintained section code master, that update is your responsibility.
For organisations with centralised TDS teams handling returns for multiple legal entities or group companies, this is a bulk update task: every entity’s section code master must be updated before the April payroll run.
How to Update Your Reconciliation Records
Reconciliation systems that match ledger TDS entries to Form 26AS data using section codes as a match key need a dual-code lookup table from April 1, 2026. The practical update steps are:
Step 1 — Map your transaction types. List every TDS section code currently active in your ERP or accounting system. For each, identify the corresponding new section code using the mapping table above.
Step 2 — Update your master data. Add new section codes to your payment type master, TDS section master, and any TRACES integration configuration. Do not delete old codes — historical transactions reference them.
Step 3 — Configure your reconciliation rules. If your reconciliation system matches Form 26AS section codes to ledger entries, add a mapping rule so that Section 393(1)(a) in Form 26AS is treated as equivalent to 194C in the ledger for any cross-year reconciliation involving deductions up to March 31, 2026 versus credits appearing in 26AS after April 1, 2026.
Step 4 — Test before April 1. Run a parallel test using a sample April-dated transaction through the full cycle: ledger entry with new section code, challan deposit with new code, and return preparation. Identify gaps before they affect live transactions.
TDS reconciliation software that maintains a configurable section code mapping layer can handle this transition without requiring changes to every individual transaction rule. Reconciliation software India built for Indian compliance typically includes provision for regulatory code changes of this type.
Three Cross-Year Reconciliation Problems to Watch For
Problem 1: March 2026 deductions credited in April 2026. A contractor payment made in March 2026 (deducted under 194C) may be credited to Form 26AS in April 2026 after the deductor files the Q4 FY 2025-26 return. Your reconciliation system may try to match this against an expected credit with Section 393(1)(a). The reconciliation logic needs to treat both codes as equivalent for this scenario.
Problem 2: April 2026 corrections for FY 2025-26 deductions. If you discover an error in a Q3 or Q4 FY 2025-26 TDS entry after April 1, the correction statement for that period still uses old section codes (the return was filed under the 1961 Act). Your team needs to know that correction statements for periods up to March 31, 2026 use old codes even if filed after the transition date.
Problem 3: Vendor certificates with mixed codes. Large vendors who receive payment from multiple clients may send you Form 16A certificates covering deductions from both sides of the April 1 transition date. A single certificate consolidating Q4 FY 2025-26 and Q1 FY 2026-27 deductions could show both old and new section codes. Your TDS receivable reconciliation must handle both.