{"id":29372,"date":"2026-09-13T07:00:01","date_gmt":"2026-09-13T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/latvia-e-invoicing-2026-rules\/"},"modified":"2026-09-13T07:00:01","modified_gmt":"2026-09-13T07:00:01","slug":"latvian-sahkoisen-laskutuksen-saannot-vuodelle-2026","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/latvian-sahkoisen-laskutuksen-saannot-vuodelle-2026\/","title":{"rendered":"Latvian verkkolaskutus 2026: Julkisyhteis\u00f6 vs. ulkomainen asiakas"},"content":{"rendered":"
\n
\n
\n

Which invoice needs XML in 2026?<\/h2>\n

If your Latvian company issues an invoice to a Latvian budget institution, a public-law body funded from the state or a local government budget, that invoice must be a structured e-invoice in XML format in 2026, and its data has to reach the Latvian tax authority VID<\/a> within five working days of sending, as set out in Cabinet Regulation No. 749<\/a>. If the invoice goes to a foreign commercial buyer, say an Estonian, Lithuanian or Finnish company, this domestic 2026 obligation does not apply to you. VID confirms that cross-border e-invoicing with foreign companies is currently planned to start from 2030<\/a>. Whether your invoice needs XML depends on the buyer’s legal status, not on whether the buyer generally operates in the public or private sector.<\/p>\n

Three dates you shouldn’t confuse: 2025, 2026 and 2028<\/h2>\n

Latvia’s e-invoicing reform moves in three separate stages, and these are exactly the dates that trip people up. The first deadline: from 1 January 2025<\/a>, a Latvian company issuing an invoice to a budget institution as the recipient of goods or services must issue a structured e-invoice. This isn’t limited to public procurement contracts; it applies to every transaction with that institution. The second deadline: from 1 January 2026<\/a>, the data from those invoices must also be sent to VID. The duty covers G2G, B2G and G2B transactions (government-to-government, business-to-government and government-to-business) between the state and Latvian companies. The third date is the general structured e-invoice mandate for domestic business-to-business (B2B) invoices: invoices to another company registered in Latvia. That was originally planned for 2026, but the Saeima, Latvia’s parliament, pushed it back to 1 January 2028<\/a>. Until that date, you can still send an ordinary PDF invoice to a regular Latvian business client, with no requirement that it be machine-readable XML.<\/p>\n

Budget institution: check the buyer’s status, not its name<\/h2>\n

The biggest practical mistake is assuming that anything “linked to the state” automatically triggers the e-invoice duty. Latvia’s Accounting Law places budget institutions, publicly derived legal entities partly funded from the state budget, and off-budget bodies under Latvia’s Law on Budget and Financial Management into this category, and these categories are spelled out in the law’s list of definitions<\/a>. That means a company merely owned by the state, such as a state capital company operating on commercial terms, doesn’t automatically fall into this group. It’s an ordinary company, and your invoice to it follows B2B logic, not B2G logic.<\/p>\n

Before drawing up an invoice, check two things: whether the buyer appears on the list of state or local government budget institutions, and whether it’s acting as the actual recipient of goods or services in your transaction rather than merely as an intermediary. On top of that, Latvia’s rules set no minimum invoice amount and no VAT-registration threshold for this duty<\/a>, so even a \u20ac15 invoice to a small municipal office has to be a structured e-invoice.<\/p>\n

How to send the invoice and notify VID: e-address, operator or API?<\/h2>\n

A structured e-invoice isn’t an email with a PDF attached. It’s an XML file that conforms to the UBL 2.1 standard and the PEPPOL BIS Billing 3.0 specification<\/a>, with UBL (Universal Business Language) as the common data structure and PEPPOL (Pan-European Public Procurement OnLine) as the shared EU network and rulebook for exchanging these files. For invoices to a Latvian state body, Cabinet Regulation No. 154<\/a> requires that a Latvia-registered supplier’s invoice meet the PEPPOL BIS Billing 3.0 specification specifically, on top of the general European standard. That’s the mandatory data format, but the same regulation allows several delivery channels: the official e-address (e-adrese, Latvia’s state digital mailbox), an email address published on the buyer’s website, or another channel agreed in the contract. The PEPPOL network itself isn’t the only route in.<\/p>\n

The general handling rules come from Cabinet Regulation No. 749<\/a>, in force since 13 December 2025. If you use the official e-address to exchange e-invoices, the system automatically forwards the invoice and its related data to VID from 1 January 2026, and you don’t have to do anything separately. If your company uses another channel agreed between the parties, such as a system integration or plain email, the company submits the e-invoice to VID through the EDS API or uploads the XML-format e-invoice directly into EDS<\/a>, EDS being VID’s Electronic Declaration System, its online filing portal.<\/p>\n

The five-working-day deadline: what to do if you miss it<\/h2>\n

Whatever the channel, one rule holds regardless: the e-invoice has to reach VID once, no later than five working days after the day it was sent<\/a>. If that window closes, what happens next depends on the reason.<\/p>\n

What if the error is an IT system failure?<\/h3>\n

If a system failure caused the delay, you or your operator must notify VID through EDS no later than the next working day<\/a> after the deadline passes, stating why the filing was missed, and then submit the invoice within three working days of the failure being fixed.<\/p>\n

What if the delay has another cause?<\/h3>\n

For any other cause, you similarly have to tell VID through EDS which period is affected and why the invoices weren’t filed, then submit them within 30 calendar days<\/a> of identifying the cause. Neither route cancels the obligation; it only pushes it back.<\/p>\n

Foreign buyer: what Latvia doesn’t require and what to check anyway<\/h2>\n

If your client is registered outside Latvia, in Estonia, Lithuania, Finland or elsewhere, a different logic applies today. Latvia’s domestic B2B structured e-invoice mandate explicitly covers invoices to another company registered in Latvia<\/a>, not cross-border transactions. VID says this directly: the 1 January 2026 rule applies only to companies, entrepreneurs and state or municipal institutions registered in Latvia<\/a>. The same logic runs both ways: if a foreign company invoices a Latvian state body, it doesn’t have to format that invoice in XML or file it with VID either.<\/p>\n

That doesn’t mean every rule disappears on a cross-border invoice. When you send an invoice to a Finnish or Estonian company, check three things separately: what the buyer’s home-country law requires, for example a local VAT invoicing rule; what your contract with the buyer requires, since some larger clients already want a PEPPOL-format invoice voluntarily; and what the buyer’s own accounting system expects. Latvia simply isn’t forcing this on you in 2026; for now it stays a commercial choice, not a legal duty.<\/p>\n\n\n\n\n\n\n\n\n\n
Feature<\/th>\nLatvian budget institution (2026)<\/th>\nForeign commercial buyer (2026)<\/th>\n<\/tr>\n<\/thead>\n
Structured e-invoice required<\/td>\nYes, from 1 Jan 2025<\/a><\/td>\nNo domestic mandate<\/td>\n<\/tr>\n
Data sent to VID<\/td>\nYes, from 1 Jan 2026<\/a><\/td>\nNot applicable<\/td>\n<\/tr>\n
Standard required<\/td>\nUBL 2.1 + PEPPOL BIS Billing 3.0<\/a><\/td>\nBy agreement, often still PDF<\/td>\n<\/tr>\n
Filing deadline<\/td>\n5 working days<\/a> after sending<\/td>\nNone<\/td>\n<\/tr>\n
When this could change<\/td>\nDomestic B2B mandate expands 1 Jan 2028<\/a><\/td>\nVID is weighing cross-border rollout from 2030<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Looking ahead to 2030: Latvia’s plan and the EU’s ViDA<\/h2>\n

Two separate things are converging on roughly the same period, and they shouldn’t get merged into one deadline in your head. First, this is Latvia’s own internal plan, not a rule already in force: VID’s guidance notes that mandatory e-invoicing with foreign companies is currently planned to start from 2030<\/a>, with more detail expected as that date approaches. Second, independent of Latvia’s own timeline, the EU’s VAT in the Digital Age (ViDA) package brings digital reporting requirements for cross-border B2B transactions into force from 1 July 2030<\/a> across the whole bloc. These rest on mandatory e-invoicing and hit every member state, Latvia included, at the same time.<\/p>\n

The practical takeaway for 2026: your invoices to Latvian budget institutions need XML and VID notification already, your invoices to Latvian business partners need it from 2028, and your cross-border invoices stay a matter of agreement for now. Latvia has currently pencilled in 2030 for mandatory e-invoicing with foreign companies, while the EU’s ViDA requirements for cross-border B2B transactions take effect, confirmed, on 1 July 2030.<\/p>\n

FAQ<\/h2>\n

Kas on 2026. aastal L\u00e4ti e-arve kohustuse erinevus bud\u017eetiasutuse ja v\u00e4lisostja vahel?<\/h3>\n

Alates 1. jaanuarist 2026 peab L\u00e4ti bud\u017eetiasutusele esitatav arve olema struktureeritud e-arve XML-vormingus ja andmed tuleb saata VID-ile viie t\u00f6\u00f6p\u00e4eva jooksul. V\u00e4lisriigi \u00e4rikliendile see kohustus ei laiene, sest piiri\u00fclene e-arvete k\u00e4ive on plaanis alles alates 2030. aastast.<\/p>\n

Millal kehtib 2026. aastal B2B e-arve kohustus L\u00e4tis?<\/h3>\n

L\u00e4ti-sisene B2B struktureeritud e-arve \u00fcldkohustus l\u00fckati edasi 1. jaanuarile 2028. Seega kuni 2028. aastani v\u00f5ib tavalisele L\u00e4ti \u00e4riettev\u00f5ttele saata PDF-arve ilma XML-vorminguta.<\/p>\n

Kuidas saata struktureeritud e-arve L\u00e4ti bud\u017eetiasutusele?<\/h3>\n

Arve peab vastama standardile UBL 2.1 ja PEPPOL BIS Billing 3.0. Edastamiseks v\u00f5ib kasutada ametlikku e-aadressi (e-adrese), ostja veebilehel avaldatud e-posti v\u00f5i lepingus kokkulepitud kanalit. Kui kasutatakse e-adrese\u2019i, saadab s\u00fcsteem andmed automaatselt VID-ile.<\/p>\n

Mis juhtub, kui e-arve esitamine VID-ile hilineb?<\/h3>\n

Kui viivitus on tingitud IT-s\u00fcsteemi rikkest, tuleb VID-i teavitada EDS-is hiljemalt j\u00e4rgmisel t\u00f6\u00f6p\u00e4eval ja esitada arve kolme t\u00f6\u00f6p\u00e4eva jooksul p\u00e4rast rikke k\u00f5rvaldamist. Muudel p\u00f5hjustel hilinemise korral tuleb arved esitada 30 kalendrip\u00e4eva jooksul p\u00e4rast p\u00f5hjuse tuvastamist.<\/p>\n