MEMORANDUM OPINION AND ORDER
Defendant PricewaterhouseCoopers, LLP (“PWC”) moves to dismiss plaintiff G. Philip Stephenson’s claim that PWC’s fraud caused him to lose his entire investment in Greenwich Sentry, a fund which invested in Bernard Madoffs Ponzi scheme. For the reasons that follow, the Court finds that Stephenson has not adequately alleged that PWC acted with scienter and grants PWC’s motion to dismiss Stephenson’s fraud claim.
BACKGROUND
This action is one of several pending in this district arising out of Bernard Ma~ doffs revelation in December 2008 that his multi-billion dollar investment firm, Bernard L. Madoff Investment Securities, LLC (“BMIS”), was a massive fraud.
Stephenson’s complaint alleges as follows. Stephenson is trustee of the Philip Stevenson Revocable Living Trust (“the Trust”). (Compl. ¶ 6.) In early 2008, Stephenson decided to invest the Trust’s assets as a limited partner in Greenwich Sentry, a limited partnership organized under the laws of Delaware. (Id. ¶ 9, 18.) Fairfield Greenwich (Bermuda) Ltd. (“FGB”), an investment advisor registered with the SEC whose “core product business model” was providing various management services for funds linked to BMIS, acted as general partner of Greenwich Sentry. (Id. ¶ 10.) Since Greenwich Sentry had no employees of its own, FGB was responsible for Greenwich Sentry’s due diligence and risk monitoring. (Id. ¶ 51.) FGB was in turn affiliated with Fairfield Greenwich Group (“FGG”), an investment management firm that offered its investors access to BMIS through so-called “feeder funds” such as Greenwich Sentry. (Id. ¶ 11.)
As a “feeder fund”, Greenwich Sentry invested substantially all of its limited partners’ investments in an account con *566 trolled by BMIS which acted as trader, broker, and custodian of all funds and securities in the account and reported results back to Greenwich Sentry. (Compl. ¶ 17.) Limited partners in Greenwich Sentry could make monthly withdrawals of funds funded either from a separate Greenwich Sentry account or from BMIS itself. {Id. ¶¶ 36, 38-9.)
PWC, a limited liability partnership organized under the laws of Ontario, Canada, acted as auditor for Greenwich Sentry from 2006 through 2008. {Id. ¶ 7.) PWC is a member of PricewaterhouseCoopers International (“PWC International”), a “Big Four” accounting firm which provides auditing, accounting, and other advisory services around the world. {Id. ¶ 8.) Like the other PWC International member entities, PWC held itself out as part of a unified business entity whose members utilize common knowledge bases and apply uniform policies and procedures. For example, as part of the firm-wide “Client Acceptance Assessment” and “Know Your Client” programs, all PWC International member firms are required to conduct research regarding the connections and/or potential conflicts of interest between new and existing clients as well as to review regulatory filings. {Id. ¶¶70, 81.) The data complied during these required inquiries is maintained in an automated database to which all member firms, including PWC, have access. {Id. ¶ 71.)
PWC and other member firms also have access to the Global Engagement Management System in which PWC International maintains data on the relationships between firm clients and on the managers responsible for relationships with those clients. {Id. ¶ 72.) Member use this database to locate employees serving related clients and exchange information with them. {Id.) Indeed, in December 2004, at the request of a PWC International member firm in Dublin, Ireland auditing a second BMIS feeder fund, a Bermuda member firm auditing a third feeder fund met with BMIS to discuss its operations “for the purpose of gaining comfort thereon for the audits by several PWC offices of a number of funds having money managed by [BMIS].” {Id. ¶¶ 76-77.) The Bermuda member firm reported the results of the meeting in a March 15, 2005 letter to the Dublin member firm and a member firm in the Netherlands that was PWC’s predecessor as auditor of Greenwich Sentry. {Id.) The Netherlands member firm in turn reported the results in a letter to an entity affiliated with FGG. {Id. ¶ 76.) This letter remained in PWC International automated files accessible to PWC. {Id. ¶ 78.)
PWC International member firms also hold themselves out as part of a firm with particular expertise in hedge funds and investment vehicles. PWC organized an Alternative Investment Funds Practice devoted to auditing hedge funds {id. ¶ 74), and PWC and its employees have been involved in developing industry standards for and guides to alternative investment auditing. {Id. ¶¶ 55-56.) PWC also audited seven other FGG feeder funds and assigned the same team auditing Greenwich Sentry to audit those funds as well. {Id. ¶ 44.)
PWC conducted an annual audit of Greenwich Sentry. For purposes of that audit, and the audit of other BMIS feeder funds, PWC developed an “Audit Plan.” (Compl. ¶ 65.) The 2008 Audit Plan proposed that PWC would conduct “discussion and enquiry with [BMIS]” and “obtain an understanding of the key control activities as they relate to the operations, sub-custodian and prime broker functions.” {Id.) The Audit Plan also indicated that PWC would “perform transaction testing on the investment strategy applied by [BMIS] for the applicable funds.” {Id.) And the Audit *567 Plan recognized the need to “confirm existence of investments” with BMIS and derivative contracts associated with BMIS’s investment strategy, a completely automated system called the “the split strike conversion strategy” (“SSC Strategy”). (Id.) In general terms, that strategy consisted of the purchase of a basket of securities corresponding to stocks in the S & P 100 Index as well as options to hedge the risk of those securities. (Bee id. ¶ 42.)
On February 20, 2008, after expressing interest in Greenwich Sentry, Stephenson received documents about one of Greenwich Sentry’s sister funds, Fairfield Sentry. (Compl. ¶ 18.) He was told that analogous documents for Greenwich Sentry were not yet available but that he could expect them to be similar and that they would be audited by a PWC International member firm. (Id.) These documents included a “due diligence questionnaire” that described protections in FGG funds, including the role played by PWC. (Id.) One week later, Stephenson received profit analyses for Fairfield Sentry which he was told by FGG would be representative of results he could expect as a limited partner in Greenwich Sentry. (Id. ¶ 19.)
In March 2008, Stephenson received the Greenwich Sentry Limited Partnership Agreement and fund reports showing that Greenwich Sentry earned profits of just under one percent as compared to a multipercentage point fall in the Down Jones Industrial Average (“DJIA”). (Compl. ¶ 20.) Stephenson also received the Greenwich Sentry PPM which described the SSC Strategy and explained that the Strategy was “implemented by [BMIS] ... through accounts maintained by the Partnership at that firm.” (Id. ¶¶ 20, 42.) Stephenson understood that PWC had approved some or all of these documents and would be serving as auditor for Greenwich Sentry. (Id. ¶21 (ellipsis in original).) That was critical for Stephenson as an experienced investor who knew the value of strong risk management: he specifically asked FGG whether PWC had identified any issues with Greenwich Sentry and never would have invested in the fund if PWC or a firm of equal repute was not auditing the fund. (Id. ¶¶ 22-24.) For its part, PWC understood that its auditing work would be relied upon by potential investors and limited partners such as Stephenson, particularly because there was no public market for Greenwich Sentry partnership interests that would facilitate public information regarding the fund. (Id. ¶¶ 85-86.)
On April 1, 2008, Stephenson executed a subscription agreement in his individual capacity and deposited $60 million in Greenwich Sentry accounts. (Compl. ¶ 27.) On May 1, 2008, Stephenson requested transfer of his account to the Trust. (Id.) Around this time, Stephenson received the 2006 and 2007 Greenwich Sentry financial statements in which PWC delivered unqualified audit opinions affirming that the statements were prepared in accordance with Generally Accepted Accounting Practices (“GAAP”) and Generally Accepted Accounting Standards (“GAAS”). (Id. ¶¶ 84-89.) After receiving those opinions, Stephenson executed a new subscription agreement in his capacity as trustee on June 1, 2008 and transferred his limited partnership interest to the Trust. (Id. ¶ 28.)
At first, the Trust’s investment appeared to be paying off. By October 31, 2008, Citco Fund Services (Europe) BV and Citco (Canada) Inc., the fund administrator and sub-administrator respectively, had reported that Stephenson’s original $60 million investment was worth $62,540,565. (Compl. ¶ 32.) And by the end of November 2008, the same investment had realized a 6.59% gain at a time when the DJIA experienced losses many *568 times that percentage. (Id. ¶ 33.) Of course, as the world now knows, those gains were illusory and Madoff needed money from investors like Stephenson to pay those prescient few who cashed out before the truth came out. Indeed, on December 11, 2008, when Madoff revealed his fraud, Greenwich Sentry refused to withdraw Stephenson’s investment and he has still never recovered a cent of his $60 million. (Id. ¶ 40.)
On January 26, 2009, Stephenson filed suit [1] against Citco Europe, Citco Canada, their parent Citco Group Limited (collectively “Citco”), and PWC alleging claims under New York law for breach of fiduciary duty against Citco and for gross negligence and breach of contract against Citco and PWC. On June 29, 2009, Stephenson filed an amended complaint [36] which he corrected [37] on July 2, 2009. The amended complaint alleged seven claims under New York law: breach of fiduciary duty and gross negligence against Citco, professional malpractice and fraud against PWC, and breach of contract and aiding and abetting fiduciary duty against both Citco and PWC. Stephenson’s fraud claim alleged that Greenwich Sentry’s financial statements were not prepared in accordance with GAAP and GAAS and that PWC’s unqualified opinion to the contrary was false.
In a memorandum opinion and order dated March 31, 2010, the Court dismissed Stephenson’s complaint in its entirety.
See Stephenson v. Citco Group Ltd.,
The Court dismissed Stephenson’s fraud claim on the ground that the complaint failed to allege that PWC acted with scienter. Applying the well-settled law of this Circuit, the Court held that alleged GAAP or GAAS violations do not establish scienter of their own force. See id. at 621. Though Stephenson also alleged that certain “red flags” should have put PWC on notice that there were control problems at Greenwich Sentry and that BMIS was a fraud, the Court held that the complaint did not allege that PWC had knowledge of these red flags. See id. at 624. And while PWC surely knew of BMIS’s incredible success and that Madoff acted as trader, broker, and custodian, the Court found that these did not give rise to the required “strong inference” of fraudulent intent. See id. However, the Court dismissed the fraud claim without prejudice and granted Stephenson leave to amend his complaint. See id.
Stephenson filed the Second Amended Complaint (the “SAC”) on June 18, 2010. Like the prior complaint, the SAC alleges that “PWC performed its audit recklessly by failing to adhere to its GAAS requirements, failing to discover the risks and failures at [Greenwich Sentry], or at or from BMIS impacting upon [Greenwich Sentry], and/or failing to report on those risks and failures or qualifying or withdrawing its Unqualified Opinion.” (Compl. ¶ 94.) In particular, the SAC alleges that PWC’s audit of Greenwich Sentry violated GAAP and GAAS and PWC’s own best practices in five ways.
First, the SAC alleges that GAAS required PWC to investigate Greenwich Sentry’s internal controls but that PWC did not take any meaningful steps to verify Greenwich Sentry and FGG’s representations that it had conducted due diligence *569 and implemented risk control mechanisms. {See Compl. ¶¶ 95-128.)
Second, the SAC alleges that, because Greenwich Sentry invested substantially all of its assets with BMIS, GAAS required PWC to investigate and test the internal controls at BMIS. The SAC alleges that PWC either never did so or recklessly ignored the results of any investigation or tests it did conduct. {See id. ¶¶ 129-146.)
Third, the SAC alleges that GAAS required PWC to investigate the representations and reliability of BMIS’s largely unknown auditor, Friehling and Horowitz (“F & H”), but that PWC either never did so or recklessly analyzed any documentation it received from F & H. The SAC alleges that, had PWC properly tested F & H, PWC would have known that information that it relied on F & H to provide could not form the basis of an unqualified opinion. {See id. ¶¶ 147-154.)
Fourth, the SAC alleges that, given the risks of fraud or misstatement presented by the lack of controls at Greenwich Sentry and BMIS, as well as by F & H’s inadequate auditing, GAAS required PWC to independently verify BMIS assets, including option contracts necessary to the SSC Strategy.- The SAC alleges that PWC never did so or recklessly ignored the results of any verification it did undertake. {See id. ¶¶ 155-177.)
Fifth, the SAC alleges that GAAS mandated PWC to require Greenwich Sentry to disclose that FGG was not performing the due diligence and risk management services for which it was earning fees. The SAC alleges that PWC did not do so and that the Greenwich Sentry financial statements never disclosed as much. {See id. ¶¶ 178-183.)
In addition to GAAP violations, the SAC, like the prior complaint, also describes a number of red flags “which would place a reasonable auditor on notice that BMIS was engaging in fraud” such that offering an unqualified opinion was reckless. (Compl. ¶ 184.) Like the prior complaint, the SAC alleges that centralizing management, trading, and reporting functions for Greenwich Sentry with BMIS, which lacked proper controls or a certified auditor, “constituted a red flag of the likelihood of fraud involving [Greenwich Sentry] and BMIS.” {Id. ¶ 195).
The SAC alleges another red flag alleged in the prior complaint: that BMIS’ extraordinary returns should have placed PWC on notice that those returns were illusory. {Id. ¶ 225.) However, the SAC pleads this red flag slightly differently than the prior complaint did. The SAC alleges that the combination of three factors constituted a red flag: (1) BMIS’ outsized returns and the fact that its funds reported gains in 95% of the months in which they were operating {id. ¶ 226); (2) BMIS purported to have achieved these results despite a risk level that was as extraordinarily low as its returns were extraordinarily high {id. ¶ 228); and (3) BMIS was “out of the market” at the end of every month even when it would have been profitable to be in the market if BMIS was really employing the automated SSC Strategy {id. at ¶ 231). The SAC alleges that, taken together, these factors should have put PWC on notice that BMIS’ trading strategy was a fraud and that BMIS was “out of the market” at the end of each month to avoid SEC reporting requirements.
The SAC also alleges five new red flags. The SAC alleges that “PWC had either actual knowledge of the facts contained in the Red Flags ... or the Red Flags were so obvious that PWC must have been aware of them if it had conducted any audit at all.” (Compl. ¶ 185.)
*570 First, the SAC alleges that BMIS reported asset values for “feeder funds” audited by PWC and other PWC International member firms that in the aggregate exceeded the value of the total assets under BMIS management that BMIS reported to the SEC. (See id. ¶¶ 199-215.)
Second, the SAC alleges that, given the large size of BMIS assets under management, the fact that BMIS purported to enter and exit the market en masse was a red flag of fraud because trading such a large portion of the market capitalization of major stocks would have caused market volatility that never in fact materialized. (See id. ¶¶ 216-224.)
The third and fourth new red flags relate to the SSC Strategy’s use of options to hedge its equity positions. Though BMIS claimed that it used private counterparties to place its own hedges through the “over-the-counter” or OTC market, these counterparties would have utilized the public options market to place their own exchanges. (Id. ¶ 241.) The SAC alleges that, because BMIS had such a high volume of assets under management and purported to move all of those assets at the same time, BMIS could not have been hedging its positions because the OTC market could not have supported the volume required to do so. (See id. ¶¶ 240-252.) And the SAC further alleges that because no counterparties could have supported their own positions in the public options market, no such counterparties existed. (See id. ¶¶ 253-266.)
Finally, the SAC alleges a composite red flag that there were red flags at all three stages of BMIS’s purported strategy: BMIS purported to trade in volumes that would have caused market distortion that never occurred; BMIS purported to utilize options in volumes that the market did not support; and BMIS purported to place its options with counterparties even though no counterparty could obtain options in volumes sufficient to hedge its own risk. The SAC alleges that “even if any one individual stage, of risk did not, standing alone, signal a red flag to PWC, the combination of risks and anomalies presented by all three supposed stages of the strategy suffice to create a red flag that BMIS’s purported strategy was a house of cards, and that it must be operating a fraud.” (Compl. ¶ 268 (emphasis in original).)
On August 20, 2010, PWC moved [62] to dismiss the SAC.
LEGAL STANDARDS
Whether Stephenson has adequately pled a claim for fraud is governed by Federal Rules of Civil Procedure 8(a)(2) and 9(b), the latter of which requires plaintiffs to plead fraud claims with particularity.
“Federal Rule of Civil Procedure 8(a)(2) requires only ‘a short and plain statement of the claim showing that the pleader is entitled to relief,’ in order to ‘give the defendant fair notice of what the claim is and the grounds upon which it rests.’ ”
Bell Atl. Corp. v. Twombly,
Since Stephenson alleges fraud, the Court must scrutinize his claim even further because Federal Rule of Civil Procedure 9(b) requires plaintiffs to plead fraud with particularity. Fed.R.Civ.P. 9(b). Under that rule, long-standing case law in this Circuit requires plaintiffs to “allege facts that give rise to a strong inference of fraudulent intent.”
Acito v. IMCERA Group, Inc.,
In addition, “there are limits to the scope of liability for failure adequately to monitor the allegedly fraudulent behavior of others.”
Novak v. Kasaks,
Under this “demanding” standard, “failures to comply with Generally Accepted Accounting Practices or other such irregularities are insufficient to establish recklessness.”
W. Va. Inv. Mgmt. Bd. v. Doral Fin. Corp.,
“A complaint might reach the ‘no audit at all’ threshold by alleging that the auditor disregarded specific ‘red flags’ that would place a reasonable auditor on notice that the audited company was engaged in wrongdoing to the detriment of its investors.”
In re Tremont Sec. Law, State Law and Ins. Litig.,
But an unseen red flag cannot be heeded. Hence courts in this Circuit have consistently dismissed fraud claims against auditors — including against auditors of BMIS feeder funds — that have not sufficiently alleged that an auditor knew of red flags.
See In re Beacon Assoc. Litig.,
And only in a select few cases have courts in this Circuit found that, “because the red flags would be clearly evident to any auditor performing its duties, one could reasonably conclude that [the auditor] must have noticed the red flags, but deliberately chose to disregard them.... ”
In re Philip Serv. Corp. Sec. Litig.,
Nor is it enough to “merely alleg[e] that the auditor had access to the information by which it could have discovered the fraud....”
In re Tremont,
A defendant has reason to look where it is aware of red flags, but flags are not red merely because the plaintiff calls them red.
See In re Marsh & Mclennan Cos., Inc. Sec. Litig.,
DISCUSSION
In order to survive a motion to dismiss, the SAC must “allege facts that give rise to a strong inference of fraudulent intent.”
Acito,
The five GAAS violations alleged by the SAC are not such facts. It is well-established that “allegations of GAAP and GAAS violations are not sufficient, on their own, to establish scienter.”
In re AOL Time Warner,
However, none of the seven red flags alleged in the SAC supplies the required “strong inference” of fraudulent intent. Most of these red flags allege no more than that PWC had access to information by which it
could
have discovered warning signs of fraud or that PWC
would
have discovered these warnings signs if it had conducted an audit in accordance with GAAS and its own policies. Perhaps that is true, though even that suggestion seems questionable since numerous other entities had access to the same information and none of them discovered Madoffs fraud before he revealed it. But, in any event, the SAC does not allege facts from which the court could infer that PWC actually knew about and ignored most of these warning signs. And the two red flags which PWC did seem to know do not appear to have put PWC on notice of a fraud. Therefore, like at least four other courts who have considered similar suits against auditors of BMIS feeder funds,
see In re Beacon Assoc.,
The first red flag alleged is that “there were no verifiable controls over BMIS”, “BMIS had exclusive control of the management of [Greenwich Sentry] funds, was the sole executing broker for trades involving [Greenwich Sentry] funds and for the [Greenwich Sentry] trading strategy; and was the sole custodian of [Greenwich Sentry] funds” as well as “the sole source of information for [Greenwich Sentry] trades and asset values.” (Compl. ¶ 193.) The SAC alleges that PWC knew these facts because they were disclosed in Greenwich Sentry’s public documentation.
(Id.
¶ 194.) However, the Court has already held that this alleged warning sign “is far too mild to support an inference of recklessness on the part of PWC.”
Stephenson I,
Stephenson argues that PWC’s reliance on
Anwar
is bootstrapping because that decision cited the Court’s prior ruling and the SAC “newly pleads in detail the significance of the operational risk at BMIS for the financial statements of [Greenwich Sentry], which is of sufficient significance to an auditor’s task that it must have been obvious in the course of a proper audit.” (PL’s Opp’n at 9-10.) The Court is not persuaded. The SAC’s new allegations are largely general statements about the importance of “operational risk” to an auditor. True, the SAC alleges that operational risk is “heightened where [an auditor] knows that the audit client has not
*576
arranged for, or is not performing, due diligence and ongoing risk monitoring and oversight” and “the actual auditor for such third party or service organization is known by the auditor of the client to be an inadequate protection against detecting and identifying the operational risk....” (Compl. ¶¶ 188-89.) But this is itself bootstrapping: the former claim essentially repeats the insufficient allegation that PWC failed to investigate internal controls; the latter claim essentially repeats the conclusory and insufficient allegation that PWC knew that FH was not a certified or reputable auditor.
See Stephenson I,
The second red flag alleged is that BMIS reported asset values for “feeder funds” that in the aggregate exceeded the value of the total assets under BMIS management that BMIS reported to the SEC. The SAC alleges that PWC knew of this variance because (a) “PWC Int’l member firms with BMIS feeder fund clients shared information with other PWC Int’l member firms” and (b) PWC was “required by its Client Acceptance [a]nd Continuance Policies, its general audit methodology, its audit plan for [Greenwich Sentry], and/or the Practice Aid to obtain and review regulatory filings in general” and BMIS’s filings with the SEC “in particular.” (Compl. ¶¶ 200, 204.) These are no more than allegations that PWC had access to information that would have revealed a variance in BMIS’s reported assets or that PWC would have discovered such a variance if it had done what it had promised. Such allegations are insufficient to establish that PWC actually knew of the variance.
See In re Tremont,
Stephenson argues that the SAC does not allege “mere ‘access’ ” but instead alleges that PWC “had this information in its own databases by virtue of the design of procedures which it and its sister firms employed to make sure that each PWC member firm knew such information” and PWC “is presumed and alleged to have actual knowledge of information within its own control and custody ... at this stage of the proceedings.” (Pl.’s Opp. at 12-13.) But Stephenson cites no case for the proposition that one member of a global firm can be charged with actual knowledge of all information in the global firm’s database and the Court is aware of none. Stephenson has “made no allegations whatsoever as to how [PWCs] unfettered access would have led them across particular documents in which the red flags would have been apparent.”
In re Refco,
The third red flag alleged is that BMIS’ unmatched returns should have placed PWC on notice that those returns
*577
were illusory.
2
In its prior order, the Court recognized that “PWC had to be aware that BMIS consistently reported excellent results, as the statements it audited reflected that” but the Court was “unwilling to hold that success in securities trading is a red flag.”
Stephenson I,
Of course, the SAC alleges not only that BMIS earned inexplicable returns, but that it purported to do so at an inexplicably low risk and by exiting the market on quarter-ending days when the SSC Strategy indicated that remaining in the market would have been profitable. And several courts in this Circuit have found known suspicious quarter-end transactions to be red flags of fraud.
See, e.g., In re Refco,
The fourth red flag alleged is that BMIS could not have executed its purported strategy to enter and exit its positions
en masse
because, given the massive size of its holdings, these transactions would have caused market volatility that never in fact occurred. The SAC alleges that PWC knew of this red flag because PWC International “employed market specialists” to track market activity; “PWC publicly represented” that it analyzed investments in market context; and “PWC represented to FGG, as part of its Audit Plan” that it would test the valuation of BMIS derivatives. (Compl. ¶ 217.) These allegations do not establish a strong inference that PWC knew that market data did not reflect the transactions BMIS reported to make, for, again, it is not enough to allege that PWC “ ‘would’ have learned the truth as to those aspects of the [fraudulent]
*578
funds if [it] had performed the ‘due diligence’ it promised.”
South Cherry Street,
For much the same reason, the SAC fails to adequately plead scienter with respect to the fifth, sixth, and seventh red flags alleged. These red flags relate to the market for the options that BMIS claimed to use as part of the SSC Strategy. The fifth red flag alleged is that the OTC market could not support the volume of options BMIS would have had to place in order to execute the SSC Strategy. And the sixth red flag alleged is that counterparties to these options could not obtain options in the public market in quantities sufficient to hedge their own positions. The SAC alleges that PWC knew of these red flags because it “ha[d] access to and follows markets via PWC Int’l’s Global Capital Markets practice”; PWC “held itself out as[ ] an expert in auditing hedge fund management”; “PWC undertook and was required to understand the market environment”; “PWC undertook and was required to understand the rationale for significant and unusual business transactions”; “PWC, by virtue of being a globally recognized leader in auditing alternative investment funds ... had access to unprecedented market intelligence”; “the Audit Plan for [Greenwich Sentry] required them to test BMIS’s investment strategy”; and GAAS required PWC to know about counterparty trading. (Compl. ¶¶ 249, 259.) These, too, are no more than allegations that a GAAS violation
ipso facto
establishes scienter or that PWC “would’ have learned the truth as to those aspects of the [fraudulent] funds if [it] had performed the ‘due diligence’ it promised.”
South Cherry Street,
Where the SAC has failed to plead that PWC actually knew about these red flags, the SAC alleges to no avail that, “even if any one individual stage of risk did not, standing alone, signal a red flag to PWC, the
combination
of risks and anomalies presented by all three supposed stages of the strategy suffice to create a red flag that BMIS’s purported strategy was a house of cards, and that it must be operating a fraud.” (Compl. ¶ 268 (emphasis in original).) Several slightly red flags might make it easier to make out a warning sign,
see, e.g., In re the Leslie Fay Cos. Inc., Sec. Litig.,
The insufficiency of the SAC’s red flag allegations becomes clear in comparing the
*579
circumstances in which courts in this Circuit have sustained claims that an auditor knew of a red flag. Those courts have found a strong inference of recklessness where the audited company’s own filings explicitly disclosed problems with internal controls,
see Varghese,
The SAC does not allege that PWC was actively involved in structuring BMIS’s or Greenwich Sentry’s transactions and does not point to any document that would have put PWC on notice of a fraud at BMIS.
3
Rather, the SAC alleges that, had PWC conducted a more thorough audit of both Greenwich Sentry and BMIS, PWC would have connected the dots and determined that BMIS — which was not its client — was a fraud. That may be a charge that PWC conducted a shoddy audit but it is not a charge that PWC shared an “intent to aid in the fraud”,
Rothman,
Nor is this a case where, “because the red flags would be clearly evident to any auditor performing its duties, one could reasonably conclude that [the auditor] must have noticed the red flags, but deliberately chose to disregard them.”
In re Philip Serv. Corp.,
In the end, the nub of Stephenson’s complaint is that PWC failed to uncover and report fraud at BMIS — a firm it was never hired to audit. The SAC alleges that, under GAAS, “PWC was required to evaluate and assess the internal controls at BMIS and to test those internal controls over the occurrence and completeness of transactions performed or reported to be performed by BMIS pertaining to [Greenwich Sentry], and over the existence of assets, liabilities and equity interests held by BMIS pertaining to [Greenwich Sentry.]” (Compl. ¶ 129.) But the allegation that PWC failed to do any of those things does not create a “strong inference” that PWC effectively had “an actual intent to aid in the fraud
by the audited company.” Rothman,
Stephenson cites no case to the contrary other than
In re Complete Mgmt. Inc. Securities Litigation,
CONCLUSION
For the foregoing reasons defendant’s motion [62] to dismiss is GRANTED and plaintiffs complaint is dismissed.
SO ORDERED.
Notes
. The Court’s analysis here and below of cases alleging fraud under the federal securities laws in analyzing a common law fraud claim merits some discussion. Prior to the Supreme Court’s decision in
Tellabs, Inc. v. Makor Issues & Rights, Ltd.,
In 1995, Congress enacted the Private Securities Litigation Reform Act (“PSLRA”). A provision of the PSLRA required plaintiffs alleging fraud under the federal securities laws to "state with particularity facts giving rise to a strong inference that the defendant acted with the required state of mind.” 15 U.S.C. § 78u-4(b)(2). In enacting that provision, Congress sought to impose “a uniform standard modeled upon the pleading standard of the Second Circuit.” S.Rep. No. 104-98, at 15 (1995), reprinted in 1995 U.S.C.C.A.N. 679, 694. Thus, even after the PSLRA, cases arising under the federal securities laws were relevant to adjudicating common law fraud claims. Indeed, "the PSLRA effectively raised the nationwide pleading standard to that previously existing in this circuit and no higher....”
Novak v. Kasaks,
In
Tellabs,
however, the Supreme Court interpreted "strong inference” in a manner that went beyond Second Circuit precedent interpreting Rule 9(b). The Supreme Court held that a strong inference "must be cogent and at least as compelling as any opposing inference of nonfraudulent intent” and that testing allegations against that standard requires a court to "engage in a comparative evaluation; it must consider, not only inferences urged by the plaintiff ... but also competing inferences rationally drawn from the facts alleged.”
Tellabs,
Nevertheless, several courts in this Circuit considering fraud claims after
Tellabs
appear to have treated the
Tellabs
framework as relevant and
post-Tellabs
cases as persuasive authority in considering common law fraud claims.
See, e.g., Bay Harbour Mgmt. LLC v.
*572
Carothers, 282
Fed.Appx. 71, 77 (2d Cir.2008) (after analyzing plaintiffs federal securities claims under the
Tellabs
framework, holding that "[flor the same reasons set forth above, [plaintiffs] have failed to plead facts, with the particularity required by Federal Rule of Civil Procedure 9(b), that could give rise to a claim for common law fraud”);
Allianz Risk Transfer v. Paramount Pictures Corp.,
No. 08-CV-10420,
And as with the previous motion to dismiss, the parties appear to have no problem with that approach: they both have nearly exclusively cited federal securities cases and have argued that the "most compelling inference” is either that PWC effectively assisted in the fraud or was a fellow victim of it. Accordingly, the Court will treat post-Tellabs cases as relevant to considering Stephenson’s common law fraud claim.
. The complaint labels this "Red Flag # 4” but the Court considers it here for the sake of clarity.
.
In re WorldCom, Inc. Securities Litigation,
No. 02-CV-3288,
