Pleading Fraud With Particularity Under CPLR § 3016(b): The Scienter Mistakes That Sink NYC Business Fraud Claims
You run a Flatiron-based software reseller. Eighteen months ago, you signed an exclusive distribution agreement with a Delaware hardware vendor that promised your territory covered everything in Manhattan south of 59th Street. Last week, a Tribeca customer forwarded you a direct quote from that same vendor undercutting your price by 22%. You want to sue for breach of contract, and your gut tells you this was fraud from day one. The question is whether a New York judge will let you say so when you file.
Fraud is a powerful add-on to a commercial case. It can open the door to punitive damages, it survives in situations where a plain contract claim does not, and it changes the tone of settlement talks. But New York makes you earn it. Pleading fraud with particularity under CPLR § 3016(b) is where most of these claims live or die, and the hardest piece to plead is scienter — the defendant's knowledge that what they said was false. Get that wrong and the fraud count is dismissed before you ever see a document in discovery.
Key takeaways
CPLR § 3016(b) requires specific facts supporting fraud, not labels or conclusions.
Scienter can be inferred from circumstances, but "defendant knew" alone almost always fails.
A fraud claim that just restates your contract claim will be dismissed as duplicative.
Facts within the defendant's exclusive knowledge may be pleaded on information and belief.
Puffery, opinion, and disappointment with results won't support an inference of knowledge of falsity.
Why does repackaging your breach of contract as fraud get the case dismissed?
Because New York courts routinely dismiss fraud claims that are nothing more than a breach-of-contract claim in dress-up. If the only "lie" you can describe is the defendant's promise to perform the contract, and the only damages you can show are the benefit of the bargain you never got, the court will treat the fraud count as duplicative and throw it out at the motion-to-dismiss stage. That ruling costs you punitive damages exposure and often the leverage you were counting on.
The First Department made this explicit in Essential Home Remodeling, Inc. v. Rossin, 2025 NY Slip Op 01314 (1st Dep't 2025), where the court dismissed a fraud counterclaim because the defendant "pleads no specific facts from which it may be reasonably inferred that plaintiff did not intend to abide by the specified timeline." The counterclaim was also duplicative of the contract claim. That's the one-two punch: no particularized scienter and no distinct injury.
To survive, your fraud claim needs its own factual spine — a misrepresentation of present fact (not a promise about the future), specific knowledge of falsity, and damages that are separate from what the contract would have given you. In our practice, we're seeing more disputes over contracts drafted with AI tools. AI can produce a polished, generic contract, but if you don't know what you need it to say, it may leave out the terms that protect you, and that gap has become a real source of litigation. Owners who find themselves holding a thin AI-drafted agreement often reach for fraud as a lifeline when the real problem is that the document never had the protections they needed. The lifeline rarely holds unless the facts of the inducement are genuinely fraudulent and separate from the contract itself. If you want the deeper mechanics of how to structure the pleading, our companion post, How to Plead Fraud in New York Business Disputes, walks through the elements piece by piece.
Why do conclusory allegations that the defendant "knew" the statement was false sink your pleading?
Because scienter is not a label — it's a factual showing, and the Court of Appeals demands facts that let a judge draw a reasonable inference of knowledge. Writing "defendant knew the representation was false" is a conclusion, not a fact. On a CPLR 3211 motion, the court will strip conclusions out and ask whether what remains supports an inference of fraud. If it doesn't, the claim is gone.
The governing rule comes from Eurycleia Partners, LP v. Seward & Kissel, LLP, 12 N.Y.3d 553 (2009), which applied the Court of Appeals' earlier decision inPludeman v. Northern Leasing Systems. The Court recognized that "the strength of the requisite inference of fraud will vary based on the facts and context of each case," but still dismissed fraud and aiding-and-abetting claims against the defendant law firm because the knowledge allegations were conclusory. That's the balance: scienter can be inferred, but you have to give the court something concrete to infer it from.
Commercial plaintiffs often learn this the hard way after a bad investment. In MP Cool Investments Ltd. v. Forkosh, 142 A.D.3d 286 (1st Dep't 2016), a sophisticated investor sued over a company that underperformed its projections. The First Department shut the fraud claim down, holding that "[a]lthough the company may not have performed as plaintiff expected, this does not support a reasonable inference that defendants knew that DuCool would fall short of its business projections." Disappointment is not scienter. What you need are facts (internal communications you've seen, documents the defendant possessed, timing of a sale, an admission from a former employee, or regulatory filings) that make it plausible the defendant knew the truth and said otherwise.
This is also why fraud claims pair well with other equitable theories when the facts allow. If your real complaint is that someone is holding money or property that doesn't belong to them, you may be better off framing the case as a conversion claim or a constructive trust than forcing a weak scienter theory.
Why does suing over puffery and sales talk doom a fraud claim?
Because New York draws a hard line between actionable misrepresentations of fact and non-actionable opinion or sales promotion. When your fraud count is built around statements like "this is a great investment" or "we have the best team in the industry," courts treat the speech as puffery and dismiss. The reason ties back to scienter: nobody can "know" that a prediction or an opinion is false, so there's nothing concrete to infer knowledge from.
The Second Department reinforced this just last year in Lapin v. Verner, 2025 NY Slip Op 03184 (2d Dep't 2025), affirming dismissal of a fraud claim over a failed real-estate investment. The court flagged the statements as puffery and found that "no facts have been alleged which might give rise to a reasonable inference that Loeb knew the misrepresentations were false or misleading at the time they were made." Two defects, one dismissal.
The fix is to anchor the fraud claim to specific statements of existing fact (the number of signed customers, audited revenue for a given year, the ownership of a specific asset, the existence of a permit, a representation about an inspection) and then plead the facts that show the defendant knew those statements weren't true. Vague claims about reputation, future performance, or quality rarely get past the pleading stage. If the deception is about broader marketing conduct toward consumers rather than a one-off business lie, a GBL § 349 deceptive practices claim can sometimes do work a common-law fraud claim cannot.
Why does rushing to file before you've mapped the circumstantial evidence of scienter backfire?
Because the First and Second Departments decide these motions on the four corners of your complaint, and if you file before you've gathered the circumstantial facts that let a judge infer knowledge, you lose. You don't get to shore up the pleading later with discovery you haven't taken yet. Dismissal is often with prejudice to the fraud count, even if the contract claim survives.
When your gut tells you a deal is going south, act on it. Bringing in a lawyer early often sends the other side a clear message that the delays have to stop, and it also gives you time to pull together the evidence that will carry a fraud pleading. Internal emails you still have access to, communications with third parties, timeline charts of what the defendant said against what the defendant was doing, industry standards the defendant violated — all of that becomes the circumstantial record that satisfies CPLR 3016(b).
The First Department's decision in Bullen v. CohnReznick, LLP, 194 A.D.3d 637 (1st Dep't 2021), is a useful blueprint. The court held that "[p]laintiffs sufficiently alleged a cause of action for fraud with particularity (CPLR 3016[b])" because the complaint laid out red flags the accountant should have seen, accounting-standard violations, and the timing of information the accountant received. None of those facts proved scienter directly, but together they let the court draw the inference. That is the kind of complaint you want to file — and you cannot write it in two days.
One tactical point worth naming: judges in New York County and Kings County Commercial Division parts tend to read these pleadings closely at the Rule 3211 stage because they know early dismissal of a fraud count narrows discovery and streamlines settlement. The time you spend before filing is often the difference between the fraud claim surviving and being gone by the first case conference. Some plaintiffs pair the fraud claim with a request for a preliminary injunction or TRO precisely so the court sees the circumstantial record early in a context that forces engagement with the merits.
Why does ignoring the "exclusive knowledge" exception cost otherwise valid fraud claims?
Because New York courts recognize that when the facts you need to plead scienter are locked inside the defendant's files, the particularity standard relaxes. If you don't invoke that principle in your complaint and explain why the facts are peculiarly within the defendant's knowledge, you may be held to a specificity standard you simply cannot meet before discovery. That's a self-inflicted dismissal.
The First Department reaffirmed this exception earlier this year in Board of Mgrs. of 45 E. 22nd St. Condominium v. 45 E. 22nd St. Prop. LLC, 2026 NY Slip Op 01123 (1st Dep't 2026), letting a fraudulent inducement claim against a developer's principal proceed. The court wrote that "notwithstanding the requirement to plead fraud claims with particularity (CPLR 3016[b]), the claim against Eichner was not impaired by allegations that were made on information and belief where the facts underlying the allegations were within Eichner's exclusive knowledge." That's the hook you want in your own complaint when the defendant is the one holding the documents, the texts, the internal reports, and the pricing data.
Practically, this means your complaint should (a) identify the categories of information that are in the defendant's exclusive possession, (b) explain why you cannot access them pre-discovery, and (c) use "upon information and belief" expressly for those scienter allegations while pleading the rest on direct knowledge. Courts give you more room when you show your work. If the fraud is intertwined with an attempt to drain assets out of a corporate entity you're suing, you'll also want to consider whether the facts support piercing the corporate veil against individual principals so a judgment on the fraud claim can be collected.
Frequently asked questions
Can I plead fraud and breach of contract in the same complaint?
Yes, but the fraud claim has to be more than a restatement of the contract claim. You need a misrepresentation of present fact that is collateral to or extraneous from the contract, specific facts supporting scienter, and damages that are not simply the benefit of your bargain. Otherwise the court will dismiss the fraud count as duplicative, as happened in Essential Home Remodeling, Inc. v. Rossin.
Does CPLR § 3016(b) apply to fraud counterclaims?
Yes. The particularity requirement applies to any claim or defense that sounds in fraud, including counterclaims and third-party claims. Defendants who hastily file a fraud counterclaim to pressure the plaintiff often see it dismissed at the Rule 3211 stage for the same conclusory-scienter reasons that sink plaintiffs' claims.
What happens if my fraud claim is dismissed but my breach of contract claim survives?
You still have your case, but you lose punitive damages exposure, the ability to pursue individual officers or directors on a fraud theory in many situations, and a meaningful piece of settlement leverage. The contract claim will proceed to discovery under a different damages framework, often capped at the benefit of the bargain and the implied covenant of good faith.
Is pleading fraud in federal court easier or harder than in New York state court?
Federal court requires the same particularity under Federal Rule of Civil Procedure 9(b), and in securities fraud the Private Securities Litigation Reform Act adds an even stricter "strong inference" standard for scienter. New York state court under CPLR § 3016(b) is often described as somewhat more flexible on circumstantial scienter after Pludeman, but neither forum tolerates conclusory knowledge allegations.
The bottom line
Pleading fraud with particularity under CPLR § 3016(b) is less about reciting the elements and more about assembling a factual record that lets a judge infer the defendant knew the truth and said the opposite. The costly mistakes — duplicating a contract claim, pleading scienter in conclusions, suing over puffery, filing before you've built the record, and ignoring the exclusive-knowledge exception — are all avoidable if you slow down at the drafting stage. A tighter, better-sourced complaint survives dismissal and changes the shape of the entire case.
If you or your business is weighing a fraud claim alongside a breach of contract case anywhere in the five boroughs, Nassau County, or Suffolk County, the team at Yassi Law PC is ready to help. Call us today at 646-992-2138 for a consultation.
Written by Reza Yassi
This article is for informational purposes only and does not constitute legal advice. Although I am an attorney, I am not your attorney, and reading this article does not create an attorney-client relationship. Laws vary by jurisdiction and may have changed since the publication of this article. For advice specific to your situation, consult a qualified attorney.
.png)