The Deductor Query Playbook: Letter Templates for Form 168 Mismatch and TDS Credit Recovery

The quarterly Form 168 pull is complete, the TDS reconciliation runbook closed its Day 10 exception categorisation, and one deductor’s Rs 84,200 deduction on a Rs 8,42,000 Section 194J code 1005 professional-fee invoice is missing from the deductor’s Form 168 filing for the quarter. The bank credit for the net Rs 7,57,800 landed on the expected date, the invoice is closed, and the deductor’s accounts contact confirmed by email that the payment was made TDS-net. But the Form 168 credit is missing, and the annual tax filing for the deductee cannot claim credit for a deduction that does not appear on the deductee’s TRACES account. This is the five-letter escalation ladder — Level 1 polite query through Level 5 statutory-auditor escalation — that Indian tax teams run against every unresolved Form 168 shortfall, with the CGST-Act, Income-tax-Act-2025, and CARO 2020 anchor for each level.

The TDS reconciliation failure modes article documents the failure surfaces this ladder patches after the fact. The Form 168 shortfall investigation article documents the pre-letter triage — root-cause classification of the shortfall into a PAN mismatch bucket, a payment code drift bucket, a challan-to-return mismatch bucket, or a genuine short-deduction bucket. This article assumes the triage is complete and the shortfall has been isolated to a deductor bookkeeping or short-deduction cause; the letter pack is what runs from there.

Why five levels rather than a single legal notice

A legal notice as the first communication forecloses the correction workflow that would restore the credit at no cost to either party. Form 168 shortfalls on bona fide invoices are, in the majority of cases, a deductor bookkeeping issue rather than a deliberate non-deposit. The four common causes route to different correction pathways.

PAN mismatch under Section 206AA. The deductor’s onboarding record carries a PAN that has since been invalidated on the Income Tax Department database, or the PAN was miskeyed at onboarding, and the Form 168 filing is either missing the deductee entirely or is credited at a twenty per cent higher rate that does not match the deductee’s contract rate. The correction is a PAN update on the deductor’s records and a supplementary Form 168 filing.

Payment code drift. The deductor booked a Section 194J code 1005 professional-services deduction against a Section 194C code 1002 contractor line, or the deductor’s ERP is on a stale Section 393 payment code reference table and posted the deduction against a superseded code. The Form 168 filing reflects the wrong code, and the deductee’s ledger match against the expected code returns no result. The correction is a Section 154 read with Section 200A correction statement filed by the deductor.

Challan-to-return mismatch. The deductor deposited the challan for the aggregate quarterly deduction but the Form 168 filing missed one deductee-invoice combination in the return schema. The correction is a supplementary Form 168 filing addressed against the challan reference already on TRACES.

Genuine short-deduction or non-deposit. The deductor deducted the amount from the payment to the deductee but did not deposit the challan for that amount, or deducted less than the invoice entitled the deductee to. The correction is a supplementary challan deposit with Section 201(1A) interest at one and a half per cent per month, filed alongside a corrected Form 168.

Levels 1 and 2 of the letter ladder are designed to trigger the correction on the first three causes without any commercial escalation. Levels 3 and 4 are for the fourth cause, and for the residual cases where the deductor is not responsive to the polite ask. Level 5 is the governance channel — the deductor’s statutory auditor under CARO 2020 clause (i) — for the residual cases where the deductor is a corporate entity and the shortfall has aged past the operational recovery window. Every level up the ladder narrows the deductor’s cost-free recovery options and shifts the disclosure exposure; the escalation itself is the discipline that produces the correction.

The compliance calendar that anchors the ladder

Two dates give the ladder its urgency and its cadence.

The Form 168 filing due date — thirtieth day after each quarter-end. Rule 31A of the Income-tax Rules 2025 requires every deductor to file the quarterly Form 168 within thirty days of the end of each quarter. A missing Form 168 credit is not conclusive evidence of a shortfall until this thirty-day window has closed for the quarter — a deductee ledger review conducted immediately after quarter-end will surface a large volume of “missing” credits that are simply not yet filed. Level 1 letters are held until the thirtieth day has passed and the deductor’s return has been processed on TRACES.

The March 31 correction 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 the five financial years covered. Beyond this date, no correction will be accepted through the TRACES portal for those years, and the credit position on Form 26AS (or Form 168 for the transitional-year portion) becomes irreversible. Level 3 letters — the request to file a correction statement before the deadline — are time-boxed against this date. The TDS correction statement article walks through the deadline mechanics in detail.

Level 1 — the polite query letter (issued T+0 from discovery)

Level 1 goes out immediately on the Day 10 exception categorisation that flagged the Form 168 shortfall. The tax executive drafts and sends it to the deductor’s accounts contact of record; the tax manager is copied. The letter carries the invoice reference, the payment date, the expected payment code, the expected deduction amount, and a request for the deductor to either confirm the correction filing or explain the absence.

Statute anchor. Section 393 Income-tax Act 2025 (payment code 1005 for fees for professional or technical services, standard rate ten per cent on the gross exclusive of GST per Circular 23/2017); Rule 31A quarterly Form 168 filing due date.

Illustrative rupee figure. Rs 8,42,000 gross professional-services invoice; ten per cent Section 194J code 1005 deduction of Rs 84,200; net remittance Rs 7,57,800. Working paper to replace with the actual invoice and deduction from the deductee ledger.

Template — Level 1 polite query letter:

[Customise before sending. Replace all placeholder brackets with the working-paper values, verify Section 197 certificate register and Section 206AA PAN status on the deductor’s records before issue, and confirm the Form 168 filing due date for the quarter has passed.]

To: [DEDUCTOR NAME], [DEDUCTOR ACCOUNTS CONTACT NAME] Cc: [DEDUCTOR CFO NAME] From: [DEDUCTEE COMPANY NAME], [DEDUCTEE FINANCE HEAD NAME] Date: [DATE OF ISSUE] Subject: Query on Form 168 credit for [QUARTER, e.g. Q1 FY 2026-27] — Invoice [INVOICE NUMBER]

Dear [DEDUCTOR ACCOUNTS CONTACT NAME],

This is in reference to our invoice [INVOICE NUMBER] dated [INVOICE DATE] raised on your company for professional services rendered, of a gross value of Rs 8,42,000 exclusive of applicable GST. The payment was received on [PAYMENT DATE] as a net remittance of Rs 7,57,800, reflecting a TDS deduction of Rs 84,200 at ten per cent under Section 393 payment code 1005 (successor to Section 194J for fees for professional or technical services).

On our review of the quarterly Form 168 filed by your organisation for [QUARTER] and reflected on our TRACES account, we are unable to trace a credit corresponding to the Rs 84,200 deduction referenced above. Our records against this deduction — the invoice reference, the payment date, the payment code, and the gross and net amounts — are set out in the enclosed working paper.

We would be grateful if you would confirm the following at your earliest convenience:

1. The challan reference (CIN) under which the Rs 84,200 was deposited;
2. The payment code (1005 or otherwise) against which the deduction was booked on your Form 168 filing;
3. Whether a corrected Form 168 filing addressing this deduction is planned within the current quarter.

Please treat this as a routine reconciliation query. If the deduction has been reported under a different payment code or against a different quarter, a note to that effect will allow us to update our records. If a Form 168 correction is pending, an indication of the expected filing date will allow us to schedule our quarterly review accordingly.

Thank you for your assistance.

Yours sincerely, [DEDUCTEE FINANCE HEAD NAME] [DEDUCTEE COMPANY NAME]

Enclosure: Reconciliation working paper (invoice, payment, expected TDS particulars).

Owner. Tax executive drafts, tax manager reviews before send.

Next action if no response by T+30. Escalate to Level 2.

Level 2 — request for corrected Form 131 quarterly certificate (issued T+30)

Level 2 is a formal request for the deductor to issue the Form 131 quarterly TDS certificate reflecting the missing credit. Rule 31A requires the deductor to issue a Form 131 to every deductee whose PAN is reflected in the Form 168 filing within fifteen days of the Form 168 due date. The Level 2 letter addresses the deductor’s CFO by name and requests the corrected certificate under the Rule 31A obligation.

Statute anchor. Rule 31A Income-tax Rules 2025 (Form 131 quarterly certificate issuance obligation); Section 200(3) Income-tax Act 2025 (deductor’s obligation to furnish the quarterly TDS statement); the sixty-day operational window that CBDT publishes for a deductor to file a correction statement following the original quarterly filing due date.

Template — Level 2 formal Form 131 request:

[Customise before sending. Confirm Level 1 was sent and has aged thirty days without a substantive response.]

To: [DEDUCTOR CFO NAME] Cc: [DEDUCTOR ACCOUNTS CONTACT NAME], [DEDUCTOR STATUTORY AUDITOR NAME (for records)] From: [DEDUCTEE COMPANY NAME], [DEDUCTEE FINANCE HEAD NAME] Date: [DATE OF ISSUE] Subject: Formal request for corrected Form 131 — Invoice [INVOICE NUMBER], [QUARTER]

Dear [DEDUCTOR CFO NAME],

Further to our query letter dated [LEVEL 1 DATE] (copy enclosed), addressed to [DEDUCTOR ACCOUNTS CONTACT NAME] and not yet substantively addressed, we write formally to request the issuance of a corrected Form 131 quarterly TDS certificate for [QUARTER FY 2026-27] reflecting the deduction of Rs 84,200 made against our invoice [INVOICE NUMBER] of Rs 8,42,000 gross exclusive of GST.

Under Rule 31A of the Income-tax Rules 2025, your organisation is required to furnish the quarterly Form 168 statement within thirty days of the end of each quarter, and to issue a Form 131 certificate to every deductee reflected in the Form 168 within fifteen days of the Form 168 due date. Our review of the Form 168 credited to our TRACES account for [QUARTER] does not reflect the Rs 84,200 deduction, and no Form 131 has been received against this deduction.

Please treat this as a formal request under Rule 31A for the following:

1. If the deduction has been reported on the Form 168 under a different reference (payment code, deductee identifier, or challan mapping), please issue the Form 131 with the corrected reference within fifteen days of the date of this letter;
2. If the deduction has not been reported on the Form 168 for [QUARTER], please file the correction statement under the CBDT-notified sixty-day correction window from the original quarterly filing due date and issue the Form 131 following the correction;
3. If neither has been done and neither is planned, please confirm the status by written reply so that we may consider the appropriate next step under our audit and reconciliation controls.

The absence of this credit on our TRACES account will otherwise prevent our organisation from claiming credit for this deduction against our annual tax liability, and the reconciliation position will be carried forward for external audit review.

Yours sincerely, [DEDUCTEE FINANCE HEAD NAME] [DEDUCTEE COMPANY NAME]

Enclosures: (1) Reconciliation working paper; (2) Copy of Level 1 query letter dated [LEVEL 1 DATE].

Owner. Tax executive drafts, tax manager signs.

Next action if no correction filed by T+60. Escalate to Level 3 (if the affected quarter belongs to FY 2018-19 through FY 2022-23 and the March 31 correction deadline is approaching) or continue directly to Level 4 (if the affected quarter is a recent FY 2026-27 or later quarter with an ordinary correction window still open).

Level 3 — request to file correction statement before March 31 deadline (issued in Q3 of the financial year)

Level 3 is triggered by the March 31 correction deadline for FY 2018-19 through FY 2022-23 residuals. The letter is time-boxed to October or November of the financial year, so the deductor’s tax team has four to five months to file the correction, receive TRACES processing feedback, and address any rejection before the deadline closes. A Level 3 letter issued in February or March technically qualifies but leaves no operational runway; where the aging clock has slipped that far, the ladder moves directly to Level 4.

Statute anchor. Section 200A read with Section 154 Income-tax Act 2025 (correction statement processing framework); CBDT notification of 31 March 2026 as the last date for filing TDS correction statements for FY 2018-19 through FY 2022-23; the irreversibility of the credit position on Form 26AS for those years beyond the deadline.

Template — Level 3 correction statement request:

[Customise before sending. Confirm the affected quarter belongs to FY 2018-19 through FY 2022-23. Confirm current date is within Q3 of the financial year (October-November) to leave at least four months operational runway before 31 March 2026.]

To: [DEDUCTOR CFO NAME] Cc: [DEDUCTOR HEAD OF TAX NAME], [DEDUCTOR STATUTORY AUDITOR NAME] From: [DEDUCTEE COMPANY NAME], [DEDUCTEE FINANCE HEAD NAME] Date: [DATE OF ISSUE — October or November preceding March 31] Subject: Request to file correction statement before 31 March 2026 — Invoice [INVOICE NUMBER], [QUARTER OF FY 2018-19 THROUGH FY 2022-23]

Dear [DEDUCTOR CFO NAME],

Further to our formal request dated [LEVEL 2 DATE] (copy enclosed), regarding the Form 131 quarterly TDS certificate for the Rs 84,200 deduction made against our invoice [INVOICE NUMBER] for [QUARTER OF FY 2018-19 THROUGH FY 2022-23], we write to request that your organisation file the appropriate correction statement on the TRACES portal before 31 March 2026.

The Central Board of Direct Taxes has notified 31 March 2026 as the last date for filing TDS correction statements for quarters of FY 2018-19 through FY 2022-23. Beyond this date, no correction statement will be accepted through the TRACES portal for the five financial years covered, and the credit position on Form 26AS for those years will become irreversible.

We write in October / November to allow your tax team four to five months of operational runway to complete the following:

1. File the correction statement addressing the Rs 84,200 deduction for [QUARTER OF FY 2018-19 THROUGH FY 2022-23] against our PAN [DEDUCTEE PAN] under the payment code (or legacy section code) applicable to the original deduction;
2. Address any TRACES rejection or processing objection that may arise from the correction submission;
3. Issue the corresponding corrected Form 131 to our organisation.

The correction is processed under Section 200A read with Section 154 of the Income-tax Act 2025 and does not attract penalty when filed voluntarily within the CBDT-notified window. Failure to file the correction before 31 March 2026 will render the credit permanently unavailable on our records, and we will be constrained to record the resulting shortfall as a commercial receivable for direct recovery under separate correspondence.

Please confirm your organisation’s intent to file the correction, and a target filing date, by [RESPONSE DEADLINE — thirty days from date of issue].

Yours sincerely, [DEDUCTEE FINANCE HEAD NAME] [DEDUCTEE COMPANY NAME]

Enclosures: (1) Reconciliation working paper; (2) Copy of Level 2 letter dated [LEVEL 2 DATE]; (3) Extract of CBDT notification setting 31 March 2026 correction deadline.

Owner. Tax manager drafts and signs, controller reviews before send.

Next action if no correction filed by 15 December preceding March 31. Escalate to Level 4.

Level 4 — commercial recovery demand for shortfall plus Section 201(1A) interest (issued T+90 from Level 1, or T+30 from Level 3 with no correction filed)

Level 4 shifts the correspondence from a tax-workflow request to a commercial recovery demand. The letter demands direct payment of the shortfall principal plus accrued Section 201(1A) interest at one and a half per cent per month from the original deduction date.

Statute anchor. Section 201(1A) Income-tax Act 2025 (interest on late deposit at one and a half per cent per month); Section 200A (assessee-in-default liability where TDS is deducted but not deposited); Section 234E fee at Rs 200 per day for delay in filing the TDS statement; the deductor’s contractual obligation to make good the deducted-but-unpaid amount as a commercial matter.

Illustrative rupee figure. Shortfall principal Rs 84,200; aged six months from original deduction date; Section 201(1A) interest = Rs 84,200 × 1.5% × 6 = Rs 7,578; total demand Rs 91,778 payable within the letter’s stated window.

Template — Level 4 commercial recovery demand:

[Customise before sending. Refresh Section 201(1A) interest to the current computation date. Confirm Levels 1 through 3 (or 1 through 2 for recent-year residuals) have been sent and are documented.]

To: [DEDUCTOR CEO NAME] / [DEDUCTOR MANAGING DIRECTOR NAME] Cc: [DEDUCTOR CFO NAME], [DEDUCTOR HEAD OF TAX NAME] From: [DEDUCTEE COMPANY NAME], [DEDUCTEE FINANCE HEAD NAME] Date: [DATE OF ISSUE] Subject: Commercial recovery demand — TDS shortfall Rs 84,200 plus Section 201(1A) interest — Invoice [INVOICE NUMBER]

Dear [DEDUCTOR CEO NAME],

Our correspondence dated [LEVEL 1 DATE], [LEVEL 2 DATE], and [LEVEL 3 DATE] (copies enclosed) regarding the Form 168 credit for the Rs 84,200 TDS deduction made against our invoice [INVOICE NUMBER] of Rs 8,42,000 gross exclusive of GST has not produced a corrected Form 168 filing, a corrected Form 131 certificate, or a filed correction statement addressing the shortfall.

The deduction of Rs 84,200 was made from the payment to our organisation. That amount, having been deducted, was required to be deposited to the credit of the Central Government by your organisation on or before the seventh of the month following the deduction, and reported in the Form 168 for [QUARTER]. The absence of the credit on our TRACES account, and the absence of a corrected Form 131 in our records, indicate that the deducted amount has either not been deposited or has not been correctly reported.

We accordingly demand direct payment of the following as a commercial recovery:

1. Principal shortfall: Rs 84,200 (deducted from payment against invoice [INVOICE NUMBER] and not reflected as a credit on our TRACES account);
2. Interest under Section 201(1A) at one and a half per cent per month from [ORIGINAL DEDUCTION DATE] to [DATE OF THIS LETTER], calculated as Rs 84,200 multiplied by one and a half per cent multiplied by [MONTHS ELAPSED] = Rs [INTEREST AMOUNT];
3. Total demand: Rs [PRINCIPAL PLUS INTEREST].

Payment is to be made by NEFT / RTGS to our account [BANK ACCOUNT DETAILS] within thirty days of the date of this letter. In the event that the shortfall is resolved by way of a corrected Form 168 filing and a valid Form 131 certificate issued to our organisation within the same thirty-day window, the demand for direct commercial recovery will be withdrawn against confirmation of the credit on our TRACES account.

The Section 201(1A) interest continues to accrue against your organisation until the shortfall is either deposited to the credit of the Central Government or paid directly to our organisation. Failure to respond to this demand within thirty days will result in escalation of this matter to the statutory auditor of your organisation under the CARO 2020 reporting framework, followed by consideration of legal remedies available to our organisation.

Yours sincerely, [DEDUCTEE FINANCE HEAD NAME] [DEDUCTEE COMPANY NAME]

Enclosures: (1) Reconciliation working paper with Section 201(1A) interest computation; (2) Copies of Level 1, Level 2, and Level 3 correspondence.

Owner. Tax manager drafts, controller signs.

Next action if no payment or correction by T+150 from Level 1. Escalate to Level 5 (if the deductor is a corporate entity subject to CARO 2020) or refer to legal for a pre-suit notice (if the deductor entity type does not attract CARO 2020).

Level 5 — escalation to the deductor’s statutory auditor (issued T+150 from Level 1)

Level 5 is the governance channel. The Companies (Auditor’s Report) Order 2020 clause (i) requires the statutory auditor of every company (subject to specified exclusions) to report on the regularity of the company’s deposit of statutory dues, including tax deducted at source. A Level 5 letter to the deductor’s statutory auditor with the full reconciliation and Levels 1 through 4 correspondence attached puts the shortfall on the deductor’s audit committee’s desk through the annual CARO reporting cycle.

Statute anchor. CARO 2020 clause (i) (statutory auditor’s duty to report on regularity of TDS deposit); the Companies Act 2013 audit framework under which the deductor’s board and audit committee receive the CARO annexure.

Applicability check before send. Level 5 is appropriate only where the deductor is a company subject to CARO 2020 — corporates and larger private limited companies are covered; small companies, one-person companies below thresholds, and specifically excluded categories are not. For deductors outside CARO 2020, the ladder stops at Level 4 and the residual is settled through commercial recovery or controller-approved write-off.

Template — Level 5 statutory auditor escalation:

[Customise before sending. Confirm deductor is a company subject to CARO 2020. Confirm the deductor’s statutory auditor name and firm from the deductor’s public disclosures (annual report, ROC filings) — never rely on the deductor’s own accounts contact for the auditor identification.]

To: [DEDUCTOR STATUTORY AUDITOR FIRM NAME], [DEDUCTOR STATUTORY AUDITOR PARTNER NAME] Cc: [DEDUCTOR CEO NAME], [DEDUCTOR CFO NAME], [DEDUCTOR AUDIT COMMITTEE CHAIR NAME] From: [DEDUCTEE COMPANY NAME], [DEDUCTEE FINANCE HEAD NAME] Date: [DATE OF ISSUE] Subject: Notification of unresolved TDS shortfall for CARO 2020 clause (i) consideration — [DEDUCTOR NAME] FY [YEAR UNDER AUDIT]

Dear [DEDUCTOR STATUTORY AUDITOR PARTNER NAME],

We write in your capacity as the statutory auditor of [DEDUCTOR NAME] for FY [YEAR UNDER AUDIT] to bring to your attention an unresolved TDS shortfall that our organisation has been unable to recover through direct correspondence with [DEDUCTOR NAME] over the past five months.

The details are as follows:

1. Invoice reference: [INVOICE NUMBER], dated [INVOICE DATE], raised on [DEDUCTOR NAME];
2. Gross invoice value: Rs 8,42,000 exclusive of GST, professional services under Section 393 payment code 1005 (successor to Section 194J);
3. TDS deduction at ten per cent: Rs 84,200;
4. Net remittance received: Rs 7,57,800 on [PAYMENT DATE];
5. Form 168 credit reflected on TRACES for [QUARTER]: Nil against this deduction;
6. Form 131 certificate received from [DEDUCTOR NAME]: Nil against this deduction;
7. Accrued Section 201(1A) interest at one and a half per cent per month from [ORIGINAL DEDUCTION DATE] to date: Rs [INTEREST AMOUNT];
8. Total shortfall: Rs [PRINCIPAL PLUS INTEREST].

Our correspondence with [DEDUCTOR NAME] on this matter is enclosed — the polite query letter of [LEVEL 1 DATE], the formal Form 131 request of [LEVEL 2 DATE], the correction statement request of [LEVEL 3 DATE], and the commercial recovery demand of [LEVEL 4 DATE]. No corrected Form 168 filing has been made, no correction statement has been filed on TRACES, no Form 131 has been issued, and no commercial recovery payment has been received.

We bring this matter to your attention in the context of clause (i) of Paragraph 3 of the Companies (Auditor’s Report) Order 2020, which requires the statutory auditor to report on the regularity of the company’s deposit of statutory dues, including tax deducted at source. Our reconciliation supports a conclusion that the Rs 84,200 deduction has either not been deposited to the credit of the Central Government or has not been correctly reported on the quarterly Form 168 filing for [QUARTER], and that this is one deductee’s experience among what may be a larger set of comparable cases in the [DEDUCTOR NAME] deductee base.

We respectfully request that this matter be considered in the CARO annexure to your audit report for [DEDUCTOR NAME] for FY [YEAR UNDER AUDIT], to the extent your independent examination of the underlying records supports the reconciliation position we have set out. Our reconciliation working paper and the underlying invoice, payment, and TRACES documentation are enclosed for your review.

We are copying [DEDUCTOR NAME]‘s Chief Executive Officer, Chief Financial Officer, and Audit Committee Chair on this letter so that the matter is before the deductor’s board and audit committee through the appropriate governance channel.

Yours sincerely, [DEDUCTEE FINANCE HEAD NAME] [DEDUCTEE COMPANY NAME]

Enclosures: (1) Reconciliation working paper with Section 201(1A) interest computation; (2) Copies of Levels 1 through 4 correspondence; (3) Invoice, payment, and TRACES documentation supporting the shortfall.

Owner. Controller signs; CFO consulted on send decision because the letter goes to a third-party audit firm and enters the deductor’s governance record.

Next action after Level 5. Await CARO reporting cycle outcome; refer to legal for a pre-suit notice if commercial recovery remains outstanding after the deductor’s audit report for the year is filed.

The five-letter Word template pack

The five templates above are maintained in a controlled folder as customisable Word documents. Placeholder counterparties, illustrative rupee figures, and customise-before-sending markers are set at the top of every letter — every send is preceded by a substitution pass against the working-paper values and a Section 197 / Section 206AA / CARO 2020 applicability check.

The pack is available for download at the deductor Form 168 query letter pack landing page, alongside the reconciliation working paper template and the Section 201(1A) interest calculator. The download is a bundled asset — no email gate on the letter templates individually.

When the manual five-letter ladder outgrows itself

The ladder holds for a finance team that runs it against a receivable ledger of a few hundred deductor entries a quarter and can dedicate a tax analyst two to three days a month to escalation correspondence. Above that, three specific manual controls break, and the TDS reconciliation failure modes article rates each as a mode above the manual tolerance threshold.

Aging-clock drift across five levels. Level 1 aged thirty days to Level 2, Level 2 aged sixty days from Level 1 to Level 3 or 4 depending on year vintage, Level 4 aged ninety days from Level 1 to Level 5. Maintaining the discipline across a few hundred deductors without silent slippage is where the spreadsheet stops keeping up — the receivable ledger accumulates rows where Level 1 went out but Level 2 was never triggered, or Level 4 was issued without the Section 201(1A) interest being refreshed to the current computation date.

Section 201(1A) interest computation refresh. Every escalating case carries an interest number that must be refreshed monthly against the original deduction date. Manual maintenance across a growing ledger produces cumulative errors in the demand computation and undermines the letter’s credibility with the deductor.

Letter customisation without template drift. Every letter carries the invoice reference, the payment code, the expected TDS, the accrued interest, and the correction deadline. Manual per-case generation across a few hundred deductors without a controlled template system introduces drift — the letter that goes out at Level 4 no longer matches the reconciliation working paper because the interest number was last refreshed six weeks ago.

The response is not to accept these failure modes — the escalation ladder exists precisely because the alternative is either premature legal notice or silent aging into a write-off. The response is to install a continuously refreshed detection and correspondence layer that runs the aging queue, the interest recompute, and the template merge as a routine background function. Terra Insight’s TransactIG delivers this correspondence surface as the queue the ladder otherwise cannot maintain, and Terra Insight’s TDS reconciliation software surfaces the shortfalls the ladder was designed to address.

Where this fits

• TransactIG — reconciliation infrastructure
• Reconciliation software India — pillar guide
• TDS reconciliation software India
• GST reconciliation software India

Related reading

• The reconciliation playbook — monthly close pillar
• TDS reconciliation runbook — monthly and quarterly (parent for this letter pack)
• TDS reconciliation failure modes — the design layer this ladder patches
• Form 168 shortfall investigation — the pre-letter triage article
• TDS receivable aging workbook — the ledger these letters draw from
• Form 168 — the new quarterly TDS statement
• Form 131 quarterly TDS certificate
• Section 393 payment codes 1001 to 1092
• Cross-era TDS reconciliation
• TDS correction statement — March 31 2026 deadline
• TDS demand notice reconciliation — Section 200A processing
• TDS credit recovery mechanisms
• Section 206AB and 206CCA higher-rate deductions

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 6 August 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024