There’s a gap in most electronic signature tools that nobody talks about until it matters: legal enforceability. Click a button, draw your name with a mouse, and you’ve “signed” something. But would that hold up in court? Would it satisfy a regulator? Would the other party’s lawyers accept it for a high-value contract? Odoo Sign just answered those questions by introducing three distinct signature tiers under the European eIDAS framework — including Qualified Electronic Signatures, which carry the same legal force as ink on paper.
Three Tiers, Three Very Different Legal Realities
The eIDAS regulation — the EU’s framework for electronic identification and trust services — defines three levels of electronic signatures, and they are not interchangeable. Simple Electronic Signatures are the baseline: click-to-sign, draw your name, get an email confirmation. They’re legally valid for most everyday documents, but they don’t carry much evidentiary weight if someone disputes them.
Advanced Electronic Signatures, which are actually what Odoo has been providing by default, add identity verification layers: SMS code confirmation, unique signer links, tamper-evident seals that detect any modification after signing. These are strong enough for the vast majority of business contracts. Most companies never need anything more.
But some do. Real estate transactions, government procurement, financial services contracts, cross-border agreements where both parties need absolute certainty — these call for Qualified Electronic Signatures. Under eIDAS Article 25(2), a QES has the legal equivalent effect of a handwritten signature. That’s not marketing language; it’s regulatory text. And Odoo Sign now supports it.
How QES Works in Practice: The itsme® Connection
Qualified Electronic Signatures require a Qualified Trust Service Provider — a third party certified by an EU member state to verify identities and issue signing certificates. Odoo integrates with itsme®, the Belgian-born identity platform that has expanded across Europe, to provide this layer. When a signer uses itsme® for QES, the identity verification happens through a government-grade process that’s tied to their national ID.
The evidence chain is comprehensive: email and SMS validation, itsme® identity proof, timestamped IP and geolocation access logs, and cryptographic alteration-detection proofs. If someone later claims they didn’t sign a document, the system can produce a forensic trail that’s difficult to dispute. Non-repudiation, in legal terms.
Beyond Europe: ESIGN Act and UETA Coverage
The three-tier framework is European, but electronic signatures are a global requirement. In the United States, Odoo Sign operates under the ESIGN Act and the Uniform Electronic Transactions Act (UETA), which take a different but equally valid approach — broadly accepting electronic signatures as legally binding as long as all parties consent to conduct business electronically. The advanced-level signatures that Odoo provides by default satisfy these requirements comfortably.
The practical upside for multinational companies is that Odoo Sign now covers both regulatory ecosystems within a single tool. European operations can use QES for contracts that demand it, while US operations use the standard advanced tier. The same document workflow, the same audit trail, the same interface — just different levels of identity verification depending on what the jurisdiction requires.
When to Use Which Tier
Most businesses won’t need QES for daily operations. NDAs, vendor agreements, internal policies, employee onboarding documents — advanced signatures handle all of these with more than enough legal weight. QES becomes important for specific scenarios: cross-border real estate closings, regulated financial products, government contracts, or any situation where the other party’s legal team insists on the highest available standard.
The value of having all three tiers in one platform isn’t that you’ll use the top tier constantly. It’s that when you need it, you don’t need a different tool. The signing workflow stays familiar to everyone involved. The document management stays centralized. And the compliance conversation changes from “can our system even do this?” to “which level do we select for this document?” That’s a much better place to be.