🟡 STAKEHOLDER CONSULTATION — DRAFT PLATFORM UNDER DEVELOPMENT
Issuing Authority: Ministry of Corporate Affairs (MCA) | Status: Comments invited before requirements are finalised | Last Date for Comments: 3 August 2026
Background: Why MCA Is Building iPIE
Since the Insolvency and Bankruptcy Code, 2016 came into force, India's insolvency framework has matured into a structured, time-bound resolution process. But the machinery supporting that process has grown up in pieces. NCLT and NCLAT run their own e-Courts system, MCA operates the MCA-21 portal for company data, IBBI runs its own compliance and disclosure platform, and the Information Utility maintains a separate repository of debt and default records. Each system works well on its own terms, but a case moving through the IBC today still depends on insolvency professionals, creditors and other participants manually carrying information from one portal to the next.
MCA's proposed answer is the Integrated Platform for Insolvency Ecosystem (iPIE) — a single technology layer meant to sit across the entire IBC lifecycle, from the first public announcement of a case to final dissolution or discharge. Rather than replacing NCLT, IBBI or MCA-21 individually, iPIE is designed to connect them through APIs so that data entered once flows automatically to every authorised stakeholder who needs it.
Before finalising what iPIE should actually do, MCA has opened a stakeholder consultation, inviting professionals, institutions, industry bodies and academia to flag gaps, missing data fields, and process pain points that the platform's design should address.
The IBC Ecosystem iPIE Will Connect
The consultation document maps out the full set of institutions and actors iPIE is meant to bring onto one platform:
Appellate and Adjudicating Authorities, already running the e-Courts system for filing and case documents
Holds director, financial statement, annual filing and charge data for every debtor company
Uses its platform for compliance, reporting, monitoring and dissemination of case-related information
Repository for debt and default data submitted by financial creditors, with authentication and verification
Central figures appointed by the Adjudicating Authority to manage each case
Regulate and oversee IPs — standards, monitoring, training and professional development
Conduct independent valuation of assets, securities and businesses
Authorised by IBBI to regulate RVs — standards, codes of conduct, examinations
Vision and Envisaged Benefits
MCA frames iPIE's goal as building a scalable, centralised platform that supports data-driven decision-making across the IBC ecosystem while strengthening transparency and digital security. The consultation paper sets out seven benefits the platform is expected to deliver:
iPIE acts as an integration layer connecting standalone IBC portals through APIs, replacing manual coordination between institutions.
Reduces delays, improves transparency, increases resolution applicant participation, and supports real-time information flow across pillars.
A single source of truth for all participants, helping NCLT prioritise cases and attract interim finance providers and resolution applicants.
Bulk communication, e-meetings, e-voting, virtual data rooms, auction and challenge platforms, and digital marketing tools, all reducing coordination burden on IPs.
Claim submission, verification, admission, rejection, and every document access, upload, download, edit and deletion is logged with user ID, timestamp and IP address for regulatory inspection.
NCLAT, NCLT, MCA, IBBI, the Information Utility and IPs are consolidated, fostering workflow synergy across creditors and market participants.
A consolidated data set enabling statistical and predictive analysis for ecosystem-wide decision-making.
Inside iPIE: The 13 Planned Modules
The consultation document lays out a detailed module architecture spanning the full case lifecycle, along with a mobile app for critical processes. Here is what each module is expected to cover:
i. User Registration and Management
Centralised registration, authentication, authorisation, onboarding and role-based access control for all stakeholders.
ii. Process Commencement
Generates a unique iPIE ID, links the case to NCLT, builds a case timeline and pulls debt-default data from IBBI. Sub-functions include:
- Digital consent for appointment of the proposed IP, with PDF generation and a Unique Consent ID
- Case e-filing on the NCLT portal with automatic iPIE ID linkage
- Case initiation with stakeholder notification and auto-transfer of NCLT filing data to IBBI
- Consent for acceptance, with notification to NCLT/IBBI/applicant if an IP declines
- Public announcement with auto-linked claim forms, integrated with IBBI via SSO
- Automated intimation to the corporate debtor, board, statutory authorities and workmen/employees
- Withdrawal, termination or suspension workflows, including CoC voting capture and NCLT order tracking
- Internal task assignment by the IP to their team, with status tracking
- Base Resolution Plan workflow for Pre-Packaged Insolvency Resolution Process (PPIRP) cases
iii. Claims Management
- IP-side configuration of claim forms per process
- Claim submission with document upload
- Verification through integration with other portals
- Withdrawal and modification of claims by claimants
- Accept/reject/partial-accept decisions by the RP, liquidator or bankruptcy trustee
- Reconsideration requests for rejected or partially accepted claims
- Built-in IP–claimant communication tool
- Claim filing by the IP on behalf of claimants who cannot file online
iv. Stakeholder Management
- Appointment of the Authorised Representative for a creditor class, chosen by most claimants
- CoC constitution with system-calculated voting percentages based on admitted claims
- Appointment/replacement voting for IRP-to-RP transition or liquidator
- Appointment of registered valuers, auditors and other professionals, with CoC ratification
- Stakeholder role, category and sub-category tracking
- Group-based communication and document sharing
- Meeting scheduling with unique meeting references and automated invitations
v. Records Management
- Integration with MCA, NeSL and other external sources for corporate debtor documents
- Structured document management system with folder categorisation
- Asset register, asset memorandum and liquidation estate management
- Storage of asset valuation reports
- Capture of quotation information, whether submitted online or entered manually by the IP
- Information Memorandum upload with version management
- Auditor upload of Avoidance Transactions Reports
- Asset custody transfer and access control at handover
vi. Resolution/Repayment Plan Management
- EoI publishing and invitation of prospective resolution applicants
- EoI response handling and provisional/final applicant lists
- RFRP publishing with Virtual Data Room set-up for due diligence
- Encrypted RFRP response submission and IP evaluation/scoring
- CoC approval and NCLT e-filing of the final resolution plan
- Capture of plan acceptance or rejection status
- Repayment plan filing for individual insolvency cases
- Contravention-of-plan reporting
- Pre-liquidation workflows: contribution to liquidation costs, and compromise/arrangement filing
- Capture of CoC decisions on liquidator fees, with meeting minutes and voting results
vii. Resolution/Repayment Implementation & Monitoring
- Distribution and allocation of proceeds under the approved plan
- Intimation to the corporate debtor, board, statutory authorities and workmen
- Formation and management of the Implementation & Monitoring Committee (IMC)
- Resolution plan implementation checklist
- Handover monitoring from IP to the Successful Resolution Applicant (SRA)
- Final report generation and submission
- Upload and tracking of the NCLT discharge order
viii. Liquidation/Bankruptcy Implementation & Monitoring
- Liquidation initiation and Stakeholder Consultation Committee (SCC) constitution
- Liquidation estate records management
- Tracking relinquishment or realisation of security interest
- Distribution of liquidation proceeds per the statutory waterfall
- Tracking deposit of unclaimed proceeds
- Final liquidation report submission
- Tracking of dissolution, closure or discharge orders from NCLT
- Private asset sales and e-auction notice publishing (EAPD)
- Bid response management and final qualified bidder lists
- Auction configuration and conduct through the baanknet portal
ix. Compliance Management
Real-time tracking, monitoring and deadline alerts for compliance filings to:
- IBBI — CIRP and liquidation compliance forms
- NCLT — applications and compliance documents
- Statutory authorities — submissions with delivery status tracking
- IPAs — compliance form submissions
- MCA — compliance form submissions
x. Litigation Management
- User management and publishing of litigation records/documents
- Tracking of NCLT/NCLAT case details, proceedings and hearings
- Tracking litigation before other courts (Supreme Court, High Court, District Court, Special Court)
- Recording and tracking of litigable issues
xi. Finance/Cost Management
Expense categorisation, cost tracking, cost-variance analysis across process phases, and monitoring of CoC/SCC approval on cost components.
xii. MIS Reports and Dashboards
Consolidated, real-time dashboards giving stakeholders and decision-makers a single view of critical case metrics.
xiii. Additional Digital Services
- Virtual Data Room for secure storage/sharing of sensitive transaction and due-diligence documents
- Electronic Voting for CoC, SCC and other stakeholder decisions
- Document Management System — a central repository for case documents
- Meeting Management System for scheduling, records and coordination
- Communication Tool for bulk messaging/notifications
- Ticketing System for user queries, service requests and grievances
- Chatbot for virtual stakeholder assistance
- Digital Signature Utility for secure, legally recognised document signing
Today vs. iPIE: What Changes
How to Submit Your Suggestions
MCA has engaged KPMG Advisory Services Pvt. Ltd. as Project Management Unit (PMU) and CMS Computers India Pvt. Ltd. as System Integrator (SI) for the iPIE build. Before requirements are finalised, stakeholders can email suggestions to [email protected] in the prescribed tabular format below.
Name*, Organization (if applicable), Designation (if applicable), Stakeholder Category*, Email Address*, Mobile Number (optional), Suggestion Category*, Detailed Suggestion*, Consent to contact for clarification* (Yes/No), Supporting Documents (optional). Fields marked * are mandatory — submissions not complying with this format may not be processed.
17 Stakeholder Categories
Insolvency Professional, Insolvency Professional Agency, Insolvency Professional Entity, Financial Creditor, Operational Creditor, Corporate Debtor, Resolution Applicant, Committee of Creditors, Registered Valuer, Information Utility, Legal Professional, Financial Institution, Technology Service Provider, Academic/Research Institution, Industry Association, Government Organisation, Homebuyer, Workmen.
7 Suggestion Categories
- Data Capture Requirements — data elements missing from iPIE today
- Stakeholder Coverage — roles not currently included in iPIE integration
- Data Sharing Gaps — data collected but not exchanged across IBC platforms
- Process Gaps & Improvements — existing IBC process gaps iPIE could fix
- System Integration Needs — weak links between institutions/systems
- User Challenges & Pain Points — practical difficulties iPIE can address
- Alerts & Notification — automated reminders for deadlines, filings, approvals
☑ Map each suggestion to one of the 7 Suggestion Categories — data capture, coverage, sharing gaps, process, integration, user pain points, or alerts
☑ Include every mandatory field (Name, Stakeholder Category, Email, Suggestion Category, Detailed Suggestion, Consent to contact) — incomplete formats may not be processed
☑ If submitting on behalf of an IPA, IPE, RVO or industry body, coordinate internally first to avoid duplicate or conflicting suggestions
☑ Attach supporting documents where they strengthen a specific data-gap or process-gap suggestion
☑ Send suggestions to [email protected] before the 3 August 2026 deadline
☑ Track MCA's further communication for the finalised requirements and eventual rollout/pilot timeline, neither of which is specified in this document
CorpLawUpdates Analysis
The most significant thing about this consultation isn't any single module — it's the scope. iPIE is not proposed as an add-on to NCLT's e-Courts or IBBI's existing systems; it is designed to sit across all of them, with API-level integration to MCA-21 and NeSL as well. If built as described, an insolvency professional could move from case initiation through claims verification, resolution plan filing, and final distribution without re-keying the same information into four different portals. That is a meaningfully different operating model from today's practice.
The likely compliance challenge sits in change management rather than legal interpretation. Firms that have built internal SOPs and tracking sheets around today's fragmented filing points — separate logins for NCLT, IBBI and MCA-21 — will need to rethink those workflows once iPIE modules like Compliance Management and Litigation Management go live. The activity-logging design, which records every claim and document action with a user ID, timestamp and IP address, also raises the bar on internal record discipline: actions that were previously informal (a phone call to a creditor, an off-system document share) will need to move onto the platform to be captured at all.
Practitioners should watch two things closely. First, whether the final module design actually resolves the "Data Sharing Gaps" the consultation itself flags as a category — today, data collected by one pillar frequently doesn't reach another, and if iPIE's API integration doesn't fully close that gap, much of its promised efficiency will not materialise. Second, the treatment of Committee of Creditors workflows: automated voting-percentage calculation and e-voting integration could significantly speed up CoC decision-making, but only if IPs and CoC members trust the platform's claim-admission data enough to rely on it during time-bound CIRP deadlines.
This is still a design-stage consultation, not a notified system — there is no confirmed rollout date, pilot phase, or transition timeline in this document. Firms with strong views on data fields, stakeholder coverage, or integration gaps have a real opportunity to shape the platform before requirements are locked in, but that window closes on 3 August 2026.
This article is for informational and educational purposes only and does not constitute legal or regulatory advice. Verify with primary regulatory sources before acting.
