MicroStrategy Revenue Accounting Case: The Quarter Closed Before the Contracts Did

In the MicroStrategy revenue accounting case, three executives agreed to give up approximately $10 million to settle SEC civil accounting fraud charges over software revenue booked too soon. The Securities and Exchange Commission’s December 2000 announcement described contracts counted before they were properly signed and software sales counted before essential work was done. If you worked on the contracts, the development commitments or the quarter-end close, you may recognize how a transaction reached the earnings report before the business had earned the revenue.

Based in Vienna, Virginia, MicroStrategy sold software that helped customers analyze information in large databases, together with maintenance, training, consulting and development services. This page follows the software contracts and accounting decisions behind its SEC case. Our page on revenue recognition and premature sales follows the broader pattern of moving sales between quarters and the growth story investors hear.

What Did the MicroStrategy Revenue Accounting Case Involve?

The Securities and Exchange Commission alleged two central problems: recognizing software revenue while essential services or future products remained due, and recognizing revenue from contracts that were not properly signed within the reporting period. In its settled company order, the agency said MicroStrategy’s increasingly complex transactions outgrew the straightforward software-license sale. In the agency’s account, the accounting treated substantial obligations as though they had already been satisfied.

The order described a restatement that reduced reported revenue by approximately $66 million out of $365 million over three years. It said the public reports had shown positive net income when MicroStrategy should have reported annual losses. When the company announced its intended correction, its shares lost more than 60% of their value that day. The restatement changed the picture investors had been given of the business.

The Signature Date Followed the Desired Result

According to the Securities and Exchange Commission’s order, MicroStrategy held customer-signed contracts until after the quarter closed, leaving its own signature outstanding. Only after determining the desired financial results did the company divide those contracts between the closed quarter and the new one, sign them and assign effective dates. Both the applicable accounting requirements and MicroStrategy’s own policy required both parties’ signatures before revenue recognition.

The order described an additional way to keep the date open:

One transaction made the quarter boundary concrete. The Securities and Exchange Commission said negotiations with NCR continued past midnight on September 30, 1999, and MicroStrategy signed the final agreement in the early hours of October 1. The agency said MicroStrategy nevertheless recognized $17.5 million in the quarter that had just ended. The contract missed the quarter. Its revenue made it.

Another contract carried a different date from the actual signature. The order said Choicepoint signed on April 2, 1999, but dated the agreement March 31, and MicroStrategy recognized $956,000 in the earlier quarter. For a contracts employee, the difference between the date printed on the agreement and the date the customer actually signed could explain the revenue entry.

The Software Still Needed the Work

The order applied the AICPA’s Software Revenue Recognition standard to these sales. For software that did not need significant production, modification or customization, it required evidence of an agreement, delivery, a fixed or determinable fee and probable collection before revenue recognition.

The historical standard also required the company to consider whether promised services were integral to making the licensed software work for the customer. Where they were, the company had to account for the combined contract rather than treat the license as a completed, separate sale. MicroStrategy’s public filings and internal policy said it followed those rules, while the Securities and Exchange Commission alleged that its accounting recognized revenue earlier than they allowed.

The ShopKo transaction shows why the customer’s intended use mattered. According to the order, the deal included software licenses, extensive consulting and development services, and a right to purchase MicroStrategy shares. Most of the licenses were to be used with applications that MicroStrategy still had to develop. The order said the company nevertheless recorded the entire $4.5 million as software-license revenue, assigning none to the service obligations or the stock-purchase right.

The Securities and Exchange Commission’s order described the same problem in a Strategy.com arrangement with Ameritrade. In that account, MicroStrategy agreed to build customized systems that would let Ameritrade provide information channels to customers, with software licenses for the applications still to be developed. The order said the company recognized the full $6 million as product revenue at the transaction date, although revenue belonged over the contract’s term. The development team still had a job to finish. In the accounting, the sale was complete.

Future Products Counted Before Delivery

NCR’s agreement presented another problem beyond the signature date. The order said it promised all current and future generally available products in MicroStrategy’s product line, yet the company could not establish the fair value of unspecified future products. Those promises required accounting for the contract over time.

Future promises also appeared outside the main agreement. The order said MicroStrategy’s sales staff gave KMart a side letter promising future product at no cost, and the company prematurely recognized approximately $2.3 million. That revenue was later deferred because the product had not been delivered and its value could not be determined. A salesperson could know the promise that changed the accounting before someone reading the invoice knew it existed.

How Do You Catch Software Revenue Accounting Fraud?

Catching accounting fraud in a software-revenue case means connecting the booked sale to the actual agreement, the work still owed and the decision to put it in that quarter. We examine those connections with the person who understands the transaction, using the records behind the reported number. MicroStrategy’s order makes the comparison unusually concrete: a signature date, a development obligation and a revenue entry can each tell a different part of the same deal.

Contract drafts, correspondence and signature dates show when the parties actually finished agreeing. Delivery and development records can show whether the customer had the promised product or still needed the company to build it. An accounting-policy memorandum explains the treatment the company said it would use, while quarter-end entries and close approvals show the treatment it chose.

The Securities and Exchange Commission’s required reforms targeted that same chain. The company had to establish a contract signature log, get agreements signed by all parties to accounting before recognizing revenue, and retain necessary contract documents, including drafts and correspondence. Nonstandard agreements required the chief financial officer’s approval before execution.

For a revenue-recognition employee, the useful account is specific to the transaction. What had the customer accepted, what remained to be delivered, which period received the revenue, and who approved that treatment? We work through those connections with you, including the difference between the written policy and the instructions used to close the books.

Who Signed MicroStrategy’s Contracts and Reports?

The Securities and Exchange Commission alleged that the former chief financial officer bore principal responsibility for accurate financial reporting and signed the periodic reports. In the same account, the chief executive signed reports and negotiated several of the largest restated deals, while the chief operating officer negotiated transactions and signed contracts on which revenue was improperly recognized.

The agency resolved the company’s reporting and accounting-control failures separately from the executives’ civil accounting fraud charges. The company order required MicroStrategy to change how it approved contracts, recognized revenue and supervised financial reporting. It required an internal audit department and an additional independent director with financial-reporting or audit-committee experience.

What Did the MicroStrategy Executives Agree to Pay?

The executive settlement required the officers to give up money, which the agency called disgorgement. The Securities and Exchange Commission allocated $8,280,000 to the chief executive, $1,630,000 to the chief operating officer and $138,000 to the former chief financial officer. It separately said each officer would pay a $350,000 civil penalty. We find the bargain absurd: the officers agreed to give up millions, but admitted nothing.

What Can a Revenue-Recognition Employee Explain?

A revenue-recognition employee may understand why a contract’s accounting treatment departed from its commercial terms. A development commitment can explain why a license was not ready to stand alone, while a signature trail can explain why the reported quarter was wrong. The MicroStrategy order connects both kinds of knowledge to the numbers investors received.

A related pattern appears in Under Armour’s case. The Securities and Exchange Commission alleged that Under Armour misled investors about revenue growth supported by customer orders pulled into earlier quarters. MicroStrategy’s order focused on unsigned contracts and inseparable software obligations. In each account, the employee who knew why revenue landed in a particular quarter could explain something the public growth story left out.

The 2018 study The Significance of Whistleblowing as an Anti-Fraud Measure, published in the Journal of Forensic & Investigative Accounting, examined occupational-fraud survey data. It found that frauds involving more participants were more likely to be detected through whistleblowing. That finding matters to a transaction crossing sales, contracts, development and accounting: knowledge of the bargain can sit with people who never write the earnings announcement.

Eligible SEC whistleblowers can share an award of 10% to 30% of qualifying money collected when an action involves more than $1 million in monetary sanctions. We assess how your knowledge of the contract and the reporting decisions can support a securities fraud whistleblower case.

If the conduct you know also involves false claims for government money, we assess that part of the matter with you. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

You Know What Was Still Unfinished

If a software sale reached the earnings report while signatures or essential work were still outstanding, talk with our whistleblower experts about the transaction you know. We build your case around the contract, the accounting decisions and your view inside the business, bringing in securities fraud whistleblower lawyers who understand software-revenue cases. We stay alongside you as that firsthand knowledge becomes a case for government action.