Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian services businesses with significant TDS-bearing revenue silently lose 8 to 14% of TDS credits because the deductor never filed, used the wrong PAN, used the wrong section code, used the wrong period, or filed past the deductee's rectification window. The cross-era complication of FY26 spanning legacy Section 194x and new Section 393 / 394 payment-code 1001-1092 makes the reconciliation harder. Books-side TDS receivable shows a number, but Form 26AS plus Form 168 together show less, and the gap is the leakage.
Maintain a TDS receivable register keyed by customer PAN, deductor TAN, invoice number, gross taxable amount, contracted TDS rate, deduction date, and expected payment code 1001-1092 plus legacy 194x reference. Daily-pull Form 26AS and Form 168 for the deductee PAN across all relevant assessment periods. Match each books-receivable to the 26AS / 168 entry by PAN, period, payment code, and amount. Age every unmatched receivable in 30 / 60 / 90 / 180-day buckets. Map each bucket to a specific recovery action (deductor confirmation, escalation, rectification filing via Form 131 or Form 141).
TDS receivable ledger with deductor TAN, deductee PAN, invoice reference, deduction date, payment code 1001-1092, cross-era 194x reference, contracted rate. Daily 26AS / 168 pull pipeline against deductee PAN. Match-engine rules with PAN-period-amount-code primary keys and amount-fuzzy fallback. Ageing buckets 30 / 60 / 90 / 180 days. Action playbook by bucket. Rectification queue feeding Form 131 / Form 141. Audit trail capturing every match, every claim, every rectification request and outcome.
A daily TDS leakage dashboard by customer with rupee receivable, days outstanding, and recovery probability band. A weekly deductor-side escalation pack with PAN, period, and amount detail ready to email. A monthly 168 match-rate trend tracking books-to-statement reconciliation coverage. A quarterly recovery report showing rupees recovered, rupees rectification-filed, rupees structurally lost — feeding the Discovered Money register on the tax-deduction class.
A CFO at a Mumbai management-consulting firm with ₹62 crore of annual revenue runs a quarter-end check on TDS receivable. The book shows ₹52 lakh of accumulated TDS credit over 14 months across 41 customers. The aggregated Form 26AS plus Form 168 statement for the firm’s PAN shows ₹44.8 lakh. The gap — ₹7.2 lakh — is real, recoverable, and entirely invisible until someone pulls both records side by side.
This is TDS credit leakage in its standard Indian form: not theft, not fraud, but the structural gap between what was deducted on your invoice payments and what the government’s TDS-credit register actually shows for your PAN. This guide walks the Form 26AS / Form 168 architecture under the 2026 migration, the section-393/394 payment-code dictionary 1001-1092 and its cross-era 194x mapping, the four root causes of leakage, and the 30 / 60 / 90 / 180-day deductor ageing playbook that recovers 60-80% of the standing gap.
Quick reference: TDS leakage detection map
| Leakage signal | Source artefact | Operative reference | Recovery action |
|---|---|---|---|
| Books TDS receivable exceeds 26AS / 168 total | TDS receivable ledger vs Form 26AS / Form 168 | Section 393 / 394, Income Tax Act 2025 | Deductor follow-up at day 30, 60, 90 |
| TDS deducted but not deposited within window | Customer payment advice vs deductor TDS challan | Section 416 — interest on late TDS deposit | Escalate to deductor CFO, request challan copy |
| Wrong PAN in deductor filing | 26AS / 168 record for related PAN versus expected | Form 131 (legacy) / Form 141 (new era) | Deductor TRACES correction, deductee PAN confirmation |
| Wrong section code | 26AS / 168 entry under different code | Payment-code dictionary 1001-1092 | Section-code rectification request to deductor |
| Cross-era mapping ambiguity | FY spanning 2026 migration cutover | Section 393(1)(a) ↔ 194J 194H 194I etc. | Apply cross-era mapping table, dual-statement reconciliation |
| Rectification window lapsed | Receivable older than 180 days | Form 131 / Form 141 filing deadline | Document for structural-loss write-off |
| Penalty under Section 416 paid by deductor | Deductor challan with interest component | Section 416 — 1.5% per month | Confirm credit appears in deductee statement post-deposit |
| Quarterly return not filed | TRACES public filing index per TAN | Quarterly TDS return cycle | First escalation — request expected filing date |
The Form 26AS / Form 168 architecture under the 2026 migration
The 2026 migration of the TDS framework into the consolidated Section 393 / 394 architecture preserved the deductee-side credit-statement infrastructure but split it across two forms during the transition.
Form 26AS continues to host the legacy annual TDS-credit statement for assessment periods predating the migration, with credits indexed by the deductor’s TAN, the legacy section code (194C, 194J, 194H, 194I, 195, 206AB, 206C and so on), the period of deduction, and the rupee amount.
Form 168 hosts the post-migration statement for deductions made under the new payment-code dictionary 1001 to 1092. Codes 1001-1003 cover the legacy 194J space — professional services to a company, professional services to an individual, fees for technical services. Codes 1010-1012 cover the legacy 194Q purchase TDS provisions. Codes 1020-1035 cover the legacy 194C contractor space. Codes 1040-1055 cover the legacy 194I rent space. Codes 1060-1085 cover the legacy 194H, 194O, 194R, 194S, 194T spaces. Codes 1086-1092 cover the legacy 195 non-resident space under the Section 394 mirror.
For most operating businesses today, an FY straddles the cutover. A deductee will see TDS receivable showing partly in 26AS (legacy 194x references) and partly in 168 (1001-1092 codes). A reconciliation engine that pulls only one of the two will read a structurally low total and over-report leakage. A correctly configured engine pulls both, aggregates per PAN per period, and reconciles against the books-side TDS receivable.
Why TDS credit leakage happens — the four root causes
Cause 1 — the deductor never deposited. The customer’s payment advice records the deduction at ₹X. The deductor was supposed to deposit ₹X within the Section 416 window — 7 days from the end of the deduction month (with the standard year-end variation for March deductions). If the deductor did not deposit, no record exists at the government end. The deductee has a receivable on books but no statement entry to back it.
Cause 2 — the deductor deposited but never filed the quarterly TDS return. The challan exists, the rupees are with the government, but no deductor return links the rupees to the deductee’s PAN. The amount appears nowhere in 26AS or 168.
Cause 3 — wrong PAN. The deductor filed the return, but used an incorrect PAN for the deductee. The credit lands in a different taxpayer’s 26AS / 168. This is more common than expected at deductor end where vendor masters are stale; new entities created by the deductee through restructuring frequently inherit wrong PAN entries from legacy contracts.
Cause 4 — wrong section code. The deductor filed under the wrong payment code. A professional-services payment that should have hit code 1001 lands under 1002 (an individual professional) or under a legacy 194C contractor reference. The credit is technically visible in the deductee statement but cross-references the wrong category — relevant for any deductee that reads the statement filtered by category rather than aggregated.
The 30 / 60 / 90 / 180-day deductor ageing playbook
Every TDS receivable starts the clock from the date of deduction recorded on the customer’s payment advice.
Day 30 — the Section 416 deposit window has closed for the deduction period. The deductor should have either deposited (and the receivable should be visible in the deductor’s draft return preview, requestable via direct contact) or be incurring interest at 1.5% per month. Action: a first soft confirmation to the deductor’s AP team, requesting expected challan / TAN-period record reference.
Day 60 — the quarterly TDS return for the relevant period must be filed. The deductee can verify against the TRACES public filing index by TAN. If the return is filed, the rupee should now appear in 26AS / 168. Action: re-confirm in the deductee statement; if absent, raise a second escalation citing PAN, period, code, and amount.
Day 90 — escalate to the deductor’s CFO office. Most large deductors have an internal-TDS-correction desk; a clean ageing pack with PAN, period, payment code 1001-1092 (or legacy 194x reference), amount, and original payment advice is what gets actioned.
Day 180 — the rectification window risk is now material. File Form 131 (legacy 194x) or Form 141 (new-era 1001-1092) rectification at the deductor’s TRACES login. The deductor formally requests the income tax department to correct the PAN, period, or code in the existing filing. Outcome is typically a fresh 26AS / 168 entry within 30-45 working days.
Beyond day 180, recovery probability drops materially. Document the receivable for structural-loss treatment.
Worked example — a ₹50 crore IT services firm
Setup: a Bangalore IT-services firm with ₹50 crore of annual revenue, 78% of which is from large-company customers (effective TDS rate 2% under Section 393(1)(a) code 1001 for professional services to a company), and 22% from individual-led consulting customers (Section 393(1)(a) code 1002, 2% rate). Total TDS-bearing revenue: ₹50 crore. Total TDS deducted: roughly ₹1 crore a year.
Pre-workflow baseline. A point-in-time check at FY-end shows ₹78 lakh of TDS credit visible in aggregated 26AS plus 168 against ₹91 lakh of TDS receivable on books. Leakage: ₹13 lakh, or 14.3% of TDS deducted.
After applying the 30/60/90/180-day workflow for two full quarters: 11 deductors confirmed pending challans for ₹4.8 lakh and deposited; 6 deductors had filed under wrong section code and corrected for ₹3.1 lakh; 3 deductors had filed under wrong PAN and corrected for ₹1.9 lakh. Total recovery: ₹9.8 lakh out of ₹13 lakh standing. Recovery rate: 75%. Residual: ₹3.2 lakh, of which ₹1.4 lakh comes from two deductors who have wound up and ₹1.8 lakh is past the rectification window.
Recovered band post-workflow: ₹9.8 lakh of permanent additional cash inflow, every year, against a recurring receivable base.
Estimate your TDS credit leakage band
Enter revenue, applicable payment codes, and rough deductor mix to model your standing TDS leakage before configuring a workflow.
Open the TDS Mismatch Estimator →The cross-era mapping table — how to keep FY26 reconciliation clean
The 2026 migration cutover means a single deductee customer may issue payments under both eras within the same FY. The reconciliation engine must hold a mapping that links the legacy 194x section to the new 1001-1092 payment code for any analytics that compare year-on-year leakage by category.
Indicative mapping (high-frequency entries only): 194C (contractor) → 1020-1035 family. 194J (professional and technical) → 1001-1003. 194I (rent) → 1040-1055 family. 194H (commission) → 1060-1065. 194O (e-commerce operator) → 1070-1075. 194Q (purchase above ₹50 lakh) → 1010-1012. 194R (benefits / perquisites) → 1078-1080. 194S (virtual digital assets) → 1082-1084. 194T (partner remuneration) → 1085. 195 (non-resident) → 1086-1092 under Section 394.
The mapping is consulted at three points: (a) when matching a legacy 26AS entry against the new-era books receivable, (b) when aggregating year-on-year leakage trends by category, (c) when filing a rectification because the deductor used the legacy reference past the cutover date.
Putting it on the audit committee agenda
The tax-deduction class of the seven-class leakage framework is the single most reliable line for the audit committee to track quarterly because the numbers move materially with workflow discipline. A standard quarterly pack contains: total TDS-bearing revenue this quarter, TDS deducted, books-receivable position, aggregated 26AS plus 168 position, the gap (leakage), the recovery pipeline by ageing bucket, the rectification queue with rupees and counterparty, and the structural-loss write-off candidates. This is the four-page artefact that turns “we suspect TDS slippage” into “we recovered ₹9.8 lakh this quarter and we expect ₹4 lakh next quarter.”
Continue reading on the leakage backbone
Pair this with Revenue leakage and the Seven Classes framework for the overall framing, ITC leakage under Rule 36(4) for the GST companion, and the Revenue leakage recovery playbook for the cross-class operating model. The Stop Revenue Leakage pillar page anchors the umbrella story.