An e-invoice, or structured electronic invoice, is an XML file that accounting software can read and process without human intervention, while a PDF invoice sent by email is not an e-invoice. In Latvia, e-invoices have been mandatory in transactions with state and municipal institutions since 1 January 2025, and they will be mandatory in transactions between businesses from 1 January 2028. If you invoice a state or municipal institution, which the law calls a budget institution, then as of 1 January 2026 you must also submit the e-invoice data to the State Revenue Service (VID).
This guide covers the invoices that businesses issue to each other and to public institutions, whereas bank e-invoices, which people use to pay their utility bills automatically, are something else entirely.
What an e-invoice is and what it is not
The Accounting Law (Grāmatvedības likums) defines a structured electronic invoice as an invoice that is prepared, sent and received in a structured electronic format that allows it to be processed automatically. In practice, this is an XML file whose structure complies with the Latvian national standard LVS EN 16931-1:2017 and the PEPPOL BIS Billing 3.0 rules.
An invoice in Word, PDF, PNG or JPG format is not an e-invoice, and neither is a scanned document sent by email or fax. VID's guidelines state that a PDF or Word invoice does not meet the legal requirement even if it contains all the required details. Where the law requires an e-invoice, such an invoice is not a supporting document on which a payment can be based.
When you save an e-invoice in e-address (e-adrese), you get two files: the XML, which is the structured e-invoice, and a PDF that a person can read. Cabinet Regulations No. 877 require that an e-invoice can be displayed on screen in human-readable form and printed on paper.
Deadlines and who they apply to
If you read somewhere that e-invoices between businesses are mandatory as early as 2026, that information is out of date. On 5 June 2025, the Saeima adopted amendments to the Accounting Law that postponed this obligation to 1 January 2028, and the following deadlines now apply:
- From 1 January 2025, e-invoices are mandatory in transactions with state and municipal institutions. If the contract with a budget institution was concluded by 31 December 2024, e-invoices are mandatory from 1 January 2026 at the latest.
- From 1 January 2026, data on e-invoices issued to budget institutions must be submitted to VID. From the same date, businesses may also voluntarily submit to VID the e-invoices they issue to each other.
- From 1 January 2028, e-invoices are mandatory between all businesses registered in Latvia, and the data on these e-invoices must also be submitted to VID.
Until 1 January 2028, e-invoicing between businesses is voluntary. VID's guidelines give an example: if a limited liability company (SIA) issues another SIA an invoice for repair work in 2026, an e-invoice is not mandatory, but a self-employed person who invoices a municipality in the same year must prepare that invoice as an e-invoice.
Under the law, "business" means more than commercial companies: the obligation also applies to sole proprietors, associations and foundations, farms and fishing holdings, branches of foreign companies and self-employed persons, including those that are not registered for VAT. It does not apply to private individuals who are not engaged in business activity, and invoices to consumers, such as utility bills to apartment owners, can be issued the same way as before. An e-invoice must be issued for both goods and services, and it does not replace the delivery note.
You can check whether a buyer is a budget institution by looking up the buyer's registration number in the ISK search tool of the Central Statistical Bureau (CSP). According to VID's guidelines, the institution must have been assigned one of these institutional sector codes: S130110, S130120, S130150, S130160, S130170, S130310, S130320, S130340 or S130400. Special economic zones, as well as port and free port authorities, are not on this list.
How to issue and send an e-invoice
You can create an e-invoice in three ways: in the state e-address service on the Latvija.gov.lv portal, through an e-invoicing service provider, also called an operator, or in your own accounting software. The parties agree between themselves on the channel through which the e-invoice will reach the buyer: it can be e-address, an operator's channel, a system integration or ordinary email.
The e-address form works if you don't have many invoices, because every line is entered by hand. To use the form, you need an active e-address account and a qualified eID, and if you send the e-invoice to a state institution, a copy reaches VID automatically. However, legal entities that are not state institutions, for example two commercial companies, currently cannot send each other an e-invoice or any other message through e-address.
If your business partner doesn't have an e-address account, you can create the invoice in e-address, download it and send it by email, but then you upload the XML file to the VID Electronic Declaration System (EDS) yourself. The same applies if you email an e-invoice from your own accounting software: you submit the data to VID yourself, either by uploading the XML file to EDS or by using VID's e-invoice API.
VID recommends checking the XML file in the European Commission's e-invoice validator before you send it. It is best to round unit prices to whole numbers or two decimal places, because under the PEPPOL rules, line amounts are rounded to two decimal places.
An e-invoice that has been issued cannot be deleted: you correct a mistake with a credit note that states the number of the invoice being corrected, and the credit note must also be a structured e-invoice.
Submitting e-invoices to VID within five business days
E-invoice data must be submitted to VID once and no later than five business days after the day the e-invoice was sent. The days are counted from the next business day, so an invoice sent on 1 June 2026 must be submitted to VID by 8 June 2026.
If you send the e-invoice to an e-address, the e-address system passes it on to VID automatically. The data also reaches VID automatically if you use an operator whose channel is integrated with VID, or software connected to the EDS API. In all other cases, the XML file is uploaded to EDS by hand, one invoice at a time, and only a person with signing rights or an authorized person may do this.
VID scans every file with antivirus software and checks that it complies with the Schematron rules and the XSD schema. Rejected invoices, together with a description of the errors, can be seen in the EDS sections "Izsniegtie noraidītie" (Issued rejected) and "Saņemtie noraidītie" (Received rejected), and if a rejected invoice has already been posted, it is canceled with a credit note and a new invoice is issued.
If you miss the five-business-day deadline, what you do depends on the reason:
- if a failure in your system or your operator's system is to blame, you must notify VID of the delay and its reason through EDS by the next business day after the deadline, and submit the e-invoice within three business days after the failure has been fixed;
- if the failure is in VID's system, you must submit the e-invoice by the next business day after VID has fixed the failure;
- in other cases, you must notify VID of the reason for and period of the delay through EDS, and submit the e-invoice within 30 calendar days of the time the reason was identified.
PEPPOL BIS Billing 3.0 in plain language
PEPPOL BIS Billing 3.0 is a specification that sets out exactly how an e-invoice under the European standard EN 16931 must be filled in, and it is maintained by the organization OpenPeppol AISBL. An invoice prepared according to this specification also complies with EN 16931, and VID requires e-invoices in Latvia to comply with this specification in particular.
Technically, an e-invoice is a UBL 2.1 XML file: a regular invoice is a UBL Invoice, and a credit note is a UBL CreditNote with type code 381. Every file contains the specification identifier CustomizationID with the value urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0.
Latvia has not added national rules of its own to the EN 16931 standard, VAT does not have to be reported in real time, and you do not have to issue e-invoices to consumers.
How ABCD ERP prepares e-invoices
The ABCD ERP Invoicing module creates a PEPPOL BIS Billing 3.0 e-invoice, a UBL XML file, from a closed sales invoice or credit note. Before the file can be downloaded or sent, the system checks that it complies with the Latvija.gov.lv field limits and Latvian rules, the UBL 2.1 schema, EN 16931 and the PEPPOL Schematron rules. If there are errors, the file cannot be downloaded or sent, and the system lists what needs to be fixed.
You can download the finished XML, send it to the customer as an email attachment straight from the system, or retrieve it through the public API, which is part of the ABCD ERP core. You submit the data to VID yourself, for example by uploading the XML file to EDS.
If you also send the customer the invoice as a PDF or in an email, you can add a payment link and a QR code to it: the customer pays the invoice online, and once it is paid, the invoice shows as paid in the Invoicing module.
Frequently asked questions
When do e-invoices become mandatory between businesses?
From 1 January 2028, e-invoices are mandatory between all businesses registered in Latvia, while in transactions with state and municipal institutions, an e-invoice has been mandatory since 1 January 2025.
Do you have to issue an e-invoice to a foreign customer?
No, an e-invoice is not mandatory for a foreign customer, but you can use one if the parties agree to it. For intra-EU transactions, mandatory e-invoicing and near real-time reporting are planned from 1 July 2030.
Does a prepayment invoice have to be issued as an e-invoice?
Not always: if you send a prepayment invoice to potential customers for marketing purposes, an e-invoice is not mandatory. A final invoice is not needed if the prepayment invoice between businesses was issued as an e-invoice and paid in full, and if the delivery is confirmed by another document that refers to the full payment.
Do e-invoices fill in the VAT return automatically?
No, e-invoices change neither the requirements for a VAT invoice nor the procedure for submitting the VAT return. You can prefill the PVN 1-I and PVN 1-III sections in EDS with VAT e-invoice data by clicking the "Ielasīt e-rēķinu datus" (Import e-invoice data) button, but this is optional.
How long must e-invoices be kept?
The retention rules do not change: supporting documents are kept for as long as they are needed to trace the transaction, but for at least five years.
If you want to see how ABCD ERP creates and validates a PEPPOL e-invoice from your own invoice, request a free trial: you can use the Invoicing module free of charge for a month.
Sources
- VID: E-invoices
- VID: frequently asked questions about e-invoices
- The Accounting Law (likumi.lv)
- Cabinet Regulations No. 749 on the exchange of e-invoices and submission of data to VID (likumi.lv)
- State Digital Development Agency (VDAA): E-invoices in e-address
- Peppol BIS Billing 3.0 specification (OpenPeppol)