A Minnesota CEO signs a service contract with a vendor. A year later, a stranger to the deal sues the company on the contract, claiming the agreement was written to benefit them. The CEO never met this person, never negotiated with them, and never thought of them as a counterparty. Can they really sue?
In Minnesota, the answer is sometimes yes, and the question turns on a doctrine most business owners have never heard of: third-party beneficiary rights. This article explains when an outsider can enforce a Minnesota contract, when they cannot, and how to draft so that the answer is the one you intended. For the broader picture on commercial contracting and risk allocation, see our contracts practice area.
What is a third-party beneficiary in Minnesota contract law?
A third-party beneficiary is a person or entity who is not a party to a contract but who may, in defined circumstances, sue to enforce it. Minnesota follows the framework set out in the Restatement (Second) of Contracts § 302, which the Minnesota Supreme Court adopted in Cretex Companies, Inc. v. Construction Leaders, Inc., 342 N.W.2d 135 (Minn. 1984). Under that framework, beneficiaries fall into two categories. Intended beneficiaries can enforce the contract. Incidental beneficiaries cannot. The entire doctrine is an exercise in sorting which side of that line a particular outsider falls on.
The intuition behind the rule is that contracting parties should be able to confer enforceable rights on outsiders when they choose to, but should not be ambushed by every person who happens to benefit from a deal. A contractor who paves a road benefits every commuter who drives on it; the commuters cannot sue if the work is shoddy. A general contractor whose subcontractor finishes a job benefits the project owner; the owner often can sue, because the contract was written to benefit them. The line between those two outcomes is the question of intent.
What is the test for an intended beneficiary?
Minnesota courts apply two alternative tests, drawn from Restatement § 302. A beneficiary qualifies as intended if either test is satisfied, provided that recognition of the beneficiary’s right is appropriate to effectuate the intention of the parties. The “appropriateness” gateway is part of the verbatim Restatement text and is not a throwaway.
The first test is the duty-owed test. The performance of the contract must discharge an obligation the promisee already owes to the third party.
The classic example: Company A owes money to Lender L. Company A then signs a contract with Buyer B, in which B agrees to pay L directly. B’s performance will discharge A’s debt to L. L is an intended beneficiary of the A-B contract and can sue B if B does not pay.
The second test is the intent-to-benefit test. The contract must express the contracting parties’ intent to benefit the third party through contractual performance. The Minnesota Court of Appeals stated this directly in Hickman v. Safeco Ins. Co. of Am., No. A03-2042 (Minn. Ct. App. Aug. 17, 2004) (unpublished) (available at https://mn.gov/web/prod/static/lawlib/live/archive/ctapun/0408/opa032042-0817.htm): “Unless the contract expresses the parties’ intent to benefit a third party through contractual performance, the third party is no more than an incidental beneficiary.” The intent must come through in the contract language, not from one party’s private hope or one beneficiary’s preferred reading.
Either test can be satisfied alone. A beneficiary does not need to win both. But the appropriateness gateway runs through both. A court will not recognize an enforcement right where the parties’ overall intent points the other way, even if a single clause looks like a duty-owed promise.
What is an incidental beneficiary, and why does it matter?
An incidental beneficiary is anyone who benefits from a contract without having been the object of contractual intent. Restatement § 302(2) is one sentence: an incidental beneficiary is a beneficiary who is not an intended beneficiary. Minnesota law gives incidental beneficiaries no right to enforce.
The category sweeps broadly. Employees of a customer who benefit when their employer’s vendor delivers on time. Neighbors of a property owner whose construction contract improves the neighborhood. Downstream suppliers whose business improves when a major customer signs a long-term deal.
All of them benefit. None of them can sue.
The reason the doctrine matters for drafting is that the line between intended and incidental beneficiaries is determined almost entirely by the contract’s words. A contract that names a third party and prescribes performance for that party’s benefit creates an intended beneficiary. A contract that operates in a commercial environment where outsiders happen to benefit does not. CEOs who want to control their exposure to outsider lawsuits should treat the contract’s text as the dial that sets that exposure.
When does a beneficiary’s right become “vested”?
Vesting is the point at which the beneficiary’s right hardens against unilateral change by the contracting parties. Before vesting, the original parties can amend, modify, or rescind the contract without the beneficiary’s involvement, even when the amendment eliminates the beneficiary’s rights entirely. After vesting, the beneficiary has a stake the parties cannot rewrite around.
Under the Restatement (Second) of Contracts § 311 framework that Minnesota courts apply, a beneficiary’s rights vest when any one of three things happens. First, the beneficiary materially changes position in justifiable reliance on the promise. Second, the beneficiary brings suit on the promise. Third, the beneficiary manifests assent to the promise in the manner requested by the contracting parties.
The practical effect is sequencing. If your company has a contract that names a third party and the parties later want to renegotiate, the question is whether the beneficiary has done anything yet. A beneficiary who has stood pat, taken no action in reliance, and made no formal assent is generally vulnerable to amendment. A beneficiary who has restructured operations around the promise, hired staff, or borrowed against the expected performance is much harder to write out.
What defenses can the promisor raise against the beneficiary?
A third-party beneficiary’s claim is not stronger than the underlying contract. The beneficiary stands in the shoes of the promisee for purposes of enforcement and is subject to the same contract-based defenses the promisor could raise against the promisee.
That includes the obvious ones. If the promisee never performed its side of the deal, the promisor can raise that failure against the beneficiary’s claim. If the contract is unenforceable for fraud, mistake, or lack of consideration, those defenses are available. If the contract has a limitation of liability provision, an integration clause excluding extrinsic promises, or an arbitration clause, Minnesota courts often apply those provisions against the beneficiary as a matter of doctrine, though the analysis is fact-specific and turns on the contract’s wording.
This last point catches non-lawyers off guard. A beneficiary who is happy to enforce the favorable parts of a contract often discovers they are also bound by the unfavorable parts. If the contract caps damages at the fees paid in the prior twelve months, the beneficiary’s recovery is capped on the same terms. If the contract requires arbitration in Hennepin County, the beneficiary arbitrates in Hennepin County. The beneficiary takes the deal as written.
How do you draft a Minnesota contract to keep beneficiaries out?
The standard tool is a “no third-party beneficiaries” clause. A clean version reads roughly as follows: this agreement is intended solely for the benefit of the parties and their permitted successors and assigns, and is not intended to confer any rights or remedies on any other person or entity. Minnesota courts will generally honor such language when the rest of the contract is consistent with it.
Three drafting points decide whether the clause holds.
In my practice advising Minnesota businesses, the recurring failure I see is the contract that pairs a confident “no third-party beneficiaries” disclaimer at the back with a payment-direction or performance clause at the front that names a specific outsider. The disclaimer is usually pulled from a template; the operative clause is bespoke. The bespoke clause wins more often than CEOs expect.
First, audit the rest of the contract for accidental beneficiaries. A no-beneficiary clause coexisting with a payment-direction provision that names a specific lender is a contradiction the no-beneficiary clause may lose. If the contract directs the promisor to perform for someone outside the deal, fix that provision rather than relying on the disclaimer to neutralize it.
Second, do not hedge. Phrases like “except as may otherwise be inferred from the express terms of this agreement” reopen the question the disclaimer is meant to close. A flat statement is more durable than a hedged one.
Third, coordinate with related provisions. Indemnification language that runs in favor of “any affiliate, officer, or representative” of the counterparty creates third-party rights for those persons. Either accept that exposure or write the indemnity to run only between the contracting parties. Our article on indemnification clauses in Minnesota contracts goes deeper on this drafting choice.
How do you draft to give a specific outsider enforcement rights?
When the goal is the opposite, name the beneficiary, state the parties’ intent, and describe the performance. A clause along these lines does the work: the parties intend that [Beneficiary], as a third-party beneficiary of this agreement, shall have the right to enforce [specified obligation] directly against [Promisor], and recognition of that right is appropriate to effectuate the parties’ intention.
That language tracks the Restatement § 302 vocabulary on purpose. Minnesota courts read contracts against the framework they apply, and a clause that uses the framework’s own words is harder to mischaracterize. The drafter should also identify the beneficiary precisely. “Lender” is weaker than “the lender identified on Schedule A,” which is weaker than the lender’s full legal name and address. Specificity reduces the risk that someone outside the named class later argues their way into the protection.
Coordinate the beneficiary clause with the rest of the deal. If the parties want to retain the right to amend without the beneficiary’s consent, the contract should say so expressly. If the beneficiary’s rights should expire on a defined event, write the expiration into the same provision that creates the right.
How does third-party beneficiary doctrine interact with assignment and assumption?
Two situations where the doctrine repeatedly surfaces in Minnesota commercial practice are business sales and contract assumptions. When a buyer assumes the seller’s contracts, the question whether the contract counterparties become third-party beneficiaries of the assumption agreement turns on the same intent analysis. An assumption that names the contracts and states the buyer will perform for the counterparties’ benefit usually creates beneficiary status. An asset purchase that conveys contracts without specific performance language often does not.
These transactions also implicate the related doctrines of assignment and delegation, which decide whether the contracts move at all. The two analyses run on parallel tracks and answer different questions. Assignment law asks whether the rights and duties under the contract have transferred. Beneficiary law asks who can enforce them once they have.
A pattern I see repeatedly in business-sale disputes: customers and downstream vendors of the seller surface months after closing, claiming the assumption agreement promised them performance directly. The merits usually turn on a single sentence in the asset purchase agreement that the parties drafted without thinking about who could later read it as a promise running their way.
A clean transaction addresses both. Our overview of assignment and delegation clauses covers the transfer side of the question.
What about beneficiaries of guarantees, bonds, and indemnity letters?
Performance bonds, payment guarantees, and indemnity letters are common contexts for beneficiary disputes because the entire reason the instrument exists is to benefit someone other than its signatories. Even so, Minnesota courts apply the same intent test. Cretex itself was a performance-bond case, and the Minnesota Supreme Court held that the unpaid materialmen were not intended beneficiaries of the general contractor’s bond because the bond was written to benefit the owner-obligee, not the suppliers. The holding cuts against the intuition that everyone touched by a bond can sue on it.
The drafting takeaway is that a guarantee or bond should explicitly name the persons it is meant to protect. A construction performance bond can be written to cover the owner only, the owner and named subcontractors, or any unpaid supplier. The instrument’s words decide which. The same is true of corporate guarantees, letters of credit, and standby support arrangements. Specificity at signing avoids litigation later.
What are the most common drafting mistakes in this area?
Three recurring patterns produce litigation Minnesota businesses could have avoided.
The first is treating “no third-party beneficiaries” as a fix-all clause without auditing the rest of the contract. The disclaimer is a starting point, not a finishing line. Provisions deeper in the contract regularly create the very rights the disclaimer purports to deny.
The second is overgeneral indemnification or insurance language. A promise to indemnify “any person harmed by the operations described herein” sweeps in plaintiffs the parties never imagined. If the indemnity is intended to run only between the contracting parties, the clause should say so.
The third is assuming employees, affiliates, or downstream customers are protected because they would benefit from performance. Without express contract language, those parties are incidental beneficiaries with no enforcement right. Companies that need protection for affiliates or employees should put that protection in the contract by name, not assume it follows from commercial reality.
For more on how clean contract drafting reduces litigation exposure across these and related issues, see our contracts practice overview.
Can someone we never contracted with actually sue us on our contract?
Sometimes, yes. If your contract was written in a way that intended to benefit a specific outside person or entity, that person can sue to enforce it under Minnesota’s adoption of the Restatement (Second) of Contracts § 302 framework. The leading case is Cretex Companies, Inc. v. Construction Leaders, Inc., 342 N.W.2d 135 (Minn. 1984). The reverse is also true: if the third party is merely an incidental beneficiary, they have no enforcement rights regardless of whether they benefited in fact. The dividing line is intent expressed in the contract, not benefit received in practice.
Does a 'no third-party beneficiaries' clause actually work?
Usually yes, when it is written cleanly and the surrounding language does not contradict it. Minnesota courts begin the intent inquiry with the contract text, and an express disclaimer is strong evidence that the parties did not intend to confer enforceable rights on outsiders. The risk is inconsistency. If one section disclaims third-party rights but another section names a specific outside person and prescribes performance for that person’s benefit, the disclaimer can be undercut. Treat the no-beneficiary clause as a default, then audit the rest of the contract to make sure no provision accidentally creates the very relationship the clause says does not exist.
Can a lender sue us if we promised in a contract to pay them directly?
Probably yes. That is the textbook duty-owed scenario from Restatement § 302(1)(a). When you, the promisor, agree to a performance that will discharge an obligation your counterparty owes to a third party, the third party is an intended beneficiary and can enforce the promise. Lenders, suppliers paid through escrow arrangements, and creditors named in payment-direction provisions all commonly qualify. If you do not want that exposure, the contract should route the payment to your counterparty and let them pay the lender.
Do we need the third party's consent to amend a contract?
Only after their rights have vested. Before vesting, the original parties can amend, modify, or even cancel the contract without involving the beneficiary, even if the amendment eliminates the beneficiary’s rights. Vesting happens when the beneficiary materially relies on the promise, sues on it, or formally assents to it. Before any of those events, the contract is the contracting parties’ property. After any of them, the beneficiary has a stake the parties cannot rewrite around without consent.
Are employees third-party beneficiaries of contracts the company signs?
Usually not. A vendor agreement that benefits the company in turn benefits its employees, but that is exactly the incidental-benefit pattern that Minnesota law denies enforcement to. Employees become intended beneficiaries only when the contract specifically promises something to them by name or by class, such as a benefits-plan agreement, a successor-employer commitment in a sale, or a settlement that directs payment to identified workers. General commercial contracts almost never create employee-enforceable rights.
Can customers sue a buyer who assumed our contracts in a business sale?
Often yes, depending on how the assumption was written. An assumption that names the customer agreements and states the buyer will perform for the customers’ benefit typically creates intended-beneficiary status. A pure asset purchase that transfers contracts but does not promise customer-specific performance is harder to enforce as a beneficiary. Pair this analysis with the assignment rules in our article on assignment and delegation clauses; the two doctrines often govern the same fact pattern from different angles.
Conclusion
Third-party beneficiary doctrine is a quiet provision of Minnesota contract law that decides who is allowed to walk through your courthouse door on a contract you signed. The framework is straightforward to state: intended beneficiaries enforce, incidental beneficiaries do not, and intent is read from the contract’s words. The framework is harder to apply, because most contracts were not drafted with the doctrine in mind, and the drafter who ignores it is the drafter who is later surprised.
Whether you want a specific outsider to have rights or want no outsiders to have any, the contract is the place to settle the question. CEOs who treat third-party beneficiary status as a drafting variable, not an accident, end up with the contracts they intended. Those who do not learn the doctrine retroactively, in a complaint that names the company as a defendant. For broader contract drafting questions, our contracts practice area collects the related material.
