Last reviewed: 9 September 2026. The quarter-one statements for FY 2026-27 went in by 31 July, and the processing intimations that follow them are landing now. Most of them are small, most of them are fixable, and a surprising number of them are not real defaults at all — they are challan-mapping errors that the deductor can close without paying a rupee of extra tax. The costly mistake is the other direction: treating a genuine short deduction as a clerical issue, letting it sit, and discovering it eighteen months later when a lower-deduction certificate is stuck or a buyer refuses to release a payment because the demand is showing against the deductor's TAN.
What the intimation actually is
When a TDS statement is filed, it is processed on the basis of arithmetic and matching: rate applied against section, deduction date against payment date, challan claimed against challan available, PAN quoted against PAN status. Anything that fails one of those tests becomes a default and the demand is communicated to the deductor with a document identification number. The relevant handles remain the familiar ones — processing under section 200A, consequences under section 201(1) and 201(1A), fee under section 234E and penalty under section 271H — and while the Income-tax Act 2025 has been in force for FY 2026-27, these provisions carry forward in substance. Portal and TRACES labels have lagged the renumbering in places, so read the section reference printed on your own intimation rather than assuming it.
Two things follow from the fact that this is machine processing. First, the demand is computed only from what the deductor reported, so a wrong entry produces a wrong demand with complete confidence. Second, the response window is real: the intimation carries a date and, once it passes, the demand hardens and starts interfering with everything else on the TAN.
The five defaults you will actually see
| Default | What triggered it | Cost | Usual fix |
|---|---|---|---|
| Short deduction | Rate lower than the section required, wrong section applied, or PAN inoperative so 20% was due | Shortfall + 1% per month under 201(1A) | Pay and tag, or Form 26A if the payee has paid |
| Short payment | Challan claimed does not cover the deduction, or the challan is mapped to the wrong quarter or section | Shortfall + interest until regularised | Correction statement re-tagging the challan |
| Late deduction | Tax deducted after the date it became deductible | 1% per month from deductible date to deduction date | Pay interest; no correction will remove it |
| Late payment | Deducted on time, deposited after the 7th of the following month (30 April for March) | 1.5% per month from deduction date to deposit date | Pay interest and tag the challan |
| Late filing | Statement filed after the quarterly due date | ₹200 per day under 234E, capped at the TDS in that statement | Pay the fee; it cannot be argued away on cause |
The month in "per month" is not a calendar month and not a proportionate one. Any part of a month counts as a whole month, which is why a single day of delay across a month-end costs two months of interest. That arithmetic is the single most common reason a deductor's own computation does not agree with the demand.
Read the justification report before you pay anything
The demand on the dashboard is a total. The justification report is the line-by-line working behind it, deductee by deductee, and it is the only document that tells you which of the five defaults you are dealing with. Downloading it, opening it with the utility and reading three columns — deductee PAN, rate applied against rate applicable, and challan claimed against challan available — resolves the majority of intimations in about twenty minutes.
Three patterns account for most of what turns up. A default sitting against a handful of PANs with an exact half-rate gap is almost always an inoperative PAN. A default that spreads evenly across every deductee in one section is usually a section or rate selection error at source. A default equal to one whole challan, with the deductees otherwise clean, is a mapping error — the money is with the government, it is simply pointed at the wrong quarter, section or head, and no further payment is due.
Worked example 1 — the inoperative PAN
A Thane manufacturing company pays ₹8,00,000 in professional fees during the quarter to a consultant and deducts at 10%, that is ₹80,000, depositing it on time. The consultant's PAN is not linked to Aadhaar and is therefore inoperative on the deduction date. The applicable rate becomes 20%, so ₹1,60,000 was deductible.
- Short deduction: ₹1,60,000 − ₹80,000 = ₹80,000
- Interest at 1% per month from the deductible date to the date the shortfall is deposited. Deducted 10 June 2026, paid 12 September 2026 — June, July, August and September, four months — ₹3,200
- Total to close: ₹83,200, plus the practical problem that the consultant has already been paid and the ₹80,000 has to be recovered commercially or absorbed
This is the default worth preventing rather than curing. A PAN-status check at vendor onboarding and again at the start of each quarter costs nothing; the cure costs the shortfall plus interest plus an awkward conversation. Where the consultant has already filed his return and paid tax on the fee, the Form 26A route below removes the ₹80,000, but not the interest for the intervening period.
Worked example 2 — one day, two months of interest
A firm deducts ₹1,50,000 on 28 June 2026 and deposits it on 8 July 2026 instead of 7 July. Interest under section 201(1A) runs at 1.5% per month from the date of deduction to the date of payment, counting part months as full months: June is one month, July is the second. The cost is 1.5% × 2 × ₹1,50,000 = ₹4,500 for a single day of delay. The same ₹1,50,000 deposited on 7 July would have cost nothing.
There is no relief provision for this and no useful argument to make. It is purely a treasury-calendar discipline problem, and the fix is to move the TDS payment to the 5th as a standing internal rule so that a bank holiday or a failed payment gateway on the 7th does not turn into two months of interest.
The Form 26A route — when the payee has already paid
The most under-used relief in this area is the proviso that a deductor is not treated as an assessee in default for the tax itself where the payee is a resident who has furnished his return of income, has included the relevant amount in that return, and has paid the tax due on it. The mechanism is Form 26A, read with Rule 31ACB, supported by an accountant's certificate in Annexure A confirming those facts from the payee's records.
What it does and does not do matters:
- Covers the tax component of a non-deduction or short-deduction default.
- Does not cover interest under section 201(1A) for the period from the date the tax was deductible to the date the payee furnished his return — that is payable regardless.
- Does not cover the late-filing fee under section 234E, which attaches to the statement, not to the tax.
- Needs the payee's cooperation: acknowledgement number, computation and confirmation that the amount is in the return. Vendors who have gone quiet are the practical bottleneck, not the form.
The realistic sequence is to raise the Form 26A request on the deductor's TRACES login, get the annexure certified, and then let the demand be recomputed. It is worth doing wherever the shortfall is material and the payee is contactable; it is not worth doing for a ₹2,000 default where the certification effort exceeds the demand.
Which fix closes which default
| Situation | Correction statement | Payment required | Form 26A |
|---|---|---|---|
| Challan tagged to wrong quarter or section | Yes — this alone closes it | No | Not applicable |
| PAN quoted wrongly, corrected within permitted limits | Yes | Usually no | Not applicable |
| Deducted at 10% where 20% applied (inoperative PAN) | Yes, after paying | Shortfall + 1% per month | Available for the tax if the payee has paid |
| Deducted on time, deposited late | Yes, to tag the interest challan | Interest at 1.5% per month | No |
| Statement filed late | Yes, to tag the fee challan | ₹200 per day, capped at the TDS | No |
A payment made without a correction statement tagging it is the second-most common reason a demand stays open after the deductor believes it has been cleared. The challan has to be paid under the right head and then claimed in a correction statement against the specific default; money sitting untagged in the system closes nothing.
Penalty exposure, and the one-year window
Separate from interest and fee, section 271H provides a penalty between ₹10,000 and ₹1,00,000 for failure to file a statement or for filing incorrect particulars. It is not automatic and it is not levied where the deductor has paid the tax, interest and fee and has filed the statement within one year of the prescribed due date. That one-year window is the practical reason to regularise an old quarter now rather than at the next notice — a FY 2025-26 quarter still inside its window is a very different conversation from one that has crossed it.
What to do in the next three weeks
- Log in on the deductor's TRACES account and list every open default across all TANs, not only the newest intimation. Old demands quietly block lower-deduction applications.
- Download the justification report for each and classify every default into one of the five types above. Do not pay anything before this step.
- Fix the mapping errors first — they are free, and they often reduce the demand substantially before any money moves.
- For genuine shortfalls, decide between paying and the Form 26A route based on the amount and whether the payee is reachable. Start the Form 26A conversations early; they are the slow part.
- Reconcile the books to the statement before the Q2 statement goes in — the correction and the fresh filing are more efficiently done in one pass rather than two.
- Run a PAN-operative check across the active vendor master before the next quarter's deductions, so this exercise does not repeat.
Mistakes that keep recurring
- Paying the demand from the dashboard without reading the justification report, and paying for a default that a correction would have removed.
- Computing interest proportionately for a few days and then disputing the demand — part months count as full months.
- Paying the challan but never filing the correction statement that tags it, so the default stays open.
- Treating an inoperative PAN as the vendor's problem. The obligation, and the demand, sit with the deductor.
- Deducting under a familiar section out of habit where the contract actually attracts another. Rates and thresholds by section are set out in the TDS Rate Finder for FY 2026-27, and the payment-type distinctions are worked through in the note on TDS on contractor, professional and commission payments.
- Missing the statement due date itself. The current quarterly forms and due dates are covered in the note on the Q1 FY 2026-27 TDS return and the renumbered forms.
Frequently asked questions
Is a TDS default intimation the same as a notice from the Assessing Officer?
No. The intimation generated after a statement is processed is a system-computed demand from the centralised processing setup, raised on the basis of what you yourself reported in the statement. It is not a scrutiny notice and it is not an allegation of concealment. It is, however, an enforceable demand once the response window closes, and it will sit on the deductor's TRACES account and block lower-deduction certificates and consolidated files until it is closed.
Can I ignore a small default of a few hundred rupees?
It is rarely worth ignoring. An open default keeps accumulating interest, and TRACES applies open demands against later refunds and correction requests. More practically, a pending demand shows up when the deductor applies for a lower-deduction certificate or downloads Form 16/16A, so a two-hundred-rupee default can hold up a much larger piece of work at exactly the wrong time.
The deductee has already paid the tax in his own return. Do I still have to pay?
Not the tax component, if you can prove it. Where the payee is a resident who has furnished his return, included the income and paid the tax due on it, the deductor is not treated as an assessee in default for that tax. Relief runs through the Form 26A route with an accountant's certificate in Annexure A. Interest for the period from the date the tax was deductible to the date the payee filed his return still applies, and the late-filing fee for the statement is not covered at all.
What is the difference between short deduction and short payment?
Short deduction means you deducted at a lower rate or on a lower base than the section required, so the shortfall was never withheld from the payee. Short payment means the correct amount was deducted but the challan does not cover it, which is very often a challan-mapping error rather than real money missing. The two need different fixes, so read the justification report before deciding which one you are looking at.
Can the late-filing fee under section 234E be waived on reasonable cause?
The fee is a fee, not a penalty, and the statute does not provide a reasonable-cause exemption for it. It is capped at the amount of TDS in that statement, so it cannot exceed the tax involved. The separate penalty for not filing the statement is discretionary and is not levied where the statement is regularised, with tax, interest and fee paid, within one year of the due date.
How long do I have to respond, and what happens if I fix the return instead of paying?
The intimation carries its own response window, usually thirty days from the date of the communication. Filing a correction statement is a valid response where the default is genuinely a data or challan error: once the corrected statement is processed, the demand is recomputed and a wrongly raised default falls away on its own. Where the default is real, the correction alone will not close it and the tax, interest and fee have to be paid and tagged.
We read the justification report, separate the mapping errors from the real shortfalls, file the correction statements and handle the Form 26A certification where the payee has already paid.
TDS Return Filing Income Tax Notice Management Refund, Demand & Rectification Talk to usThis note is general guidance on TDS default processing as it stands on 9 September 2026 and is not a substitute for advice on your own facts. Section references follow the handles printed on current intimations; portal labels are being updated for the Income-tax Act 2025 and should be read against your own communication. Interest, fee and penalty consequences depend on dates and amounts specific to each statement.