How Peppol Works: A Plain-English Guide for European Contractors

Peppol is the electronic network over which businesses and governments across Europe exchange invoices, purchase orders, and other business documents in a standardised format. If you are a trade contractor in Belgium, the Netherlands, Norway, or increasingly Germany, France, or Spain, you will increasingly encounter clients — particularly public authorities and large companies — who require invoices to be sent via Peppol rather than as PDF files attached to emails. Understanding how Peppol actually works, at a conceptual level, helps demystify what can sound like impenetrable technical language and reveals that the experience for the end user is considerably simpler than the infrastructure beneath it.

The Problem Peppol Solves

Before Peppol, electronic invoice exchange between businesses and governments was fragmented: each buyer had their own portal, their own format, and their own technical requirements. A subcontractor working for a Belgian municipality, a Dutch housing corporation, and a German federal agency would need to access three different portals, register separately with each, and format invoices differently for each. The administrative overhead was often worse than simply posting a paper invoice. Peppol solves this by creating a single network with a single set of rules: a business connects once to an access point, and from that single connection can send documents to any other participant on the network, anywhere in the world, in any country where Peppol operates. The analogy is the email system: you use Gmail, your client uses Outlook, and you can still exchange emails because both services connect to the same underlying internet infrastructure. Peppol is the construction-invoice equivalent of that infrastructure.

The Four Corners: Sender, Sender's Access Point, Receiver's Access Point, Receiver

The four-corner model is the technical architecture underpinning Peppol. Corner one is the sender — the trade contractor issuing the invoice. Corner two is the sender's Peppol Access Point — a certified service provider connected to the Peppol network that validates and transmits the invoice on the sender's behalf. Corner three is the receiver's Peppol Access Point — another certified service provider that receives the invoice from the Peppol network and delivers it to the receiver's system. Corner four is the receiver — the client who receives the invoice. The sender never connects directly to the receiver: the two access points handle the transmission between them, routing the document via the Peppol network. For the contractor, the practical experience is simply pressing "send" in their invoicing software; everything that happens in corners two and three is invisible.

Peppol IDs: How Invoices Reach the Right Recipient

The routing mechanism that makes the four-corner model work is the Peppol ID. Every Peppol participant is registered in a distributed directory — the Service Metadata Publisher (SMP) — with a Peppol Participant ID that uniquely identifies them on the network. For businesses in most EU countries, the Peppol ID is based on the company's tax identification number or VAT number, combined with a country code scheme identifier. For example, a Belgian company with VAT number BE0123456789 might have the Peppol ID 0208:0123456789 (using the Belgian scheme 0208 for CBE numbers). When a contractor in the Netherlands wants to send an invoice to that Belgian company, they enter the Belgian company's Peppol ID in QuotCraft, and the network automatically locates the Belgian company's access point via the SMP directory and routes the invoice to it. No manual addressing, no knowledge of which access point the receiver uses.

The Peppol BIS Billing 3.0 Format: What Gets Transmitted

The document format transmitted over the Peppol network for invoices is Peppol BIS Billing 3.0 — Peppol's implementation of the European standard EN 16931. It is an XML file containing all the invoice data in a structured, machine-readable format: seller and buyer details, invoice lines, VAT breakdown, payment terms, and a reference to the legal document exchange. The XML file is not something the contractor ever sees or touches: their invoicing software generates it automatically from the invoice they create in the normal way. At the receiving end, the buyer's accounting system parses the XML and posts the invoice data directly to the relevant accounts — no human rekeying required. The format is validated at both the sending and receiving access points against a set of Peppol business rules, ensuring that only correctly structured invoices are transmitted. An invoice that fails validation is returned to the sender with an error message identifying the problem.

Peppol for Public Sector Invoices: Mandatory Across Europe

The original driver for Peppol adoption in Europe was public procurement: the EU Directive 2014/55/EU on electronic invoicing in public procurement requires all central government contracting authorities in EU member states to be able to receive electronic invoices in the EN 16931 format. In practice, many public authorities have implemented this via Peppol. In the Netherlands, the central government has been on Peppol since 2012. In Belgium, federal authorities are on Peppol and the mandate extends progressively to regional and local authorities. In Norway (an EEA member), Peppol-format invoicing has been mandatory for public sector suppliers since 2012 — one of the earliest mandates anywhere. In Denmark, the NemHandel network, which preceded Peppol, has been mandatory for public suppliers since 2005 and is now integrated with the Peppol network. For a trade contractor who wins public contracts — building maintenance work for a municipality, electrical installations for a school, HVAC servicing for a government office — Peppol connectivity is effectively a prerequisite.

Peppol Beyond the EU: Norway, Iceland, Switzerland, Australia, Singapore

One of the less well-known aspects of Peppol is that it extends well beyond the EU. Norway and Iceland, as EEA members, are full Peppol participants. Switzerland, while not an EU or EEA member, is connected via its own e-billing infrastructure that interoperates with Peppol for international transactions. Outside Europe, Australia and New Zealand use a Peppol-based network (A-NZ Peppol) for B2G e-invoicing, and Singapore has its InvoiceNow network on Peppol. This means that a European contractor with an Australian or Singaporean client — perhaps an international construction firm or a multinational facilities management company — can send invoices via Peppol even across those non-European borders. For most European trade contractors, this international dimension is not immediately relevant, but it illustrates the global reach of the infrastructure they are connecting to.

Becoming Peppol-Connected Without Technical Knowledge

The barrier to Peppol connectivity for a trade contractor is lower than most assume. They do not need to procure a server, learn XML, or negotiate with a technical team. They need only to use an invoicing or quoting platform that is itself a certified Peppol Access Point, or that is connected to one. The contractor creates an account, enters their business details (including their VAT number, from which their Peppol ID is derived), and their registration on the Peppol network is handled by the platform. From that point, sending a Peppol invoice is identical to sending any other invoice: create it in the platform, enter the client's details (including their Peppol ID if they have one, or select from a directory lookup), and send. The platform handles corners two and three of the four-corner model entirely.

How QuotCraft Functions as a Certified Peppol Access Point

QuotCraft is a certified Peppol Access Point, authorised by OpenPeppol to operate on the Peppol network. This means that any contractor using QuotCraft is automatically connected to Peppol without needing a separate access point subscription. When a Belgian electrician in QuotCraft sends an invoice to a Dutch project developer, QuotCraft's access point transmits the Peppol BIS 3.0 XML document to the Dutch company's access point via the Peppol network. The Dutch company's ERP receives the invoice data automatically. For the Belgian electrician, the experience is simply pressing "send" on a completed invoice — the Peppol transmission is invisible. QuotCraft also supports receiving Peppol documents: if a subcontractor or supplier sends a Peppol invoice to the contractor's Peppol ID, QuotCraft receives and stores it automatically in the contractor's invoice inbox, ready for approval and payment.