Received a TDS CPC notice Section 200A and not sure what triggered it? You're not alone — this is one of the more common notices deductors receive, and it catches people off guard because it often shows up months after the return was filed. The notice highlights discrepancies between what you reported and what the CPC's system calculated. It's a system-generated intimation — not an assessment order — but it still needs a proper, timely response.
Here's what it means, why it lands in your inbox, and exactly how to deal with it.
TDS notice under Section 200A is a system-driven intimation issued by the Centralised Processing Centre
Authorities must issue it within one year from the end of the financial year in which TDS returns are filed
Common triggers include TDS non-deduction, challan mismatch, delayed returns, or late TDS deposit
You can check, download, and respond to the TDS CPC notice entirely through the TRACES portal
Downloading the justification report and filing a correction return are the core steps in resolution
Section 200A of the Income Tax Act governs how the tax department processes TDS returns after filing. Once you submit a TDS return, the Centralised Processing Centre — managed through the TRACES portal — runs it through a system check to identify any discrepancies. That check is what generates the Section 200A intimation.
PAN errors, delayed filing, challan mismatches, and incorrectly calculated interest are the most frequent discrepancies the system flags. None of these require manual review — the CPC processes everything automatically, which is why the notice can arrive without any prior correspondence.
The department has a one-year window to issue a TDS notice under Section 200A, counted from the end of the financial year in which the TDS returns were filed. The intimation also doubles as a notice of demand under Section 156 of the Income Tax Act — but that doesn't always mean payment is required. Many times, it's simply a confirmation that your return was accepted as filed. That's the 200A intimation in its most benign form.
There's usually one clear cause behind every TDS CPC notice Section 200A. Here are the most common ones:
Non-deduction or short-deduction of TDS: The deductor either missed deducting TDS entirely or deducted less than required. A simple typo, wrong TDS rate, missed PAN-linked exemption, or an inoperative PAN can all trigger this. It happens more often than people admit.
Challan mismatch: When the TDS challan details don't match what's in the TDS return — wrong BSR code, incorrect challan serial number, wrong date, or keyed-in wrong amounts — the system flags it immediately during TDS processing under 200A.
Delayed filing of TDS returns: Any delay beyond the due date automatically triggers a Section 234E late fee of ₹200 per day of delay. The CPC computes this through the Section 200A processing — no separate notice needed.
Late deposit of TDS: TDS is due by the 7th of the following month — or the 30th of April for March. Miss that, and a TDS CPC notice follows. The interest clock starts ticking from the date of default.
When a Section 200A TDS notice arrives, it contains specific structured information — not a vague demand. Here's what you'll typically find:
TAN, financial year, and quarter
Summary comparing returned figures against processed figures
Interest under Section 201(1A)
Late fee under Section 234E
Net demand payable — or refund, if applicable
The annexure attached to the income tax notice 200A TDS goes deeper — it details row numbers, deductee information, and challan references. That's the section worth reading carefully before deciding how to respond.
There are multiple paths through TRACES, but here's the most direct route to access your TDS CPC notice Section 200A:
Log in to TRACES using your TAN
Go to the Communications tab
Select Inbox — your Section 200A intimations and notices will be listed here
Click View Details against the specific notice to open it
Click Request for Download Intimation or Request for Justification Report — these options are enabled for PAN error cases and TDS demand situations
A request number is generated after this step — wait 24 to 48 hours for processing
Go to Dashboard → Downloads → Requested Downloads, filter by request date or request number
Once status shows Available, click the row and hit HTTP Download to save the file
The justification report is particularly important when there's a demand. It maps every discrepancy the CPC identified — which makes the correction process significantly cleaner.
Assume you've received a default TDS notice under Section 200A. Here's the step-by-step process to close it:
Step 1: Identify the exact nature of the default in the 200A TDS intimation — short-deduction, short-payment, PAN error, challan mismatch. Download the justification report as described above.
Step 2: Reconcile against your filed returns. Cross-check challan details carefully — amounts, dates, BSR codes, serial numbers. Don't assume the system is wrong before you verify your own data.
Step 3: If the demand is correct and payment is due, pay through challan ITNS 281. If the demand is wrong, skip this step and move to correction.
Step 4: Log in to TRACES → go to Defaults → click the row for the relevant period → click Request for Correction. The type of correction option you select depends on what specifically needs fixing.
Step 5: File the correction return — either tagging the payment against the demand or correcting the specific details that caused the discrepancy.
Once the correction is processed, the default status in TRACES changes to Closed. That's your confirmation the Section 200A notice is resolved.
Both interest and late fee apply — but they're triggered by different situations, and it's worth keeping them separate in your head.
Late fee under Section 234E: ₹200 per day for every day the TDS return is delayed. This is capped at the total TDS amount — so it won't exceed what was deductible. The CPC computes this automatically during TDS processing under Section 200A.
Interest under Section 201(1A):
1% per month (or part of month) for delayed deduction
1.5% per month (or part of month) for delayed payment after deduction
One thing that catches people out — a part of a month counts as a full month. If you're one day late into a new month, you pay interest for the whole month. The CPC auto-computes both the Section 234E late fee and the Section 201(1A) interest during processing. Neither is negotiable at the notice stage.
A: Your response to a TDS CPC notice Section 200A is procedural — it doesn't require a written explanation or letter to the department. Log in to TRACES, download the justification report, identify the specific default, and either make payment through ITNS 281 or file a correction return depending on whether the demand is correct or not. The notice gets resolved once the correction is processed and the default status changes to Closed.
A: Log in to TRACES using your TAN, go to the Communications tab, and click on Inbox. Your Section 200A intimation and TDS notices will be listed there. Click View Details against the relevant notice to access the full breakdown of discrepancies, demand, and challan references.
A: No — there's no provision to directly revise the original TDS return. What you can do is file a correction statement to fix PAN errors, challan mismatches, or any other incorrect details. The correction return is the standard route for resolving defaults flagged in a TDS notice under Section 200A.
A: No fixed statutory deadline exists for responding to a Section 200A TDS notice. That said, interest under Section 201(1A) accrues every month — including for part months — so delaying your response directly increases your liability. Responding as quickly as possible after downloading the justification report is the practical approach.
A: No. The Section 234E late fee cannot be waived at the CPC level or through the TRACES portal. If you believe the delay was caused by genuine technical issues, the only recourse is filing an appeal before the Commissioner (Appeals) under Section 246A of the Income Tax Act.
A: Interest under Section 201(1A) is calculated from the date the tax was deductible to the date of actual payment. The rate is 1% per month for delayed deduction and 1.5% per month for delayed payment. A key point — even one day into a new month is treated as a full month for interest calculation purposes. The CPC computes this automatically during TDS processing under 200A.
A: The demand stays outstanding on record. It can be adjusted against future refunds you're entitled to. In persistent cases, recovery action may follow. Ignoring a TDS CPC notice Section 200A is not a safe option — the interest keeps accumulating and the default remains visible on TRACES against your TAN.
A: A Section 200A intimation is a system-generated communication that informs you about the outcome of TDS return processing — it can be a simple acceptance or it can carry a demand. When it carries a demand, it also functions as a notice of demand under Section 156 of the Income Tax Act. Not every 200A intimation requires payment — some are just confirmations that the return was accepted as filed.
A: The justification report is a detailed document available on TRACES that maps every discrepancy the CPC found while processing your TDS return. For any TDS CPC notice carrying a demand, the justification report is essential — it shows exactly which rows, deductees, or challans are causing the default. Without reviewing it, filing a correction return becomes guesswork.
A: TDS must be deposited by the 7th of the month following the month in which it was deducted. For the month of March, the due date is extended to the 30th of April. Missing either of these dates triggers late deposit interest under Section 201(1A) and increases the likelihood of receiving a TDS notice under Section 200A.
Your email address will not be published. Required fields are marked *