Satyam Fraud Twice As Large As First Thought

Trial of Former Chairman To Start Soon

1 min read
Satyam Fraud Twice As Large As First Thought

In January of this year, the IT outsourcing world was stunned to learn that the Chairman of India's Satyam Computer Services resigned after he confessed to doctoring the country's fourth largest IT outsourcing company's books for the past several years. The Chairman, Ramalinga Raju, admitted at the time that fictitious assets and non-existent cash concealed a $1.1 billion operating deficit.

Raju, who originally claimed that he acted alone, is in Hyderabad's Chanchalguda jail along with along with his brother and Satyam's former managing director, Rama Raju, along with six others including their former auditors. They are charged with the fraud, forgery, cheating, embezzlement and insider trading.

Last week, the Wall Street Journalreported that India's Central Bureau of Investigation (CBI) is saying that the actual fraud was more than $2.8 billion. The CBI noted that the company had paid out some $5.5 million in dividends to shareholders, which surprise, surprise included the accused.

On good explanation for cooking the revenue books, I suppose.

The shares of Mahindra Satyamfell on the news, but later recovered. Tech Mahindra took over Satyam in April.

The WSJ also reported that the trial of Ramalinga Raju will begin in the next few weeks.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less