Zucco Partners, LLC v. Digimarc Corp.

552 F.3d 981, 2009 U.S. App. LEXIS 583, 2009 WL 57081
CourtCourt of Appeals for the Ninth Circuit
DecidedJanuary 12, 2009
Docket06-35758
StatusPublished
Cited by873 cases

This text of 552 F.3d 981 (Zucco Partners, LLC v. Digimarc Corp.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Ninth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Zucco Partners, LLC v. Digimarc Corp., 552 F.3d 981, 2009 U.S. App. LEXIS 583, 2009 WL 57081 (9th Cir. 2009).

Opinion

BYBEE, Circuit Judge:

Zueco Partners, LLC and other named plaintiffs (collectively, “Zueco”), on behalf of those who purchased publicly-traded securities of Digimarc Corporation (“Digi-marc” or “the Company”) between April 22, 2003 and July 28, 2004, appeal the District of Oregon’s dismissal of their Second Amended Complaint, which alleges that Digimarc (and two of its officers, Bruce Davis and E.K. Ranjit) violated sections 10(b) and 20(a) of the Securities Exchange Act of 1934 and the regulations promulgated thereunder, including Rule 10b-5. Zueco contends that the district court erred in determining that its com *987 plaint failed to allege a strong inference of scienter as required by the Private Securities Litigation Reform Act (“PSLRA”) because that court applied a more stringent standard than required by the Supreme Court’s recent decision in Tellabs, Inc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 127 S.Ct. 2499, 168 L.Ed.2d 179 (2007). Although we have previously evaluated the sufficiency of such claims under the PSLRA by the standards of In re Silicon Graphics Inc. Securities Litigation, 183 F.3d 970 (9th Cir.1999), and In re Daou Systems, Inc. Securities Litigation, 411 F.3d 1006 (9th Cir.2005), we have yet to fully explain how the Court’s Tellabs decision relates to much of our analysis under those cases.

The district court determined that, pursuant to Daou, the plaintiffs’ complaint failed to allege scienter with the requisite particularity to survive dismissal under the PSLRA’s heightened pleading standard. Because we hold that the Court’s decision in Tellabs does not materially alter the particularity requirements for scienter claims established in our previous decisions, but instead only adds an additional “holistic” component to those requirements, we affirm the district court’s dismissal of the complaint with prejudice and hold that Zueco has failed to adequately plead a strong inference of scienter. 1

I

Accounting for the costs of internal software development is not a simple task. In order to comply with Generally Accepted Accounting Principles (“GAAP”), a company that engages in internal software development projects must make subtle differentiations between three stages of development that determine whether expenditures incurred must be “expensed” (recorded immediately on the company’s financial statement as a cost incurred) or “capitalized” (recorded as a cost incurred in increments over several financial statements). This distinction is important because if an expenditure is capitalized rather than expensed a company will (in the absence of other factors) look more profitable in the short term (albeit less profitable in the long term) and show a more consistent pattern of reported income— because its expenditures are spread out over a longer period of time. Under GAAP, if a software development project is in the “preliminary project stage,” wherein the company is evaluating development and marketing alternatives; or in the “post-implementation/operation stage,” in which the developed software is placed into service, most expenditures related to the project must be expensed. If, however, a project is in the “application development stage,” in which management authorizes the project and has settled on a comprehensive development and marketing strategy, most expenditures incurred must be capitalized. Capitalized expenditures are amortized on a straight-line basis over the estimated useful life of the software developed (which, for a company like Digimarc, is generally three to five years).

According to Zueco, Digimarc, a fledgling Delaware corporation headquartered in Oregon, whose business centers on providing secure personal identification documents (such as drivers licenses) based on *988 digital watermarking technology, purposefully manipulated its financial prospects by, inter alia, capitalizing internal software development expenditures that should have been expensed. Zucco’s compendious 130-page Second Amended Complaint (“SAC”) claims that Digimarc “used two primary accounting manipulations to deceptively bolster Digimarc’s financial condition.” Namely, Digimarc “capitalize[d] on its asset balance sheet ordinary payroll costs that Digimarc paid to its software engineers and other employees so that the Company could avoid recognizing these expenses on its income statements.” Also, Digimarc allegedly “fail[ed] to recognize ordinary expenses incurred by the Company” and instead “improperly moved or retained these expenses in Digimarc’s inventory or property and equipment accounts as purported ‘project development expenses.’” The net effect of these manipulations, Zueco contends, was to deceive investors into believing that the young corporation had “turned the corner” from its early losses and had become profitable.

On September 13, 2004, Digimarc publicly announced that it had erroneously accounted for internal software expenditures and that due to these accounting errors it had likely overestimated earnings for the previous six quarters. The September announcement listed the improper capitalization of internal software development costs as the most likely source of these accounting errors, and also cited “other project cost capitalization accounting practices” of Digimarc’s ID Systems division (acquired from Polaroid in December 2001 and which represented 89 percent of the corporation’s revenue in 2003 and 2004) as containing potential errors that “may also result in additional adjustments which may affect prior periods.” On September 13, Digimarc estimated these accounting errors to “be in the range of approximately $1.2 million to $2.0 million” and to possibly “require a restatement of prior period financial statements.”

Although the full extent of these accounting errors (approximately $2.7 million in overstated earnings) was not revealed until April 5, 2005, when Digimarc’s formal restatement was issued, the corporation’s September 2004 announcement was enough to trigger a number of class action lawsuits. Zueco, which had purchased fifty shares of Digimarc stock in March 2004 (at a price of $12.76 per share) filed a class action lawsuit in the District of Oregon fifteen days after the corporation’s public announcement, alleging that defendants Digimarc, its Chief Executive Officer Bruce Davis, and its former Chief Financial Officer E.K. Ranjit violated sections 10(b) and 20(a) of the Securities Exchange Act of 1934 and its implementing regulations, including Rule 10b-5. Similar suits, which followed on October 5th and 6th, were eventually consolidated with Zucco’s action on December 16, 2004. Two unrelated actions alleging violations of California corporations law, meanwhile, were filed in California state court on October 19th, and subsequently re-filed in the District of Oregon. See In re Digimarc Corp. Derivative Litig., 549 F.3d 1223 (9th Cir.2008).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
552 F.3d 981, 2009 U.S. App. LEXIS 583, 2009 WL 57081, Counsel Stack Legal Research, https://law.counselstack.com/opinion/zucco-partners-llc-v-digimarc-corp-ca9-2009.