Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
From April 1, 2026, TDS and TCS section codes (194C, 194J, 194H, and so on) are replaced by numeric payment codes 1001 to 1092 under parent sections 392 (salary), 393 (non-salary TDS), and 394 (TCS). Vendor masters, GL codes, and reconciliation configurations must map legacy codes to new payment codes before go-live.
Extract every section code active in the ERP, vendor master, and return preparation tool. Map each legacy section to its Income Tax Act 2025 parent section and indicative payment code. Treat paired codes as equivalent for cross-era matching during the transition.
Dual-mode reconciliation supports legacy, payment_code, and dual runs. CBDT publishes the final payment code mapping before go-live, and the final list must be confirmed against the CBDT notification before locking production.
Vendor master annotated with payment code, migration-ready reconciliation configuration, and end-to-end April 2026 test results covering ledger entry, challan deposit, return preparation, and certificate download under the new code.
Finance teams that have spent two decades reading Form 26AS as a list of Section 194C, 194J, 194I, and 195 entries will open the new Form 168 in April 2026 and see columns of four-digit payment codes instead: 1001, 1002, 1005, 1014, 1062. The Income Tax Act 2025 replaces the legacy section-based taxonomy with a numeric payment code system in the 1001–1092 range, organised under three parent sections. This guide explains the structure, the mapping to old sections, and what it changes in your TDS reconciliation records.
The renumbering affects every system that stores a section reference: your ERP payment master, your TDS reconciliation tool, the challan interface on your bank’s portal, and the classification logic in any Form 26AS matching process you run against your receivable ledger.
What the TDS Payment Code Taxonomy Looks Like
The payment code system groups every TDS and TCS trigger into one of three parent sections. Section 392 covers salary TDS, which was previously Section 192 of the 1961 Act. Section 393 covers all non-salary TDS, including contractor payments, professional fees, rent, interest, commission, and specified purchases. Section 394 covers Tax Collected at Source on goods like scrap, alcohol, motor vehicles, and the LRS/overseas tour bucket.
Under each parent section, payment codes in the 1001 to 1092 range identify the specific payment nature. The 1001 series roughly aligns with contractor-style payments, 1002 with professional and technical services, the 1005–1008 range with rent and interest, and the 1060+ range with TCS categories. The CBDT is expected to publish the definitive list of payment codes with the final notification; indicative groupings based on the Income Tax Bill 2025 are shown in the reference table below. Treat the table as a mapping framework, and confirm each exact code against the enrolled Bill text before you hard-code it into your ERP.
The practical effect is that the “section” column in every TDS system becomes a “payment code” column. The challan section dropdown becomes a payment code dropdown. The Form 26AS section reference becomes a Form 168 payment code column. The Form 16A section block becomes the Form 131 payment code block.
Why the Change Creates Reconciliation Risk
The taxonomy shift is not a cosmetic rename. It creates three operational problems that show up directly in month-end reconciliation runs.
Risk 1. Master data drift between ERP and TRACES
Your ERP stores a section code against every vendor. If the vendor master still says “194J” on April 5, 2026 while the TRACES return requires the new payment code for professional fees, the return preparation step breaks. This is not a file-format error that throws a clean exception. It is a classification mismatch that either fails validation or, worse, passes validation under the wrong code and shows up as a mismatch in the vendor’s Form 131 download.
Risk 2. Cross-era data in one quarter
In Q1 FY 2026-27, the TDS receivable ledger will carry credits that originated before April 1 (carried over from Q4 FY 2025-26 TRACES filings with old section codes) alongside credits that originated after April 1 (with new payment codes). A reconciliation system that matches Form 26AS entries to ledger entries using the section code as a join key will produce false mismatches unless it treats old sections and new payment codes as equivalents.
Risk 3. Challan misclassification in April’s first week
The April 7 challan deposit deadline for March TDS deductions lands in the first week of the new era. A challan deposited on April 7, 2026 for a March 28 contractor payment still uses the legacy 194C reference, because the deduction predates the new Act. A challan for an April 3 payment uses the new payment code. Finance operations that batch these together in a single bank payment run risk mixing codes on one payment instrument, which creates OLTAS matching problems later.
How to Build Your Payment Code Mapping
Step 1. Extract your live section code list
Run a report on your current TDS configuration: every section code in use across the vendor master, the chart of accounts, the payment type master, and the TDS return preparation tool. Typical Indian finance teams find between 8 and 15 active section codes. The common ones are 194C, 194J, 194I, 194A, 194H, 194Q, 195, 192, 206C, and section-specific variants for lower-deduction certificates under 197. List them with the current volume of transactions per section per quarter.
Step 2. Map each to its parent section and payment code
For each legacy section, identify the Income Tax Act 2025 parent (392, 393, or 394) and the indicative payment code. Salary TDS under 192 moves to Section 392. Non-salary TDS, which is the bulk of most organisations’ volume, consolidates under Section 393 with payment codes in the 1001–1014 range for common categories and extending into the 1060+ range for specialised payments. TCS under 206C series moves to Section 394. The reference table below shows the indicative mapping.
Step 3. Add the mapping to your reconciliation configuration
A reconciliation engine that classifies by section code needs a configuration layer that recognises both the legacy code and the new payment code as referring to the same transaction type. TransactIG’s platform supports this through a dual-mode configuration flag (legacy, payment_code, or dual), so that a single reconciliation run can handle transactions deducted before April 1 (legacy) and after (payment code) without requiring two separate jobs. Finance teams running on spreadsheets or in-house macros will need to build the equivalent lookup manually.
Step 4. Test the Q1 FY 2026-27 cycle end to end
Before your first April 2026 challan deposit, run a test transaction through the full cycle: vendor invoice, ledger entry with payment code, challan deposit, return preparation, and certificate download. Do this in a sandbox or against a test deductee PAN if the bank’s payment portal supports it. The goal is to catch a code mismatch before it becomes a live filing rather than after.
Indicative TDS Payment Code Reference Table
The following is an indicative mapping based on the Income Tax Bill 2025 as introduced. The CBDT is expected to publish the final notified list with the enrolled Act. Confirm each code before production use.
| Old Section (1961 Act) | Payment Nature | Parent Section (2025 Act) | Indicative Payment Code | Rate (Expected) |
|---|---|---|---|---|
| 192 | Salary TDS | 392 | 1001 | Per slab |
| 194A | Interest (non-bank) | 393 | 1005 | 10% |
| 194C | Contractor / sub-contractor | 393 | 1002 | 1% / 2% |
| 194D | Insurance commission | 393 | 1006 | 5% |
| 194H | Commission / brokerage | 393 | 1007 | 5% |
| 194I(a) | Rent, plant and machinery | 393 | 1008 | 2% |
| 194I(b) | Rent, land and building | 393 | 1009 | 10% |
| 194J | Professional and technical fees | 393 | 1003 | 10% / 2% |
| 194N | Cash withdrawal | 393 | 1011 | 2% / 5% |
| 194Q | Purchase of goods | 393 | 1012 | 0.1% |
| 194R | Benefit or perquisite | 393 | 1013 | 10% |
| 194S | Virtual digital assets | 393 | 1014 | 1% |
| 194T | Partner remuneration | 393 | 1015 | 10% |
| 195 | Non-resident payments | 393 | 1062 | Treaty / 20 to 40% |
| 206C(1) | TCS, scrap, alcohol, timber | 394 | 1071 | 1% |
| 206C(1H) | TCS, sale of goods above ₹50L | 394 | 1073 | 0.1% |
The exact numbers in the “Indicative Payment Code” column are illustrative groupings and must be confirmed against the CBDT notification before you load them into a production master. What will not change is the bucket structure: contractor-style payments stay together, professional fees stay together, rent stays together, and TCS sits under a separate parent.
India-Specific Compliance Implications
Three Indian compliance touchpoints are immediately affected by the payment code taxonomy.
The new Form 168 (replacing Form 26AS). Every deductee’s annual tax statement will list credits by payment code rather than by section. A salaried individual’s Form 168 will show payment code 1001 under Section 392 for salary TDS. A consulting firm’s Form 168 will show payment code 1003 under Section 393 for professional fees. Any internal reconciliation process that reads Form 26AS today must be rewritten to read Form 168 tomorrow, with payment code rather than section as the primary join key.
Form 131 (replacing Form 16A). The annual TDS certificate format changes. The block that currently shows “Section 194J” will instead show “Payment Code 1003 under Section 393”. Indian IT services firms, consultants, and agencies who track Form 16A receipts across clients will receive Form 131s with the new format from FY 2026-27 onwards. Cross-client aggregation of certificates requires mapping from the new code back to the vendor-specific category in the internal master.
Form 141 (replacing 26QB, 26QC, 26QD, 26QE). The consolidated challan-cum-statement for property purchase TDS, rent TDS by individuals, contractor TDS by individuals, and virtual digital asset TDS merges into a single form. Payment code drives the classification within Form 141, not separate form numbers.
The Income Tax India e-filing portal will publish the final notified payment code list. Treat it as the definitive reference, not any third-party summary, including this article.
What Automated TDS Reconciliation Changes
A reconciliation engine that was built on section codes needs a configuration change, not a rewrite, to handle the payment code taxonomy. The critical capability is cross-era matching: the ability to treat legacy 194C and new payment code 1002 as the same transaction type within a single reconciliation run, so that Q1 FY 2026-27 reconciliation can match March deductions (legacy codes) to credits appearing in Form 168 (new codes).
TransactIG supports this through three configuration modes. In legacy mode, the engine treats everything under the 1961 Act’s section codes, used for closing FY 2025-26 and for correction statements covering earlier years. In payment_code mode, the engine runs pure Income Tax Act 2025 classification, used from Q2 FY 2026-27 onwards once the transition quarter is closed. In dual mode, both taxonomies are active simultaneously with a mapping layer treating old and new codes as equivalent. Most finance teams will operate in dual mode through FY 2026-27.
This is the practical benefit of purpose-built TDS reconciliation software over spreadsheet-based processes: the code taxonomy shift becomes a configuration setting rather than a quarter of manual remapping. For broader changes across bank, NACH, and GST workflows, reconciliation software India built for Indian compliance absorbs regulatory shifts of this type without breaking the downstream matching logic.
Match rates at Indian enterprises moving from manual spreadsheets to structured TDS matching typically climb from a 51% baseline to around 88% once section and payment code masters are correctly mapped.