Cohance Lifesciences Ltd. sees a credit rating action

Suryapet’s exact share of Cohance’s capacity or revenue is not company-reported. The closest capacity proxy is:

• Suryapet lists 671 m³ of total reactor volume ^[1].
• Cohance reports 3,000+ KL of standalone manufacturing capacity across its network ^[2].
• On a simple reactor-volume comparison, Suryapet represents less than approximately 22.4% of network capacity, calculated as 671 ÷ 3,000. This is only an indicative proxy: the denominator is stated as “3,000+,” and reactor volume is not the same as annual output capacity. Suryapet’s revenue contribution was not separately reported, so no revenue percentage can be calculated reliably.

A separate management reference to 400+ KL of Suryapet project capacity ^[3] appears to relate to an expansion project rather than necessarily the full site; using that figure would imply roughly 13.3% on the nominal 3,000-KL denominator, but it should not be treated as the total site’s share.

Contingency plan: The closure disclosure describes a remediation-and-reopening plan rather than a detailed contract-fulfilment workaround. Cohance said it had initiated corrective and preventive measures, would submit representations and compliance documentation to TGPCB, and would seek cancellation of the closure directions so that Suryapet could resume operations at the earliest ^[4]. The company also said the operational and financial impact could not yet be quantified with reasonable certainty ^[5].

A Suryapet-specific commitment to shift production to alternate sites, use inventory, outsource manufacturing, or amend existing supply contracts could not be confirmed from the cited closure disclosure.

Estimated carrying value: A facility-level net carrying value for Suryapet cannot be established from the latest disclosed figures. Consolidated property, plant and equipment was ₹1,990.1 Cr as of Q1 FY27, but the Suryapet component was not separately identified ^[6]. FY26 capex of approximately ₹215 Cr was allocated across the Nacharam expansion, Suryapet capacity expansion and high-containment upgrades at other sites, so it cannot be attributed entirely to Suryapet ^[7].

The closest disclosed proxy is management’s earlier commitment of approximately ₹200 Cr for the Suryapet expansion ^[8]. However, that is a project investment commitment, not the asset’s net book value: it does not account for commissioning, depreciation, impairment or other capitalization adjustments. Accordingly, ₹200 Cr may be used only as a rough gross-investment proxy, not as a confirmed carrying value.

Environmental provisions or contingent liabilities: A specific previously recognized provision or contingent liability relating to environmental compliance at Suryapet could not be confirmed from the cited financial disclosures. The later report of a Telangana Pollution Control Board closure order states that the financial impact could not yet be quantified ^[9]; it does not establish that a prior environmental provision or contingent liability had been recorded.

Analytical implication: Any balance-sheet exposure from the Suryapet event remains unquantified on the evidence cited. The key disclosures to monitor are a facility-level impairment assessment, remediation or restoration provision, and any explicit contingent-liability note in the next audited financial statements.

Verdict: Suryapet currently has the most serious disclosed regulatory event in the cited record: a TGPCB closure order requiring suspension of operations following an industrial accident. The evidence does not support a complete plant-by-plant compliance ranking, but no comparable TGPCB closure event is cited for the other manufacturing units. ^{[10] [9]}

Prior TGPCB notices or show-cause orders

The cited FY26 annual-report material describes capacity expansion, compliance upgrades across Suryapet, Parawada and Vizag, and the capitalisation of the Suryapet CDMO unit; it does not identify a prior TGPCB notice or show-cause order in the relevant excerpts. ^{[12] [2]}

A prior environmental-clearance filing containing a TGPCB notice or show-cause order is not cited, so the historical existence or non-existence of such orders cannot be confirmed. The current closure order should therefore not automatically be treated as the first-ever TGPCB action; it is the first such action evidenced in the cited record.

Analytical implication: Suryapet should be viewed as a newly elevated site-specific compliance risk, while Nacharam demonstrates that the company has previously managed a separate regulatory-remediation episode. However, the available disclosures do not establish whether Suryapet had earlier show-cause notices, consent-condition breaches, or repeat TGPCB findings.