Peppol registration for Belgian businesses

Registration as network membership, not a tax form

For a Belgian business, Peppol registration is the process of becoming a reachable participant on the Peppol network. It is distinct from VAT registration at the FPS Finance or enrolment on Mercurius for public-sector invoicing. Registration means your organisation has a Peppol participant identifier, metadata published in a Service Metadata Publisher (SMP), and a certified Access Point that sends and receives structured documents on your behalf.

Since the structured B2B e-invoicing obligation took effect in 2026, registration is no longer a niche procurement concern. Any VAT-liable Belgian business trading domestically needs a discoverable identity and working inbound connectivity, not only outbound sending.

The Belgian participant identifier (BCE / KBO)

Peppol addresses participants with standardised identifiers defined in ISO 6523. In Belgium, the canonical scheme is 0208, which maps to the enterprise number registered in the Crossroads Bank for Enterprises (BCE, Dutch: KBO).

A typical Belgian Peppol identifier looks like:

0208:0123456789

The ten-digit number is the KBO/BCE enterprise number, zero-padded where needed. Using this scheme avoids duplicate or ad hoc addressing: your trading partners, accounting software, and network lookup services all refer to the same legal entity.

Important nuances:

• One legal entity, one primary identifier. Branches and establishments may have separate KBO units, but B2B invoicing normally ties to the VAT-liable enterprise number on the invoice.
• Identifier ≠ registration. Knowing your enterprise number does not mean you are on Peppol. Publication in the Peppol directory happens only after an Access Point registers you.
• Lookup before sending. Senders query the network (via SML/SMP) to confirm the recipient exists and accepts the intended document profile before delivery.

See What is Peppol? for how identifiers fit into the broader exchange model.

The Access Point as registration agent

Businesses do not connect to Peppol directly. They contract with a certified Access Point provider, which implements AS4 messaging, certificate management, and Peppol governance rules. For registration purposes, the Access Point acts as your technical representative on the network.

When you onboard with a provider, it typically:

1. Collects your legal name, enterprise number, and contact details for verification
2. Creates or claims your participant identifier under scheme 0208
3. Publishes SMP metadata describing which Access Point serves you and which document types you support
4. Provisions credentials, endpoints, or software integration for send and/or receive

Some providers embed Access Point functionality inside invoicing or accounting products. Others offer standalone connectivity exposed through API or SFTP. From a network perspective the pattern is the same: your documents enter and leave Peppol through that provider's certified infrastructure.

Access Point

A Peppol-certified gateway that registers participant identities, publishes SMP entries, and delivers structured documents to and from your organisation.

Read Peppol Access Point for certification, SMP/SML roles, and what to evaluate when choosing connectivity.

SMP publication and discoverability

After registration, your entry appears in a Service Metadata Publisher (SMP). The SMP answers two practical questions for anyone trying to reach you:

• Which Access Point should receive documents addressed to your participant ID?
• Which document types and process IDs do you accept (for Belgium, typically Peppol BIS Billing 3.0 aligned with EN 16931)?

The Service Metadata Locator (SML) is the index that points lookup tools to the correct SMP. End users rarely configure SML or SMP manually; the Access Point provider maintains these records when your registration changes.

Discoverability matters for compliance. If your SMP entry is missing, incomplete, or points to an inactive Access Point, suppliers cannot deliver mandated structured invoices. Symmetrically, customers cannot receive your outbound invoices if your metadata or send capability is misconfigured.

Publication is not instantaneous in every case. Propagation across the federated directory can take time after initial registration or after switching providers. Plan migrations before decommissioning an old Access Point.

Send capability versus receive capability

Peppol distinguishes sending and receiving as separate operational capabilities. Both rely on the same participant identifier, but they impose different requirements on your systems.

Receiving

Inbound Peppol invoices arrive at your Access Point, which validates the message envelope and payload, then forwards the structured document to your inbox, ERP, or archive. Receiving requires:

• An active SMP entry advertising supported billing document types
• A working integration or inbox where staff or software can process UBL/XML
• Retention and audit practices consistent with Belgian e-invoicing rules

Under the 2026 B2B mandate, receive capability is mandatory for in-scope VAT-liable businesses. A organisation that can only send but cannot accept structured inbound invoices is not operationally compliant.

Sending

Outbound sending means your invoicing tool produces a valid structured invoice (typically UBL under Peppol BIS Billing), hands it to your Access Point, which resolves the recipient's SMP entry and delivers the document. Sending requires:

• Valid semantic and syntax (EN 16931 / Peppol BIS rules)
• Correct recipient identifier (usually the counterparty's 0208 number)
• Your Access Point's outbound channel and signing certificates

Many businesses implemented receive first when the obligation approached, then aligned outbound invoicing. Both directions should now be treated as production infrastructure, not pilot features.

Asymmetric setups and migrations

Historically some entities registered receive-only to accept public-sector invoices while still sending PDFs commercially. The Belgian B2B obligation closes that gap for domestic VAT-liable trade. During provider migration, you may temporarily have overlapping registrations; coordinate cut-over with both Access Points so SMP entries always resolve to an active endpoint.

End-to-end registration flow

The following sequence is representative for a Belgian SME onboarding through a software-integrated Access Point:

1. Confirm the enterprise number (KBO/BCE) that will appear on invoices
2. Select a certified Access Point provider matching your send/receive needs
3. Sign service terms; the provider verifies your identity against KBO data
4. Register participant ID 0208:xxxxxxxxxx and publish SMP metadata
5. Test inbound delivery (test invoice from provider or counterparty) and outbound send to a known Peppol participant
6. Verify public lookup (Peppol directory or provider tool) shows your identifier as active

Large groups with multiple VAT numbers register each liable entity separately. Shared service centres must map inbound documents to the correct legal entity inside their ERP.

Common registration pitfalls

Registration in the wider compliance picture

Peppol registration solves network reachability. It does not by itself guarantee valid invoice content, correct VAT treatment, or archival compliance. Those remain matters of business process, accounting policy, and Belgian tax law.

Treat registration as durable infrastructure: review it when you change invoicing software, merge entities, or replace your Access Point provider. Your participant identifier anchored to the KBO number stays constant; the SMP record and integrations behind it must stay current.