Skip to main content

Documentation Index

Fetch the complete documentation index at: https://invopop-mintlify-changelog-week-1778411791.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Belgium handles e-invoicing through the Peppol network, which will become mandatory starting January 2026. For comprehensive information about Peppol features and capabilities, please refer to our Peppol Guide.

FAQ

Install the Peppol app, register your supplier with BOSA-migrated participant ID, and use a workflow that generates a Peppol BIS Billing 3.0 document and sends it via the Lookup → Send actions.
In Belgium specifically there is no need to send a copy to the tax authority until the e-reporting mandate comes into effect in Jan 2028.
See the Belgium tax regime in GOBL for tax IDs and category codes. The Peppol BIS Billing 3.0 mapping is shared across EU members and lives in peppol-bis-v3.
Belgium uses two Peppol scheme identifiers:
  • 0208 (KBO/BCE enterprise number) — This is the preferred and default scheme for Belgium. It corresponds to the company’s KBO/BCE number (Kruispuntbank van Ondernemingen / Banque-Carrefour des Entreprises), which is the official Belgian business register. Most Belgian companies are registered in Peppol under this scheme.
  • 9925 (BE VAT number) — This is an older, alternative scheme based on the Belgian VAT number. It is typically used by entities that have a Belgian VAT number but are not registered in the KBO/BCE — for example, foreign companies with a Belgian VAT registration.
When you should use 0208: Always use 0208 as your first choice when sending invoices to Belgian companies. This is the standard identifier and what the vast majority of Belgian businesses are registered under.When 9925 may be needed: If you get a “receiver not found” error when sending to a Belgian company using 0208, and you have confirmed the company exists in the Peppol Directory, check whether they are registered under 9925 instead. This is uncommon but does happen.To specify the scheme when sending, include the customer’s Peppol inbox in your GOBL document:
"customer": {
  "name": "Example Company",
  "tax_id": {
    "country": "BE",
    "code": "0123456789"
  },
  "inboxes": [
    {
      "key": "peppol",
      "scheme": "9925",
      "code": "BE0123456789"
    }
  ]
}
Note that when using 9925, the code must include the BE prefix (e.g. BE0123456789), whereas 0208 uses the raw KBO/BCE number without a prefix.
Use the Lookup Participant ID workflow step to verify a recipient’s Peppol registration before sending. If a lookup with 0208 fails, try again with 9925.
In countries where Peppol is the standard but not mandatory, you may still need to issue an e-invoice when the recipient isn’t on the network. Both parties can agree on an alternative transfer method, but the invoice must still be EN16931 compliant.Recommended approach:
  • Set up a separate workflow that generates the XML without the send-Peppol-document step
  • Or reuse your existing workflow without the customer Peppol ID — the send step is automatically skipped
  • Fetch the generated XML and deliver it through the agreed channel, typically email
B2C invoices typically lack the structured customer information required for Peppol delivery, and most consumers don’t have inboxes. Use a conditional workflow:
  1. Add an If/Else step that checks for a customer inbox using count(customer.inboxes, true) > 0.
  2. On the false branch, generate a PDF and email it to the customer, then stop the flow.
This routes B2B invoices through Peppol while keeping a smooth path for consumers.
If a job fails with KO and receiver not found in the peppol network, treat it like an invalid email address — the recipient simply isn’t reachable on Peppol. Add the Lookup Participant ID step (ideally in a separate validation workflow run against customer data) so you catch missing IDs before generating the invoice.
No. The regime is automatically derived from the supplier’s settings, which is the recommended approach for Peppol — leave it unset on the document.
See the oasis-ubl-v2 addon and the Peppol app reference for required fields, supported document types, and Participant ID schemes.
More available in our Belgium FAQ section

Participate in our community

Ask and answer questions about invoicing in Belgium →