TDS Reconciliation for Tax Audit: Books vs Challans vs Returns
A paid TDS challan does not prove that every deduction was correct or properly reported. Build separate obligation, deduction, payment and return-reconciliation layers.
AI Summary
Scope: FY 2025-26 / AY 2026-27 under the Income-tax Act, 1961 and applicable Income-tax Rules, 1962; do not reuse section/form references unchanged for Tax Year 2026-27. Verification date: 11 October 2026.
Four records answer four different questions
The expense ledger identifies transactions that may trigger TDS. The deduction ledger records tax actually deducted. Challans show deposits. The filed statement records deductee-wise reporting. A total agreeing at one layer does not demonstrate correctness at the others.
For the relevant Form 3CD review, Clause 34 asks for TDS/TCS particulars. Prepare a supporting reconciliation before entering the figures. Confirm the period, transaction category and applicable law instead of applying one rate across every supplier ledger.
Layer 1: build the obligation population
Extract relevant expense, purchase and liability accounts, including year-end credits and amounts capitalised where appropriate. Record payee identity, residence information, payment/credit dates, nature, amount and the reviewed TDS conclusion.
Assess thresholds, exemptions, certificates and other relevant conditions using evidence. Narration keywords can identify candidates but should not decide the final legal category. Keep transactions outside the obligation population with a short explanation when the reason needs review.
Layer 2: compare expected and actual deductions
Link the reviewed transaction population with deduction entries. Distinguish correct deductions, missed deductions, short deductions and items requiring a different timing or categorisation conclusion. Verify PAN and deductee identity before matching.
A small control example
Assume a reviewed fictional population requires ₹1,00,000 of TDS for the period. The ledger records ₹90,000 deducted, deposits total ₹85,000 and accepted statement rows total ₹80,000. These values create three different investigation amounts.
| Comparison | Difference | What to investigate |
|---|---|---|
| Reviewed obligation vs deductions | ₹10,000 | Missed/short deduction or population error |
| Deductions vs deposits | ₹5,000 | Timing, unpaid liability or reconciliation error |
| Deposits vs statement allocation | ₹5,000 | Unallocated challan, omitted row or reporting error |
These are control differences, not automatic findings of default. For example, a deposit outside the selected period may explain timing. Inspect dates and references before concluding. Do not combine all three differences into one disallowance figure.
Layer 3: trace challans and statements
Maintain challan references and allocation by period and deductee. Identify deposits used in a different statement, unmatched entries and excess amounts awaiting allocation. Compare the latest accepted statement or correction with the books, retaining the original and correction references.
Correcting a PAN or allocating a challan may resolve reporting without changing the underlying expense. Conversely, correcting a statement does not by itself establish that deduction and deposit timing were compliant. Keep the facts and consequences distinct.
Close the review loop
- Agree the transaction population with relevant books.
- Document applicability and deduction conclusions.
- Match deductions with deposits and return rows.
- Review timing, interest and potential tax consequences separately.
- Agree approved Clause 34 particulars with supporting totals.
When financials are prepared through assureOffice, reconcile TDS payable and relevant expenses with the approved statements. Keep the detailed tax working with the audit file. This combination gives the reviewer both a reliable closing balance and an explanation of the year's deduction and payment activity.
Use a balance roll-forward as a cross-check
Prepare a TDS-payable bridge: opening payable, current deductions, payments, supported corrections and closing payable. Agree each movement with the appropriate records. A current-quarter challan may clear an earlier deduction, so payment timing alone does not identify the expense period.
Suppose the ledger shows ₹50,000 payable, but a challan allocation report appears to show no unpaid balance. Trace opening items, unallocated payments and correction statements before clearing the difference. Separate the accounting balance from the return's transaction matching. Record which issue was corrected in books, which required a statement correction and which still needs follow-up with supporting evidence.
Related articles
- Cash Payments in Tax Audit: Identifying Transactions That Need Further Review
- Payments to Specified Persons: Preparing the Form 3CD Clause 23 Working
- AIS, TIS and Form 26AS Do Not Match the Books: How to Reconcile Them