eIDAS and UK e-signatures: what businesses need

The terminology around UK and EU electronic signatures can feel needlessly bureaucratic. For a normal business contract, the useful question is simpler: what evidence do we need, and does any law or counterparty require a particular signature level?

The short answer

In the UK, electronic signatures can generally be used to execute documents, subject to the usual rules on form and any transaction-specific restrictions. eIDAS is the EU framework that defines simple, advanced and qualified electronic signatures. A simple electronic signature is often sufficient for ordinary contracts, but a company should check the governing law, execution formalities and whether the recipient has imposed a higher standard.

Before you start

Identify the governing law and the type of document before choosing a signing method. A straightforward services agreement is not the same as a deed, a land transaction or a regulated filing. Check who has authority to sign and whether witnessing is required. If the document crosses UK-EU borders, make the signature evidence intelligible to both parties rather than relying on unexplained product labels.

The practical rule is to separate the document from the evidence about the document. A visible name or squiggle is useful to a reader, but it is not the whole record. For an agreement that matters, keep the final PDF, the completed event log, the invitation address and the version that was sent. That small bit of housekeeping is much easier than rebuilding a timeline after a disagreement.

A reliable way to do it

For a standard contract, provide the final record through a secure e-signature flow, make the signer’s action clear and retain the completed PDF and audit trail. If you need an advanced or qualified signature, confirm the exact requirement with the receiving organisation and use an appropriate trust service. Do not assume that ‘eIDAS compliant’ is a complete answer without knowing which assurance level is meant.

• Use the final version of the document, not a draft with unresolved comments.
• Put signature, date and any required text fields beside the relevant clause.
• Send the link to the person whose email address you have already checked.
• Ask the signer to review the whole document before they complete the signature field.
• Save the completed PDF and its audit record together in the same matter or client folder.

That sequence is deliberately boring. Boring is good here. It makes it clear which version was offered, gives both sides the same finished copy and avoids the familiar mess of several attachments called ‘final final’. It also makes the process workable on a phone: the signer needs a browser and a clear link, not a new account or an app download.

What the options look like

A realistic example

A London consultancy signs a routine UK services agreement with a French client. The parties agree the governing law, use a browser-based signing flow and retain the same final PDF. For a later procurement submission, the French client asks for a qualified signature under its tender rules. The consultancy treats that as a separate requirement and obtains the required process rather than arguing that its ordinary contract workflow must be enough for every situation.

The useful measure is not how polished the process appears in a demo. It is whether a busy person can complete it without a call, a printer or a password reset. A straightforward signing flow removes the tiny reasons people put a document aside. It also leaves the sender with evidence that is readable by a human, not locked in a proprietary dashboard.

The mistakes worth avoiding

The trap is over-generalising. Saying that all electronic signatures are equivalent in every circumstance is inaccurate; saying that only qualified signatures are valid is also inaccurate for ordinary contracts. Another trap is ignoring deeds and witnessing. These can have special execution rules that a standard click-to-sign process may not satisfy without careful setup.

Do not treat this as legal advice for a particular transaction. Some documents have special form, witnessing, identity or jurisdictional requirements. In the US, ESIGN and UETA make electronic records and signatures generally valid, but they do not erase statutory exceptions. In Europe and the UK, a simple electronic signature can be valid, while a regulated use case may need a different assurance level. Check the document type before promising a counterparty that any method will do.

A contract may not be denied legal effect solely because an electronic signature was used in its formation. — ESIGN Act, 15 U.S.C. §7001

How to make the right call

For routine UK commercial agreements, a clear electronic signing process and audit trail are usually the practical starting point. Escalate when the document is a deed, the transaction is regulated, a public body has specified an assurance level, or the parties have unusual cross-border requirements. Good advice beats a generic compliance badge.

A good default is proportionate evidence. For an internal acknowledgement, a clear email and a saved PDF may be enough. For a client agreement, lease or confidentiality document, use a signing flow that records the email address, timestamps, IP address, user agent and a tamper-evident document hash. None of that makes a bad contract good; it does make a valid agreement easier to evidence.

Make the record useful next year

Once the document is complete, give it a name a colleague can understand without opening it. Include the party, document type and completion date, then store the signed PDF and certificate together with sensible access controls. Record where the unsigned source lives, but do not edit the completed copy. This is a small operational discipline, yet it is the difference between a settled record and a frantic search through old email when a renewal, invoice or dispute appears months later.

It is also worth telling the other party where their copy will arrive. People are more comfortable signing when they know they will be able to retrieve the final agreement afterwards. If an email is bounced, a signer says the details are wrong or a clause is under discussion, pause rather than trying to patch the live request. Void it, resolve the issue and send one clean final version. That preserves a record both sides can trust.

Finally, treat the signing request as part of the customer experience. Use the name people know you by, a specific subject line and a short explanation of why the document is arriving now. Check the request on both a laptop and a phone before a large send. If a recipient has accessibility needs, provide a workable alternative and make the document available in a form they can retain. Clear communication is not decorative: it helps establish informed action and stops a genuine request being mistaken for a phishing email.

Next step

If you have a PDF ready, try the workflow with one low-risk document first. Upload it, place the fields and send yourself a test link. You will see where the recipient hesitates before you ask a real customer, tenant or supplier to sign. InkRobin’s free plan covers five documents a month, so there is room to test the practical bits before changing a team process.