For most of the life of the TDS system, a correction statement could be filed at any time. A deductor who discovered in 2024 that a PAN had been wrongly reported in 2015 could go back and fix it. Deductees chasing missing credit in Form 26AS relied on exactly that.
That is no longer the position. Correction statements are now subject to a time limit, and it has already closed off the earliest years of the system.
The change that closed the door on old years
The Finance (No. 2) Act, 2024 introduced a time limit on the filing of correction statements in respect of TDS and TCS statements. With effect from 1 April 2025, no correction statement may be filed after the expiry of six years from the end of the financial year in which the original statement was delivered.
The rationale was administrative: perpetual revisability meant that credit positions for very old years could change long after assessments had been completed, and the department had no closure. The effect on deductors is that errors have a shelf life, and after it expires they cannot be fixed at all.
This is not a soft deadline. Once the six years have run, the TRACES facility does not accept a correction for that period. There is no application process to extend it.
It is one of the few hard closure rules in income tax compliance in India, and there is no application to extend it.
How the six-year period is computed
The period runs from the end of the financial year in which the statement was delivered, not from the quarter to which the deduction relates. That distinction matters at the margins, because a statement for the March quarter is typically delivered in the following financial year.
Working through the current position: during the financial year 2025-26, corrections were available for statements delivered from the financial year 2019-20 onwards. Statements for the financial year 2017-18 and earlier fell outside the window entirely. Each passing financial year drops another year off the back.
The practical implication is a housekeeping one that most organisations do not perform: at the start of each financial year, identify the year that is about to fall out of the window and check whether anything in it still needs correcting. Once it is gone, a deductee who has been chasing missing credit for that year has no route left through the deductor.
What a correction statement can and cannot fix
A correction statement filed on TRACES, using the consolidated file for the relevant quarter, can address most of what goes wrong in a return:
- Deductee details — name, PAN, amount paid, tax deducted, section under which deducted, date of payment or credit.
- Adding a deductee who was omitted from the original statement.
- Deductor details — address, responsible person, contact details.
- Mapping of a deduction to a challan, where the deduction was reported against the wrong challan.
- Rate and section — where tax was reported under the wrong section, which then produces a short-deduction default.
What it does not do is create money. If tax was under-deducted or not deposited, the correction statement records the correct position but the shortfall, with interest, still has to be paid. A correction filed without the corresponding payment simply converts one default into another.
Nor does a correction statement address a defect in the challan itself, which is a separate mechanism.
Challan errors are a different problem
A challan carries several fields, and an error in any of them can leave tax paid but unmatched — which, from the deductee’s point of view, is indistinguishable from tax not paid.
The common errors are the assessment year, the major head, the minor head, the nature of payment and the TAN. Correction of these follows two different routes depending on timing:
Through the bank, within a short window after the deposit, for certain fields. Banks accept correction requests for specified fields within prescribed periods measured from the date of deposit, and the periods differ by field.
Through the assessing officer or the online challan correction facility, once the bank window has closed. Where the challan has been consumed in a statement, the correction has to be consistent with the statement, or the statement corrected alongside.
The order of operations matters. Correcting a statement to point at a challan that is itself wrongly tagged does not resolve the mismatch. Where both are wrong, the challan is fixed first and the statement is then aligned to it.
PAN errors and the cost of getting them wrong
A wrong or invalid PAN in a TDS statement has two consequences, and the second is expensive.
First, the deductee does not receive credit. The deduction sits against a PAN that does not belong to them, and no amount of explanation to the department substitutes for a corrected statement.
Second, the deduction is treated as having been made without a PAN, which attracts the higher rate applicable in those circumstances. The result is a short-deduction default computed at the difference between the higher rate and the rate actually applied — often on a substantial base.
The number of PAN corrections permitted in a correction statement is restricted, and structural changes to a PAN are not permitted at all. This is one of the reasons vendor and employee master data hygiene is a TDS control rather than an administrative nicety: validating a PAN before the first payment costs nothing, and correcting it afterwards may not be possible at all once the six-year window has run.
Vendor and employee master data is therefore a business taxation control rather than an administrative housekeeping task.
Section 234E: the fee that cannot be waived
Section 234E levies a fee of ₹200 for every day during which the failure to deliver a statement continues. The fee is subject to a ceiling: it cannot exceed the amount of tax deductible or collectible to which the statement relates.
Three features of section 234E are worth being precise about, because they distinguish it from most other charges under the Act.
It is a fee, not a penalty. It is not levied by an order following an opportunity of hearing; it is computed and demanded, and it is payable along with the statement.
There is no waiver provision. Unlike a penalty, where reasonable cause may be pleaded, section 234E contains no discretion to reduce or waive the fee. The only limits are the daily rate and the ceiling.
The statement will not be accepted without it. In practice, the fee has to be paid before the delayed statement can be filed, which means that a deductor sitting on an unfiled statement is accruing a fee that they will have to pay in full before they can stop it accruing.
The arithmetic is unforgiving. A statement delayed by a year accrues ₹73,000, subject to the ceiling. A deductor with four quarterly statements outstanding across two TANs is looking at a six-figure fee for a purely procedural failure.
Section 271H: the penalty, and the escape from it
Separately from the fee, section 271H provides for a penalty of not less than ₹10,000 and not more than ₹1,00,000 where a person fails to deliver a statement within the prescribed time, or delivers a statement containing incorrect information.
There is a specific relief. No penalty is levied under section 271H for failure to deliver the statement in time where the person proves that the tax deducted or collected, together with the fee and interest, has been paid to the credit of the Government and the statement has been delivered before the expiry of one year from the prescribed due date.
That one-year escape is the reason a delayed statement should be filed rather than left. A deductor who files eleven months late pays the section 234E fee but escapes the penalty. A deductor who files thirteen months late pays both.
Section 273B also permits a penalty under section 271H to be avoided where reasonable cause for the failure is proved, but that is a contested route and depends entirely on the facts.
Reasonable cause under section 273B is a contested route decided on the facts, which is the point at which it crosses into tax litigation.
A remediation sequence
Where a deductor is cleaning up historic defaults, the order below avoids most of the rework:
- Download the default summary and justification report from TRACES for each TAN and each year. The justification report identifies the specific deductee rows and the reason for each default.
- Identify which years remain within the six-year window. Anything outside it cannot be corrected, and effort should be directed at what can.
- Fix challans first — assessment year, major and minor head, TAN — through the appropriate route.
- Pay any short deduction with interest before filing the correction, so the statement and the payment are consistent.
- File the correction statement using the consolidated file for the quarter.
- Verify Form 26AS of the affected deductees after processing, rather than assuming the correction took effect.
- Record the position for the tax audit, where TDS compliance is separately reported. Our note on discrepancies found in tax audits covers that reporting.
Where the volume is large, the exercise is closer to an accounting and bookkeeping reconstruction than to a filing task.
Contact Now – +919034263307
Visite websites – taxationlegaladvisor.in
