Skip to main content
ARVELEHT

Documentation · BE · Peppol BIS 3.0

How Arveleht handles Belgian Peppol.

If you invoice a Belgian business after 1 January 2026, the invoice has to flow over the Peppol network. This page explains what that means concretely, what Arveleht produces today, and which live-relay step is still held for provider verification.

01 · What’s mandated

Belgium amended its VAT code (Loi du 6 février 2024 / Wet van 6 februari 2024) to require structured e-invoicing for domestic and cross-border B2B supplies. From 1 January 2026, invoices between VAT-registered Belgian buyers and sellers — and from cross-border suppliers selling into BE — must be:

  • Peppol BIS Billing 3.0 UBL (not XRechnung, not Factur-X).
  • Delivered via Peppol — through a certified access point registered in the SMP. No email attachments, no FTP uploads.
  • Retained as audit evidence — the delivery receipt (corner-4 acceptance signal from the buyer’s AP) is the legally recognised proof that the invoice reached its destination.

02 · What Arveleht produces

A Belgian-bound invoice on /invoices/new renders through the same gobl.ubl pipeline as Germany but with ContextPeppol, which produces the Peppol-flavoured CustomizationID:

urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0
  • Scenarios covered. Domestic standard VAT (21%), mixed rates (21% + reduced 6% catalogue), credit notes (UNTDID 381 with explicit preceding invoice reference), multi-line reverse-charge cross-border supplies (cat AE with BR-AE-10 exemption reason).
  • Validation. Every Peppol UBL is round-tripped through the PEPPOL-EN16931-UBL.sch Schematron before hand-off to the access point. Five happy-path fixtures are locked in the engine test suite to catch drift.
  • Provider status. The public Pilot renders the Peppol BIS 3.0 UBL for download today. Automated Peppol relay is intentionally held until a provider account, signing path, and webhook receipt loop are verified end-to-end.

03 · The delivery receipt chain

Peppol delivery is a multi-hop pipeline. The receipt ledger already records rendered and validated invoice transitions; the submitted, delivered, and acknowledged Peppol hops are enabled only after the provider webhook loop is proven:

  1. Draft — the envelope exists, hasn’t been rendered yet.
  2. Validated — gobl calculate + validate passed.
  3. Rendered — UBL bytes are written and schematron-validated.
  4. Submitted — handed to the configured Peppol provider with a provider-issued submission id returned.
  5. Delivered — the buyer’s access point acknowledged at the SMP layer (corner-3).
  6. Acknowledged — the buyer’s ERP confirmed receipt (corner-4).

Each row carries the previous row’s hash; tamper with one and the chain fails verification on page load.

04 · What this doesn’t do yet

Public Belgian live relay is not switched on yet. Peppol receive is also not wired. If you need to send or receive Belgian invoices live today, keep using your existing access point until Arveleht’s provider verification clears.

Next: FR · Factur-X CII → · Back to docs index