Odoo and itsme announced on 30 September 2026 that qualified electronic signatures would be integrated directly into Odoo Sign. Available with Odoo 20, the feature is intended for documents requiring stronger identity assurance than a standard electronic signature, including contracts, regulated transactions, human resources documents and powers of attorney. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Odoo’s release notes state that users can request itsme qualified signatures in more than 30 European countries. Under the European Union’s eIDAS framework, qualified electronic signatures have the legal equivalence of handwritten signatures. (Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
What changes in Odoo 20
The qualified signing process is built into Odoo Sign rather than presented as a separate signing service. An organisation preparing a document in Odoo can request an itsme qualified signature as part of its signing workflow. Document preparation, signature requests and identity verification can therefore take place within the Odoo environment. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes)
Odoo’s documentation lists itsme as an advanced signer authentication option alongside SMS authentication and Aadhaar eSign. Their inclusion in the same application does not mean they are interchangeable. The appropriate method depends on the signer, jurisdiction and level of identity assurance required for the document. (Odoo 20.0 Docs: Productivity Sign)
The practical distinction is between collecting an electronic signature and selecting a method designed for a higher-assurance transaction. Odoo and itsme position the qualified option for workflows in which signer identity and the signature’s legal status are important. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
How the itsme signing flow works
The signing flow reuses an identity that itsme has already verified. Depending on the flow, authentication can involve NFC, facial recognition or a personal code. The qualified signature is combined with a certificate issued by a Qualified Trust Service Provider. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
A standard request to sign and an itsme qualified signature do not provide the same process. The qualified option adds verified identity and a qualified certificate to the transaction. These elements underpin the stated equivalence to a handwritten signature under eIDAS. (Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Implementation planning should extend beyond enabling the option in Odoo Sign. Organisations should identify which signers can use itsme, confirm availability in each relevant country and determine which documents require qualified signing. They should also test the full signer experience, including identity authentication and completion of the certificate-backed signature. (Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Where qualified signing may fit
The announced use cases include contracts, regulated transactions, human resources documents and powers of attorney. These examples point to documents for which an organisation needs greater confidence in the signer’s identity or must use a qualified signature. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Not every document in Odoo Sign will require this method. Organisations can separate workflows by document type, legal requirement and risk. Routine documents may use another available signing or authentication method, while designated documents can use itsme where the parties and jurisdiction support it. (Odoo 20.0 Docs: Productivity Sign; Odoo 20 Release Notes)
This distinction affects template and approval design. An organisation using one template in several countries should not assume that every recipient can complete the same itsme flow. The release notes describe availability across more than 30 European countries, but the supplied information does not establish identical coverage for every country, signer type or document category. (Odoo 20 Release Notes)
Considerations for Australian organisations
The legal equivalence described by Odoo and itsme is expressly connected to eIDAS. Australian organisations dealing with European employees, customers, suppliers or counterparties may find the feature relevant to those transactions. They should not, however, assume that an eIDAS-qualified signature satisfies every Australian legal, regulatory or evidentiary requirement. (Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
The supplied Odoo and itsme materials do not give the feature an Australian legal status equivalent to a handwritten signature. Before applying it to an Australian document, decision-makers should consider the document type, governing law, parties and applicable signing formalities. Technical availability does not by itself establish suitability for a transaction. (Odoo 20.0 Docs: Productivity Sign; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Cross-border processes may require more than one signing option. One party may be eligible to use itsme while another is not. Odoo Sign supports itsme, SMS and Aadhaar eSign as authentication choices, but the supplied sources do not establish that these methods have the same legal effect or availability. (Odoo 20.0 Docs: Productivity Sign)
What to verify before rollout
First, confirm the Odoo version used by the relevant environment. The qualified electronic signature integration is identified as an Odoo 20 capability, so teams should not assume that the same workflow exists in an earlier release. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes)
Second, verify country and signer eligibility. The release notes refer broadly to more than 30 European countries, but implementation should account for the specific countries and people involved. Confirm whether intended signers already have an itsme identity or can complete its verified identity process. (Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Third, map the required signature level to each document category. Contracts, regulated transactions, HR documents and powers of attorney are named use cases, but this list does not determine the requirement for an individual document. Internal procedures should state why qualified signing is needed, who can request it and what happens when a signer cannot use itsme. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Fourth, test the process from request to completion. Testing should cover itsme authentication, including any use of NFC, facial recognition or a personal code, and creation of the qualified signature using a Qualified Trust Service Provider certificate. Test cases should reflect the countries, signer profiles and document templates expected in production. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
Finally, define how administrators choose between itsme and Odoo Sign’s other documented authentication options. The selected method should reflect the document’s requirements rather than applying the highest-assurance option to every request. (Odoo 20.0 Docs: Productivity Sign)
Confirmed scope and open questions
Odoo 20 integrates itsme qualified electronic signatures into Odoo Sign and supports requests in more than 30 European countries. The signing process uses an already verified identity and a certificate from a Qualified Trust Service Provider. Odoo and itsme state that the resulting signature has the legal equivalence of a handwritten signature under eIDAS. (Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)
The supplied information does not provide a country-by-country eligibility list, establish the signature’s treatment under Australian law or determine which documents within an organisation require qualified signing. Those questions must be checked against the intended Odoo environment, signer population and legal requirements before rollout. (Odoo 20.0 Docs: Productivity Sign; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses; Odoo 20 Release Notes; Odoo And Itsme Partner To Bring Qualified Electronic Signatures To Businesses)