CAG should look into his leaky office: Digvijay Singh

Digvijay Singh

Congress leader Digvijay Singh today again hit out at the Comptroller and Auditor General over reports that it has taken exception to the Oil Ministry's decision to "accede" to the demands of Reliance Industries Ltd on audit of its Krishna-Godavari basin asset.

"CAG interim report again leaked. Would CAG instead of sermonising every one please look into his Leaky Office?" Singh wrote on the popular microblogging site Twitter.

There were media reports that the auditor has refused to agree to a time-barred audit, restricting the audit only to accounting books and records, submitting the final report only to the Oil Ministry and not using the information and data received from RIL for any other audit the CAG may carry out in the future.

The reports stated that while asking the Ministry to remove these conditions "unambiguously", the CAG has said that many of the RIL's demands are restrictive and impinge on the CAG's basic rights and mandate to carry out audit as per the CAG Act and the Constitution.

The Congress general secretary had earlier on August 31 caused a flutter by lashing out at Comptroller and Auditor General Vinod Rai that he has a political agenda. Singh had later also blamed Rai for 'leak' of CAG reports.

Please read our terms of use before posting comments
TERMS OF USE: The views, opinions and comments posted are your, and are not endorsed by this website. You shall be solely responsible for the comment posted here. The website reserves the right to delete, reject, or otherwise remove any views, opinions and comments posted or part thereof. You shall ensure that the comment is not inflammatory, abusive, derogatory, defamatory &/or obscene, or contain pornographic matter and/or does not constitute hate mail, or violate privacy of any person (s) or breach confidentiality or otherwise is illegal, immoral or contrary to public policy. Nor should it contain anything infringing copyright &/or intellectual property rights of any person(s).
comments powered by Disqus