E-signatures for accounting and tax practices

Accounting firms sign constantly — engagement letters, management representation letters, consent to disclose, and the return authorisations that let a preparer file on a client's behalf. Most of it can be handled electronically. But tax return authorisation sits in its own category, because the tax authority has its own rules about how a taxpayer signs, and those rules are stricter than general contract law.

Comfortably electronic

• Engagement letters and scope agreements
• Management representation letters
• Consent and authorisation to disclose tax return information
• Power of attorney forms filed with the tax authority
• Advisory and planning agreements
• Fee arrangements and payment authorisations

These are ordinary contracts. ESIGN and UETA cover them, and internal controls around who may sign for the firm are an ordinary delegation question.

Tax return authorisation is the special case

The authorisation a taxpayer signs to permit electronic filing is not just a contract — it is the record that the taxpayer reviewed the return and authorised its submission to the tax authority. The authority publishes its own requirements for how that signature may be captured, and those requirements include identity verification of the signer.

The practical implication: an electronic signature on this form generally needs either a remote online notarisation, or a knowledge-based authentication step that verifies the signer against records, or an equivalent multi-factor identity proofing process. A platform that simply captures a typed name and a checkbox does not meet the standard for this document class, even though it is perfectly adequate for an engagement letter.

This is the single most common compliance mistake in paperless tax practice: generalising a workflow that is valid for contracts onto a form that has its own identity-verification rule.

Practical structure for a firm

1. Classify documents into three tiers: ordinary contracts, client information forms with sensitive data, and authority submissions with identity verification requirements.
2. Configure the identity-verified tier separately. It needs KBA or notarisation, and the evidence of that verification must be retained with the record.
3. Retain the exact version signed. Where a client signs a return authorisation, the record should show which return drafts and supporting statements were available to them at the time.
4. Handle withdrawals deliberately. A client may revoke an authorisation. Your system should record the revocation with the same fidelity as the original consent.
5. Export to the client file. Do not let the sole copy of a signed document live only inside a vendor's platform.

The seasonal load question

Tax practices are seasonal, and signature volume concentrates into a few weeks. Two things break under that load: templates that nobody maintained during the off-season, and support capacity. Test the full workflow — including the identity verification step and the client-side experience on a phone — before filing season starts, not during it.

What the audit trail needs to show

• Who signed, and the evidence of their identity verification
• What exactly was signed, by document version
• When it was signed, in a timestamp you can rely on
• Whether the document was subsequently altered
• How the completed record was retained and where