Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A consulting firm or professional with 20 or more clients receives TDS credits from many deductors under multiple sections (194J, 194C, 194I, 194H), each filing independently at different times and occasionally misclassifying sections. The recipient's Form 26AS aggregates everything, but late filings, section errors, and PAN slips prevent simple aggregate matching.
Parse Form 26AS XML into rows by deductor TAN, section code, quarter, and amount, and match each row to invoices in the income ledger using TAN plus section plus amount as keys. Classify unmatched rows as section misclassification, late-filed-return timing, or PAN error and route each to a deductor correction statement. Aggregate at the client PAN level for multi-TAN clients.
TAN-to-client master linking multi-branch deductors to economic clients. Per-invoice expected section and TDS stored in the income ledger. Typed variance classifier for section misclassification, timing, and PAN errors.
Every Form 26AS entry traced to an invoice or a documented deductor error, no phantom credits claimed against unmatched 26AS rows, and complete TDS credit claimed in the ITR with an auditor-ready trace file.
TDS multiple deductors reconciliation India is a challenge for any entity — consulting firm, contractor, or professional — receiving fees from 20 or more clients in a financial year. Each client deducts TDS independently, deposits it under their own challan, and files a quarterly return mapping the TDS to the recipient’s PAN. The recipient’s Form 26AS aggregates all these entries. The reconciliation task is to confirm that every entry in 26AS corresponds to income recorded in the books, at the correct section, and for the correct amount.
What the Multi-Deductor Scenario Covers
When a single PAN receives income from multiple sources — professional fees under Section 194J, contract payments under Section 194C, rent under Section 194I — each deductor files independently with no visibility into the others. The recipient’s aggregate TDS credit in 26AS is the sum of all deductors’ filings for that PAN.
The reconciliation scope for the recipient includes: verifying that 26AS is complete (all deductors who were supposed to deduct have filed), verifying section codes match the nature of income in books, and confirming that the TDS amounts in 26AS match the net deduction shown on invoices received from each client. For an employee who changed jobs in the year, both employers deduct TDS under Section 192, and the same reconciliation logic applies — but the additional complication is that double deduction can occur if Form 12B was not submitted to the new employer.
Where Reconciliation Breaks Down
Section code misclassification by deductors. A client may deduct TDS at 2% under Section 194C on a payment that the recipient has booked as professional fees income (194J at 10%). The net TDS deducted is lower than the TDS amount recorded in the recipient’s books. From the recipient’s perspective, the 26AS shows a lower credit than expected. From the deductor’s perspective, the filing is consistent with their classification. The correction requires the deductor to file a revised return.
Late TDS return filing by some deductors. Where a client files their quarterly TDS return after the due date, the TDS entry does not appear in 26AS until after processing. A recipient filing an advance tax computation in December may find that Q1 and Q2 TDS from three of their twenty clients is still missing from 26AS. The advance tax paid will be higher than necessary if the recipient cannot reliably forecast when the missing entries will appear.
PAN errors resulting in TDS credited to another entity. A deductor who enters an incorrect PAN — transposed digits, wrong entity — causes the TDS to be credited in 26AS under the wrong PAN. The recipient’s 26AS shows no entry for that deductor, while another unrelated entity has an unexpected credit. The fix requires the deductor to file a correction statement through TRACES, which can take 3–7 working days after submission.
Reconciliation Process
Step 1: Export Form 26AS as XML. Download the full-year Form 26AS from the income tax portal in XML format for the relevant PAN. The XML structure carries deductor TAN, deductee PAN, section code, amount paid, TDS deducted, and deposition status for each entry.
Step 2: Build a deductor-wise TDS receivable register. From the books of accounts, prepare a register that lists each client, total invoiced amount, section applicable, TDS rate expected, TDS amount expected, and TDS amount actually deducted (per invoice or receipt records).
Step 3: Match each 26AS entry to the corresponding invoice and receipt. For each entry in 26AS, locate the matching invoice in the register. The match criteria are deductor TAN, amount paid, and section code. Flag any 26AS entry with no matching invoice — this is a potential wrong-PAN credit that should not be claimed.
Step 4: Identify and classify exceptions. After matching, flag three categories: (a) invoices with TDS deducted in books but no corresponding 26AS entry — likely a deductor’s late filing or PAN error; (b) 26AS entries with no matching invoice — potential wrong-PAN credit or unrecorded income; (c) section mismatches — TDS at 194C in 26AS but 194J in books.
Step 5: Pursue corrections with individual deductors. For each category (a) exception, contact the relevant client and request confirmation that their TDS return was filed and the PAN was entered correctly. For category (c) mismatches, request a correction return from the client.
Multi-Deductor TDS Reconciliation — Exception Types
| Exception | Likely cause | Action required | Deadline to resolve |
|---|---|---|---|
| 26AS entry — no matching invoice | Wrong PAN used by deductor; or unrecorded income | Verify with deductor; do not claim if income not recorded | Before ITR filing |
| Invoice in books — no 26AS entry | Deductor filed late or PAN error | Follow up with deductor for TRACES correction | Before advance tax due date |
| Section code mismatch (194C vs 194J) | Deductor misclassified the engagement | Request revised TDS return from deductor | Before ITR filing |
| TDS amount mismatch (net of advance) | Deductor deducted on net payment, not gross | Reconcile to invoice total; flag underpayment or overpayment | Before ITR filing |
| Salary — no Form 12B disclosure | Employee changed employer without disclosing prior salary | Submit Form 12B to new employer; recompute TDS; pay shortfall | Before 31 March of the relevant FY |
What Automated Reconciliation Changes
When a consulting firm or contractor manages 50 or more active client engagements — each with independent TDS filing cycles — the manual effort of cross-referencing 26AS XML against an invoice register becomes significant each quarter. Errors in section codes and missing entries accumulate, and the year-end ITR filing then carries reconciliation risk.
TDS reconciliation software India that ingests 26AS XML and matches against the invoice register at the deductor-TAN level surfaces section mismatches, missing entries, and wrong-PAN credits as structured exceptions — before the advance tax deadline, not after the ITR is filed. Reconciliation software India configured for multi-source TDS tracking reduces the time spent chasing individual deductors for correction statements by identifying precisely which entries need correction and why.