MCA & ROC Filing | MCA21 Portal Integration

MCA21 submission inside the platform. SRN tracking that does not need a separate dashboard.

Direct MCA21 API submission for the forms where the API is live. DSC-signed PDF generation for forms still on the legacy upload. SRN, payment challan and acknowledgement capture happen on the same record. Rejections come back with the reason and the corrective action.

Start free trial Book a demo

How it works

From signed form to MCA21 SRN, on one screen.

Step 01

Form prepared in the platform

AOC-4, MGT-7, DIR-3 KYC, DPT-3, BEN-2, ADT-1, INC-22, MGT-14 and other prescribed forms are drafted from the underlying registers and the ledger.

Step 02

DSC sign-off captured

Director, CS or CA DSC applies to the form. The DSC details, certificate validity and signing timestamp are stored against the form record.

Step 03

MCA21 submission

Where the MCA21 API is live for the form, submission happens directly with the SRN returned to the platform. For legacy upload forms, a DSC-signed PDF is generated for upload, with the SRN captured back manually.

Step 04

Status, rejection, re-filing

SRN, MCA21 status, payment challan and any rejection reasons sit on the same record. Re-filing flows from the same draft after corrections, with the full audit trail of what was submitted and what came back.

What the system does

Capability, input, output.

Capability	Input	Output
Form preparation	Registers + ledger + master data	Pre-filled MCA21 form draft
DSC signing	Director / CS / CA DSC	Signed form with cert metadata
MCA21 API submission	Signed form + payment challan	SRN + acknowledgement
Legacy upload generation	Forms not yet on API	DSC-signed PDF for portal upload
Status feed	MCA21 SRN status	Approved / under-review / rejected
Re-filing flow	Rejection reason + corrected draft	Re-filed form with full trail

Form preparation

Input

Registers + ledger + master data

Output

Pre-filled MCA21 form draft
DSC signing

Input

Director / CS / CA DSC

Output

Signed form with cert metadata
MCA21 API submission

Input

Signed form + payment challan

Output

SRN + acknowledgement
Legacy upload generation

Input

Forms not yet on API

Output

DSC-signed PDF for portal upload
Status feed

Input

MCA21 SRN status

Output

Approved / under-review / rejected
Re-filing flow

Input

Rejection reason + corrected draft

Output

Re-filed form with full trail

Compliance + integrations

Submission with the audit trail attached.

Every form submitted to MCA21 carries the SRN, the signing DSC details and the supporting workpapers in one record. The audit trail across draft, sign-off, submission and acknowledgement is hash-chained for Rule 11(g).

Regulations we work within

IT Act 2000, Section 5

DSC-signed forms recognised as legal records.
Rule 11(g), Companies Act

Hash-chained audit trail across the filing.
MCA Form Schema

Form versions and validation rules updated centrally.

Connects to

MCA21 API submission and status feed
DSC providers eMudhra, Sify, NSDL e-Gov
Payment gateway MCA21 payment challan generation

MCA21 Portal Integration FAQ

What buyers ask.

Which MCA21 forms are submitted via API and which are legacy uploads?

The MCA21 V3 portal supports API submission for an expanding list including AOC-4, MGT-7 and many DIN-related forms. Forms not yet on V3 generate as DSC-signed PDFs for legacy upload, with SRN captured back. The platform tracks which forms are on which path so the user does not need to.

Multiple DSCs are needed (director plus CS plus CA). Is that handled?

Yes. The platform supports multi-DSC sign-off on a single form. Each signatory signs with their own DSC; the form record stores the certificate details, the role and the signing timestamp for each. The form submits only after all required signatures are present.

How are payment challans handled?

MCA21 fees are computed per form per entity. The platform generates the payment challan, captures the payment reference and attaches it to the form before submission. Payment is made through the MCA21 payment gateway in the same flow.

What if MCA21 is down?

API failures are logged with the response code. The platform retries automatically per the MCA21 retry policy. If the portal is in scheduled maintenance, the queue holds the submission and submits when the portal returns. Manual override is available where needed.

Related features

See an MCA21 submission inside the platform.

Pick a form from your last filing window. The platform shows the draft, the DSC sign-off, the payment challan and the MCA21 submission flow on one screen.