Just a moment...
Generate professional replies to Show Cause Notices, assessment orders, audit objections, and other legal communications using TaxTMI's AI Drafter.
Step 1 – Issue Identification & Review
The AI analyses your query, notice, order, or uploaded documents and identifies the key issues involved.
• Review the issues identified by the AI
• Add, edit, remove, or refine issues as required
Step 2 – Draft Generation
Once you approve the issues, the AI performs issue-wise legal research and prepares a structured draft response.
• Relevant statutory provisions
• Judicial precedents and Supreme Court, High Court and other citations
• Issue-wise legal analysis
• Practical arguments and supporting content
• Professionally structured draft ready for further review. 
Press 'Enter' to add multiple search terms. Rules for Better Search
Use comma for multiple locations.
---------------- For section wise search only -----------------
Accuracy Level ~ 90%
Press 'Enter' after typing page number.
Press 'Enter' after typing page number.
No Folders have been created
Are you sure you want to delete "My most important" ?
NOTE:
Press 'Enter' after typing page number.
Press 'Enter' after typing page number.
Don't have an account? Register Here
Press 'Enter' after typing page number.
Issues: (i) Whether the successful resolution applicant was a related party of the corporate debtor so as to attract the ineligibility under the insolvency code. (ii) Whether the banks or the Reserve Bank of India could be directed to pursue attachment of the corporate debtor's assets or otherwise intervene for the benefit of creditors after approval of the resolution plan.
Issue (i): Whether the successful resolution applicant was a related party of the corporate debtor so as to attract the ineligibility under the insolvency code.
Analysis: The challenge rested on the assertion that the successful resolution applicant's participation in a joint venture made it a related party of the corporate debtor. The Court held that this question had already been examined in insolvency proceedings and that the resolution applicant had disclosed the relevant background. On the materials referred to, no nexus or control was shown to establish related-party status within the meaning of the insolvency code.
Conclusion: The objection based on related-party ineligibility was rejected and was held against the petitioner.
Issue (ii): Whether the banks or the Reserve Bank of India could be directed to pursue attachment of the corporate debtor's assets or otherwise intervene for the benefit of creditors after approval of the resolution plan.
Analysis: The Court held that approval of a resolution plan under the insolvency code binds the corporate debtor, creditors and other stakeholders, and that claims are to be dealt with within that framework. It further held that, once the resolution plan is approved and management changes hands, the corporate debtor and its assets operate on a clean slate, and the immunity embodied in section 32A protects the corporate debtor's assets from attachment in relation to prior offences, subject to the statutory requirements. In that background, no mandamus could be issued to compel the respondent banks or the RBI to take the steps sought by the petitioner.
Conclusion: The requested writ reliefs were declined and the issue was decided against the petitioner.
Final Conclusion: The writ petition failed because the approved resolution plan remained binding and the post-approval regime under the insolvency code did not permit the petitioner to reopen settled insolvency consequences or seek the reliefs claimed.
Ratio Decidendi: Once a resolution plan is approved under the insolvency code, it binds all stakeholders and the corporate debtor proceeds on a clean slate, so prior claims and asset-protection disputes must yield to the statutory resolution framework.