June 10, 2026

Intimation Under Section 143(1): What to Do When a 123 Section Deduction is Questioned

Tax filing feels like crossing a finish line. The numbers go in, the acknowledgement comes through, and life moves on. Then, one ordinary day, an email arrives from the Income Tax Department, and that feeling of being done disappears instantly.

The first reaction for most people is worry. Before that thinking goes any further, here is what is actually happening and what needs to be done.

An Intimation is Not What Most People Think

There is a difference between an intimation under Section 143(1) and a scrutiny notice that most taxpayers never learn until one of them lands in their inbox.

A scrutiny notice means a tax officer has decided to examine the return closely. That is a more involved process with its own timeline and requirements.

An intimation under Section 143(1) is not that.

When a return is filed, it goes into an automated processing system at the Central Processing Centre. No human officer reviews it at this stage. The system simply checks the figures declared in the return against records the department already holds. Salary and TDS data from employers. Interesting information from banks. Investment and income details reported by financial institutions.

When the numbers match, a clean intimation goes out confirming the return as processed. When something does not line up, a flagged intimation goes out pointing to the specific discrepancy and asking the taxpayer to either agree with the department’s computation or explain why the return figure is correct.

Nobody is being singled out. The system found a number it could not reconcile and is asking for a response.

One important note on timing. For returns filed for FY 2025-26, the department can issue an intimation under Section 143(1) up to nine months from the end of the financial year in which the return was filed. For a return filed in July 2026, that window runs until December 31, 2026.

Why a 123 Section Deduction Gets Questioned

Deductions are among the most common reasons an intimation flags a return.

When a taxpayer claims a 123 section deduction, the automated system checks whether the claim can be verified against data it holds. If the investment details reported by a financial institution do not match what was declared in the return, or if the deduction amount cannot be confirmed from available records, the system raises a query.

This happens for several reasons. An employer may have reported a different figure in Form 16. A bank or financial institution may not have submitted updated records in time. In some cases, the return itself contains a data entry error that creates the mismatch.

None of these automatically means the deduction was wrong. It simply means the system could not verify the claim from available records.

Read the Document Before Anything Else

The most common habit when an intimation arrives is either handing it to a CA without reading it first or setting it aside because it feels too complicated to deal with immediately. Both slow things down unnecessarily.

The document is not written in impossible language. It shows three things clearly. What was declared in the return? What the system computed. And the gap between the two.

When a 123 section deduction has been questioned, the intimation will identify the specific line item, the amount disallowed or adjusted, and the resulting tax demand or difference. Note the exact figure being disputed before doing anything else.

Pull Out the Original Documents

Once the disputed figure is clear, gather the records that supported the deduction when the return was originally filed:

  • Life insurance premium receipts or policy payment certificates
  • PPF passbook showing contributions made during the year
  • ELSS investment certificates or mutual fund statements
  • School tuition fee receipts for children if claimed
  • Form 16 from the employer confirming deductions reported
  • Form 26AS for FY 2025-26 to verify what was officially reported to the department

Compare these against what was declared in the return. Either the return had an error that needs correcting, or the return was accurate, and the system was working with incomplete data. One of those two will become clear once the documents are in front of you.

Taking the Right Next Step

If the review shows the return had an error, a rectification request under Section 154 is the correct path. This allows the figures to be corrected and a revised computation submitted. For FY 2025-26 returns, this option stays available for four years from the end of the financial year in which the intimation was received.

If the documents confirm the return was right, log into the income tax e-filing portal, go to pending actions, locate the intimation under Section 143(1), and submit a response with the supporting documents attached. State clearly why the 123 section deduction was valid. Walk through the figures. Let the documents carry the argument rather than relying on lengthy written explanations.

If the intimation is correct and additional tax is genuinely owed, paying it promptly is the most sensible decision. Interest under Sections 234B and 234C continues building on unpaid tax from the original due date. A manageable demand left unaddressed grows into a larger one over time.

The Response Window Does Not Wait

Intimations under Section 143(1) come with a response deadline of thirty days from the date mentioned on the document itself.

Thirty days sounds like enough time. It moves faster than expected when documents need gathering, and the portal is unfamiliar. Starting the document review within the first week of receiving the intimation leaves breathing room to put together a proper response without a deadline closing in from behind.

A questioned 123 section deduction that receives a clear documented response within the window almost always resolves without escalating further. Left unaddressed, it becomes the starting point for follow-up proceedings that are more time-consuming and more stressful than a simple online response would ever have been at the start.

About the author 

Kyrie Mattos


{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}