Land Documentation Challenges And Connectivity Disputes: ACME Solar’s Case With CTUIL

In a recent development, ACME Solar Holdings Pvt. Ltd. (ASHPL) and its subsidiary, ACME Sikar Solar Pvt. Ltd. (ASSPL), filed a petition seeking specific relief from the Central Electricity Regulatory Commission (CERC). The case, formally recognized as Petition, revolves around the intricacies of regulatory compliance related to the utilization of connectivity granted to their solar project.

The petitioners approached the Commission under the purview of certain regulations, seeking a declaration that ASSPL meets all necessary conditions for utilizing connectivity granted on May 10, 2022. The backdrop of this case lies in the directives issued in a previous order dated April 21, 2024. In that order, the Commission had mandated the submission of land documents by ASSPL to the Central Transmission Utility of India Ltd. (CTUIL) within a four-week timeframe. Failure to comply would result in the revocation of connectivity granted to ASHPL.

The core of the petitioners’ argument hinges on the assertion that while the connectivity was initially granted to ASHPL, the land acquisition for the project was managed by ASSPL, the project-specific vehicle (SPV). Given this arrangement, they argue that the land documents submitted in the name of ASSPL should be considered valid for compliance purposes.

Complications arose when CTUIL observed discrepancies in the documentation. Specifically, lease deeds with landowners were executed in the name of ASSPL, yet the connectivity had been granted to ASHPL. CTUIL’s position required lease deeds to be signed by the entity to which connectivity was granted, leading to a conflict over regulatory interpretation.

The petitioners highlighted that ASSPL had secured lease rights over the necessary land and achieved financial closure for the project. They emphasized the impracticality of transferring lease deeds to ASHPL, given the structural organization of the project. Furthermore, they noted that without interim relief from the Commission, the connectivity would be revoked, negating their efforts and investments thus far.

The petitioners also filed interim applications seeking immediate relief to prevent CTUIL from taking coercive action, including the revocation of connectivity, during the petition’s pendency. These applications underscored the urgency of the situation, stressing the potential adverse impact on the project if interim protection was not granted.

During the proceedings, the Commission directed CTUIL not to take any coercive actions against the petitioners’ connectivity application until the matter was resolved. The Commission acknowledged the petitioners’ compliance with prior directives and noted their progress toward achieving the project’s commercial operation by the set deadline.

In their written submissions, the petitioners reiterated their compliance with the conditions laid down in the previous order. They provided updates on the project’s status, including financial closure and the placement of orders for major equipment essential for the project’s execution. This comprehensive compliance, they argued, should be sufficient to fulfill the regulatory requirements, despite the technicality of the lease deed issue.

The case highlights the complexities inherent in regulatory compliance for large-scale infrastructure projects, particularly when multiple entities and varying interpretations of regulations are involved. The petitioners’ proactive approach in seeking clarification and relief from the Commission underscores the importance of regulatory oversight in ensuring that projects progress without undue hindrance.

As the matter awaits final resolution, the interim relief granted by the Commission provides a temporary reprieve, allowing the petitioners to continue their project activities without the immediate threat of connectivity revocation. This case serves as a pertinent example of the intricate balance between regulatory compliance and practical project execution in the energy sector.

Please view the document here for more details.