{"id":29436,"date":"2026-09-17T11:00:01","date_gmt":"2026-09-17T11:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/"},"modified":"2026-09-17T11:00:07","modified_gmt":"2026-09-17T11:00:07","slug":"tiessaistes-norekinu-adrese-peppol-id","status":"publish","type":"page","link":"https:\/\/bilnex.io\/lv\/tiessaistes-norekinu-adrese-peppol-id\/","title":{"rendered":"Verkkolaskuosite vai Peppol ID: k\u0101da ir at\u0161\u0137ir\u012bba?"},"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=\"in-short-the-address-the-network-and-the-operator-are-three-\">In short: the address, the network and the operator are three separate things<\/h2>\n<p>No, a verkkolaskuosoite and a Peppol-tunnus are not the same thing, even though the numbers look almost identical. A verkkolaskuosoite, meaning Finland&#8217;s domestic e-invoice address, is normally an OVT code, and it only works together with a v\u00e4litt\u00e4j\u00e4tunnus, the identifier of the recipient&#8217;s operator or bank. A Peppol-tunnus is that same OVT code with Finland&#8217;s scheme identifier 0216 in front of it. The State Treasury, which acts as the Finnish Peppol authority, makes the difference obvious with its own example: <a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\">the domestic address is 003702454401 and the Peppol address is 0216:003702454401<\/a>. So here&#8217;s the working rule. If your customer gives you two fields, an address and an intermediary code, send down the domestic route. If they give you one code with a colon in it, send via Peppol. Don&#8217;t derive one from the other.<\/p>\n<div class=\"ce-key-facts\">\n<p class=\"ce-key-facts-title\"><strong>Key facts<\/strong><\/p>\n<table class=\"ce-key-facts-table\">\n<thead>\n<tr>\n<th>Fact<\/th>\n<th>Value<\/th>\n<th>Valid from<\/th>\n<th>Source<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Format of a Finnish Peppol address<\/td>\n<td>0216:003702454401 \u2014 scheme identifier 0216 + OVT code (the domestic address is the same code without 0216)<\/td>\n<td>as of 2026-09<\/td>\n<td><a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\" rel=\"nofollow noopener\">valtiokonttori.fi<\/a><\/td>\n<\/tr>\n<tr>\n<td>The old 0037 scheme identifier in Peppol<\/td>\n<td>FI:OVT (0037) has been removed from the participant identifier code list; removal date 31 December 2024<\/td>\n<td>2024-12-31<\/td>\n<td><a href=\"https:\/\/docs.peppol.eu\/edelivery\/codelists\/v9.7\/Peppol%20Code%20Lists%20-%20Participant%20identifier%20schemes%20v9.7.html\" rel=\"nofollow noopener\">docs.peppol.eu<\/a><\/td>\n<\/tr>\n<tr>\n<td>Right to demand a structured e-invoice in Finland<\/td>\n<td>A contracting authority and a business covered by Act 241\/2019 may require an e-invoice; a business is covered when its financial-year turnover exceeds EUR 10,000<\/td>\n<td>2020-04-01<\/td>\n<td><a href=\"https:\/\/www.finlex.fi\/en\/legislation\/collection\/2019\/241\" rel=\"nofollow noopener\">finlex.fi<\/a><\/td>\n<\/tr>\n<tr>\n<td>Public-sector obligation to receive e-invoices<\/td>\n<td>Central government bodies and central purchasing bodies from 1 April 2019, other contracting authorities from 1 April 2020<\/td>\n<td>2019-04-01 \/ 2020-04-01<\/td>\n<td><a href=\"https:\/\/www.finlex.fi\/en\/legislation\/collection\/2019\/241\" rel=\"nofollow noopener\">finlex.fi<\/a><\/td>\n<\/tr>\n<tr>\n<td>Peppol growth in Finland<\/td>\n<td>Peppol transaction volume grew 60.6% in 2024\u20132025; central government adopted the Peppol network on 1 April 2024<\/td>\n<td>2024-04-01<\/td>\n<td><a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\" rel=\"nofollow noopener\">valtiokonttori.fi<\/a><\/td>\n<\/tr>\n<tr>\n<td>ViDA digital reporting deadline<\/td>\n<td>Digital reporting requirements for cross-border B2B transactions apply from 1 July 2030; domestic systems must align by 1 January 2035<\/td>\n<td>2030-07-01<\/td>\n<td><a href=\"https:\/\/taxation-customs.ec.europa.eu\/news\/adoption-vat-digital-age-package-2025-03-11_en?prefLang=it\" rel=\"nofollow noopener\">taxation-customs.ec.europa.eu<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2 id=\"how-a-finnish-ovt-code-and-a-peppol-identifier-are-built\">How a Finnish OVT code and a Peppol identifier are built<\/h2>\n<p>Take a Y-tunnus, the Finnish company registration number, say 1234567-8. The OVT code is assembled from three parts:<\/p>\n<ul>\n<li><strong>Fixed opening:<\/strong> 0037.<\/li>\n<li><strong>The Y-tunnus without the hyphen:<\/strong> 12345678, eight characters.<\/li>\n<li><strong>Optional extension:<\/strong> up to five characters (A\u2013Z or 0\u20139) that the company itself assigns to a unit or department.<\/li>\n<\/ul>\n<p>The result is 003712345678, or the longer form 003712345678ABCDE. In Peppol, the scheme identifier and a colon go in front: 0216:003712345678.<\/p>\n<p>This is where the confusion usually starts. 0216 is not a Finnish country code. It is a scheme identifier, which tells Peppol what kind of identifier sits to the right of the colon. The old scheme identifier 0037 is no longer valid as a Peppol participant identifier: <a href=\"https:\/\/docs.peppol.eu\/edelivery\/codelists\/v9.7\/Peppol%20Code%20Lists%20-%20Participant%20identifier%20schemes%20v9.7.html\">the FI:OVT entry was removed from the code list with the date 31 December 2024<\/a>. Yet 0037 still lives <em>inside<\/em> the OVT code, as its first four characters. The scheme name went away, not the prefix.<\/p>\n<h2 id=\"verkkolaskuosoite-plus-valittajatunnus-or-a-peppol-address\">Verkkolaskuosoite plus v\u00e4litt\u00e4j\u00e4tunnus, or a Peppol address?<\/h2>\n<p>The Finnish domestic route has two mandatory data fields. TIEKE, which maintains the Finnish address directory, says it plainly: <a href=\"https:\/\/tieke.fi\/palvelut\/verkkolaskuosoitteisto\/\">the v\u00e4litt\u00e4j\u00e4tunnus shows which intermediary the invoice travels through, and without it the invoice does not arrive<\/a>. With Peppol you don&#8217;t have to know the routing yourself. The end user joins the network through a service provider, and <a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\">that service provider registers the Peppol address in the network&#8217;s address book and may run part of the Address and Capability Lookup (ACL) service, the query that shows who can receive what<\/a>.<\/p>\n<table>\n<thead>\n<tr>\n<th>What you&#8217;re comparing<\/th>\n<th>Finnish domestic route<\/th>\n<th>Peppol route<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>What you ask the recipient for<\/td>\n<td>verkkolaskuosoite (OVT) <strong>and<\/strong> v\u00e4litt\u00e4j\u00e4tunnus<\/td>\n<td>Peppol address in the form 0216:OVT<\/td>\n<\/tr>\n<tr>\n<td>Where you verify it<\/td>\n<td>Verkkolaskuosoitteisto<\/td>\n<td>Peppol address book or a service provider&#8217;s capability lookup<\/td>\n<\/tr>\n<tr>\n<td>Who delivers the invoice<\/td>\n<td>a Finnish operator or bank<\/td>\n<td>a certified Peppol service provider<\/td>\n<\/tr>\n<tr>\n<td>Reach<\/td>\n<td>inside Finland<\/td>\n<td>every participant in the Peppol network, Finland and beyond<\/td>\n<\/tr>\n<tr>\n<td>Typical format<\/td>\n<td>Finvoice 3.0, TEAPPSXML 3.0<\/td>\n<td>Peppol BIS Billing<\/td>\n<\/tr>\n<tr>\n<td>Where it breaks<\/td>\n<td>the intermediary code is missing or wrong<\/td>\n<td>you assume an OVT code means Peppol readiness<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For most Baltic small businesses sending a handful of invoices a month to a Finnish customer: use the channel the customer named, and keep the other one on file as a backup. With a public-sector buyer it is worth asking for both. The State Treasury&#8217;s guidance recommends publishing both the domestic e-invoice address and the Peppol address, which means treating them as two distinct channels rather than two names for the same thing.<\/p>\n<h2 id=\"peppol-readiness-can-t-be-read-out-of-an-ovt-code\">Peppol readiness can&#8217;t be read out of an OVT code<\/h2>\n<p>The Finnish verkkolaskuosoitteisto is genuinely useful: <a href=\"https:\/\/tieke.fi\/palvelut\/verkkolaskuosoitteisto\/\">using it and adding your own details is free, the data is maintained by Finnish intermediaries (operators and banks), and you can look up which organisations are able to send and\/or receive e-invoices<\/a>. The limitation lies elsewhere: it describes the domestic route. Publishing a Peppol address and capability <a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\">is not mandatory, which is why neither the Finnish directory nor the Peppol register is exhaustive<\/a>. An empty search result means &#8220;unknown&#8221;, not &#8220;unable&#8221;.<\/p>\n<p>So do this instead:<\/p>\n<ul>\n<li><strong>Ask in writing:<\/strong> which channel the customer wants, domestic or Peppol.<\/li>\n<li><strong>Check the directory:<\/strong> for the domestic channel, the address and the v\u00e4litt\u00e4j\u00e4tunnus; for Peppol, the address in the form 0216:OVT.<\/li>\n<li><strong>Confirm readiness with a lookup:<\/strong> your e-invoice operator can see from a Peppol query whether the recipient actually receives invoices.<\/li>\n<li><strong>Agree the format:<\/strong> Peppol BIS Billing, Finvoice 3.0 or TEAPPSXML 3.0.<\/li>\n<li><strong>Save it on the customer card:<\/strong> channel, address and intermediary code together. A verbal &#8220;we&#8217;ve got an OVT&#8221; is not an address.<\/li>\n<\/ul>\n<p>Finland&#8217;s e-invoicing act 241\/2019 contains no penalty or sanction provision. <a href=\"https:\/\/finlex.fi\/fi\/lainsaadanto\/2019\/241\">The act covers only its scope, definitions, the obligation to receive and process e-invoices, the right to receive an e-invoice, and entry into force<\/a>. There is no separate fine for picking the wrong channel. The cost is practical: the invoice doesn&#8217;t arrive, nobody notices for a week, and the payment date slips.<\/p>\n<h2 id=\"what-finnish-law-actually-requires\">What Finnish law actually requires<\/h2>\n<p>Act 241\/2019 <a href=\"https:\/\/www.finlex.fi\/en\/legislation\/collection\/2019\/241\">entered into force on 1 April 2019 and implements Directive 2014\/55\/EU on e-invoicing in public procurement in Finland<\/a>. A business falls under the act when its financial-year turnover exceeds EUR 10,000. From 1 April 2020, a contracting authority and a business covered by the act have the right to require an e-invoice from another contracting authority or business. On the public-sector side, the obligation to receive and process invoices applied to central government bodies and central purchasing bodies from 1 April 2019, and to other contracting authorities from 1 April 2020.<\/p>\n<p>What the act does not contain is any obligation to use Peppol specifically. It talks about a structured invoice that conforms to the European invoice content standard EN 16931, and <a href=\"https:\/\/eur-lex.europa.eu\/eli\/dec_impl\/2017\/1870\/oj\">the reference to that standard and the list of permitted syntaxes were published by Commission Implementing Decision (EU) 2017\/1870<\/a>. There is more than one way to produce a conforming invoice: <a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\">Peppol BIS Billing, Finvoice 3.0 and TEAPPSXML 3.0 can all do it<\/a>. &#8220;Does the invoice comply with EN 16931&#8221; and &#8220;did the invoice travel over the Peppol network&#8221; are two different questions. In pure B2B you are not required to use Peppol. A structured invoice becomes obligatory when the customer demands one.<\/p>\n<h2 id=\"what-changed-in-2026-and-what-to-have-ready-by-2030\">What changed in 2026, and what to have ready by 2030<\/h2>\n<p>The 2026 changes concern format and validation, not addressing. OpenPeppol published the Peppol BIS Billing 3.0 release on 20 May 2026, and it became mandatory on 17 August 2026. That is about invoice content and validation rules, and it brought no new Finnish address format with it. The same logic runs through all Peppol documentation: specifications and code lists move forward version by version, and <a href=\"https:\/\/docs.peppol.eu\/edelivery\/codelists\/v9.7\/Peppol%20Code%20Lists%20-%20Participant%20identifier%20schemes%20v9.7.html\">the participant identifier list currently sits at version 9.7<\/a>.<\/p>\n<p>Volume, meanwhile, is shifting towards Peppol. <a href=\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\">In Finland the number of Peppol transactions grew 60.6% in 2024\u20132025, and central government adopted the Peppol network together with Advanced Ordering documents on 1 April 2024<\/a>. That&#8217;s why you increasingly find yourself in the situation where the first thing a Finnish customer hands you is a Peppol address.<\/p>\n<p>The bigger picture comes from ViDA (VAT in the Digital Age). <a href=\"https:\/\/taxation-customs.ec.europa.eu\/news\/adoption-vat-digital-age-package-2025-03-11_en?prefLang=it\">The package was adopted on 11 March 2025 and published in the Official Journal of the European Union on 25 March 2025: digital reporting requirements for cross-border B2B transactions apply from 1 July 2030, and by 1 January 2035 member states with domestic real-time reporting must align their systems with the EU standards<\/a>. According to the same announcement, member states may impose mandatory e-invoicing under certain conditions once the rules are in force. ViDA does not make Peppol mandatory by name.<\/p>\n<p>For you that means two things: keep both the OVT plus v\u00e4litt\u00e4j\u00e4tunnus and the Peppol address in order on your customer cards, and make sure your software can produce a machine-readable invoice that conforms to EN 16931. Those two choices carry both today&#8217;s Finnish invoice and 2030&#8217;s cross-border reporting.<\/p>\n<h2 id=\"recurring-questions-about-ovt-codes-and-peppol\">Recurring questions about OVT codes and Peppol<\/h2>\n<h3 id=\"is-a-y-tunnus-enough-to-send-an-invoice\">Is a Y-tunnus enough to send an invoice?<\/h3>\n<p>No. A Y-tunnus identifies the company; it is not a routing address. For domestic sending you need a verkkolaskuosoite in OVT form plus a v\u00e4litt\u00e4j\u00e4tunnus; for sending via Peppol you need the address in the form 0216:OVT.<\/p>\n<h3 id=\"if-a-customer-has-an-ovt-code-are-they-on-peppol\">If a customer has an OVT code, are they on Peppol?<\/h3>\n<p>Not necessarily. OVT codes are widely used in Finland entirely outside Peppol. A company becomes a Peppol participant once a service provider has registered its address in the network&#8217;s address book, and since publishing is not mandatory, confirm readiness with a lookup rather than an assumption.<\/p>\n<h3 id=\"does-the-domestic-address-disappear-when-a-customer-moves-to\">Does the domestic address disappear when a customer moves to Peppol?<\/h3>\n<p>Not automatically. The State Treasury&#8217;s guidance recommends that public-sector bodies publish both addresses, so expect the same recipient to be reachable on two channels at once for a while.<\/p>\n<p class=\"ce-lang-links\"><span class=\"ce-label\">Also available in:<\/span> <a href=\"https:\/\/bilnex.io\/verkkolaskuosoite-vs-peppol-tunnus\/\" hreflang=\"et\" lang=\"et\">eesti keeles<\/a> \u00b7 <a href=\"https:\/\/bilnex.io\/lv\/verkkolaskuosoite-peppol-atskiriba\/\" hreflang=\"lv\" lang=\"lv\">latviski<\/a> \u00b7 <a href=\"https:\/\/bilnex.io\/lt\/verkkolaskuosoite-peppol-id-2\/\" hreflang=\"lt\" lang=\"lt\">lietuvi\u0161kai<\/a><\/p>\n<div class=\"ce-related-topic\">\n<p class=\"ce-label\"><strong>Related in this topic<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/bilnex.io\/en\/e-invoicing-finland-2026\/\">E-Invoicing in Finland 2026: Rules, Limits and the PDF Trap<\/a><\/li>\n<li><a href=\"https:\/\/bilnex.io\/en\/finnish-verkkolasku-without-software\/\">How to Send a Finnish Verkkolasku Without Software<\/a><\/li>\n<li><a href=\"https:\/\/bilnex.io\/en\/finland-e-invoice-law-2019\/\">Finland 241\/2019: When Buyers Can Demand E-Invoices<\/a><\/li>\n<li><a href=\"https:\/\/bilnex.io\/en\/verkkolasku-finland-definition\/\">What is a verkkolasku? Finnish e-invoice rules 2026<\/a><\/li>\n<\/ul>\n<\/div>\n<p class=\"ce-reviewed\"><em>Last reviewed: <time datetime=\"Tue Sep 15\">15 September 2026<\/time><\/em><\/p>\n<h2>FAQ<\/h2>\n<h3>Kas Soome Y-tunnusest piisab e-arve saatmiseks?<\/h3>\n<p>Ei piisa. Y-tunnus on vaid ettev\u00f5tte registrikood, mitte marsruutimisaadress. Riigisiseseks saatmiseks on vaja OVT-kujulist verkkolaskuosoitet koos v\u00e4litt\u00e4j\u00e4tunnusega ning Peppoli kaudu saatmiseks aadressi kujul 0216:OVT.<\/p>\n<h3>Kas OVT-koodi olemasolu t\u00e4hendab automaatselt Peppoli valmidust?<\/h3>\n<p>Ei t\u00e4henda. OVT-koodi kasutatakse Soome siseriiklikus v\u00f5rgus ka ilma Peppolita. Ettev\u00f5te on Peppolis k\u00e4ttesaadav vaid siis, kui tema teenusepakkuja on aadressi Peppoli aadressiraamatusse kandnud, mida tuleb kontrollida valmidusp\u00e4ringuga.<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Kas Soome Y-tunnusest piisab e-arve saatmiseks?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Ei piisa. Y-tunnus on vaid ettev\u00f5tte registrikood, mitte marsruutimisaadress. Riigisiseseks saatmiseks on vaja OVT-kujulist verkkolaskuosoitet koos v\u00e4litt\u00e4j\u00e4tunnusega ning Peppoli kaudu saatmiseks aadressi kujul 0216:OVT.\"}},{\"@type\":\"Question\",\"name\":\"Kas OVT-koodi olemasolu t\u00e4hendab automaatselt Peppoli valmidust?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Ei t\u00e4henda. OVT-koodi kasutatakse Soome siseriiklikus v\u00f5rgus ka ilma Peppolita. Ettev\u00f5te on Peppolis k\u00e4ttesaadav vaid siis, kui tema teenusepakkuja on aadressi Peppoli aadressiraamatusse kandnud, mida tuleb kontrollida valmidusp\u00e4ringuga.\"}}]}<\/script><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/bilnex.io\/#organization\",\"name\":\"Bilnex\",\"alternateName\":\"Bilnex\",\"url\":\"https:\/\/bilnex.io\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\/\/bilnex.io\/wp-content\/uploads\/2025\/07\/Bilnex-Favicon-512px.jpg\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/bilnex-io\/\",\"https:\/\/www.facebook.com\/bilnex.io\"]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/bilnex.io\/#website\",\"url\":\"https:\/\/bilnex.io\",\"name\":\"Bilnex\",\"publisher\":{\"@id\":\"https:\/\/bilnex.io\/#organization\"},\"inLanguage\":\"en-GB\"},{\"@type\":\"Article\",\"@id\":\"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/#article\",\"headline\":\"Verkkolaskuosoite or Peppol ID: what's the difference?\",\"description\":\"Understand the difference between Finnish verkkolaskuosoite with operator ID and Peppol ID 0216:OVT. Find out which routing to request for Finnish e-invoicing.\",\"inLanguage\":\"en-GB\",\"mainEntityOfPage\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/\"},\"url\":\"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/\",\"dateModified\":\"2026-09-15T06:58:27.798Z\",\"author\":{\"@id\":\"https:\/\/bilnex.io\/#organization\"},\"publisher\":{\"@id\":\"https:\/\/bilnex.io\/#organization\"},\"isPartOf\":{\"@id\":\"https:\/\/bilnex.io\/#website\"},\"citation\":[\"https:\/\/www.finlex.fi\/en\/legislation\/collection\/2019\/241\",\"https:\/\/eur-lex.europa.eu\/eli\/dec_impl\/2017\/1870\/oj\",\"https:\/\/www.valtiokonttori.fi\/en\/service\/the-state-treasury-is-the-finnish-peppol-authority\/\",\"https:\/\/tieke.fi\/palvelut\/verkkolaskuosoitteisto\/\",\"https:\/\/docs.peppol.eu\/edelivery\/codelists\/v9.7\/Peppol%20Code%20Lists%20-%20Participant%20identifier%20schemes%20v9.7.html\",\"https:\/\/taxation-customs.ec.europa.eu\/news\/adoption-vat-digital-age-package-2025-03-11_en?prefLang=it\"],\"about\":{\"@type\":\"Thing\",\"name\":\"Soome verkkolasku\"}},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Bilnex\",\"item\":\"https:\/\/bilnex.io\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Verkkolaskuosoite or Peppol ID: what's the difference?\",\"item\":\"https:\/\/bilnex.io\/en\/verkkolaskuosoite-peppol-id\/\"}]}]}<\/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>Abos par\u0101d\u0101s viens un tas pats OVT numurs, ta\u010du at\u0161\u0137iras process: kad l\u016bgt verkkolaskuosoite plus v\u00e4litt\u00e4j\u00e4tunnus, un kad Peppol adresi.<\/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-29436","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/pages\/29436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/comments?post=29436"}],"version-history":[{"count":1,"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/pages\/29436\/revisions"}],"predecessor-version":[{"id":29440,"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/pages\/29436\/revisions\/29440"}],"wp:attachment":[{"href":"https:\/\/bilnex.io\/lv\/wp-json\/wp\/v2\/media?parent=29436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}