Electronic signatures in LatviaBuilt for business
in Latvia.

The Electronic Documents Law was adopted by the Saeima on 31 October 2002 and entered into force on 1 January 2003. Section 1(2) says a secure electronic signature is a qualified electronic signature within Article 3(12) of Regulation (EU) No 910/2014. Section 3(2) says an electronic document is considered signed by hand if it has a secure electronic signature.

Simple electronic signature on Essential and Pro · QES for Europe is an Enterprise option

Service agreement

Signed

Example

Completed with the evidence record

§ 3(2)Secure signature counts as signed by hand

Art. 25eIDAS qualified effect

1 Jan 2003Electronic Documents Law in force

PDF + recordDownload the evidence

One flow. A clear record.

Confidence from send to signed.

A clear signing path that records intent, each action, and the evidence behind the agreement.

  1. 01

    Prepare and send

    Upload the document, place the fields, and name every signer.

    See how it works
  2. 02

    Accept and sign

    Each signer accepts the electronic process and signs the fields you placed.

    See how it works
  3. 03

    Prove and keep

    Download the completed PDF together with its evidence record.

    See how it works

Everyday agreements

Document types you can sign with inSigner

Upload a PDF and keep the completion record with the file. Documents in public circulation under Section 3(5), and documents that other laws give another procedure under Section 3(6), are not on this list.

  • Sales

    1. Sales contracts
    2. Order forms
    3. Quotes
    4. Proposals
    5. Statements of work
    6. Master service agreements
    7. Change orders
    8. Renewal agreements
  • Customers

    1. Service agreements
    2. Onboarding packets
    3. Subscription agreements
    4. Acceptance forms
    5. Delivery receipts
    6. Project briefs
    7. Support agreements
    8. Customer addenda
  • Vendors

    1. Vendor agreements
    2. NDAs
    3. Purchase orders
    4. Consulting agreements
    5. Contractor agreements
    6. Supplier questionnaires
    7. Referral agreements
    8. Partnership agreements
  • People

    1. Offer letters
    2. Employment agreements
    3. Handbook acknowledgments
    4. Policy acknowledgments
    5. Commission plans
    6. Performance plans
    7. Equipment agreements
    8. Contractor packets
  • Property

    1. Letters of intent
    2. Offers
    3. Broker engagement letters
    4. Property management agreements
    5. Move-in checklists
    6. Maintenance addenda
    7. Parking agreements
    8. Work orders
  • Company

    1. Internal approvals
    2. Policy updates
    3. Meeting acknowledgments
    4. Access requests
    5. Travel approvals
    6. Expense approvals
    7. Confidentiality acknowledgments
    8. Project sign-offs

And many more.

Evidence, not just a signature

Every action leaves a clear record.

The completion record brings together who was invited, what they signed, and the hash of the final file.

Evidence record

Example
Status
Completed
Signers
The people you invited
Integrity
SHA-256 hash of the final file

If the file changes, the hash no longer matches. Download it with the PDF.

  1. 01

    Consent to sign

    The record keeps the acceptance of the electronic process.

  2. 02

    Signer attribution

    Name, email or phone, and the send, view, and sign events.

  3. 03

    Time-stamped events

    A chronological record from delivery to completion.

  4. 04

    Document integrity

    A SHA-256 hash shows whether the final file still matches.

Commercial agreements

One record. Many everyday documents.

The same completion record for commercial agreements that do not need the qualified signature this page describes.

  • Business

    Sales contracts

    Vendor agreements

    NDAs

  • Operations

    Proposals

    Orders

    Statements of work

  • People teams

    Offer letters

    Policy acknowledgments

  • More than one team

    The same flow

    In the languages you already use

Questions, answered

What teams in Latvia ask us.

The limits sit here, including the statute this page cites and the claims this page does not make.

Contact our team

What inSigner covers

The parts of an electronic signature flow in Latvia that the service offers today.

Are electronic signatures legal in Latvia?

The Electronic Documents Law was adopted by the Saeima on 31 October 2002 and entered into force on 1 January 2003. Section 1(2) says a secure electronic signature is a qualified electronic signature within Article 3(12) of Regulation (EU) No 910/2014. Section 3(2) says an electronic document is considered signed by hand if it has a secure electronic signature. A signature that is not a secure electronic signature does not, by itself, make the document signed by hand under the first sentence of Section 3(2).

What does the statute do?

The Electronic Documents Law was adopted by the Saeima on 31 October 2002, proclaimed in Riga on 20 November 2002, in force on 1 January 2003. Regulation (EU) No 910/2014 applies directly because Latvia is in the EU. An amending law of 11 May 2017, in force 22 May 2017, aligned definitions with the regulation. Section 1(2): a secure electronic signature is a qualified electronic signature within Article 3(12) of the regulation. Section 3(1): written form is fulfilled if an electronic document has an electronic signature and conforms to other laws and regulations. Section 3(2): the document is considered signed by hand if it has a secure electronic signature, or an electronic signature plus a written agreement to sign with one, drawn up and signed on paper or electronically with a secure electronic signature. Section 3(5): between state and local government institutions, or between them and natural or legal persons, it is considered signed with a secure electronic signature and a time stamp, or an electronic signature under that agreement. Section 3(6): the law applies insofar as other laws have not set other procedures. Article 25(2) gives a qualified electronic signature the equivalent legal effect of a handwritten signature. Without a secure electronic signature, the first sentence of Section 3(2) does not, by itself, treat the document as signed by hand. The Cabinet determines the supervisory institution. The standard inSigner signature is not a Latvian qualified certificate. QES for Europe is an Enterprise option, is not that certificate, and is not on Essential or Pro.

How does the record show who signed and what they signed?

Each person signs the fields you placed in the document you sent. The evidence record keeps their name and email address or phone number, when the document was sent, viewed, and signed, the IP address, the device details, and the authentication used.

Can I download evidence for a completed document?

Yes. You can download the completed PDF and the evidence record, including a SHA-256 hash of the final file. If a single byte changes, the hash no longer matches.

What inSigner does not cover

The limits, including the claims this page does not make.

Is the standard signature a qualified electronic signature?

No. Essential and Pro use an ordinary electronic signature. The first sentence of Section 3(2) treats a document as signed by hand when it has a secure electronic signature, and Article 25(2) reserves the equivalent effect of a handwritten signature for a qualified electronic signature. inSigner does not issue a Latvian qualified certificate on Essential or Pro. QES for Europe is an Enterprise option, priced separately. It is not a Latvian qualified certificate and it is not on Essential or Pro.

Can every document go through inSigner?

No. Section 3(5) covers circulation between state and local government institutions, or between those institutions and natural or legal persons, and it asks for a secure electronic signature and a time stamp, or for an electronic signature under the written agreement in Section 3(2). That written agreement is drawn up and signed on paper or electronically with a secure electronic signature. inSigner does not decide whether a document is in public circulation or whether the parties have that written agreement.

Does inSigner make our workflow GDPR compliant?

No.

Does inSigner cover clinical consent, account opening, or round-the-clock regulated workflows?

No. This page does not offer patient forms, clinical consent, account opening, or credit agreements as a regulated program. Identity checks such as KYC are add-ons priced separately, not the default. inSigner does not publish an uptime percentage or a public status page, and it does not decide the legal effect of a document.

This page is general information about electronic signatures in Latvia, not legal advice. The signature policy in the legal center is the binding text. Responsibilities for electronic signatures

Your next agreement in Latvia starts here

Send it. Sign it. Prove it.

Create an account and send a commercial agreement with its completion record.

Start signing free