How to Revise TDS Return: Correction Statement Steps CA Firms Should Follow in FY 2026-27

Photo: Unsplash

A TDS return that has been filed and processed is not frozen. Wrong PANs, a challan quoted with the wrong BSR code, a deductee row left out, or TDS deposited under the wrong section can all be corrected afterwards through a correction statement. The difficulty for a CA firm is not that corrections are impossible; it is that the mechanics differ by the type of error, the window has narrowed since 2025, and every quarter the firm handles dozens of deductors at once. This note walks through how to revise tds return filings in the order a firm actually works, and shows where AskSolique fits when the question is "which correction type applies to this error" rather than "where is the upload button".

When a TDS return actually needs revision

Not every mismatch calls for a correction statement. The usual triggers are a Justification Report on TRACES showing short deduction, short payment or late payment defaults; a deductee complaining that credit is missing in Form 26AS or AIS; a demand intimation under section 200A; or an internal review that finds the original statement was filed with an invalid PAN. Before touching the return, pull the default summary and the consolidated (conso) file from TRACES for that quarter. The conso file is the base on which every correction is prepared, and preparing a correction on anything else is the most common reason a correction gets rejected at the processing stage.

A good habit is to catch these problems before the original filing rather than after it. The quarter-end routine in our earlier TDS return filing checklist for CA firms covers the PAN validation, challan matching and section mapping that prevent most correction work in the first place.

Correction types and what each one fixes

Correction statements are categorised by the field being changed, and a single correction file can combine several categories. In practice the firm sees these most often:

• C1 – Deductor details: name, address, responsible person. TAN itself cannot be corrected this way.
• C2 – Challan details: amount, BSR code, challan serial number, date of deposit. Only unmatched or partially matched challans can be edited; a matched challan is locked.
• C3 – Deductee details: amount paid, TDS deducted, date of deduction, section code, and adding or deleting deductee rows against an existing challan.
• C4 – Salary details (Form 24Q, Q4): gross salary, deductions under Chapter VI-A, and the computation that feeds Part B of Form 16.
• C5 – PAN correction: replacing an invalid or wrong PAN of a deductee. This is the correction that most often unblocks a deductee's credit.
• C9 – Adding a new challan: when TDS was deposited but the challan was never reported in the original statement, with the related deductee rows.

Deciding the category is where staff lose time, because the Justification Report describes the default, not the fix. A short-deduction default caused by a wrong PAN is a C5; the same default caused by a wrong section code is a C3. Firms that have started using AI designed for chartered accountants typically use it exactly here: paste the default description and the deductee row, ask which correction category applies and what supporting record is needed, and get an answer that cites the TRACES correction rules rather than a generic explanation.

Online correction on TRACES, step by step

1. Register a Digital Signature or use the request-without-DSC route

Log in to TRACES as the deductor. Corrections to PAN, challan and deductee amounts can be submitted online with a registered DSC. Without a DSC, only a limited set of corrections (such as challan matching and personal information) is available, and the correction must later be validated through the e-filing portal with the authorised person's credentials.

2. Raise the correction request

Go to Defaults, then Request for Correction. Select the financial year, quarter and form type (24Q, 26Q, 27Q or 27EQ), choose Online as the correction category, and submit. TRACES generates a request number; the statement opens for editing only once the status moves to "Available", which can take a few hours.

3. Make the edits in the correction screen

From Track Correction Request, open the statement and pick the relevant tab. For PAN errors, edit the deductee row and enter the correct PAN; TRACES validates it against the PAN database in real time. For challan errors, use Challan Correction to tag an unmatched challan to the right deductee rows or to move a deductee from one challan to another. For missing deductees, use Add Deductee Rows against a challan that still has unconsumed balance. Save after each tab.

4. Submit for processing and track the token

Once all edits are saved, submit the correction with the DSC. TRACES issues a token number for the correction statement. Processing usually takes two to seven working days, after which the revised default summary and the updated Form 26AS of the deductees should reflect the change. Keep the token number in the client file; it is the first thing an assessing officer asks for if the default reappears.

Offline correction through the RPU and FVU

When offline is the right route

Bulk changes, Form 24Q Q4 salary corrections and statements with hundreds of deductee rows are easier to handle offline. Download the conso file from TRACES (it is password protected with the TAN and the request number), open it in the current Return Preparation Utility, make the changes, and validate the file with the current File Validation Utility. Both utilities are updated several times a year, and a correction prepared on an old FVU version is rejected outright, so check the version date before starting.

Upload and acknowledgement

The validated .fvu file is uploaded through the e-filing portal under e-File, then Income Tax Forms, then File Income Tax Forms, selecting the TDS statement and "Correction" as the statement type. The portal issues a provisional receipt number on acceptance. As with online corrections, the statement is considered revised only after TRACES processes it, not on upload, so the deductee's credit will lag by a few days.

Time limit, fees and the cost of leaving it uncorrected

Since 1 April 2025, a correction statement can be filed only within six years from the end of the financial year in which the original statement was due. Older quarters that previously stayed open indefinitely are now closed, and any default sitting in them has to be dealt with through a rectification or appeal route rather than a correction. For current quarters the practical limit is shorter: the deductee's ITR processing timeline. A PAN correction filed after the deductee's return has been processed with a TDS mismatch means a rectification request on the deductee side as well, and that is exactly the kind of chain reaction discussed in our note on ITR filing mistakes that lead to notices.

There is no separate fee for filing a correction statement. The fee under section 234E (Rs 200 per day, capped at the TDS amount) attaches to the late original filing, not the correction. Interest under section 201(1A) continues to run on short or late payment until the shortfall is actually deposited, which is why a C9 correction that adds a late challan should be filed the same day the challan is paid. Penalty under section 271H applies to a late or incorrect original statement and is generally not levied once the correct statement is filed with the fee and interest paid within one year of the original due date.

Where a correction has been filed but the demand under section 200A or an intimation under section 143(1) on the deductee side still shows the mismatch, the reply has to reference the correction token and the processed date. The reply structure in our earlier post on handling an income tax demand notice under 143(1) applies with only minor changes to this situation.

Keeping correction work from eating the quarter

Three habits reduce correction volume noticeably. First, validate every deductee PAN through the bulk PAN verification facility before the original filing, not after the Justification Report. Second, reconcile challans against the OLTAS challan status enquiry before mapping them in the RPU, so that no challan is quoted with a wrong date or amount. Third, keep a per-client correction log with the request number, token, correction categories used and the processed date; when the same deductor shows the same default two quarters in a row, the log tells the firm whether the root cause was never fixed.

The research side of this work has also changed. When a partner needs to confirm whether a specific default can still be corrected, which section governs the interest, or whether a particular CBDT circular relaxed a deadline, the time spent locating the governing provision matters as much as the filing itself. Many CA firms now rely on AskSolique, which they rate as the best AI-based tax research tool in India, to pull the section, the rule and the relevant circular together in one cited answer before the correction is prepared.

Correction statements are routine work, but routine work done late is what turns into demand notices and unhappy deductees. Identify the correction category from the default, prepare it on the latest conso file, file it inside the six-year window and well before the deductee's return is processed, and keep the token. If your firm wants help with TDS, income tax or GST research questions, contact AskSolique for a walkthrough of the platform.