What is Peppol?
Peppol is an international network that lets organisations exchange structured business documents without agreeing on a format beforehand. The name stands for Pan-European Public Procurement On-Line, which describes where it came from rather than what it is used for today, where the dominant document is the commercial invoice.
The comparison with email is imperfect but useful. You choose a provider, you get an address, and from that moment you can write to anyone regardless of which provider they chose. Peppol works the same way: a company connects to one certified access point, receives an identifier, and can then exchange with every other participant on the network. There is no bilateral agreement to negotiate, no per-partner mapping to maintain, and no customer portal to log into one by one.
What travels is the part that matters. A PDF attached to an email is a picture of an invoice: a human reads it and retypes the figures. A Peppol document is a structured XML file, normally in UBL format following the Peppol BIS Billing specification, where every field is labelled. The recipient's system reads the VAT number, the amounts, the due date and the line items directly, and books them without transcription. That is the entire economic argument, and it is why the format is specified so tightly.
Why Peppol matters
For a Belgian company the answer changed on 1 January 2026, when structured electronic invoicing stopped being an efficiency project and became a legal obligation.
- The obligation is in force. Every business registered for VAT and established in Belgium must issue and receive structured electronic invoices for its domestic business-to-business transactions. Sending a PDF by email no longer satisfies the requirement.
- The exemptions are narrower than most people assume. They cover bankrupt entities, VAT subjects without a Belgian establishment, businesses under the flat-rate regime, which itself disappears by 1 January 2028 at the latest, and companies whose activity consists only of operations exempt under Article 44 of the VAT Code. Everything else is in scope.
- Non-compliance carries a tariff. The Royal Decree of 8 July 2025 sets escalating fines of 1,500 euros for a first breach, 3,000 for a second and 5,000 thereafter.
- The transition is subsidised. Small businesses and self-employed workers can deduct 120% of the additional subscription cost attributable to electronic invoicing, for tax years 2024 to 2027, and the investment deduction was raised to 20% from 1 January 2025.
- It removes friction rather than adding it. Once connected, invoices stop being retyped, arguments about whether a document was received disappear because delivery is acknowledged at protocol level, and payment cycles shorten because the invoice arrives already booked.
The strategic point is easy to miss in the compliance rush. A mandate that puts every counterparty on a common structured format also removes the main obstacle to automating the rest of the purchase-to-pay chain. Companies that treat 2026 as a box to tick will connect and stop there. Companies that treat it as clean machine-readable data arriving at their door will build approval, reconciliation and reporting on top of it.
How it works
Four parties take part in every exchange, which is why the design is known as the four-corner model.
The sender issues the invoice from its accounting package or business application. The sender's access point, a certified service provider, validates the document against the specification and routes it. The recipient's access point receives it and delivers it. The recipient books it in its own system. Neither company needs to know which provider the other uses, and that property is what makes the network scale.
Routing relies on a directory. Each participant is registered under an identifier, in Belgium normally the enterprise number, and a lookup service tells the sending access point where to deliver and which document types the recipient accepts. Transport uses AS4 over TLS with acknowledgement at each hop, so a sender knows whether delivery succeeded instead of hoping an email was opened.
Validation is the part that surprises newcomers. A document that does not satisfy the specification is rejected by the access point before it reaches the recipient, and the usual causes are mundane: a missing enterprise number, a VAT rate that does not match the amount, a unit of measure outside the code list. This is a feature, not an obstacle. It moves error detection from the recipient's accounting team to the moment of sending, where correction is cheap.
Implementation
The sequence below is ordered by cost, cheapest first. Most companies stop at step two.
- Check what your existing software already does. Most accounting packages sold in Belgium added Peppol capability during 2025. If yours has it, connecting is a configuration task measured in hours rather than a project.
- Register your enterprise number with one access point and send a real invoice to a real customer. One successful exchange tells you more than any vendor demonstration.
- Verify what you receive, not only what you send. The obligation runs both ways, and inbound handling is where most projects are incomplete. A structured invoice that lands in a folder nobody opens is worse than a PDF.
- Map the fields your business actually depends on. Purchase order references, cost centres, project codes and payment terms have defined places in the specification. Putting them in a free-text note works technically and defeats the purpose.
- Connect the in-house applications last. If invoices originate in a custom application, a FileMaker solution or a module built for you, the work is a genuine integration: producing compliant UBL, handling rejections, recording delivery status. Budget it as development, not as a subscription.
That last point is where the market is thinnest. Off-the-shelf packages are well served. Companies whose invoicing lives inside a bespoke application face a different problem: the document has to be produced correctly from data that was never modelled for it, and rejections have to surface somewhere a human will see them. It is not a hard integration, but it is one that no subscription solves on its own.
Related technologies and tools
- UBL: the XML vocabulary in which Peppol invoices are written, so the recipient's system reads each field by name rather than by position.
- Peppol BIS Billing: the specification that narrows UBL to one agreed interpretation, including the validation rules an access point enforces.
- AS4: the transport protocol used between access points, providing encryption and delivery acknowledgement.
- Access point, also called a Peppol service provider: the certified intermediary that connects you to the network. You need exactly one.
- The Peppol Directory: the public register of participants and the document types each accepts, which is what makes routing possible with no prior agreement.
Conclusion
Peppol is infrastructure, not software. The decision it forces is small for most Belgian companies and genuinely involved for a minority. If invoices come out of a standard package, connecting is configuration. If they come out of an application built for you, it is an integration project with a rejection-handling requirement that is easy to underestimate and expensive to discover late.
The mistake worth avoiding is buying before checking. A company that signs with a new provider while its accounting software already supports the network pays twice for one connection. The first useful action costs nothing: confirm what your current tools support, then send one real invoice and read the acknowledgement.
