Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
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.
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.