ITR Processing Held Under Risk Management: What to Do When Your Return is Flagged

You filed your client's return months ago. E-verification was successful. The acknowledgment is in hand. But the processing status on the portal stubbornly reads: "Your return is being processed. It has been selected under Risk Management Strategy of the department."

This status message causes anxiety for clients and frustration for CAs. What does it mean? What happens next? Can you do anything about it?

This guide answers every practical question about ITR processing held under risk management, based on current departmental practices, published guidelines, and the experience of thousands of CA practitioners.

What "Processing Held Under Risk Management" Means

The CASS/Risk Management System

The Income Tax Department uses a Computer Aided Scrutiny Selection (CASS) system — an AI-driven risk management engine that automatically analyzes every filed return for potential discrepancies, risk indicators, and anomalies.

When a return is "held under risk management," it means:

1. The CPC in Bengaluru has received the return
2. Initial processing (computation of tax) has been completed or is in progress
3. The CASS system has flagged the return for potential risk
4. The return is held in a queue for further review before the CPC issues the Section 143(1) intimation

Important clarification: Being flagged does NOT automatically mean scrutiny. The return may be:

• Released after review (most common outcome)
• Selected for limited scrutiny
• Selected for complete scrutiny
• Subject to verification of specific claims before processing

The Difference Between "Held" and "Selected for Scrutiny"

Status	Meaning	Outcome
Processing held under risk management	Return flagged by CASS for review	May be released or selected for scrutiny
Selected for scrutiny u/s 143(3)	Scrutiny notice issued	Detailed assessment proceedings begin
Processing completed	CPC has issued 143(1) intimation	Assessment at CPC level is done

The "held" status is an intermediate stage. Many returns that are held are eventually released and processed normally.

Why Returns Get Flagged

The CASS system evaluates returns against multiple risk parameters. While the exact algorithm is not public, the following triggers are well-established based on CBDT guidelines, RTI responses, and practitioner experience:

1. High Deductions Relative to Income

Returns claiming deductions under Chapter VI-A (80C, 80D, 80G, 80E, 80GG, etc.) that are disproportionately high relative to gross total income are flagged. Specific triggers include:

• Total deductions exceeding 50-60% of gross total income
• Section 80G donations exceeding 10-15% of gross total income
• Section 80GG rent deduction claimed when HRA is also received
• Unusual combinations of deductions that suggest optimization beyond genuine claims

2. Large Refund Claims

Refund claims, especially those exceeding Rs 5-10 lakh for individuals or Rs 50 lakh for companies, are almost always flagged. The risk parameters include:

• Refund amount exceeding 20-25% of total tax paid/TDS
• First-time large refund claim
• Sudden spike in refund compared to prior years
• Refund claimed due to brought-forward losses set off

3. AIS/TIS Mismatches

When the declared income in the ITR does not match the information in AIS/TIS:

• Income reported by third parties (banks, mutual funds, employers) not reflected in ITR
• Capital gains from securities transactions not matching SFT data
• Interest income from fixed deposits not matching bank-reported data
• Rent received as reported by tenants not matching declared rental income

4. Unusual Income Patterns

• Sudden and significant increase in income compared to prior years
• Large cash deposits not commensurate with declared income
• Significant agricultural income claimed (especially in states where agriculture is not predominant)
• Income from foreign sources without corresponding FEMA disclosures

5. Historical Flags

• Previous returns of the same PAN had issues (demands, penalties, search/survey)
• PAN associated with a group that is under investigation
• Connected PANs (family members, related entities) flagged for similar issues

6. Information from External Sources

• SFT (Statement of Financial Transactions) data showing high-value transactions
• Property registration data showing purchases inconsistent with declared income
• International transaction data from treaty partner countries
• Information from surveys, searches, or investigations involving the assessee or connected parties

The SMS and Email Alerts

When a return is flagged, the taxpayer typically receives:

SMS: "Your ITR for AY 2023-24 is under processing. It has been identified under Risk Management Strategy. Please ensure all details are correct."

Email: A more detailed notification referencing the risk management selection, sometimes specifying the broad category of risk identified.

What to Tell Clients When They Receive This Alert

Recommended response to client:

"This is a routine process. The Income Tax Department's automated system flags a percentage of all returns for additional verification. Being flagged does not mean there is a problem with your return. In most cases, the return is released and processed normally within a few weeks. We have filed your return correctly based on your actual income and supporting documents. If the department requires any additional information, we will handle it."

What NOT to say:

• Don't say "your return has been selected for scrutiny" — it hasn't been, yet
• Don't say "there's nothing to worry about" without context — some clients may have genuine issues
• Don't speculate about the reason for flagging unless you know

Timeline: How Long Does It Take?

Based on observed patterns across recent assessment years:

Phase	Typical Duration
Return filed to "held" status appearing	1-4 weeks
"Held" status to resolution	2-6 months
If released: "Held" to 143(1) intimation	2-8 weeks after release
If selected for scrutiny: Notice u/s 143(2)	Within the time limit for issuing 143(2) notice

Key Deadline for Scrutiny Selection

The AO must issue a scrutiny notice under Section 143(2) within 3 months from the end of the financial year in which the return was filed (as per the amended time limits). For returns filed in FY 2025-26, the 143(2) notice must be issued by 30th June 2027.

If this deadline passes without a 143(2) notice, the return cannot be selected for scrutiny (subject to reassessment provisions).

What Happens Next: The Three Outcomes

Outcome 1: Return Released and Processed (Most Common)

The risk management review concludes that no action is needed. The return is released to normal processing, and the CPC issues a Section 143(1) intimation. This is the most common outcome — the vast majority of flagged returns are eventually released.

What you'll see: The portal status changes from "processing held" to "processed" and the 143(1) intimation becomes available for download.

Outcome 2: Limited Scrutiny

The return is selected for limited scrutiny on a specific issue. The AO issues a Section 143(2) notice with the scope limited to the identified risk area. For example:

• "Verify the claim of deduction under Section 80G"
• "Verify the source of cash deposits during demonetization period"
• "Verify the capital gain computation on sale of property"

What you'll see: A notice under Section 143(2) specifying the limited scope of inquiry.

Outcome 3: Complete Scrutiny

The return is selected for complete scrutiny, where the AO examines the entire return. This is the least common outcome for risk-management flagged returns (complete scrutiny is more often triggered by search/survey findings or specific intelligence inputs).

What you'll see: A Section 143(2) notice without scope limitation.

What CAs Can Do Proactively

Before Filing: Prevention Is Better Than Flagging

1. Reconcile AIS before filing. Ensure every item in the AIS is either included in the return or has feedback submitted explaining the discrepancy.

2. Document high deductions. If claiming large deductions, ensure supporting documents are organized and readily available — don't wait for a notice to gather proofs.

3. Explain unusual items in the return. Use the "Additional Information" or notes section of the ITR to proactively explain:

   • Sudden increase in income
   • Large capital gains or losses
   • Unusual deduction claims
   • Agricultural income claims

4. Verify TDS credits. Ensure Form 26AS/AIS TDS data matches the return. Mismatches are a primary flagging trigger.

5. Review prior year flags. If the client's return was flagged in a prior year, pay extra attention to the same issue areas.

During the "Held" Period

1. Don't panic — and don't call the CPC. The CPC does not take phone calls about risk management selections. Calling the helpline will only yield generic responses.

2. Keep documents ready. Organize all supporting documents for the return in a structured folder — if scrutiny follows, you'll need to respond quickly.

3. Monitor the portal. Check the processing status weekly. Note the dates of any status changes.

4. File an e-Nivaran grievance if unreasonably delayed. If the return has been held for more than 6 months without any communication, file a grievance requesting status update.

5. Do NOT file a revised return to "fix" the flagging. Filing a revised return while the original is under risk management review can create complications. Only file a revised return if there is a genuine error to correct.

If Selected for Scrutiny

1. Read the 143(2) notice carefully. Identify:

   • Is it limited or complete scrutiny?
   • What specific issues are raised?
   • What documents are requested?
   • What is the deadline for response?

2. Respond within the deadline. Requests for adjournment should be genuine and limited — frequent adjournments create negative impressions.

3. Provide only what is asked. In limited scrutiny, the AO should not expand the scope beyond the identified issues. If the AO attempts to inquire into matters outside the scope, object in writing citing CBDT Instruction No. 5/2016 which restricts expansion of limited scrutiny without prior approval.

4. Maintain written records. Every submission to the AO should be on record — avoid oral explanations without written follow-up.

The CBDT Guidelines on Scrutiny Selection

CBDT periodically issues guidelines for scrutiny selection. Key points from recent instructions:

CBDT Instruction No. 1/2015 and Updates

• CASS parameters are reviewed annually
• Returns are scored on a composite risk score based on multiple parameters
• The top-scoring returns within each risk category are selected
• Compulsory scrutiny criteria include: search cases, survey cases, returns with international transactions above threshold, specific intelligence inputs

CBDT Instruction No. 5/2016 (Limited Scrutiny)

• Limited scrutiny must remain limited to the issues for which the case was selected
• AO cannot expand to complete scrutiny without prior approval of PCIT/CIT
• The approval process requires the AO to record specific reasons for expansion
• This instruction is your strongest weapon against scope creep during limited scrutiny

CBDT Guidelines on Faceless Assessment

All scrutiny assessments (except search/survey cases and international tax cases) are conducted through the Faceless Assessment Scheme. This means:

• No physical appearance before the AO
• All communication through the e-Assessment portal
• Responses submitted electronically with document uploads
• Video conferencing for personal hearing if requested

Common Mistakes CAs Make with Flagged Returns

1. Filing revised returns reactively. Don't file a revised return just because the original was flagged. Revised returns during risk management review can trigger additional scrutiny.

2. Ignoring the 143(2) deadline. If the limitation for 143(2) notice passes without a notice, the client is safe from scrutiny. Track this deadline carefully.

3. Over-sharing in voluntary submissions. Some CAs proactively submit documents to the AO before being asked. This can inadvertently open new issues. Wait for specific requests.

4. Allowing scope creep in limited scrutiny. If the AO asks about issues beyond the limited scrutiny scope, object immediately in writing. Cite CBDT Instruction 5/2016.

5. Not obtaining the reasons for scrutiny selection. The assessee has a right to know the reasons for selection. Request the "reasons recorded" — this helps you prepare targeted responses.

How AI Tools Can Help

AI-powered tools bring significant advantages when dealing with risk management flags and subsequent scrutiny:

• Pre-filing risk assessment: AI can analyze a return before filing and flag potential risk parameters that may trigger CASS selection, allowing CAs to proactively address or document these items.
• AIS reconciliation automation: AI can compare AIS data against the client's books and highlight every discrepancy, reducing the risk of mismatch-based flagging.
• Scrutiny response drafting: When a 143(2) notice arrives, AI can analyze the specific issues, research relevant case law, and draft comprehensive responses with legal citations.
• Scope monitoring: AI can track the AO's queries against the limited scrutiny scope and alert the CA if the AO appears to be exceeding the authorized scope.

TaxNoticeAI's risk analysis engine can evaluate a return's risk profile before filing and help CAs prepare proactive documentation. When scrutiny follows a risk management flag, TaxNoticeAI generates defense responses backed by verified legal citations from our corpus of over 2,900 legal documents.

Key Takeaways

1. "Processing held under risk management" is an intermediate status — not a scrutiny selection
2. Most flagged returns are eventually released and processed normally
3. Common triggers: high deductions, large refunds, AIS mismatches, unusual income patterns
4. Do not file revised returns reactively or make voluntary submissions during the "held" period
5. Track the Section 143(2) limitation deadline — if it passes without notice, the client is safe from scrutiny
6. In limited scrutiny, guard against scope creep — cite CBDT Instruction 5/2016
7. Pre-filing AIS reconciliation and proactive documentation are the best preventive measures
8. Keep clients informed but calm — the "held" status resolves favorably in the majority of cases