TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025

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.

Last updated: 8 May 2026 — codes verified against the most recent CBDT releases. The 2025 Act has been live for over a month; mappings reflect the post-cutover state of FY 2026-27.

Post-Cutover Reality: What Q1 FY 2026-27 Actually Looks Like

The Income Tax Act 2025 has been live for over a month. April challan deposits are in OLTAS under payment codes, the Q4 FY 2025-26 return cycle is closing under legacy section codes (deadline May 31, 2026), and the first Q1 FY 2026-27 return is due by July 31. Finance teams who tested the cutover in March are running cleanly. Teams that did not test are surfacing exceptions in three predictable places:

• April 7 challan batch. The first OLTAS deposit window after the cutover. Organisations that ran a single bank-payment file mixing March deductions (legacy codes) and early-April deductions (payment codes) saw the bank reject the file or post the entries against the wrong section identifier. Where this happened, a challan correction filing is the cleanest fix.
• Q4 FY 2025-26 return preparation in May. Teams that updated their return preparation FVU to the new version are finding the FVU rejects entries with payment codes (because Q4 FY 2025-26 is a 1961 Act period). The fix is to keep the legacy FVU active for Q4 returns and switch to the new FVU for the Q1 FY 2026-27 cycle starting July.
• Vendor master flag for 206AB / 206CCA. Sections 206AB and 206CCA (higher TDS for non-filers) are abolished under the 2025 Act. ERP-level scripts that automatically apply the doubled rate based on the non-filer flag should have been disabled on April 1. Teams that missed this are still applying the higher rate in error and will need to issue refund-of-excess-TDS adjustments to vendors.

If your team is one month into the new system and reconciliation looks stable, you are in the cohort that prepared correctly. If you are still chasing exceptions, the migration timeline below is a corrective rather than preventative checklist — the same steps still apply, just compressed.

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.

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.

Decoding a Form 168 Entry: Worked Example

A typical Form 168 line for an IT services firm in Q1 FY 2026-27 looks like this:

Reading this row: ABC Tech Ltd deducted ₹2,50,000 of TDS on April 15, 2026 against a professional services invoice. The payment code 1003 under Section 393 corresponds to what was previously Section 194J. The 10% rate implies a gross invoice value of ₹25,00,000. The credit is “booked” — meaning the deductor’s quarterly return has been filed and processed by TRACES. The challan CIN ties the credit back to the specific bank deposit.

Reconciliation logic on the recipient side: filter your TDS receivable ledger for the same deductor TAN over the same period, group by gross invoice amount, and confirm the booked credit equals 10% of the corresponding professional services revenue. If your ledger still tagged this entry as Section 194J, the matching engine must accept payment code 1003 as equivalent — which is the cross-era / dual-mode behaviour discussed earlier.

Cross-Reference Quick Lookup: Most-Asked Codes

The most frequent code lookups Indian finance teams have surfaced in the first month after cutover:

The exact code numbers in the second column are indicative — confirm against the CBDT-notified list before locking into production. The structural grouping (1001 series for salary, 1002–1015 for common non-salary TDS, 1062 area for non-resident, 1071+ for TCS) is stable.

Industry Code Profiles: What Most Indian Sectors Actually Use

Different industries activate different code subsets. The high-volume codes for typical Indian sectors are:

IT services and consulting. Primary code 1003 (professional fees, ex-194J) — typically 70–85% of inbound TDS receivable. Secondary code 1002 (contractor, ex-194C) — 10–25% for project-shaped work. Occasional 1062 (non-resident, ex-195) for offshore subcontractor payments. Total of two to four active codes.

Manufacturing and engineering. A wider mix. Code 1002 (contractor) for sub-contracted assembly and fabrication. Code 1003 (professional fees) for design and certification consulting. Code 1008 / 1009 (rent of plant or building) for factory and warehouse leases. Code 1012 (purchase of goods above ₹50 lakh) on the deductor side for raw material procurement. Code 1007 (commission) for dealer and channel partner payments. Five or six active codes for a typical mid-size manufacturer.

NBFC and banking. Code 1005 (interest, ex-194A) is dominant on the inbound side from depositors and borrowers. Code 1003 (professional fees) for credit advisory, valuation, and legal services. Code 1062 (non-resident) for cross-border lending. On the deductor side, NBFCs deduct under 1005 on every interest payout to depositors above the ₹40,000 threshold (₹50,000 for senior citizens).

Real estate and infrastructure. Code 1009 (rent of land or building) is the headline code — often 60–80% of receivable balance for landlords with large lease portfolios. Code 1002 (contractor) for construction work. Code 1003 (professional fees) for architects, structural engineers, and project managers. The annual rent threshold of ₹2,40,000 makes payment code 1009 the most-tracked code for real estate businesses.

E-commerce and platform sellers. Code 1010 (e-commerce operator payments, ex-194O) dominates — typically 70%+ of inbound TDS for marketplace-only sellers. Code 1003 (professional fees) for marketplace consulting. Cross-link to the retail and D2C cluster for marketplace settlement reconciliation patterns.

Hospitality and hotels. Code 1009 (rent) for franchise and OTA-leased property arrangements. Code 1007 (commission) for OTA commission deductions. Code 1002 (contractor) for F&B outsourcing and event services. The OTA-side reconciliation is covered in the hospitality cluster.

Common Errors at the Code Transition (and How to Catch Them)

Five recurring failure modes have emerged in the first month of operation:

Error 1: Mixed-code challan files. A bank payment file containing both March deductions (legacy codes) and April deductions (payment codes) results in OLTAS posting under inconsistent identifiers. Fix: split bank payment runs by deduction-month — March deductions in one file with legacy codes, April-onwards deductions in a separate file with payment codes.

Error 2: Wrong payment code on the challan. Operations teams unfamiliar with the new dropdown have selected nearby codes by accident — for example 1003 (professional fees) when 1002 (contractor) was correct. Fix: file a challan correction through TRACES within the same return cycle. The CIN-to-code reassignment flows through to the deductee’s Form 168 once the return is filed.

Error 3: Return preparation FVU still on the old version. Some return preparation utilities default to the previous FVU version. Filing Q1 FY 2026-27 with the legacy FVU produces an FVU error. Fix: download and install the post-April 2026 FVU before preparing Q1 returns.

Error 4: Dual-system inconsistency. When the ERP carries the legacy section code but the return preparation tool generates the payment code (or vice versa), the entry posted to OLTAS does not match the entry in the deductee’s Form 168. Fix: align both systems on payment code, with legacy section as a metadata-only field for audit traceability.

Error 5: 206AB rate-doubling still firing. The non-filer flag in the vendor master should have been disabled on April 1, 2026. ERPs that left the rate-doubling logic active are over-deducting on every flagged vendor. Fix: disable the rate-doubling rule, refund the excess TDS to the vendor, and adjust the next return.

What Reconciliation Teams Should Ship This Month

If you are one month into the new system, three deliverables should be in place by the end of May:

1. A Q4 FY 2025-26 return filed cleanly under legacy codes. The May 31 deadline closes the 1961 Act period for your organisation. Confirm Form 16A certificates for the year are generated with old section codes, and pull a final FY 2025-26 Form 26AS for archive.

2. A Q1 FY 2026-27 return-prep test run. The actual filing deadline is July 31, but a test run in May against current April activity catches code-mapping issues while there is still time to fix them at the master level rather than at the return-correction level.

3. A reconciliation pass on April Form 168 entries. TRACES updates Form 168 within 7–10 days of challan deposit and return processing. April challan deposits are now reflecting in deductee Form 168s. Run a reconciliation against your TDS receivable ledger for April activity to catch any code mismatches before the volume compounds in May and June.

For the comprehensive transition handling guide, see the Section 393 article which covers the parent-section consolidation logic, and the cross-era TDS reconciliation guide for the dual-code matching framework that the next two quarters of reconciliation will need.