“Peppol-compliant” does not mean one thing, but three separately verifiable things: the invoice XML file (machine-readable file format) complies Peppol for BIS Billing 3.0 standard, the invoice moves through a certified access point (Access Point) and the recipient, whether a company or a public platform, has actually received and processed the invoice, not simply received it. Peppol interoperability framework The sending access point must validate the outgoing invoice before sending, but this only proves technical correctness, not that the customer actually approved the invoice. From August 17, 2026, it is mandatory BIS Billing version 3.0.21, published on May 20, 2026. When your software vendor talks about “Peppol readiness,” ask for evidence of all three points, not just one.

What does Peppol compliance actually mean?

The problem with many e-invoice vendors“ marketing is that ”Peppol-compliant” sounds like a single entity, but in reality it is a matter of three independent layers. The first layer is the invoice content: does the XML comply with BIS Billing 3.0 rules? The second layer is the transport: does the invoice travel through a Peppol-certified access point, which is part of the 4-corner model, where the sender and recipient each connect to their own service provider only. OpenPeppol framework According to the regulation, access points may only provide Peppol services after signing the Peppol Service Provider Agreement and passing the compliance test. The third layer is acceptance: whether the recipient's system actually processed the invoice. This is where most disputes arise: the software shows "sent", but this does not mean that anyone on the other side ever opened the invoice.

How to check software for Peppol compliance in 20 minutes?

This can be done without involving the IT department.

  • Identify the real operator: Check your software contract or settings to see who the actual sender of the invoice is in the Peppol network. This is usually not the accounting software brand, but the service provider behind it.
  • Check legal name: search for that name From the list of OpenPeppol certified service providers, last updated on August 28, 2026.
  • Request valid sample XML: Ask the seller for a real, currently generated invoice file, not a demo from years ago.
  • Do the end-to-end test: Send this invoice to a real Peppol address and check to see if you also receive a confirmation of receipt, not just a confirmation of shipment.

This is where most entrepreneurs get confused. Accounting software itself cannot be “Peppol certified”. Only a service provider that acts as an access point or SMP (Service Metadata Publisher, which publishes recipient data to the network) can receive the certificate. If the software exports XML and shows the Peppol logo, this does not automatically mean that the invoice is moving through a certified channel. See from the list of certified service providers exactly under whose legal name the Peppol Service Provider Agreement has been concluded, and note that the country field in the list shows the registered location of the service provider, not the region of operation. A customer registered in Estonia may receive service from a company that is officially registered elsewhere.

Are the invoice format and validation certificates still correct?

The correct XML format is one thing, its ongoing maintenance is another. Peppol BIS Billing v3 release information confirms that version 3.0.21 was released on May 20, 2026 and became mandatory on August 17, 2026. Ask the vendor in writing if their system already works with this version. The new version also added an optional profile “Billing with Response”, which requires a separate SMP registration. This means that just supporting standard invoicing does not prove that the software supports all Peppol workflows that your business partner may need.

Was the invoice actually sent or received?

The sending status, technical validation and the actual procedure are three different things. The Lithuanian example makes this concrete: the National Service Centre under the Lithuanian Ministry of Finance you know According to the report, over 4,500 Peppol invoices sent to the SABIS platform in May 2026 were not processed at all. This is 51% of the monthly Peppol shipments. According to the same report, only 131% of the incorrectly submitted invoices were later returned without correction. The reason is simple: the invoice was not processed if there was no contract or if the buyer, seller or contract code did not match the data in the system. The Peppol notification “sent” does not check these fields.

What checks should be done before launching Peppol in the Baltics?

Estonia

In Estonia, an accounting entity or its contractual e-invoice handler can submit to the commercial register data that it wishes to accept only machine-readable e-invoices. The same law assumes that an e-invoice is properly prepared if it complies with the EN 16931-1 standard, but the parties may also agree on another suitable standard.

Latvia

In Latvia, the structured e-invoice XML file must comply with PEPPOL to BIS Billing 3.0 specification. G2G, B2G and G2B invoices are mandatory from 1 January 2025, and from 1 January 2026, data on these invoices must be submitted to the State Revenue Service (VID). B2B invoices will become e-invoices and submission to the VID will be mandatory from 1 January 2028, in the meantime (from 1 January 2026 to 31 December 2027) data can be submitted voluntarily.

Lithuania

In Lithuania, it is worth considering that SABIS does not automatically confirm receipt of the invoice: as described above you know invoices are not processed precisely because of the mismatch between the codes and contract data, so it is worth checking the partner's codes separately before sending in large quantities.

What to ask a software provider today?

  • What is the legal name of your Peppol access point and is it listed? On the list of OpenPeppol certified providers?
  • Which document profiles (Billing, Billing with Response, Self-Billing) does the software support and which ones require separate SMP registration?
  • Does the system validate invoices? BIS Billing 3.0.21 rules according to and when was this version implemented?
  • How can I check before sending whether the recipient's Peppol address and their supported document profile match?
  • What error messages appear if an invoice is not processed on the recipient's side, and how do I find out about them?
  • What is the vendor update schedule when Peppol releases a new mandatory version?
  • What proof will I receive after sending a real test invoice – shipping confirmation, receipt confirmation, or both?

FAQ

What does Peppol compliance mean in three layers?

The first layer is the compliance of the invoice XML format with the BIS Billing 3.0 standard. The second layer is the transport through a certified access point. The third layer is the actual receipt and processing by the recipient, not just confirmation of sending.

How to check software for Peppol compliance in 20 minutes?

Identify the actual operator from the contract, check their name against the OpenPeppol certified provider list, request a valid sample XML, and complete the entire test invoice sending process to a real Peppol address.

Should I check the access point or software logo?

Only the service provider that acts as an access point can receive the certificate. The Peppol logo in the software does not automatically certify a certified channel – always check the OpenPeppol list.

What to ask the software provider before launching Peppol?

Ask for the legal name of the access point, supported document profiles, BIS Billing 3.0.21 version deployment date, and error messages about unprocessed invoices.