MCA V3 portal: the four things a CS gets wrong in her first week

The MCA V3 portal [L4-C1] is where every filing actually happens. Legacy MCA21 V2 was permanently decommissioned on 30 June 2026 with a 30-day grace period until 30 July 2026 for filings delayed by documented V3 technical issues. All company e-forms have migrated: SPICe+, AOC-4 family, MGT-7 family, MGT-14, DIR-3-KYC (both web-form and e-form), DIR-12, CHG-1/9/4, INC-20A, INC-22, DPT-3, MSME-1, CSR-1, CSR-2, ADT-1, PAS-3, SH-7, MR-3 attachment via MGT-8/MGT-7. LLP forms (FiLLiP, Form 3, Form 4, Form 8, Form 11) are also on V3.

A first-year CS spends her first week wrestling with four setup issues. All four are avoidable if she knows what to look for.

Issue 1: User type wrong (Registered User vs Business User)

V3 has two profile types. A "Registered User" can view MCA data but cannot associate a DSC and cannot file forms. A "Business User" can associate a DSC and file. Most first-year CS create a Registered User profile because it is the default option on the signup flow, then hit a wall on the first filing day.

Fix: On Day 1, log into mca.gov.in, go to Profile, and verify User Type shows "Business User". If it shows "Registered User", raise an upgrade request. The upgrade requires PAN verification and typically completes within one working day.

Issue 2: emBridge / DSC signing failures

The V3 portal signs forms via the emBridge (formerly emsigner) desktop application. Practitioners spend hours debugging DSC issues that have simple root causes.

Fix (the practitioner-tested sequence):

1. Uninstall the existing emsigner / emBridge application via Windows Add / Remove Programs.
2. Restart the machine (do not skip this).
3. Download the latest emBridge from mca.gov.in Downloads section.
4. Install; when prompted, allow the localhost service to start on machine boot.
5. Plug in the DSC USB token; confirm Windows recognises it in Device Manager.
6. Open a fresh Google Chrome Incognito window (not Firefox, not Internet Explorer).
7. Log into mca.gov.in as Business User; DSC association should now work.

This sequence resolves approximately 90 percent of persistent DSC issues. Where it does not, the issue is usually Issue 3.

Issue 3: Duplicate V2 / V3 profile blocking DSC association

If the same PAN or email address had a V2 profile before migration, the migrated V3 profile may reject a DSC association with a cryptic error. The root cause is that the migration created a shadow duplicate profile that must be reconciled.

Fix: Raise a service-request ticket on the MCA portal specifying "Duplicate V2/V3 profile blocking DSC association" and provide PAN, email, and DIN if applicable. Typical resolution: 3 to 5 working days.

Issue 4: Browser support

V3 is reliably supported on current stable versions of Google Chrome and Microsoft Edge. Firefox and Internet Explorer fail intermittently on form load, on SRN submission, and on DSC signing.

Fix: Use Chrome or Edge. Where a firm mandates Firefox, keep a dedicated Chrome install just for MCA filings.

The MCA21 data-centre fire of 5 June 2026 and CCFS-2026

On 5 June 2026 the MCA21 data centre suffered a fire that disrupted portal availability for a period. General Circular 03/2026 dated 8 July 2026 [L4-C2] extended the Companies Compliance Facilitation Scheme (CCFS-2026) validity to 31 August 2026. Under CCFS-2026, entities with pending annual returns and financial statements can file at normal fees plus 10 percent of the additional fees, with immunity from prosecution. If any of your clients has backlog filings, plan the catch-up before 31 August 2026.

The one-page portal readiness check for every new joiner

1. Business User profile confirmed.
2. DSC valid, USB token working, driver installed.
3. emBridge latest version installed, localhost service running.
4. Chrome or Edge as the default filing browser.
5. Test filing: draft a dummy MGT-14 (no submit), verify DSC signing bridge loads.
6. SRN Enquiry bookmarked for tracking pending / failed SRNs.