Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
RPA bot

RPA MCA Filing Status Check: Know When an SRN Moves Without Checking Daily

For company secretaries, CS firms and group finance teams: track filed forms across companies and hear only when something changes.

A company secretary opening a box file in an office lined with almirahs

RPA MCA filing status check suits anyone tracking many filed forms at once. After filing, each form's SRN is checked on the MCA portal until it is approved, sent for resubmission or rejected. A CS firm with dozens of client companies can spend an hour a day on this.

A bot can look up each SRN on a schedule, compare the status with the last run and email only the changes. A resubmission request then reaches the right person the day it appears.

Here is how, with an illustrative example.

What checking SRNs by hand costs

Missed resubmission windows

A request for changes noticed too late.

Daily repetition

The same SRNs checked again and again.

Client questions

Clients ask for status before the firm knows it.

One tracker sheet

A spreadsheet only one person keeps current.

An example: a Kolkata CS firm

Take an illustrative firm handling filings for about 60 private companies. During annual filing season, a junior checked more than a hundred SRNs every morning.

One morning's SRN check

  • Annual return, Co 12Approved since the last run.Done
  • Financials, Co 7No change; not in the email.Pending
  • Director change, Co 31Resubmission requested; partner alerted.Mismatch
  • Share allotment, Co 4Status read, still under processing.Checked
  • Address change, Co 19Unchanged beyond the firm's expected time.Overdue
  • Lookup, Co 22Blocked run flagged for a person.Missing
The partner saw the resubmission request the morning it appeared.

The junior stopped checking every SRN and started working on the changes. The resubmission was corrected within the window, and clients received status updates before they asked.

Six box files, one pulled forward with an orange ribbon and a bell
Only the file that needed resubmission was pulled forward for the partner.

How the ROC filing tracker bot works

Step 1 of 5

A list of SRNs

Each filed form is a work item, added as you file.

  1. A list of SRNs: Each filed form is a work item, added as you file.
  2. Lookups by bot: Built in Vibe Studio to read each form's status.
  3. Only changes: Each status compared with the last run.
  4. Change email: Approvals, resubmissions and rejections listed.
  5. People decide: Partners act on changes; the bot never refiles.

Choosing a route for MCA SRN status checks

A shared tracker works when filings are few. Once several people file for many companies, a bot that reports changes keeps everyone on the same page without a daily ritual.

Manual tracking against an Apragya bot

FeatureManual trackingApragya RPA bot
ChecksEvery SRN, every dayScheduled lookups
What people readThe whole trackerOnly changes
ResubmissionsFound when checkedEmailed on the day
Blocked lookupsSilently skippedFlagged for a person
HistoryLast edit onlyRun history kept

Checked against public information on 16 September 2026.

What sets Apragya apart

Changes, not lists

Tracking keeps emails short.

Many companies

Filings for group companies or clients in one queue.

AI with review

An agent can draft the client update for approval.

Projects and tasks

Resubmissions can become tasks with owners.

Access by role

Partners and juniors see what they should.

Versioned bots

Update when the portal changes.

See our AI automation platform overview, the UiPath alternative guide and the government tender monitoring bot.

Getting started

  1. Gather the SRNs you are tracking and their companies.
  2. Decide who should hear about approvals and resubmissions.
  3. Build and test the bot on a handful of SRNs.
  4. Let the first run learn current statuses.
  5. Add new SRNs as each form is filed.

The MCA portal changes from time to time, so plan for the bot to be updated.

What it costs to start

Enterprise
Custom plan
RPA bots in Vibe Studio, with VPC or on-premise options
INR 7,999
Pro, a month
Up to 25 users, every enterprise app and the agent builder
Free
Up to 3 users
CRM, HR and Vendor Onboarding, to try the platform

MCA filing status bots, answered

Does the bot file forms?
No. Filing needs digital signatures and professional judgement, so it stays with your team.
What if the portal shows a CAPTCHA?
The run is marked as needing a person, who can clear it and save the session for later runs.
Is there a ready-made MCA bot?
No. It is built and tested for your use in Vibe Studio and updated when the portal changes.
Where does the bot run?
On the platform or on a Tenant Runner inside your office network, which connects out to Apragya so no inbound firewall rule is needed.
How do we add new filings?
Each new SRN is added to the bot's work queue as the form is filed, with the company name, so the next run picks it up.
Can clients see status?
An agent can draft updates, and a person approves them before they are sent.
What does it cost to start?
RPA bots in Vibe Studio come with the Enterprise plan, which is priced for your volume; talk to our sales team. Pro, at INR 7,999 a month for up to 25 users, includes every enterprise app and the no-code agent builder, and the free plan covers up to 3 users with CRM, HR and Vendor Onboarding.

Hear about resubmissions the day they happen

Add ten SRNs to a bot and let it watch them for a month.