
Is E-Signature Legally Valid in Germany? What eIDAS and the BGB Require (2026)
A practical 2026 guide to e-signatures in Germany: how the three eIDAS levels work, and where the BGB's Schriftform still forces a qualified signature.
A Hamburg-based scale-up is standardizing how it signs contracts. NDAs and SaaS orders are already going out through an e-signature tool, and the HR lead asks whether the same workflow can be used to send a termination letter to a departing employee. The template is ready, the manager has approved it, and someone is about to hit send — until legal asks an uncomfortable question: was that notice ever going to be valid?
German law has a rule most other e-signature jurisdictions do not: when the law requires the statutory written form — the Schriftform — only a qualified electronic signature can replace handwriting. An ordinary e-signature cannot.
The short answer in 2026 is that electronic signatures are legally valid and widely usable in Germany for the large majority of commercial contracts. The real question is which form the specific document requires. This is general information, not legal advice — for anything unusual, high-value, or termination-adjacent, involve German counsel before you sign.
What eIDAS and the BGB require
Two layers apply at the same time.
At EU level, the eIDAS Regulation (EU) No 910/2014 applies directly in every member state, including Germany. It is technology-neutral and deliberately does not create one uniform "electronic signature." Instead it distinguishes three levels:
- Simple Electronic Signature (SES). Any electronic data used to indicate consent: a typed name, a click-to-accept box, an email reply confirming agreement, a drawn signature on a tablet.
- Advanced Electronic Signature (AES). A signature uniquely linked to the signer, created under the signer's sole control, and linked to the document so that any later alteration can be detected.
- Qualified Electronic Signature (QES). An AES created with a qualified signature-creation device and backed by a certificate from a qualified trust service provider listed under the EU Trusted List. In practice this means certificate-based signing with a verified identity check — often via video identification, an electronic ID card (eID), or a bank identity service. A QES has the equivalent legal effect of a handwritten signature. At national level, the German Civil Code (BGB) decides which documents need which level. The key provision is § 126a BGB: wherever the law requires the statutory written form (Schriftform), that requirement is satisfied only by a document signed by the holder of the signature on every page with a qualified electronic signature. SES and AES do not close the gap. Where no form requirement applies at all, the principle of freedom of form applies and ordinary electronic signatures are perfectly fine.
Ordinary signature versus a "qualified" one
Most teams conflate "electronic signature" with "QES," leading to two opposite mistakes: over-engineering routine NDAs with certificate-based identity checks, or — much more dangerously — using a standard e-signature on a document that legally required a qualified one.
For the bulk of everyday business agreements, a standard commercial e-signature workflow (SES or AES territory) is sufficient:
- NDAs and confidentiality agreements
- Service, consulting, and SaaS agreements
- Purchase orders and supplier terms
- Most employment agreements at the moment of conclusion
- Internal policies, amendments, and board resolutions where the articles do not demand a stricter form
The things that make those signatures defensible are the same regardless of level: an invitation to a verified address, the complete final document presented before signing, an unambiguous signing action, timestamps of viewing and signing, and an integrity check proving the file did not change afterwards. If you are setting up such a workflow, our guide on how to send a contract for e-signature covers the mechanics.
A QES is only required when a specific legal provision says so — or when a counterparty, bank, or authority imposes it by contract or policy.
The Schriftform trap: where QES is mandatory
This is the section German businesses get wrong. The following situations are codified examples where the Schriftform applies and only a QES is acceptable:
- Termination notices in employment (Kündigung, § 623 BGB). A notice terminating an employment relationship must be in writing — email does not satisfy it, and neither does a standard e-signature. Only the employer's handwritten signature or a QES makes the termination effective. A notice that misses the form is void, and the employment relationship continues: exactly the scenario from the opening story.
- Consumer loan agreements (Verbraucherdarlehensvertrag, § 492 BGB). The statutory written form applies to the credit agreement; under eIDAS-linked provisions, a QES satisfies it, but an ordinary e-signature does not.
- Guarantee declarations (Bürgschaft, § 766 BGB). A private guarantee requires the written form. There is a narrow exception where the guarantor acts in the course of a commercial business, but relying on it without checking the facts is a common source of litigation.
- Real estate transactions. Purchase agreements for land, and the creation of a mortgage or land charge (Grundschuld), require a notarial deed (öffentliche Beurkundung by a Notar). An electronic signature cannot replace the notary.
One nuance: the written form under § 126 BGB can be waived in many private-law cases, but the waivers themselves have form rules, and moving back to a simpler form after a QES has been agreed is not automatic.
When you should expect something stronger
Outside the statutory list, ask before sending a document for e-signature in Germany:
- Is the document part of a regulated activity — consumer credit, insurance, payment services — where the regulator or the counterparty's compliance policy demands a certificate-based signature?
- Does the counterparty's bank, auditor, or procurement function require a QES or an audit-ready record as internal policy?
- Is the transaction value or dispute risk high enough that stronger identity assurance is worth the extra step even where the law would allow SES?
- Is the governing law actually German? A cross-border agreement may be governed by another law with different form rules — see how this plays out in our UAE e-signature guide or the Thailand guide.
If the answer to any is yes, use the process the recipient actually requires rather than assuming a standard e-signature will be accepted.
What still needs a notary or in-person process
Some transactions sit entirely outside what an e-signature platform can complete, even with a QES:
- Land purchases and mortgages. The notarial deed is mandatory; the notary reports the transfer to the land registry.
- Certain corporate formalities. GmbH articles of association and GmbH share transfers require notarial deeds, though incorporation through the online procedure (Video- oder Onlinebeurkundung) has become available under the Certificate Act, using qualified electronic means.
- Wills and inheritance contracts. Testamentary dispositions follow their own BGB form rules and generally require a notary.
- Family-law declarations such as certain name declarations and marital property agreements.
For everything else — the day-to-day contracts that make up most business volume — electronic signing is fully usable.
GDPR: the part businesses forget
Every e-signature audit trail contains personal data: names, email addresses, IP addresses, timestamps, sometimes identity-verification records. The GDPR, read together with the German Federal Data Protection Act (BDSG), applies to all of it. Four questions should have clear answers before you roll out a signing tool:
- What personal data is collected during signing, and on what legal basis?
- How long is the data retained, and where is it hosted?
- Who can access the signed document and its audit trail?
- Are signers informed about the processing?
A platform that cannot answer these clearly is a compliance gap independent of whether the signature itself is legally valid.
Building a signing record that holds up
The right standard: build the record you would want to show a court or auditor a year from now, not just the one needed to close the deal today. For a routine contract, keep the final signed document, the audit trail, the signer's verified contact details, and the platform's integrity check together — and classify each document type as "SES/AES" or "QES required" before sending. AiDocX keeps the document, the signing workflow, and the audit trail in one place and lets teams route a document to the right signature level, so a German business never has to reconstruct what happened from scattered email threads.
Common mistakes
Sending a termination notice with a standard e-signature. § 623 BGB requires the written form; only a QES satisfies it electronically. The most expensive mistake on this list, because a void termination restarts the employment relationship. Assuming every contract needs a QES. Most do not. Certificate-based signing on a routine NDA just adds friction, cost, and drop-off for both sides.
Treating notarization as a platform feature. Land purchases and GmbH share transfers need a Notar. No e-signature tool, however qualified, replaces that step.
Ignoring the GDPR side of the audit trail. Valid signature, invalid data processing — both can be true at once.
A simple decision checklist
Use a standard e-signature (SES/AES) for routine commercial agreements with no statutory form requirement: NDAs, service contracts, supplier terms, most employment agreements at conclusion — provided both parties accept electronic contracting and the platform produces a clear audit trail.
Use a QES when a specific statute requires the Schriftform — termination notices, consumer loan agreements, private guarantees — or when a bank, regulator, or counterparty contractually requires a certificate-based signature.
Use a notary or in-person process for real estate transactions, GmbH formations and share transfers, wills, and anything a German authority tells you requires public certification.
This is general information, not legal advice. For anything unusual, high-value, or government-facing, confirm the requirement with German counsel before you sign. For the routine contracts that make up most of a business's document volume, eIDAS and the BGB give electronic signing a solid legal foundation — the discipline is knowing which of the three levels a document sits on.
Ready to automate your documents with AI?
Start free with AiDocX — AI contract drafting, meeting minutes, consultation notes, e-signatures, and more in one platform.
Get Started FreeMore from AiDocX Blog
AI Purchase Order Tracking System (2026): Auto-Generate POs and Never Lose an Approval Again
What an AI purchase order tracking system actually does: auto-generate POs from a description, route approvals, and track every PO from draft to delivery — without spreadsheets.
Better Than Pandadoc? 7 Reasons Teams Switch in 2026 (+ Migration Checklist)
Searching for something better than Pandadoc? The 7 most common reasons teams switch — pricing, tracking, AI drafting — plus a same-day migration checklist.
ContractPodAi Alternative (2026): What Startups and SMEs Should Use Instead
Looking for a ContractPodAi alternative? Compare AI contract creation, e-signature, pricing transparency, and onboarding time — plus a step-by-step migration checklist.