Chat on WhatsApp

CBDT's 6 Compulsory Scrutiny Triggers for FY 2026-27: Which Small-Business ITRs Get a 143(2) Notice

CBDT issued its compulsory-scrutiny guidelines for FY 2026-27 on 4 June 2026, listing six parameters (CS-01 to CS-06) that decide which FY 2025-26 returns face complete scrutiny. Selection is not random, and the Section 143(2) notice deadline is 30 June 2026. Here is what realistically affects an SMB.

9 July 2026 8 min read
Key Takeaways
  • CBDT prescribed six parameters (CS-01 to CS-06) on 4 June 2026 under F.No. 225/56/2026/ITA-II for complete scrutiny of FY 2025-26 returns (Taxguru, 2026).
  • Selection is not random — a return is picked only if it falls under a specific parameter; AIS/SFT-based returns are not auto-scrutinised unless they hit CS-06.
  • The recurring-addition trigger (CS-05) starts above ₹50 lakh in the eight metro charges or ₹20 lakh elsewhere; the Section 143(2) notice deadline is 30 June 2026.
Income tax filing dashboard with ITR documents and verification steps for CBDT's Compulsory Scrutiny Triggers for

CBDT issued its compulsory-scrutiny guidelines for FY 2026-27 on 4 June 2026 under F.No. 225/56/2026/ITA-II, listing exactly which returns filed in FY 2025-26 get picked for complete scrutiny — the first such list under the new Income Tax Act, 2025 (Taxguru, 2026). The good news for most small businesses: scrutiny selection is not random, and a normally-filed return rarely qualifies.

This guide translates the six parameters into plain English, flags which realistically touch an SMB, and explains the 30 June 2026 notice deadline so you know when you are in the clear.

Key Takeaways
  • CBDT prescribed six parameters (CS-01 to CS-06) on 4 June 2026 for complete scrutiny of FY 2025-26 returns.
  • Selection is not random — a return is picked only if it falls under a specific parameter.
  • The recurring-addition trigger (CS-05) starts above ₹50 lakh in the eight metro charges, ₹20 lakh elsewhere.
  • A Section 143(2) notice for FY 2025-26 returns must be served by 30 June 2026.

What did CBDT announce for compulsory scrutiny in FY 2026-27?

CBDT laid down the exact conditions under which returns already filed will be taken up for complete scrutiny during FY 2026-27, along with the internal deadlines for tax officers to compile case lists (CAclubindia, 2026). Consolidated CS-05 and CS-06 lists had to reach the Directorate of Income-tax (Systems) by 15 June 2026 through the prescribed hierarchy.

The point of publishing this every year is transparency: it tells taxpayers the objective triggers, so an ordinary return that avoids them is not exposed to discretionary picking.

What are the six scrutiny parameters (CS-01 to CS-06) in plain English?

CS-01 covers survey cases under Section 133A; CS-02 covers search and requisition under Sections 132/132A; CS-03 covers reassessment under Section 148; CS-04 covers cancelled 12A/12AB/10(23C) registrations still claiming exemption; CS-05 covers large recurring additions; and CS-06 covers specific tax-evasion information from enforcement agencies (A2Z Taxcorp, 2026).

Compulsory scrutiny triggers, FY 2026-27A return is picked only if it hits one of theseCS-01 Survey 133AOn-site survey casesCS-02 Search 132Search / requisitionCS-03 Reassess 148Reopened returnsCS-04 ExemptionCancelled 12A/80G etc.CS-05 Recurring add.>₹50L metro / ₹20LCS-06 Evasion infoAgency intelligenceBlue = event-driven · Amber = exemption · Red = amount / intelligence based
Source: Taxguru and A2Z Taxcorp on CBDT F.No. 225/56/2026/ITA-II, June 2026.

Which of these triggers realistically affect a small business?

For a typical SMB, CS-01 to CS-03 only apply if you were already surveyed, searched, or reopened — events you would know about. CS-04 hits trusts and NGOs with cancelled registrations. That leaves CS-05 (very large recurring additions) and CS-06 (specific evasion intelligence) as the practical ones — and both need something already unusual in your history to fire.

If you have had a past addition upheld on appeal, or you have received enforcement-agency attention, get professional help early. Our income-tax notice handling team drafts responses and represents you through the assessment.

What is the Section 143(2) deadline and why does it matter?

For returns filed during FY 2025-26, the department must serve the Section 143(2) notice — the one that formally opens scrutiny — by 30 June 2026 (Taxguru, 2026). If that date passes without a notice landing in your registered email and the e-filing portal, your return cannot be taken up for complete scrutiny for that year. It is a hard cut-off worth diarising.

How does the raised ₹50 lakh / ₹20 lakh recurring-addition threshold change things?

CS-05 fires when an earlier confirmed or upheld addition on a recurring question of law or fact exceeds ₹50 lakh in the eight metro charges (Mumbai, Delhi, Chennai, Kolkata, Bengaluru, Hyderabad, Ahmedabad, Pune) or ₹20 lakh elsewhere; the metro limit was doubled from ₹25 lakh in June 2025 (Taxguru, 2026). The higher floor keeps mid-sized recurring disputes out of automatic scrutiny.

What is NOT picked for compulsory scrutiny?

Returns filed in response to Section 142(1) notices linked purely to AIS, SFT, or CPC-TDS data are not taken up for compulsory scrutiny unless they also fall under CS-06. So an AIS-mismatch nudge, on its own, does not put you in the complete-scrutiny bucket. Reconcile it, respond, and move on.

How should an SMB prepare if it receives a 143(2) notice?

Read which parameter is cited, gather the specific records that support the flagged item, and respond within the timeline through the faceless portal. Do not ignore it — a non-response invites a best-judgement assessment. Keeping clean, reconciled books through the year with bookkeeping support turns a scrutiny notice from a scramble into a document-retrieval exercise. For filing itself, our business ITR filing service keeps the return defensible from the start.

What should you verify before using this Income Tax guide?

Before acting on cbdt's 6 compulsory scrutiny triggers for fy 2026-27, verify the current rules or platform behavior with the Income Tax Portal. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.

Use this article as a working checklist, then confirm forms, due dates, AIS or Form 26AS data, regime rules, and filing instructions. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.

CheckpointWhy it mattersWhere to confirm
Current rule or platform statusLimits, forms, policies, and APIs can change after a blog update.Income Tax Portal
Your exact business caseA local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step.Documents, invoices, campaign data, analytics setup, or workflow logs
Implementation evidenceThe safest filing decision is backed by proof, not memory or screenshots from an old setup.Portal acknowledgement, dashboard export, invoice sample, test lead, or error log

How do we apply this in real business work?

We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.

A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.

When should you get expert review?

Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.

How often should this be rechecked?

Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.

What is the fastest safe way to decide?

Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.

What can go wrong if you skip verification?

The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.

What evidence should you keep after making the change?

Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.

This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.

  • Date checked: record when the official source, dashboard, or portal screen was reviewed.
  • Business context: note the entity, state, product, campaign, property, or workflow affected.
  • Proof of action: save the acknowledgement, report export, test result, or live URL.
  • Owner: assign one person to re-check the item when rules, tools, or business volume change.
Verification workflowUse this loop before changing money, tax, reporting, or customer communication.1234Check sourceMatch recordsTest actionSave proof
Repeat this check whenever rules, platform settings, business volume, or ownership changes.

Which next step should you take after reading this?

Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with Income Tax Notice Handling, Business ITR Filing, and Bookkeeping Services. Then update the decision only after the official source and your own records agree.

Frequently asked questions

What are the six compulsory-scrutiny parameters for FY 2026-27?

They are CS-01 survey cases under Section 133A, CS-02 search or requisition under 132/132A, CS-03 reassessment under Section 148, CS-04 cancelled 12A/12AB/10(23C) registrations still claiming exemption, CS-05 large recurring additions, and CS-06 specific tax-evasion information from enforcement agencies. A return is taken up only if it falls under one of these.

Will filing my ITR normally trigger scrutiny?

No. Selection is not random. Returns are picked only if they fall under one of the six parameters. Returns filed in response to Section 142(1) notices linked purely to AIS, SFT, or CPC-TDS data are not taken up for compulsory scrutiny unless they also meet parameter CS-06. An ordinary, reconciled return is not exposed.

What is the deadline for the tax department to send a scrutiny notice?

For returns filed during FY 2025-26, the Section 143(2) notice must be served by 30 June 2026. Consolidated CS-05 and CS-06 case lists had to reach the Directorate of Income-tax (Systems) by 15 June 2026 through the prescribed hierarchy. If that date passes with no notice, your return cannot be taken up for complete scrutiny.

How much does a recurring addition have to be to trigger CS-05?

A confirmed or upheld recurring addition on a question of law or fact must exceed ₹50 lakh in the eight metro charges (Mumbai, Delhi, Chennai, Kolkata, Bengaluru, Hyderabad, Ahmedabad, Pune) or ₹20 lakh in other charges. The metro limit was doubled from ₹25 lakh in June 2025, keeping mid-sized disputes out of automatic scrutiny.

Let's Talk

Let's talk about your business.

Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.

  • Free 30-minute call
  • A plan built around your goals
  • No obligation, no pressure
  • Your own account manager

By submitting, you agree to our privacy policy. We'll never spam you.