top of page

Limitation of Liability Cap in New York: Costly Mistakes When Arguing Gross Negligence and Willful Misconduct

Writer: Reza Yassi
Reza Yassi
5 days ago
11 min read
Limitation of Liability Cap in New York: Costly Mistakes When Arguing Gross Negligence and Willful Misconduct

Your Long Island City distribution company runs its entire order system on a cloud platform you license for $8,000 a month. For two weeks in March, the platform keeps dropping orders, and the vendor's support desk closes your tickets without fixing anything. By the time the problem is traced to a known bug the vendor never disclosed, you've lost a major retail account and roughly $2.4 million in revenue. The vendor's answer is one sentence pointing to Section 9: liability capped at fees paid in the prior twelve months, consequential damages excluded. Whether that limitation of liability cap in New York holds depends far less on the size of your loss than on what the vendor knew and why it acted.


Key takeaways


  • A contract cap won't protect a vendor whose conduct shows reckless indifference to your rights or an intent to harm you.

  • A breach driven by the vendor's own profit motive usually isn't willful misconduct under New York law.

  • Proof that the vendor knew about a problem, ignored it, and stayed silent is what moves a claim past the cap.

  • Send a preservation demand early, because the evidence of what the vendor knew sits in its own systems.

  • Read the whole contract, including waiver-of-subrogation and exclusive-remedy terms, before you build your case.


Why is it a mistake to assume a limitation of liability cap can never be broken?


It's a mistake because New York public policy won't let a contract shield a party from its own gross negligence or intentional wrongdoing, no matter how carefully the clause is drafted. Caps and consequential-damages exclusions are generally enforced between businesses, and courts respect the bargains sophisticated parties strike. But that bargain has a floor.


The leading case is Sommer v. Federal Signal Corp., 79 N.Y.2d 540 (1992). A fire alarm company had contract clauses limiting its liability to $55.50. The Court of Appeals refused to enforce those clauses against gross negligence and held that a fact question about whether the company had been grossly negligent kept it from winning summary judgment. In the Court's words: “Whatever may be the case in other contexts, public policy precludes enforcement of contract clauses exonerating a party from its reckless indifference to the rights of others, whether or not termed ‘gross negligence.’”


Notice what that standard requires. Gross negligence in this setting isn't just a bad mistake or an expensive one. It's conduct that shows reckless indifference to your rights or that smacks of intentional wrongdoing. That's a high bar, and most of the costly mistakes discussed below come from misjudging where it sits.


There are actually two separate routes past a cap. The first is contractual. Many vendor and services agreements expressly carve gross negligence, willful misconduct, fraud, confidentiality breaches, or indemnification obligations out of the cap, so read that clause line by line. The second is the public-policy floor from Sommer, which applies even if your contract has no carve-out at all. You'll want to know which route you're on, because the contract's own wording can be broader or narrower than the public-policy rule.


If your deal involves the sale of goods (servers, security hardware, manufacturing equipment), the Uniform Commercial Code adds its own rules. Under UCC § 2-719, consequential damages may be limited or excluded unless the limitation is unconscionable, and the statute says a limitation of damages where the loss is commercial is not prima facie unconscionable. The same section provides that when an exclusive or limited remedy fails of its essential purpose, you may pursue the remedies the UCC otherwise allows. An unconscionability attack under UCC § 2-302 gives you a chance to present evidence about the clause's commercial setting, purpose and effect, but between two businesses it's an uphill climb. For a fuller look at what an exclusion can take off the table, see this guide to consequential damages in New York breach of contract cases.


Why does calling a deliberate breach “willful misconduct” usually fail?


It usually fails because New York's highest court has held that walking away from a contract to serve your own financial interest is not the kind of willfulness that unlocks a cap. This is the single most common miscalculation in these disputes. The vendor dumped you for a bigger client, or stopped performing because the deal stopped being profitable, and that feels willful. Legally, it usually isn't.


In Metropolitan Life Insurance v. Noble Lowndes International, Inc., 84 N.Y.2d 430 (1994), a software vendor deliberately abandoned its contract with MetLife to serve its own economic interests. The contract excluded consequential damages but excepted “willful acts.” A jury awarded MetLife millions. The Appellate Division cut that award back to a refund of the $204,000 MetLife had paid, and the Court of Appeals affirmed, explaining that “the parties intended to narrowly exclude from protection truly culpable, harmful conduct, not merely intentional nonperformance of the Agreement motivated by financial self-interest.”


The First Department applied the same logic to a modern software deal in MUFG Union Bank, N.A. v. Axos Bank, 2021 NY Slip Op 04414 (1st Dep't 2021). The plaintiff sought roughly $100 million in lost profits after its software partner sold its bankruptcy software business to a competitor. The contract had liability caps of $5 million and $10 million. The court enforced the caps, finding “no evidence that Epiq breached the JSA intending to willfully inflict harm on Union; rather, the proof is that Epiq sold its bankruptcy software business to Axos in order to advance its own economic self-interest.”


Read together, these cases tell you how to avoid the mistake. Don't build your case on the theory that the vendor broke the deal on purpose. Almost every deliberate breach is on purpose. Build it on evidence that the vendor intended to harm you, or used its position to take something it had no right to take. If the real dispute is about future profits you lost, the cap fight will decide whether those numbers ever reach a jury, so it helps to understand how New York courts treat lost profits damages before you spend money proving them.


Why does treating an expensive professional mistake as gross negligence backfire?


It backfires because courts measure gross negligence by the vendor's state of mind and conduct, not by the size of your loss, and an honest but careless error rarely qualifies. A $3 million loss caused by ordinary negligence is still ordinary negligence.


Brevet Direct Lending Short Duration Fund, L.P. v. Aprio LLP, 2024 NY Slip Op 03128 (1st Dep't 2024), shows the line clearly. An accounting firm relied on confirmation emails that turned out not to have come from their purported senders. The losses were serious. The First Department still affirmed summary judgment for the firm, holding that its “failure to check if the addresses from which emails, which did not bounce back and which appeared to come from legitimate addresses, were sent were the actual addresses of their purported senders, does not meet this standard.” The cap stood.


Look at the procedural posture, too. The court decided gross negligence on summary judgment. You can't count on the issue automatically going to a jury just because you've used the right words in your complaint.


Now compare Abacus Federal Savings Bank v. ADT Security Services, Inc., 18 N.Y.3d 675 (2012). A bank sued its alarm vendors after a burglary, and the vendors pointed to their contractual limitations. The Court of Appeals reinstated the bank's breach of contract claim against one vendor because the bank alleged the vendors knew about the problem and did nothing: “Abacus alleges that both defendants had knowledge—for weeks, if not months—that the equipment had been malfunctioning. Moreover, Abacus asserts that defendants not only failed to investigate the source of their equipment malfunction, but they failed to put anyone at the branch on notice of the potential security breach.”


The difference between Brevet and Abacus is the pattern that matters most in these cases. A single lapse looks like negligence. The same lapse repeated after warnings, open tickets, or internal alarms starts to look like indifference. That's why the dates in a vendor's own ticketing system and incident logs often matter more than any expert report on what technically went wrong. The question isn't whether the vendor's system failed. It's how long the vendor knew it was failing and what it chose to do about it.


Why does waiting to build your evidence and file suit cost you leverage?


Waiting costs you because the proof that gets past a cap lives in the other side's files, and every month of delay gives the vendor time to clean up the record, let logs expire, or move money. A common mistake is waiting too long. Business owners get strung along by promises that a fix is coming, that a credit is on the way, or that the account team is escalating the issue. Those promises often don't pan out, and in the meantime routine retention policies keep deleting the records you'll need, and a struggling vendor may become harder to collect from.


The statute of limitations won't save you from this problem. Under CPLR § 213, an action on a contractual obligation generally must be commenced within six years. If your contract is for the sale of goods, the UCC generally sets a shorter four-year limit, and the contract itself can shorten that to as little as one year. Either way, that's usually enough time to sue. It's not enough time to preserve chat messages, support tickets and server logs that a vendor's routine retention policy may overwrite in 90 days. Once you know a loss is coming, a written preservation demand to the vendor should go out quickly. The evidence that tends to matter most includes:


  • Support tickets and their open, closed and reopened dates

  • Internal incident reports, root-cause analyses and post-mortems

  • Emails or chat messages showing the vendor knew of the defect

  • Customer notices the vendor sent, delayed, or never sent


Sometimes the evidence shows more than indifference. In Banc of America Securities LLC v. Solow Building Co. II, L.L.C., 47 A.D.3d 239 (1st Dep't 2007), a landlord demanded a $6 million fee it had no lease basis to charge and withheld approvals the lease required it to give. A divided First Department held that a trier of fact could find an intent to inflict monetary harm that would make the lease's remedy limitation unenforceable, and it denied the landlord summary judgment over a two-judge dissent. The majority wrote that “the Court of Appeals did not intend economic self-interest to be applied as an expansive principle to excuse all manner of misconduct.” Using contractual leverage to extract money the other side has no right to demand isn't mere self-interested nonperformance.


How you plead matters as well. Under CPLR § 3016(b), where a cause of action or defense is based on misrepresentation, fraud, mistake, wilful default, breach of trust or undue influence, the circumstances constituting the wrong must be stated in detail. Even when your theory is gross negligence rather than fraud, a complaint that lays out dates, names and documents is far harder to dismiss than one that recites labels. The same discipline applies when you add a fraud claim, as explained in this guide to pleading fraud with particularity in New York.


Why does ignoring the rest of the contract sink claims that clear the cap?


It sinks them because a cap is rarely the only clause standing between you and recovery, and a separate provision can bar the claim even after you show gross negligence. Abacus is the cautionary example. The bank's contract claim survived against one alarm vendor, but its claim against the other vendor was barred by a waiver-of-subrogation clause, and its tort claim was dismissed. Proving bad conduct wasn't enough to overcome a different provision of the deal.


So before you invest in the gross negligence fight, map every clause that limits what you can recover. Look for a separate consequential-damages exclusion, an exclusive-remedy clause (such as repair, replace or refund), insurance and waiver-of-subrogation provisions, shortened notice or claim deadlines, and any requirement that disputes go to arbitration. Each one can change the analysis independently.


Check the governing law, too. Under General Obligations Law § 5-1401, parties to a transaction covering in the aggregate at least $250,000 may agree that New York law governs, whether or not the contract bears a reasonable relation to New York, though the section doesn't apply to contracts for labor or personal services. Many national software and services agreements pick another state's law instead, and that state may treat caps and carve-outs differently. This overview of choice of law clauses in New York commercial contracts explains how those provisions are enforced.


The drafting process itself can create these disputes. A generic or template contract, whether pulled from a form library or generated with an AI tool, may look polished but leave out the terms that protect you. A template limitation clause dropped into a services agreement without any carve-outs is exactly the kind of gap that leaves a customer relying on the narrow public-policy exception alone.


Finally, think about the full value of a claim that does clear the cap. Under CPLR § 5001, interest is recovered on a sum awarded for breach of contract and is computed from the earliest ascertainable date the cause of action existed. On a multi-year dispute, that interest can add up, as this post on prejudgment interest in New York breach of contract cases explains. You can read the full text of the Court of Appeals and Appellate Division decisions discussed here through the New York State Law Reporting Bureau's Official Reports.


What else do NYC business owners ask about limitation of liability clauses?


The questions below come up most often when a vendor or contractor invokes a cap after a major loss.


Frequently Asked Questions


Does a court strike the whole limitation of liability clause if the vendor was grossly negligent?

Under Sommer, public policy bars enforcing the clause against grossly negligent or intentionally wrongful conduct. The clause can still apply to ordinary breaches and ordinary negligence under the same contract. That's why your proof has to tie the loss to the culpable conduct, not just to the vendor's general performance.

Is gross negligence decided by a judge or a jury?

It depends on the record. In Sommer, a fact question about gross negligence sent the issue to trial, while in Brevet the First Department decided on summary judgment that the conduct didn't meet the standard. The more evidence you have of knowledge and inaction, the better your chance of reaching a jury.

If my contract already excludes willful misconduct from the cap, am I covered?

Not necessarily. In Metropolitan Life, the contract excepted willful acts, and the Court of Appeals still read that exception narrowly to exclude self-interested nonperformance. You'll generally need evidence of truly culpable, harmful conduct, not just a deliberate decision to stop performing.

How long do I have to sue a vendor for breach of contract in New York?

Under CPLR § 213, an action on a contractual obligation generally must be brought within six years. Contracts for the sale of goods generally carry a four-year limit under the UCC, and your contract may contain even shorter notice or claim deadlines. The legal deadline is usually less pressing than the practical one. Logs, tickets and messages that prove what the vendor knew can disappear long before the limitations period runs.


A limitation of liability cap in New York is strong but not absolute. It gives way when the evidence shows reckless indifference to your rights or an intent to harm you, and it holds when the vendor simply made a mistake or chased its own profit. Your outcome turns on proving what the vendor knew, when it knew it, and what it chose to do next.


If you or your business has suffered a major loss and the vendor or contractor responsible is pointing to a limitation of liability clause, Reza Yassi at Yassi Law PC is ready to help. Call us today at 646-992-2138 for a consultation.



Written by Reza Yassi | LinkedIn


Prior results do not guarantee a similar outcome.


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.


slider 4.jpg
Reza Yassi(author).png

Principal Attorney, Yassi Law P.C.
Reza Yassi is the principal attorney at Yassi Law P.C., representing clients in commercial litigation and personal injury matters. He is known for his aggressive yet tactical approach, combining strategic planning with clear client communication while serving individuals and businesses across New York and New Jersey.

bottom of page