The TDS receivable ledger accrues tax credit at invoice time, but only Form 26AS credits are claimable in the ITR. At scale, matching requires TAN-level logic across multi-TAN deductors, tolerance handling for rate and rounding differences, and cross-era support for FY 2025-26 legacy codes alongside FY 2026-27 payment codes.
Match each ledger entry to Form 26AS on four keys — deductor TAN, section code (or post-April-2026 payment code), quarter, and amount — and classify unmatched entries into typed outcomes: amount mismatch, PAN error, missing credit, or cross-quarter slip. Route each outcome to the deductor with Form 16A (or Form 131) and challan references. Reconcile multi-TAN deductors by aggregating at the client PAN level.
Ledger fields capturing deductor TAN and section at invoice level. TAN-to-client master aggregating branches under a single economic client. Tolerance band for rounding differences, strict match on rate differences.
Confirmed Form 26AS credits available to claim in the ITR, a live list of unmatched entries by deductor for structured follow-up, and no year-end scramble to discover missing credits after Q4 close.
TDS receivable ledger reconciliation is the process of matching each entry in your company’s TDS receivable account against a corresponding credit in Form 26AS. It determines which tax credits are confirmed, which are delayed, and which require action from a counterparty deductor. When done systematically and at sufficient frequency, it eliminates the ITR-season scramble of discovering missing credits after Q4 books are closed.
2026 Migration Update — Throughout FY 2026-27, the TDS receivable ledger will carry both legacy section codes (for FY 2025-26 invoices where credits land via correction statements) and new payment codes for FY 2026-27 deductions under the Income Tax Act 2025. Reconciliation logic must support cross-era matching so that a legacy 194J entry can align with a new payment-code credit referring to the same service. See the cross-era TDS reconciliation guide and the 2026 migration checklist.
What the TDS Receivable Ledger Records
The TDS receivable ledger is a sub-ledger or account within the company’s general ledger that tracks TDS deducted by customers, clients, or financial institutions that the company expects to claim as a credit in its income tax return. Under accrual accounting, an entry is created when the invoice is raised — at the gross amount, with a separate TDS receivable line for the deducted portion. The balance in this account represents tax already paid on the company’s behalf by its counterparties.
The reconciliation matches each ledger entry to its Form 26AS credit using four primary keys: deductor TAN, section code, quarter, and certificate number where available. A matched entry can be closed; an unmatched entry requires follow-up with the specific deductor.
Three Reconciliation Outcomes
Matched
The Form 26AS credit and the TDS receivable ledger entry agree on deductor TAN, section code, quarter, and amount. No action required. The entry is confirmed for ITR credit claim.
Amount Mismatch
Form 26AS shows a credit from the correct TAN under the correct section, but the amount differs from the ledger entry. This is classified as a TAX_DEDUCTION variance. Common causes: the deductor applied a different TDS rate than the company expected; the deductor applied TDS to a net amount after accounting for a credit note; or a rounding difference exists. Each variance must be reviewed and documented — small rounding differences are typically accepted; rate differences require a query to the deductor.
Missing Credit
A ledger entry has no corresponding Form 26AS credit from the deductor TAN. This could indicate: the quarterly TDS return has not been filed yet (timing issue); the deductor filed with an incorrect PAN; the challan was not deposited. The action depends on determining which of these applies.
TDS Receivable Reconciliation Outcomes
| Outcome | Description | Variance Code | Action Required |
|---|---|---|---|
| Matched | Ledger entry = Form 26AS credit (TAN, section, quarter, amount) | None | Close entry; include in ITR claim |
| Amount mismatch | Credit present but amount differs | TAX_DEDUCTION | Review rate applied; query deductor if difference > rounding |
| Missing — timing | Credit absent; quarterly return not yet due or recently filed | None (timing) | Re-check Form 26AS after 10–15 business days |
| Missing — PAN error | Credit absent; deductor filed return with wrong PAN | NOT_DEPOSITED (pending) | Ask deductor to file C1 correction on TRACES |
| Missing — not deposited | Deductor has not filed challan or return | NOT_DEPOSITED | Escalate to deductor with formal follow-up record |
Scale and Tooling
An IT services company billing 80 clients across 194C (contractor), 194J (professional services), and 194I (rent) sections may generate 300–400 Form 26AS entries per financial year. Each entry must be matched to a specific invoice or payment in the TDS receivable ledger. VLOOKUP-based spreadsheet matching works for organisations with fewer than 50 entries but fails at higher volumes because it cannot handle TAN name variations, multi-TAN clients, or tolerance-based matching for rounding differences.
Closing the TDS receivable ledger entry follows two paths: either the entry is matched to a Form 26AS credit and tagged for ITR claim, or it is formally written off with documented management approval, a record of follow-up attempts with the deductor, and a note explaining why the credit was not recoverable. Write-offs without documentation create audit exposure.
TDS reconciliation software designed for this use case imports Form 26AS data and maps it against the TDS receivable ledger by TAN, section, and quarter — applying the same multi-pass matching logic used for payment reconciliation. The Income Tax India portal provides Form 26AS downloads that feed directly into such systems. Reconciliation software India platforms built for Indian compliance handle multi-TAN clients, tolerance-based amount matching, and generate deductor-specific follow-up reports for the entries that remain open after each quarter’s Form 26AS is downloaded and processed.
Financial Exposure From Unreconciled TDS Receivables
The financial risk of unreconciled TDS receivables extends beyond delayed credits. Section 205 of the Income Tax Act bars the department from recovering tax from the deductee where tax has been deducted at source — but this protection applies only when the deduction actually occurred and was deposited. If the deductor failed to deposit (or deposited under a wrong PAN), Section 205 protection does not activate for the deductee, and the credit remains unclaimed.
CBDT Instruction 5/2013 directs Assessing Officers to pursue the deductor for recovery rather than denying credit to the deductee, but in practice, the deductee bears the operational burden. Where the deductor filed the return with the wrong PAN (a C5 correction scenario), the credit sits in another taxpayer’s Form 26AS. Only the deductor can initiate the correction — the recipient has no mechanism to move the credit independently. Until the correction is processed, the receivable remains open and the ITR credit claim is blocked.
For enterprises operating at scale, even a small percentage of unreconciled receivables creates material exposure. A company with annual revenue of Rs 100 crore and an average TDS deduction rate of 2% carries Rs 2 crore in TDS receivables. If 10% of those receivables remain unreconciled at year-end due to wrong-PAN entries, late filings, or non-deposits, the exposure is Rs 20 lakh in credits that cannot be claimed — directly reducing the effective tax refund or increasing the advance tax shortfall. At a 5% unreconciled rate, the exposure is Rs 10 lakh. These amounts compound across financial years when prior-year open items are not resolved before the Section 154 rectification window closes (four years from the end of the relevant assessment year).
Quarterly reconciliation with deductor-level follow-up is the only mechanism that converts these receivables into confirmed credits before the ITR filing deadline.