BlueLandscape · Invoicing · Peppol
Peppol e-invoicing from day one.
UBL 2.1 / Peppol BIS Billing 3.0 XML on every sent invoice. The same standard the Dutch government, B2G buyers across the EU, and increasingly B2B accountants expect.
What is Peppol?
Peppol (Pan-European Public Procurement OnLine) is the European interoperability framework for e-invoices. Member states agreed on a single shared XML format — Peppol BIS Billing 3.0 — so an invoice issued in Amsterdam can be received and processed automatically in Madrid, Helsinki, or Vilnius. The Netherlands has required Peppol for B2G invoicing since 2017. For domestic B2B, the Dutch cabinet set a date on 11 September 2026: electronic invoicing becomes mandatory from 1 July 2030 (KOR small-business-scheme businesses are exempt); which channel that mandate runs over has not yet been decided.
Behind the spec is UBL — Universal Business Language. UBL is the XML schema; Peppol BIS is the business rules layered on top.
What you get with us
Every sent invoice carries the XML file as an attachment. The buyer's accountant downloads it and imports it directly into their bookkeeping — no re-typing, no OCR, no PDF parsing.
Tax categories — standard rate, reduced, zero-rated, exempt, reverse-charge — are emitted as the correct UBL `ClassifiedTaxCategory` codes (S / Z / E / AE) with the required exemption reasons. Intra-EU sales, exports outside the EU, and domestic reverse-charge are all first-class.
Generation versus delivery
Today we generate the XML and email it directly to your buyer. We do not yet submit it to a Peppol Access Point on your behalf — that's a separate integration (Storecove, Peppolapi.nl, etc.) we'll add when buyers ask for it.
In practice for freelancers + small teams, attaching the XML to the email is what most need today. If your buyer specifically needs Peppol Access Point delivery, you can forward the XML to your own Access Point provider.
Peppol endpoints
Both your own issuer profile and a buyer's company profile can carry a Peppol endpoint ID. When either is set, we emit it on that party in the XML (cbc:EndpointID) — the identifier a future Access Point integration would route on. Setting it doesn't make delivery automatic today: as above, we generate and email the XML but don't submit it to an Access Point ourselves yet.
No add-on tier for Peppol
Some invoicing tools charge extra for the e-invoicing module. We don't — UBL/Peppol comes with every €0.20 send. See pricing.
Create an account