Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A finance analyst files the quarterly Form 26Q for Q1 FY 2026-27 on the tenth of July. Two weeks later, an internal review or a deductee query flags a defect — one deductee's PAN is wrong, one challan reference does not tie to the OLTAS record, one payment was tagged as Section 194J when it should have been Section 194C, or a payment made in the last week of June was booked into the Q2 register and missed the Q1 return entirely. The original return is accepted; Form 168 for the deductee will surface the defect at year-end if the correction is not filed inside the current quarter. The question is not whether to correct — the correction is mandatory to close the gap in Form 168. The question is which correction type applies, how the TRACES workflow runs, and what penalty landscape sits behind the correction.
Every defect in a filed TDS return falls into one of six buckets. Bucket 1 — challan mismatch (BSR code, challan serial number, challan date, or challan amount) — corrects through a C2 statement against the OLTAS record. Bucket 2 — PAN error in a deductee row — corrects through a C1 statement that updates the PAN without touching the amount or the challan. Bucket 3 — amount mismatch (the deducted amount does not tie to the invoice) — corrects through a C3 statement that updates the deductee record. Bucket 4 — section drift (a Section 194J payment reported as Section 194C or vice versa) — corrects through a C2 challan re-tag plus a C3 deductee-record update. Bucket 5 — a payment booked into the wrong quarter — corrects through a C9 add-deductee against the correct quarter's challan (or a fresh challan deposit and C9 if the correct quarter has no unutilised challan). Bucket 6 — statement cancellation entirely — corrects through a C5 statement that voids the original and requires a fresh original filing. Each bucket has a different TRACES turnaround, a different rejection profile, and a different Section 200A intimation surface. From 1 April 2026, the Section 393(1) code on the correction must migrate to the successor payment code (for example code 1023/1024 for contractor, 1027 for professional fees, 1031 for purchase of goods) alongside the substantive change.
Access to TRACES with the deductor's TAN credentials. NSDL RPU (the Return Preparation Utility, Java-based) downloaded from the NSDL TIN website. FVU (the File Validation Utility) downloaded from the same source. A defect-classification working paper that captures the original acknowledgement number, the quarter, the defect bucket (C1 through C9), the affected deductee or challan, the correction filed, and the TRACES processing outcome. A calendar tracking every open FY 2018-19 to FY 2022-23 correction against the 31 March 2027 permanent time-bar with reverse-calculated escalation to the controller in the final six months. A Section 200A intimation register that logs every processed correction and the residual shortfall, if any, so a rejected correction is re-filed within the current quarter rather than surfacing as a Form 168 mismatch at year-end.
Every defect surfaced in the monthly TDS reconciliation is classified into one of the six buckets, routed to the correct correction type on TRACES, filed inside the current quarter, and closed on a Section 200A intimation. Form 168 for every deductee ties to the deductor's ledger with no rolling exception. The FY 2018-19 to FY 2022-23 backlog is reduced to zero before the 31 March 2027 time-bar, with the residual balance provisioned as an Ind AS 37 write-off where recovery is documented as impossible. From April 2026 onwards, every correction filed carries the Section 393(1) successor code, and the deductee's Form 168 refreshes on the correct code within three to seven business days of processing.
You filed Form 26Q for the quarter on the tenth. It was accepted. Two weeks later, someone flags a defect — one deductee’s PAN is wrong, a challan reference does not tie to the deposit record, or an internal audit query notes that a June payment was booked into the July register and never made it onto the Q1 return. The original filing is closed on TRACES. Form 168 for the deductee will surface the gap at year-end if you do nothing.
What do you actually do?
The quick answer
Every defect in a filed TDS return maps to one of six correction types on TRACES — C1 for a deductee PAN, C2 for a challan-detail change, C3 for a deductee record change, C4 for a Form 24Q salary annexure change, C5 for a statement cancellation, and C9 for adding a deductee row against an existing challan. Log into TRACES with the deductor’s TAN credentials, download the Conso file for the affected quarter, open it in NSDL RPU (Return Preparation Utility), apply the change, validate through FVU (File Validation Utility), and upload the .fvu file as a correction against the original acknowledgement number. Processing takes three to seven business days; Form 168 for the affected deductee refreshes once the correction is processed.
The one hard cliff — no correction statement can be filed after 31 March 2027 for FY 2018-19 through FY 2022-23. Five financial years close to correction simultaneously with no condonation route inside the Act.
Step 1 — Identify which of the six defect buckets you have
Before you open TRACES, classify the defect. The correction type follows from the defect type, and filing the wrong correction wastes a TRACES cycle.
Bucket 1 — Challan mismatch (C2)
The BSR code, the challan serial number, the challan date, or the challan amount reported on the statement does not match the actual Government receipt in OLTAS (Online Tax Accounting System). This surfaces on TRACES as a challan-mismatch flag on the original acknowledgement, or in the deductor’s Form 168 as a Rs figure the OLTAS reconciler cannot trace back to a valid challan. Correction type — C2. Verify the challan exists in the Government receipts register before filing; a C2 against a non-existent challan is rejected outright.
Bucket 2 — PAN error (C1)
A deductee row carries the wrong PAN — a typo, a swapped-digit error, or an invalid check-digit that TRACES accepted at the original filing but that fails the Form 26AS credit routing. The deductee’s Form 168 will not credit the deduction because the PAN does not resolve. Correction type — C1. The PAN update is the cleanest of the six corrections; no challan touchpoint, no OLTAS reconciliation, three-to-seven-day TRACES turnaround.
Bucket 3 — Amount mismatch (C3)
The deducted amount, the taxable amount, or the gross amount on a deductee row does not tie to the invoice. Often this surfaces from a deductee query — “Form 168 shows Rs 6,73,000 credited but our ledger says Rs 8,42,000” — and the reconciliation identifies that the original return reported a wrong amount on one deductee row. Correction type — C3. The twelve-step Form 168 shortfall investigation is the deeper treatment of this exact reconciliation flow, including the Section 206AA higher-rate case and the Circular 23/2017 GST-inclusive base case.
Bucket 4 — Section drift (C2 plus C3)
A Section 194J professional-fees payment was reported as Section 194C contractor, or vice versa. This is a two-part correction — the challan needs re-tagging (C2) if the challan itself was deposited under the wrong Section, and the deductee record needs updating (C3) to reflect the correct Section, TDS rate, and threshold treatment. From 1 April 2026, the Section 393(1) successor code on the correction must also migrate — code 1027 for the Section 194J leg, code 1023 or 1024 for the Section 194C leg (depending on individual/HUF versus other). The TDS payment codes 1001 to 1092 reference is the full cross-era coding table.
Bucket 5 — Booked in the wrong quarter (C9)
A payment made in the last week of June was booked into the July AP register and missed the Q1 Form 26Q entirely. The Q1 return has an unreported deductee row that the Q2 return is trying to squeeze in retroactively. The right correction is a C9 on the Q1 return — add the deductee row against an existing challan in Q1 that has unutilised balance, or deposit a fresh challan for the missed amount and then C9 the deductee row against that new challan.
Bucket 6 — Statement cancellation (C5)
The original return was filed for the wrong TAN, or for the wrong quarter, or was a duplicate of a return already filed. The entire statement needs to be voided. Correction type — C5. After the C5 is processed, a fresh original filing for the correct TAN and quarter needs to follow. C5 is the rarest of the six and always signals a process breakdown upstream — a controller should be looped in on any C5 filing.
Step 2 — Log into TRACES and download the Conso file
Sign in to the TRACES portal with the deductor’s TAN credentials. Navigate to “Statements/Payments” then “Request for Conso File” for the affected quarter (for example Q1 FY 2026-27 Form 26Q). The Conso file — a Government-signed consolidated statement in .txt format representing the current accepted state of the return — takes a few minutes to a few hours to generate depending on the queue. Once generated, download it under “Requested Downloads.”
The Conso file is the source of truth for the correction, not the .fvu you originally uploaded. Every subsequent correction builds on the most recently processed version — if a C1 correction has been processed on the return, the next correction must build on the C1-updated Conso file, not on the original.
Step 3 — Prepare the correction in NSDL RPU and validate through FVU
Open the Conso file in NSDL RPU (Return Preparation Utility) — the Java-based utility downloaded from the NSDL TIN website. Locate the row or challan that needs changing, apply the correction, and export the corrected file. The RPU output feeds into FVU (File Validation Utility), which performs the format and business-rule validation and produces the .fvu file for upload.
Common validation failures at this step — a corrected PAN that fails the check-digit test, a corrected challan amount that exceeds the OLTAS balance, a corrected Section code that no longer matches the challan’s payment head. Fix these in RPU before re-running FVU; a .fvu with validation errors will be rejected on upload.
Step 4 — Upload the correction against the original acknowledgement
Return to TRACES, navigate to “Statements/Payments” then “Correction Statement,” and upload the .fvu file against the original acknowledgement number for the quarter. TRACES issues a new acknowledgement for the correction. Processing takes three to seven business days on the standard queue; complex corrections (Section 200A intimation rebuttals, multi-challan C2 corrections, C9 additions against fresh challans) can extend to two to three weeks.
Step 5 — Verify Form 168 reflects the correction
Once TRACES processes the correction, the deductee’s Form 26AS and Form 168 update to reflect the corrected data. Log into TRACES under the deductee’s PAN (or ask the deductee to verify their end) and confirm the corrected credit is showing. A correction that TRACES accepts but that does not reflect in Form 168 signals a downstream processing issue — raise a support ticket on TRACES with the correction acknowledgement number.
The Form 168 as the new TDS annual statement article covers the annual view the deductee actually uses to claim the credit — the correction feeds this statement, and any residual shortfall surfaces here first.
The one to escalate first — the 31 March 2027 permanent time-bar
Corrections for FY 2018-19, FY 2019-20, FY 2020-21, FY 2021-22, and FY 2022-23 become impossible to file after 31 March 2027. The CBDT-notified time-bar under Section 200(3) read with Rule 31A closes the correction window permanently, and no condonation of delay route exists under the Act for a Rule 31A correction. Five financial years of unresolved defects — deductee PANs that never reconciled, challans that stayed mis-tagged, amounts that never tied to the invoice — become stuck in Form 168 mismatches that no future correction can resolve.
The seven-week pre-cliff correction sprint that Indian finance teams run through the second half of FY 2026-27 is the operational response to this. The full pre-cliff correction sprint walks through the week-by-week play — Week 1 extracts the backlog from TRACES by financial year, Week 2 classifies every line into the six buckets, Weeks 3 and 4 file corrections in priority order, Weeks 5 and 6 handle TRACES turnaround and rejection resolution, Week 7 signs off the residual with an Ind AS 37 provision for the irrecoverable balance. The March 2027 FY 2018-23 correction statement time-bar article is the deeper treatment of what exactly closes on that date and why the condonation route is not available.
The penalty landscape behind a late correction
The correction itself does not attract a fresh Section 234E late-filing fee if the original return was filed on time — the Rs 200-per-day counter applies only to the original filing. What does apply is Section 271H: a penalty between Rs 10,000 and Rs 1,00,000 that the Assessing Officer may direct for incorrect information in a filed statement. The Section 271H proviso protects the deductor if the tax with interest and Section 234E fee have been paid and the correct statement has been delivered within one year of the original due date. A correction filed inside that one-year window is protected; a correction filed beyond it is exposed to the full Section 271H ceiling.
The Section 200A intimation that TRACES issues after processing a correction is the surface where the Section 271H exposure crystallises. A defensible correction closes the underlying gap and the intimation shows no residual demand; a rejected correction leaves the gap open with interest under Section 220(2) accruing at 1 per cent per month on the shortfall — the TDS interest and penalty impact calculator models the running exposure on an illustrative Rs 1.69 lakh Form 168 shortfall across the delayed correction timeline.
From 1 April 2026 — the Section 393 code migration on the correction
The Income-tax Act 2025, effective 1 April 2026, consolidates the TDS provisions of the Income-tax Act 1961 into Section 393. Every deduction leg reported in Form 26Q from Q1 FY 2026-27 onwards must carry the Section 393(1) payment code (for example code 1023 or 1024 for the Section 194C contractor payment leg, code 1027 for Section 194J professional fees, code 1031 for the Section 194Q purchase-of-goods deduction). A correction statement filed after 1 April 2026 for a legacy Section 194X deduction carries the Section 393(1) successor code alongside the substantive change. Mis-coding on the correction — filing under the legacy Section 194X code where the Section 393(1) code should have been used — triggers a Section 200A intimation from the Centralised Processing Centre for TDS.
When the manual correction cycle outgrows itself
One correction per quarter is normal residual for a mid-market deductor — it is the artefact of an otherwise-clean monthly TDS close. Two to three corrections per quarter, sustained across a full financial year, signals a structural cause upstream: an AP process that is not classifying vendor invoices to the right TDS section on entry, a challan-deposit workflow that is not tagging the correct payment head at the counter, or a monthly TDS reconciliation that runs only against the deductor’s ledger and never against the deductee’s Form 168 view.
Above six to eight corrections per quarter, the manual C-type classification and TRACES cycle stops being a routine tax-executive task and becomes a rolling exception queue. The Deductor Form 168 query letter pack provides the standing template set for the recurring deductee-side chases; the TDS receivable aging workbook treats the running shortfall register as a first-class output that the controller signs off monthly. Above that threshold, moving the six-bucket defect classification and the TRACES correction cycle onto continuously refreshed detection — where Terra Insight’s TDS reconciliation software treats the Form 168 shortfall queue and the Section 200A intimation register as first-class outputs — is what keeps the quarterly TDS close inside a fifteen-day cadence rather than an open-ended firefight.
Go deeper
- FY 2018-23 TDS correction statement time-bar — the technical treatment of the 31 March 2027 permanent cliff
- The pre-cliff TDS backlog correction sprint — the seven-week week-by-week play
- The twelve-step Form 168 shortfall investigation — the illustrative Rs 1.69 lakh case walked end-to-end
- TDS correction return process — the C1 to C9 reference and the FVU workflow
- Form 141 unified challan-cum-statement — the specified-payment TDS successor from April 2026
- TDS payment codes 1001 to 1092 — the Section 393(1) cross-era mapping
Frequently Asked Questions
The original TDS return has been accepted. Can I still correct it?
Yes, provided the underlying financial year is not time-barred. The correction statement mechanism under Rule 31A allows a deductor to rectify a filed Form 24Q, Form 26Q, Form 27Q, or Form 27EQ at any time after the original acceptance — download the Conso file for the quarter from TRACES, apply the changes in NSDL RPU (Return Preparation Utility), validate through FVU (File Validation Utility), and upload the .fvu file as a correction against the original acknowledgement number. Processing takes three to seven business days on TRACES; Form 168 (the annual tax deduction statement introduced by the Income-tax Act 2025) updates once the correction is processed. The one hard boundary is the FY 2018-19 through FY 2022-23 permanent time-bar of 31 March 2027 — after that date, no correction statement can be filed for those five years and no condonation route exists under the Act.
I have a challan mismatch. Which correction type do I file?
C2 — the challan-detail correction. C2 updates the BSR code, the challan serial number, the challan date, or the challan amount for a payment linked to the statement. Use C2 when the deductor deposited the correct total but the statement quoted a wrong challan reference, when a challan was over-utilised across statements (the same challan linked to two quarters), or when the payment head is wrong (a 194J deposit tagged as 194C on the challan). C2 processing on TRACES also reconciles against the Government’s OLTAS (Online Tax Accounting System) record — a challan that does not exist in OLTAS is rejected outright, so verify the challan in the Government receipts register before filing the C2. The illustrative Rs 1,69,000 shortfall in Form 168 that reconciled entirely to a challan mis-tagging is a C2 case where the correction closes the gap without any additional tax deposit.
I missed adding a deductee row in the original return. Which correction type covers this?
C9 — the add-deductee correction. C9 lets you add a new deductee row against an existing challan already reported in the original statement (or against a challan added simultaneously in a C2 correction). The added row must fit within the unutilised balance of the challan; a C9 that would over-utilise the challan is rejected. If the challan is fully utilised in the original filing, a fresh challan deposit is needed before the C9 can be filed. The successor Form 168 for the deductee will reflect the added row three to seven business days after TRACES processing, and the deductee can then claim the corresponding TDS credit in their income tax return. This is the correction most often needed after a monthly close identifies a payment that was routed through AP without a TDS deduction entry — the deposit and the C9 close the gap together.
Does filing a correction after the deadline carry a penalty?
The correction itself does not carry a fresh penalty if the original return was filed on time — the Section 234E Rs 200 per day late-filing fee only applies to the delay in the original filing, not to subsequent corrections. Section 271H, however, does apply to incorrect information in a filed statement: a penalty between Rs 10,000 and Rs 1,00,000 that the Assessing Officer may direct. The Section 271H proviso protects the deductor if the tax with interest and Section 234E fee have been paid and the (correct) statement has been delivered within one year of the original due date — meaning a correction filed inside that one-year window is protected, and a correction filed beyond it is exposed. The Section 200A intimation that TRACES issues after processing a correction is where the Section 271H exposure surfaces if the correction is rejected on the first pass and the underlying gap remains open.
What actually happens to a FY 2018-19 correction after 31 March 2027?
It becomes impossible to file — the TRACES portal will not accept a correction statement dated after 31 March 2027 for any of the five financial years from FY 2018-19 to FY 2022-23. The CBDT-notified time-bar under Section 200(3) read with Rule 31A closes the correction window permanently, and no condonation of delay route exists under the Act for a Rule 31A correction (unlike, for example, the Section 119(2)(b) condonation available for delayed refund claims under Chapter XIX). The consequences are asymmetric: any TDS a deductor has deducted, deposited, and reported under the wrong PAN or against a mis-linked challan for those five years remains stuck in Form 168 mismatches that no future correction can resolve. For the deductee, the corresponding TDS credit in Form 26AS and Form 168 remains unclaimable — the amount is treated as a permanent write-off with no recovery route. This is the driver of the seven-week pre-cliff correction sprint that Indian finance teams run through the second half of FY 2026-27.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 200(3), Income-tax Act 1961 — Every person deducting tax at source shall, after paying the tax deducted to the credit of the Central Government within the prescribed time, prepare such statements for such period as may be prescribed and deliver or cause to be delivered to the prescribed income-tax authority or the person authorised by such authority such statement in such form and verified in such manner and setting forth such particulars and within such time as may be prescribed. The statute anchor for the quarterly TDS statements (Form 24Q, Form 26Q, Form 27Q, and Form 27EQ) and — read with Rule 31A — for the correction statement mechanism that allows a deductor to rectify a filed return. The correction window is not open in perpetuity; the CBDT-notified permanent time-bar for FY 2018-19 through FY 2022-23 corrections is 31 March 2027, after which the corrections become impossible with no condonation route inside the Act.
- ▸ Rule 31A, Income-tax Rules 1962 — Every person responsible for deduction of tax under Chapter XVII-B shall deliver, or cause to be delivered, quarterly statements to the Director General of Income-tax (Systems) in FORM No. 24Q (for salary), FORM No. 26Q (for non-salary payments other than to non-residents), FORM No. 27Q (for payments to non-residents), and FORM No. 27EQ (for tax collected at source under Section 206C). The rule further provides that the deductor may file a correction statement for rectification of any mistake in the original statement, and the correction statement must be delivered in the same form and manner. Corrections are typed C1 through C9 depending on the field being changed — C1 for deductee PAN, C2 for challan detail, C3 for deductee record, C4 for salary annexure in Form 24Q, C5 for statement cancellation, and C9 for adding a new deductee row against an existing challan.
- ▸ Section 234E, Income-tax Act 1961 — Without prejudice to the provisions of the Act, where a person fails to deliver or cause to be delivered a statement within the time prescribed in sub-section (3) of Section 200 or the proviso to sub-section (3) of Section 206C, he shall be liable to pay, by way of fee, a sum of two hundred rupees for every day during which the failure continues. The fee applies to late filing of the original return; a correction filed after the original due date does not itself attract Section 234E if the original was on time, but a first-time filing that arrives late as a correction against a placeholder return carries the full running Rs 200 per day counter capped at the TDS amount of the statement.
- ▸ Section 271H, Income-tax Act 1961 — Without prejudice to the provisions of the Act, the Assessing Officer may direct that a person who fails to deliver or cause to be delivered a statement within the time prescribed under sub-section (3) of Section 200 or the proviso to sub-section (3) of Section 206C, or furnishes incorrect information in the statement which is required to be delivered or caused to be delivered under sub-section (3) of Section 200 or the proviso to sub-section (3) of Section 206C, shall pay, by way of penalty, a sum which shall not be less than ten thousand rupees but which may extend to one lakh rupees. The proviso protects the deductor from Section 271H penalty if the tax deducted with interest and Section 234E fee have been paid to the Government and the statement has been delivered within one year of the original due date — the corollary being that a correction filed more than a year after the original due date is exposed to the full Section 271H ceiling.
- ▸ Section 200A, Income-tax Act 1961 — Where a statement of tax deduction at source or a correction statement has been made under Section 200 by a person deducting any sum, such statement shall be processed in the manner provided — the tax deductible, interest computable, fee under Section 234E chargeable, and any other adjustable amount shall be computed after making prima facie adjustments; an intimation shall be prepared or generated and sent to the person specifying the sum determined to be payable by, or the amount of refund due to, such person; and the intimation shall not be sent after the expiry of one year from the end of the financial year in which the statement is filed. The Section 200A intimation is what surfaces on TRACES after a correction is processed — a defensible correction closes the underlying gap; a mis-typed correction (C1 filed where C2 was needed, or vice versa) is rejected on processing and the intimation carries the shortfall forward with interest accruing.
- ▸ Section 393(1), Income-tax Act 2025 — The Income-tax Act 2025, effective 1 April 2026, consolidates the tax deduction and collection provisions of the Income-tax Act 1961 into Section 393. Every deduction leg reported in Form 26Q from Q1 FY 2026-27 onwards must carry the Section 393(1) payment code (for example code 1023 or 1024 for the Section 194C contractor payment leg, code 1027 for Section 194J professional fees, code 1031 for the Section 194Q purchase-of-goods deduction). A correction statement filed after 1 April 2026 for a legacy Section 194X deduction carries the Section 393(1) successor code — the substantive obligation is unchanged, but the coding on the correction has to migrate.