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.
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 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.
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.
- A list of SRNs: Each filed form is a work item, added as you file.
- Lookups by bot: Built in Vibe Studio to read each form's status.
- Only changes: Each status compared with the last run.
- Change email: Approvals, resubmissions and rejections listed.
- 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
| Feature | Manual tracking | Apragya RPA bot |
|---|---|---|
| Checks | Every SRN, every day | Scheduled lookups |
| What people read | The whole tracker | Only changes |
| Resubmissions | Found when checked | Emailed on the day |
| Blocked lookups | Silently skipped | Flagged for a person |
| History | Last edit only | Run 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
- Gather the SRNs you are tracking and their companies.
- Decide who should hear about approvals and resubmissions.
- Build and test the bot on a handful of SRNs.
- Let the first run learn current statuses.
- 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
MCA filing status bots, answered
Does the bot file forms?
What if the portal shows a CAPTCHA?
Is there a ready-made MCA bot?
Where does the bot run?
How do we add new filings?
Can clients see status?
What does it cost to start?
Hear about resubmissions the day they happen
Add ten SRNs to a bot and let it watch them for a month.