Which documents still need special handling?

Wills in England and Wales must still meet the Wills Act 1837 formalities. Deeds need witnessing where required, and HM Land Registry accepts witnessed electronic signatures only under its own conditions. Some regulated or overseas documents have specific requirements. Check each document type.

What is the difference between simple, advanced and qualified electronic signatures?

UK eIDAS defines them. A simple electronic signature is any electronic data used to sign, such as a typed name or click. An advanced signature is uniquely linked to and capable of identifying the signer and detects later changes. A qualified signature uses a qualified certificate and device. Most business contracts use simple or advanced signatures.

What evidence should we keep?

The signed document, a hash or tamper seal, and an audit trail showing who signed, how they were authenticated, timestamps, IP or device data and the sequence of events. Store them together with your record.

Should we build our own e-signature?

Usually not. Integrate an established provider's API, which handles signing ceremonies, authentication, tamper sealing and audit certificates, and focus your build on the workflow around it.

Web Development4 min read

Electronic Signature Integration for UK Business Applications: Workflows, Evidence and Auditability

How to integrate e-signatures into UK business software: the legal position in England and Wales, signature types, deeds, APIs, evidence and audit trails.

How should UK business software integrate electronic signatures?

Integrate an established e-signature provider's API: generate the document from your application, define signers, order and authentication, send it, listen for webhooks, then store the completed document and audit certificate against your record. In England and Wales, electronic signatures can execute most documents, including deeds, if the signer intends to authenticate and formalities such as witnessing are met. Wills and some registrations have their own rules, and Scotland and Northern Ireland differ.

This guide is for product and engineering teams adding signing to contracts, onboarding, lettings, HR or approvals. It is general information as at October 2026, not legal advice.

Key takeaways

Check the legal requirements for each document type, especially deeds and wills.
Choose signer authentication proportionate to risk.
Keep the signed document and audit trail together.
Drive status from webhooks, with reconciliation.
Build the workflow; buy the signing.

The legal position in brief

Topic	Position (England and Wales)
General validity	Electronic signatures can execute documents if there is intention to authenticate and formalities are met (Law Commission, 2019)
Legal basis	Electronic Communications Act 2000, UK eIDAS and case law
Deeds	Witnessing still required where the law requires it; HM Land Registry has accepted witnessed electronic signatures since 27 July 2020 under its conditions, including the witness being physically present (HMLR)
Wills	Outside scope; Wills Act 1837 formalities apply
Scotland and Northern Ireland	Separate rules; take local advice

Integration workflow

Generate the document from a template with merged data; lock content before sending.
Define signers, roles, signing order and fields.
Authenticate signers proportionately: email link, SMS one-time passcode, or identity verification for higher risk.
Send through the provider API, storing the envelope ID against your record.
Track status with webhooks (sent, viewed, signed, declined, expired) and a scheduled reconciliation.
Store the completed PDF and audit certificate in your system, with retention rules.
Trigger downstream steps, such as account activation or invoicing, only on completion.

Evidence and auditability

If a signature is challenged, you need to show who signed, how they were identified and that the document has not changed. Providers seal completed documents and issue audit certificates; keep them, plus your own record of who requested the signature and why. Log access to signed documents. See SaaS audit logging.

Hypothetical example: a lettings platform

This example is hypothetical. A lettings platform generates tenancy agreements from property and tenant data, sends them for signature to all tenants and the landlord in order, authenticates tenants by SMS passcode, and stores the signed agreement and audit certificate on the tenancy record. Deposits and move-in tasks are triggered only when the envelope is complete.

Common mistakes

Assuming every document can be signed the same way.
Storing only the PDF without the audit certificate.
Polling status instead of using webhooks, or webhooks without reconciliation.
Allowing edits after a document is sent.
Weak signer authentication for high-value agreements.

Sources

Law Commission: electronic execution of documents; HM Land Registry: electronic signatures in practice.

Accessed 10 October 2026. Nothing here is legal advice.

Conclusion

E-signature integration is mostly workflow and evidence: the right legal approach per document type, proportionate signer authentication, webhook-driven status and signed documents stored with their audit trails. For contract workflows, see contract lifecycle management software.

Adding signing to your application?

ZSpace Labs is a remote-first technology studio that works with clients globally on business workflows and integrations. If it would help to plan an e-signature integration, we are happy to talk it through.

Start a Project

FAQ

Common questions.

In England and Wales, the Law Commission concluded in 2019 that an electronic signature can be used to execute a document, including a deed, if the signer intends to authenticate it and any formalities, such as witnessing, are met. The government endorsed this in 2020. Scotland and Northern Ireland have their own rules.