The same PDF does not mean the same Peppol e-receipt

Peppol (Eiropas škelas e-rēķinu uttässäs tīkls) validates the structured account data, as it looks like in a PDF file. Before sending, three separate layers must be checked: XML file structure, satura saturātība standartam EN 16931 (Eiropas e-rēķina satura standarts, kas nakama, kādiem datam irīkā ir kūbā), un Peppol paše biznesa ruleikumi, kas collected in the BIS Billing 3.0 speikātītācijai. According to ar openPeppol documentation, the message is considered appropriate, and according to the currently valid rules, no fatal error is detected. Brīdinājum does not affect compliance. Tikpat väyätä sädäties, too validation tools check tikika pashu rēķina ľišu, nevis to, vai pirceja sistema to gebässä akceptēs vai apmaksās. Starp zaļo innuu validationācīje un „rēķins ir apmaksāts” ir vēl several soļi.

How does the five salt test look when you press the "Sūtīt" button?

Process, regardless of whether you use an ERP system, accounting software or operator portal:

  • Export XML: Ubljiet no rēķina fileu in UBL or CII format. No validation is possible at all.
  • Run the schema un business rule check: first strukturs kontrolle, tad Schematron noteikumi (valoda, whether verifies the XML in internal sasaistes), whether verifies in the sum, home un lauku savstarpējo compliance.
  • Eliminate fatal errors: according to openPeppol rules The customer may not send a message if it does not comply with BIS. Tas ir stingrs noteikums, nevis ieteikums.
  • Check the recipient's Peppol readiness: svättät, ka pircējs ir registrärts sättät un sägät sättät äätä to dokumenta sävät, ko sūtāt.
  • Save the validation result: paturiet report and delivery confirmation. Tas ir prīms, ko jums prasīs, ja rēķins „pazūd”.

Which validators are suitable for use?

XSD, or XML Schema, checks whether XML is correct or not. Stūra iekavas ir sārābīgajā Ṭṭṭa, sāmābībī elementi ir kārāt. Schematron verkere citu lietu: biznesa svettel un elementu savstarpējs sasaistes, e.g. vai rindu sum sakrīt ar rēķina kūpsummu. According to Eiropas Komisijas explanation, . For this purpose, Komisija offers free validation service, kuram nav navkuma registracija un kuru Latvijas VID directly recommends using an XML rēķina in the VID system. Ja rēķinus sūtāt caur operatoru vai kontaktijas software, kas validationāciu veic veikārī, katru rēķinu manualu rīkā verkater nav nav nejat. It's acceptable in everyday situations, but when testing new XML generation logic, it's worth using a separate, no-nonsense tool.

Let's report: fatala saksa põis, uttääjums pös

Fatāla sämä sätä, ka rēķins doesn't match BIS un to mähä säutä. Brīdinājums prīdī, ka rēķins tehnīski ir sīmāsāms, but it deserves attention. In practice, the most common problems arise in five places: in the buyer's and buyer's identifier (incorrect scheme or incorrect registration code), in the PVN category, in the title, in the kopsummas värtībās (knife errors are easily izklīs), in the payment summā with the currency code, and with the payment of the tax return. And 100 eur plus 22% PVN was indicated in the account line, but in the total amount, the validator will find a fatal error, and it is justified, because exactly this amount goes into the buyer's accounting.

How do you verify the delivery of the product?

According to Satura, the correct rēķins does not mean that it also reaches its destination. Peppol satura un biznesa tetutu ir viena lieta ir viena lieta, routing pa Peppol nettu ir cita. Before sending, it's worth checking whether the end point of the buyer supports exactly the type of document you want to send. Peppol Directory ir publiski šečijams registrerto sāniņu sarakts, tā tā pīvlšana ir tēljum pērējēju responsibility, nevis obligation. That's why there are absolutely no corrections to the recipient market. And if you're wondering, you're asking exactly what Peppol's identifier is, nevis paluäties uz to, also Directory parādīs visu.

Will it change in August 2026?

BIS Billing 3.0 version 3.0.20 (copā ar hotfix labojumu) ir biluta sādībāmā sādītā ar 23.02.2026, bet new version 3.0.21 becomes mandatory on 17.08.2026. Izmainas labo elektroniskās adreses škemas (EAS - kods, kas nadara, kura sistema ir registrāts company identificator) kodu saraksta kurūtu un izēm 14 nedarbojohos kodus, sūra tārašā ar veco validatoru var uzrādt nepareizu resultu. Šī pati verzija pīdās sīdās profilu, aka sāmātā sāmātā sāmālū pārība jumu par rēķinu (invoice response) dħu tam nekuma sīdga SMP registracija, un tas teīd automikāt adjoats katram rēķinam. And if you use the ready solution, ask the operator in writing, kad tas artefactus pärcels uz jano versioni; and XML veidojat pats, update validations rules before 17.08.2026, otherwise your software will validate the account according to rules that Peppol no longer accepts.

Estonia and Latvia: local tests

Every company is included in the commercial register as a recipient of an e-rēķinu, starting from 01.07.2025 var projat no pärdeväja e-rēķinu standartā EN 16931-1. Rēķins whether it meets šim standardam, tiek sūtān par properly prepared. This does not mean that Peppol Igaunijā ir obligāts katram B2B rēķinam. That means vien to, ka registrertais saimečeks var projat šo formatu.

Laika graphics in Latvia are complicated. VID explain, also e-rēķini B2G, G2B un G2G transaktionās ir sāmābī no 01.01.2025, un e-rēķina datu iesneštīga VID became mandatory no 01.01.2026, dati jēiēssīd ne later kā piecu darba dienė kaiām pēš rēķina sīpākas. In the B2B segment, the provision of data is voluntary until the end of 2027, but VID recommends that before submitting the XML file, it is checked in the same Eiropas Komisija's free validation service, which you also use as a Peppol account. Shie divi geħħalie obiābi, satura sāvlaħība un savlaħa iesneštīga VID, ir vaťas verkater atsevišķos sarakstos, nevis venā reizē pałęties, ka operators visu sedz automatically.

FAQ

Does a valid PDF mean that the Peppol e-invoice is validated and suitable for sending?

No. Peppol validates the structured e-invoice message data (XML), not the PDF appearance. The XML structure, EN 16931 content, and Peppol/BIS Billing 3.0 business rules must be checked separately before sending.

What are the 5 steps before sending a Peppol e-invoice?

First, export the invoice to XML (UBL or CII). Then run a schema and business rules check. Fix fatal errors according to BIS compliance, check the recipient's Peppol capability, and save the validation report and confirmation.

What is the difference between schema (XSD) and business transaction (Schematron) validation?

XSD checks whether the file is correct XML: mandatory elements and structure. Schematron checks business rules and relationships between elements, for example, whether row and total amounts match.

What will change with the new version of BIS Billing 3.0 from August 17, 2026?

The new BIS Billing 3.0 version 3.0.21 will become mandatory on 17.08.2026. The change fixes an error in the Electronic Addressing Scheme (EAS) code list and removes 14 non-working codes that could give an incorrect result with the old validation logic.