Back to Signature by Country
Signature by Country4 min read

Lithuania Digital Signing: Legal Rules, QES Use Cases, and Signature Methods

TP
Toomas Pihl
Agrello
Lithuania Digital Signing: Legal Rules, QES Use Cases, and Signature Methods

Educational guide to Lithuania digital signing law: when QES is required or strongly recommended, when simpler signatures can work, and how local methods are used in practice.

This guide is educational and practical. It is not legal advice. For high-value or regulated transactions, confirm document-level requirements with legal counsel.

1) Core legal framework around digital signing

2) Documents and transactions that should be treated as QES-level

Use this practical rule: if a transaction must carry handwritten-equivalent legal weight in electronic form, choose QES-level signing.

In Lithuania, note that some transactions require a stricter notarial form, where QES alone is not sufficient:

Practical takeaway: for documents that need strong written-form/evidence posture, use QES-level methods; for transactions with mandatory notarisation, route through notarial workflow.

2.1) Practical acceptance reality in Lithuania

Beyond formal legal minimums, Lithuanian business and institutional acceptance is strongly tied to provider/method trust anchored in the Lithuanian Trusted List and RRT supervision. In practice, workflows based on trusted-list-qualified providers are easier to validate and accept.

Source: Trusted List of the Republic of Lithuania

3) Form-free and lower-formality documents where simpler methods can work

Where law does not impose stricter form requirements, parties may use simpler signature flows if risk tolerance and counterparty expectations allow it.

Typical examples:

  • routine internal approvals
  • low-risk acknowledgements
  • operational confirmations
  • early-stage commercial documents where parties do not require handwritten-equivalent certainty

Legal anchor: Civil Code of the Republic of Lithuania (Article 1.71).

4) Decision Matrix (Lithuania)

Document type / situation Recommended level Why
Statute or counterparty requires handwritten-equivalent legal certainty in electronic form QES Aligns with eIDAS Article 25(2) handwritten-equivalence principle.
Written-form transaction executed electronically (no stricter statutory process) QES (default safe choice) Supports stronger enforceability and evidence posture in disputes.
Transaction with mandatory notarial-form requirement Notarial workflow Civil Code imposes stricter form requirements beyond signature type alone.
Form-free, low-risk operational documents Simpler e-signature can be acceptable Civil law form rules generally allow flexibility where stricter form is not prescribed.

Signature Methods used in Lithuania

National eID-based qualified certificates

Lithuania distributes qualified e-signature certificates through nationally recognized providers, including the Migration Department under the Ministry of the Interior and the State Enterprise Centre of Registers.

Source: E-signature certificates (Lithuanian providers)

SIM/app-based qualified certificates (including Smart-ID distribution in Lithuania)

In Lithuania, qualified certificates from SK ID Solutions AS are distributed with Smart-ID and with SIM cards from major Lithuanian operators.

Source: E-signature certificates (providers and distribution)

Trusted-list-based provider validation

Qualified trust services are validated against the national trusted list maintained by RRT, which supports predictable cross-border and local verification under eIDAS trust-list rules.

Source: Trusted List of the Republic of Lithuania

Why non-standard methods face resistance in Lithuania

Organizations usually optimize for predictable legal outcomes and fast verification. If a signature path does not map clearly to trusted-list-qualified providers and known validation workflows, counterparties may escalate review or request re-signing through familiar channels.

Optional: simpler platform e-signatures for low-formality cases

For form-free, lower-risk workflows, simpler e-signatures may be operationally sufficient when parties agree and legal form requirements do not demand QES or notarisation.

This guide is for informational purposes and does not replace legal advice. Signature sufficiency depends on transaction type, sector regulation, counterparty requirements, and risk profile. Always verify document-specific requirements before execution.

Ready to get started?

Join Agrello and manage your contracts the smart way.