Satyam Fabricated Accounts and Audit Failures: The Invoices Were Hidden From the People Doing the Work

Satyam agreed to a $10 million settlement in the Securities and Exchange Commission’s case over fabricated accounts. The SEC alleged that false invoices hidden from business-unit managers overstated revenue by $1.1 billion. We see a company settlement dwarfed by the revenue the agency said was invented. If you work in billing, treasury or audit, you may recognize the gap between a number everyone signs off on and a transaction nobody in the business remembers.

Satyam Computer Services was an information technology services company based in Hyderabad, India, with depositary shares trading on the New York Stock Exchange during the alleged fraud. This page follows its invoice system, bank records and separate auditor proceedings. Our page on fictitious sales and round-trip transactions follows the broader pattern of invented business and payments made to look like independent sales.

What Did Satyam Report, and What Did the Records Show?

The SEC alleged that Satyam reported revenue from services it never provided, then manufactured evidence that customers had paid for them. Its civil complaint against the company describes a chain running from the invoice management system into the accounting system, the financial statements and the reports investors read.

For actual business, Satyam prepared invoices for information technology services, sent them to customers and recorded them in its electronic invoice system. That system exported data into the financial system, where revenue entered the company’s books. The books then supplied the financial statements. A fabricated invoice inserted near the beginning could travel through the rest of that chain as apparent business.

According to the complaint, senior management gave selected employees administrative access that allowed false invoices to count toward revenue while concealing them from business-unit heads. Those managers would have recognized services their units never supplied or customers their units had never dealt with. The alleged bypass separated the people reporting the revenue from the people who could say whether the work happened.

The SEC identified 6,603 false invoices generated from 2003 through September 2008 and exported into Satyam’s financial system. The complaint also described additional false invoices created without the special administrative access, so the access setting was one way into the books, rather than the whole inquiry.

The bank records supplied the next fiction. The SEC alleged that management prepared false bank statements to support the reported revenue and income, then falsified fixed-deposit balances and interest to make the invented income look invested. In its fixed-deposit comparison for March 31, 2008, the complaint put reported balances and interest at $912,660,956 against actual balances and interest of $2,210,812.

The profitability story moved in the wrong direction too. The complaint alleged that Satyam reported increasing net income while actual net income declined, and reported profits during quarters when it was losing money. For a reconciliation accountant, the issue is the connection between the invoice, the claimed receipt and the bank’s own record of the money.

How Could Fabricated Accounts Survive the Audit?

The SEC found that Satyam’s auditors failed to perform procedures confirming cash, cash equivalents and accounts receivable. In its announcement of the auditor action, the agency described a failure to control bank confirmations that extended beyond the Satyam engagement.

The SEC’s account of its order against the India-based PricewaterhouseCoopers firms says audit staff:

That is the failure an audit insider can recognize: who sent the request, who received the response and whether anyone checked with the bank. In the SEC’s account, we see an independent confirmation process handed back to the company whose cash needed confirming. Management supplied the number and the reassurance.

Inside a public company’s reporting process, accounting personnel maintain the books and reconciliations, the audit committee oversees the external auditor, and the auditor supports its opinion with evidence in the audit file. Our page on auditors and securities fraud gatekeepers follows those responsibilities more broadly. Here, the concrete failure was the handling of outside confirmation, a task whose value depended on keeping the client’s answer separate from the bank’s.

The Admission and the Attempt to Replace Fiction With Property

The SEC complaint records an admission by Satyam’s then-chairman, submitted to the SEC in a company report. The letter acknowledged materially false revenue and fictitious cash and bank balances. It also explained why management had kept the inflated performance going: the chairman feared that revealing the company’s poor results would invite a takeover that exposed the fraud.

According to the complaint’s account of the letter, the attempted acquisition of Maytas Properties and Maytas Infra was a final effort to replace fictitious assets with real ones. The real estate and infrastructure businesses were controlled by the chairman and his brother, Satyam’s then-chief executive. Investors and analysts challenged the proposed move into unrelated businesses and the transfer of company assets to that family. Satyam abandoned the acquisition after announcing it in December 2008.

For someone in corporate development or treasury, this connects a proposed transaction to the accounts it was supposed to change. The acquisition proposal had a business explanation for investors and, in the chairman’s own account recorded by the SEC, a very different purpose inside the company.

What Did the Separate Satyam Proceedings Establish?

The SEC’s April 5, 2011 announcement said Satyam agreed to settle fraud charges and undertake internal reforms, while five India-based PwC firms agreed to a separate $6 million SEC penalty over their audit failures. The agency found a broader quality-control failure across PW India.

The audit firms agreed to accept no new U.S.-based clients for six months and appoint an independent monitor to oversee their reforms. Those reforms included new review controls before issuing audit opinions, revised audit procedures and staff training. In a separate Public Company Accounting Oversight Board proceeding, Lovelock & Lewes and Price Waterhouse Bangalore agreed to a $1.5 million penalty concerning the Satyam audit engagement.

The SEC complaint says India’s government dissolved Satyam’s board and appointed new directors, after which Tech Mahindra became the controlling shareholder. The agency put realized losses among institutional investors holding Satyam’s depositary shares at over $450 million. Those investors had bought into a company whose reported cash and profitability, according to the agency, depended on fabricated records.

What Evidence Is Needed for Whistleblowing on Fabricated Accounts?

For fabricated accounts, useful securities fraud evidence connects the reported number to the work, customer and payment behind it. Satyam’s case makes that connection unusually concrete: invoices entered the revenue system while business-unit managers could not see them, and bank information supplied apparent support for the resulting balances.

A billing employee may know which customer ordered the service and which team performed it. Customer records, invoices and the version visible to the business unit can explain a discrepancy that disappears in the consolidated revenue total. Someone administering the invoice system may know who had access to create entries that ordinary users could not see.

A treasury or bank-reconciliation employee sees another part of the same story. Receipts, deposit records and reconciliations connect a claimed payment to an actual account. An audit employee may know how confirmation responses arrived, what the workpapers recorded and what happened to an unresolved exception. We work with you to connect that knowledge to the decisions behind the reported accounts.

The same need for supporting fiction appeared at Luckin Coffee. In its account of the Luckin allegations, the SEC described a false operating database and altered bank and accounting records supporting fabricated retail sales. The SEC said the annual external audit uncovered that misconduct. The comparison makes the audit work itself worth examining: what evidence reached the auditor, and how was it tested?

If your knowledge comes from an audit or compliance role, how you learned about the conduct belongs in our conversation. We address that role with securities fraud whistleblower lawyers who understand accounting matters and the records behind what you know.

Can Someone in India Report U.S. Securities Fraud?

Someone living or working in India can qualify for the SEC whistleblower program. The SEC says a person need not live or work in the United States to qualify for an award. Satyam’s U.S. connection was concrete: its depositary shares traded in New York, and its company reports reached the SEC and U.S. investors.

For someone reporting securities fraud from outside the United States, we examine the company, its securities and the statements the overseas records may contradict. We work through SEC reporting and award questions with you, including the connection between what happened in the business and what investors were told.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. That program concerns fraud against government money; the SEC securities whistleblower program has its own award process. We identify the program that fits the conduct you know.

Why the Person Behind Fabricated Accounts Matters

Research on fraud detection helps explain the value of a person who knows how an entry was created. The 2018 Journal of Forensic & Investigative Accounting study The Significance of Whistleblowing as an Anti-Fraud Measure found that whistleblowing detected 35.9% of the frauds in a sample of 4,943 cases, compared with 21.4% detected through internal controls.

The study also found that whistleblower detection became more likely as more people participated in a scheme. At Satyam, the SEC’s allegations involved instructions from senior management, employees entering invoices, business-unit heads excluded from seeing them and auditors handling confirmations. Someone who understood one of those handoffs could explain what the finished financial statement concealed.

The 2019 review Accounting Fraud: A Literature Review, published in Risk Governance and Control: Financial Markets & Institutions, examines both statistical detection methods and knowledge gathered through people inside a business. That is the distinction we bring back to the invoice and the bank confirmation: a pattern in the numbers can direct attention, while the person who handled the transaction can explain how the number got there.

When the Invoice and the Bank Tell Different Stories

If you know why a reported sale never reached a customer or why a confirmation never came from the bank, speak to one of our Whistleblower Experts about how the revenue was invented. We build your strongest securities fraud whistleblower case around the contradiction you can explain, bring in securities fraud whistleblower lawyers who know financial reporting and audit failures, and stay beside you through the reporting and award process.