DocuSign qualified electronic signature (QES)
What qualified electronic signatures mean under eIDAS, how DocuSign supports QES workflows, and when legal requires more than email-link signing.
Shaan F.
Co-founder & CEO, Atlas
On this page
Qualified electronic signature (QES) is the highest tier under EU eIDAS regulation. It requires an advanced signature created using a qualified certificate on a qualified signature creation device, backed by a qualified trust service provider.
DocuSign offers QES-capable workflows in EU contexts through partnerships and specific product configurations. Your US Standard plan email link is not automatically QES.
> Share: "QES is a regulatory tier, not a marketing badge you get by turning on a setting."
QES vs advanced vs simple
| Tier | eIDAS label | Typical proof strength |
|---|---|---|
| SES | Simple | Clickwrap, basic mark |
| AES | Advanced | Identity-linked, tamper evidence |
| QES | Qualified | AES plus qualified cert on QSCD |
National law dictates when QES is mandatory versus when AES suffices.
DocuSign QES workflow shape
Signers may:
- Use EU trust service identity methods
- Complete qualified certificate issuance steps
- Sign with vendor-supported QSCD integration
UX is heavier than US email signing. Plan longer completion times and help desk scripts.
Read DocuSign eIDAS for regional context and /docs/integrations/qes-eidas for Atlas notes.
Procurement questions
Ask DocuSign written confirmation:
- Which trust service provider backs QES in your country?
- Where are qualified certificates stored?
- What audit artifact proves QES for each envelope?
- Data residency for qualified sessions?
US deals vs EU mandates
US ESIGN commercial contracts rarely require QES. EU subsidiaries on the same group paper may. Multinationals sometimes split workflows by entity.
Do not assume one global template satisfies all regulators.
When QES is overkill
Internal US HR acknowledgments, low-value SaaS MSAs between US entities, and many B2B commercial contracts operate on advanced or simple tiers without QES.
Over-engineering increases abandonment.
Atlas positioning
Teams with hard QES mandates must validate Atlas against legal requirements before replacing DocuSign QES SKUs. Commercial API signing from Atlas follows review-first patterns suitable for many US and general commercial use cases, not automatic QES equivalence.
Signer experience planning
QES flows take longer. Set signer expectations in cover email with time estimate and ID document requirements. Mobile-only signers may struggle; offer desktop alternative.
Store qualified audit artifacts with same retention as contract PDF for regulatory exams.
Operational checklist before you scale
Document the owner for template changes, integration credentials, and signer support escalation. Run a thirty-minute tabletop exercise: candidate cannot open link, finance needs certificate today, API returns 429 during launch. Write answers in internal wiki with envelope ID examples redacted.
Measure time-to-first-completed-envelope for new hires on ops team. If only one person knows admin console, bus factor is high. Export sandbox walkthrough recording when vendor UI updates each quarter.
For hybrid stacks, label outbound emails so signers know which brand hosts their session. Mixed DocuSign and Atlas emails confuse recipients and increase phishing reports to IT.
When migrating vendors, keep legacy read-only login until archive export finishes. Do not cancel production keys until webhook consumers handle new event schema in staging.
Review credit or envelope burn monthly against forecast. Spiky nonprofits and seasonal bulk sends surprise finance if unmonitored.
Train agents and support to request envelope ID first. Guessing from subject line wastes cycles.
Align legal retention on signed PDF plus audit artifacts with IT backup policy. Cloud vendor retention defaults may be shorter than regulatory need.
If signers routinely complete on mobile, test mobile browser on both iOS Safari and Android Chrome before policy mandates ID verification.
Publish internal SLA for signature turnaround separate from vendor uptime SLA. Business expectation management reduces escalations to engineering.
Schedule semiannual access review for admin accounts on signing platform. Former contractors with send permission are a common audit finding.
Legal should annotate contract repository with required signature tier per template ID. Sales must not pick template by habit alone.
FAQ
Does Atlas accept PDF and DOCX?
Yes. Upload either format when you create an envelope. DOCX files become PDF before anyone signs.
How do I sign in?
Use a Bearer API key from your dashboard settings. MCP connectors in ChatGPT and Claude use OAuth instead.
When do credits get used?
One credit per send, not per upload. You get five free sends when you sign up.
Where should I start?
/docs and API reference.