Since the beginning of January 1st 2026, Belgium has made it company to have a structured B2B e-Invoicing. Thus, it has become necessary for every VAT-registered business established in Belgium to send and receive invoices as structured electronic documents over the Peppol network. In addition, they must use Peppol BIS Billing 3.0 (UBL 2.1) format aligned with the European standard EN 16931. PDFs sent by email no longer satisfy the obligation for in-scope B2B transactions.
If your finance and IT teams are still catching up, this checklist walks you through exactly what to prepare so your move to e-Invoicing in Belgium is clean, compliant, and audit-ready.
Businesses that need support with Peppol connectivity, structured invoice validation, and ERP integration can use a Belgium e-invoice solution to simplify their compliance journey.
What Belgium businesses should prepare first
The fundamentals of invoicing must be in place before touching or changing any system. These are the non-negotiables for Belgium invoice compliance:
Confirm you’re in scope.
- The compulsory message by the government only covers B2B transactions between businesses that are VAT-registeredin Belgium. The non-established business entities even if they are based in Belgium and B2C sales are excluded from the mandate.
Verify your KBO/BCE registration.
You must be registered in the Peppol Directory using your Belgian enterprise (KBO/BCE) number so trading partners can find and route invoices to you.
Connect through a certified Peppol Access Point.
You cannot send or receive structured invoices through Peppol without an Access Point. Businesses should first understand how Belgium B2B e-invoicing works across suppliers, buyers, ERP systems and certified Peppol Access Points. E-invoicing vendors and service providers can then support invoice transmission, validation, routing and status management.
Adopt the correct format.
The ready to use format is Peppol BIS Billing 3.0. Alternative EDI formats (e.g., EDIFACT). Moreover, these formats are only permitted if both the business organizations agree and the output remains EN 16931-compliant.
Plan for validation.
Invoices must go through and clear EN 16931 and Peppol business rules (e.g., BR-06 seller name, BR-CO-15 VAT consistency) way before they are accepted. For pre-checks, businesses can use free tools such as Peppol Validator and understand the checks beforehand.
Note the next milestone. Near-real-time e-reporting (the Peppol five-corner model) is scheduled for 1 January 2028 — build with that in mind.
Tip: Credit notes can still be issued as PDF in some cases if your customer accepts them, but once you issue a structured electronic invoice (SEI), the recipient is obliged to accept it.
Review supplier and customer master data
Bad master data is the number one cause of rejected e-Invoices. Structured invoices leave no room for “close enough” — fields must match exactly what Peppol expects. Audit your supplier and customer records against this checklist:
| Field | What to check |
|---|---|
| Legal name | Matches the official KBO/BCE registration exactly (BR-06 requires a seller name). |
| Enterprise / VAT number | Valid Belgian KBO/BCE and BE VAT number; no spaces, prefixes, or typos. |
| Peppol participant ID | Confirm each B2B partner is registered and reachable on Peppol. |
| Registered address | Complete street, postal code, city, and country code (ISO format). |
| Country & VAT scheme | Correct ISO country codes; flag cross-border and reverse-charge partners. |
| Contact & routing details | Email/endpoint for fallback and reconciliation. |
| Duplicates & inactive records | Merge duplicates and archive dormant accounts before go-live. |
Action items:
- Run a deduplication and validation pass across your customer and supplier ledgers.
- Cross-check VAT numbers against the EU VIES database.
- Confirm which trading partners are already live on Peppol and which still need onboarding.
- Establish a process to capture the Peppol ID for every new B2B partner at onboarding.
Check ERP invoice fields and tax data
Your ERP must produce invoices that carry every mandatory EN 16931 data element. Map your current invoice template against the structured-invoice requirements and close any gaps before go-live.
Mandatory and high-risk fields to verify:
- Invoice number — unique, sequential, no gaps.
- Issue date (and delivery/tax point date where required).
- Seller and buyer identifiers — legal name, address, VAT and KBO/BCE numbers.
- Line-item detail — description, quantity, unit, unit price, line net amount.
- VAT breakdown — VAT category code, rate, taxable base, and VAT amount per rate. The total VAT must reconcile (BR-CO-15) or the invoice will be rejected.
- VAT exemption reason — when an exemption or reverse charge applies, the reason must be stated in the correct field (TaxExemptionReason).
- Currency — correct ISO currency code.
- Totals — net, VAT, and gross amounts that mathematically reconcile.
- Payment terms & references — due date, structured payment reference, IBAN.
- Purchase order / contract references — increasingly required by larger buyers for automated matching.
Action items:
- Confirm your ERP can export UBL 2.1 / Peppol BIS 3.0 and import incoming structured invoices.
- Test how your system handles VAT rounding — small discrepancies trigger validation failures.
- Validate sample invoices through a Peppol validator and fix every error before connecting live.
- Document how exemptions, reverse charge, and intra-community supplies are encoded.
Choose the right e-invoicing support model
| Support Model | Best For | Advantages | Considerations |
|---|---|---|---|
| ERP-native | Single ERP environments | Native integration | Verify ongoing compliance updates |
| Managed Service Provider | SMEs and Mid-market | Fast implementation and managed compliance | Vendor dependency |
| Hybrid Integration | Multi-ERP enterprises | Flexible architecture | Higher implementation complexity |
Select the right e-Invoicing support model. Your way of connecting to Peppol depends on your invoice volume, ERP setup, and internal IT capacity. There’s no one answer, of course — align the model with your organization’s needs.
ERP-native / built-in Peppol module
Best for companies who already have an ERP with a certified Peppol connector in place. Lowest friction, invoices never leave your system. Confirm the module is certified and kept up to date with EN 16931 revisions.
Service provider / access point (managed e-Invoicing software)
Use a third-party e-Invoicing vendor as your certified access point who will handle transmission, validation, archiving, and partner onboarding. Ideal for most SMEs and mid-market firms — fast to deploy and the provider manages compliance changes for you.
Hybrid / integration platform
For high-volume or multi-ERP environments, an integration layer connects your systems to a Peppol access point with custom mapping and EDI support. More flexible but needs IT resources.
What to look for when comparing e-Invoicing solutions:
- Certified Peppol Access Point status.
- Native EN 16931 / Peppol BIS 3.0 support and automatic regulatory updates.
- Built-in validation before sending.
- Compliant long-term archiving.
- Clear roadmap for the 2028 e-reporting requirement.
- Smooth integration with your existing ERP and partner onboarding support.
Basic go-live checklist for finance teams
Run through this final list before you switch on structured invoices in Belgium:
- Business confirmed in scope; KBO/BCE and VAT numbers verified.
- Registered and discoverable in the Peppol Directory.
- Connected via a certified Peppol Access Point.
- ERP exports imports incoming structured invoices and Peppol BIS Billing 3.0 (UBL 2.1).
- The Data of Customer and Supplier master must be VAT-validated, deduplicated and clean
- All mandatory EN 16931 invoice fields mapped and populated.
- VAT breakdown and totals reconcile; exemption/reverse-charge logic tested.
- Sample invoices pass Peppol validation with zero errors.
- End-to-end test completed with at least one live trading partner.
- Compliant archiving in place for sent and received invoices.
- Finance team trained on handling rejections, credit notes, and exceptions.
- Roadmap noted for the 1 January 2028 e-reporting milestone.
Go-live should only be approved after:
- Finance signs off invoice validation.
- Tax confirms VAT mapping.
- IT validates ERP and Peppol integration.
- Business users successfully complete end-to-end testing.
- Management approves production readiness.
Bottom line.
Belgium’s e-Invoicing mandate is not simply about exchanging invoices through Peppol—it requires organisations to improve master data quality, modernise ERP processes, and establish reliable invoice validation before transactions reach customers and suppliers. Businesses that begin with data readiness, structured testing, and cross-functional ownership will reduce implementation risk while building a stronger foundation for future Belgian e-reporting requirements.
0 Comments