Paris Court of Appeal, 9 April 2026: an electronic signature is only as strong as its evidence file

On 9 April 2026, the Paris Court of Appeal handed down a decision that will likely fly under the radar of mainstream press, but deserves the attention of anyone who contracts electronically. The judges upheld a contract signed by electronic means, not because of the signature itself, but because the party relying on it produced a complete contractual bundle: contract reference, associated technical elements, consolidated evidence file.

The signal is clear. In litigation, an electronic signature on its own, especially in its simple or advanced form, does not carry the day. It is the bundle of technical and documentary evidence that tilts the case. For lawyers, in-house counsel and SMB executives who rely on electronic signatures every day, this decision is a reminder of a discipline that often slips: the signature is just a brick.

What the Court of Appeal actually held

The decision (Paris Court of Appeal, 9 April 2026, accessible via the courdecassation.fr search engine) addresses a commercial dispute where the validity of an electronically signed contract was contested. The defendant raised doubts about the signer's identity, the document's integrity, and the reliability of the process used.

The court ultimately validates the contract, but the reasoning is what matters. The judges do not simply note the presence of an electronic signature. They examine:

• the contract reference and its consistency with pre-contractual exchanges,
• the technical elements produced around the signature: logs, timestamps, technical identifiers,
• the documentary chain surrounding the act: emails, work orders, related invoices.

In other words, the proof comes from the whole, not from the signature in isolation. This approach is consistent with a longstanding principle of French law: judges weigh a bundle of indicia, and each piece reinforces the probative value of the others.

Why the signature alone falls short

An electronic signature is, by construction, a technical object: a certificate, a cryptographic computation, a log entry. For that object to carry probative weight in litigation, the judge needs to answer several questions:

1. Who signed? Is the signer's identity plausibly established?
2. What was signed? Is the document produced today the one that was actually signed at the time?
3. When did it happen? Is the signing date verifiable?
4. How did it happen? Does the technical process offer sufficient guarantees?

For a qualified signature under eIDAS, Article 1367 of the French Civil Code creates a presumption of reliability: the burden of proof is reversed. The challenger must prove failure. For a simple or advanced signature, no such presumption exists: the party relying on the signature must actively build its file.

This is exactly what the Paris ruling reiterates. Without a consolidated file, a simple or advanced signature leaves the judge facing a black box. With a complete file, the signature regains its probative force.

The bundle-of-evidence concept applied to digital records

The bundle of indicia is a classical mechanism in evidence law. The judge does not decide on a single piece, but appraises a coherent whole. Applied to an electronically signed contract, this bundle typically includes:

No single piece is sufficient. But their convergence makes a challenge difficult to credibly mount. Lawyers call this a converging presumption: several concordant indicia together amount to proof, absent contrary evidence.

What this means for non-qualified timestamps

This is where the Paris ruling resonates beyond the topic of signatures. The same logic applies to non-qualified electronic timestamps.

Article 41(1) of the eIDAS Regulation mirrors Article 25 on signatures: an electronic timestamp cannot be denied legal effect solely because it is not qualified. But its actual probative weight likewise depends on the file that surrounds it.

A standalone timestamp, presented in isolation before a judge, says little: "this file existed on this date." That is already useful, but it is limited. Combined with:

• the metadata of the file (author, application, version),
• the production chain (earlier drafts also timestamped, exchanges about the project),
• the contractual context (order, delivery, invoice),
• the technical traceability (application logs, exports),

it becomes a central piece of a coherent demonstration. The logic is the same as for signatures: the cryptographic brick gains its real value through what it reinforces.

What it proves, what it does not

In practice, a strong evidence file around an electronically signed contract combines:

• the signature certificate itself, with its level (simple, advanced, qualified)
• a provider attestation detailing the technical process
• the timestamp of the operation, ideally from an independent service
• the event logs retracing the signing session
• the identification elements of the signer (authentication journey, ID copy where applicable)
• the pre-contractual exchanges documenting the parties' intent
• subsequent contract performance (proofs of execution, payments, deliveries)

The more this file is constituted before any litigation and properly archived, the more solid the defence becomes when a challenge eventually arises.

Practical recommendations for in-house counsel

A few simple reflexes that change the picture:

1. 1
   Systematically keep the full contractual bundle

   Signed contract, certificate, provider attestation, logs: one file per contract, properly archived.
2. 2
   Document the pre-contractual context

   Emails, work orders, accepted quotes. These pieces tell the story of intent and reinforce the file's coherence.
3. 3
   Timestamp key versions of documents

   Negotiated drafts deserve a timestamp before signing. This proves that the signed version corresponds to the outcome of the negotiation.
4. 4
   Periodically review your provider's attestations

   A qualified eIDAS provider publishes its service practices. In litigation, you may need to produce these documents.
5. 5
   Match the signature level to the risk

   For high-stakes contracts, aim for a qualified signature. For day-to-day contracts, a well-documented advanced signature is enough in practice.

Where LegalStamp fits in

LegalStamp is not an electronic signature service. It is a non-qualified timestamping service that computes the SHA-256 hash of a file in your browser (the file never leaves your machine) and anchors that hash on the Bitcoin blockchain via OpenTimestamps.

How does this connect with the logic of the Paris ruling? The LegalStamp timestamp adds to your evidence file at two key moments:

• Before signing: timestamping negotiated versions of a contract freezes intermediate drafts. If the signed version differs from the last timestamped version, there is a trace.
• Around performance: timestamping deliverables, reports and attestations reinforces the evidentiary chain of contract performance.

LegalStamp is a non-qualified timestamping service under eIDAS. This means it does not benefit from the presumption of reliability reserved for qualified trust service providers (QTSPs). However, Article 41(1) of the eIDAS Regulation prohibits denying legal effect to this timestamp solely because it is not qualified. Combined with your contractual bundle, your signing logs and your pre-contractual exchanges, it is one more probative brick added to the bundle.

This is exactly the logic of the 9 April 2026 ruling: no single element does it all, but each strengthens the others.

Conclusion

The Paris Court of Appeal ruling of 9 April 2026 does not create new law. It restates a discipline: in litigation, an electronic signature is worth what its file is worth. The same logic applies to non-qualified timestamps, and more broadly to any digital evidence. Building a consolidated evidence file proactively, before any dispute arises, is a modest investment that radically changes the position when challenge comes.

For legal teams structuring their contractual processes, the reflex to engrave is simple: never lean on a single technical piece. Always build a bundle, document it, and keep it.

FAQ

Disclaimer: this article is provided for informational and educational purposes only. It does not constitute legal advice. For a concrete case (validity of a signature in litigation, structuring an evidence file, choice of signature level), have your approach validated by a lawyer specialised in digital law or contract law.