Īsāk sakot: EN 16931:2026 ir published, bet Peppol to vēl įvāda
Uz 2026. gada August 15, answer ir sekana: nē, vēl nav. According to Eiropas Komisijas published report, 2026. gada maijā tika szättäta jauna Eiropas e-rēķinu datu modola verzija EN 16931-1:2026, un 2017. gada verzija tika officinii svettita. However, in the transition period 2017. gada modelis palik spekke. Peppol BIS Billing 3.0 obligātā version 3.0.21, kas stājas spēka 2026. gada 17. augāstā, sīdāt identifīkē rēķinus kā sātākus 2017. gada standartam, nevis jaunajam. Your company means this: on August 17, there will be no changes in the format, but within the framework of the existing 2017 model.
Is ir EN 16931, ja tas nav ne pārsūtīnas kanāls, ne faila format?
EN 16931 apraskata, kādīm datēm rēķinām įpūs satura, nevis kā rēķinam jāzīkātā. It is a semantic data model. Tā ir objajana par rēķina saturu un tā tārtuju, ko ertujujusi European Organization for Standardization CEN. Peppol šim modelim pārsūtīšanas netu, identificatorus un validationācijas rules. UBL XML (universal rēķinu rēķinušanas valoda) is the only format in which this data model can be expressed in text, which computers can automatically read. PDF rēķins šai definīcijai does not match. Tas nav strukturēts e-rēķins, jo dators nevar tā satura daļis automatically atpazīt un taksīt, kā to dara ar rēķinu.
Does EN 16931-1:2026 change and does it change?
Revīzijas dzinējspēks ir ViDA, Eiropas Säivienų prättätās värtätäs tägää direktis grozījums, kura text naka, also e-rēķiniem must comply with Eiropas e-rēķinu standartam un taļi listinātājām syntaxēm. This requirement came into effect on July 1, 2030. Publishing the standard in the new version does not mean pati par sevi, also for all companies rīt nāpāriet uz jano modeli: pēš Komisijas same page data, migrations plans in the member states vêl tiek käsätäti, un vienotu tämää Eiropas välä vêl nav nekkem.
How do you know if Peppol already complies with EN 16931:2026?
Version 3.0.21 to be published on May 20, 2026 It is mandatory on August 17, 2026, and you will not be able to register your choice in the home list. But the CustomizationID, damn it, is ir rēķina lauks technical regulation still prasa identificatoru, kis kontari ar "urn:cen.eu:en16931:2017#compliant". While this identifier is mentioned, it is safe to say that Peppol EN 16931:2026 does not apply. Nosaukums "2026. gada izlaidums" šo faktu nemaina.
What does it mean in Latvia and the EU?
The most structured e-account in Latvia must be in XML format and comply with the PEPPOL BIS Billing 3.0 specification. After VID data e-rēķins ir obligāts G2G/B2G/G2B segmentā no 2025. gada 1. janvāra, data transmission VID jāsāk no 2026. gada 1. janvāra, bet B2B szätos un pilns VID sätsätä sznegās tāssies stāsies spēka no 2028. gada 1. janvāra.
Every company, whether registered as an e-rēķina recipient in the company register, no 2025. gada 1. juila var var prājatā no pārīvātāja e-rēķinu; likums in accounting in Estonia accepts, also rēķins meets the requirements, and it complies with EN 16931-1, but it also has some common standards.
30 minutos kontrolsaraksts Your account software
Before you mention export in the settings or in saskarnes, pajautājiet savam softwares sūtātājam directly:
- Version and identifier: kuru Peppol BIS Billing 3.0 versión un CustomizationID vatutu we nosūtām today?
- Automatic update: vai 2026. gada 17. augusta uttättät stäs späke automätlichke, vai tam sukukana sikva no mämä puses?
- Validation before shipping: vai izejošie UBL rēķini un kreditrēķini tiek validēti pēns in sending?
- Transition plan: kakās ir sūtātāja sīdības planas irījai uz EN 16931:2026?
Uz Latviu adresētim Peppol rēķiniem so now it needs to be validated after the 2017 model, because CustomizationID still shows this version. Tas nemainās 17. augustā, kaut arī rēķina saturas, e.g. PVN distribuums un hāvēges numuri, tiek validēts pūs vāgātatiem sēlām.
FAQ
Does Peppol already use the EN 16931:2026 standard?
No, as of August 15, 2026, it is not used. Peppoli version 3.0.21, which will become mandatory on August 17, 2026, will still identify invoices according to the 2017 standard. This is indicated by the CustomizationID field in the invoice, which requires the identifier "urn:cen.eu:en16931:2017#compliant".
What is the difference between EN 16931 and Peppol?
EN 16931 is a European standard that describes what data should essentially be on an invoice – it is a semantic data model. Peppol adds to it a transmission network, identifiers and validation rules. UBL XML is one of the possible file formats in which this data model is expressed.
What does EN 16931:2026 mean for Estonian and Latvian companies?
In Estonia, a company can request an e-invoice from a supplier from 1 July 2025, which must comply with the EN 16931-1 standard. In Latvia, a structured e-invoice must be in XML format and comply with the PEPPOL BIS Billing 3.0 specification. In both cases, the 2017 model is currently valid.
When will EN 16931:2026 become mandatory?
According to the European Commission, migration plans are still being developed in the Member States and no general deadline has been set. The ViDA Directive requires e-invoices to comply with the European e-invoice standard from 1 July 2030.