| Scope boundary | eIDAS says an electronic signature cannot be denied legal effect solely because it is electronic, and gives qualified electronic signatures equivalent legal effect to handwritten signatures. | ESIGN covers any transaction in or affecting interstate or foreign commerce: a signature, contract, or record may not be denied legal effect solely because it is electronic. UETA is the parallel uniform state-law model (Uniform Law Commission, 1999) that most states have enacted for state-law transactions. There is no separate qualified tier. | Do not stop at generic electronic validity when the EU transaction requires a qualified electronic signature. |
|---|
| Covered actors | eIDAS qualified signatures depend on qualified certificates, qualified trust service providers, and validation data tied to the signing time. | ESIGN and UETA are technology-neutral: they validate electronic signatures and records without requiring any certificate, accredited provider, or trusted list. ESIGN even bars a state from according greater legal effect to a specific technology, so there is no federal registry of qualified providers equivalent to an eIDAS QTSP. | Keep certificate-chain, QTSP, and validation evidence separate from ordinary signer-authentication logs. |
|---|
| Trigger | Escalate when a flow claims qualified electronic signature status, uses qualified certificates, depends on a QTSP, serves EU public-sector processes, or needs EU cross-border recognition. | Apply ESIGN/UETA analysis when the flow is governed by U.S. law: in particular, when a law requires written information to a consumer, ESIGN only treats the electronic record as satisfying that requirement if the consumer has affirmatively consented and received the required disclosures. Also flag attribution, retention, and admissibility questions. | Assign separate EU trust-service and U.S. e-signature legal owners before launch. |
|---|
| Core obligations | A qualified electronic signature based on a qualified certificate issued in one EU Member State is recognised as a qualified electronic signature in other Member States. | The U.S. uses a federal-floor-plus-state-enactment model, not cross-border qualified-certificate recognition. ESIGN sets the federal baseline, and a state law can modify or supersede it only by enacting UETA as approved by the Uniform Law Commission in 1999 or by adopting consistent technology-neutral alternatives that reference ESIGN. | Use eIDAS recognition evidence for EU Member State questions and a separate U.S. source record for ESIGN/UETA questions. |
|---|
| Evidence record | eIDAS validation should preserve the signing certificate, certificate validity status at signing, QTSP evidence, validation policy, and validation result. | Under ESIGN, a retention requirement is met by an electronic record that accurately reflects the information and remains accessible for later reference; for consumer disclosures, keep proof of affirmative consent and the required hardware/software statement. No certificate-status or trusted-list evidence is required. | A reusable evidence bundle needs labels showing which records prove eIDAS qualified status and which records support U.S. transaction review. |
|---|
| Timing and deadlines | For eIDAS, record the signing time, certificate validity period, and the status of the qualified certificate at that same time, because validation must confirm the certificate was valid at signing. | ESIGN took effect on October 1, 2000 (with limited delayed dates for record-retention rules and certain loans). It sets no signing-time certificate-validity test like eIDAS; U.S. timing questions concern the transaction and the applicable U.S. law, not certificate status at the moment of signing. | Do not reuse a final approval decision if the certificate status at signing has not also been captured. |
|---|
| Enforcement | An eIDAS qualified signature must pass validation against the EU rule set, including certificate status, QTSP status, and the signed-data integrity checks. | ESIGN and UETA impose no validation procedure to pass. An electronic signature is enforceable under the same contract-law rules as a paper one, subject to the consumer-consent conditions and the statutory exceptions; disputes turn on attribution, intent, and consent rather than certificate or QTSP status. | Do not map a U.S. evidence trail directly onto EU qualified-signature validation without separate eIDAS checks. |
|---|
| Overlap and reuse | Shared artifacts like timestamps, certificate chains, and validation logs can support eIDAS checks, but only if they are tied to the right signing time and trust-service status. | A shared audit trail or timestamp can support a U.S. ESIGN/UETA enforceability argument (intent, attribution, retention) even though it does nothing to establish eIDAS qualified status; the same artifact answers different legal questions on each side. | Reuse the same evidence only when the report labels which rule set each artifact supports. |
|---|
| Practical decision rule | If the flow must prove EU qualified-signature status, require the qualified certificate, QTSP, trusted-list, signing-time, and validation-result record set. If the flow only needs basic EU electronic-signature legal effect, the simpler eIDAS evidence path may be enough. | If the transaction is governed by U.S. law, ESIGN and the governing state's UETA enactment already make an ordinary electronic signature valid, with no qualified certificate or trusted list needed. Check the ESIGN consumer-consent rules where written disclosures are required, and confirm the matter is not in an excepted category such as wills, family law, most of the UCC, court documents, or certain notices. | Start with the jurisdiction and the legal effect the transaction must achieve, then collect only the evidence that proves that rule set. |
|---|