The tax was genuinely deducted. The payment was genuinely made. And still, a demand notice landed on the wrong doorstep — because somewhere upstream, one digit in a PAN had been typed incorrectly, and the system did exactly what it was built to do: flag the person who could least explain it.
Tax Deducted at Source, or TDS, is meant to work quietly in the background. A client pays a vendor, deducts a percentage as tax, deposits it with the government, and files a TDS return reporting that deduction against the vendor's PAN. The vendor then sees that credit reflected in their Form 26AS — the tax department's running statement of credits — and claims it against their own tax liability when filing returns.
Most of the time, this works exactly as designed. In this case, it didn't — because the client's accounts team, filing a TDS return covering dozens of vendor payments in a single quarter, transposed two digits in one vendor's PAN. The tax had genuinely been deducted and deposited. The return had genuinely been filed. But it was filed against a PAN that belonged to someone else entirely, so the credit never showed up where it was supposed to.
Whose Problem Does the System Think This Is?
The vendor discovered the gap only when their own return was processed and a demand notice arrived — the tax department's system, seeing a claimed credit that didn't match any corresponding entry against the vendor's own PAN, treated the mismatch as the vendor's error and raised a demand for the shortfall, plus interest. From the vendor's side, this felt deeply unfair, and understandably so: they had received a valid TDS certificate, they had every reason to believe the deduction had been correctly reported, and the actual mistake belonged entirely to someone else's accounts team.
The Law Actually Agrees With That Instinct
This is one of the more genuinely protective, and under-known, provisions in Indian tax law. Section 205 of the Income-tax Act, 1961, states plainly that where tax is deductible at source, the person from whose income the deduction has been made — the vendor, in this case — shall not be called upon to pay the tax himself to the extent the deduction has actually been made. In other words: if the deductor genuinely deducted the tax, the deductee cannot be forced to pay it again, even if the deductor's reporting was faulty. Courts, including the Delhi High Court and several others, have repeatedly held that a deductee cannot be saddled with the deductor's compliance failure — the department's proper recourse in such cases is against the deductor who filed the incorrect return, not the deductee who suffered the deduction.
Armed with that principle, the fix here wasn't a fight — it was documentation. The vendor's TDS certificate, the client's bank statement showing the payment and deduction, and a formal request to the client to file a correction statement rectifying the PAN error, together made the case straightforward: the credit belonged to the vendor, the mistake belonged to the client's return, and Section 205 meant the demand had no legal basis while that correction was pending.
The Real Lesson, on Both Sides of This Kind of Notice
If you receive a demand over a TDS mismatch and you know, with certainty, that the deduction was actually made — don't assume you're the one who has to fix the paperwork trail. Section 205 exists precisely to protect you while the actual error gets corrected upstream, and knowing to invoke it, with the right supporting certificate, changes a demand notice from a genuine liability into a straightforward administrative correction. And if you're on the deducting side, this is a quiet but real reminder of why a single-digit PAN error in a bulk TDS filing isn't a minor clerical slip — it can genuinely disrupt someone else's tax position for months before anyone traces it back to its source. Reconciling PAN entries against vendor records before filing a TDS return is a small habit that prevents a problem far larger than the five minutes it takes.