Peppol E-Invoicing Integration for Your Own Systems
Since 1 January 2026, Belgian companies liable to VAT exchange structured e-invoices with each other over the Peppol network, and a PDF sent by e-mail no longer counts. If your invoices are created in an ERP, a webshop or software built for your business rather than in a standard accounting package, that system needs its own connection. We build that connection, so invoices leave from where they are created and incoming ones land where they are processed.
Technical help, not legal or tax advice: VAT treatment and bookkeeping stay with your accountant.
What the Belgian obligation asks of your systems
Since 1 January 2026, all Belgian enterprises liable to VAT must use structured electronic invoices with each other. These invoices are exchanged directly between the two companies' software, over a decentralised network called Peppol, and the government's e-invoicing site, einvoice.belgium.be, states that a PDF sent by e-mail or through a platform is no longer enough. For your systems that means three things:
- Sending: invoices to other VAT-liable Belgian companies leave your system as structured data, not as a PDF attachment.
- Receiving: structured invoices from your suppliers have to reach you, even if you only invoice private individuals.
- Data: the receiving software reads the invoice field by field, so what your system fills in is what the other side processes.
Peppol in Belgium: what is a Peppol invoice?
A Peppol invoice is a structured electronic invoice: the amount, the date and the VAT are read automatically by the receiving software, with no retyping. It travels over the Peppol network, a secure network that the government's site einvoice.belgium.be compares to a telecommunications network. It is in principle drawn up in the Peppol BIS format, which follows the European standard for electronic invoicing (EN 16931) and is built on UBL, a standardised XML-based method. A PDF invoice sent by e-mail is not a structured electronic invoice, because the receiving side cannot process it automatically. The software produces the format, not you: it is to this structured format that we convert the data of your ERP, your webshop or your custom software.
Where your invoice is created decides the work
The first question is not which tool to buy, but where your invoices are made today.
-
A standard invoicing or accounting package
Many packages already send and receive over Peppol, and the government keeps a list of software applications for it. If your invoices are made in one of them, there is usually nothing to build: check that it handles both directions and switch it on there.
-
An ERP, a webshop or software built for you
If invoices are created in an ERP, a webshop or a custom platform, that system needs its own connection to a Peppol access point, so invoices leave from where they are made and incoming ones arrive where they are processed.
How we connect a system to Peppol
The same six steps whether the source is an ERP, a webshop or a platform built for your business.
-
1
Map the invoice data
We map your invoices and credit notes, VAT numbers and units to the structured format Peppol carries, and list the fields your system does not fill in yet.
-
2
Connect the access point
We connect your system to the access point you choose, through its API. We do not resell access points.
-
3
Check before sending
Each invoice is checked before it leaves. A rejected one comes back to your team with the reason, instead of disappearing.
-
4
Write the status back
Delivery and status messages are written back into the source system, so your team sees what happened to each invoice where it already works.
-
5
Import incoming invoices
Structured invoices from your suppliers are imported into the system that processes them, ready for approval and booking.
-
6
Test before go-live
Everything runs against a test environment before the first real invoice is sent.
Choosing an access point
An access point is the service provider that connects your software to the Peppol network. The choice is yours, and we do not recommend a vendor. For an integration, these are the questions worth asking each candidate:
- Does it send and receive, or only send?
- Is there a test environment you can use before go-live?
- How does its API report delivery and errors?
- Does it suit the number of invoices you send and receive?
When a ready-made package is the better choice
If your invoicing already happens in a package that sends and receives over Peppol, switching it on there is simpler than building an integration, and we will tell you so. An integration makes sense when invoices are created in a system such a package does not reach: an ERP, a webshop or a platform built for your business.
Your accountant stays involved
Which invoices fall under the obligation, their VAT treatment and their booking stay with your accountant or tax adviser. The integration moves invoices between systems and shows their status; it does not replace that advice, and we do not give legal or tax advice.
What drives the effort
We give no figures before we have seen the setup. These are the factors that decide how much work a connection takes:
- How many systems create invoices
- Sending only, or sending and receiving
- How clean the invoice data is: VAT numbers, units, credit notes
- How delivery and status messages need to be handled
- How many invoices pass through each month
- Whether the chosen access point offers a usable API
Beyond Belgium
France and Germany have their own e-invoicing rules and formats, and the way we connect a system is the same there: map the data, connect, check, write the status back. Their timetables are summarised in the FAQ on our system integration page, and our article Peppol, Factur-X or XRechnung: which e-invoice format? compares the formats.
Peppol e-invoicing: frequently asked questions
Tell us where your invoices are created
Name the systems involved and whether you need to send, receive or both. We reply in writing with what the connection would involve.
Describe your invoicing setup