Skip to content

Did you know? “Mercury-compliant” signing under English law

A short explainer for anyone working on cross-border finance deals governed by English law.

If you have sat on a signing call with English counsel, you may have heard them insist that the documents be executed in a “Mercury-compliant” way. It sounds like jargon, but the idea behind it is simple — and worth knowing if you act on financing or other transactions under English law.

Where the name comes from

“Mercury” refers to an English case, R (Mercury Tax Group Ltd) v HMRC [2008] EWHC 2721 (Admin). In that matter, signature pages had been signed against one draft of a document and then lifted across and attached to a later, amended version. The court found that this had not validly executed the document — for a deed, the signature must belong to the final version.

The takeaway that stuck with the market: you cannot detach a floating signature page from a draft and staple it onto the final version. The signature has to be tied to the actual, final text that the party agreed to sign.

What the market did about it

In response, the Law Society of England and Wales issued practice guidance on executing documents by virtual means (2010, later supplemented for electronic signatures). It set out a handful of accepted protocols for signing when the parties are not sitting around the same table — which, in modern cross-border deals, is nearly always.

What “Mercury-compliant” looks like in practice

The most common approach on a virtual signing runs like this:

  1. The final, agreed version of the document is circulated to the signatories — typically as a PDF.
  2. Each signatory prints and signs the signature page.
  3. The signatory returns the signed signature page together with the final version it belongs to — usually combined into a single PDF — rather than a lone, free-floating page.

The point is traceability: anyone looking at the executed document should be able to see that the signature belongs to exactly that final text — not to an earlier draft.

Why this matters more for some documents than others

English law is particularly formal about deeds and certain instruments (for example those touching real property), where getting execution wrong can affect validity. That is why English counsel are careful to run the signing protocol past everyone before the closing, so there are no surprises when it is time to sign.

The important caveat

Mercury and the Law Society guidance are features of English law. They are not a statement of Swedish signing practice, and they are not the same thing as ordinary e-signature routines. As a starting point, Swedish law takes a more permissive approach to form: under the principle of freedom of form (formfrihet), a commercial contract is generally binding however — or whether — it is signed, so the concern is usually more evidentiary (which version was actually agreed?) than one of validity, the main exceptions being form-bound acts such as transfers of real property, where written form and signatures are required. That said, the underlying point may still be relevant in a Swedish-law context: a virtual or so-called PDF signing also raises practical questions about how to make sure that each signature is connected to the correct final version of the document. So if you meet a “must be Mercury-compliant” instruction, read it as an English-law formality to plan for in the deal — and as a useful reminder to think carefully about signing mechanics more generally.

This note is a general explainer and not legal advice. For a specific transaction, talk to your deal counsel about the right execution mechanics.

Whats Going on

July 9, 2026

Did you know? “Mercury-compliant” signing under English law

A short explainer for anyone working on cross-border finance deals governed by English law.

If you have sat on a signing call with...

February 27, 2026

Factoring in the context of existing financing structures

Factoring is often introduced into a company’s financing structure alongside traditional bank loans, bond terms and security ar...