A client questions an invoice. Says they never saw the engagement letter. Says whatever you sent them doesn't match what they agreed to.

Most firm owners have imagined that scenario at least once. The anxiety behind it is real: if a client pushed back hard enough, would an e-signature hold up?

The short answer is yes, with conditions. Under federal law and the laws of all 50 states, electronic signatures carry the same legal weight as ink on paper when the process meets specific requirements. The law is not ambiguous on this. Vendor marketing aside, courts and regulators have upheld this framework for over two decades.

The rest of this post walks through exactly what those requirements are, what gets challenged in a dispute, and what your engagement letter workflow needs to have in place before that moment arrives.

‍Key takeaways

  • Electronic signatures are legally binding in the US for engagement letters under the ESIGN Act and UETA, which together cover all 50 states and treat e-signatures as legally equivalent to ink signatures when four specific requirements are met.
  • The audit trail matters more than the signature image. In a dispute, a court asks for the timestamped activity log showing when the document was opened, who accessed it, and from which IP address. Not the signature graphic itself.
  • Most e-signature failures are execution problems, not legal ones. Skipping the consent disclosure, using a platform with no identity verification, and fragmenting the audit trail across multiple tools are the gaps that make a valid signature indefensible.

What makes an electronic signature legally binding?

An electronic signature is legally binding in the United States when it meets the requirements of the ESIGN Act (15 U.S.C. 7001, enacted 2000) and the Uniform Electronic Transactions Act (UETA, 1999). Both laws establish that neither party can deny legal effect to a signature solely because it is in electronic form. The signer must intend to sign, consent to transact electronically, and the signature must be attributable to them and tied to a record retained for future reference.

The ESIGN Act applies nationwide, governing interstate and foreign commerce. UETA operates as its state-level counterpart: 49 states plus the District of Columbia, Puerto Rico, and the US Virgin Islands have adopted it. New York is the only holdout. It uses its own Electronic Signatures and Records Act (ESRA), which reaches the same legal outcome for most commercial transactions.

Together, these two frameworks cover the agreements US accounting and bookkeeping firms encounter every day, including engagement letters, service agreements, and payment authorizations. A client who signed electronically last month has bound themselves to the same extent as if they had signed in ink at your desk. The question is not whether e-signatures work. The question is whether your process can prove it when the moment arrives.

What are the legal requirements for a valid electronic signature?

Four requirements establish whether an electronic signature is valid under ESIGN and UETA: intent to sign, consent to transact electronically, association of the signature with the specific document and signer, and the ability to retain and reproduce the record. Satisfying all four is what separates a defensible agreement from one that falls apart the moment a client disputes it.

Intent to sign

Intent to sign means the signer took an affirmative action to execute the agreement. Clicking "I agree," typing a name into a signature field, or drawing a signature on a touchscreen all satisfy the requirement. What does not satisfy it: a client forwarding your email without completing the signing step, or someone accessing a document link and closing it without acting.

For engagement letters, a signing mechanism that requires a deliberate final action is essential. Ambiguity about whether someone signed or merely viewed creates exactly the dispute you are trying to prevent.

Consent to do business electronically

Consent means the parties agreed to conduct the transaction electronically. Under ESIGN specifically, this requires a disclosure many firms skip entirely: the signer must be told they have the right to receive the document on paper instead, and the right to withdraw electronic consent later.

Skipping the disclosure does not automatically void the signature. But if a client later claims they never agreed to electronic delivery, the absence of documented consent gives them a foothold they otherwise would not have. A platform that embeds consent capture into the signing flow handles this automatically. A PDF attached to an email does not.

Association with the document and signer identity

The signature must link to the specific document version the signer reviewed and to the identity of the signer. A system that captures the signer's email address, IP address, and the document version at the moment of signing satisfies this. A typed name in the body of an email does not, because no verifiable link exists between the name and the document.

Ability to retain and reproduce the record

Both ESIGN and UETA require firms to retain electronic records in a form they can reproduce accurately for later reference. For engagement letters, the signed agreement must preserve the original content, the signature event, and the timestamp, and remain accessible for the duration of the relationship.

Firms that email signed PDFs and then delete the source record are building a gap they may not notice until they need it in a dispute.

What evidence and authentication does a valid e-signature require?

A valid e-signature is more than a signature image. The evidence behind it determines what happens when a client disputes the agreement. Two elements carry the most weight in a challenge: the audit trail attached to the signing event, and the authentication method used to verify the signer's identity before they executed the document.

Audit trail and record retention

The audit trail is what a court, an arbitrator, or a client's attorney asks for. Not the signature image itself. The log behind it.

A defensible audit trail records the timestamped IP address of the signer, the device used, the specific document version presented to them, and every action taken during the session: when the document was opened, when the signer viewed it, when they executed the signature, and when the process completed. If any of those data points are missing, the signature may still hold up legally, but the ability to prove it is compromised.

Firms using standalone PDF tools or bolted-on signing integrations often end up with fragmented audit trails. The signature exists. The surrounding evidence lives in a different system, or does not exist at all.

Signer authentication methods

Authentication confirms the person who signed is who they claim to be. Email-link verification, where the platform delivers a unique signing link to the signer's known email address, is the standard floor for engagement letters and satisfies the legal requirement. Worth noting the context: DocuSign's research found that 73% of employees have sent contracts via email, making email simultaneously the most common delivery channel for agreements and one of the most vulnerable to interception. A platform that generates a unique, expiring signing link tied to a specific signer's email address creates a meaningfully stronger evidentiary connection than a PDF attached to a message.

Higher-value engagements warrant stronger methods. Knowledge-based authentication, SMS verification, and ID verification add layers that matter for large advisory retainers, litigation support work, or any situation where the financial stakes of a disputed agreement are significant. ESIGN and UETA do not mandate a specific authentication method, but stronger authentication directly improves how defensible the signature is if challenged.

Which documents can and cannot be signed electronically?

Most business agreements qualify for electronic signatures under ESIGN and UETA, including engagement letters, service agreements, invoices, and payment authorizations. A narrow set of documents is explicitly excluded by statute, primarily estate planning instruments, family law documents, and specific consumer protection notices. Engagement letters are not on that list.

Documents you can sign electronically

For accounting and bookkeeping firms, the documents that matter are all within scope: engagement letters, service agreements, change orders, fee schedules, payment authorizations, and retainer agreements. These are standard commercial contracts, and ESIGN and UETA cover exactly this territory.

Billing authorizations, including ACH payment agreements, also qualify, particularly when the authorization forms part of a signed engagement agreement that establishes the ongoing billing relationship.

Documents electronic signatures cannot cover

ESIGN §7003 explicitly excludes the following:

  • Wills, codicils, and testamentary trusts
  • Documents governed by family law statutes, including adoption and divorce
  • Court orders and official court documents
  • Notices of cancellation of utility services
  • Notices of default, foreclosure, or eviction from a primary residence
  • Termination notices for health or life insurance policies
  • Product recall notices affecting health or safety

None of these come up in a standard bookkeeping or accounting engagement. The engagement letter itself is not on the list. Knowing the exclusions matters for two reasons: it closes the question for any client who asks, and it flags the documents that require a wet signature for firms that do estate planning work alongside their accounting services.

What should an accounting firm look for in an e-signature platform?

Three features separate e-signature platforms that satisfy the legal floor from the ones that actually protect a firm when it matters: whether signing is native to the agreement workflow or bolted on from a third-party tool, whether the platform generates a complete and accessible audit trail, and whether it supports multiple signatories for joint clients and partnership structures.

Native signing vs. a bolted-on third-party tool

Many practice management and proposal platforms add e-signature capability by embedding a DocuSign or Dropbox Sign integration. The arrangement creates a structural problem: the signed agreement lives in one system, the audit trail lives in another, and the billing trigger lives in a third. When a dispute arises, the evidence sits across tools with no shared data layer between them.

A platform where signing is native, where the agreement, the audit trail, and the payment authorization all live in the same system of record, produces a more defensible document and cuts the reconciliation work that fragmented tools create. The completion rate data supports this: DocuSign reports that 80% of e-signed agreements close in less than a day, and 44% in under 15 minutes. Purpose-built workflows, as opposed to PDF-and-email chains, account for most of that difference.

Compliance certifications and audit trail access

Platforms that cite ESIGN and UETA compliance are meeting a baseline, not clearing a high bar. What matters operationally is whether the platform can export a full audit trail on demand: timestamps, IP addresses, and the document version the signer reviewed. Two certifications worth checking are SOC 2 Type II, which reflects independently audited data security practices, and PCI DSS, which covers payment data handling for any firm collecting billing authorization at the point of signing.

On the cost side, DocuSign's published research puts the per-document savings at $4 to $10 when switching from paper-based processes. At the volume a mid-size accounting firm handles in a busy quarter, the operational case for a purpose-built platform is not difficult to make.

Multi-signatory and authorization controls

Engagement letters for partnerships, joint filers, or clients with multiple decision-makers often require more than one signature. A platform that supports multiple signatories per agreement, with a configurable routing order, handles these situations without requiring you to resend documents or manually track who has signed and who is still pending.

Relevant for any firm with a client base that includes partnerships, family businesses, or corporate entities where multiple stakeholders need to approve the engagement before work begins.

Common mistakes that weaken an e-signature's enforceability

The legal requirements for a binding e-signature are not complicated. Most failures happen in execution. Four gaps appear repeatedly in how accounting firms handle the signing process, and each one quietly reduces the defensibility of the signature without anyone realizing it until a dispute arrives.

Skipping the consent disclosure

ESIGN requires that signers receive a specific disclosure: they have the right to receive the document on paper, and the right to withdraw electronic consent later. Many firms send engagement letters by emailing a PDF with instructions to sign and return. The process may capture a signature but skips the formal consent disclosure entirely.

Skipping the disclosure does not automatically void the signature. But if a client claims they never agreed to electronic delivery, the absence of a documented disclosure gives them a position they would not otherwise have. The same underdocumented patterns that lead to scope creep disputes tend to surface here too: small process gaps that feel low-risk until a client decides to push back.

Not keeping a complete audit trail

A signature image is not a record. The record is the activity log: when the platform delivered the document, when the client opened it, when they executed the signature, from what IP address, on what device. Firms that save the signed PDF without the underlying activity log have the output of the signing event but not the evidence behind it.

If a client disputes a signature, the audit trail is what you present. The PDF alone is not enough.

Using a platform with no identity verification

Email-link verification is the minimum floor. A signing link delivered to the client's known email address creates a reasonable evidentiary connection between the signer and an email identity on file. Platforms that allow document access through a public link with no authentication remove that connection: anyone with the link could technically execute the document, which weakens the attribution argument the moment a client disputes the signature.

For retainers above a significant value, review whether the authentication method reflects the financial exposure on the agreement.

Trying to sign a document e-signatures cannot cover

The exclusion list under ESIGN §7003 is narrow, but it matters for firms that handle estate planning or documents adjacent to court proceedings. Using an e-signature on an excluded document does not automatically void it, but it introduces uncertainty that becomes expensive to resolve. For any firm preparing wills, testamentary trusts, or documents connected to adoption or divorce proceedings, confirm with counsel before relying on an electronic signature.

Why your engagement letter software should handle signing natively

Understanding the legal framework is step one. Step two is not having to trust that whatever tool sends your engagement letters actually implements it correctly.

When signing is native to the platform, the audit trail, the consent disclosure, and the signer identity all attach to the same record as the agreement. No reconstruction required across systems if a dispute arrives weeks or months later.

Anchor builds e-signature into the agreement and billing workflow as a native feature. When a client signs through Anchor, the signing event, the activity log, and the payment authorization all live in the same record. The firm does not need to cross-reference a signing certificate against a QuickBooks invoice to establish what happened and when.

One audit trail for the entire client relationship

Most e-signature tools produce a certificate for the original signing event. What they do not produce is a continuous record covering the full relationship.

Because agreements in Anchor stay live rather than converting into frozen PDFs, every scope or pricing amendment carries its own consent event and timestamp inside the same activity log as the original signature. For a three-year retainer client with two fee adjustments and a scope expansion along the way, the firm has a single, continuous record of every consent moment, with no folder of separate signed PDFs and email threads to reconstruct later.

For firms managing long-term client relationships, that continuity is what live agreements are built to provide.

Frequently asked questions

Is a typed name in an email a valid electronic signature in the US?

Yes, with a significant caveat. A typed name satisfies the intent-to-sign standard under ESIGN and UETA if context makes clear the sender intended it as a signature. The problem is evidence: a plain email has no audit trail linking the name to a specific document version, no authentication tying the action to the signer's identity, and no consent disclosure on record. The signature may be legally defensible in a narrow sense; the evidentiary record behind it is not. For engagement letters, a purpose-built signing process is worth the difference.

Do I need a qualified electronic signature for engagement letters?

No. Qualified electronic signatures are a European Union concept under the eIDAS Regulation, a tiered classification system with no equivalent in US law. Under ESIGN and UETA, the US framework does not classify e-signatures by qualification tier. A standard electronic signature with documented intent, consent, and a supporting audit trail is fully sufficient for engagement letters. For firms working with international clients on documents that may fall under EU jurisdiction, check with counsel before assuming US standards apply.

What happens if a client claims they never signed my engagement letter?

The defense is the audit trail. A timestamped record showing the platform delivered the document to the client's email, the client opened it, and the signer executed the signature from a specific IP address is the evidentiary foundation for contesting the claim. Without that record, the firm relies on the client's good faith, and that reliance is exactly the exposure a proper e-signature process is supposed to close. If the current tool cannot produce the full activity log on demand, plan on it not being available when it matters.

‍

Conclusion

Electronic signatures are legally binding in the US. The framework is settled, the statute is clear, and engagement letters fall cleanly within scope. Whether an e-signature protects the firm in a dispute comes down to process: whether the workflow captured consent, whether it verified signer identity, and whether the activity record is complete and accessible when needed.

The firms that end up in disputes over repudiated agreements are not usually the ones who picked the wrong tool. They are the ones who emailed a PDF, got a reply, and moved on without a defensible record behind it.

For firms that want to close that gap: Anchor's agreements page or get started here.

‍