UETA vs. ESIGN: What Sales Teams Need to Know

UETA and ESIGN both do the same basic job. They say a signature or contract can’t be thrown out just because it’s electronic. The difference is where each one comes from. ESIGN is a federal statute passed in 2000. UETA is a model law that each state adopts on its own, so the version you rely on depends on where your deal lives. For most B2B SaaS contracts, the two work together and a signature in your sales workflow is valid. The gaps show up in a few excluded document types, in consumer-facing deals, and in the evidence you keep.

This guide is for SaaS sellers, sales engineers and solutions consultants who send order forms, MSAs and NDAs and want to know why the signature holds up. It isn’t legal advice. For a specific contract or dispute, talk to your own counsel.

TL;DR

• ESIGN is federal law (15 U.S.C. § 7001) and covers transactions in or affecting interstate or foreign commerce. UETA is a 1999 model act that states adopt individually.
• Both rest on one rule: a signature or record can’t be denied legal effect solely because it’s electronic.
• Both exclude some documents, such as wills and most UCC transactions, so check before you force a digital workflow.
• Real validity depends on intent to sign, consent to do business electronically, and a record that ties the signature to a person.
• Consumer deals trigger extra ESIGN consent steps. Most B2B SaaS deals don’t, but any B2C-style sale does.

Table of Contents

• The short version: two laws, one idea
• UETA vs. ESIGN side by side
• Where UETA applies and where it doesn’t
• What both laws require for a valid e-signature
• What you can’t sign electronically
• The consumer consent trap
• Common mistakes in SaaS deals
• Why signing belongs inside the deal, not after it
• Our perspective
• A practical checklist before you send the contract
• Where TrailerCast fits
• FAQ
• Sources

The short version: two laws, one idea

Before 2000, a buyer who wanted out of a deal could argue that an emailed or clicked agreement wasn’t “in writing” or “signed.” Two laws closed that door.

UETA came first. The National Conference of Commissioners on Uniform State Laws proposed it in 1999, with the goal of removing legal barriers to electronic commerce. It is a template. A state legislature has to pass it, and can tweak it.

ESIGN followed. Signed into law on June 30, 2000, it gives a general rule of validity for electronic records and signatures in transactions in or affecting interstate or foreign commerce. That means a federal floor under every state.

If you sell software to a company in another state, ESIGN almost certainly applies. The state’s UETA may apply too. In practice you rarely have to choose between them.

UETA vs. ESIGN side by side

The American Bar Association describes the relationship this way: UETA is the law in nearly all U.S. jurisdictions, and ESIGN is federal law. Between them, every jurisdiction has a rule recognizing electronic signatures.

Where UETA applies and where it doesn’t

How many states have adopted UETA depends on who is counting and when. One 2026 summary of the landscape treats it as nearly universal. Some commentators say 47 states plus D.C., Puerto Rico and the U.S. Virgin Islands. Others put it at 49 states. The gap comes mainly from the handful of states that wrote their own statutes. New York, for example, relies on its own electronic signatures law rather than UETA. Washington State, on the other hand, passed a bill in 2020 that adopts UETA, establishing that a signature, record or contract can’t be denied effect solely because it is electronic.

The practical takeaway: don’t memorize a headcount. If a contract is governed by the law of a specific state, look up how that state treats electronic signatures. In every state, ESIGN still sits underneath for interstate commerce.

What ESIGN does to state law

ESIGN works as a federal backstop. Legal commentary summarized by the ABA says it preempts inconsistent state laws and ensures nationwide validity, while UETA handles the details of state-level implementation. For a sales team, that’s good news: a signed order form between a California vendor and a Texas buyer isn’t in a legal gray zone.

What both laws require for a valid e-signature

The statutes don’t hand you a checklist of buttons to click. Practitioners boil validity down to two things, according to the ABA’s real property section:

1. Intent to sign. The person meant to sign, and the act of signing shows it.
2. Agreement to do business electronically. In SaaS sales this is often implied by the exchange of documents, but an explicit clause makes stronger evidence.

On top of that sits a third, practical piece: proof. The law is technology-neutral, so it doesn’t favor any vendor or tool. What makes your signature hold up is the audit trail and security procedures that show who signed. If a deal is ever challenged, you want to show a person, not a machine, signed.

Here’s what that means for your workflow:

• Send the document to the named signer at a verified email, not to a shared inbox.
• Capture timestamps, IP addresses and the document version they saw.
• Include a short clause in the contract confirming both sides agree to sign and keep records electronically.
• Store the final signed copy and the audit trail together.

If you want to see what a clean sales-side process looks like, our 7-step eSignature workflow for sales teams walks through it.

What you can’t sign electronically

This is where most sellers get surprised. “Electronic signature” isn’t one bucket. ESIGN’s specific exceptions carve out records governed by certain laws, and UETA has its own parallel list. The ABA notes that both acts exclude wills, codicils, testamentary trusts, and most transactions governed by the Uniform Commercial Code, other than Articles 2 and 2A.

The ESIGN statute adds other categories, including certain court documents and some formal notices such as those tied to utility cancellation or default and foreclosure. Read section 7003 for the full list.

For a SaaS seller, here is how that plays out:

• A standard subscription agreement, MSA, order form, DPA or NDA is normally fine.
• A security agreement or something that touches secured lending may fall under the UCC. Ask counsel.
• A buyer’s legal team may insist on wet ink for their own reasons. That’s a contract preference, not a legal bar. Be ready to accommodate it without losing the deal.

When in doubt, ask whether the document is governed by something other than ordinary contract law. If it is, check before you build a digital-only process around it.

The consumer consent trap

Most of our readers sell to businesses, so this section may not apply. But small-business buyers, sole proprietors and anything that looks like a consumer sale can pull you into it.

Under ESIGN, when a law requires information to be given to a consumer in writing, the electronic record has to come with a clear statement of the consumer’s right to request paper, the right to withdraw consent, and the hardware and software needed. The consumer also has to show they can actually access the records, for example by clicking a link to open the document. A bare “sign here” button doesn’t meet that standard, and skipping the steps can leave the signature open to challenge by the consumer.

If your product ever sells to individuals rather than companies, build the disclosures and the access check into the signing flow, and have counsel review them.

Common mistakes in SaaS deals

I’ve watched deals go sideways in small ways that were avoidable. These come up the most:

• Treating a typed name in an email thread as the contract. It may be enforceable, but you’ve got weak evidence of who agreed to what and when.
• Forgetting the signer’s authority. The law validates the signature. It doesn’t confirm the person can bind their company. Confirm title or ask for a signing authority statement.
• Letting a champion sign for a buyer they don’t control. In a multi-stakeholder deal, the person you’ve talked to for six weeks may not be the person who approves.
• Sending a PDF by email and calling it done. Without an audit trail, you’ve got a file, not proof.
• Ignoring state-specific quirks. If the buyer’s state has its own statute, check how it handles attribution and security procedures.

Why signing belongs inside the deal, not after it

Here’s the part that doesn’t show up in the statutes. The legal question is rarely what kills a deal. The space between the last call and the signature does. The champion walks back to a CFO who wasn’t on the demo, the CISO’s questions sit in a recording nobody rewatches, and the contract shows up from a separate tool with no context.

When signing happens in a different system from the conversations, you lose the thread. You also lose some of your evidence. The record of who saw what, when, and in what order is scattered across a call recorder, an email inbox and a signature app.

We wrote more about this in why in-app signing wins. The short version: keep the buyer in one place from first call to signature, and the audit trail follows the deal.

Our perspective

We built TrailerCast because the calls were never the problem. The space between them was. Contracts are a clear example. A seller can run a flawless discovery call and a sharp demo, then lose three weeks to a signing process bolted on at the end.

On the legal side, our view is plain. UETA and ESIGN have settled the question of whether electronic signatures count. You don’t need to be a lawyer to sell with confidence. You do need to know the three things that still trip people up: excluded documents, consumer consent, and thin evidence. The first two are about knowing your deal. The third is about your tooling.

Because both laws are technology-neutral, no tool makes a signature valid by itself. What a good workflow gives you is the record: who signed, when, on which version, with the context of the deal around it. That is why we put eSignature in the same workspace as calls, trailers and buyer-facing Decision Rooms, and why our embedded contract signing feeds straight into a handoff brief for the team that picks up after close.

If you’re setting this up for a team, bring your counsel in early, give them the real contract templates, and ask them to confirm the exclusions and consent language for the states and customer types you sell to.

— Daniel

A practical checklist before you send the contract

Use this as a last pass, in order:

1. Check the document type. Is it a standard commercial agreement, or something touching wills, trusts, UCC secured transactions, court filings or formal notices?
2. Check the buyer. Business or consumer? If there’s any consumer element, add the ESIGN disclosures and access demonstration.
3. Check the governing law. Which state’s law governs? Look up its electronic signature statute.
4. Add the electronic-records clause. A short paragraph confirming both parties agree to transact and sign electronically.
5. Verify the signer. Named individual, work email, appropriate authority.
6. Confirm the audit trail. Timestamps, IP data, document version, and a stored final copy.
7. Have a wet-ink fallback. If procurement asks, don’t argue. Offer it and keep moving.

Where TrailerCast fits

TrailerCast puts conversation intelligence, AI-edited demo trailers, buyer-facing Decision Rooms, embedded eSignature and post-close handoff in one workspace. Your buyer’s questions, the stakeholder trailers you sent, and the signing step all live on the same deal record.

Pricing is simple: one plan with every feature, from $59 per month per seat. If you want to see how the pieces connect, start with our buyer portal and Decision Rooms or read about our approach to security. This article explains the law in general terms. It isn’t a statement that any specific workflow meets the legal requirements for your contracts, so have your counsel confirm that.

FAQ

Are electronic signatures legal in the USA?

Yes. Federal law (ESIGN) and state laws (mostly UETA) provide that a signature or contract can’t be denied legal effect solely because it is electronic. Certain document types, such as wills and most UCC transactions, are excluded, so check those separately.

Does UETA or ESIGN apply to my B2B contract?

Often both. ESIGN covers transactions in or affecting interstate or foreign commerce, and the governing state’s electronic signature law applies too. If they conflict, the federal law acts as the backstop. Your counsel can confirm how this works for your governing-law state.

What legal documents can’t be signed electronically?

The common exclusions are wills, codicils, testamentary trusts, and most transactions under the Uniform Commercial Code. ESIGN also lists certain court documents and formal notices. The full list is in 15 U.S.C. § 7003.

Do I need special software to make an e-signature valid?

No. Both laws are technology-neutral. What matters is intent to sign, agreement to transact electronically, and a record, like an audit trail, that ties the signature to the person. A purpose-built tool makes that record easier to produce.

Sources

• Electronic Signatures and Legal Opinions, American Bar Association
• Comment Concerning Use of Electronic Signatures and Third-Party Opinion Letters, American Bar Association
• 15 U.S.C. § 7001: General rule of validity
• 15 U.S.C. § 7003: Specific exceptions
• FDIC: The E-Sign Act examination manual
• An Overview of Electronic Signatures, Otten Johnson

Recommended

• 7 Step eSignature Workflow for Sales Teams Closing Contracts Faster
• Embedded eSignature for Sales | Auto Handoff Brief
• Embedded eSignature Benefits: Why In-App Signing Wins