Income Tax Demand Notice 143(1): A Practical Reply Checklist for CA Firms

Every assessment season, CA firms across India see the same pattern: a client forwards an intimation, panics about the number at the bottom, and wants a reply sent the same day. Most of these are processing adjustments, not scrutiny, and they can be closed quickly if the team follows a fixed routine. This guide walks through that routine. For firms that handle the income tax demand notice 143 1 volume every year, AskSolique was built to cut the research and drafting time on exactly these cases.

What a Section 143(1) Intimation Actually Is

An intimation under section 143(1) is generated by the Centralised Processing Centre (CPC) after it processes a return. It is not an assessment order and it is not a scrutiny notice. CPC compares the return with the data it already holds, applies a limited set of permitted adjustments, and tells the taxpayer whether the result is a refund, a demand, or no change.

The permitted adjustments are narrow. They cover arithmetical errors, incorrect claims that are apparent from the return itself, disallowance of losses where the return was filed late, mismatches with Form 26AS, AIS or Form 16, and a few deduction-related checks. Because the scope is limited, a large share of these demands turn out to be avoidable once someone compares the return line by line with the intimation.

Before any of this, CPC usually sends a prior communication under section 143(1)(a) proposing the adjustment and giving the taxpayer 30 days to respond. Many demands arise simply because that earlier communication was ignored or missed in the client's inbox.

The First 30 Minutes: Triage Before Drafting

The fastest firms do not start by writing a reply. They start by classifying the demand. A simple triage sequence works well for most practices:

1. Confirm the document. Check that it is a genuine intimation by matching the DIN and verifying it on the e-filing portal. Clients sometimes forward phishing emails that copy the CPC format.
2. Read the computation table. The intimation shows two columns: "as provided by taxpayer" and "as computed under 143(1)". The difference between the two columns is where the demand comes from.
3. Identify the adjustment type. Is it a TDS credit mismatch, a deduction disallowed, interest under sections 234A/B/C, or a carried-forward loss rejected?
4. Check the 26AS and AIS. Most salaried-client demands trace back to TDS not reflected, an employer filing late, or income reported in AIS that the client forgot.
5. Note the deadline. The response window on the portal is usually 30 days. Missing it lets the demand stand and can lead to adjustment against future refunds.

Once the cause is clear, the decision becomes simple: agree, disagree, or partly agree with the demand.

Choosing the Right Response Route

The e-filing portal gives four broad options under "Response to Outstanding Demand": the demand is correct, the demand is partly correct, the taxpayer disagrees with the demand, or the taxpayer wants to pay. Each route needs different supporting material.

Demand is correct. If the adjustment is valid, the cleanest route is to pay through Challan 280 and record the payment details. Arguing a valid adjustment only creates more correspondence.

Disagree with demand. This is the route for TDS credit not given, double counting, or an adjustment that CPC made outside its permitted scope. The reply must name the exact reason from the portal's dropdown and attach evidence such as Form 16, Form 16A, the corrected 26AS or a challan copy. Keeping a consistent drafting structure helps here, and many teams start from a ready income tax notice reply format so that every associate cites facts, section and evidence in the same order.

Rectification under section 154. Where the error is in the processing itself, an online rectification request is often faster than disputing the demand. It is the right tool for mistakes apparent from the record, such as a TDS credit present in 26AS but ignored during processing.

Revised return. If the client's own return was wrong and the revision window is still open, filing a revised return can resolve the issue at source. This decision should be taken carefully, because a revised return replaces the original entirely.

Common Causes and How to Answer Them

TDS credit mismatch. The deductor may have quoted a wrong PAN, filed the TDS return late or not at all. The answer is to ask the deductor to file a correction statement, then request rectification once 26AS updates. A reply sent before the correction appears will usually be rejected again.

Deductions disallowed under Chapter VI-A. Claims under sections 80C, 80D or 80G get disallowed when they are not reflected in Form 16 or when the employer did not consider them. The reply should explain that the deduction was claimed directly in the return and attach proof of investment or payment.

Interest under sections 234A, 234B and 234C. These are mechanical. Check whether advance tax challans were matched correctly. If a challan was paid under the wrong assessment year or the wrong minor head, it may need to be corrected with the bank or the assessing officer.

Carried-forward loss rejected. Losses cannot be carried forward from a belated return. If the original return was filed on time, attach the acknowledgement and argue the point; if it was late, the adjustment is usually valid.

The old-to-new section question is also becoming relevant. With the new Act coming into force, teams are mapping familiar provisions to new numbering, and this guide to mapping old sections to the Income Tax Act 2025 is a useful reference when a reply needs to cite the correct provision.

When a Simple Reply Needs Legal Backing

Most 143(1) replies are factual. A minority are not. If CPC has made an adjustment that arguably goes beyond the "apparent from the return" limit, the reply becomes stronger when it cites how tribunals and high courts have treated similar adjustments. That is where research time balloons, because associates search across multiple sites, compare judgments and then check whether a ruling has been overturned.

A focused research tool helps. Searching through an income tax case law database for India by section and issue, rather than by keyword alone, lets the team find the governing decision quickly and quote it correctly. The time saved on one complex reply often pays for the subscription in a month.

For firms still deciding how far to take this, it helps to look at where AI genuinely saves time and where human review is still non-negotiable. This piece on AI for chartered accountants covers that balance honestly, and the checklist on what to check before adopting an AI tool in a CA firm is a sensible next read.

A Repeatable Workflow for the Practice

Firms that handle dozens of intimations a month benefit from a standard operating procedure. A practical version looks like this:

• Log every intimation in a tracker with client name, assessment year, demand amount, cause and deadline.
• Assign triage to a junior, with a fixed list of checks (DIN, computation table, 26AS, AIS, prior communication).
• Route disputes that need case law to a senior, and keep a library of past replies that worked.
• File responses on the portal, save the acknowledgement, and set a reminder to check whether the demand has been closed.
• Review the tracker monthly to spot repeat causes, such as one employer whose TDS filings are always late.

That last step is often missed. When the same cause appears across many clients, a single conversation with the deductor can prevent next year's demands altogether.

Final Word

A 143(1) demand is usually a data problem, not a legal dispute. Treat it as one: classify it, match it against the records, choose the right portal route and back the reply with evidence. Keep legal research for the cases that truly need it, and keep the drafting consistent so every reply reads the same regardless of who prepared it.

If your firm wants to see how AskSolique handles notice research and reply drafting on live client cases, please contact us to arrange a walkthrough.