B2B e-invoicing in Belgium: what the obligation really changes

Since January 2026, invoices between VAT-registered businesses must be structured and sent via Peppol. Switching to electronic invoicing is not just a matter of emailing a PDF.

Business software7 min read

The most common misunderstanding fits in one sentence: a PDF invoice sent by email is not an electronic invoice within the meaning of the obligation. A PDF is an image meant for a human reader. What the regulations require is a structured file that accounting software can read without anyone stepping in.

What the Peppol network requires

Peppol is a transmission network. You don't connect to it directly: you go through an access point, which routes your invoices to your customer's access point. The format carried is a UBL file compliant with the BIS Billing 3.0 profile, and that is where the real difficulty lies.

This profile defines several hundred validation rules. An invoice that breaks just one of them is rejected by the network. You are not always notified of the rejection straight away, and your customer, for their part, has received nothing. In practice, a formatting error turns into a late payment that nobody notices until the reminder goes out.

The rules that cause trouble in practice

  • The company number must be valid according to its check digits, not merely contain ten digits.
  • The IBAN must pass the modulo 97 check; a typing slip cannot be spotted with the naked eye.
  • The totals excluding VAT, the breakdown by VAT rate and the amount due must add up to the cent.
  • Each line must carry a unit of measure code taken from the official code list, not free text.
  • Purchase order references, when the customer requires them, must follow the format they have specified.

Taken one by one, these rules look trivial. Together, across several hundred invoices a month entered by people in a hurry, they produce a significant rejection rate.

Validate before, not after

The difference between a tool that works and a tool that breeds frustration comes down to where validation happens. If it happens when the invoice is sent to the network, the user discovers the error hours later, in the form of a technical code. If it happens at data entry, in the interface, the faulty field is flagged immediately, in the user's own language, along with what needs correcting.

A validation rule that doesn't explain how to satisfy it is not validation; it is an obstacle.

What to look for in a tool

  • Does validation happen at data entry, or only when the invoice is sent?
  • Do error messages point to a specific field, in your language?
  • Is the generator tested against the official sample files for the BIS 3.0 profile?
  • Can you export your invoices in a readable format if you change tools?
  • Is the Peppol access point included, or billed separately?

What if you issue few invoices?

Below a few dozen invoices a month, an off-the-shelf solution does the job and costs less than custom development. Custom development is justified when invoicing is bound up with a particular line of business: usage-based billing, cost allocation across analytical accounts, complex discount rules. It is a trade-off to be settled with figures, not principles.

Is this question coming up in your business?

Describe your situation. We reply within one working day.

Reply within one working day. You can also write to contact@chenit.eu or call 0456 71 39 98.