Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
The TDS receivable ledger says Rs 8,42,000 was credited by a client across the quarter. Form 168 shows Rs 6,73,000. The gap is Rs 1,69,000. A controller cannot sign off the quarterly close without either recovering the shortfall, provisioning against it, or documenting it as a rolling exception with an owner and a date. Yet most Indian finance teams run a two- or three-check investigation — check the section code, check the PAN, check the challan — and then dump the residual into an unexplained exception bucket that rolls forward into year-end. The residual bucket is exactly what turns into a Section 143(3) query note during the annual assessment, or a CARO 2020 audit finding on an unreconciled TDS receivable balance. The fix is a completeness protocol — twelve checks, each anchored to a statute, each closing with a rupee-tagged recovery, a documented next action, or a formal residual with a reason code.
Run the twelve-check sequence in a fixed order so the higher-probability causes clear first and the residual after each check is smaller. Check 1 — cross-era code confusion between Section 393 payment code and legacy Section 194 code. Check 2 — Section 206AA higher-rate deduction on missing or invalid PAN. Check 3 — Circular 23/2017 violation with deduction on the GST-inclusive amount. Check 4 — deductor filed under the wrong section code (contractor as professional services or the reverse). Check 5 — quarter boundary drift where the invoice was raised end-Q1 but the deductor filed in Q2. Check 6 — challan not deposited even though the deduction was made. Check 7 — deductor short-deducted against the applicable rate. Check 8 — intercompany credit misdirected to the wrong PAN in a group structure. Check 9 — DTAA benefit not applied on a non-resident deductor. Check 10 — TDS on advance payment reconciled to the wrong invoice. Check 11 — annual aggregate threshold under Section 194J or equivalent triggered mid-year. Check 12 — deductor's own Form 168 correction pending, statement not yet filed for the quarter. Every check produces a rupee-tagged output — recovered, pending correction, or formal residual — and every residual carries a next-action code that feeds the escalation ladder.
Ownership map — the tax executive runs the twelve checks; the tax manager reviews the residual bucket and signs off the aging categorisation; the controller reviews any single-deductor shortfall above Rs 50,000 or any quarterly aggregate shortfall above Rs 2,00,000. Reference tables required at the start of the investigation — the current Section 393 payment code schedule, the legacy Section 194 to payment code mapping table, the deductor PAN validation status refresh, the Section 197 low-deduction certificate register, and the DTAA rate reference for non-resident deductors. Working paper structure — one row per receivable line, columns for each of the twelve checks, a per-row rupee output, and a per-row reason code that flows into the [TDS aging workbook's](https://www.terra-insight.com/insights/tds-receivable-aging-workbook-excel-india/) named exception categories. Escalation calendar — 30-day tier to tax manager, 60-day tier to controller, 90-day tier to CFO with provision or Section 197 escalation.
A closed twelve-check working paper against every Rs 1,69,000-class shortfall in the quarter — every rupee traced either to a recovered amount, a pending deductor correction, a Section 206AA refund request, a Circular 23/2017 dispute, a DTAA claim, an intercompany reallocation, an annual-threshold provision, or a formal residual with a per-row reason code. A supplier follow-up register generated from the checks that produced a pending-correction output. A Section 197 low-deduction certificate application register for the deductors whose shortfalls recur across quarters. A residual bucket with a per-row reason code that survives Section 44AB tax audit review and CARO 2020 audit review. A tax manager sign-off on the quarterly close and a controller sign-off on any single-deductor exception above Rs 50,000. The output is not zero shortfall — it is a documented, categorised, escalation-tagged shortfall that a controller can defend.
The TDS receivable ledger said Rs 8,42,000 was credited by the client across the quarter. Form 168 said Rs 6,73,000. The gap was Rs 1,69,000. I had eight working hours to close the quarterly reconciliation, a controller expecting a sign-off before end of day, and a client relationship on the sales side that could not afford a wrong accusation. This is the twelve-step investigation that ran that day — anchored to statutes, tagged in rupees, and structured so the higher-probability causes cleared first and the residual after each step got smaller. It is the operational companion to the TDS reconciliation runbook that documents the monthly and quarterly cadence, the TDS receivable aging workbook that holds the ledger this investigation ran against, and the TDS reconciliation failure mode analysis that catalogues the design layer above every one of these twelve checks.
Why twelve checks and not five
The temptation, sitting with a receivable ledger and a Form 168 pull, is to jump to the highest-probability cause. In the FY 2026-27 transition year that is cross-era code confusion — a Section 194J invoice paid in April 2026 that the receivable ledger keyed under the legacy code rather than under Section 393 payment code 1005. Cross-era code confusion typically explains a third of the shortfall in the first two quarters after transition. Two more causes — deductor filed under the wrong section, and quarter boundary drift — typically explain another third. Five checks would close two-thirds of the shortfall on most quarters and leave the last third in a residual bucket that the tax manager waves through as unexplained.
That residual is the audit finding. Not the rupee amount — the fact that a rupee amount is carried forward without a per-row reason code. A CARO 2020 review or a Section 44AB tax audit tests documentation state, not resolution rate, and a residual without a per-row reason code fails both. The twelve-check protocol is the completeness discipline that produces a closed working paper — every rupee traced either to a recovered amount, a pending correction with a named counterparty, or a formal residual with a reason code that survives auditor review.
Check 1 — cross-era code confusion between Section 393 and Section 194 series
The March 2026 professional-services invoice paid in early April 2026 sits in the receivable ledger. Under the two-key discipline documented in the cross-era reconciliation article, the ledger should carry the legacy section code because the deduction event was in FY 2025-26. The deductor’s Form 168 filing for Q1 FY 2026-27 will show the credit against the payment code, not the legacy section code, but the receivable ledger’s lookup was keyed to the wrong side.
I re-ran the ledger with both keys — Section 393 payment code first, legacy Section 194 code second — and Rs 9,400 of the Rs 1,69,000 shortfall cleared to matched. The remaining shortfall was now Rs 1,59,600. Resolution: re-key the ledger. Escalation: none required at this stage; the ledger fix is a working-paper correction.
Check 2 — Section 206AA higher-rate deduction on missing or invalid PAN
Where the deductor could not validate the deductee’s PAN against the Income Tax Department’s database at the time of deduction, Section 206AA requires a deduction at the higher of the Section rate or 20 per cent. On a Rs 4,00,000 professional-services invoice with a Section 393 code 1005 rate of 10 per cent, a valid PAN produces Rs 40,000 of deduction. An invalid PAN produces Rs 80,000. The receivable is booked at Rs 40,000 (the contractual rate) but the deductor deposited Rs 80,000, and Form 168 shows Rs 80,000.
In this quarter’s investigation no Section 206AA cases surfaced. The Rs 1,59,600 shortfall carried forward unchanged. Resolution when it does surface: file a PAN correction request with the deductor and claim the excess Rs 40,000 as a refund receivable against the deductor. Escalation: 15-day tier to the tax manager because the shorter economic recovery window under Section 206AA compresses the standard 30-day escalation.
Check 3 — Circular 23/2017 violation with deduction on the GST-inclusive amount
Circular 23/2017 clarifies that TDS applies on the pre-GST amount where GST is shown separately in the invoice. A Rs 4,00,000 professional-services invoice with 18 per cent GST carries a gross of Rs 4,72,000. A deductor that deducts on Rs 4,72,000 rather than Rs 4,00,000 produces an excess deduction of Rs 8,400 at the 10 per cent rate — Rs 47,200 rather than Rs 40,000. The receivable is booked at Rs 40,000 but Form 168 shows Rs 47,200.
In this investigation Check 3 also came up empty. The Rs 1,59,600 shortfall carried forward. Resolution when it does surface: refund reconciliation request against the deductor, not an automatic setoff. Escalation: 15-day tier to the tax manager for the same short-window reason as Check 2.
Check 4 — deductor filed under the wrong section code
The largest single item in the investigation surfaced here. A body-corporate contractor invoice for Rs 8,40,000 attracted Section 393 payment code 1002 at 1 per cent — Rs 8,400 of deduction. The deductor’s tax team, misreading the scope of work as professional services, filed the deduction against code 1005 to 1008 (successor to Section 194J) at 10 per cent — Rs 84,000. Form 168 showed Rs 84,000 sitting against code 1005; the receivable ledger was searching under code 1002 and returned zero.
Re-running the receivable match with both target codes — code 1002 first, code 1005 to 1008 second — cleared Rs 84,000 to matched, though the classification itself is still wrong on the deductor’s side. The remaining shortfall was now Rs 75,600. Resolution: written request to the deductor for a Section 154 correction statement moving the deduction from code 1005 to code 1002. Escalation: 30-day tier to the tax manager. This is the class where the failure mode analysis rates the design-layer control at High Action Priority.
Check 5 — quarter boundary drift between invoice date and filing quarter
An invoice raised on 30 June — the last day of Q1 — is a Q1 receivable. The deductor may have deducted the tax in July when the payment was released, and filed it against Q2 rather than Q1. Form 168 for Q1 will show the shortfall; Form 168 for Q2 will show the surplus.
Two invoices in this quarter fell into this class — Rs 12,600 aggregate. The check runs by comparing the receivable’s invoice date against the deductor’s filing quarter, and cleared to “will match in next quarter” against the next Form 168 pull. Remaining shortfall now Rs 63,000. Resolution: hold the receivable, tag it for the next quarterly reconciliation. Escalation: none required if the next quarter’s Form 168 confirms; escalation to 30-day tier if it does not.
Check 6 — challan not deposited even though the deduction was made
The client’s finance team confirmed by email that Rs 42,000 was deducted in July but the challan for that month had not yet been deposited at the time the deductor filed its Form 168 for the quarter. The deduction was real; the Form 168 filing was incomplete.
This is the class where the deductor’s own Section 200A demand cycle will process the shortfall in the next assessing-officer window, and where the deductee holds the receivable pending the deductor’s correction. Rs 42,000 cleared to “pending deductor correction”. Remaining shortfall now Rs 21,000. Resolution: written follow-up to the deductor citing the acknowledged deduction and requesting a corrected Form 168 filing. Escalation: 30-day tier to the tax manager, 60-day tier to the controller if the correction is not filed by the next quarterly close.
Check 7 — deductor short-deducted against the applicable rate
The remaining Rs 21,000 traced to a single invoice of Rs 4,20,000 attracting professional-services deduction at 10 per cent — Rs 42,000 correct — where the deductor deducted at 5 per cent and deposited Rs 21,000. Form 168 shows Rs 21,000; the receivable was booked at Rs 42,000; the gap is exactly Rs 21,000.
This is a straight short-deduction and the TDS credit recovery mechanisms article covers the recovery pathway. Rs 21,000 cleared to “pending deductor correction”. The shortfall was now fully accounted — Rs 9,400 recovered on Check 1 to matched, Rs 84,000 recovered on Check 4 to matched, Rs 12,600 pending on Check 5, Rs 42,000 pending on Check 6, and Rs 21,000 pending on Check 7. Resolution: written request for a corrected challan. Escalation: 30-day tier to the tax manager, and note the deductor’s short-deduction pattern for the Section 197 register.
Check 8 — intercompany credit misdirected in a group structure
The check does not apply here — the deductor is not an intercompany party. But the discipline runs it anyway. In a group with multiple PAN registrations, a deductor may credit the wrong sister-company PAN, and Form 168 will show the credit against the wrong deductee. The receivable in one company will show a shortfall; the receivable in the sister company will show an unexpected credit.
Resolution when it does surface: the two group companies pass an internal journal to move the credit and file the underlying record correction with the deductor. Escalation: routine 30-day tier because both sides of the correction are internal.
Check 9 — DTAA benefit not applied on a non-resident deductor
Also inapplicable here. Where the deductor is a non-resident and a Double Taxation Avoidance Agreement provides for a lower withholding rate, the deductor may nonetheless have applied the domestic Section 393 rate. The receivable would then show a higher-than-expected credit and the deductee is entitled to a refund of the excess.
Resolution when it does surface: file the Tax Residency Certificate and the Form 10F with the deductor and claim the DTAA refund. Escalation: routine 30-day tier.
Check 10 — TDS on advance payment reconciled to the wrong invoice
Where a customer paid an advance in Q1, the deductor deducted TDS on the advance, and the invoice against which the advance was adjusted was raised in Q2, the receivable’s invoice-date lookup will search Q2’s Form 168 while the credit sits in Q1’s Form 168. Not applicable in this quarter, but the check remains in the sequence.
Resolution when it does surface: re-key the receivable’s search date to the earlier-of invoice date or advance receipt date. Escalation: working-paper correction only.
Check 11 — annual aggregate threshold crossed mid-year
Section 194J and equivalent Section 393 codes apply above a Rs 30,000 annual aggregate threshold per deductee per financial year. A deductor may have deducted zero on the first Rs 30,000 of professional fees and then applied the rate only on the excess. The receivable ledger booked at the standard rate on every invoice will surface an apparent shortfall on the early invoices that were correctly not deducted.
Not applicable in this quarter for this deductor (the aggregate was well above the threshold on invoice one). Resolution when it does surface: re-book the receivable to reflect the correct Section 194J threshold treatment. Escalation: working-paper correction.
Check 12 — deductor’s own Form 168 correction pending
The last check confirms that the deductor has not filed a Section 154 correction against their own Form 168 for the quarter. A deductor who has identified a filing error and is preparing a correction may have communicated the intended correction but not yet filed it — in which case the current Form 168 pull is stale and the deductee’s shortfall investigation is running against a not-yet-final statement.
Not applicable in this quarter. Resolution when it does surface: hold the receivable, tag it for the next quarterly pull. Escalation: none required unless the correction is still not filed at the next quarterly close.
The tally after twelve checks
Of the Rs 1,69,000 opening shortfall — Rs 93,400 cleared to matched after Checks 1 and 4 (the two-key cross-era re-run and the wrong-section re-key), and Rs 75,600 carried forward to a pending-correction bucket populated by Checks 5, 6, and 7. Zero rupees carried forward as an unexplained residual. Every rupee had a reason code, a named next action, and an escalation date.
The escalation ladder for the pending-correction bucket
The pending-correction bucket runs the standard escalation ladder documented in the TDS runbook and the pillar playbook. Thirty days to the tax manager, sixty to the controller, ninety to the CFO with either a provision entry or a Section 197 low-deduction certificate application for chronic short-deducting counterparties. Every day of aging carries an interest cost — the deductor’s own Section 201(1A) interest liability accrues at 1 per cent per month for short deduction and 1.5 per cent per month for late deposit, which is why a written follow-up citing the interest cost is materially more effective than a follow-up that only cites the receivable balance. Section 197 becomes the preventive escalation step at the ninety-day tier — the deductee applies to the assessing officer for a certificate that formalises the correct rate on that deductor’s contract and prevents the shortfall from arising in future quarters.
When manual Form 168 shortfall investigation outgrows itself
The twelve-check discipline holds for a tax executive running a receivable ledger of a few hundred deductor entries and a shortfall history stable across two or three quarters. Above that scale three specific manual controls break, and the TDS reconciliation failure modes article rates each at High Action Priority.
The two-key cross-era match under the FY 2025-26 to FY 2026-27 transition, refreshed daily as deductors file returns at different cadences across the Form 168 processing window and the residual Form 26AS window, cannot be run manually at group-controller scale without silent misses. The Section 206AA PAN validation refresh keyed to every deductor for every quarter produces a validation workload that outpaces a spreadsheet the moment the deductor count crosses a low three-digit threshold. And the twelve-check investigation itself against a rolling shortfall of tens or hundreds of open items across a large receivable base — quarter after quarter — is where the manual tax team runs out of hours. The exception queue rolls forward, the residual bucket loses its per-row reason codes, and the audit finding lives in perpetuity.
The response is the continuously refreshed detection layer that runs all twelve checks as an automated categorisation with escalation triggers, rather than as a one-day-per-quarter manual exercise. Terra Insight’s TransactIG delivers this detection surface as the queue the twelve-check protocol otherwise cannot maintain.
Where this fits
- TransactIG — reconciliation infrastructure
- Reconciliation software India — pillar guide
- TDS reconciliation software
- GST reconciliation software
Related reading
- The Reconciliation Playbook — the twenty-day monthly close pillar
- TDS reconciliation runbook — the monthly and quarterly cadence
- TDS receivable aging workbook — the ledger this investigation runs against
- TDS reconciliation failure mode analysis — the design layer above this investigation
- The unreconciled bank credit decision tree — the seven-branch companion investigation
- The DRC-01B 72-hour triage playbook — the GST-side companion investigation
- Form 168 — the new quarterly TDS statement
- Cross-era TDS reconciliation — payment codes vs Section 194 legacy
- TDS payment codes 1001 to 1092
- Section 206AA PAN validation and higher-rate deduction
- TDS demand notice reconciliation under Section 200A
- TDS credit recovery under Form 26AS and Form 168
- TDS on GST component — Circular 23/2017
Frequently Asked Questions
Why twelve checks and not the five most common ones?
The twelve-check protocol is a completeness discipline, not a probability ranking. In any given quarter, three or four of the twelve typically explain the entire shortfall — cross-era code confusion, deductor filed under wrong section, and quarter boundary drift are the three highest-frequency causes in the FY 2026-27 transition year. But a five-check investigation that stops after the high-frequency causes is what produces the residual bucket that the controller carries into year-end as an unexplained receivable, and it is the residual bucket that turns into a Section 143(3) query note during the annual assessment. The twelve checks are the closed set — running the full sequence against the ledger produces either a recovered amount, a documented next action, or a formal residual with a reason code that survives auditor review. The time cost is one working day for a quarterly close; the alternative cost is an audit finding that the receivable balance cannot be defended.
What separates a Form 168 short-deduction that a deductor will correct from one that has to be provisioned?
Three signals separate them. First, the deductor’s acknowledgement — a written or emailed acknowledgement that the deduction was under-computed converts the shortfall from a receivable exception to a pending correction, and the aging clock switches from the 30-day tax-manager tier to the 60-day controller tier. Second, the deductor’s correction cadence — a deductor who has historically filed Section 154 correction statements against similar shortfalls within one quarter is a recovery candidate, while a deductor with no correction history against three or more prior shortfalls is a provisioning candidate. Third, the Section 197 certificate history — a deductor who has ignored a Section 197 low-deduction certificate the deductee holds is not a recovery candidate at all; the shortfall is being generated by a documented process failure on the deductor’s side that the deductee has already tried to prevent, and the receivable requires provisioning under Ind AS 115 as a variable-consideration constraint rather than being carried forward as a full receivable.
How does cross-era code confusion mask the real shortfall?
A Section 194J professional-services invoice paid in March 2026 belongs under the legacy section code. The same invoice paid in April 2026 belongs under Section 393 payment code 1005 to 1008. A receivable ledger that carries only the payment code will surface a Form 168 miss on every March invoice, and a ledger that carries only the legacy section code will surface a Form 168 miss on every April invoice. The apparent shortfall in either case is the aggregate of the wrongly-keyed rows, not a genuine deductor problem. The fix is the two-key discipline documented in the TDS runbook — try the payment code first, then the legacy section code — and running the discipline before the twelve-check investigation opens is what prevents Check 1 from consuming the entire investigation window. Once the two-key match runs cleanly, the residual shortfall is the real one, and the remaining eleven checks are what explain it.
When does the residual bucket become an audit finding rather than a manageable exception?
The audit finding threshold is not a rupee amount; it is a documentation state. A residual bucket that carries a per-row reason code — deductor short-deducted with acknowledgement pending; Section 206AA higher-rate confirmed and refund request filed; Circular 23/2017 excess-deduction disputed with the deductor — is not an audit finding, it is a working paper. The same residual bucket that carries only a rupee total with no per-row explanation is an audit finding, regardless of the rupee amount. The CARO 2020 audit and the tax audit under Section 44AB both test the documentation state, not the resolution rate, and a residual with a per-row reason code and an escalation date survives both audits. The twelve-check protocol produces the documentation state; a five-check investigation does not.
When does manual Form 168 shortfall investigation outgrow itself?
The twelve-check discipline holds for a tax executive running a receivable ledger of a few hundred deductor entries across two or three quarters of shortfall history. Three specific manual controls break above that scale. First, the two-key cross-era match under the FY 2025-26 to FY 2026-27 transition, refreshed daily as deductors file returns at different cadences across the Form 168 processing window and the residual Form 26AS window, cannot be run manually at group-controller scale without silent misses. Second, the Section 206AA PAN validation refresh keyed to every deductor for every quarter, tied to the higher-rate deduction exception queue, produces a validation workload that outpaces a spreadsheet the moment the deductor count crosses a low three-digit threshold. Third, the twelve-check investigation itself against a rolling shortfall of tens or hundreds of open items across a large receivable base — quarter after quarter — is where the manual tax team runs out of hours. The response is the continuously refreshed detection layer that runs all twelve checks as an automated categorisation with escalation triggers, rather than as a one-day-per-quarter manual exercise.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 393, Income-tax Act 2025 — payment codes 1001 to 1092 — Deduction of tax at source on payments other than salary. From April 1, 2026, every non-salary TDS deduction carries a payment code between 1002 and 1092 — code 1002 for contractor payments to bodies corporate (successor to Section 194C), code 1005 to 1008 for professional and technical services (successor to Section 194J), code 1017 for commission (successor to Section 194H), code 1019 for rent (successor to Section 194I). A receivable ledger keyed on the wrong code returns a Form 168 miss even when the deduction is real. The twelve-check investigation begins with the code confusion class because it is the single largest source of silent Form 168 mismatches in the FY 2026-27 transition year.
- ▸ Section 200A read with Section 201(1A), Income-tax Act 2025 — Processing of TDS statements and interest on late deposit or short deduction. Where the assessing officer processes a TDS return under Section 200A and identifies short deduction, short deposit, or a classification mismatch, a demand notice issues under the same section. Interest under Section 201(1A) applies at 1 per cent per month for short deduction from the date on which tax was deductible to the date on which it was actually deducted, and at 1.5 per cent per month for late deposit from the date of deduction to the date of actual payment. The escalation ladder for every unrecovered Form 168 shortfall runs against these clocks.
- ▸ Section 206AA, Income-tax Act 2025 (retained from Income-tax Act 1961) — Requirement to furnish Permanent Account Number. Where the deductee does not furnish a valid PAN, or the PAN furnished is inactive, invalid, or does not match the name on the Income Tax Department's PAN database, the deductor is required to deduct tax at the rate specified in the relevant provision or at 20 per cent, whichever is higher. Every 20 per cent deduction on the receivable side must be traceable to a documented PAN validation status on the deductor's records — the Form 168 will show the deducted amount, but a receivable ledger booked at the contractual rate will surface a shortfall.
- ▸ CBDT Circular 23/2017 dated 19 July 2017 — Clarification on TDS under Chapter XVII-B on payments containing a Goods and Services Tax component. TDS is required to be deducted only on the amount payable exclusive of GST where GST on services has been indicated separately in the invoice. Deduction on the GST-inclusive amount produces an excess deduction on the deductee side and a corresponding excess payable on the deductor side; the correction is a refund reconciliation, not an automatic setoff. Every excess-deduction claim in the shortfall investigation is validated against this circular before being carried forward as a receivable.
- ▸ Section 197, Income-tax Act 2025 — Low deduction certificate — Certificate for deduction at lower rate or no deduction. On an application made by the deductee, the assessing officer may issue a certificate under Section 197 authorising the deductor to deduct tax at a rate lower than the rate applicable under Section 393 or at nil. Where a Form 168 shortfall is expected to recur — a habitual short-deducting counterparty, or a Section 194J deductor treating a contract as Section 194C — the deductee can apply for a certificate that formalises the correct rate and prevents the shortfall from arising in the first place. Section 197 is the preventive escalation step at the tail of the twelve-check ladder.