Why are Indian statutory updates so scattered?

Indian statutory changes arrive across MCA, CBDT, CBIC, RBI, and SEBI, each on its own site in its own format. Here is why that scatter causes missed and misread changes, and how a single updates feed that links to the official source and the underlying law fixes it for CS and CA teams.

In this guide
Answer firstVerified 7 August 2026

Indian statutory updates are published across separate regulator sites, MCA, CBDT, CBIC and GST, RBI, and SEBI, each in its own format and cadence. That scatter causes two failures: real changes are missed, and forwarded summaries are misread. A single updates feed that shows what changed across sources, links to the official document behind each change, and connects to the underlying Act lets a team see the change and verify it in one place instead of hunting across sites.

Why are Indian statutory updates scattered?

There is no single official place where Indian statutory changes appear. A company secretary tracking company law reads MCA. The same person handling tax reads CBDT and CBIC. If the company is listed, add SEBI. If it borrows or lends in regulated ways, add RBI. Each site has its own layout, its own numbering, and its own cadence, and none of them talks to the others.

So the work becomes a patrol. Check five sites on a rhythm, or wait for someone to forward a summary. Both routes have a failure mode, and the failure is where the cost lives.

What failures does source scatter cause?

Scatter fails in two directions, and most compliance misses trace back to one of them.

FailureHow it happens
Missed changeA regulator posts a change; the patrol slips that week; nobody sees it until a deadline
Misread changeA forwarded summary is acted on without opening the official document, so the scope or date is wrong

The two are linked. The busier the patrol, the more tempting the forwarded summary becomes, and the summary is exactly the artefact that drops the effective date and the scope. Fixing scatter has to address both: surface the change, and keep the source next to it.

Is a missed MCA circular the same problem as a wrong GST date?

Same cause, two symptoms. The missed circular is the patrol failure. The wrong GST date is the summary failure. Both start from the fact that the official document lived on a different site from the one you checked that week.

Which regulators publish statutory updates?

For most Indian compliance work, the recurring sources are a known set.

  • MCA: company law circulars, notifications, and form changes.
  • CBDT: direct-tax circulars, notifications, and portal changes.
  • CBIC and GST: indirect-tax notifications, circulars, and return changes.
  • RBI: notifications, circulars, and master directions for banking and NBFC matters.
  • SEBI: circulars and regulation amendments for securities and listed entities.

A role that owns one source has a manageable patrol. A role that owns three or more is where the single-feed argument becomes hard to ignore.

Do BSE and NSE circulars sit in the same scatter?

For a listed company, yes. Exchange circulars add two more places to check on top of SEBI. They are still official documents with a number and date; they are not a reason to skip the SEBI circulars listing.

What does one updates feed mean?

"One place" is easy to misunderstand as a place that replaces the regulators. It should mean the opposite: a front door that gathers what changed and then sends you to the authority.

  1. See what changed: one feed across sources, in one format, on one screen.
  2. Open the source: a link to the official document behind each change, not a rewritten summary.
  3. Read the law: a path from the change to the Act, rule, or regulation it touches.

Should I trust a statutory summary first?

No. The discipline that makes a single feed trustworthy is that it points to the source rather than replacing it. A summary can help you triage, but the decision has to rest on the official document, because that is where the number, date, and scope are exact.

This is why a feed that links out is more useful than one that only paraphrases. It removes the hunting without asking you to trust a paraphrase over the regulator. How to test a forwarded claim is in how to verify an Indian regulatory update.

How do I verify a statutory update?

  1. Match the change to an official document on MCA notifications, CBDT latest news, CBIC Central Tax notifications, RBI notifications, or SEBI circulars.
  2. Read the number, date, and who and what it covers.
  3. Trace the change to the Act, rule, or regulation behind it.
  4. If it cannot be traced to an official document, treat it as a rumour.

Where can I read statutory updates together?

Complied AI is built around exactly this front door. It keeps statutory updates across MCA, CBDT, CBIC and GST, RBI, and SEBI in one updates feed, links each change to the official document behind it, and connects to the underlying law so you can read the source and the section together. The feed removes the hunting; the source links keep the authority where it belongs. For the research steps after you have the document, see how to trace an update to its Act section.

Practical checks

Common questions

Where are Indian statutory updates actually published?

They are published across separate regulator sites: the Ministry of Corporate Affairs for company law, CBDT and the Income Tax Department for direct tax, CBIC and the GST portal for indirect tax, the Reserve Bank of India for banking and NBFC matters, and SEBI for securities and listed entities. Each publishes in its own format and on its own schedule. There is no single official Gazette feed that covers all five.

Why is tracking statutory updates across those sources hard?

Because there is no single official feed across regulators. Each site has its own layout, notification numbering, and cadence, so a team either checks several sites on a rhythm or relies on forwarded summaries. The first is time-consuming and easy to let slip; the second is easy to misread. A CS who owns MCA, CBDT, and SEBI is already on three patrols.

Does a single updates feed replace the official MCA or CBIC site?

No, and it should not try to. A useful feed is a front door: it shows what changed across sources and then links straight to the official document and the underlying law so you verify the change on the source. The regulator sites remain the authority; the feed removes the hunting. Acting on the paraphrase instead of the PDF is how a due date gets misread.

Who benefits most from statutory updates in one place?

Company secretaries, chartered accountants, and in-house compliance teams who are responsible across more than one regulator. The more sources a role has to watch, the more a single feed that links to official documents saves, because the cost of scatter grows with each additional source. A role that owns only GST has a manageable patrol; a role that owns five does not.

We missed an MCA circular last month. Is that the scatter problem?

Usually yes. MCA posted a general circular; the weekly patrol of five sites slipped; nobody saw it until a form version or a due date had already moved. That is the missed-change failure. The other failure is acting on a forwarded summary of that circular without opening the PDF, so the class or the effective date is wrong.

How do I tell a real statutory change from a rumour?

Match it to an official document with a number and date on the regulator's site, then read who and what it covers. MCA issues general circulars, CBDT issues orders under section 119 of the Income-tax Act, 1961, CBIC issues numbered central tax notifications, RBI issues notifications, and SEBI issues circulars. If you cannot open that PDF, treat the claim as a rumour.

Is checking five regulator homepages once a week enough?

It is the minimum patrol, and it still fails when a mid-week circular moves a filing. A better habit is a single feed across MCA, CBDT, CBIC, RBI, and SEBI that links each item to the official document, reviewed on a fixed rhythm and tightened around results season or ROC week. Homepages hide circulars behind two more clicks.

Publication method

How this guide was prepared

This guide is published by the Complied AI research desk. Its source list and stated position were checked against the official records shown below on 7 August 2026.

Automation, including AI, may assist research, drafting and structure. It does not replace the official record or amount to an independent professional review. Read our editorial standards and corrections policy.

Verification path

Official sources used

Keep reading

Related guides