Introduction
PEPPOL in Belgium handled government procurement invoices for years before the 2026 mandate extended it to private-sector B2B. The network infrastructure was already functioning. What the mandate changed was the obligation — every domestic B2B transaction between VAT-registered companies now has to use it. That shift brought a significant number of businesses onto the network in a short period, which also surfaced the implementation gaps that tend to emerge when onboarding happens under deadline pressure. This guide covers how the network operates and how to join it correctly. Cross-border businesses trading with partners that follow the digital e-invoice process New Zealand uses can extend the same compliant infrastructure across both markets. PEPPOL in Belgium is becoming a standard requirement for VAT-registered businesses operating in Belgium.
The Four-Corner Network Model
The four-corner architecture is the design principle that makes PEPPOL in Belgium decentralised. The seller’s ERP connects to the seller’s access point. The buyer’s ERP connects to the buyer’s access point. The two access points exchange the invoice across the network. That is it. No government server sits between them. The delivery confirmation comes from the buyer’s access point, not from a tax authority clearance step. This is structurally different from France or Italy, where invoices pass through a central government portal before reaching the buyer. Understanding PEPPOL in Belgium early gives finance teams a significant head start before enforcement begins.
Belgium invoice network participants are identified by a PEPPOL participant identifier linked to the Belgian enterprise number. The identifier must be published in the PEPPOL SMP before any invoice can be delivered. The sender’s access point queries the SMP before each transmission to confirm the receiver is listed. If it is not, the invoice has no valid destination in the network and cannot be sent through PEPPOL. The scope of PEPPOL in Belgium continues to expand as FPS Finance rolls out each compliance phase.
What Accredited Access Points Do
PEPPOL in Belgium requires an OpenPEPPOL-accredited access point on both sides of every transaction. The access point on the sending side validates the XML against EN 16931 schematron rules, handles the network addressing, routes the invoice to the receiver’s access point, and returns a delivery acknowledgement. The access point on the receiving side validates the incoming XML and delivers it to the buyer’s ERP. BOSA, Belgium’s PEPPOL Authority, maintains the accredited provider list and the national PEPPOL directory. Businesses preparing for PEPPOL in Belgium should prioritise master data accuracy across customer and supplier records.
PEPPOL access point Belgium selection should be driven by ERP connector availability and Belgian onboarding experience— not just per-invoice pricing. A provider that has handled Belgian PEPPOL implementations across many ERP platforms will have practical experience with the field mapping problems and directory registration issues that appear in real implementations. A newer entrant may offer attractive pricing but less operational depth. PEPPOL in Belgium compliance depends on having the right ERP connectivity in place before the deadline.
Invoice Format Requirements on PEPPOL
PEPPOL BIS Billing 3.0 is the message specification used for Belgian domestic B2B invoices. Invoices must be UBL 2.1 or CII D16B, conforming to EN 16931. Schematron validation at the access point checks every mandatory field against the specification. Tax category codes must use EN 16931 values. Dates must be ISO 8601. Party identifiers must match the registered format. An invoice that looks complete in a human review can still fail if any of those field-level requirements are violated. Getting PEPPOL in Belgium right from the outset avoids costly remediation work later in the rollout.
Electronic document exchange Belgium rejections carry error codes that can be mapped to specific ERP configuration or master data issues. Date format errors and incorrect tax category codes. Building an internal error code reference during the sandbox testing phase — before going live — means rejections in production can be diagnosed and resolved quickly rather than escalated to the access point provider every time. PEPPOL in Belgium requirements apply equally to domestic and cross-border B2B transactions within Belgium.
Archiving Under PEPPOL Rules
PEPPOL in Belgium carries a seven-year archiving obligation on both sides of every invoice exchange. The original XML must be retained in unaltered form. A PDF version alongside it is acceptable for human readability — but FPS Finance audits require the XML, not the PDF. Access point archiving services typically include a retrieval interface where specific invoices can be located by date or VAT number. Test the retrieval process before go-live — confirming that a specific archived invoice can be produced on demand is more useful than being told it is technically possible. Teams running Microsoft Dynamics integration benefit from pre-built connectors that simplify structured invoice delivery.
The archiving obligation runs for the life of the records — and that outlasts most access point contracts. A provider relationship that ends in 2028 still has four more years of archiving obligation attached to invoices sent in 2026. The archive must be migrated to a new storage location before the provider relationship terminates. Explicit archive export rights in the contract — the right to export in a portable format on termination — are the practical protection against that problem.
Inbound PEPPOL: Processing Received Invoices
PEPPOL in Belgium compliance covers receiving as much as sending. When structured invoices arrive from PEPPOL-connected suppliers, they must be received through an active inbound connection and processed by the AP system automatically. A business that downloads XML files manually from an access point portal and re-keys them into the ERP has not built an inbound PEPPOL channel — it has replaced one manual process with a slightly different manual process.
Belgium compliance system for inbound also requires a rejection notification workflow. When an inbound invoice fails validation at the buyer’s access point, a structured rejection notification should go back to the supplier. Businesses that accept all inbound invoices without validation — or that have no automated rejection process — are carrying an inbound compliance gap that audit records will reveal.
PEPPOL Directory: How to Check Trading Partner Status
PEPPOL in Belgium directory checks should happen at two points in a project. First, early in the implementation: use the BOSA lookup tool to check every key supplier and customer. Identifying which partners are not yet registered at the start of the project gives time to manage those gaps. Second, after each round of onboarding: verify that new registrations have propagated correctly and that the identifier format matches what the ERP is configured to use. Businesses using Belgium e-invoicing solutions can connect to the PEPPOL network with minimal setup effort.
Where a key trading partner is not registered by go-live, a written interim delivery arrangement with a firm registration date creates the documented compliance evidence FPS Finance expects to see. Undocumented verbal agreements carry no audit protection. The interim arrangement should specify the delivery method and the invoice format.
Common PEPPOL Implementation Mistakes
PEPPOL in Belgium implementations fail at predictable points. The first is going live without testing inbound scenarios — outbound works in sandbox but inbound was never configured. The second is registering only the parent company and discovering subsidiary entities with separate Belgian VAT numbers need their own identifiers. The third is attempting go-live before directory propagation has been verified — invoices fail at the directory lookup step, creating a confusing error pattern. Platforms such as Zoho Books e-invoicing tools are already configured to handle structured invoice exchange.
PEPPOL in Belgium project timelines also suffer when trading partner readiness is treated as a go-live checklist item rather than an early-project workstream. A supplier that needs to register on PEPPOL takes two to four weeks. Finding that a critical supplier is unregistered two weeks before go-live leaves no time to resolve it without a temporary alternative arrangement. Running the trading partner check in the first week of the project, not the last, avoids that scenario entirely.
Conclusion
PEPPOL in Belgium is stable and well-documented. Extending it to B2B has introduced a much larger participant base and a higher volume of first-time implementations, which has surfaced the predictable gaps: incomplete inbound configuration, identifier propagation issues, insufficient sandbox testing. All of those are fixable in the implementation phase. Fixing them after go-live on live invoice traffic is considerably more disruptive.
Frequently Asked Questions
Q1. Do I need PEPPOL if I only send invoices, not receive them?
No — PEPPOL participation is required for both sending and receiving. A business not configured to receive cannot accept structured.
Q2. Can two companies with different access point providers exchange invoices?
Yes. The PEPPOL network connects all accredited access points. Two businesses using different providers exchange invoices through the network without.
Q3. How is a PEPPOL identifier different from a VAT number?
A PEPPOL identifier combines a scheme prefix with the Belgian enterprise number. It is the network address used to route.
Q4. How long does it take to appear in the PEPPOL directory after registration?
Typically, a few hours after the access point completes onboarding. Allow 24 hours and verify using the BOSA directory lookup.
Q5. What happens if we send a PEPPOL invoice to an unregistered receiver?
The sender’s access point returns a directory lookup failure. The invoice cannot be delivered. An alternative compliant delivery method must.
Source by:
Image by Gemini
