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.
Key Dates at a Glance
| Date | Event | Reconciliation impact |
|---|---|---|
| March 31, 2026 | Last day of FY 2025-26 under the Income Tax Act 1961 | All deductions up to this date carry old section codes |
| April 1, 2026 | Income Tax Act 2025 takes effect; FY 2026-27 begins | All new deductions carry Section 393 sub-clause codes |
| May 31, 2026 | Q4 FY 2025-26 TDS return deadline (Form 26Q / 27Q) | Filed under old codes even though after April 1 |
| July 31, 2026 | Q1 FY 2026-27 TDS return deadline | First return filed entirely under Section 393 |
| June 15 to July 31, 2026 | TRACES Form 26AS will reflect Q1 deposits | First Form 26AS pulls showing Section 393 sub-clauses |
| October 31, 2026 | Q2 FY 2026-27 TDS return deadline | Mid-year reconciliation should be running cleanly under new codes |
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.
Worked Examples: How Section 393 Looks in Practice
The abstract description of dual-code reconciliation becomes concrete when applied to specific transactions. Each of these scenarios is drawn from how the deduction-date routing logic actually plays out at the year boundary.
Example 1: Professional services contract straddling the transition
An IT consulting firm bills a client ₹10,00,000 for a project completed in February 2026 and a separate ₹15,00,000 for work delivered in May 2026. Both invoices are subject to TDS under what was Section 194J (now Section 393(1)(b)) at 10%.
The February invoice TDS of ₹1,00,000 is deducted under the 1961 Act and carries section code 194J wherever it appears — challan, quarterly return, Form 26AS, Form 16A. The May invoice TDS of ₹1,50,000 is deducted under the 2025 Act and carries section code 393(1)(b). The total TDS receivable for FY 2026-27 in the consulting firm’s books would aggregate both ₹1,00,000 (if it falls in 26AS for FY 2026-27 due to a late-deposit by the deductor) and ₹1,50,000 — but under different section codes for the same payment type. A reconciliation system that filters strictly by 393(1)(b) would miss the ₹1,00,000 entry.
Example 2: Rent paid across the year boundary
A manufacturing company pays monthly factory rent of ₹3,00,000 to its landlord. TDS at 10% under what was Section 194I (now Section 393(1)(e)) applies. For March 2026 rent paid on March 31, 2026, the ₹30,000 TDS is deducted under the 1961 Act. For April 2026 rent paid on April 30, 2026, the ₹30,000 TDS is deducted under the 2025 Act.
The landlord’s Form 26AS for FY 2026-27 will show both entries — but the March deduction (deposited and reported in Q4 FY 2025-26 return) appears with code 194I, and the April deduction (in Q1 FY 2026-27 return) appears with code 393(1)(e). Both relate to the same rent contract, the same TAN-PAN counterparty, the same monthly cash flow — only the section identifier differs.
Example 3: Marketplace TDS under Section 194O / 393(1)(j)
An e-commerce seller’s TDS reconciliation under Section 194O (which becomes a sub-clause of Section 393) is operationally complex even before the transition. A platform like Amazon or Flipkart deducts Section 194O TDS at 1% on the gross order value (including GST) and deposits it monthly. For sales settled in March 2026, the TDS is deducted under 194O. For sales settled in April 2026, the same operator deducts under the new Section 393 sub-clause.
For sellers reconciling their Form 26AS Part A-I against their settlement files, this means the same operator-PAN combination will produce credits under two different section codes within the same Form 26AS pull for FY 2026-27. The matching engine must aggregate by operator PAN regardless of section code, not split into separate buckets.
Industry Impact: Where Section 393 Hits Hardest
Different sectors carry different TDS code mixes, which makes the Section 393 transition harder for some industries than others.
IT services and consulting firms. The highest-impact category. Most revenue is subject to Section 194J TDS at 10% (becoming 393(1)(b)), with a meaningful slice under 194C for project deliverables (becoming 393(1)(a)). Annual TDS receivable balances for a mid-size IT firm typically run from ₹50 lakh to several crore. The reconciliation framework needs both code sets active and a cross-year matching mode to clear FY 2025-26 accruals against FY 2026-27 deposits. See the cluster of TDS receivable reconciliation insights for industry-specific patterns.
Manufacturing and engineering. A mix of 194C (contractors and sub-contractors), 194J (technical consultancy, design fees), 194I (rent of premises and plant), 194Q (purchase of goods over ₹50 lakh from a single vendor), and 194H (commission to dealers and agents). Five active section codes pre-transition, all five mapping to different Section 393 sub-clauses post-transition. The mapping master is heavier here than for almost any other sector.
NBFC and lending. Section 194A (interest, becoming 393(1)(c)) dominates the inbound TDS receivable, with smaller amounts under 194J for advisory fees. Outbound TDS deductions on borrower-side payments are also material. Both directions need the dual-code framework.
Real estate and infrastructure. Section 194I (rent) and Section 194IA (purchase of immovable property over ₹50 lakh) are core. Lessors with portfolios of 20–100 properties experience the most concentrated transition workload because every monthly rent receivable across every tenant carries the same code change.
Hospitality and hotels. Section 194I rent on franchise properties, Section 194H commission to OTAs (Booking.com, MakeMyTrip), and Section 194C contractor payments to F&B outsourcing partners are all in scope. The OTA settlement reconciliation already covered in the hospitality cluster will see the section code change reflected in Q1 FY 2026-27 settlements onward.
E-commerce and platform sellers. Section 194O is the headline section. Platform-deducted TDS is the largest category, often forming 70%+ of inbound TDS receivable for marketplace-only sellers. The transition’s reconciliation complexity scales with platform count — sellers on three or more platforms (Amazon, Flipkart, Meesho) will see the code change appear at slightly different cadences depending on each platform’s internal system rollout.
Migration Timeline: A Month-by-Month Checklist
The Section 393 transition is best treated as a 6-month project starting January 2026 and ending around September 2026 with the first clean post-transition quarter behind you.
January–February 2026: Plan and prepare. Inventory current section code usage in the TDS receivable ledger (which sections produce material balances). Confirm with ERP and reconciliation tool vendors whether Section 393 mapping is supported and on what timeline. Update the section code master with both old and new codes, marked with effective dates. Brief the finance team on the change.
March 2026: Validate the mapping. Run a parallel reconciliation in test or staging that uses the new code mapping logic against a copy of FY 2025-26 production data. Confirm matches still close. Brief deductee-side counterparties (large customers, key tenants) about the upcoming change so their AR teams know what to expect from your TDS certificates.
April 1, 2026: Cutover day. ERP and reconciliation systems start deducting under Section 393 sub-clauses for new transactions. The section code master flag must apply correctly: all transactions dated on or after April 1 use new codes, prior transactions use old codes. Run a smoke test with a single deduction to confirm challan, return preparation, and Form 16A reflect the new code.
April–May 2026: Q4 FY 2025-26 close. File Q4 FY 2025-26 returns (deadline May 31) under old section codes. This is the last return cycle on the 1961 Act. Verify Form 16A certificates for the year are generated with old codes. Pull a final Form 26AS for FY 2025-26 closing.
June–July 2026: First post-transition quarter. Q1 FY 2026-27 deductions accumulate under Section 393. File the first Q1 return (deadline July 31) using new codes. Pull the first FY 2026-27 Form 26AS to verify TRACES is reflecting new codes correctly. Run reconciliation for any cross-year cases (Q4 FY 2025-26 deposits trickling into FY 2026-27 26AS).
August–September 2026: Stabilisation. Q2 FY 2026-27 reconciliation should be fully clean under the new framework. Use this period to retire any temporary scripts or manual workarounds put in place during cutover. Document the final mapping table for audit purposes.
For the comprehensive day-by-day checklist see the TDS 2026 migration checklist. The cross-era handling for transactions that straddle the boundary is covered separately in the cross-era TDS reconciliation guide.
Common Reconciliation Errors at the Section 393 Transition
Five recurring failure modes show up when the cutover is not handled cleanly. Each is preventable.
Error 1: Single-code reconciliation runs. A reconciliation system that filters Form 26AS strictly by 393(1)(b) will miss any FY 2025-26 deposits that arrive late and still carry 194J. Symptoms: aggregate TDS receivable shows a gap that grows in May and June 2026 as Q4 FY 2025-26 deposits trickle in. Fix: run with both codes accepted as equivalent for the same payment type.
Error 2: Hard-coded rate validation against old codes. Many in-house reconciliation rules check that Section 194J TDS is exactly 10% of the gross. After April 1, the rule must accept either 194J or 393(1)(b) as triggering the same 10% check. A rule with a hard-coded section string fails silently — it accepts incorrect rates as valid because the new code does not match the rule’s filter.
Error 3: Mixed-code Form 26AS pulls. Pulling a single combined Form 26AS file for FY 2025-26 and FY 2026-27 mixes old and new codes in one dataset. Reconciliation engines that route on code rather than on date can mis-classify transactions. Fix: pull each financial year separately and tag rows with the correct year before merging.
Error 4: ERP not updated for outbound deductions. If your organisation also deducts TDS on payments out (vendor TDS), the ERP must apply Section 393 codes from April 1 onwards. An ERP still configured for old codes will produce challans and returns with 194C / 194J — incorrect for post-April transactions, and may cause TRACES match failures in the deductor’s own quarterly return.
Error 5: Treating the change as a search-and-replace. Some teams attempt to “rename” old section codes to new ones in historical data — replacing 194J with 393(1)(b) across the board. This breaks the audit trail and creates inconsistency with Form 26AS for FY 2025-26 (which keeps the old codes). The correct posture is to add new codes alongside old ones and let the deduction date decide which applies, never to overwrite history.
Updated Reconciliation Workflow Under Section 393
Beyond the cutover mechanics, the steady-state reconciliation workflow under Section 393 looks slightly different from the 1961 Act version:
Filter by sub-clause first, by amount second. With multiple sub-clauses living under one section number, the first reconciliation filter is no longer “Section 194X” — it is “Section 393, sub-clause X”. The matching engine’s section column must store the full sub-clause identifier, not just the parent section.
Maintain payment code as a parallel key. As discussed above, the four-digit payment code (1001–1092 range) is a parallel identifier alongside the sub-clause. Some downstream systems surface payment code rather than sub-clause. The matching layer should accept either as a valid section reference.
Run rate validation against the sub-clause table. Each sub-clause has its own rate — 393(1)(a) at 1%/2%, 393(1)(b) at 10%/2%, 393(1)(e) at 10%/2%, etc. The rate validation table must be keyed on sub-clause + deductee category, not on a flat section number.
Carry the section code through to GL postings. When posting matched TDS receivable journal entries to the general ledger, retain the sub-clause in a metadata field so the audit trail back to Form 26AS is preserved. This is critical for ICFR / SOX / statutory audit walkthroughs that examine TDS reconciliation evidence.
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.
How much working capital is your TDS gap actually costing?
The TDS Mismatch Estimator runs entirely in your browser. Adjust four inputs — annual TDS, deductee count, gap %, resolution lag — to see the rupee exposure, interest cost, and analyst hours your 26AS gap is consuming.
Run the TDS Mismatch Estimator →