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):
- Uninstall the existing emsigner / emBridge application via Windows Add / Remove Programs.
- Restart the machine (do not skip this).
- Download the latest emBridge from mca.gov.in Downloads section.
- Install; when prompted, allow the localhost service to start on machine boot.
- Plug in the DSC USB token; confirm Windows recognises it in Device Manager.
- Open a fresh Google Chrome Incognito window (not Firefox, not Internet Explorer).
- 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
- Business User profile confirmed.
- DSC valid, USB token working, driver installed.
- emBridge latest version installed, localhost service running.
- Chrome or Edge as the default filing browser.
- Test filing: draft a dummy MGT-14 (no submit), verify DSC signing bridge loads.
- SRN Enquiry bookmarked for tracking pending / failed SRNs.
The DSC lifecycle in practice
Digital Signature Certificates (DSC) have specific lifecycle management. Class 3 DSCs are required for MCA filings (Class 2 was deprecated in 2020). DSC validity: 1 to 3 years typical; renewal 30-60 days before expiry. Vendors: eMudhra, Sify, VSign, IdenTrust, Capricorn. Association with V3 profile after issuance. Revocation on individual departure from firm or on compromise. Multiple DSCs may be associated with the same V3 profile for different roles (Director, Company Secretary, Managing Director). Understanding DSC lifecycle prevents filing-day surprises.
SRN tracking discipline
Every filed form generates a Service Request Number (SRN). Tracking SRNs is essential for verifying filing status. Common statuses: Pending Payment; Awaiting Digital Signature; Approved; Rejected; Requires Resubmission. Firms should maintain an SRN log per client with target-outcome tracking. Missed SRN follow-ups produce filings that never complete, later surfacing as compliance gaps.
Form resubmission handling
MCA sometimes rejects forms or marks them for resubmission. Reasons: incomplete information, incorrect attachments, DSC mismatches, procedural errors. Resubmission handling: understand the specific reason from MCA notes; fix the issue; resubmit within the window; track under the same or new SRN as MCA specifies. Repeated resubmissions signal weak initial preparation; understanding rejection patterns helps improve first-attempt filing quality.
Filing calendar and deadline management
V3 filings have specific deadlines tied to Section-based obligations. Missing deadlines triggers additional-fee slabs and potential penalty exposure. Practical rule: maintain a filing calendar per client with target dates, actual filing dates, SRN references, and completion confirmations. Missed deadlines are rarely catastrophic on individual filings but accumulate into significant compliance risk if patterns emerge.
Portal outages and business continuity
The V3 portal occasionally experiences outages beyond the June 2026 datacentre fire. Planned maintenance windows are announced; unplanned outages happen occasionally. Practical rule: don\'t leave filings to the last day; plan buffer time; monitor MCA circulars for any relief on deadlines affected by outages; document any outage impact on your practice for records.
Multi-user workflows on V3
Firms often have multi-user workflows: junior CS drafts filing; senior CS reviews; partner signs. V3 supports role-based access; ensure user roles align with actual work distribution. Handovers between users during a filing require care to avoid form-state conflicts. Documented internal workflows prevent these conflicts.
Learning V3 through structured practice
V3 proficiency comes through structured practice, not just reading documentation. Practical rule: run test filings on non-critical dummy scenarios during onboarding; participate in ICSI V3 orientation programmes; learn from peers who have completed high-volume V3 work. First-week frustration is universal; by month three, most CS become efficient V3 users.
V3 audit trail and evidence
V3 maintains audit trails of user actions, form submissions, and status changes. This audit trail is available for compliance record purposes. Practitioners should download and archive filing acknowledgements immediately upon successful filing. MCA occasionally has data-integrity issues where filed forms show incorrect status; keeping local copies of acknowledgements protects the practice.
Client access to V3 for viewing
Clients can create Registered User profiles (view-only) to access their own filings. This gives clients direct visibility into their compliance status without requiring practitioner intermediation for every query. Encouraging clients to maintain Registered User access improves practice transparency and client trust.
V3 and beneficial-ownership disclosures
V3 integrates with Significant Beneficial Owner (SBO) disclosure requirements under Section 90. BEN-1 (declaration), BEN-2 (return), BEN-3 (register) filings run through V3. Understanding SBO requirements alongside V3 mechanics is essential for private-company practice.
Filing accuracy versus completeness trade-offs
Filings must be both accurate and complete. Accuracy: every field correctly populated with verified data. Completeness: all required attachments; nothing missing. Trade-off tension: rushing for a deadline may compromise accuracy; over-preparing may miss deadlines. Practical rule: build filing habits that support both accuracy and completeness through structured checklists and peer review.