Peregrine Systems: Software Sales the Customers Didn’t Have to Pay For

In its fictitious software revenue case against Peregrine Systems, the SEC alleged that the company booked sales its customers had no binding obligation to pay, then used bank financing to disguise the unpaid receivables. For a sales-finance or receivables employee, the telling detail is whether the customer owed what the ledger said it owed.

Peregrine Systems sold infrastructure management software from San Diego. The Securities and Exchange Commission brought its civil case in the Southern District of California, alleging that the company inflated its revenue and stock price. This page follows Peregrine’s reseller contracts, bank financing and collection entries. The broader pattern of fictitious sales and round-trip transactions connects those practices to other businesses.

What Was the Peregrine Systems Revenue Restatement?

Peregrine’s revenue restatement reduced previously reported revenue of $1.34 billion by $509 million. At least $259 million of that reduction reversed transactions that lacked substance, according to the SEC.

The SEC alleged materially incorrect financial statements for 11 consecutive quarters, from the quarter ended June 30, 1999, through the quarter ended December 31, 2001. Its complaint said the fraud came to light. The transaction allegations explain how reported software demand grew while the obligation to pay could remain somewhere in the future, or disappear altogether.

Reseller Contracts With a Hidden Exit

The SEC alleged that Peregrine parked software with resellers, known as channel partners, when direct sales to end users had not closed and the company needed revenue to meet its forecasts. The contracts appeared binding. Secret oral or written agreements could give the reseller a very different bargain.

According to the complaint, some channel partners had no obligation to pay because Peregrine would later arrange an end-user sale and send the payment through them. Others could back out of the license contract. Still others could bill Peregrine for services equal to the software licenses they had failed to resell. A purchase obligation could come with its own reimbursement.

The complaint describes the software revenue recognition requirements that applied at the time: evidence of an arrangement, delivery, a fixed or determinable fee and probable collection. It alleged that senior officers and sales and finance personnel understood those requirements but booked transactions that failed them. For someone who negotiated the side agreements, the important terms might never appear on the face of the contract accounting received.

Round-Trip Payments and an Elastic Quarter-End

Peregrine also allegedly financed its customers’ purchases by investing cash or stock in them while they agreed to buy its software. The complaint said customers then used the investment, or proceeds from selling the stock, to pay Peregrine. The receipt returned value the seller had supplied in the first place.

The SEC separately alleged that Peregrine booked revenue on swaps even when it did not intend to use the product it acquired, merely exchanged software inventory for resale or lacked support for the valuation. The purchase side of the transaction mattered as much as the sales side. A treasury employee might see the outgoing investment while a sales employee saw the incoming order.

Quarter-end pressure also reached the calendar. According to the complaint, Peregrine kept its books open and recorded transactions in an earlier quarter even though they closed afterward, sometimes months later. The SEC quoted the officers’ description of that practice:

In the SEC’s telling, the forecast set the closing date. If you worked on contract execution or the close, you could see which quarter the agreement actually belonged to. December had been given an extension.

Bank Cash Made Unpaid Receivables Look Collected

The SEC alleged that Peregrine used receivables financing to conceal the collection problem created by its revenue entries. Unpaid balances pushed up days sales outstanding, the measure of how long a company takes to collect receivables. According to the complaint, the senior treasury manager calculated how much to sell to banks each quarter to bring that measure down to management’s target.

The banks supplied cash, and Peregrine removed the receivables from its balance sheet. But the complaint alleged that the banks could turn back to Peregrine for payment. When customers failed to pay, Peregrine often paid the banks itself or repurchased the receivables. The company had kept the collection risk while accounting as though it had passed that risk to the banks.

In its restatement, Peregrine added a $141.6 million loan balance to its March 31, 2002 balance sheet because the financing should have been recorded as borrowing. The SEC contrasted the arrangements with this disclosure in Peregrine’s last quarterly report before the fraud surfaced:

In the SEC’s account, the bank agreements and the company’s payments contradicted that public description. A receivables-finance employee could know exactly who had to pay when the customer did not. The risk had left the disclosure before it left the company.

A Fabricated Invoice Filled the Remaining Gap

The complaint alleged that even financing the available receivables could leave Peregrine short of its target. In June 2001, the senior treasury manager allegedly created a false $19.58 million invoice with senior management’s approval and sold it to a bank. The chief financial officer signed an assignment representing that the invoice reflected a valid receivable.

The SEC said the transaction overstated operating cash flow and understated both receivables and liabilities to the banks. The invoice, the signed assignment and the supposed customer’s obligation are different parts of that story. Someone responsible for the customer account could know what the bank’s paperwork concealed.

One Customer Payment Reduced Receivables Twice

The SEC also alleged a second reduction of receivables after Peregrine had already removed them in a bank financing transaction. Peregrine continued collecting from customers, then remitted the money to the banks. During the gap, the senior treasury manager allegedly reduced receivables again, treated the cash as Peregrine’s and omitted the corresponding amount owed to the bank.

The complaint said the manager called this the “double dip.” Peregrine allegedly reversed the entries in the following quarter when it sent the money to the banks. For a cash-application employee, the reversal log could explain why a quarter-end collection looked better than the account’s actual history.

The Write-Off Changed the Story of the Sale

According to the complaint, Peregrine also hid uncollectible receivables in acquisition-related expense accounts. The SEC alleged that many of those receivables should never have been recorded as revenue, and that officers and employees knew the write-offs had nothing to do with acquisitions. Presenting them as one-time acquisition charges also kept them out of the company’s disclosed pro forma operating results.

The accounting records offered another view of the problem. The complaint alleged that Peregrine lacked detailed sales and receivables records that reconciled to its general ledger. Employees tracked license revenue in a spreadsheet called the Revenue Report, then made a manual quarter-end entry forcing the ledger to match it without reconciling the difference. The SEC’s account describes the spreadsheet supplying the answer the accounting system was made to accept.

What Records Show Fictitious Software Revenue?

For suspected software revenue fraud, useful evidence connects the customer’s actual commitment, the financing terms and the cash entries to the number reported to investors. The corporate records trail follows that connection from the transaction through the close and the public financial statements.

Customer confirmations and correspondence can reveal an exit right or a refusal to pay. Financing agreements can identify who bears the collection risk. Cash applications and reversal logs can connect a reported receipt to the customer, the bank and the accounting period. We examine those records with the person who understands what the business actually agreed to do.

The same need for evidence beneath the sales total appears in Luckin Coffee. In its accounting-fraud allegations, the SEC described a false operating database and altered accounting and bank records supporting fabricated retail sales. At Peregrine, the complaint instead followed hidden contract terms, financing agreements and collection entries. In each account, records outside the reported revenue total supplied the commercial story investors were missing.

What Did the SEC Judgment Require?

The SEC’s announcement of the July 23, 2003 final judgment describes an order Peregrine agreed to that prohibited violations of securities antifraud, reporting, accounting-record and internal-control requirements. It also required an internal auditor, a corporate compliance officer, employee training and accelerated reporting on internal controls.

The judgment also required Peregrine to disclose the condition of its internal controls and financial-reporting procedures when its reorganization plan became effective. The court approved the SEC’s decision to require neither a civil money penalty nor repayment of gains in this action.

We see an enormous revenue correction and a company resolution with no civil money penalty. For an insider, those controls concern decisions already visible in daily work: who approves the sale, who signs the financing assignment and who directs the entry that makes the quarter close.

Why Knowledge Inside Sales Finance Matters

A 2019 working paper hosted by MIT Sloan, Do Corporate Whistleblower Laws Deter Accounting Fraud?, examined companies exposed to state False Claims Acts through state pension-fund ownership. It estimated a 5% to 9% reduction in accounting-fraud likelihood after that exposure, using financial-statement measures of fraud risk.

In a smaller internal-audit sample, the paper found little evidence of increased audit spending, hours or staffing after exposure to those laws. Its findings point to the prospect of someone speaking up as a source of pressure on the numbers. In Peregrine’s alleged scheme, a person who knew the customer’s side agreement or the bank’s right to payment could explain something the reported totals concealed.

For someone considering reporting securities fraud to the SEC, we assess how that knowledge connects to the transactions and disclosures. Under the SEC whistleblower rules, eligible whistleblowers can receive 10% to 30% of qualifying sanctions collected when a qualifying action exceeds $1 million in monetary sanctions.

A separate route concerns false claims for government money: a whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. We work through which program fits the conduct with you.

You Know Whether the Customer Owed It

If your sales ledger and your customer’s understanding tell different stories, speak with our whistleblower experts about the gap. We build your securities fraud case around the contracts, financing and collection decisions you know, and bring in securities fraud whistleblower lawyers who understand software revenue. You gain a team that can challenge the accounting explanation and stay beside you through the case.