Liquidated Damages vs. Penalty Clauses in MN

What is the difference between liquidated damages and a penalty in Minnesota?

A liquidated damages clause is a contract term that sets damages in advance for a defined breach. A penalty clause does the same thing in form but does it in a way Minnesota courts will not enforce.

The difference is substantive, not labeling. Under Gorco Construction Co. v. Stein, 256 Minn. 476, 99 N.W.2d 69 (1959), the controlling factor is whether the amount agreed upon is reasonable or unreasonable in light of the contract as a whole, the nature of the damages contemplated, and the surrounding circumstances.

A clause that sets a number bearing a real relation to anticipated harm is liquidated damages. A clause that sets a number designed to punish nonperformance, or to scare the other side into compliance, is a penalty.

The practical consequence is that the same number can be liquidated damages in one contract and a penalty in another. A 15 percent cancellation fee tied to a contract where the seller had committed labor and materials may pass. The same 15 percent fee, tied to a contract where the seller had incurred no expense and could easily prove actual loss, will fail. The clause does not exist in isolation. It has to fit the contract.

What are unliquidated damages?

Unliquidated damages are damages the contract does not fix in advance. If your contract has no liquidated damages clause, or the clause is struck as a penalty, your recovery is unliquidated: you prove the amount of your loss with evidence, under the ordinary rules for contract damages.

The Minnesota Supreme Court defined the other side of that line in Schutt Realty Co. v. Mullowney, 215 Minn. 340, 10 N.W.2d 273 (1943), quoting a treatise: “The term ’liquidated damages’ signifies the damages the amount of which the parties to a contract stipulate and agree, when the contract is entered into, shall be paid in case of breach.” The same passage says such a stipulation “is enforceable, at least in those cases where the damages which result from a breach of the contract are not fixed by law or are in their nature uncertain and where the amount stipulated does not manifestly exceed the injury which will be suffered.”

The practical choice is between certainty and proof. A liquidated amount spares you the work of proving loss. Unliquidated damages leave you free to recover whatever you can prove, but you carry the cost and risk of proving it.

When are liquidated damages enforceable under the Minnesota two-part test?

Minnesota courts apply a two-part test that has stayed remarkably stable since 1959. The court asks whether both conditions are met: (a) the amount fixed is a reasonable forecast of just compensation for the harm caused by the breach, and (b) the harm caused by the breach is one that is incapable or very difficult of accurate estimation. Both prongs must be satisfied. A clause that sets a reasonable number for damages that are easy to calculate fails the second prong. A clause that sets an unreasonable number for damages that are genuinely hard to estimate fails the first.

The test is not mechanical. The formation-time forecast matters heavily, but Minnesota courts may also consider actual damages and post-breach disproportionality when evaluating whether the clause operates as compensation or a penalty. If, at signing, the parties faced a real estimation problem (lost goodwill, lost market opportunity, downstream costs that could not be modeled), the second prong is satisfied. If the harm was straightforward to measure (unpaid invoices, finite project costs, lost rent on an existing lease), the second prong is much harder to satisfy. For more on how courts measure provable harm, see calculating damages: 6 tips for breach of contract cases.

How did Gorco become the controlling case?

Most Minnesota liquidated damages disputes still cite Gorco as the case that fixed the modern two-part test.

The facts were ordinary. A homeowner cancelled a contract to build two garages. The contract included a 15 percent cancellation fee covering salesman’s commissions, advertising, and the commitment of labor and equipment.

The Minnesota Supreme Court refused to enforce the clause and reversed for a new trial. The court explained that the fee covered specific elements of damages that were clearly and readily susceptible of definite measurement and proof by ordinary rules. Because the damages were measurable, an amount greatly disproportionate to provable loss was a penalty.

Gorco also frames the presumption drafters lean on: liquidated damages are prima facie valid on the assumption that the parties in naming a liquidated sum intended fair compensation for an injury caused by breach, not a penalty for nonperformance.

That presumption is the door the clause walks through. The two-part test is the doorway it has to fit. The case still controls because Minnesota appellate courts apply its framework today.

How does the UCC change the test for sales of goods?

When the contract is for the sale of goods, the Uniform Commercial Code overlay at Minn. Stat. § 336.2-718 governs. The statute says: “Damages for breach by either party may be liquidated in the agreement but only at an amount which is reasonable in the light of the anticipated or actual harm caused by the breach, the difficulties of proof of loss, and the inconvenience or nonfeasibility of otherwise obtaining an adequate remedy. A term fixing unreasonably large liquidated damages is void as a penalty.”

The UCC framework is functionally similar to the common-law test, with two practical refinements. First, the statute permits courts to look at either anticipated or actual harm, which gives the non-breaching party a second window: even if the amount looked unreasonable at signing, it may be saved if actual losses turn out to match.

Second, the statute speaks only to clauses that are unreasonably large. A clause fixing unreasonably small damages is governed elsewhere in Article 2 and may be analyzed as a remedy limitation rather than a penalty.

For sale-of-goods contracts, draft the clause with both anticipated and actual harm in mind: a clause that bears a defensible relationship to either is harder to break.

Do liquidated damages work the same way in service contracts and master service agreements?

Yes, and for a pure services contract the common-law Gorco test is the test. Article 2 of the UCC reaches only goods: under Minn. Stat. § 336.2-102, “this article applies to transactions in goods and, in the case of a hybrid transaction, it applies to the extent provided in subsection (2).” Gorco itself was a services deal, a contract to build two garages, and Schutt Realty arose from a wrecking contractor’s failure to demolish a building “within a stipulated time.” A master service agreement (MSA) for consulting, software support, staffing, logistics, or managed IT is judged by the same two questions: was the amount a reasonable forecast, and was the harm hard to estimate when you signed?

If your MSA also delivers equipment or other goods, it may be a hybrid transaction. The statute applies Article 2 differently depending on whether “the sale-of-goods aspects” predominate, so a liquidated damages term tied to hardware delivery and one tied to service hours can be judged under different rules in the same contract.

Service-level agreements (SLAs) usually carry the clause in the form of service credits: a percentage of the monthly fee credited back when uptime, response time, or resolution time falls below a target. Calling the payment a “credit” does not settle the question. Gorco says that in deciding whether a provision is a penalty, “neither the intention of the parties nor their expression of intention is the governing factor.” A credit sized to the reduced value of the service you received looks like a price adjustment or a reasonable forecast. A credit that multiplies with each missed hour until it exceeds the fee itself looks like a penalty.

For a service credit to hold up, a few drafting choices matter:

• Measure each service level objectively, with the data source, the measurement period, and the exclusions (scheduled maintenance, customer-caused outages) stated in the agreement.
• Size the credit to the lost value of the service, and cap the total credits in a period, often at a percentage of that period’s fees.
• Say whether credits are your only remedy for a missed service level or whether you keep a termination right and a claim for actual damages after repeated failures.

What breaches commonly trigger liquidated damages in an MSA?

Four triggers show up in most service agreements, and each fits the two-part test differently.

• Missed deadlines and delayed deliverables. A late implementation or a missed milestone delays your own launch, and the cost of that delay is often hard to measure day by day. That supports a per-day or per-milestone amount, as discussed below for per diem clauses.
• Missed service levels. Downtime and slow response cost you productivity and customer goodwill that rarely appear in a ledger. A credit tied to the shortfall is the usual tool.
• Data-security and compliance breaches. A vendor’s security failure can bring notification costs, regulatory exposure, and lost customers that no one can price at signing. The difficulty of estimating that harm helps the second prong, but the amount must still be a reasonable forecast, not a number chosen to frighten the vendor. Many MSAs handle actual breach costs through indemnity instead, and an agreement that uses both should say how they interact.
• Quality failures. Substandard work measured against an objective standard (error rates, rework counts) can support a fixed amount per failure when the downstream cost is hard to prove.

When you negotiate these triggers, ground the amounts in data from past projects or industry experience, add cure periods for minor misses, and use tiered amounts so a small miss costs less than a severe one. A vendor that cannot survive the worst-case number will price the risk into the fee or walk away, and the clause should protect you without making the deal unworkable.

How does Gorco’s framework apply to recurring failure patterns?

Recurring liquidated damages disputes in Minnesota commercial leases illustrate where the Gorco framework cuts hardest against the drafter. A lease that already contains a rent acceleration clause, fixes liquidated damages on top of that recovery, and says nothing about the landlord’s duty to mitigate stacks remedies in a way courts read as punitive. The combination of readily measurable damages (acceleration produces a numerical recovery from the lease itself) and a missing mitigation accounting puts the clause on the wrong side of Gorco.

A practical way to read Gorco is in two tiers: when actual damages can be calculated with reasonable certainty, the stipulated amount must not be greatly disproportionate to those damages; when actual damages cannot be calculated with reasonable certainty, the more permissive standard applies and the amount must not be manifestly disproportionate to actual damages suffered. A drafting and litigation pairing follows: if the clause might fail, plead actual damages as an alternative remedy.

What drafting moves keep a clause on the liquidated-damages side of the line?

The drafting choices that survive scrutiny have a common shape.

First, tie the stipulated amount to a real estimation problem identified in the contract itself. A short recital that explains why the parties chose a stipulated amount (the difficulty of forecasting customer disruption, the impossibility of pricing reputational harm, the volatility of replacement-equipment costs) is not boilerplate. Courts read recitals when they are looking for evidence that the parties actually faced an estimation problem.

Second, calibrate the amount to anticipated harm, not aspirational deterrence. A number that looks like a guess at average cost survives more often than a round figure that looks designed to discourage breach.

Third, account for mitigation where the clause overlaps with rent acceleration, resale proceeds, replacement transactions, or other recoveries that could create double recovery. A short sentence reserving the non-breaching party’s mitigation duty, or crediting actual mitigation against the stipulated amount, removes the easiest target.

Fourth, avoid layering the clause on top of other remedies (acceleration, full-term rent, lost-profits recoveries) without saying expressly how they interact. Stacking remedies invites a court to read the package as a penalty even if any single piece would survive on its own.

Fifth, write the clause as the exclusive remedy for the defined breach, or write it as elective with clear language. Ambiguity is read against the drafter, and in liquidated damages disputes the drafter is almost always the party trying to enforce.

For a related drafting framework, see carve-outs to caps in liability provisions, where the same logic of fitting the clause to the contract applies.

How does exclusivity work for liquidated damages clauses?

Do not assume exclusivity. The contract should state whether the liquidated damages amount is exclusive, cumulative, or elective for the defined breach.

If the parties want the non-breaching side to have a choice between the stipulated amount and provable actual damages, the contract must say so. Silence creates an election-of-remedies fight that the drafter will usually lose. Drafters who want optionality should write it in.

The flip side is real too. A clause written as exclusive can be a problem for the non-breaching party if actual damages turn out to be much larger than the stipulated number. The clause caps the recovery on its own terms. Optionality solves the problem only if the contract is drafted that way at signing, not after the breach.

How does the duty to mitigate interact with a liquidated damages clause?

Mitigation is the doctrinal pressure point that defeats many otherwise plausible clauses. A liquidated damages clause that ignores mitigation, or that effectively ensures a recovery beyond the loss the non-breaching party actually suffered, is in trouble.

A landlord who collects accelerated rent and the same rent again from a replacement tenant has been made more than whole. A clause that allows that result is hard to defend as a reasonable forecast of just compensation.

The fix is express. The clause should either credit actual mitigation receipts against the stipulated amount, or set the stipulated amount low enough that the combined recovery still tracks the non-breaching party’s expected loss.

Drafters resist this because it complicates the clean efficiency the clause was supposed to provide. The trade-off is real. A simpler clause that risks unenforceability gives up more than a slightly more complex clause that survives. The right balance depends on the deal, the breach scenarios that matter, and what the non-breaching party can actually do to mitigate after a default.

Does insurance cover a liquidated damages payment?

Do not assume it does. Whether your liability policy pays a liquidated damages amount turns on the policy’s own wording: what the insuring agreement treats as covered damages, and whether an exclusion for liability you assumed by contract applies. Before you agree to a large liquidated damages number, read the insuring agreement and exclusions, and ask your broker in writing whether the payment would be covered. If it would not, price that exposure into the deal or negotiate a lower cap.

Can liquidated damages be adjusted after the contract is signed?

Yes, if both parties agree to the change. The reliable way is a written amendment that both sides sign, naming the clause it replaces and the new amount or formula. Until then, the original term binds you.

For a sale of goods, Minn. Stat. § 336.2-209 provides that “An agreement modifying a contract within this article needs no consideration to be binding,” and a signed contract that “excludes modification or rescission except by a signed writing or other signed record cannot be otherwise modified or rescinded.” That no-consideration rule is written for contracts within Article 2, so in a services contract the amendment should state what each side receives in exchange for the change. An amended amount still has to pass the same two-part test.

Are liquidated damages enforceable in oral agreements?

An oral contract can carry an agreed damages amount, but it faces two hurdles a written one does not. The first is the statute of frauds. Under Minn. Stat. § 513.01, no action may be maintained on “every agreement that by its terms is not to be performed within one year from the making thereof” unless it, “or some note or memorandum thereof, expressing the consideration, is in writing, and subscribed by the party charged therewith.” For goods, Minn. Stat. § 336.2-201 makes “a contract for the sale of goods for the price of $500 or more” unenforceable without “a record sufficient to indicate that a contract for sale has been made,” subject to the exceptions that section lists.

The second hurdle is proof. You would have to prove that the other side agreed to the specific amount or formula, and that the amount was a reasonable forecast when you agreed to it. Memories of a handshake rarely supply that, so put any damages term in writing, even a short email the other side confirms.

How do liquidated damages work in international service agreements?

In a cross-border agreement, the governing-law clause decides which penalty test applies. The Gorco test is Minnesota’s; another country’s courts may apply a different rule, and a clause that Minnesota would enforce can be treated differently elsewhere. For transactions governed by the UCC, Minn. Stat. § 336.1-301 provides that “when a transaction bears a reasonable relation to this state and also to another state or nation the parties may agree that the law either of this state or of such other state or nation shall govern their rights and duties.”

For an international MSA, I suggest naming the governing law, the forum for disputes (a court or arbitration), and the currency of any liquidated amount. Then ask where you would actually have to collect: a judgment or award is only as useful as your ability to enforce it in the country where the other party’s assets are, so confirm with local counsel how that country treats both the clause and a foreign judgment before you rely on the clause as your main protection.

When is a per diem delay clause enforceable?

Per diem delay clauses, common in construction and time-sensitive supply contracts, are an instructive subcategory. They tend to survive Minnesota scrutiny when the daily amount reflects a reasonable forecast of the additional cost the non-breaching party will incur for each day of delay, and when delay damages are genuinely difficult to prove with daily precision.

They tend to fail when the daily amount is round, large, and disconnected from any cost analysis, especially in disputes where the non-breaching party can produce books showing exact daily impact. The two-part test applies the same way it does anywhere else, but the breach scenario (rolling delay) plays well with the second prong because daily delay losses are notoriously hard to prove with precision.

The drafting move that matters most is the rationale for the daily figure. A delay clause that ties the per diem rate to a specific cost basis (carrying costs, idle-equipment costs, lost daily revenue from a comparable project) gives the court something to point to when sustaining the clause. A delay clause with a number that appeared from nowhere invites the penalty argument. For a related discussion, see delay penalty clauses in time-sensitive shipments.

What clauses look like liquidated damages but are something else?

Several common contract terms function like liquidated damages without always being analyzed under the Gorco framework. Termination fees, early termination charges, restocking fees, and minimum-purchase shortfall payments can be characterized as price terms, performance fees, or alternative consideration rather than damages, depending on how they are drafted.

The characterization matters because price terms are not subject to the penalty doctrine. A monthly subscription fee with a 12-month commitment, where the customer pays out the remaining months on early termination, may be enforced as the price of the service rather than struck down as a stipulated-damages provision.

Default interest rates, late fees, and prepayment penalties travel a different path. Default interest is constrained by usury concepts and by Minnesota’s general suspicion of clauses that produce escalating recoveries unrelated to harm. See default interest clauses unenforceable for the related analysis. Early termination fees specifically face a separate line of unconscionability cases that overlap with, but do not duplicate, the penalty doctrine. See early termination fees: unconscionability claims. The drafter’s job is to know which framework is actually going to govern. A clause drafted under the wrong assumption is exposed.

The clauses that interact most directly with stipulated damages are consequential-damages waivers and overall liability caps. Each does different work and rests on different doctrine. For how those companions operate, see consequential damages in contract breaches.

Closing thought

A liquidated damages clause is a small piece of contract real estate that does outsized work when it survives and creates outsized problems when it does not. Minnesota’s framework is stable, the leading case is six decades old, and later applications are not surprising; they are reapplications of Gorco to fact patterns that drafters keep producing.

The pattern that breaks clauses is the same one that has broken them since 1959: a number that does not fit the contract, set against damages that were not actually hard to estimate, layered on top of other recoveries without accounting for mitigation.

The pattern that saves clauses is the opposite: a number tied to a real estimation problem, calibrated to anticipated harm, written as a single coordinated remedy, and clear about how it interacts with the rest of the contract.

For a candid read on a specific clause you are about to sign or send, our Minnesota business contracts practice handles this work regularly. Email [email protected] with a short description of the deal, and hold any confidential documents until an intake and conflict check are complete. After that, I can give you a focused assessment of where the clause is strong and where it is exposed.