Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
The TDS receivable in the books says one number and Form 168 (or the old Form 26AS, for pre-FY 2026-27 residuals) says a smaller one. The controller cannot sign off the quarterly close without either recovering the gap, provisioning against it, or documenting it with a per-row reason code. Most finance teams run a two- or three-check investigation — check the section code, check the PAN, check the challan — and then park the residual as an unexplained exception that rolls forward. The parked residual 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. The fix is a twelve-item shortlist that closes every rupee to a specific cause.
Run the twelve reasons in a fixed order so the higher-probability causes clear first. Cross-era code confusion. Section 206AA higher-rate deduction. Circular 23/2017 GST-inclusive deduction. Deductor filed under the wrong section. Quarter boundary drift. Challan not deposited. Short-deducted at the wrong rate. Intercompany credit misdirected. DTAA benefit not applied. TDS on advance reconciled to the wrong invoice. Annual threshold under Section 194J triggered mid-year. Deductor Form 168 correction pending. Every reason produces one of three outputs — a recovered amount, a pending correction with a named counterparty, or a formal residual with a reason code.
Reference tables at the start of the investigation — the current Section 393 payment code schedule, the legacy Section 194 to payment code mapping, the deductor PAN validation status refresh, the Section 197 low-deduction certificate register, and the DTAA rate table for non-resident deductors. Ownership map — tax executive runs the twelve checks, tax manager reviews the residual, controller signs off any single-deductor shortfall above Rs 50,000. Escalation calendar — thirty-day tier to tax manager, sixty-day tier to controller, ninety-day tier to CFO with provision or Section 197 escalation.
A per-row working paper that traces every rupee of the shortfall to a recovered amount, a pending correction, or a formal residual. A deductor query letter register generated from the pending-correction outputs. A Section 197 application register for the deductors whose shortfalls recur. A quarterly close that a controller can sign off without carrying an unexplained receivable, and an audit trail that survives Section 44AB tax audit review and CARO 2020 review. The output is not zero shortfall — it is a documented, categorised, escalation-tagged shortfall with a defensible next action against every open item.
You pulled the quarterly TDS receivable ledger and it shows Rs 8,42,000 in credits against a client across the quarter. Form 168 shows Rs 6,73,000. The gap is Rs 1,69,000. Nothing in the working papers says why. The client’s finance team says they deducted the full amount and filed on time. Something is off — but where do you look first, and how do you know whether this is a wrong ledger entry, a real deductor problem, or a reconciliation timing artefact you can safely ignore this quarter?
The quick answer. In the FY 2026-27 transition year, a TDS receivable shortfall against Form 168 (or the residual Form 26AS window) almost always falls into one of twelve buckets. The three highest-frequency causes — cross-era code confusion between Section 393 payment codes and the legacy Section 194 series, Section 206AA higher-rate deduction on a PAN the deductor treated as invalid, and quarter boundary drift where the invoice was raised end-quarter but the deductor filed in the next one — typically explain more than half the gap on any given quarter. The other nine round out the completeness check.
This walkthrough covers the five most common causes in short-form. For the full twelve-check investigation — with per-row rupee tags, statute anchors, and the escalation ladder against Section 200A and Section 201(1A) — see the Form 168 shortfall investigation article that this piece routes into. The reasons below use an illustrative Rs 1,69,000 shortfall on a Rs 8,42,000 quarterly receivable to keep the arithmetic concrete.
Reason 1 — cross-era code confusion between Section 393 and Section 194
From April 1 2026, every non-salary TDS deduction moves from the Section 194 series to Section 393 with a payment code between 1002 and 1092. Payment code 1002 for contractor payments succeeds Section 194C. Payment codes 1005 to 1008 for professional and technical services succeed Section 194J. Payment code 1017 for commission succeeds Section 194H.
A Section 194J invoice paid in March 2026 belongs under the legacy section code. The same invoice paid in April 2026 belongs under payment code 1005 to 1008. A receivable ledger keyed on only one system will surface a Form 168 miss on every row that used the other one — even though the deduction is real, the challan is deposited, and Form 168 reflects it under the correct code.
Where to look. Pull the receivable ledger and cross-check the key against the invoice payment date. Any row with an April 2026 or later payment date should carry a payment code (1002 through 1092), not a legacy section code. Any row with a March 2026 or earlier payment date should carry the legacy code. Run a two-key match — try the payment code first, then fall back to the legacy code — and the aggregate shortfall usually shrinks by a third before you touch a deductor.
What to do. Fix the key on the ledger. If the ERP does not carry both keys, add a mapping column that resolves either way. See the cross-era TDS reconciliation article for the full mapping table.
Reason 2 — Section 206AA missing PAN triggered the 20 per cent higher rate
Where the deductee has not furnished a valid PAN, or the PAN is inactive or fails a name-match against the Income Tax Department’s database, Section 206AA requires the deductor to deduct at the higher of the applicable rate or 20 per cent. A Section 194C contractor invoice that should have been deducted at 2 per cent lands with a 20 per cent deduction. A Section 194J professional-services invoice that should have been deducted at 10 per cent also lands with a 20 per cent deduction.
The Form 168 shows the deducted amount. The receivable ledger booked at the contractual rate shows less. The difference — 18 per cent extra on the Section 194C invoice, 10 per cent extra on the Section 194J invoice — is the visible shortfall.
Where to look. Filter the receivable ledger for any deduction at exactly 20 per cent against a normally sub-20-per-cent section. Cross-check the PAN validation status on the deductor’s records. Where the deductor’s finance team can pull a PAN validation report showing Invalid, Inactive, or Name Mismatch on the date of deduction, Section 206AA is confirmed.
What to do. Refresh the PAN validation with the deductor and ask for a corrected challan against the true rate. The Section 197 low-deduction certificate route is the preventive fix for a recurring counterparty — the Section 206AA PAN validation article walks through both paths.
Reason 3 — TDS deducted on the GST-inclusive amount (Circular 23/2017)
CBDT Circular 23 of 2017 dated 19 July 2017 clarifies that TDS on services must be deducted only on the amount payable exclusive of GST, where GST has been shown separately on the invoice. A deductor that computes TDS on the GST-inclusive amount deducts more than the circular allows. The excess sits with the tax department and can only be recovered through a deductor-side refund — it does not automatically flow into Form 168 as an excess credit for the deductee.
Where to look. Any receivable line where the deducted amount is higher than the contractual rate applied to the GST-exclusive invoice value is a candidate. On a Rs 1,00,000 professional-services invoice with 18 per cent GST at Rs 18,000, a 10 per cent Section 194J deduction should be Rs 10,000. A Rs 11,800 deduction is a Circular 23/2017 violation on the GST-inclusive Rs 1,18,000 amount.
What to do. Raise a Circular 23/2017 correction request with the deductor and ask them to file a Section 154 correction statement. The excess amount is refundable to the deductor, who then has to remit it to you separately — this is administrative and slow, but the paper trail is what defends the receivable from being provisioned.
Reason 4 — the deductor filed under the wrong section
A Section 194J contract treated as Section 194C by the deductor’s system creates a wrong-section entry in Form 168. The deducted amount is real. The rate may or may not be right (depending on which side underestimated). The receivable ledger keyed on the correct section will not match the Form 168 credit keyed on the wrong section.
The most common variants are: a Section 194J technical-services invoice classified as Section 194C works-contract by a deductor whose vendor master is stale; a Section 194H commission classified as Section 194C by a deductor whose finance team runs on a template not built for commission; a Section 194I rent classified as Section 194C by a deductor whose lease register is separate from the AP system.
Where to look. Pull the Form 168 view keyed by section rather than by counterparty. Any counterparty that appears under a section your ledger has no receivable against, but is missing from a section your ledger does have a receivable against, is a wrong-section candidate.
What to do. Provide the deductor with the correct section reference (the invoice terms and the contract summary usually settle the classification) and ask for a Section 154 correction statement. The deductor Form 168 query letter pack has a template for the wrong-section chase.
Reason 5 — quarter boundary drift
An invoice raised on 29 June may be paid — with TDS deducted — on 3 July. The receivable ledger books the TDS credit against Q1 (the invoice month). The deductor files against Q2 (the deduction month). Form 168 for Q1 shows the shortfall; Form 168 for Q2 shows the offsetting credit. The aggregate is right; the per-quarter view is wrong.
Where to look. Any receivable line where the invoice date and the payment date fall in different quarters is a candidate. Roll the Form 168 view forward by one quarter for these lines and check whether the shortfall clears.
What to do. Book the TDS receivable against the quarter of the payment (the deduction), not the quarter of the invoice. Where the ERP forces the invoice-quarter booking, add a quarter-drift adjustment column that reconciles the two.
The one to escalate first
Of the twelve reasons, the highest-severity is not the highest-frequency. It is the challan-not-deposited case (Reason 6 in the full protocol) — a deductor who has deducted the tax but not deposited the challan against your PAN, or has deposited it against a wrong PAN. Every day the challan sits undeposited or misdeposited, Section 201(1A) interest accrues on the deductor’s side at 1.5 per cent per month, and the credit will never appear in Form 168 until the challan is corrected. The receivable is real on the books, but the tax department has no record of it against your PAN.
The moment you find a shortfall that cannot be explained by any of Reasons 1 to 5 above, escalate to the tax manager for a direct conversation with the deductor’s finance head. Do not carry an undeposited-challan case into the next quarter without a written acknowledgement — the escalation cost compounds monthly, and the recovery path narrows once the deductor’s own return is processed.
When manual checking outgrows itself
The twelve-item shortlist works for a tax executive running a receivable ledger of a few dozen deductors across two or three quarters of shortfall history. Above roughly a hundred deductors, or when the shortfall is a recurring feature every quarter, three specific manual controls break. The two-key cross-era match across the FY 2025-26 to FY 2026-27 transition, refreshed daily as deductors file at different cadences, cannot be run on a spreadsheet at group-controller scale without silent misses. The Section 206AA PAN refresh keyed to every deductor and every quarter is a validation workload that outpaces spreadsheet capacity. The twelve-check investigation itself, run every quarter against tens or hundreds of open items, is where the tax team runs out of hours.
Terra Insight’s TDS reconciliation software treats the twelve checks as continuously refreshed detection rather than a one-day-per-quarter manual exercise. Every receivable line is scored against all twelve reasons on ingest, escalation triggers fire against the TDS receivable aging workbook tiers, and the manual protocol stays as the training discipline the system runs against rather than the process the tax executive runs by hand.
Go deeper
- The twelve-check Form 168 shortfall investigation — the full protocol with statute anchors and escalation ladder
- TDS reconciliation failure modes — the design layer above this walkthrough
- Cross-era TDS reconciliation — the two-key discipline for FY 2025-26 to FY 2026-27
- Form 168 — the new quarterly TDS statement
- Section 206AA PAN validation and the 20 per cent higher rate
- TDS payment codes 1001 to 1092
Related resources
- TDS receivable aging workbook
- Deductor Form 168 query letter pack
- TDS reconciliation software India
- Reconciliation software India
Frequently Asked Questions
Which of the twelve reasons is most common in the FY 2026-27 transition year?
Cross-era code confusion between the new Section 393 payment code schedule and the legacy Section 194 series. 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 payment code 1005 to 1008. A receivable ledger that carries only the payment code will surface a Form 168 miss on every pre-April invoice, and a ledger that carries only the legacy section code will surface a Form 168 miss on every post-April invoice. The apparent shortfall in either case is the aggregate of the wrongly-keyed rows, not a real deductor problem. The fix is a two-key discipline — try the payment code first, then the legacy section code — and running it before any deductor chase is what prevents this bucket from consuming an entire quarterly close.
How do I tell whether the shortfall is Section 206AA higher-rate or the deductor short-deducted?
Look at the deduction rate on the deductor’s certificate first. A deduction at exactly 20 per cent against a Section 194C or Section 194J invoice is almost always Section 206AA — the deductor treated the PAN as missing or invalid and defaulted to the higher rate. Cross-check the PAN validation status on the deductor’s records (the deductor’s finance team can pull the report from their TDS software) — a status of Invalid, Inactive, or Name Mismatch confirms Section 206AA. A deduction at a rate below the applicable rate but above 20 per cent is short deduction — the deductor computed the tax wrongly rather than defaulting to the higher rate. The follow-up path differs. Section 206AA is fixed by refreshing the PAN status with the deductor and asking for a corrected challan against the true rate. Short deduction is fixed by the deductor filing a Section 154 correction statement, which typically takes one quarter.
Can I claim the shortfall as a receivable in books if I have no Form 168 credit yet?
Yes, if the deduction is real and the ledger is defensible. The receivable is booked at the point the customer credits the payment net of the deducted amount, not at the point Form 168 reflects the credit. The Form 168 credit is the reconciliation confirmation, not the recognition trigger. Where the shortfall carries forward across two or more quarters without a Form 168 posting, the standard practice is to keep the receivable open with an aging tag, run the deductor chase through the query letter register, and provide against the receivable only if the deductor has a documented history of ignoring correction requests. The provision decision is a controller call and typically follows a written follow-up register that shows a specific counterparty has ignored two or more prior chases.
How long does a Form 168 correction take once the deductor agrees?
The deductor files a Section 154 correction statement in the next quarterly return cycle, and the corrected credit typically appears in Form 168 within thirty to sixty days of that filing. In the interim, the receivable stays open with a note in the working paper — deductor acknowledged shortfall, correction filed on date X, Form 168 credit expected by date Y. If the correction has not surfaced within ninety days of the acknowledged shortfall, the escalation moves from tax-executive follow-up to a controller-level conversation with the deductor’s finance head, and the ledger note switches to the sixty-day tier. The full escalation ladder is documented in the twelve-check investigation article linked below, and the query letter templates for each escalation tier are in the deductor letter pack resource.
When does this stop being a spreadsheet exercise?
The moment the deductor count crosses roughly a hundred and the shortfall investigation starts recurring every quarter. Three specific manual controls break at that scale. The cross-era two-key match across the FY 2025-26 to FY 2026-27 transition, refreshed daily as deductors file returns at different cadences, cannot be run on a spreadsheet at group-controller scale without silent misses. The Section 206AA PAN validation refresh keyed to every deductor for every quarter, tied to the higher-rate deduction exception queue, produces a workload that outpaces manual capacity. And the twelve-check investigation itself against a rolling shortfall of tens or hundreds of open items — quarter after quarter — is where the manual tax team runs out of hours. Continuous detection software takes the twelve checks and runs them as an automated categorisation every day, with escalation triggers wired into the aging workbook, 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 covers contractor payments under the successor to Section 194C. Codes 1005 to 1008 cover professional and technical services under the successor to Section 194J. Code 1017 covers commission under the successor to Section 194H. A receivable ledger keyed on the wrong code returns a Form 168 miss even when the deduction is real. This is the single largest source of silent Form 168 versus ledger mismatches in the FY 2026-27 transition year.
- ▸ 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 always surface a shortfall until the higher-rate flag is applied.
- ▸ 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. The correction is a refund reconciliation through the deductor rather than an automatic setoff — every excess-deduction claim on the receivable side must be validated against this circular before being carried forward.
- ▸ 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 statement 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 on any unrecovered Form 168 shortfall runs against these clocks.
- ▸ 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 because a habitual short-deducting counterparty keeps treating a Section 194J contract as Section 194C, or the deductor's system keeps defaulting to a higher rate, the deductee can apply for a Section 197 certificate that formalises the correct rate and prevents the shortfall from arising in the first place.