Trusted Digital Transformation Partner

Home / E-Invoicing / Belgium

Belgium · Peppol · Live since January 2026

E-Invoicing in Belgium

Structured B2B e-invoicing over Peppol became mandatory for Belgian VAT-registered businesses in January 2026 — for every company at once, with no size-based phase-in. We build it into Oracle EBS and Fusion.

Talk to us about Belgium

In short

E-invoicing in Belgium requires domestic B2B invoices to be issued as structured electronic documents through Peppol network, using Peppol BIS Billing 3.0 (EN 16931). Since 1 January 2026, Belgian VAT-registered businesses have been required to issue and receive structured electronic invoices for domestic B2B transactions via the Peppol network, in an EN 16931-compliant format such as Peppol BIS Billing 3.0 (UBL 2.1). Unlike most countries, Belgium applied the obligation to all businesses at the same time rather than phasing by turnover. Whatever the local mechanism, the invoice still has to come out of your ERP correctly — and in our experience that is where projects actually succeed or fail. ROSTAN builds the integration into Oracle EBS and Fusion Receivables so compliance is generated from the invoice the business already raises.

The deadline

Live now

Dates reported from published guidance. Confirm your own obligation with your tax adviser — ROSTAN implements the ERP integration and does not provide tax or legal advice.

What Belgium requires

Since 1 January 2026, Belgian VAT-registered businesses have been required to issue and receive structured electronic invoices for domestic B2B transactions via the Peppol network, in an EN 16931-compliant format such as Peppol BIS Billing 3.0 (UBL 2.1). Unlike most countries, Belgium applied the obligation to all businesses at the same time rather than phasing by turnover.

OpenText — E-Invoicing Europe 2026

What makes Belgium different

The details that change the integration

Peppol, not a government portal

Belgium routes invoices over the Peppol network through access points rather than a central clearance platform. That makes the integration a document-exchange problem: your ERP must emit a valid UBL document and consume one back.

No size exemption

Every VAT-registered business was in scope from day one. If you have a Belgian entity issuing domestic B2B invoices, it is already covered — there is no small-company grace tier to fall back on.

EN 16931 semantics

The European standard defines what fields must be present and what they mean. Most failures are not transport failures — they are missing or wrong data in the ERP that the schema rejects.

Receiving matters too

The obligation runs both ways. Supplier invoices arriving as structured documents need to land in Accounts Payable and match, which is the half most projects under-scope.

The portal is rarely the problem

Statutory e-invoicing is the single largest workload on our own Oracle service desk. These are the causes we see behind rejections, wherever the mandate is.

Tax or product master data that does not match what the schema expects — the most common single cause.

Party identifiers (VAT numbers, registration IDs, addresses) missing or formatted for a human rather than a validator.

A payload that validates in test and fails in production because a real invoice carries a case the sample never did.

No controlled retry path — a rejected invoice is not a valid invoice, and manual re-keying does not scale.

Nobody owning reconciliation: invoices issued in the ERP but never confirmed as accepted downstream.

The receiving side left out of scope, so supplier invoices arrive in a format Accounts Payable cannot process.

FAQ