Statute of Frauds & E-Signatures: What Must Be in Writing (2026)

Key Takeaways: Which Contracts Must Be in Writing · E-Signatures Satisfy the Writing Requirement · UCC Article 2 vs Common Law Rules · State-by-State Exceptions · Practical Compliance Strategies

TL;DR: The Statute of Frauds requires certain contracts to be "in writing" and "signed" — but both federal (ESIGN Act) and state (UETA) law confirm that electronic records and e-signatures satisfy these requirements. The key exceptions are narrow: wills, certain trust instruments, and specific UCC provisions. For everyday business contracts — real estate, agreements that can't be performed within one year, guarantees, and sales of goods over $500 — e-signatures are fully valid. This guide maps the requirements by contract type and jurisdiction.

The Statute of Frauds is one of the oldest doctrines in Anglo-American contract law — dating to a 1677 English statute designed to prevent fraudulent claims about oral agreements. Its core principle remains relevant: certain categories of contracts must be evidenced by a signed writing to be enforceable.

For businesses adopting electronic signatures, the Statute of Frauds raises a natural question: does an electronic record count as a "writing"? Does an electronic signature count as "signed"? The answer, in virtually all cases, is yes — but the path to that answer involves navigating federal law, state adoptions, and a small but important set of exceptions.

The Six Traditional Categories: What Must Be in Writing#

The Statute of Frauds typically requires a signed writing for six categories of agreements (with state variations):

1. Contracts for the sale of land — Any agreement transferring an interest in real property, including sales, long-term leases (typically over one year), easements, and mortgages. This is the most consistently enforced category across all states.

2. Contracts that cannot be performed within one year — If the terms of the agreement make it impossible to complete performance within 12 months from the date of formation. Note: if the contract could theoretically be performed within a year (even if it's unlikely), many courts hold it falls outside the Statute.

3. Contracts for the sale of goods over $500 (UCC §2-201) — Under the Uniform Commercial Code, contracts for the sale of goods priced at $500 or more require a writing. The 2003 UCC revision raised this to $5,000, but most states still apply the $500 threshold.

4. Surety agreements (guarantees) — A promise to pay the debt of another person must be in writing. The key distinction: a direct promise to a creditor ("I'll pay if they don't") requires writing; a direct arrangement between parties doesn't.

5. Contracts in consideration of marriage — Prenuptial agreements and property settlements incident to marriage. The marriage itself isn't required to be in writing — the ancillary financial agreements are.

6. Executor/administrator promises to pay estate debts — When a personal representative promises to pay estate obligations from their own funds (not estate assets), a writing is required.

How ESIGN and UETA Resolve the E-Signature Question#

The Federal ESIGN Act (15 U.S.C. §7001) states unambiguously: "a signature, contract, or other record relating to such transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form." This means electronic records satisfy the "writing" requirement, and electronic signatures satisfy the "signed" requirement — for all categories subject to the Statute of Frauds that fall within ESIGN's scope.

The Uniform Electronic Transactions Act (UETA), adopted by 47 states plus D.C., provides the state-level equivalent. Section 7(a) states: "A record or signature may not be denied legal effect or enforceability solely because it is in electronic form." Section 7(c) explicitly addresses the Statute of Frauds: "If a law requires a record to be in writing, an electronic record satisfies the law."

Practical effect: An electronically signed contract for the sale of a $2 million commercial building satisfies the Statute of Frauds in every U.S. jurisdiction. The electronic record is the "writing." The electronic signature is the "signature." The audit trail provides evidence of execution that exceeds what a wet signature typically provides.

The exceptions that still matter:

• Wills, codicils, and testamentary trusts — excluded from both ESIGN and UETA
• Court orders and court-required documents — often excluded by state law
• Notices of insurance cancellation, default, or foreclosure — excluded from ESIGN (not UETA)
• Certain UCC documents (Articles 3, 4, 8, 9) — carved out from UETA Section 3

UCC Article 2 Specifics: Sales of Goods#

The UCC Statute of Frauds for goods transactions (§2-201) has its own nuances:

What satisfies the writing requirement: A signed writing "sufficient to indicate that a contract for sale has been made between the parties." It doesn't need to contain every term — just enough to confirm a deal exists, plus the quantity. Price, delivery terms, and other details can be missing.

The merchant's exception (§2-201(2)): Between merchants, a written confirmation sent within a reasonable time that the recipient doesn't object to within 10 days satisfies the Statute of Frauds against both parties. An email or electronic message from one merchant to another confirming a sale, unrebutted for 10 days, creates a binding writing.

Specially manufactured goods (§2-201(3)(a)): If goods are specially manufactured for the buyer and the seller has substantially begun production, no writing is required at all — the Statute of Frauds doesn't apply.

Electronic records easily satisfy §2-201 requirements. A purchase order sent through a procurement platform, an email confirming a sale, or an e-signed supply agreement all qualify. ZiaSign's audit trails provide additional protection by documenting exactly when the writing was created, delivered, and acknowledged.

Practical Compliance: Ensuring Your E-Signed Contracts Hold Up#

While the legal framework clearly validates e-signatures for Statute of Frauds purposes, practical compliance requires attention to detail:

1. Ensure the contract identifies the parties. The electronic record should clearly state who the parties are — not just email addresses, but legal names and, where relevant, entity information.

2. Include quantity terms in goods contracts. Under UCC §2-201, quantity is the one essential term. An e-signed agreement for "widgets at $10 each" without specifying how many is potentially unenforceable.

3. Maintain the electronic record intact. The Statute of Frauds requires a "writing" — if you can't produce the electronic record later, you've lost your evidence. Use a platform that provides long-term retention with tamper-evident audit trails.

4. Confirm signatory authority. The Statute of Frauds requires the writing to be signed "by the party to be charged." In a business context, ensure the signer has authority to bind the entity. An e-signature from an unauthorized employee doesn't satisfy the requirement.

5. Don't forget witness and notarization requirements. The Statute of Frauds specifies a "signed writing" — but other laws may impose additional formalities. Real estate transactions often require notarization. Some states require witnesses for certain documents. These requirements exist in addition to the Statute of Frauds.

ZiaSign's platform addresses all five considerations: clear party identification, structured template fields that ensure required terms are captured, tamper-evident long-term storage, role-based signing authority workflows, and integration with notarization and witness verification services.

This article is part of ZiaSign's comprehensive resource library. Explore more guides at ziasign.com/blogs, or try our 119 free PDF tools.

Practical Compliance Checklist#

Before rolling out statute of frauds & e-signatures: what must be in writing, confirm signer evidence, retention expectations, exception handling, review ownership, and what proof the business will need later.