Īsā answer uz 2026. gada August 7
On August 7, 2026, Peppol BIS Billing 3.0 is still running on version 3.0.20 with the obligatory 3.0.20-hotfix patch. Ten days later, August 17, 2026, version 3.0.21 must be published, May 20, 2026. Visi trės termiņi ir fixed in openPeppol in the release notes. Tas nav jauns rēķinu formats, bet gan validationācijas un kodu listu updatības venā un tāh paša Peppol BIS Billing 3.0 saimē. Praktiski visdrošāk tagad ir projatt no e-rēķinu operatora vai kontaktiyas softwares produktsari sikstisku pastiskujumu - kad tā sistema pāries uz 3.0.21 sukuri un vai tā tīl šim termam ir procetarta.
| Dates | What is valid? |
|---|---|
| August 7, 2026 | 3.0.20 + mandatory hotfix |
| August 17, 2026 | 3.0.21 becomes mandatory for everyone |
Or Peppol BIS Billing 3.0 ir viens fails or did we get a fresh version?
Most people don't understand why, "Peppol BIS Billing 3.0" and version numbers, for example 3.0.20 or 3.0.21, are the same, but there is nothing wrong with them. BIS Billing 3.0 ir stabilis biznesa dokumenta apraksts, kis nakaka, kādīm datu laukiem kubībā rīna. It describes the process as a standard account and credit card, which openPeppol uses as a profile 01 and as in its official specification still referred to as “Profile 01 – Billing”. However, this general specification is regularly updated in minarkos izlaidumos – 3.0.19, 3.0.20, 3.0.21 and tā tā darā – whether it is implemented in the updated home list or in the list of acceptable values (for example, in the country home) and the validation artefact, whether it verifies whether the XML file sent complies with the rules. The current official manual is still in version number 3.0.20, as shown specifications title page. The number will be changed to 3.0.21 until it becomes official.
Is it version 3.0.21?
3.0.21 in lieto home list, whether published on March 6, 2026, un UBL/CII validation artefacts in version 1.3.16, whether published on April 10, 2026. Help data minēti openPeppol in the release notes. UBL un CII ir divi alternatīvi XML syntaxes a little, kādos var būt rakstsits Peppol rēķins; UBL is used by the majority of Baltic operators. Nozīmīgākā izmaiņa skar skar skarveli PEPPOL-COMMON-R052 un PEPPOL-COMMON-R053, kas pīvet bija ātādījumi, bet 3.0.21 tie tavībā par kěūdām all profiliem. Praktiski tas sämä, also testing should be used with real client and supplier data, not just with XML, because it is precisely these rules that are checked in this box. In addition, jauns kombes profils 02 rēķina-un-atbildes procesam appears – par to sämää käher. I'm going to fix the rēķinu svātājam, whether you are using profile 01 and simply apmainās ar rēķiniem un kreidrēķiniem, biznesa process neminās ne par soli. Mention only phone checks.
Ko verracht till 17. Augustam?
Drošākais ceļs ir sistematīki sistemātiski, nevis pałęties, ka operators “jau tiek ar to kāla”:
- Apstiprinājums no supplyāja: pieprasiet operatoram pätsäki, kad tā produktijas vide pāries uz 3.0.21 validation artifacts.
- Validator update: and rēķinus validējat pats, use the latest UBL/CII 1.3.16 rules, ne veco 3.0.20 set.
- Testējiet with real data: izsūtiet testa rēķinu un kreidtrēķinu caur sistema ar āla klienta un prīstātāja nadamitiem, adresēm un registration kodiem, because it is precisely in these fields R052 and R053 that there are errors.
- Check the buyer ID: hotfix 2026. gada 27. janārīva add a new ICD home in Slovākijas 0245, un 3.0.21 add a new ICD home 0246-0248. In case of error, make sure that these codes are also programmed in your system.
- Keep in evidence: paturiet in dispatch and delivery confirmation no prījas perioda, lai prūkūtutu, uz kāda rēkumu kopuma pamata rēķins tika izszūts.
What is the difference between profile 01 and profile 02?
Profils 01 ir standarta process: pärdevæks sūta rēķinu vai kreidrēķinu, pircējs to sävem, un process ir sättät. Tā tehniskie identificatori ir fiksiti: CustomizationID jeb rēķina edištės deklarācijas identificatori ir `urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0`, un ProfileID jeb biznesa procesa identificatori ir `urn:fdc:peppol.eu:2017:poacc:billing:01:1.0`, kā tos fiksē current manual. Your existing XML after 3.0.21 does not have these values. Standarta rēķinu procesam šis izlaidums janu CustomizationID or ProfileID nenes.
Jauns ir tikika kombes profils 02, kas ar 3.0.21 pilizijajas procesam, kūr pircejam jāsūta apārībā saite par rēķinu, jeb rēķina answer - for example, a confirmation, ka rēķins ir ir sītāt vai noraidīts. Šis profils prasa sikku registraciju SMP or service Metadata Publisher (Service Metadata Publisher) in which Peppol tīkls stores information in which documents your company can accept, kā explains release notes. And your pircēji profilu 02 neipeprasa un neatbalsta, nav tägamas to registrät. Close profile 01 and add profile 02 only when a specific business partner directly requires it.
What does it mean for Igaunijā, Latvija un Lietuvā?
Estonia from July 1, 2025 spekke ir kontaktiyas likuma grozījums, ar kuru komercrejstrā par e-rēķina saimattu registrāts kontaktiyas subjekts var projāt, lai pārdevĪs tam prētitutu e-rēķinu, un rēķins tiek sītān par parākām preparātutu, and tas conforms to Eiropas standartam EN 16931-1, ja puses nav vienojušas par citu standartu.
In Latvia, the claim is clear, based on Peppol: Valsts eiženemu dienests strukturētu e-rēķinu is characterized as XML file, kura strukturai For Peppol BIS Billing 3.0 specification. G2G, B2G and G2B e-rēķins ir obligāts no 1. 2025. gada e-rēķins ir obligāts no 2025. gada.
Lietuvā e-rēķins virzās caur valsts platformu SABIS, ko Finanšu ministrija ir connected to the Peppol network. Practically speaking, also SABIS lietojošie Lietuvas pircēji and pārdevēji actually contacted using the same Peppol BIS Billing documents and profile as described in this article.
Why does rēķini prakti noraidīti tiek noraidīti?
Liela daħa ħawtu, kad “rēķins neaizgāja cauri”, it follows no piecu kāgītu sajaukšanas. EN 16931 ir Eiropas standarts, which generally describes the rēķina semantic data model. Peppol BIS Billing 3.0 ir šī standara CIUS or Core Invoice Usage Specification meets the requirements of EN 16931 in particular In the context of the Peppol network. Izlaiduma numurus, e.g. 3.0.20 vai 3.0.21, nav jauns standarts vai jauns rēķina formats - tas ir validationācijas un kodu ištuvi versijas updatāt taj pāša BIS Billing 3.0. SMP registracija, kas naka what profile your company is able to accept, ir atsevišķs tehnisks estättums, kas automatically nemainās til ar izlaiduma nomaiņu. Un PDF rēķins, kaut cik pārākti tas kākātotos, nav Peppol rēķins – tas ir pielikums, ko kārākā nelasa un neizvalidē põgs Peppol rēķins. Kad rēķins tiek noraidīts, first check kurus no šims pieciem elementiem īstenībā is missing, pēns pāsat aizāmāties, also “Peppol nebidorbo”.
FAQ
What changes in version 3.0.21?
3.0.21 uses the code lists published on March 6, 2026 and the UBL/CII validation artifacts in version 1.3.16. The most significant change concerns the rules PEPPOL-COMMON-R052 and PEPPOL-COMMON-R053, which become errors. Optional profile 02 is added.
What is the difference between profile 01 and profile 02?
Profile 01 is a standard invoice sending without a response. Profile 02 adds an invoice response process where the buyer must send feedback. Profile 02 requires a separate SMP registration.
What to check before August 17, 2026?
Ask the operator for written confirmation of the transition, update the validators, test with real data (R052 and R053), check the buyer identifiers (ICD codes 0246–0248) and keep the evidence.