TDS Verification in FY 2026-27: What to Automate After the Section Renumbering
TDS verification was already the most mechanical, least intellectually rewarding part of a tax audit. This year it also became the part most likely to break quietly, because the data now arrives in two different numbering schemes at once.
The Problem That Is New This Year
The Income-tax Act 2025 took effect from 1 April 2026. Its effect on TDS is structural rather than cosmetic:
| Familiar provision | Where it now sits |
|---|---|
| The entire 194A–194T non-salary family | Consolidated into Sec 393, as one serialised list where each nature of payment carries a payment code instead of a section suffix |
| Section 194C (contractors), as an example | Payment code 1017 under Sec 393 |
| Salary TDS (192) | Sec 392 |
| No-PAN higher deduction (206AA) | Sec 397(2) |
For a verification workflow, the consequence is specific and easy to miss: challans and TRACES records generated after the cutover reference the new payment codes, while the client's books, their internal TDS registers, and last year's comparatives still carry the old section labels. Both are correct. They just don't match on a string comparison.
A reconciliation built on matching "194C" to "194C" does not fail loudly when the source data shifts to "1017". It reports fewer matches and a longer exception list, and somebody spends an afternoon investigating differences that are not differences.
If you need the mapping, we keep it free and standalone on the TDS Rate Finder and the Income Tax Act 2025 Section Mapper.
What TDS Verification Actually Consists Of
Most files treat this as one procedure. It is really three reconciliations plus an applicability test, and they catch different things.
1. Books to challans — was what we deducted actually deposited?
Compare TDS deducted per the books against challans paid. Differences here are cash-flow and compliance failures: deducted and not deposited, deposited late, deposited under the wrong section or payment code, deposited against the wrong TAN or quarter.
2. Challans to returns — does the return reflect what we paid?
Compare challans against the quarterly statements filed (24Q/26Q/27Q). Failures show up as unconsumed challan balances, short-reported deductees, or PAN errors that push a deductee to the higher no-PAN rate.
3. Returns to Form 26AS / AIS — does the deductee see what we reported?
This is the one clients care about, because it determines whether their vendors get credit.
4. The applicability test — should we have deducted at all?
This is the one that matters most for the audit opinion, and the one a reconciliation structurally cannot find. A payment on which TDS was never deducted, never deposited, and never reported is perfectly reconciled across all three views above. It appears nowhere. It is found only by testing expenditure against the deduction provisions, which is the subject of TDS the auditor's way.
Put plainly: the first three reconciliations verify that the client did correctly what they decided to do. Only the fourth asks whether the decision was right.
Where the Exposure Actually Sits
The reason this matters beyond compliance housekeeping is Section 40(a)(ia) — the disallowance where tax was deductible but not deducted, or deducted and not deposited within the prescribed time. For resident payments the disallowance runs at 30% of the expenditure; for the non-resident limb under 40(a)(i) the whole amount is at risk.
That converts a clerical TDS default into a tax cost, and it flows straight into Clause 21(b) of Form 3CD, alongside the TDS reporting in Clause 34. A file that reconciles TDS beautifully but never tested applicability has verified the wrong thing.
Late deposit also carries interest under Section 201(1A), running from the date of deductibility rather than the date of deduction — which is why "we paid it in June" is not the end of the enquiry.
What Should Be Computed, Not Eyeballed
Everything below has exactly one right answer derivable from the data. None of it should be a judgement call, and none of it should be a language model's guess:
- Normalising both numbering schemes to a common key before matching, so old section labels and new Sec 393 payment codes reconcile against each other rather than appearing as exceptions
- Three-way matching of books, challans and returns, at the deductee-and-quarter grain rather than in totals — totals can agree while every underlying line is wrong
- Rate testing: the rate actually applied against the rate prescribed for that nature of payment, flagging both under- and over-deduction
- Threshold testing: cumulative payments to a deductee crossing the single-payment and annual thresholds, which is where deduction obligations switch on mid-year and get missed
- PAN validation and the no-PAN higher-rate consequence under Sec 397(2)
- Due-date computation per challan, and the resulting 201(1A) interest exposure
- The 40(a)(ia) / 40(a)(i) disallowance schedule, computed rather than transcribed, and tied to Clause 21(b)
- Clause 34(a), (b) and (c) tie-out against the underlying registers
That list is arithmetic and lookup. It is also, in most firms, several days of an article's time per client during the busiest weeks of the year — which is exactly the wrong trade.
What Stays With the Auditor
- Whether a payment is in the nature of contract, professional fee, rent, or commission, when the invoice description is unhelpful and the contract is silent
- Whether a reimbursement is genuinely a reimbursement
- Whether a vendor's lower-deduction certificate under Section 197 is valid, current, and correctly applied
- Whether a non-resident payment attracts deduction at all, which needs the treaty and the nature of income before the rate
- Whether a default is isolated or symptomatic of a control failure worth reporting
- Whether the aggregate exposure is material to the opinion
The pattern is the same one that runs through every mechanical audit area: the computation should be exhaustive and automatic, and the judgement should be conscious and documented. What usually happens instead is the reverse — the computation is sampled because there is no time, and the judgement is inherited from last year's file.
What to Ask Before Trusting a Tool
If you are evaluating anything that claims to automate TDS verification this year, three questions separate the real from the demo:
- Does it handle both numbering schemes simultaneously? Not "we've updated to the new Act" — specifically, does it match an old-section record against a new-payment-code record without human help?
- Does it test applicability, or only reconcile? Ask it to find a payment on which TDS was never deducted. A reconciliation engine cannot, because there is nothing to reconcile.
- Does it show its working? A disallowance figure you cannot trace back to the specific vouchers and the specific due-date computation is not something you can put your name against.
Frequently Asked Questions
What changed for TDS under the Income-tax Act 2025?
Effective 1 April 2026, the non-salary TDS provisions of the 194 series consolidate into Section 393 as a single serialised list, where each nature of payment carries a payment code rather than a section suffix — Section 194C, for instance, maps to payment code 1017. Salary TDS consolidates into Section 392, and the no-PAN higher-deduction rule formerly in 206AA becomes Section 397(2).
Why do TDS reconciliations break in the first year after the change?
Because the same transaction can be labelled two ways. Books, internal registers and prior-year comparatives typically still use old section labels, while challans and TRACES records generated after the cutover use the new payment codes. A matching engine keyed to one scheme silently stops matching records carrying the other, producing a longer exception list rather than an error.
What is the difference between TDS reconciliation and TDS verification?
Reconciliation compares what was deducted, deposited and reported across books, challans and returns — it confirms internal consistency. Verification additionally asks whether tax should have been deducted in the first place. A payment where TDS was never deducted reconciles perfectly, because it appears in none of the three records.
How does a TDS default affect the tax audit?
Through Section 40(a)(ia) — expenditure on which tax was deductible but not deducted or not deposited in time is disallowed at 30% for resident payments, and in full under 40(a)(i) for the non-resident limb. This feeds Clause 21(b) of Form 3CD, and the TDS particulars themselves feed Clause 34. Late deposit separately attracts interest under Section 201(1A).