Satyam Computer Services was an Indian IT company whose chairman, B. Ramalinga Raju, admitted on 7 January 2009 that its accounts had been falsified, including cash and bank balances that did not exist. The special CBI court in Hyderabad convicted him and nine others on 9 April 2015, and SEBI's findings centred on fictitious invoices and fictitious bank statements. For auditors, the lasting lesson is that evidence from the client is not the same as evidence from the bank.
Last reviewed: 17 October 2026. Facts checked. We opened the SEBI order of October 2018 (which recites the 2014 SEBI order and the 2017 SAT order), a Moneylife report on the April 2015 verdict, and a BCAJ summary of the 2019 SAT ruling. We read search summaries, but did not open the full text, of the January 2018 SEBI order on the auditor, and we did not check appeals filed after 2019. Everything below is attributed to the body that said it.
What happened, in one timeline
| Date | Event | Source we used |
|---|---|---|
| 7 January 2009 | Chairman Ramalinga Raju confessed to a fraud, reported as ₹7,136 crore | Search summary of press coverage |
| 15 July 2014 | SEBI final order against the promoters and officials for falsified financial statements | SEBI order of October 2018, which recites it |
| 9 April 2015 | Special CBI court convicts ten people, sentences from two to seven years, running concurrently | Moneylife |
| 12 May 2017 | SAT upholds SEBI's findings on merits but sends back the amount to be disgorged and the period of market restraint | SEBI order of October 2018 |
| January 2018 | SEBI bars the PwC network firms from certifying listed companies for two years and orders return of audit fees | Search summaries (Bar and Bench, LiveLaw) |
| 9 September 2019 | SAT sets aside the debarment but upholds disgorgement of about ₹13 crore in fees | BCAJ summary |
What the regulator and the court found
SEBI's 2018 order quotes the SAT as saying that the chairman and the managing director "were instrumental in creating fictitious invoices, fictitious receipts" and that fictitious monthly bank statements were prepared on that basis. It adds that the CFO, a vice president of finance and the head of internal audit, "inspite of noticing" fictitious documents, allowed the books to be prepared on them.
The CBI court convicted the accused of offences that, according to reports, included cheating, criminal conspiracy, forgery and falsification of accounts. Moneylife reports that those convicted included the chairman, two of his brothers, the former CFO, the former internal audit head and two former auditors. It also reports fines of over ₹5 crore each for the chairman and the managing director.
The audit side
The auditor question is where the Satyam case is most often misquoted, so here is what is on the record.
- SEBI's January 2018 order, as reported by LiveLaw, said the auditor accepted Satyam's monthly bank statements as final even though they did not match the company's daily statements. SEBI described this as a disregard for stipulated auditing practice.
- The SAT, on 9 September 2019, set aside the ban. According to the BCAJ summary, the tribunal said negligence does not automatically amount to fraud, that SEBI needed direct evidence of connivance, and that a cleverly designed fraud cannot necessarily be found by an auditor.
- The same ruling kept the disgorgement of about ₹13 crore in audit fees, because the auditors were found negligent on certain counts.
- The CBI court's verdict, per Moneylife, covered two former auditors among the ten convicted. We have not checked the outcome of any later appeal and do not comment on it.
In short: a regulator found serious failures of audit practice, a tribunal separated negligence from fraud, and a criminal court reached its own verdict. Those are three different findings. Do not merge them into one sentence.
Lessons auditors take from Satyam
- Get confirmations directly from the bank. Cash and fixed deposits were reported as overstated. An independent confirmation, sent and received by the auditor, is stronger than a statement handed over by the client. Our audit evidence guide explains why source matters.
- Reconcile evidence that should agree. If monthly statements and daily records disagree, that is a finding to chase, not a difference to accept.
- Test revenue and cash together. Fictitious invoices and fictitious balances reinforce each other. Look for receipts that never reached a real account.
- Keep documentation that shows the reasoning. The SAT's emphasis on a documented, reasonable process is a reminder of why audit documentation matters.
- Treat management override as a standing risk. When the people at the top create the false records, ordinary controls may not catch it.
Digital tools can help here, such as running Benford's law checks on invoice populations, but they supplement bank confirmations and do not replace them.
Frequently Asked Questions
What was the Satyam scam?
It was the falsification of Satyam Computer Services' accounts, which the chairman admitted on 7 January 2009. SEBI and a special CBI court later made findings and orders against the promoters and others.
Who audited Satyam?
Price Waterhouse, an Indian member of the PwC network, was the auditor named in the SEBI proceedings. We make no finding beyond what SEBI, the SAT and the court have said.
Was the auditor convicted?
Moneylife's report of the April 2015 verdict lists two former auditors among the ten convicted by the special CBI court. Separately, the SAT set aside SEBI's debarment of the audit firms in September 2019. Both are on the record, and they concern different proceedings.
How much money was involved?
The confession was reported as ₹7,136 crore. We did not verify the figure against the confession letter itself.
What changed after Satyam?
We did not verify a list of specific law changes in this check, so we do not make claims about them here. Our piece on NFRA enforcement themes covers the regulator's recent work.
Related Articles
Statutory facts on this page are checked against their sources, and the page says where it relied on secondary reporting. How we verify · Report an error