Guide
E-Invoicing in Belgium
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Belgium.
What matters in practice
This Belgium guide explains PEPPOL BIS 3.0 routing, enterprise number checks, EN 16931 mappings, and the common buyer-reference questions that affect acceptance.
This article treats E-Invoicing in Belgium as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Common e-invoice formats
Common e-invoice formats is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on PEPPOL BIS 3.0 (UBL) and EN 16931 mappings, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- PEPPOL BIS 3.0 (UBL)
- EN 16931 mappings
Routing & delivery
Routing & delivery connects E-Invoicing in Belgium with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding PEPPOL to validating or converting the invoice file.
Common identifiers
Common identifiers is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on Enterprise number and VAT ID, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Enterprise number
- VAT ID
Mandate & scope
Belgium commonly relies on PEPPOL BIS 3.0 for structured invoice exchange, especially in public procurement, while EN 16931 mappings keep VAT and master data aligned.
Mandate & scope
Mandate & scope is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on B2G recipients typically expect structured UBL data instead of PDF-only invoices, Enterprise number and VAT ID should match the supplier master data used by the buyer and Buyer references, VAT categories, and payment data should follow EN 16931 code lists exactly, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- B2G recipients typically expect structured UBL data instead of PDF-only invoices.
- Enterprise number and VAT ID should match the supplier master data used by the buyer.
- Buyer references, VAT categories, and payment data should follow EN 16931 code lists exactly.
How to send (practical steps)
How to send (practical steps) is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on Confirm whether the recipient expects PEPPOL delivery and which participant identifier scheme…, Prepare the invoice with the correct enterprise number, VAT ID, and buyer routing references and Validate the UBL structure and business rules before submission, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Confirm whether the recipient expects PEPPOL delivery and which participant identifier scheme they use.
- Prepare the invoice with the correct enterprise number, VAT ID, and buyer routing references.
- Validate the UBL structure and business rules before submission.
- Send through a PEPPOL access point and retain the delivery acknowledgement.
Validation & compliance
Validation & compliance is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on Check participant ID schemes and endpoint values before routing, Validate VAT category codes, totals, unit codes, and payment means and Ensure buyer identifiers and references match the values provided by the recipient, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Check participant ID schemes and endpoint values before routing.
- Validate VAT category codes, totals, unit codes, and payment means.
- Ensure buyer identifiers and references match the values provided by the recipient.
Common pitfalls
Common pitfalls is where the general explanation of E-Invoicing in Belgium becomes operational. The section focuses on Using outdated enterprise number or VAT data from supplier master records, Missing or incorrect buyer participant ID for PEPPOL routing and Using free-text tax labels instead of valid coded values, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Using outdated enterprise number or VAT data from supplier master records.
- Missing or incorrect buyer participant ID for PEPPOL routing.
- Using free-text tax labels instead of valid coded values.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of E-Invoicing in Belgium. The answers focus on Which invoice channel is most common in Belgium and What should I verify before sending a Belgian invoice and are written to clarify implementation choices quickly.
Which invoice channel is most common in Belgium?
PEPPOL BIS 3.0 is the most common structured channel, especially for public procurement and other regulated exchanges.
What should I verify before sending a Belgian invoice?
Check the enterprise number, VAT ID, buyer references, and PEPPOL participant details before sending.
Official links
Official links connects E-Invoicing in Belgium with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding OpenPeppol and Belgian e-Procurement to validating or converting the invoice file.