Document signing and e-signatures in a compliance flow
Kord Team
E-signatures are fairly routine now, but what many don’t always understand is what makes one usable in a regulated context. There, a signature isn’t just evidence that someone agreed to something, but something linked to a specific, identifiable person.
This blog outlines the legal position on e-signatures in the UK, the different types recognised specifically for property transactions, and what a signature needs alongside it to pass muster in a compliance flow.
The legal position on e-signatures
Under the Electronic Communications Act 2000, an electronic signature is admissible as evidence of a document’s authenticity, as long as there’s clear intention to authenticate it. The Law Commission’s 2019 report on the electronic execution of documents confirmed that most documents, including deeds, can be validly signed electronically under existing law, without new legislation.
That’s the general position. Property transactions add a further layer, since HM Land Registry sets its own requirements for what it will accept.
The three types HM Land Registry recognises
HM Land Registry’s Practice Guide 82 sets out three categories of electronic signature it accepts for deeds and other documents, each with different requirements:
- Mercury signature: a scanned image of a wet-ink signature, added to an electronic document. It’s the simplest method, but it’s still a physical signature captured digitally, not a true electronic signature.
- Conveyancer-certified electronic signature, previously called a witnessed electronic signature: a genuinely electronic signature, applied through a signing platform, with the signatory witnessed in real time as they sign, and the process managed with two-factor authentication.
- Qualified electronic signature (QES): a cryptographically sealed signature, certified by a trusted service provider, offering a higher level of assurance than the other two. Its use in property transactions has so far been limited to pilot schemes.
Which type is appropriate depends on the document and the transaction. Not every deed needs the highest level of assurance, but using the wrong type for a given document can mean HM Land Registry rejects the application.
What makes an e-signature usable in a compliance flow
Capturing a signature is just the start.
The next step is to make it defensible if the transaction is ever questioned, and that demands a complete audit trail showing who signed, when, and how, evidence that the signing process itself wasn’t tampered with, and (if required) confirmation that witnessing took place correctly.
A signature platform that can’t produce this evidence on request hasn’t solved the compliance problem.
Where e-signatures fit alongside identity verification
Since a signature doesn’t independently confirm that the person signing is who they claim to be, firms can’t rely on it to prove something significant like an engagement letter establishing a client relationship or a deed transferring a property.
Pairing document signing with identity verification solves that problem. Rather than treating ‘get the client’s identity verified’ and ‘get the client’s signature’ as two separate steps handled by two separate tools, a single flow can confirm identity first, then bind the signature that follows to that same verified person.
Building this into one flow
Firms already running identity verification as part of onboarding gain little from a signing process that sits entirely apart from it, with no connection between the person verified at the start of a matter and the person who signs the documents later on.
Kord is built around connecting these steps: verified identity data carried through the matter, so that document execution isn’t a leap of faith at the end of the process.