TDS the Auditor's Way: Catching the Deduction That Never Happened
Most TDS reconciliation tooling answers one question well: does what the client deducted match Form 26AS? That's necessary, but it's the easier half of the problem. The harder, more expensive-to-miss question is the mirror image — where TDS should have applied and simply didn't get deducted at all. A vendor invoice that clears the books with no deduction, because nobody flagged that Section 194C or 194J applied, doesn't show up as a mismatch in a 26AS reconciliation. It shows up as nothing — until the assessing officer's disallowance under Section 40(a)(ia) finds it instead.
Why "reconciliation" alone misses the real exposure
A standard TDS reconciliation checks whether the TDS that was deducted matches what's reported. That's a real check, but it starts from an assumption — that the deduction decision itself was made correctly in the first place. If a payment to a contractor never had TDS applied because the person entering the voucher didn't recognize it as a 194C-triggering payment, there's nothing in that voucher for a standard reconciliation to catch. The gap only becomes visible when something separately tests every payment against whether TDS should have applied, not just whether the TDS that exists reconciles.
This is precisely the scenario firms flag most often: "suppose there are expenses where TDS is liable but the party has not deducted — will it identify?" and its mirror, "if I pass a separate entry for a purchase and a separate journal entry for TDS, can it detect that?" Both are really the same underlying ask — catch the applicability gap, not just the reconciliation gap.
What applicability-first detection actually looks for
CORAA's TDS reconciliation runs structurally rather than starting from the assumption that a deduction decision was already correct — every ledger entry gets tested against section applicability (194C, 194J, and the rest of the deduction sections) independent of whatever TDS was or wasn't already applied, so a payment that should have triggered a deduction and didn't gets flagged on its own, not only when its 26AS counterpart fails to match.
On the reconciliation side proper — matching what was deducted to Form 26AS — a genuine Sec 199 credit recovery is only flagged where Rule 37BA's conditions hold (the corresponding income has actually been offered to tax) and the return is still within the Sec 139(5) revision window; lines that are time-barred, belong to a different year or assessee, or are just timing differences get held back rather than counted as recoverable, because asserting a recovery that doesn't hold up is worse than not asserting one at all. For TAN-less ERP entries, name-bridging reconciles the party against the 26AS deductor directly, so a missing TAN doesn't silently drop a real credit from the match — low-confidence matches route to their own review bucket rather than getting asserted as a tie.
Why this distinction matters for the audit opinion, not just the working paper
An applicability gap that surfaces during the audit, before the return is filed, is a correction. The same gap discovered by an assessing officer during scrutiny, after the return is filed, is a disallowance under Section 40(a)(ia) — added back to income, with the client bearing both the tax cost and the credibility hit of the auditor having missed it. The value of catching it early isn't just efficiency; it's the difference between "we found this and fixed it" and "the department found this for us."
What to ask a vendor about their TDS module
Two separate questions, and it's worth confirming both get a real answer: does the tool test every ledger entry for TDS applicability structurally, independent of whether a deduction already exists — or does it only reconcile deductions that were already made? And on the credit-recovery side, does it apply the Rule 37BA and Sec 139(5) conditions before flagging a 26AS-vs-return gap as recoverable, or does it flag every gap as a potential credit regardless of whether the conditions actually hold?
Frequently Asked Questions
How is TDS applicability detection different from TDS reconciliation?
Reconciliation checks whether TDS that was already deducted matches Form 26AS. Applicability detection independently tests every ledger entry against the sections that could trigger a deduction (194C, 194J, etc.), catching cases where TDS should have applied but was never deducted at all — a gap a pure reconciliation can't see.
What happens if a Section 199 credit shows up in 26AS but wasn't claimed in the return?
It's only flagged as recoverable if Rule 37BA's condition holds — the corresponding income has actually been offered to tax — and the return is still within the Section 139(5) revision window. Time-barred lines or ones belonging to a different year or assessee are held back rather than asserted as recoverable.
Can TDS matching work if the party ledger doesn't have a TAN recorded?
Yes, for TAN-less ERP entries the system name-bridges the party against the 26AS deductor directly. Low-confidence matches route to a separate review bucket rather than being asserted as a tie.
What's the real cost of a missed TDS applicability gap?
Beyond the immediate tax cost, an undeducted TDS payment is disallowed under Section 40(a)(ia) if caught during assessment — added back to income. Catching the same gap during the audit, before filing, avoids both the disallowance and the credibility cost of the department finding it first.
Related: TDS Reconciliation module · Start a free trial