Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Five financial years — FY 2018-19, FY 2019-20, FY 2020-21, FY 2021-22, and FY 2022-23 — become permanently time-barred for TDS correction on 31 March 2026 under the Section 200 limitation notified by CBDT. A mid-market Indian finance team carrying an illustrative Rs 84 lakh cumulative TDS backlog spread across approximately 2,600 line items — Rs 68 lakh concentrated in FY 2018-19 alone — cannot rely on ad hoc corrections filed as time permits. The backlog carries Section 201(1A) interest at one and a half per cent per month on the amount-mismatch bucket, Section 206AA higher-rate exposure on the PAN-error bucket, Section 200A demand-notice exposure on the challan-mismatch bucket, and section-drift complications between legacy Section 194C, 194J, 194H, and 194I identifiers. Every line unfixed by 31 March 2026 becomes irreversible — Form 26AS credit denied, deductee-side under-credit at Section 143(1) processing, Section 40(a)(ia) disallowance for the underlying expense on the deductor side, and a controller-level Ind AS 37 provision on the residual.
Sequence the sprint across seven weeks with a specific closing state per week. Week 1 (Extract) — pull the consolidated challan status, deductee mismatch report, and historical Form 26Q and Form 27EQ filings from TRACES for each of the five financial years; open the sprint working paper folder. Week 2 (Categorise) — classify every line item into one of four fix types: challan mismatch (Section 200A anchor), PAN error (Section 206AA higher-rate anchor), amount mismatch (Section 201(1A) 1.5 per cent per month interest anchor), or section drift (legacy Section 194 identifier reclassification). Weeks 3 and 4 (File corrections) — file corrections in priority order of largest interest and demand exposure first, using Form 26Q correction for resident non-salary TDS, Form 27Q correction for non-resident TDS, and Form 27EQ correction for TCS lines, under Section 200 read with Rule 31A on the TRACES correction workflow. Weeks 5 and 6 (TRACES turnaround and rejection resolution) — absorb the 30-to-45-day TRACES processing window, triage every rejection within 48 hours by rejection reason, and refile with correction to challan status, PAN validation, or file schema as applicable. Week 7 (Sign-off) — controller review of the residual, categorisation into recoverable-and-provisioned versus non-recoverable-and-written-off, Ind AS 37 provision computed on the residual, and CFO sign-off on the Section 37 write-off versus Section 41 recovery decision for the non-recoverable bucket.
Sprint kickoff checklist opening in the second week of February — TRACES login credentials confirmed for the deductor account, sprint working paper folder opened, calendar block for the tax executive across all seven weeks, tax manager review sessions scheduled for the end of Weeks 2, 4, 6, and 7. Four-bucket categorisation template with columns for the deductor TAN, deductee PAN, quarter and financial year, section code, challan CIN, deduction amount, deposit amount, and fix type. Section 201(1A) interest calculator refreshed weekly during the sprint against the current proposed deposit date. Cross-era mapping reference — Section 194C to legacy code (and Section 393 code 1002 for context), Section 194J to legacy code (Section 393 code 1005 for context), Section 194H to legacy code (Section 393 code 1015 for context), Section 194I to legacy code (Section 393 code 1019 for context), Section 194Q to legacy code (Section 393 code 1031 for context). PAN validation utility integrated with the Income Tax Department's PAN validation status API to confirm Rule 114AAA inoperative status before every PAN-error correction. TRACES rejection tracker with columns for rejection reason, refile action required, refile owner, and refile due date.
By 31 March 2026, the sprint closes with three defensible outputs. First, a closed correction working paper for the five financial years with every corrected line item traced to a TRACES-accepted correction statement, a CIN reference, and a Form 26AS credit update. Second, an Ind AS 37 provision on the residual balance signed off by the controller, with the recoverable-and-provisioned bucket separated from the non-recoverable bucket, and the CFO decision on Section 37 write-off versus continued provisioning documented in the working paper. Third, a defensible audit trail for the statutory audit and for any subsequent Section 143(1) or Section 143(3) assessment on the deductee side or the deductor side, showing every correction filed, every rejection triaged, every refile pushed to acceptance, and every residual line reasoned to a provision or write-off with the applicable statute anchor.
The 31 March 2026 correction deadline for FY 2018-19 through FY 2022-23 TDS statements is the hardest deadline in the Indian tax calendar. Five financial years close to correction simultaneously under the Section 200 limitation notified by the CBDT, with no condonation provision available. A mid-market finance team looking at the TRACES portal in mid-February with an illustrative Rs 84 lakh cumulative backlog across approximately 2,600 line items — Rs 68 lakh concentrated in FY 2018-19 alone, Rs 5 lakh in FY 2019-20, Rs 2 lakh in FY 2020-21, Rs 1 lakh in FY 2021-22, and Rs 8 lakh in FY 2022-23 — has seven weeks. This is the sprint that runs against that clock.
The TDS reconciliation runbook is the preventive discipline that would have caught most of this backlog at monthly close. The TDS reconciliation failure modes article is the design layer that catalogues the fourteen ways the runbook can silently fail. This sprint is the recovery discipline when both were skipped for five consecutive years and the correction window is closing. It reads as a linear seven-week manual, but every week’s work maps back to a specific failure mode the design layer flagged as High Action Priority above the manual tolerance threshold.
Why the 31 March deadline is unforgiving
Section 200 read with Rule 31A of the Income-tax Rules 1962 requires every deductor to furnish quarterly TDS statements and permits correction statements within the applicable limitation window. The CBDT notified 31 March 2026 as the last date on which correction statements will be accepted through the TRACES portal for quarters of FY 2018-19 through FY 2022-23. Beyond that date, no correction is admissible for those five financial years, the credit position on Form 26AS becomes irreversible, and every consequence downstream — Form 26AS credit denied to the deductee, Section 40(a)(ia) disallowance for the underlying expense on the deductor side, Section 201(1A) interest continuing to accrue on the deductor’s unresolved default, and Section 143(1) intimation adjustments on both sides — becomes permanent.
There is no provision for condonation of delay for TDS correction statements under Section 200. The deadline is absolute and applies uniformly to all five financial years. The TDS correction statement article walks through the deadline mechanics in detail and confirms that FY 2023-24 and FY 2024-25 remain open under the applicable limitation period — only the five years covered by this sprint are closing simultaneously.
Seven weeks is the minimum defensible sequence. Compressing into fewer weeks collapses the TRACES processing window in Weeks 5 and 6 into a period where rejections cannot be refiled and corrected before the deadline closes. Starting later than the second week of February leaves the sprint colliding with year-end books close, GST annual return preparation, and Q4 GSTR-3B filings — the sprint gets deprioritised in favour of urgent statutory work and the deadline closes on unresolved lines. The sprint is a protected block on the tax executive’s calendar for the full seven weeks, with the tax manager reviewing at the end of Weeks 2, 4, 6, and 7 and the controller signing off in Week 7.
Week 1 — Extract every unresolved TDS demand from TRACES by financial year
Week 1 is not about correction. It is about extraction. The tax executive logs in to TRACES as the deductor and pulls three reports for each of the five financial years — the consolidated challan status under Statements or Payments, the deductee mismatch report under Defaults, and the historical Form 26Q filings quarter by quarter under the View Statement path. For entities with TCS liability, Form 27EQ filings are pulled from the corresponding TCS deductor login. Every report is filed in a dedicated sprint working paper folder with a filename that includes the financial year, the quarter, and the extraction date.
The extraction workload is deliberately front-loaded. Twenty quarters of filings across five financial years, cross-referenced against the deductor’s own challan register and the deductee mismatch reports, produces an aggregate line-item count that must be worked through in Week 2. Trying to categorise while extracting produces silent misses — a challan whose status is genuinely unmatched but which the extraction skipped, a deductee mismatch report where the entries were truncated because the pull returned only the top hundred rows without pagination.
Week 1 closes with an aggregate line-item count reconciled back to the TDS receivable aging workbook and the deductor’s own ledger, and a rough rupee-value distribution by financial year that confirms the exposure concentration. On the illustrative Rs 84 lakh backlog, the Rs 68 lakh concentration in FY 2018-19 is where the tax manager review at the end of Week 2 will focus the highest priority.
Week 2 — Categorise every line into one of four fix types
Week 2 splits the aggregate line-item count into four buckets. Each bucket carries a specific statute anchor and a specific correction pathway. The categorisation split governs the Weeks 3 and 4 filing priority.
Challan mismatch (Section 200A processing anchor). The BSR code, deposit date, or challan serial number was captured incorrectly on the return, and TRACES shows the challan as unmatched. The underlying tax was actually deposited — the challan reference just does not tie to the return. This bucket usually accounts for the largest share of line items but the smallest share of rupee value. The correction is a resubmission of the return with the corrected challan reference, filed under Section 200 read with Rule 31A on the TRACES correction workflow.
PAN error (Section 206AA anchor). The deductee’s PAN was miskeyed on the return, the credit did not land in the deductee’s Form 26AS, and the deductor is exposed to Section 206AA higher-rate liability if the corrected PAN turns out to be inoperative under Rule 114AAA. The correction requires PAN validation against the Income Tax Department’s current PAN status database before any correction statement is filed — a correction against an inoperative PAN will be rejected by TRACES because the Section 206AA higher-rate stands until the PAN is Aadhaar-linked and re-verified. Where the PAN is valid, the correction is a supplementary Form 26Q filing with the corrected PAN and, where the original deduction was at the higher twenty-per-cent rate, a supplementary challan for the shortfall between twenty per cent and the correct section rate.
Amount mismatch (Section 201(1A) interest anchor). The deduction on the return is less than the challan deposit, or the challan deposit is less than the deduction. The amount-mismatch bucket carries the largest interest exposure because Section 201(1A) accrues at one and a half per cent per month on the late-deposit leg from the original deduction date to the correction deposit date. On an illustrative Rs 68 lakh residual aged approximately eighty-four months to a March 2026 deposit, the after-interest exposure is material and is what forces the sprint sequence to run against the largest rupee-value lines first. The correction is a supplementary challan deposit with Section 201(1A) interest computed to the deposit date, filed alongside a corrected Form 26Q or Form 27EQ.
Section drift (legacy Section 194 identifier reclassification). A payment for manpower supply was booked under Section 194J at ten per cent when the correct legacy classification was Section 194C at one or two per cent by payee category. Or a rent payment was booked under Section 194I at ten per cent when the correct classification depended on the asset type. The correction is a Section 200 correction statement that reclassifies the section identifier, adjusts the rate accordingly, and files a supplementary challan for any shortfall or notes the excess deposit for refund reconciliation. Legacy Section 194 identifiers apply throughout — the Section 393 payment codes 1001 to 1092 introduced under the Income-tax Act 2025 apply only to payments made on or after 1 April 2026 and are relevant here only as a cross-reference the deductor’s current-year filings are already under. The cross-era TDS reconciliation article walks through the mapping in detail.
Week 2 closes with the tax manager reviewing the categorisation split, the priority sort for Weeks 3 and 4 confirmed, and the escalation path for any line item where the category is genuinely ambiguous.
Weeks 3 and 4 — File corrections in priority order
Weeks 3 and 4 are the filing weeks. The priority sort runs on financial exposure — amount mismatch first because of the Section 201(1A) interest exposure, PAN error second because of the Section 206AA higher-rate exposure, challan mismatch third because the underlying tax is already deposited, section drift fourth because it is the most complex to file cleanly. Within each category, the sort runs largest rupee-value first so the largest interest and demand exposures land in the correction queue with the maximum TRACES processing time inside the deadline.
Every correction is filed under Section 200 read with Rule 31A on the TRACES correction workflow. Form 26Q correction is used for resident non-salary TDS, Form 27Q correction for non-resident TDS, and Form 27EQ correction for TCS lines. The correction file is generated using the current TRACES File Validation Utility version to avoid schema-mismatch rejection in Weeks 5 and 6. Each correction file bundles the corrections for a single deductor TAN, a single financial year, and a single form type — mixing across forms or across years in a single file is a common source of rejection.
The per-correction fee under Section 234E — Rs 200 per day of delay in the original filing, capped at the tax deductible amount — applies where the original return was filed late. The Section 201(1A) interest computation refreshes weekly during the sprint against the current proposed deposit date; on a Rs 4 lakh amount-mismatch aged sixty-three months, the interest at one and a half per cent per month is Rs 4 lakh multiplied by one and a half per cent multiplied by sixty-three — approximately Rs 3,78,000 — payable alongside the supplementary challan.
The tax manager reviews the completed filings at the end of Week 4. Every line filed during Weeks 3 and 4 carries a submission reference, a filing date, and an expected TRACES processing date fifteen to twenty days later so the rejection resolution window in Weeks 5 and 6 has runway before 31 March. The Form 168 shortfall investigation article walks through the sibling investigation discipline for the current year and mirrors this priority sort for that surface.
Weeks 5 and 6 — TRACES turnaround and rejection resolution
TRACES typically processes a correction statement within 30 to 45 days of submission. Weeks 5 and 6 absorb the round-trip turnaround for the corrections filed in Weeks 3 and 4. The outcome — accepted, defective, or rejected — is visible on the TRACES deductor login and must be checked daily during these two weeks.
A rejection carries one of four common reasons. Challan unmatched — the underlying challan is still unmatched on the deductor’s TRACES account and the correction cannot map to a valid CIN. The refile requires the deductor to first resolve the challan status through the Track Correction Request workflow on TRACES before refiling. PAN inoperative under Rule 114AAA — the deductee PAN is still inoperative because Aadhaar linkage has not been completed, and the Section 206AA higher-rate correction cannot be reduced to the section-code rate. The refile requires the deductee to complete PAN-Aadhaar linkage and re-verification before the correction is admissible. Challan already consumed — the correction was filed against a challan that has already been consumed by an accepted correction in an earlier cycle. The refile requires reallocation of the challan credit across the underlying deductions and refile against a different challan reference. Schema validation failure — the correction file does not validate against the current TRACES upload version. The refile requires regeneration of the FVU using the current version of the utility.
Every rejection in Weeks 5 and 6 must be triaged within 48 hours of surfacing so the refile has processing time inside the 31 March deadline. Where a rejection is traceable to a deductor-side issue that the deductor has not resolved despite repeated follow-up, the deductor query letter pack — the chase-list activator built for exactly this situation — is used to escalate the follow-up through the standard deductor query letter templates with a compressed aging clock against the 31 March deadline.
The TRACES portal reconciliation article documents the correction workflow mechanics in detail and covers portal-side issues that can delay processing beyond the standard turnaround.
Week 7 — Controller sign-off and Ind AS 37 provision on the residual
Week 7 opens with the controller reviewing the closing state of the sprint. Every line item on the working paper is now in one of three states — corrected and accepted with a TRACES-accepted correction statement, corrected and pending final TRACES processing, or residual and unresolved. The residual bucket is where Week 7 spends its time.
The residual is analysed on two axes. First, recoverable versus non-recoverable. A residual where the deductor is contactable, the challan is matched on TRACES, and only the corrected filing is pending processing beyond 31 March is treated as recoverable but provisioned under Ind AS 37 for the timing exposure. A residual where the deductor is uncontactable, the deductee PAN remains inoperative, or the underlying tax was demonstrably not deposited by the deductor is treated as non-recoverable.
Second, for the non-recoverable bucket, the CFO decides between two accounting treatments. Write off in the current financial year as an allowable business loss under Section 37(1) of the Income-tax Act — the tax benefit crystallises immediately, but any subsequent recovery attracts Section 41 taxation as deemed income when the previously deducted amount is realised. Alternatively, hold as a full Ind AS 37 provision without a Section 37 write-off — the accounting reserve is created without a tax deduction, and any subsequent recovery is simply a reversal of the provision that stays outside the Section 41 net. The trade-off is between immediate tax benefit with future recovery risk on one side, and no immediate tax benefit with clean subsequent-recovery accounting on the other.
The Week 7 working paper documents both options with the tax exposure quantified both ways, and the CFO’s decision with the rationale. The controller signs off the sprint working paper and files it alongside the year-end audit file for statutory audit sampling. The Ind AS 37 provision quantum is the after-interest exposure computed under Section 201(1A) plus the recoverable-but-uncollected principal, discounted to present value where the resolution timeline exceeds twelve months.
The exception — if the sprint cannot close by 31 March
Where the seven-week sequence has been followed and a residual balance remains that cannot be corrected in time, the exception is not a failure of the sprint discipline — it is a design outcome the sprint anticipates. The four Weeks 5 and 6 rejection reasons that cannot be resolved before 31 March all resolve, at the residual date, into an accounting decision rather than a statutory correction. The Section 37 versus Section 41 decision is that accounting decision.
Where the seven-week sequence was not followed and the sprint reaches 31 March with categorisation incomplete, no correction filed, or no controller sign-off, the exception is more serious. Every unresolved line becomes a permanent Section 40(a)(ia) disallowance on the underlying expense (deductor side) and a permanent under-credit on Form 26AS (deductee side). The audit committee item is unavoidable, and the following financial year’s assessment cycle carries the full exposure. The design principle of the sprint is that the seven-week discipline is the only mechanism by which the 31 March deadline is genuinely met — an ad hoc filing plan across the same seven weeks produces a materially larger residual.
When the manual sprint outgrows itself
The seven-week sprint holds for a finance team running the cycle against a backlog of a few thousand line items across the five financial years, with a tax executive dedicated to the sprint for the full period. Above that, three specific manual controls break, and each one shows up as a rejection in Weeks 5 and 6 that consumes refile capacity the sprint cannot afford.
The Week 1 extraction across five financial years. Twenty quarters of Form 26Q filings, twenty quarters of Form 27EQ filings for entities with TCS liability, five financial years of consolidated challan status, and five financial years of deductee mismatch reports produce an extraction workload that cannot be completed manually inside a working week without silent misses when the deductee PAN counts run into the low thousands.
The Week 2 four-bucket categorisation. Simultaneous reference to the challan register, the PAN validation database, the challan-to-deduction map, and the cross-era section-to-code reference table for every line item on a spreadsheet produces silent misclassification at scale. Each misclassification during Weeks 3 and 4 produces a TRACES rejection during Weeks 5 and 6, and the refile capacity is finite.
The Section 201(1A) interest computation refreshed weekly on every open case. Keyed to the original deduction date, the current proposed deposit date, and the applicable one-and-a-half-per-cent-per-month rate across a large residual, this cannot be sustained on a spreadsheet without cumulative errors that skew the priority sort. A wrong priority sort in Weeks 3 and 4 lands the largest exposures late in the queue, and TRACES processing pushes the acceptance date past 31 March.
The response is not to accept these failure modes — the anchoring consequence is a permanent time-bar, and the exposure quantum on the illustrative Rs 84 lakh backlog does not survive a one-year sprint that missed. The response is to install a continuously refreshed correction and priority-sort layer that runs the extraction, the categorisation, and the interest computation as an operational function rather than a seven-week manual exercise. TransactIG reconciliation infrastructure delivers this layer as the TDS reconciliation software that mid-market Indian finance teams move to when the backlog stops fitting inside the manual sprint window.
Where this fits
- Reconciliation software India — pillar guide
- TDS reconciliation software India
- GST reconciliation software India
Related reading
- The reconciliation playbook — the twenty-day monthly close pillar
- TDS reconciliation runbook — the parent monthly-quarterly window
- TDS reconciliation failure modes — the design layer above this sprint
- TDS receivable aging workbook — the ledger the sprint draws from
- Deductor query letter pack — the chase-list activator for Weeks 5 and 6
- TDS correction statement — the March 31 2026 deadline explainer
- Cross-era TDS reconciliation — legacy Section 194 identifiers and codes 1001-1092
- TRACES portal reconciliation — the correction workflow reference
- Form 168 — the new TDS statement from FY 2026-27
- Form 168 shortfall investigation — the sibling triage article
- TDS demand notice reconciliation
- TDS credit recovery mechanisms
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 200 read with Rule 31A, Income-tax Act 1961 and Income-tax Rules 1962 (correction statement window) — Section 200 requires every deductor to furnish quarterly statements of tax deducted at source in the prescribed form and manner. Rule 31A prescribes Form 26Q for TDS on resident non-salary payments, Form 27Q for non-resident payments, and Form 27EQ for tax collected at source. A correction statement can be filed on the same form as the original within the limitation window applicable to the financial year to which the statement relates. The CBDT has notified 31 March 2026 as the last date on which correction statements will be accepted through the TRACES portal for quarters of FY 2018-19 through FY 2022-23. Beyond that date, no correction is admissible for those five financial years and the credit position on Form 26AS becomes irreversible.
- ▸ Section 201(1A), Income-tax Act 1961 — Interest on failure to deduct or deposit tax. Where a person responsible for deducting tax fails to deduct or, after deduction, fails to pay the whole or any part of the tax as required, that person shall be liable to pay simple interest at one per cent per month or part thereof from the date on which the tax was deductible to the date on which the tax is deducted, and at one and a half per cent per month or part thereof from the date on which the tax was deducted to the date on which it is actually paid. Every amount mismatch corrected during the sprint carries a Section 201(1A) interest exposure computed month by month from the original deduction date to the correction deposit date. On an illustrative Rs 68 lakh FY 2018-19 residual aged approximately eighty-four months to a March 2026 deposit, the exposure at the one-and-a-half-per-cent leg is material and is what forces the sprint sequence to run against the largest financial exposure first.
- ▸ Section 206AA, Income-tax Act 1961 — Requirement to furnish Permanent Account Number. Where the deductee does not furnish a valid PAN, or the PAN furnished is invalid, inoperative under Rule 114AAA, or does not match the Income Tax Department's PAN database, the deductor is required to deduct tax at the higher of the rate specified in the relevant provision or twenty per cent. A correction statement resolving a Section 206AA higher-rate deduction requires the deductor to file a supplementary challan for the shortfall between the correct section-code rate and the earlier twenty-per-cent deduction, and to file a corrected Form 26Q reflecting the deductee's now-valid PAN. Where the PAN remains inoperative at the correction date, the twenty-per-cent deduction stands and no supplementary challan is admissible.
- ▸ Section 200A, Income-tax Act 1961 (processing of TDS statements) — The Central Processing Centre for TDS processes every quarterly TDS statement on receipt, computes short deduction, short payment, interest under Section 201(1A), and Section 234E late-filing fee, and issues an intimation of demand where applicable. A challan mismatch, a wrong section code, or an amount mismatch surfaced during the correction sprint attracts fresh Section 200A processing on the corrected statement — the sprint therefore closes not only the deductee's TDS credit position but also the deductor's own Section 200A intimation exposure for the five financial years covered.
- ▸ Section 393 payment codes 1001 to 1092, Income-tax Act 2025 (cross-era reference) — The Section 393 payment code schedule under the Income-tax Act 2025 consolidates every non-salary TDS-attracting transaction into a four-digit payment code from 1001 to 1092 for payments made on or after 1 April 2026. FY 2018-19 through FY 2022-23 payments continue to reference the legacy Section 194-series identifiers — 194C for contractor payments, 194J for fees for professional or technical services, 194H for commission and brokerage, 194I for rent, 194Q for purchase of goods above the threshold. Section drift corrections during the sprint therefore work in the legacy identifier space, with the cross-era mapping table (Section 194C to code 1002, Section 194J to code 1005) held only as a reference for teams that need to explain the correction to a deductor whose current-year filing is under the new codes.
- ▸ Ind AS 37 — Provisions, Contingent Liabilities and Contingent Assets — Ind AS 37 requires a provision to be recognised when an entity has a present obligation as a result of a past event, it is probable that an outflow of resources embodying economic benefits will be required to settle the obligation, and a reliable estimate can be made of the amount of the obligation. Where the seven-week sprint closes with a residual unrecoverable balance — corrections that TRACES rejected, deductors uncontactable, or PANs permanently inoperative — the residual is provided under Ind AS 37 with controller sign-off. The provision quantum is the after-interest exposure computed under Section 201(1A) plus the recoverable-but-uncollected principal, discounted to present value where the resolution timeline exceeds twelve months.
- ▸ CBDT Notification for TDS correction statement — 31 March 2026 deadline for FY 2018-19 through FY 2022-23 — The CBDT notified 31 March 2026 as the last date for filing TDS correction statements for quarters of FY 2018-19, FY 2019-20, FY 2020-21, FY 2021-22, and FY 2022-23. The deadline is absolute — there is no provision for condonation of delay for TDS correction statements under Section 200 read with Rule 31A. FY 2023-24 and FY 2024-25 correction windows remain open under the applicable limitation period; only the five years from FY 2018-19 through FY 2022-23 are closing simultaneously on 31 March 2026.