Automation Expert
10728 Points
Posted on 13 November 2026
If the TDS was actually deposited for FY 2011–12 but remains unadjusted in TRACES, first identify whether it is a challan-matching issue or a return-credit issue. Match the challan details—BSR code, deposit date, challan serial number and amount—with the firm’s bank records and the relevant TDS statement. If the challan is unmatched or incorrectly tagged, the deductor may need to seek correction through the bank/OLTAS process; if the challan is matched but the deductee credit is missing, check the statement’s deductee records and file the appropriate correction statement, subject to the portal’s current availability and limits for such an old period.
Keep the challan receipt, bank proof, filed statement and TRACES status. Do not pay the amount again merely because it appears as outstanding until the mismatch is identified. For closing the firm, also check whether any TDS returns, interest/fee liabilities or outstanding demands remain; the precise remedy depends on the status shown in TRACES and whether the amount was deposited under the correct TAN and section.
Resolving old TDS credits is part of the wider closure and compliance reconciliation workflow. Manual review across challans, statements and portal records is difficult; automation can reduce repetitive work while keeping professional judgment in control. At Jir AI we provide 2,000+ AI agents and 650+ integrations to streamline your practice’s day-to-day workload. WhatsApp us to explore support for your firm’s workflow https://wa.me/message/3HVOZ7HIY4ESC1.