Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
TDS correction statements for FY 2018-19 through FY 2022-23 become permanently time-barred on March 31, 2026 under the Section 200 limitation. PAN errors, challan mismatches, amount discrepancies, and wrong section codes for these five years cannot be rectified after that date, exposing deductors to Section 201 demand notices, 1.5% per month interest, and Section 40(a)(ia) disallowance.
Pull Form 26AS and AIS for every deductee-year in the FY 2018-19 to FY 2022-23 range, compare against the deductor's 26Q and 27Q returns, and classify each mismatch as PAN error, challan mismatch, amount discrepancy, section code error, or deductee-master error. Route each typed variance to its correction statement queue on TRACES before the March 31 cut-off.
Variance taxonomy with typed correction codes. Deadline tracker per financial year. TRACES correction statement routing queue with ageing indicators against March 31, 2026.
A closed punch list of filed correction statements, refreshed Form 26AS entries matching the deductor ledger, and a documented audit trail of every FY 2018-19 to FY 2022-23 mismatch that was rectified before the permanent time-bar.
TDS correction statements for FY 2018-19, FY 2019-20, FY 2020-21, FY 2021-22, and FY 2022-23 become permanently time-barred on March 31, 2026. After that date, deductors cannot file correction statements for these years on TRACES, and any errors in the underlying TDS returns — wrong PAN, challan mismatch, amount discrepancy — cannot be rectified. For organisations with TDS receivable mismatches that trace back to these years, this is a closing window with significant financial consequences.
Which Financial Years Are Affected
The time-bar applies to five consecutive financial years:
| Financial Year | Quarter Range | Correction Deadline | Status After March 31, 2026 |
|---|---|---|---|
| FY 2018-19 | Q1–Q4 | March 31, 2026 | Permanently barred |
| FY 2019-20 | Q1–Q4 | March 31, 2026 | Permanently barred |
| FY 2020-21 | Q1–Q4 | March 31, 2026 | Permanently barred |
| FY 2021-22 | Q1–Q4 | March 31, 2026 | Permanently barred |
| FY 2022-23 | Q1–Q4 | March 31, 2026 | Permanently barred |
| FY 2023-24 | Q1–Q4 | Remains open | Can still be corrected |
| FY 2024-25 | Q1–Q4 | Remains open | Can still be corrected |
The limitation period under Section 200 of the Income Tax Act 1961 caps how far back deductors can file correction returns. March 31, 2026 marks the end of the permissible window for the five affected years. This date is absolute — there is no provision for condonation of delay for correction statements under this provision.
What Types of Corrections Become Impossible After March 31
The following error types, which are corrected through TDS correction statements on TRACES, will become irrecoverable for FY 2018-19 through FY 2022-23 after March 31, 2026:
PAN errors: Where the deductor filed the return with an incorrect PAN for the deductee, the TDS credit does not appear in the deductee’s Form 26AS under the correct PAN. The deductee cannot claim this credit in their income tax return without a correction.
Challan mismatches: Where the challan BSR code, serial number, or deposit date was entered incorrectly in the return, the TDS credit does not map correctly to the underlying payment. TRACES shows the challan as unmatched.
Amount discrepancies: Where the TDS amount in the return differs from the amount deposited via challan, the credit in Form 26AS may be less than what was actually deducted and deposited.
Section code errors: Where the wrong TDS section was used (e.g., 194C when it should have been 194J), creating a classification mismatch in the deductee’s credit statement.
Deductee details errors: Where name, address, or other deductee master data was entered incorrectly.
How to Check If You Have Outstanding Corrections
The fastest way to identify outstanding issues for the five affected years is a three-step check:
Step 1 — Download TRACES mismatch report. Log in to TRACES as a deductor. Navigate to “Statements / Payments” and then “Challan Status.” Pull the consolidated challan status for each of the five affected years. Unmatched or overbooked challans are visible here.
Step 2 — Check 26AS for deductees who have flagged mismatches. If your accounts receivable or vendor management teams have received complaints about TDS credit not appearing in 26AS, those are your highest-priority correction targets. Collect the list of deductees, their PAN, the quarter, and the amount in dispute.
Step 3 — Run a ledger-to-26AS comparison for high-value deductors. For organisations with significant TDS receivable balances from FY 2018-22, download the Form 26AS for those years and compare against your TDS receivable ledger entries. Any ledger entry not matched to a 26AS credit for the correct quarter and section is a potential correction candidate.
Most Common TDS Errors That Need Correction Now
Across high-volume TDS deductors — IT services firms, manufacturing companies, and financial intermediaries — the most frequently corrected errors in older years are:
Challan BSR code errors: TRACES returns the challan as “unmatched” even though the tax was deposited. The underlying deduction records cannot be mapped to the challan, so the credit does not appear in 26AS.
PAN of deductee incorrect: The deductee’s TDS does not appear in their 26AS at all, or appears under a different entry. Common for payments made to sole proprietors or individuals whose PAN was not collected at time of payment.
Amount short in return vs. challan: Deductor deposited ₹1,20,000 in challan but return shows ₹1,00,000. The deductee’s 26AS shows only ₹1,00,000.
Return filed for wrong quarter: Deduction made in Q2 (July–September) but reported in Q3 return. This creates a quarter mismatch that affects the deductee’s ability to claim credit in the correct period.
Step-by-Step: Filing a Correction Statement on TRACES Before the Deadline
Given the March 31, 2026 deadline, the process must move quickly:
Step 1 — Prepare correction data. Create a CSV or Excel file with the specific corrections needed: deductee PAN, original challan details, correct challan details, corrected amounts, corrected section codes. TRACES correction statements require the original return data as a base.
Step 2 — Request consolidated TDS file from TRACES. Log in at the TRACES portal, navigate to “Downloads,” and request the Consolidated TDS File (CSI file) for the relevant quarter and year. This is the base file from which you build the correction statement.
Step 3 — Prepare correction file using NSDL FVU. Use the latest version of the NSDL FVU (File Validation Utility) to prepare the correction file. Match the version to the applicable Form 24Q or 26Q format for the year in question.
Step 4 — Upload correction statement. Upload the validated correction file on TRACES under “Statements / Payments” > “Upload TDS.” Note the PRN (Provisional Receipt Number) as confirmation.
Step 5 — Verify credit update in 26AS. TRACES typically processes correction statements within 3–7 business days. Confirm the deductee’s 26AS reflects the corrected credit after processing.
The time pressure here is real. With TRACES processing taking 3–7 days, the effective filing deadline for corrections to be processed before March 31 is approximately March 24, 2026. Start the TRACES correction workflow immediately.
Corrections for FY 2023-24, 2024-25, and 2025-26 Stay Filable Through March 2029
The March 31, 2026 time-bar closes the window for five specific years (FY 2018-19 through FY 2022-23). It does not affect the more recent years. Correction statements for FY 2023-24, FY 2024-25, and FY 2025-26 remain filable under the standard three-year limitation window, with the FY 2025-26 corrections staying open until approximately March 31, 2029.
One important point for finance teams planning post-April 2026 correction workflows: any correction filed for FY 2023-24, FY 2024-25, or FY 2025-26 — even if filed in FY 2026-27 or later — must continue to use the old section codes (194C, 194J, 194A, and so on) and the old form references (Form 26Q, Form 16A, Form 26AS). These corrections relate to transactions that occurred under the Income Tax Act 1961, and the section numbering applicable at the time of the original deduction governs the correction.
This creates a practical split in your correction workflow after April 1, 2026. Fresh Q1 FY 2026-27 filings will use new Section 393 sub-clause codes and payment codes 1001–1092. Simultaneously, any correction to an earlier year’s return will still reference 194C or 194J codes. A reconciliation system that supports a dual-mode configuration (processing legacy, payment_code, or dual entries) can handle both without forcing teams to keep parallel tools. The cross-era TDS reconciliation guide walks through how to tag each correction workflow so it routes to the correct code set, and the TDS 2026 migration checklist covers when to cut over ERP masters versus when to retain old codes for correction filings.
What Happens If You Miss the March 31 Deadline
After March 31, 2026, the TRACES portal will not accept correction statement filings for FY 2018-19 through FY 2022-23. The errors in those years become permanent in the system of record.
For deductors, this means potential demand notices under Section 200A for any short deduction that is identified in a future scrutiny assessment. Interest under Section 201(1A) at 1.5% per month from the deduction date continues to accrue on short-deducted amounts. The expense underlying a 194C or 194J payment where TDS was not correctly deposited may also be disallowed under Section 40(a)(ia).
For deductees, the consequence is unclaimed TDS credit. If a deductor’s PAN error or challan mismatch prevented the credit from appearing in Form 26AS, and the correction window closes on March 31, the deductee loses the ability to claim that credit in a future revised return for the affected year.
TDS reconciliation software that maintains a structured TDS receivable ledger and matches Form 26AS downloads against expected credits by quarter and section can surface these mismatches systematically, rather than relying on ad hoc discovery through vendor complaints.
Organisations that process TDS under multiple sections across many deductors should run a complete ledger-to-26AS comparison for all five affected years before March 21, 2026, to leave time for both the TRACES correction workflow and the portal’s processing window. The reconciliation software India framework for this type of systematic cross-year comparison is well-established — the constraint is time, not complexity.