What are the ESIGN Act and UETA?
The ESIGN Act and UETA are the two laws that make electronic signatures legally binding across the United States. ESIGN is federal and applies to interstate commerce; UETA is a model state law that covers transactions inside each state. Read together, they mean a signed PDF holds up the same way a signed sheet of paper does.
The two were written within a year of each other and use nearly the same definitions, so you almost never have to choose between them. A signing process built to satisfy one satisfies the other. The practical question is not which law applies but whether your record proves what happened - and that comes down to the four requirements below.
What does the federal ESIGN Act do?
The Electronic Signatures in Global and National Commerce Act was signed on June 30, 2000 and codified at 15 U.S.C. 7001. Its core rule is one sentence long in effect: a signature, contract, or record may not be denied legal effect solely because it is in electronic form.
Because it is federal, ESIGN sets a nationwide floor that no state can drop below. It also adds a consumer-protection step that paper never required: before a business sends legally required disclosures electronically, the consumer has to consent to receive them that way and confirm they can access the format. That consent step is the part teams most often miss.
What does UETA add at the state level?
The Uniform Electronic Transactions Act was drafted in 1999 by the Uniform Law Commission and has since been adopted by 49 states, the District of Columbia, Puerto Rico, and the US Virgin Islands. New York is the lone holdout, and it reaches the same result through its own Electronic Signatures and Records Act.
UETA governs the intrastate transactions ESIGN does not reach and gives state courts a consistent rulebook. One detail worth knowing: both laws apply only when the parties have agreed to do business electronically. That agreement can be explicit or inferred from conduct, which is why a clear consent checkbox is good practice rather than a formality.
What are the four requirements for a valid e-signature?
Both laws turn on the same four elements. Miss one and the signature can be challenged; capture all four on the record and it is hard to dispute.
- Intent to sign. The signer takes a deliberate action - typing a name, drawing a mark, or clicking a clearly labeled button - that shows they meant to sign.
- Consent to do business electronically. Each party agrees to use electronic records, usually captured as an explicit, logged checkbox.
- Association with the record. The signature is logically and permanently tied to the exact document that was signed, not a copy that could be swapped later.
- Record retention. Every party can keep and reproduce the signed record in a form that stays accurate over time.
Document eSign captures all four automatically: the consent step is logged, the signature is bound to a tamper-evident PDF, and every party keeps a copy with a certificate of completion.
Which documents do ESIGN and UETA not cover?
A short list of high-stakes documents is carved out, where lawmakers decided a paper trail or in-person formality still matters:
- Wills, codicils, and testamentary trusts
- Court orders, notices, and official court filings
- Certain family-law matters such as adoption and divorce
- Statutory notices: utility shut-offs, insurance cancellation, eviction, and product recalls
Everything else most businesses sign every day - employment offers, NDAs, vendor and service agreements, sales orders, leases, and statements of work - is squarely covered.
How do you keep an electronically signed record defensible?
Legality and defensibility are different problems. ESIGN and UETA make the signature valid; what wins a dispute is evidence of who signed, when, from where, and how they were verified. That evidence lives in the audit trail, not the statute.
A strong record pairs a complete audit trail with a cryptographic seal so any later change is detectable. Document eSign stamps every completed document with a SHA-256 hash and a PAdES-B signature, then records each event - sent, viewed, signed - with its IP, device, and authentication method. For higher-value agreements you can require an emailed one-time passcode or a per-signer PIN before signing.
Frequently asked questions
When was the ESIGN Act passed?
The ESIGN Act was signed into federal law on June 30, 2000. It took effect on October 1, 2000, and has applied to electronic signatures in interstate and foreign commerce ever since.
What is the difference between ESIGN and UETA?
ESIGN is a single federal statute that applies nationwide to transactions in interstate commerce. UETA is a model act adopted state by state that governs intrastate transactions. They use almost identical definitions, so in practice a compliant signing flow satisfies both at once.
Does UETA apply in every US state?
UETA has been adopted by 49 states plus the District of Columbia, Puerto Rico, and the US Virgin Islands. New York is the exception; it relies on its own Electronic Signatures and Records Act, which reaches the same outcome.
Do ESIGN and UETA require a specific technology?
No. Both laws are technology-neutral. They do not mandate any particular signature method, encryption standard, or vendor. What matters is intent, consent, association with the record, and the ability to retain it.
Are there documents ESIGN and UETA do not cover?
Yes. Wills and testamentary trusts, court orders and filings, certain family-law documents, and statutory notices such as utility shut-offs or insurance cancellations are excluded. Most everyday business agreements are fully covered.