Skip to content
TThe Consulting Crew

Blogs · AI

The tax department runs on AI now: how returns get picked for scrutiny

By Ashish Kumar Sharma · Published 17 Aug 2026

A mismatch used to need an officer to find it. Now a system flags it in weeks — and the notice writes itself. Here is what the machines compare, and the discipline that keeps you off their lists.

Most business owners still picture tax enforcement as a person reading files. That person now arrives at step five. Steps one to four are software: data pulled from banks, registrars, marketplaces and your own filings; matched against your returns; scored; and queued. If you understand what gets compared, most notices stop being bad luck and start being predictable — which means preventable.

The income-tax side: AIS, CASS and the nudge machine

Three systems matter. The Annual Information Statement (AIS) compiles what third parties report against your PAN — bank interest, dividends, mutual fund and share trades, property purchases and sales, foreign remittances, large cash movements. CASS (Computer Assisted Scrutiny Selection) applies risk rules to filed returns and picks scrutiny cases with minimal human input. And the e-verification and e-campaign programmes send the SMS every filer has started seeing: “transactions in your AIS do not match your return.”

The practical consequence: the return is no longer the starting point. The data is. By the time you file, the department already holds a third-party picture of your year, and filing something materially different from that picture is what creates the flag. This is also why fixing an omission voluntarily — revised return or ITR-U — is treated so differently from being caught: the system rewards the version where you moved first.

The GST side: matching that runs without an officer

GST was born digital, so its enforcement is further along. What runs automatically today:

  • DRC-01B — GSTR-1 liability vs GSTR-3B payment. Declare sales in GSTR-1 and pay less in 3B beyond tolerance, and the portal itself demands an explanation within 7 days.
  • DRC-01C — ITC claimed in 3B vs ITC available in GSTR-2B. The spreadsheet argument (“my supplier will file soon”) now has a form number and a deadline.
  • IMS — every purchase invoice passes through accept/reject/hold, so your credit trail is explicit and timestamped.
  • E-way bill and e-invoice cross-checks — goods movement data compared against declared turnover; gaps between e-way bill values and GSTR-1 are a standard analytics report.
  • Network analysis — fake-ITC rings are detected by graph analytics across GSTINs, which is why a supplier three steps removed from you can still poison your credit chain. Vetting vendors is now self-defence; our ITC guide covers the discipline.

What actually triggers a flag

ComparisonThe pattern that gets flagged
GST turnover vs ITR receiptsHealthy sales in GSTR-3B, thin receipts in the ITR
TDS credits vs declared income26AS shows contract receipts the P&L never mentions
Bank SFT data vs incomeCash deposits or card spends out of line with declared income
GSTR-1 vs GSTR-3BLiability declared but not paid — DRC-01B territory
GSTR-2B vs GSTR-3BITC claimed ahead of what suppliers filed — DRC-01C territory
E-way bills vs declared salesGoods moving that the returns never sold
AIS securities data vs ITRShare and mutual fund trades missing from the return

The one-number discipline

Every defence against automated enforcement reduces to a single habit: one set of numbers everywhere. Sales in GSTR-1, GSTR-3B, the books and the ITR should tie. Purchases should reconcile to 2B monthly, not annually. TDS credits in 26AS should map to income actually booked. That is a bookkeeping cadence, not a heroic year-end exercise — it is precisely what a monthly books-and-MIS retainer exists to produce. Businesses with reconciled monthly books almost never meet the analytics engine; businesses with March-only books meet it on the engine's terms.

If a nudge or intimation has already arrived

Speed and accuracy beat panic. An e-campaign SMS wants feedback or an updated return; a DRC-01B/01C wants a portal reply in 7 days; an ASMT-10 or DRC-01 wants a documented reconciliation. In every case the reply that works is the one built on invoice-level workings — see our DRC-01 case study for what that looks like in practice. What does not work is silence: automated systems escalate on timers.

How we can help

Our retainers are built for the analytics era: monthly 2B reconciliation, GSTR-1/3B/books tie-outs, AIS review before every ITR, and notice handling with a first reply inside 48 hours when something does land. If you have received a mismatch SMS or a portal intimation, send it to us today — the clocks on these are short.

Got a notice you can't place? Run it through our free notice decoder →

This article is general information, not tax advice. Systems and thresholds evolve; confirm specifics for your situation before acting.

Let's get your compliance off your plate.

Tell us what you are dealing with. A short reply from someone who does this every day — no pitch, no obligation.

  • Reply within one working hour on WhatsApp
  • Fixed monthly fee, agreed before any work starts
  • No lock-in — month to month, 15 days’ notice

Request a callback

Two fields and you are done. We reply on WhatsApp within one working hour, Mon–Fri 10:00–19:00 and Sat 10:00–14:00 IST.

or message us on WhatsApp instead →
The Consulting Crew

A Strategy That Drives Results