MCA-21 V3, Six Months In: The Real-World Issues Practising CS Are Still Working Around

The MCA-21 V3 portal's broad rollout completed across major form sets in early 2025. The headline migration issues — DSC re-registration, form rejection on legacy data, downloads stuck, dashboard not updating — were largely resolved through 2025 patches. Six months into steady-state operation, a quieter set of operational frictions remains. For the practising CS, the platform is workable; the design choices and the residual quirks are worth knowing. This article is the honest field report.

What's working well

Pre-fill from master data. Director details, company master data, registered office, paid-up capital — auto-populate cleanly.
Pre-validation before payment. Most schema-level errors are caught at the form level rather than at the SRN.
Dashboard. The user dashboard surfaces filing status, payment history, and pending submissions reasonably well.
Bulk operations. Aggregated views for multi-entity professionals have improved.
Mobile-friendly access for tracking (filings still desktop-friendly only).

What's still friction

DSC quirks

DSC re-registration on V3 is required after certain operations. Token compatibility — particularly with older USB tokens and certain browser versions — remains the single most common support ticket among practising CS. Workaround: maintain DSCs on at least two browsers + one fallback machine. The 30-minute V3 “session” timeout combined with a DSC challenge midway is a familiar frustration.

Form rejection on data interpretation

Where the master data has a legacy quirk — paid-up capital recorded as ₹ vs nominal, director's name with extra spaces — V3 sometimes rejects until corrected at the master-data level via STK / GNL forms. The cleanup cycle adds 10-20 days.

Payment retries

The payment gateway has improved but still occasionally fails on retries. Best practice: check the dashboard before re-paying. Avoid same-day repeated retries.

Multi-state filings

For companies with multi-state operations involving state-specific forms (state-level stamp duty, professional tax registrations), V3's integration with state portals remains partial. Manual coordination still required for some.

The “add another” pattern

V3's forms with repeating sections (multiple directors, multiple charges, multiple resolutions) have intermittent issues with adding rows beyond a certain count. Workaround: save and re-open the form; usually clears.

Search and reports

The reporting layer (company master data search, charge index, filing history) is functional but slower than V2 was for some queries. For bulk research, the public data download utilities are the workaround.

e-Form INC-22A / INC-22 / INC-20A

The post-incorporation triple of address verification, commencement, and operational confirmations has had specific recurring issues — particularly around proof of registered office and Google geo-tagging. The CS toolkit must include current-state guidance per form.

STK forms

The voluntary strike-off route via STK-2 had a backlog through 2025; processing times have stabilised at 60-90 days. STK-7 final orders flow through reasonably.

The compliance professional's adjusted workflow

Pre-filing checklist: DSC status, browser compatibility, master data validation, supporting documents PDF-OK.
Filing window: Avoid end-of-quarter / end-of-month last-week peak load. Mid-month is faster.
Post-filing tracking: SRN confirmation, payment confirmation, dashboard status — three separate checks.
Defect / query handling: V3 routes via the SRN. Quick response is rewarded.
Escalation: The IEPF help desk and the regional ROC offices remain useful for stuck matters; have the SRN and the email chain handy.

The transition residuals

Pre-V3 forms (V2-era) still occasionally surface in audits. The mapping from old form numbers to new is worth keeping on hand.
Historical filings access — for diligence on a target's past compliance, the access patterns differ between in-portal search and the public data download.
Master data correction trail — V3's audit trail of master data corrections is more granular than V2's, useful in diligence.

What the MCA seems to be working on next

API access for larger filer firms (rumoured for late 2026).
Further integration with GST / IT databases.
BEN / SBO module enhancements.
Director master data consolidation.

How Delta Filings supports V3 workflow

The Delta Filings filings module integrates with V3 form templates, ships pre-validation that catches the most common rejection causes, and tracks SRN status with reminders for defect responses. For a CS practice with high filing volume, the rejection-rate reduction over time is the most-cited operational improvement.

The closing note

V3 is now the normal. The first generation of migration pain is behind us. The steady-state quirks are manageable with discipline. The CS who builds the workflow around the platform's actual behaviour — rather than the design documents' intended behaviour — moves faster and breaks fewer filings. That is the entire art of the V3 era.