{"id":29107,"date":"2026-08-08T07:00:03","date_gmt":"2026-08-08T07:00:03","guid":{"rendered":"https:\/\/bilnex.io\/lv\/peppol-bis-billing-versija\/"},"modified":"2026-08-08T07:00:03","modified_gmt":"2026-08-08T07:00:03","slug":"peppol-bis-atsiskaitymo-versija-2","status":"publish","type":"page","link":"https:\/\/bilnex.io\/lt\/peppol-bis-atsiskaitymo-versija-2\/","title":{"rendered":"Kuri \u201ePeppol BIS Billing 3.0\u201c versija bus prieinama 2026 m. rugpj\u016b\u010dio m\u0117n.?"},"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=\"isa-atbilde-uz-2026-gada-7-augustu\">\u012as\u0101 atbilde uz 2026. gada 7. augustu<\/h2>\n<p>2026. gada 7. august\u0101 Peppol BIS Billing 3.0 t\u012bkl\u0101 v\u0113l darbojas versija 3.0.20 kop\u0101 ar oblig\u0101to 3.0.20-hotfix labojumu. Desmit dienas v\u0113l\u0101k, 2026. gada 17. august\u0101, oblig\u0101ta k\u013c\u016bst versija 3.0.21, kas public\u0113ta 2026. gada 20. maij\u0101. Visi tr\u012bs termi\u0146i ir fiks\u0113ti openPeppol <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/upcoming\/release-notes\/\">izlaiduma piez\u012bm\u0113s<\/a>. Tas nav jauns r\u0113\u0137inu form\u0101ts, bet gan valid\u0101cijas un kodu sarakstu atjaunin\u0101jums vien\u0101 un taj\u0101 pa\u0161\u0101 Peppol BIS Billing 3.0 saim\u0113. Praktiski visdro\u0161\u0101k tagad ir piepras\u012bt no e-r\u0113\u0137inu operatora vai gr\u0101matved\u012bbas programmat\u016bras ra\u017eot\u0101ja rakstisku apstiprin\u0101jumu \u2013 kad t\u0101 sist\u0113ma p\u0101ries uz 3.0.21 noteikumiem un vai t\u0101 l\u012bdz \u0161im termi\u0146am ir p\u0101rbaud\u012bta.<\/p>\n<table>\n<thead>\n<tr>\n<th>Datums<\/th>\n<th>Kas ir sp\u0113k\u0101<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>2026. gada 7. augusts<\/td>\n<td>3.0.20 + oblig\u0101tais hotfix<\/td>\n<\/tr>\n<tr>\n<td>2026. gada 17. augusts<\/td>\n<td>3.0.21 k\u013c\u016bst oblig\u0101ta visiem<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"vai-peppol-bis-billing-3-0-ir-viens-fails-vai-vesela-versiju\">Vai Peppol BIS Billing 3.0 ir viens fails vai vesela versiju saime?<\/h2>\n<p>Liel\u0101k\u0101 da\u013ca neizpratnes rodas t\u0101p\u0113c, ka &#8220;Peppol BIS Billing 3.0&#8221; un versijas numurs, piem\u0113ram, 3.0.20 vai 3.0.21, izklaus\u0101s vien\u0101di, bet nav viens un tas pats. BIS Billing 3.0 ir stabils biznesa dokumenta apraksts, kas nosaka, k\u0101diem datu laukiem j\u0101b\u016bt r\u0113\u0137in\u0101. Tas raksturo standarta r\u0113\u0137ina un kred\u012btr\u0113\u0137ina procesu, ko openPeppol d\u0113v\u0113 par profilu 01 un kas <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/bis\/\">t\u0101 ofici\u0101laj\u0101 specifik\u0101cij\u0101<\/a> joproj\u0101m min\u0113ts k\u0101 &#8220;Profile 01 \u2013 Billing&#8221;. Ta\u010du \u0161\u012b visp\u0101r\u0113j\u0101 specifik\u0101cija regul\u0101ri tiek atjaunota maz\u0101kos izlaidumos \u2013 3.0.19, 3.0.20, 3.0.21 un t\u0101 t\u0101l\u0101k \u2013 kas ievie\u0161 atjaunin\u0101tus kodu sarakstus jeb pie\u013caujamo v\u0113rt\u012bbu sarakstus (piem\u0113ram, valstu kodus) un valid\u0101cijas artefaktus, kas p\u0101rbauda, vai nos\u016bt\u012btais XML fails atbilst noteikumiem. Pa\u0161reiz\u0113j\u0101 ofici\u0101l\u0101 rokasgr\u0101mata joproj\u0101m nes versijas numuru 3.0.20, k\u0101 liecina <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/bis\/\">specifik\u0101cijas titullapa<\/a>. Numurs nomain\u012bsies uz 3.0.21 tikai tad, kad \u0161is izlaidums st\u0101sies sp\u0113k\u0101 ofici\u0101li.<\/p>\n<h2 id=\"kas-maina-versija-3-0-21\">Kas maina versija 3.0.21?<\/h2>\n<p>3.0.21 lieto kodu sarakstus, kas public\u0113ti 2026. gada 6. mart\u0101, un UBL\/CII valid\u0101cijas artefaktus versij\u0101 1.3.16, kas public\u0113ti 2026. gada 10. apr\u012bl\u012b. Abi datumi min\u0113ti openPeppol <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/upcoming\/release-notes\/\">izlaiduma piez\u012bm\u0113s<\/a>. UBL un CII ir divi alternat\u012bvi XML sintakses veidi, k\u0101dos var b\u016bt rakst\u012bts Peppol r\u0113\u0137ins; liel\u0101k\u0101 da\u013ca Baltijas operatoru izmanto UBL. Noz\u012bm\u012bg\u0101k\u0101 izmai\u0146a skar noteikumus PEPPOL-COMMON-R052 un PEPPOL-COMMON-R053, kas iepriek\u0161 bija br\u012bdin\u0101jumi, bet 3.0.21 tie k\u013c\u016bst par k\u013c\u016bd\u0101m visiem profiliem. Praktiski tas noz\u012bm\u0113, ka test\u0113jot j\u0101izmanto re\u0101li klienta un pieg\u0101d\u0101t\u0101ja pamatdati, ne tikai parauga XML, jo tie\u0161i \u0161ie noteikumi p\u0101rbauda \u0161os laukus. Papildus par\u0101d\u0101s jauns izv\u0113les profils 02 r\u0113\u0137ina-un-atbildes procesam \u2013 par to pla\u0161\u0101k zem\u0101k. Parastam r\u0113\u0137inu s\u016bt\u012bt\u0101jam, kas izmanto profilu 01 un vienk\u0101r\u0161i apmain\u0101s ar r\u0113\u0137iniem un kred\u012btr\u0113\u0137iniem, biznesa process nemain\u0101s ne par soli. Maina tikai fona p\u0101rbaudes.<\/p>\n<h2 id=\"ko-parbaudit-lidz-17-augustam\">Ko p\u0101rbaud\u012bt l\u012bdz 17. augustam?<\/h2>\n<p>Dro\u0161\u0101kais ce\u013c\u0161 ir r\u012bkoties sistem\u0101tiski, nevis pa\u013cauties, ka operators &#8220;jau tiek ar to gal\u0101&#8221;:<\/p>\n<ul>\n<li><strong>Apstiprin\u0101jums no pieg\u0101d\u0101t\u0101ja:<\/strong> pieprasiet operatoram rakstiski, kad t\u0101 produkcijas vide p\u0101ries uz <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/upcoming\/release-notes\/\">3.0.21 valid\u0101cijas artefaktiem<\/a>.<\/li>\n<li><strong>Validatoru atjaunin\u0101\u0161ana:<\/strong> ja r\u0113\u0137inus valid\u0113jat pats, izmantojiet jaun\u0101kos UBL\/CII 1.3.16 noteikumus, ne veco 3.0.20 komplektu.<\/li>\n<li><strong>Test\u0113jiet ar re\u0101liem datiem:<\/strong> izs\u016btiet testa r\u0113\u0137inu un kred\u012btr\u0113\u0137inu caur sist\u0113mu ar re\u0101la klienta un pieg\u0101d\u0101t\u0101ja nosaukumiem, adres\u0113m un re\u0123istr\u0101cijas kodiem, jo tie\u0161i \u0161ajos laukos R052 un R053 k\u013c\u016bst par k\u013c\u016bd\u0101m.<\/li>\n<li><strong>P\u0101rbaudiet pirc\u0113ja identifikatorus:<\/strong> hotfix 2026. gada 27. janv\u0101r\u012b pievienoja Slov\u0101kijas nodok\u013cu kodu 0245, un 3.0.21 pievieno jaunus ICD kodus 0246\u20130248. P\u0101rrobe\u017eu p\u0101rdo\u0161anas gad\u012bjum\u0101 p\u0101rliecinieties, ka \u0161ie kodi j\u016bsu sist\u0113m\u0101 ir ieprogramm\u0113ti.<\/li>\n<li><strong>Saglab\u0101jiet pier\u0101d\u012bjumus:<\/strong> paturiet nos\u016bt\u012b\u0161anas un pieg\u0101des apstiprin\u0101jumus no p\u0101rejas perioda, lai pier\u0101d\u012btu, uz k\u0101da noteikumu kopuma pamata r\u0113\u0137ins tika izs\u016bt\u012bts.<\/li>\n<\/ul>\n<h2 id=\"kada-atskiriba-starp-profilu-01-un-profilu-02\">K\u0101da at\u0161\u0137ir\u012bba starp profilu 01 un profilu 02?<\/h2>\n<p>Profils 01 ir standarta process: p\u0101rdev\u0113js s\u016bta r\u0113\u0137inu vai kred\u012btr\u0113\u0137inu, pirc\u0113js to sa\u0146em, un process ir pabeigts. T\u0101 tehniskie identifikatori ir fiks\u0113ti: CustomizationID jeb r\u0113\u0137ina atbilst\u012bbas deklar\u0101cijas identifikators ir `urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0`, un ProfileID jeb biznesa procesa identifikators ir `urn:fdc:peppol.eu:2017:poacc:billing:01:1.0`, k\u0101 tos fiks\u0113 <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/bis\/\">pa\u0161reiz\u0113j\u0101 rokasgr\u0101mata<\/a>. J\u016bsu eso\u0161aj\u0101 XML p\u0113c 3.0.21 \u0161\u012bs v\u0113rt\u012bbas nav j\u0101maina. Standarta r\u0113\u0137inu procesam \u0161is izlaidums jaunu CustomizationID vai ProfileID nenes.<\/p>\n<p>Jauns ir tikai izv\u0113les profils 02, kas ar 3.0.21 pievienojas procesam, kur\u0101 pirc\u0113jam j\u0101s\u016bta atgriezenisk\u0101 saite par r\u0113\u0137inu jeb r\u0113\u0137ina atbilde \u2013 piem\u0113ram, apstiprin\u0101jums, ka r\u0113\u0137ins ir pie\u0146emts vai noraid\u012bts. \u0160is profils prasa atsevi\u0161\u0137u re\u0123istr\u0101ciju SMP jeb pakalpojumu metadatu re\u0123istr\u0101 (Service Metadata Publisher), kur\u0101 Peppol t\u012bkls glab\u0101 inform\u0101ciju, k\u0101dus dokumentus j\u016bsu uz\u0146\u0113mums sp\u0113j pie\u0146emt, k\u0101 skaidro <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/upcoming\/release-notes\/\">izlaiduma piez\u012bmes<\/a>. Ja j\u016bsu pirc\u0113ji profilu 02 nepieprasa un neatbalsta, nav j\u0113gas to re\u0123istr\u0113t. Palieciet pie profila 01 un pievienojiet profilu 02 tikai tad, kad konkr\u0113ts biznesa partneris to tie\u0161i pieprasa.<\/p>\n<h2 id=\"ko-tas-nozime-igaunija-latvija-un-lietuva\">Ko tas noz\u012bm\u0113 Igaunij\u0101, Latvij\u0101 un Lietuv\u0101?<\/h2>\n<p>Igaunij\u0101 no <a href=\"https:\/\/www.riigiteataja.ee\/en\/compare_wordings?grupiId=100007&amp;vasakAktId=510072025005\">2025. gada 1. j\u016blija<\/a> sp\u0113k\u0101 ir gr\u0101matved\u012bbas likuma groz\u012bjums, saska\u0146\u0101 ar kuru komercre\u0123istr\u0101 par e-r\u0113\u0137ina sa\u0146\u0113m\u0113ju re\u0123istr\u0113ts gr\u0101matved\u012bbas subjekts var piepras\u012bt, lai p\u0101rdev\u0113js tam iesniegtu e-r\u0113\u0137inu, un r\u0113\u0137ins tiek uzskat\u012bts par pareizi sagatavotu, ja tas atbilst Eiropas standartam EN 16931-1, ja puses nav vienoju\u0161\u0101s par citu standartu.<\/p>\n<p>Latvij\u0101 pras\u012bba ir skaidr\u0101k balst\u012bta uz Peppol: Valsts ie\u0146\u0113mumu dienests struktur\u0113tu e-r\u0113\u0137inu raksturo k\u0101 XML failu, kura strukt\u016brai j\u0101atbilst <a href=\"https:\/\/www.vid.gov.lv\/lv\/e-rekini\">Peppol BIS Billing 3.0 specifik\u0101cijai<\/a>. G2G, B2G un G2B dar\u012bjumos struktur\u0113ts e-r\u0113\u0137ins ir oblig\u0101ts no 2025. gada 1. janv\u0101ra, e-r\u0113\u0137ina datu nos\u016bt\u012b\u0161ana Valsts ie\u0146\u0113mumu dienestam tiem pa\u0161iem segmentiem ir oblig\u0101ta no 2026. gada 1. janv\u0101ra, un B2B pras\u012bba kop\u0101 ar vienlaic\u012bgu iesnieg\u0161anu st\u0101sies sp\u0113k\u0101 no 2028. gada 1. janv\u0101ra.<\/p>\n<p>Lietuv\u0101 e-r\u0113\u0137ins virz\u0101s caur valsts platformu SABIS, ko Finan\u0161u ministrija ir <a href=\"https:\/\/finmin.lrv.lt\/lt\/paslaugos\/SABIS\/\">savienojusi ar Peppol t\u012bklu<\/a>. Praktiski tas noz\u012bm\u0113, ka ar\u012b SABIS lietojo\u0161ie Lietuvas pirc\u0113ji un p\u0101rdev\u0113ji faktiski sazin\u0101s, izmantojot tos pa\u0161us Peppol BIS Billing dokumentus un profilus, kas aprakst\u012bti \u0161aj\u0101 rakst\u0101.<\/p>\n<h2 id=\"kapec-rekini-patiesiba-tiek-noraiditi\">K\u0101p\u0113c r\u0113\u0137ini paties\u012bb\u0101 tiek noraid\u012bti?<\/h2>\n<p>Liela da\u013ca gad\u012bjumu, kad &#8220;r\u0113\u0137ins neaizg\u0101ja cauri&#8221;, izriet no piecu j\u0113dzienu sajauk\u0161anas. EN 16931 ir Eiropas standarts, kas visp\u0101r\u012bgi raksturo r\u0113\u0137ina semantisko datu modeli. Peppol BIS Billing 3.0 ir \u0161\u012b standarta CIUS jeb Core Invoice Usage Specification \u2013 sa\u0161aurin\u0101ta lieto\u0161anas pam\u0101c\u012bba, kas <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/bis\/\">padara EN 16931 pras\u012bbas konkr\u0113t\u0101kas<\/a> Peppol t\u012bkla kontekst\u0101. Izlaiduma numurs, piem\u0113ram, 3.0.20 vai 3.0.21, nav jauns standarts vai jauns r\u0113\u0137ina form\u0101ts \u2013 tas ir valid\u0101cijas un kodu sarakstu versijas atjaunin\u0101jums taj\u0101 pa\u0161\u0101 BIS Billing 3.0. SMP re\u0123istr\u0101cija, kas nosaka, k\u0101dus profilus j\u016bsu uz\u0146\u0113mums sp\u0113j pie\u0146emt, ir atsevi\u0161\u0137s tehnisks iestat\u012bjums, kas autom\u0101tiski nemain\u0101s l\u012bdz ar izlaiduma nomai\u0146u. Un PDF r\u0113\u0137ins, kaut cik pareizi tas izskat\u012btos, nav Peppol r\u0113\u0137ins \u2013 tas ir pielikums, ko iek\u0101rta nelasa un neizvalid\u0113 p\u0113c Peppol noteikumiem. Kad r\u0113\u0137ins tiek noraid\u012bts, vispirms p\u0101rbaudiet, kur\u0161 no \u0161iem pieciem elementiem \u012bsten\u012bb\u0101 tr\u016bkst, pirms s\u0101kat aizdom\u0101ties, ka &#8220;Peppol nedarbojas&#8221;.<\/p>\n<h2>FAQ<\/h2>\n<h3>Mis muutub versioonis 3.0.21?<\/h3>\n<p>3.0.21 kasutab koodiloendeid, mis avaldati 6. m\u00e4rtsil 2026, ja UBL\/CII valideerimisartefakte versioonis 1.3.16. Olulisem muudatus puudutab reegleid PEPPOL-COMMON-R052 ja PEPPOL-COMMON-R053, mis muutuvad vigadeks. Lisandub valikuline profiil 02.<\/p>\n<h3>Mis vahe on profiilil 01 ja profiilil 02?<\/h3>\n<p>Profiil 01 on tavaline arve saatmine ilma vastuseta. Profiil 02 lisab arvevastuse protsessi, kus ostja peab saatma tagasiside. Profiil 02 n\u00f5uab eraldi SMP-registreeringut.<\/p>\n<h3>Mida kontrollida enne 17. augustit 2026?<\/h3>\n<p>K\u00fcsi operaatorilt kirjalik kinnitus \u00fclemineku kohta, uuenda validaatoreid, testi p\u00e4ris andmetega (R052 ja R053), kontrolli ostja identifikaatoreid (ICD-koodid 0246\u20130248) ja hoia t\u00f5endid alles.<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Mis muutub versioonis 3.0.21?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"3.0.21 kasutab koodiloendeid, mis avaldati 6. m\u00e4rtsil 2026, ja UBL\/CII valideerimisartefakte versioonis 1.3.16. Olulisem muudatus puudutab reegleid PEPPOL-COMMON-R052 ja PEPPOL-COMMON-R053, mis muutuvad vigadeks. Lisandub valikuline profiil 02.\"}},{\"@type\":\"Question\",\"name\":\"Mis vahe on profiilil 01 ja profiilil 02?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Profiil 01 on tavaline arve saatmine ilma vastuseta. Profiil 02 lisab arvevastuse protsessi, kus ostja peab saatma tagasiside. Profiil 02 n\u00f5uab eraldi SMP-registreeringut.\"}},{\"@type\":\"Question\",\"name\":\"Mida kontrollida enne 17. augustit 2026?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"K\u00fcsi operaatorilt kirjalik kinnitus \u00fclemineku kohta, uuenda validaatoreid, testi p\u00e4ris andmetega (R052 ja R053), kontrolli ostja identifikaatoreid (ICD-koodid 0246\u20130248) ja hoia t\u00f5endid alles.\"}}]}<\/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>7. Augusta spekke ir versija 3.0.20, statymas Nr. 17. Augusta sv\u00e4g\u00e4t\u00e4 bus 3.0.21 \u2014 davjam ko tas s\u00e4m\u00e4\u00e4 \u00e4\u00e4\u00e4\u00e4 \u00e4\u00e4\u00e4\u00e4\u00e4\u00e4.<\/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-29107","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/pages\/29107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/comments?post=29107"}],"version-history":[{"count":0,"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/pages\/29107\/revisions"}],"wp:attachment":[{"href":"https:\/\/bilnex.io\/lt\/wp-json\/wp\/v2\/media?parent=29107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}