Introduction
Belgium PEPPOL is the mandatory delivery network for domestic B2B structured invoices following the January 2026 mandate — but for many businesses, the technical reality of what connecting to it properly requires was underestimated at the start. Signing with an access point provider is not the same as having a functioning PEPPOL connection. The identifier must be published correctly. The ERP must produce valid XML. The inbound channel must be built. Archiving must be configured. Each of those elements needs to work before the connection is actually compliant. Belgium PEPPOL is becoming a standard requirement for VAT-registered businesses operating in Belgium.
What PEPPOL Means for Belgian Businesses
Every domestic B2B invoice must now travel through the PEPPOL network — validated by the sender’s accredited access point, routed to the receiver’s access point, and delivered into the buyer’s ERP. Belgium PEPPOL participation is not a registration form. It is a functioning technical connection that requires ERP integration, field mapping, and sandbox testing. Understanding Belgium PEPPOL early gives finance teams a significant head start before enforcement begins.
PEPPOL integration Belgium for companies running SAP or Dynamics 365. The connector handles the XML transformation and Schematron validation. The field mapping — where ERP data elements are assigned to EN 16931 mandatory fields — is the configuration work that takes the most time and produces the most first-month rejection issues when done incorrectly. The scope of Belgium PEPPOL continues to expand as FPS Finance rolls out each compliance phase.
PEPPOL Access Points: Selection Criteria
Accredited access points are listed on the OpenPEPPOL website and Belgium’s BOSA PEPPOL directory. When comparing providers, the criteria that matter in practice are: certified connector availability for the ERP platform in use, Belgian onboarding experience and archiving service terms. A provider with a large Belgian customer base has encountered the implementation problems that a newer entrant may not yet have seen. Businesses preparing for Belgium PEPPOL should prioritise master data accuracy across customer and supplier records.
Invoice exchange Belgium through a well-configured access point is largely automatic after integration. Invoices leave the ERP, pass Schematron validation, travel to the buyer’s access point, and are delivered — all within seconds. That speed is most operationally visible in accounts receivable management, where delivery confirmation replaces the uncertainty of email-based invoice transmission. Belgium PEPPOL compliance depends on having the right ERP connectivity in place before the deadline.
Format: UBL 2.1,CII D16B, and EN 16931
Belgium PEPPOL messages must be UBL 2.1 or CII D16B, conforming to EN 16931, using PEPPOL BIS Billing 3.0. Schematron validation at the access point checks every mandatory field before the invoice enters the network. A field populated with the wrong value type — an ERP-internal tax code where an EN 16931 tax category code is expected — will fail validation even though it contains data.
Compliance framework Belgium for format validation is best tested in the access point sandbox before any live traffic. Running real invoice data from the actual ERP through sandbox validation catches the field mapping problems that are specific to the business’s ERP configuration. Running only test files supplied by the access point provider validates the sandbox connection but not the ERP output.
Directory Registration and Participant Identifiers
Belgium PEPPOL directory registration is managed by the access point provider. The provider creates a participant identifier — scheme prefix combined with the Belgian enterprise number — and publishes it in the SMP. After publication, any PEPPOL-connected sender can route invoices to it. Directory propagation takes a few hours. Always verify the identifier is visible in the BOSA lookup tool before sending the first live invoice.
Invoice network Belgium registration must cover each legal entity separately. A parent company’s identifier does not extend to subsidiaries with separate Belgian VAT numbers. Groups with multiple VAT entities must register each one individually. Finding this requirement after the parent entity is live creates additional onboarding workstreams that were not planned for.
Inbound PEPPOL: Receiving and Processing Structured Invoices
Belgium PEPPOL compliance includes receiving. When structured invoices arrive from PEPPOL-connected suppliers, they must be processed through an active inbound connection — not downloaded manually from an access point portal and re-keyed into the ERP. The inbound integration routes the incoming XML to the correct AP module, validates it, and matches it against purchase orders.
UAE digital reporting requirements similarly cover both outbound and inbound flows. Belgian businesses with UAE operations manage two separate technical compliance frameworks — Belgium’s decentralised PEPPOL model and the UAE FTA’s government-linked clearance system. The inbound obligation in both markets is real and carries its own audit exposure.
Archiving Under PEPPOL Rules
Belgium PEPPOL archiving requires the original XML to be retained for seven years by both sender and receiver. A PDF version alongside the XML is acceptable for human reference but does not satisfy the archiving requirement on its own. Access point archiving services handle this in most cases — but the retrieval process should be tested before go-live, not assumed to work based on a contract clause. Teams running Xero e-invoicing integration benefit from pre-built connectors that simplify structured invoice delivery.
Archive portability is the contractual term most businesses overlook at signing. If the access point provider relationship ends before the seven years are up, the XML archive must be migrated before termination. Without explicit archive export rights in the contract, recovering those records in a usable format can be difficult and expensive.
Multi-Entity and Group Compliance
Belgium PEPPOL registration is per VAT entity. A group with a holding company and two operating subsidiaries — even running on one ERP system — needs three separate participant identifiers in the PEPPOL directory. Implementing PEPPOL for the parent only and assuming coverage extends to subsidiaries is a structural gap that FPS Finance will identify in an audit review. Businesses using QuickBooks e-invoicing setup can connect to the PEPPOL network with minimal setup effort.
Belgium PEPPOL intra-group invoice treatment requires specific analysis for groups where entities share a VAT number versus those with separate registrations. Entities sharing a single VAT number may fall outside the mandate for transactions between them. Entities with separate VAT numbers are in scope. Getting written confirmation from FPS Finance on the treatment of specific intra-group flows removes the ambiguity before implementation design is finalised.
Conclusion
PEPPOL is not a registration form — it is a functioning bilateral network connection that requires ERP integration, field mapping, inbound configuration and archiving. Belgian businesses that understood that from the start are running reliably. Those that treated provider sign-up as the endpoint of implementation are discovering the gaps on live invoices.
Frequently Asked Questions
Q1. What is OpenPEPPOL and why does it matter?
OpenPEPPOL is the international non-profit that governs the PEPPOL network standards and accredits access point providers. Only OpenPEPPOL-accredited providers can.
Q2. Can we change access point providers after go-live?
Yes — but provider changes require re-onboarding and migrating the PEPPOL identifier, exporting the XML archive before the old provider.
Q3. Does PEPPOL support invoices in currencies other than euros?
Yes. PEPPOL BIS Billing 3.0 supports multi-currency invoices. The currency code field must be explicitly populated in the XML.
Q4. What happens to invoices sent during a PEPPOL network outage?
Accredited access points maintain queuing systems that retry delivery during outages. Check the provider’s SLA for maximum retry windows.
Q5. Do we need to notify trading partners when we go live on PEPPOL?
Yes — notify key partners of your go-live date and participant identifier. This allows them to begin routing invoices.
Source by:
Image by Gemini
