If you run a US business and sign contracts electronically, two laws decide whether those signatures hold up: the federal ESIGN Act and the state-level UETA. They overlap heavily, which is good news — you rarely have to choose between them — but knowing how they fit together tells you exactly what makes an e-signature enforceable.
This guide explains what each law covers, how they interact, the four requirements every valid e-signature must meet, and the handful of documents that still require a pen.
What is the difference between the ESIGN Act and UETA?
The ESIGN Act is a federal law and UETA is a state model law, but both establish the same core principle: a signature, contract, or record cannot be denied legal effect simply because it is electronic. UETA (the Uniform Electronic Transactions Act, 1999) was drafted for states to adopt, and 49 states plus DC have done so — New York is the notable holdout, using its own statute (Docusign). The ESIGN Act (the Electronic Signatures in Global and National Commerce Act, 2000) is the federal backstop that applies to interstate and foreign commerce. Where a state has adopted UETA, UETA generally governs in-state transactions; ESIGN fills gaps and covers states that have not adopted it. The practical result is consistent: electronic signatures are enforceable nationwide.
How do the ESIGN Act and UETA compare?
The two laws are deliberately aligned, but they differ in scope, source, and reach. The table summarizes the practical distinctions a business owner cares about.
| Aspect | ESIGN Act | UETA |
|---|
| Type of law | Federal | State model law |
|---|
| Year | 2000 | 1999 |
|---|
| Adoption | Nationwide | 49 states + DC (not New York) |
|---|
| Scope | Interstate and foreign commerce | Transactions within an adopting state |
|---|
| Core effect | E-signatures and records are enforceable | E-signatures and records are enforceable |
|---|
| Consumer consent rules | Detailed disclosure requirements | More general |
|---|
Because the substance is so similar, most signing workflows satisfy both at once. The main difference business owners notice is ESIGN's more specific consumer-consent disclosure requirements when signing with individuals.
What are the four requirements for a valid electronic signature?
An electronic signature is legally valid under ESIGN and UETA when four conditions are met: intent to sign, consent to do business electronically, association of the signature with the record, and record retention (Docusign). Intent means each party demonstrably meant to sign — clicking "I Agree" or applying a signature mark. Consent means the parties agreed to transact electronically; with consumers, specific disclosures apply. Association means the signing system keeps a record reflecting how the signature was created and ties it to the document. Retention means both parties can access and keep an accurate copy of the signed record. Miss any one — for example, no clear retained copy — and enforceability weakens. This is also where verification adds value: an issuer-controlled record strengthens both the association and retention elements after signing.
Which documents still require a wet signature?
Some documents are carved out of ESIGN and UETA and may still require a handwritten signature. Both laws explicitly exclude wills, codicils, and testamentary trusts, and matters governed by family law such as adoption and divorce (Adobe). Court documents — pleadings, orders, and official notices — are also excluded, as are certain notices like utility cancellations, foreclosure or eviction notices, product recalls, and documents accompanying hazardous materials. Some states additionally require wet ink for instruments like powers of attorney or health-care directives, so state rules matter. For everything else — commercial contracts, NDAs, offer letters, consent forms — e-signatures are fully enforceable when the four requirements are met. See the distinction between electronic and digital signatures for how technology layers onto these legal rules.
How does VerifyDoc.ai support ESIGN and UETA compliance?
VerifyDoc.ai strengthens the association and retention pillars by making the finished, signed record independently verifiable. ESIGN and UETA require that the signature be associated with the record and that an accurate copy be retained and accessible; VerifyDoc.ai attaches QR-backed verification, cryptographic hashing, a hosted issuer-controlled proof page, and a certificate of authenticity so the exact signed version stays provable for years — no login, no app for the recipient. That gives a counterparty, auditor, or court a fast, self-serve way to confirm the document matches the issuer's record. Explore the e-signatures product page and the pillar guide on verifying document authenticity to see how this fits a compliant signing workflow.
