Govt allows RIL to surrender SEZ in Haryana
NEW DELHI: The government has allowed
MukeshAmbani owned Reliance Industries to surrender its special
economic zone in Haryana.
The decision to denotify Reliance
Haryana SEZ Ltd, a unit of RIL, was taken by Board of Approval, headed by Commerce
Secretary S R Rao, in its meeting on June 12.
"After deliberations, the board
decided to approve the proposal...for de-notification of the sector specific
SEZ for multi services.
"The approval is subject to...a
certificate that the developer has either not availed or has refunded all the
tax/duty benefits availed under SEZ Act/Rules in respect of the area to be
de-notified, there are either no units in the SEZ or the same have been
debonded, the state government has no objection to the de-notification proposal
etc," the minutes of the SEZ BoA meeting said.
The BoA is a 19-member
inter-ministerial body that deals with SEZs and the issues related to them.
In the meeting, the board has also
directed that the information regarding that case "must invariably be sent
to CBDT and CBEC for taking necessary action".
However, no reason was given by the
developer for de-notification of the zone.
Reliance Haryana SEZ Ltd, a sector
specific SEZ for multi services at villages Mohammadpur Jharsa, Gharauli Khurd,
Khandsa and Harasru, District Gurgaon, Haryana was notified over an area of
440.71 hectares.
It was notified on November 14, 2007.
Separately, the BoA deferred the
proposal of another SEZ promoted by Mukesh Ambani at Raigad in Maharashtra.
Mumbai SEZ Ltd has requested for grant
of extension of in-principle approval for setting up of a multi-product SEZ
Raigad, Maharashtra.
"The Board after deliberations
deferred the proposal and decided to obtain the views of the State Government
on the issue before considering the extension," the minutes said.
The SEZ was given in-principle approval
on August 8, 2006. As per SEZ Rules, the validity of the approval was up to
August, 7, 2007. The developer has already been granted six extensions, the
validity of which was going to expire on August, 7, 2013.
The developer was seeking further
extension of validity for one more year.
