Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Section 393 of the Income Tax Act 2025 consolidates 194C, 194J, 194H, 194I, 194A, and 194Q into sub-clauses of a single section from April 1, 2026. TDS receivable ledgers that only store legacy codes will show false gaps against Form 26AS entries carrying 393(1)(a), 393(1)(b), 393(1)(f), 393(1)(e), 393(1)(c), and 393(1)(k) identifiers.
Store both code sets side by side at the ledger level, linked through a section mapping master. Match each TDS receivable entry to Form 26AS using the code that applies on its deduction date, not a single fixed code per vendor. Ignore bank narration for section identification — it lags legislative changes — and rely on TRACES return data as the authoritative source.
Section mapping master with sub-clause metadata. Ledger field that holds both legacy section and 2025 Act sub-clause. Cross-era matching mode with transaction-date routing.
TDS receivable ledgers that reconcile cleanly against Form 26AS across the FY 2025-26 to FY 2026-27 transition, correct aggregate credits for IT and services companies receiving TDS under multiple sub-clauses, and an audit trail traceable to the section code active on each deduction date.
Section 393 of the Income Tax Act 2025 is not a minor renaming exercise. It is a structural consolidation that merges what were previously independent TDS sections — each with their own section number, separate line in Form 26AS, and distinct challan classification — into a single section with sub-clauses. For reconciliation teams, this creates a transition challenge that spans at least two financial years: FY 2025-26 (where old codes remain in effect) and FY 2026-27 (where Section 393 sub-clauses take over), with cross-year reconciliation cases that involve both simultaneously.
The Income Tax India e-filing portal is the authoritative source for the final enacted text of the Income Tax Act 2025.
What Is Section 393 of the New Income Tax Act 2025
Chapter XX of the Income Tax Act 2025 consolidates all Tax Deducted at Source provisions that were previously distributed across Sections 192 through 206CE of the Income Tax Act 1961. Section 393 is the core TDS provision within Chapter XX — it covers TDS on payments to residents across a broad range of payment types, each addressed through sub-clauses.
The sub-clause structure is how Section 393 replaces multiple independent sections. Section 393(1)(a) covers contractor payments (previously 194C). Section 393(1)(b) covers professional and technical services fees (previously 194J). Section 393(1)(c) covers interest payments (previously 194A). Section 393(1)(e) covers rent (previously 194I). Section 393(1)(f) covers commission and brokerage (previously 194H).
This consolidation means that on Form 26AS, TDS certificates, and TRACES reconciliation reports, the section code field will show “393(1)(a)” instead of “194C” for contractor TDS from April 1, 2026. The underlying economic transaction, rate, and threshold are unchanged. The identifier that systems use to classify and match the transaction changes.
For Indian IT and services companies that receive significant TDS under 194J — often ₹50 lakh to several crore per year — this reclassification affects every element of the TDS receivable tracking process.
Old TDS Sections Consolidated Under Section 393
The following table shows the consolidation structure relevant to most Indian enterprises:
| New Section | Sub-clause | Old Section | Payment Type | Key Rate |
|---|---|---|---|---|
| Section 393 | (1)(a) | 194C | Contractor payments | 1% / 2% |
| Section 393 | (1)(b) | 194J | Professional / technical fees | 10% / 2% |
| Section 393 | (1)(c) | 194A | Interest (non-bank) | 10% |
| Section 393 | (1)(d) area | 194D | Insurance commission | 5% |
| Section 393 | (1)(e) | 194I | Rent (land / building / plant) | 10% / 2% |
| Section 393 | (1)(f) | 194H | Commission and brokerage | 5% |
| Section 393 | (1)(k) | 194Q | Purchase of goods | 0.1% |
| Section 393 | (2) area | 206C | TCS on specified goods | Rate varies |
Section 195 (non-resident payments) maps separately to Section 413 rather than Section 393, reflecting its distinct treaty-based rate structure.
Related Payment Code Guidance
Section 393 sub-clauses are only one half of the new identifier system. From April 1, 2026, every non-salary TDS transaction also carries a four-digit payment code in the 1001–1092 range. Section 393(1)(a) contractor payments carry payment code 1094, Section 393(1)(b) professional fees carry a distinct code, and so on across the sub-clause set. Challan deposits, Form 141 submissions, and Form 168 statements all reference both the section sub-clause and the numeric payment code.
For reconciliation teams, this means the section code master needs two columns going forward: the Chapter XX sub-clause (393(1)(a)) and the corresponding payment code (1094). Matching logic should accept either identifier as a valid key, because different downstream systems surface different fields. The payment codes 1001–1092 reference lists the complete mapping, and the cross-era TDS reconciliation guide explains how a dual-mode configuration (legacy, payment_code, or dual) handles the overlap between FY 2025-26 entries (old section codes) and FY 2026-27 entries (sub-clauses plus payment codes). Finance teams preparing for the switchover should also work through the TDS 2026 migration checklist to confirm ERP, TRACES, and ledger updates are sequenced correctly.
How Reconciliation Logic Changes Under Section 393
Before April 1, 2026, a typical TDS receivable reconciliation run works like this: download Form 26AS, filter by financial year and section code (194J for professional fee TDS), match each entry to the corresponding ledger credit, flag unmatched items. Section codes are a reliable first-level filter because each payment type has a unique section number.
After April 1, 2026, the same reconciliation for FY 2026-27 transactions must filter for Section 393(1)(b). For an organisation that receives TDS under both contractor and professional service categories, the reconciliation must handle 393(1)(a) and 393(1)(b) as distinct categories — not interchangeable, because they carry different rates and have different rate-check logic.
The complication arises at the year boundary. Consider an organisation reconciling its TDS receivable for FY 2026-27. The majority of its credits will show Section 393(1)(b). However, late-deposited TDS from Q4 FY 2025-26 (where the deductor delayed deposit) may still trickle into Form 26AS after April 1 — but those credits will show Section 194J, because the deduction was made before the transition date. The reconciliation system must recognise both codes as valid representations of the same underlying payment type.
TDS reconciliation software built to accommodate configurable section code mapping handles this transition without manual intervention on each transaction. The mapping table updates at the system level, and matching logic applies the correct equivalence rules based on the deduction date.
The Cross-Year Problem: FY 2025-26 Deductions vs FY 2026-27 Claims
The most operationally complex scenario involves a deduction made in February or March 2026 (under old Section 194C or 194J) that is deposited by the deductor in April or May 2026 (after the Act transition date). The deposit uses old section codes because the underlying deduction predates April 1. The credit appears in Form 26AS in FY 2026-27 with old section codes. Your FY 2026-27 reconciliation system, configured for Section 393 sub-clauses, may not recognise or classify this correctly.
This is a predictable structural issue that affects every organisation with substantial TDS receivable. The practical resolution steps are:
Flag year-boundary transactions. Any deduction made between January 1 and March 31, 2026 for which Form 26AS credit is expected after April 1, 2026 should be flagged in your TDS receivable ledger as a “cross-year transition case.” These entries need manual or rule-based handling until the credit appears in 26AS.
Maintain parallel code sets. Your reconciliation system’s section code master should include both the old code (194C) and the new code (393(1)(a)) for the same payment type, with a flag indicating which applies based on the deduction date. Matching rules should accept either code as valid for the same underlying payment category.
Run a Q4 FY 2025-26 holdover report. After the Q4 FY 2025-26 return is filed (deadline May 31, 2026), identify all deductees for whom Q4 TDS was reported. Track when those credits appear in Form 26AS. Any credit appearing after April 1, 2026 will carry old section codes even though it arrives in your FY 2026-27 reconciliation cycle.
Updating Your Reconciliation System for Section 393
The reconciliation system update for Section 393 has three components:
Section code master update. Add all Section 393 sub-clauses to your payment type master and TDS section reference table. Map each new code to its equivalent old code. Set the effective date (April 1, 2026) so the system knows which code applies based on deduction date, not filing date.
TRACES integration update. If your reconciliation system downloads Form 26AS data via the TRACES API or bulk download, confirm whether the data format changes post-April 1 for the section code field. The field name may remain the same while the values change. Test with a sample download after April 1 before running a full reconciliation cycle.
Rate validation logic. If your reconciliation system validates that the TDS amount in Form 26AS matches the expected rate applied to the gross payment (e.g., 10% of the invoice amount for Section 194J), update the rate validation rules to reference the correct new section code. Section 393(1)(b) at 10% is the same rate as 194J at 10% — the validation logic must map correctly.
Reconciliation software India that is configured for Indian compliance typically supports configurable code tables. The update is a configuration change, not a code change, if the system was built with this type of regulatory flexibility in mind.
Section 393 and TRACES: What Changes on the Portal
TRACES is updating its portal interface to support Section 393 sub-clause codes in all relevant workflows. Key areas of change:
Quarterly return filing (Form 26Q / 24Q). The FVU (File Validation Utility) will be updated to accept Section 393 codes for Q1 FY 2026-27 returns (filed by July 31, 2026). Ensure your return preparation software is using a post-April 2026 version of the FVU before preparing Q1 returns.
Form 16A certificate generation. TRACES generates Form 16A certificates from the underlying quarterly return data. Returns filed with Section 393 codes will produce certificates showing those codes. This is the correct behaviour — deductees should expect certificates with 393(1)(a) or 393(1)(b) for deductions made after April 1, 2026.
Challan-to-return matching. TRACES’s internal matching of challan deposits to quarterly returns is performed using section codes as one of the matching parameters. Challan deposits for April 2026 transactions should use Section 393 codes to ensure the TRACES internal match works correctly. A challan with a Section 194C code deposited for an April 2026 deduction may not match cleanly in the TRACES system once the portal updates to the new code set.
Historical return access. TRACES will maintain read access to returns filed under the old Act (FY 2025-26 and earlier). Downloading Form 26AS for FY 2025-26 after April 1, 2026 will still show old section codes for that year’s entries. This backward compatibility is essential for multi-year TDS reconciliation and audit support.
The transition to Section 393 is a one-time effort with ongoing implications. Organisations that invest in a clean mapping table, a dual-code reconciliation configuration, and a clear year-boundary handling procedure before April 1 will find the transition straightforward. Organisations that treat it as a minor administrative update — a simple code rename — will face systematic reconciliation exceptions throughout Q1 FY 2026-27.