{"id":29316,"date":"2026-09-07T07:00:02","date_gmt":"2026-09-07T07:00:02","guid":{"rendered":"https:\/\/bilnex.io\/en\/latvia-b2b-e-invoicing-2026\/"},"modified":"2026-09-07T07:00:02","modified_gmt":"2026-09-07T07:00:02","slug":"latvian-yritysten-valinen-verkkolaskutus-2026","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/latvian-yritysten-valinen-verkkolaskutus-2026\/","title":{"rendered":"Latvian yritysten v\u00e4linen verkkolaskutus vuonna 2026: Mik\u00e4 on pakollista ja mik\u00e4 ei"},"content":{"rendered":"<article class=\"article-content-section article-content article-single\">\n<div class=\"container content-area\">\n<div class=\"text-content ce-answer\">\n<h2 id=\"is-b2b-e-invoicing-already-mandatory-in-latvia-in-2026\">Is B2B e-invoicing already mandatory in Latvia in 2026?<\/h2>\n<p>Picture an ordinary invoice: one Latvian limited-liability company (SIA) billing another SIA for a service or a shipment of goods. In 2026, that invoice still doesn&#8217;t have to take the form of a structured e-invoice, a machine-readable version of the invoice that accounting systems can process automatically, as opposed to a document meant for a person to read. The obligation to use one arrives later. Under the transitional provisions of the <a href=\"https:\/\/likumi.lv\/ta\/id\/324249-gramatvedibas-likums\">Accounting Law<\/a>, starting January 1, 2028, every company registered in Latvia that invoices another Latvian company will have to issue a structured e-invoice and, at the same time, submit that invoice&#8217;s data to the State Revenue Service (VID). That deadline was originally set for 2026, but an amendment that took effect on June 12, 2025 pushed it back two years.<\/p>\n<p>Invoices sent to budget institutions, meaning ministries, municipalities and similar public bodies, sit on a different timeline. E-invoicing there has been mandatory <a href=\"https:\/\/www.vid.gov.lv\/lv\/e-rekini\">since January 1, 2025<\/a>, and submitting that invoice data to VID became mandatory on January 1, 2026.<\/p>\n<p>This is where the confusion starts. People notice the January 2026 date attached to public-sector invoicing and assume it applies to everyone, concluding that &#8220;e-invoicing is already mandatory.&#8221; It isn&#8217;t, at least not for ordinary B2B trade. The <a href=\"https:\/\/likumi.lv\/ta\/id\/324249-gramatvedibas-likums\">Accounting Law<\/a> sets the B2B submission obligation to begin on January 1, 2028. It doesn&#8217;t explicitly describe what happens before that date, but the only reasonable reading is that in 2026 and 2027, submitting structured e-invoice data for B2B transactions is not yet a legal requirement.<\/p>\n<h2 id=\"how-do-you-check-whether-your-buyer-is-a-business-or-a-budge\">How do you check whether your buyer is a business or a budget institution?<\/h2>\n<p>Before deciding how to format an invoice, check who&#8217;s on the receiving end. If the buyer is a ministry, a municipality or another budget institution, a structured e-invoice is already the only form VID will accept. <a href=\"https:\/\/www.vid.gov.lv\/lv\/e-rekini\">VID explains<\/a> that &#8220;budget institution,&#8221; in the sense the Accounting Law uses it, covers budget-funded bodies, derived public entities that are partly financed from the state budget, and non-budget-funded institutions. You can check where a specific counterparty falls by looking up its registration number in the Central Statistical Bureau&#8217;s register. If your buyer is simply an SIA, an AS (joint-stock company) or a self-employed person, in other words a private business rather than part of the public administration, you can keep sending a plain PDF in 2026, and that&#8217;s entirely legal.<\/p>\n<h2 id=\"what-actually-counts-as-a-structured-e-invoice-in-latvia\">What actually counts as a structured e-invoice in Latvia?<\/h2>\n<p>A PDF attached to an email is a document meant for a person to read, not a structured e-invoice, no matter how well-formatted it looks. A system can&#8217;t process it automatically. A structured e-invoice, <a href=\"https:\/\/likumi.lv\/ta\/id\/324249-gramatvedibas-likums\">as the law defines it<\/a>, is instead prepared, sent and received as a machine-readable XML file (a text format built for software to read directly, rather than for a person) that complies with the European standard EN 16931. In practice, that means the XML file&#8217;s structure has to follow the <a href=\"https:\/\/likumi.lv\/ta\/id\/365040-kartiba-kada-organize-un-isteno-strukturetu-elektronisko-rekinu-apriti-un-kada-strukturetu-elektronisko-rekinu-datus-iesniedz-valsts-ienemumu-dienestam\">UBL 2.1 and PEPPOL BIS Billing 3.0<\/a> specifications, technical rule sets that define exactly which fields an invoice must contain and how they&#8217;re labeled. It&#8217;s the same format already running between government agencies. If your accounting software already has this export function, there&#8217;s nothing stopping you from switching it on for B2B invoices in 2026, even though no law requires it yet.<\/p>\n<h2 id=\"what-are-the-four-practical-ways-to-send-a-b2b-e-invoice-in-\">What are the four practical ways to send a B2B e-invoice in 2026?<\/h2>\n<p><a href=\"https:\/\/likumi.lv\/ta\/id\/365040-kartiba-kada-organize-un-isteno-strukturetu-elektronisko-rekinu-apriti-un-kada-strukturetu-elektronisko-rekinu-datus-iesniedz-valsts-ienemumu-dienestam\">Cabinet Regulation No. 749<\/a> sets out several delivery channels, and you can mix and match them:<\/p>\n<ul>\n<li><strong>The official electronic address (e-adrese)<\/strong>: a state-run digital mailbox account, if you&#8217;ve activated one, though for now this route is built primarily for exchanges with government bodies, not between two private companies.<\/li>\n<li><strong>An operator or PEPPOL channel<\/strong>: a service provider that delivers the XML file to the recipient and, in parallel, can pass it on to VID.<\/li>\n<li><strong>Any other mutually agreed channel<\/strong>: a direct integration between two accounting systems, or even plain email with an XML file attached, as long as both sides have agreed to it.<\/li>\n<li><strong>VID&#8217;s EDS portal<\/strong>: this isn&#8217;t a delivery channel to your customer at all. It&#8217;s a data-submission tool. <a href=\"https:\/\/www.vid.gov.lv\/lv\/e-rekini\">EDS only accepts an XML file<\/a>, not a PDF, and you&#8217;d use manual upload or its API only if you choose to submit e-invoice data to VID.<\/li>\n<\/ul>\n<h2 id=\"how-do-the-e-adrese-vid-and-the-five-business-day-rule-apply\">How do the e-adrese, VID and the five-business-day rule apply to B2B invoices?<\/h2>\n<p>The law doesn&#8217;t dictate which channel two companies use to exchange invoices between themselves. That&#8217;s something <a href=\"https:\/\/likumi.lv\/ta\/id\/365040-kartiba-kada-organize-un-isteno-strukturetu-elektronisko-rekinu-apriti-un-kada-strukturetu-elektronisko-rekinu-datus-iesniedz-valsts-ienemumu-dienestam\">businesses need to agree on directly<\/a>. Latvija.gov.lv&#8217;s e-adrese currently isn&#8217;t a universal B2B option, as <a href=\"https:\/\/www.vdaa.gov.lv\/lv\/e-rekini\">the State Data Protection Inspectorate (VDAA) notes<\/a>: legal entities which aren&#8217;t state institutions can&#8217;t use the e-adrese to communicate with each other. So two private companies can&#8217;t send invoices directly to one another through it. If B2B invoice data does end up reaching VID, voluntarily, since it isn&#8217;t required in 2026 or 2027, it happens either through an operator or through EDS, and one submission deadline applies either way: the e-invoice must reach VID no later than five business days after the day it was sent. If a system outage causes a delay, you need to notify EDS by the next business day at the latest, and then submit the invoice within three business days of the outage being resolved.<\/p>\n<h2 id=\"a-practical-2026-checklist-for-getting-ready-for-2028\">A practical 2026 checklist for getting ready for 2028<\/h2>\n<p>You don&#8217;t need to rebuild your whole invoicing process today, but starting a year before the deadline isn&#8217;t smart either. A sensible order of operations:<\/p>\n<ol>\n<li><strong>Ask your three to five biggest B2B customers<\/strong> which channel they&#8217;d want a structured e-invoice delivered through, if you sent them one.<\/li>\n<li><strong>Check whether your accounting software already exports XML<\/strong> in line with the EN 16931 standard and the PEPPOL BIS Billing 3.0 format.<\/li>\n<li><strong>Run one test send<\/strong> with a single business partner: better to find the bugs in 2026, when it&#8217;s optional, than in 2028, when it isn&#8217;t.<\/li>\n<li><strong>Only set up the VID data feed if both sides already use it.<\/strong> Otherwise it&#8217;s extra work with no payoff yet.<\/li>\n<li><strong>Keep a PDF preview available<\/strong> for clients and staff members who still rely on a human-readable invoice day to day. XML and PDF can run side by side.<\/li>\n<\/ol>\n<h2>FAQ<\/h2>\n<h3>Kas B2B e-arve on 2026. aastal L\u00e4tis kohustuslik?<\/h3>\n<p>2026. aastal ei ole B2B e-arve L\u00e4tis kohustuslik. Kohustus algab 2028. aasta 1. jaanuaril. Erandiks on budjetiasutused, kellele struktureeritud e-arve on juba kohustuslik alates 2025. aastast.<\/p>\n<h3>Kuidas kontrollida, kas ostja on B2B ettev\u00f5te v\u00f5i budjetiasutus?<\/h3>\n<p>Kontrollige ettev\u00f5tte staatust L\u00e4ti Keskstatistikaameti registris. Kui ostja on ministeerium, omavalitsus v\u00f5i muu budjetiasutus, peab e-arve olema struktureeritud. Kui ostja on SIA v\u00f5i FIE, kehtivad B2B reeglid.<\/p>\n<h3>Mis loetakse L\u00e4tis struktureeritud e-arvet?<\/h3>\n<p>Struktureeritud e-arve on masinloetav XML-fail, mis vastab EN 16931 standardile ja PEPPOL BIS Billing 3.0 spetsifikatsioonile. PDF-faili e-posti manuses ei loeta struktureeritud e-arvet.<\/p>\n<h3>Millised on neli v\u00f5imalust B2B e-arve saatmiseks 2026. aastal L\u00e4tis?<\/h3>\n<p>V\u00f5imalikud saatmiskanalid on: ametlik e-aadress (ei sobi kahe eraettev\u00f5tte vahel), operaatori v\u00f5i PEPPOLi kanal, muud vastastikku kokkulepitud kanalid (n\u00e4iteks e-post koos XML-failiga) ja VID EDS (andmete esitamise t\u00f6\u00f6riist, mitte kliendile saatmiseks).<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Kas B2B e-arve on 2026. aastal L\u00e4tis kohustuslik?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"2026. aastal ei ole B2B e-arve L\u00e4tis kohustuslik. Kohustus algab 2028. aasta 1. jaanuaril. Erandiks on budjetiasutused, kellele struktureeritud e-arve on juba kohustuslik alates 2025. aastast.\"}},{\"@type\":\"Question\",\"name\":\"Kuidas kontrollida, kas ostja on B2B ettev\u00f5te v\u00f5i budjetiasutus?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Kontrollige ettev\u00f5tte staatust L\u00e4ti Keskstatistikaameti registris. Kui ostja on ministeerium, omavalitsus v\u00f5i muu budjetiasutus, peab e-arve olema struktureeritud. Kui ostja on SIA v\u00f5i FIE, kehtivad B2B reeglid.\"}},{\"@type\":\"Question\",\"name\":\"Mis loetakse L\u00e4tis struktureeritud e-arvet?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Struktureeritud e-arve on masinloetav XML-fail, mis vastab EN 16931 standardile ja PEPPOL BIS Billing 3.0 spetsifikatsioonile. PDF-faili e-posti manuses ei loeta struktureeritud e-arvet.\"}},{\"@type\":\"Question\",\"name\":\"Millised on neli v\u00f5imalust B2B e-arve saatmiseks 2026. aastal L\u00e4tis?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"V\u00f5imalikud saatmiskanalid on: ametlik e-aadress (ei sobi kahe eraettev\u00f5tte vahel), operaatori v\u00f5i PEPPOLi kanal, muud vastastikku kokkulepitud kanalid (n\u00e4iteks e-post koos XML-failiga) ja VID EDS (andmete esitamise t\u00f6\u00f6riist, mitte kliendile saatmiseks).\"}}]}<\/script><\/p>\n<\/div>\n<\/div>\n<\/article>\n<style>.ce-answer{max-width:760px;margin:0 auto;padding:8px 20px 48px;line-height:1.65}.ce-answer h2{margin:1.5em 0 .55em;line-height:1.3}.ce-answer h3{margin:1.1em 0 .45em}.ce-answer p{margin:0 0 1em}.ce-answer ul,.ce-answer ol{margin:0 0 1em;padding-left:1.4em}.ce-answer li{margin:.25em 0}.ce-answer table{border-collapse:collapse;width:100%;margin:0 0 1.2em}.ce-answer th,.ce-answer td{border:1px solid #ddd;padding:8px 10px;text-align:left}.ce-answer blockquote{border-left:3px solid #ccc;margin:1em 0;padding:6px 14px}.ce-answer sup a{text-decoration:none}.ce-answer-title{margin:.6em 0 .4em}<\/style>\n","protected":false},"excerpt":{"rendered":"<p>Vuonna 2026 yritysten v\u00e4linen s\u00e4hk\u00f6inen laskutus on Latviassa edelleen vapaaehtoista. Pakollinen k\u00e4ytt\u00f6\u00f6notto astuu voimaan 1. tammikuuta 2028, vaikka vapaaehtoiset kokeilut kannattaa aloittaa jo nyt.<\/p>","protected":false},"author":8,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-29316","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages\/29316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/comments?post=29316"}],"version-history":[{"count":0,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages\/29316\/revisions"}],"wp:attachment":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/media?parent=29316"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}