If you invoice Belgian business customers, you have come across the word Peppol a dozen times without anyone telling you what it actually means. Your accountant mentions it, your software shows a “send via Peppol” button, and every article repeats that it has been mandatory since January 2026. Format, network, platform, standard: four words used as if they were synonyms. They are not.
The short answer fits in one sentence: Peppol is first and foremost a delivery network, not an invoice format. That distinction is not a vocabulary detail. It decides what your current tool really covers, what you are still missing, and what you need to budget for.
Peppol is not an invoice format
An electronic invoice is two separate things: a content and a delivery.
The content is the file itself. In Belgium, that means a UBL file: a structured document, readable by a machine, where every piece of information sits in a precise place. It is not a PDF, and it looks like nothing familiar when you open it.
The delivery is how that file travels to your customer. This is where Peppol comes in.
The most accurate picture is a postal one. The UBL file is the letter: its content, its layout, the mandatory details it must carry. Peppol is the postal service: a set of certified access points that pass items to each other under shared rules. Writing a flawless letter does not make it arrive. Having a postman does not make the letter correct.
The nuance almost nobody mentions
There is one point where honesty is needed, because it feeds the confusion, and most articles stop just short of it.
The word “Peppol” also covers a specification, called Peppol BIS Billing 3.0. It does not create a new format: it narrows the European standard EN 16931 by deciding, among the choices that standard leaves open, which ones are accepted on the network. So Peppol does impose rules on the content of the letter, but it remains, fundamentally, the postman.
The exact hierarchy, from general to specific:
- EN 16931: the European standard defining the mandatory minimum content of an electronic invoice
- UBL: the syntax, meaning how that content is written into a file
- Peppol BIS Billing 3.0: the additional rules imposed by the network
- Peppol: the network itself, which carries the file
If these acronyms are still unfamiliar, our e-invoicing glossary defines each one without jargon.
The two steps that always get confused
| Step | What it means | Who handles it |
|---|---|---|
| Produce | Turn your invoice data into a UBL file compliant with EN 16931 and the Peppol BIS rules | Your invoicing tool |
| Deliver | Place that file on the Peppol network and get it to your customer | A Peppol access point |
Neither replaces the other. A perfectly compliant file sitting on your hard drive does not make you compliant. An access point receiving a malformed file will not fix it.
The network runs on a four-corner principle: you hand your invoice to your access point, which passes it to your customer’s access point, which drops it into their system. Neither you nor your customer needs to know the other’s provider. That is exactly what makes the network useful, and also what makes it invisible, and therefore hard to understand.
What Belgium has required since January 2026
Since 1 January 2026, business-to-business electronic invoicing has been mandatory in Belgium. No revenue threshold, no phased transition by company size: the rule applies to a one-person company exactly as it does to a large group. We cover that timeline in our article on the Belgian obligation already in force.
In practice this means two obligations at once: produce a compliant structured file, and deliver it over the Peppol network. A business meeting only one of the two conditions is not compliant.
Exemptions exist depending on tax regime and type of activity. Your specific situation deserves a check with your accountant or with the Belgian tax authority rather than with an article.
Do you already have an access point without knowing it?
This is the most useful question to ask, and the answer is often yes.
Many Belgian businesses already have network access without having explicitly chosen it, because it is bundled somewhere:
- Your accounting or invoicing software may include an access point. The “send via Peppol” button is the giveaway.
- Your accountant may already be delivering on your behalf, through their own provider.
- Your ERP, if you run one, often has a dedicated module.
Three questions, in this order: do my invoices actually travel over the Peppol network? Which access point is being used? And does the service cover receiving as well as sending?
That last question matters more than it sounds. The Belgian obligation runs both ways: you must be able to send, and to receive.
To find out whether a given customer is reachable on the network, the Peppol directory is public: you look up a company by its enterprise number. If they are not listed, your invoice cannot reach them that way, whatever your provider does.
Three lines of reasoning that cost money
“My software sends via Peppol, so my invoices are compliant.” The network carries files, it does not rewrite them. Access points check technical compliance on submission, but not all with the same severity, and a file can pass at one end and be rejected at the other. Content compliance stays with whoever produces the file.
“I already email my invoices as PDFs, that is electronic.” A regular PDF is a picture of an invoice: readable by a human, opaque to a machine. Unless it is a hybrid format, which we explain in our introduction to Factur-X, though Factur-X applies to France and Germany, not to Belgium, which chose UBL.
“Peppol is for large companies.” True in several countries. Not in Belgium, where no threshold was set.
What if your file is right but you have no access point?
This is the most common situation for small businesses, and it deserves a straight answer rather than a sales pitch.
You have three routes. Your accountant, if they already deliver for their clients, which is usually the simplest and cheapest. Your invoicing software, if the vendor offers the option. Or a dedicated provider exposing network access, billed per document or by subscription.
In all three cases, the provider expects a correct UBL file from you. That is the common denominator, and it is where the most frequent problem sits: plenty of tools produce something that “looks like” UBL without following every rule of the standard.
Check before you send
A rejected file does not always tell you, and your customer’s payment terms keep running in the meantime.
You can check an existing file for free: upload your XML or PDF and the EN 16931 compliance report appears immediately, with no account to create. It is a technical check that takes seconds, and nobody should be charging you for it.
If you need to produce the file rather than check it, Factilix generates compliant UBL invoices for your Belgian and Dutch customers, with automatic validation before download. Let us be clear about who does what: Factilix builds the file, it does not deliver it over the Peppol network. That part stays with your accountant, your software, or your access point.
It is a deliberate limit, and it has a useful flip side: the file you get works with any access point at all. You are not locked in to anyone.
Article published on 10 August 2026. The Belgian obligation was verified against an official source (finances.belgium.be). Rules can change; always check the most recent version with the relevant authorities or your adviser.