Minnesota Statute of Frauds: What Must Be Written

What does Minnesota’s statute of frauds actually cover?

Minnesota’s statute of frauds covers six big categories of contract. Four sit in Minn. Stat. § 513.01: agreements not to be performed within one year, special promises to answer for another’s debt, agreements made upon consideration of marriage, and promises to pay a debt discharged in bankruptcy or insolvency. Two more sit elsewhere in chapter 513: contracts for the sale or long-lease of land in § 513.05 and conveyances of land interests in § 513.04. The Uniform Commercial Code adds a seventh: sales of goods for $500 or more under § 336.2-201.

Each category has its own escape valves and quirks. Section 513.01 requires the writing to be “subscribed by the party charged therewith” and to express the consideration. Section 513.05 uses the word “void,” not just unenforceable, when its requirements are missed. Section 336.2-201 keeps the contract alive against a party who admits it in court, even without a writing. The starting point for any contract dispute is to identify which category applies, because the rules diverge from there. For other contract enforceability rules that interact with these, see Minnesota’s other contract enforceability rules.

When does the one-year rule require a writing?

Minn. Stat. § 513.01 requires a signed writing for “every agreement that by its terms is not to be performed within one year from the making thereof.” The test is the agreement’s own terms, not what actually happens. A deal that could in theory be performed within a year is outside the statute, even if both sides expect it to take longer.

That distinction matters in practice. An at-will employment relationship is outside the statute even if the employee stays for a decade, because either side could end it within the year. A two-year supply contract is inside the statute and needs a writing. A 13-month consulting engagement that begins on the day of signing is also inside. The trickier cases come up at the edges: a deal signed in March that begins in July and runs 12 months from start crosses the one-year line by four months and falls inside the statute. Verbal understandings that quietly stretch across a year through the kind of term extensions by silence common in vendor relationships often cross this line without anyone noticing.

In my practice, the recurring pattern is a multi-year service agreement that started as a one-year deal, was extended verbally to “another year or two,” and then both sides act surprised when one side disputes the extension.

Do real-estate and long-lease contracts have to be in writing?

Real-estate contracts in Minnesota sit in the most rigid category of the statute. Minn. Stat. § 513.05 provides that “Every contract for the leasing for a longer period than one year or for the sale of any lands, or any interest in lands, shall be void unless the contract, or some note or memorandum thereof, expressing the consideration, is in writing and subscribed by the party by whom the lease or sale is to be made, or by the party’s lawful agent thereunto authorized in writing.” The companion section, § 513.04, governs the actual conveyance of any “estate or interest in lands” and requires the same kind of signed writing.

Three details trip operators. First, the statute uses the word “void,” not “unenforceable,” a stronger formulation than many other Minnesota statute-of-frauds categories. Second, leases of one year or less are carved out, but a lease that runs longer than a year (an 18-month office lease, for instance) needs a writing. Third, when an agent is signing on behalf of an owner, § 513.05 requires the agent’s authority to be in writing too, and if the contract gets recorded, the agent’s written authority must be recorded as well. Verbal authorizations to a real-estate agent or broker do not survive a challenge.

When does selling goods trigger Minnesota’s $500 writing rule?

Sales of goods at or above $500 fall under Minn. Stat. § 336.2-201, Minnesota’s enactment of the Uniform Commercial Code’s statute of frauds for goods. Subsection (1) provides that “a contract for the sale of goods for the price of $500 or more is not enforceable by way of action or defense unless there is a record sufficient to indicate that a contract for sale has been made between the parties and signed by the party against whom enforcement is sought.” A signed quote, a signed purchase order, or a signed confirmation generally satisfies the rule.

The threshold is still $500 in Minnesota. Some states adopted a 2003 amendment raising the trigger to $5,000; the drafters later withdrew that amendment, and Minnesota never adopted it. Two practical points follow. First, the writing does not have to be the “contract” itself: a stub of a memo identifying the parties, the goods, and the quantity is enough. Second, the section says enforcement is limited “beyond the quantity of goods shown in such record,” meaning a writing that names 1,000 widgets cannot support a claim for 5,000.

Article 2 generally does not reach pure service deals, and its application to software licenses is mixed; the predominant-purpose test usually controls. Many SaaS and service contracts therefore fall under chapter 513’s general statute of frauds rather than § 336.2-201.

What counts as “a writing,” and does email or DocuSign work?

A “writing” under § 513.01 and § 513.05 does not have to be the contract itself. The statute permits “the agreement, or some note or memorandum thereof, expressing the consideration.” Minnesota courts have read that to allow a chain of documents (a signed quote, an email accepting it, an invoice) to satisfy the rule together, so long as one of them is signed by the party being held to the deal.

Electronic records and signatures generally count. Minnesota has adopted the Uniform Electronic Transactions Act at Minn. Stat. ch. 325L, and the federal E-SIGN Act provides a parallel rule. Together they make a DocuSign envelope, a signed PDF, and a clear email exchange functionally equivalent to a wet-ink signature for most business contracts. The same logic carries over to online clickwrap and browsewrap contracts, where the writing requirement is usually satisfied by the manifestation of assent at click-through.

The trap is incomplete documentation. An email that says “great, let’s do it” without identifying terms or consideration is not a “note or memorandum” of anything specific. Side-letter understandings on top of a signed master agreement also raise integration clauses and side letters issues, where the master agreement’s merger clause may swallow the oral side deal regardless of the statute of frauds.

Is a personal guaranty enforceable without a signed writing?

No, with a narrow exception. Minn. Stat. § 513.01 requires that “every special promise to answer for the debt, default or doings of another” be in writing. A handshake guaranty of a corporation’s loan, a verbal promise to backstop a subsidiary’s lease, an oral assurance to a vendor that a parent company will cover a sister company’s invoices: all unenforceable without a signed instrument expressing the consideration.

Minnesota courts have generally treated promises that fall under the “main purpose” doctrine differently. Where the promisor’s primary aim is the promisor’s own economic benefit (rather than acting purely as a surety for someone else), the promise is treated as the promisor’s own contract and falls outside the suretyship clause. The doctrine is narrow and fact-specific, and clients lose more main-purpose arguments than they win. The safer path is to insist on a signed guaranty for any third-party debt, and to make sure the guaranty is supported by the right corporate authority. See personal and corporate guaranties for the related authority issues that often surface in these disputes.

Are bank loan modifications and forbearance agreements enforceable orally?

No. Minnesota has a separate, stronger statute of frauds for credit agreements at Minn. Stat. § 513.33. Subdivision 2 provides that “A debtor may not maintain an action on a credit agreement unless the agreement is in writing, expresses consideration, sets forth the relevant terms and conditions, and is signed by the creditor and the debtor.” Unlike the general statute, the credit-agreement rule requires both sides to sign.

Subdivision 3 then forecloses most of the verbal workarounds lenders and borrowers commonly try. Verbal financial advice from a banker, verbal consultations, and verbal agreements to forbear from exercising remedies (including foreclosure, acceleration, or repossession) or to extend installments do not give rise to a credit agreement absent a writing that satisfies subdivision 2. A loan officer’s spoken assurance that “we’ll work with you” or “we won’t call the loan this quarter” is unenforceable. About half of the lender-borrower disputes I see involve a borrower trying to enforce a verbal forbearance the bank now denies, and § 513.33 almost always wins for the bank.

The takeaway for CEOs is straightforward: any change to a loan, line of credit, or forbearance arrangement needs to land in a signed amendment or written forbearance agreement before it is relied on.

What if there is no writing: can the deal still be enforced?

Sometimes. Minnesota recognizes four practical escape paths when the statute of frauds technically blocks enforcement. The first is part performance in equity. Minn. Stat. § 513.06 preserves the equitable doctrine: “Nothing in this chapter contained shall abridge the power of courts of equity to compel the specific performance of agreements in cases of part performance thereof.” Minnesota courts have applied the doctrine most often in real-estate cases, typically where a buyer has taken possession, paid the purchase price, and made improvements.

The second is the UCC merchant rule. Under § 336.2-201(2), a written confirmation between merchants binds the silent recipient unless the recipient objects in writing within 10 days. This is the most common reason a one-sided written confirmation ends up enforceable against a buyer who never signed anything. The third is the trio of UCC escapes in § 336.2-201(3): specially manufactured goods, in-court admission that a contract existed, and goods that have been paid for and accepted (or received and accepted), limited to the quantity actually paid for or received.

The fourth is promissory estoppel, a doctrinal Minnesota overlay applied where the asserting party reasonably relied on a clear promise and would suffer injustice if the writing requirement were enforced. Note that § 513.33’s credit-agreement rule is generally treated as foreclosing promissory estoppel against lenders, so the doctrine is most useful in non-credit, non-real-estate disputes. None of these escapes is reliable. Each requires litigation to establish, and the cost of arguing the exception almost always exceeds the cost of getting a writing in the first place. For the related question of when oral modifications of written contracts survive an integration clause, the analysis runs along similar lines.

How do Minnesota CEOs avoid statute-of-frauds problems in practice?

The pattern across my practice is the same. The deals that go to dispute are almost never the ones with a signed master agreement and clean amendments. They are the ones where a one-year vendor relationship rolled into year three on emails, a $200,000 equipment order moved on a verbal promise, a sister company’s lease was backstopped by the parent on a phone call, and a bank’s forbearance was extracted from a loan officer at a coffee meeting.

Five practical habits prevent most of these disputes. First, get a signed quote, signed purchase order, or signed engagement letter that names the parties, the deliverable, and the price before performance starts. Second, write change orders for any modification, even small ones, especially on multi-year deals. Third, never accept a verbal guaranty for any third-party debt; insist on a signed guaranty backed by board or member approval where the guarantor is an entity. Fourth, paper every conversation with a lender that touches loan terms, forbearance, or extensions, and require the bank’s signature. Fifth, treat the difference between a service contract and a goods contract as worth understanding, because the Article 2 escape valves only apply to goods. For a strategic frame on this, see how to think about contracts as a system rather than as one-off documents.

The statute of frauds rewards discipline. Minnesota’s framework adds a few demanding details (the “expressing the consideration” requirement, the void-not-unenforceable language for land sales, the two-signature credit-agreement rule), and a single missing signature on a real-estate deal or a multi-year supply agreement can wipe out the deal entirely. The fix is rarely complicated and almost never expensive. A signed page at the start of a deal is dramatically cheaper than litigating part-performance two years later. For a broader read on contract systems and enforceability, see our contracts practice area. If a specific deal is sitting on documents that may not satisfy the statute of frauds, email aaron@aaronhall.com with a brief description and the relevant documents for a practical read on the exposure.