“Can our ERP trigger a qualified electronic signature automatically?” — that’s the question CIOs and procurement managers have been asking with increasing frequency since eIDAS 2 came into force in 2024.
The short answer: yes, technically. The honest answer: it depends on your ERP, your chosen signature solution, and your ability to maintain the integration over time.
Regulation (EU) 2024/1183 — adopted on 11 April 2024 and published in the Official Journal on 30 April 2024 (EUR-Lex) — distinguishes three levels of electronic signature: simple (SES), advanced (AES), and qualified (QES). Only the QES is recognised as the legal equivalent of a handwritten signature across the European Union. This article does not revisit the regulatory mechanics (see our eIDAS 2 and ERP analysis for that) — it answers one operational question: which solution should you choose and how do you connect it to your existing ERP?
Five vendors compete for this market among European businesses: Yousign, DocuSign, itsme, Signaturit (the group that acquired Universign) and Adobe Acrobat Sign. Their native connectors, pricing models and geographical constraints differ considerably.
1. Why Your ERP Workflows Need a Qualified Signature
1.1 Four Use Cases That Justify QES
Qualified signatures are not always mandatory — but they become necessary whenever the legal value of a document must be beyond dispute in the event of litigation or audit.
Supplier contracts above €5,000. A purchase order “signed” via a simple checkbox in an ERP supplier portal does not constitute a QES. If the supplier challenges the commitment, you must prove that the signature genuinely bound their identity to the document. A QES ties the signer’s identity to the document through a certificate issued by an EU-accredited Qualified Trust Service Provider (QTSP) — and this proof is unassailable before any European court.
Multi-year purchase orders and firm commitments. As soon as a document creates obligations spanning multiple financial years, legal teams and external auditors require a signature whose evidentiary value cannot be challenged during an internal control review.
Sensitive payroll documents. Employment contract amendments, final settlement statements, and agreed termination agreements require a handwritten-equivalent signature. Dematerialising them with SES or AES exposes the organisation to risk in employment tribunal proceedings.
Procurement approvals in regulated sectors. Pharmaceutical, aerospace, Belgian and European public procurement: certain subcontracting or raw-material purchase documents explicitly require QES to be accepted by the relevant authorities.
1.2 What SES and AES No Longer Cover
Simple signatures (SES) — a “I agree” click in a supplier portal or a scanned signature image — offer minimal evidentiary value. Advanced signatures (AES) — the most common in document management software — bind the signature to an identity through a strong authentication process, but without a qualified certificate issued by an accredited QTSP.
AES is sufficient for the majority of routine B2B transactions. But for high-stakes contracts, legal teams at large organisations increasingly require QES — in anticipation of new eIDAS 2 obligations and to guard against challenges before courts.
2. QES Solution Comparison for ERP (2026)
The European electronic signature market is one of the fastest-growing B2B SaaS segments. It is driven by eIDAS 2 obligations, the digitalisation of procurement processes, and pressure from legal teams on ERP workflows. Here are the five main vendors for enterprise deployments.
| Criterion | Yousign | DocuSign | itsme | Signaturit (Universign) | Adobe Acrobat Sign |
|---|---|---|---|---|---|
| Max eIDAS level | QES (Enterprise) | QES | QES | QES | QES |
| Geographic scope | Europe | Global | Benelux | Europe | Global |
| REST API | Yes | Yes | Yes | Yes | Yes |
| Native SAP connector | No (API/iPaaS) | Yes (SAP Store) | No | No | Yes (SuccessFactors/BTP) |
| Native Dynamics 365 connector | No (API) | Yes (Power Automate) | No | No | Yes (native) |
| Odoo connector | Community module | Not native | Native (Odoo 20) | No | No |
| Indicative QES pricing | Enterprise (on request) | Enterprise (on request) | Included with bank account | ~€10/signature | On request |
| Data hosting | France | USA/EU | Belgium | France (Universign pole) | USA/EU |
2.1 Yousign: The Sovereign European Choice
Founded in 2013 and hosted on French soil, Yousign is today the most widely deployed French electronic signature solution among SMEs and mid-market companies. Its 2026 pricing starts at €9/month excl. VAT for limited use (10 signatures/month, 1 user) and €25/month excl. VAT for the Business plan (unlimited signatures, 5 users, API access). The REST API is available from the Business plan, starting at €106/month excl. VAT for high-volume integrations (source: Stackindep, 2026). Qualified signatures (QES) are reserved for the Enterprise plan, on request.
Advantages for European CIOs prioritising sovereignty. Data remains hosted in France, GDPR-compliant and outside the scope of the US Cloud Act. The REST API is well documented, with webhooks to synchronise signature status back into your ERP.
Main limitation. There is no certified native Yousign connector for SAP or Dynamics 365: integration must go through the Yousign REST API or an iPaaS tool (MuleSoft, Boomi, Make, n8n). For Odoo, an open-source community module developed by Akretion is available on Odoo Apps (GitHub Akretion), but it is not maintained by Yousign — evaluate its support level before any production deployment.
2.2 DocuSign: The Most Mature Ecosystem for SAP and Dynamics
DocuSign is the global leader in electronic signatures. For organisations running SAP S/4HANA or SAP Business One, it offers SAP Signature Management by DocuSign, available directly on the SAP Store (SAP Partner Finder): it integrates natively into SAP MM (procurement), SD (sales) and HR workflows without custom development. For Dynamics 365, the official Power Automate connector enables automated sending from CRM or Finance & Supply Chain without leaving the Microsoft environment (Microsoft Learn).
Advantages. Global coverage, the broadest ecosystem of native connectors on the market, QES available on Enterprise plans.
Limitations. Pricing is complex — per envelope, not per signature. Business plans start at around €15/month for 5 envelopes (personal use), but Enterprise plans with QES and SAP connectors involve bespoke contracts that frequently exceed €10,000/year for 50 users. Data hosting may be outside the EU on standard plans: verify the DPA before signing. And the term “lock-in” is not an exaggeration — migrating away from DocuSign on an integrated SAP deployment is expensive.
2.3 itsme: QES at No Extra Cost for the Benelux
itsme is a digital identity platform operated by a consortium of Belgian banks (Belfius, BNP Paribas Fortis, KBC, ING) and telecom operators. It claims 8 million active users across 32 European countries and processes 50 million actions per month (itsme press release, March 2026). Its distinctive feature: QES is included at no extra cost per signature — identity verification relies on the signer’s existing bank account, without a physical token or certificate to provision.
Since the partnership announced on 30 September 2026 with Odoo, itsme is available natively in Odoo 20 via the Odoo Sign module (Odoo blog, 30 September 2026).
The decisive advantage. For a Belgian or Dutch company, this is the most direct path to QES at zero marginal cost per signature — all internal signers and virtually all local suppliers already have the app installed.
Hard limit. Signers must have a Belgian or Dutch bank account with access to the itsme app. For suppliers outside the Benelux or international partners, a fallback mechanism (AES or SES) is essential — do not forget this in your Odoo Sign configuration.
2.4 Signaturit / Universign: The Franco-European Alternative with Transparent Pricing
Universign, the historic French qualified signature provider founded by Cryptolog, was acquired by the Signaturit group (Spain) in 2021 (Cambon Partners). In 2025–2026, the group made Universign its flagship brand for European expansion, to the point that universign.com now redirects to signaturit.com. Both solutions are converging onto a unified platform.
Published pricing is one of the rare cases in this market that explicitly lists the QES price: approximately €10 per signature, with volume packs available for high-volume enterprises (Signaturit pricing, 2026). Advanced signatures (AES) are priced at €2.50 per signature.
Advantage. French hosting for the Universign scope, transparent QES pricing — unlike DocuSign or Adobe, which always refer you to sales. A credible sovereign alternative.
Limitation. No native ERP connector — integration via REST API only.
2.5 Adobe Acrobat Sign: For Organisations Already on Adobe Licensing
If your organisation holds an Adobe Enterprise licence, Adobe Acrobat Sign may allow you to avoid a new vendor contract. It offers native connectors for SAP SuccessFactors (Adobe Help, August 2026 release notes) and Dynamics 365 (Adobe & Dynamics 365), with QES available on Enterprise plans via partner QTSPs. Pricing on request.
Its main weakness: hosting is predominantly in the United States (outside the specific EU Shield offering), which can create issues for contracts containing personal data.
3. Technical Integration by ERP
3.1 SAP S/4HANA
The recommended pattern is SAP Signature Management by DocuSign via the SAP Store. It integrates into MM (procurement), SD (sales) and HR modules via standard SAP workflows — without ABAP development. The typical flow for a supplier purchase order:
- The buyer approves the PO in SAP MM.
- The SAP workflow sends the PDF to the DocuSign server via SAP Signature Management.
- The supplier receives the DocuSign email and signs (SES, AES or QES depending on configuration).
- The signed document — with its proof file (.p7s) — is archived in the SAP DMS (OpenText or SAP Document Management) with a timestamp.
- The PO status is automatically updated in SAP.
For an alternative integration with Yousign or Signaturit (where data sovereignty takes priority), the pattern goes through SAP BTP Integration Suite with a custom REST connector — which implies an additional integration budget (typically €3,000 to €8,000 in professional services, depending on workflow complexity).
3.2 Dynamics 365 (Business Central and Finance & Supply Chain)
Microsoft has standardised on Power Automate + DocuSign as the primary path. The flow:
- A trigger in Dynamics 365 (quote creation, contract approval) launches a Power Automate flow.
- The flow generates the PDF from Dynamics and sends it via the official DocuSign connector.
- The signature status is returned via webhook and updated in the Dynamics record.
- The signed document is archived in SharePoint (linked to Dynamics via Dataverse).
A cost item often overlooked. The DocuSign connector for Power Automate requires a Power Automate Premium licence (approximately €15/user/month) in addition to the DocuSign licence — include this item in your TCO from the scoping phase.
For a Yousign integration on Dynamics 365, the pattern is similar (Yousign REST API + Power Automate Custom Connector), but requires a developer or integration partner for the initial configuration.
3.3 Sage X3 (and Sage 200/300)
Sage X3 has no certified connector with any QES signature solution on the market. Integration relies on a script triggered from the Procurement module, which calls the Yousign or Signaturit REST API via an HTTP call, then re-imports the signed document into the Sage X3 document tree on receipt of the confirmation webhook.
This type of integration requires development in Sage X3 Script Language (or L4G depending on the version) and maintenance whenever the signature solution updates its API.
Practical recommendation. Prefer Yousign or Signaturit/Universign for Sage X3: their REST APIs have stronger European integration community documentation, and the French hosting of signature proof files is consistent with the typical GDPR profile of Sage X3 customers (industrial and services mid-market).
3.4 Odoo 18 and 20
Odoo natively includes an Odoo Sign module covering SES and AES levels. To reach QES, options vary by version and geographic scope:
- Odoo 20, Benelux: the itsme integration is native from September 2026 — no development required, QES included for all signers with a Belgian or Dutch bank account.
- Odoo 18 or 20, rest of Europe: the Yousign community module (Akretion) is available on Odoo Apps and GitHub. It is not maintained directly by Yousign — evaluate compatibility with your Odoo version before production deployment.
- Any version, outside Benelux, without Yousign module: integration via REST API + Odoo webhook, to be developed bespoke or via an integration partner.
For organisations on Odoo 16 or 17 wanting native itsme access, an upgrade to Odoo 20 is required — verify your migration plan with your integrator.
4. Legal and Operational Considerations
Signature proof archiving. The evidentiary value of a QES does not rest solely on the moment of signing — it also depends on preserving the proof over time. The proof file (in .p7s format or LTA/LTV archive) must be retained for a minimum of 5 years, in line with standard commercial limitation periods across EU member states. Verify that your solution generates LTA (Long-Term Archiving) archives and that your ERP or DMS stores them in a non-alterable format.
Bilateral contracts: both parties must sign in QES. For a contract to fully benefit from handwritten equivalence on both sides, both parties must sign with a QES. A supplier who signs with AES while you sign with QES does not produce a “doubly qualified” contract.
Managing refusals and reminders. Build the scenario where the signer refuses or fails to respond within the deadline into your workflow design from the start. All solutions listed here offer webhooks to handle these events — do not overlook them during ERP integration. A signature workflow with no failure-case handling is an operational risk.
GDPR and Cloud Act compliance. For contracts containing personal data (employment contracts, NDAs that include natural persons’ data), hosting the signature proof outside the EU — with DocuSign on US servers without the EU offering, or with Adobe without Shield — may create a GDPR compliance issue in respect of data transfers. Verify your vendor’s Data Processing Agreements (DPA) before any deployment.
Which Solution for Your Profile?
There is no universal solution in this market. The choice depends on three variables: your ERP, your geographic footprint, and your tolerance for vendor lock-in.
- European SME or mid-market company on Sage X3 or Odoo, data sovereignty a priority: Yousign or Signaturit/Universign — European API, France-based hosting, webhook-based integration. Signaturit’s QES pricing is publicly listed (€10/signature).
- Large enterprise or group on SAP S/4HANA, requiring a certified native connector: DocuSign via SAP Signature Management (SAP Store) remains the most robust and lowest-maintenance path — at the cost of strong vendor commitment and Enterprise-level pricing.
- Benelux group on Odoo 20: native itsme, QES at no extra cost per signature, immediate deployment for signers with a local bank account.
- Organisation already on Adobe Enterprise licensing, with Dynamics 365 or SAP SuccessFactors: Adobe Acrobat Sign to consolidate supplier contracts.
To go deeper on the regulatory framework underpinning these choices, see our full eIDAS 2 and ERP analysis — practical impact on invoices, signatures and archiving. If you manage Odoo workflows in Belgium, our Odoo 20 + itsme guide: native QES in Odoo Sign walks through the deployment step by step.
