Back to blogOctober 23, 2026

Belgium e-invoicing rules for software teams

Structured e-invoicing is mandatory between Belgian businesses

Since 1 January 2026, structured electronic invoicing is compulsory for transactions between Belgian enterprises that are liable to VAT (B2B). The official Belgian e-invoicing portal states that all Belgian VAT-liable enterprises must exchange structured electronic invoices with each other.

Who is covered

The obligation applies to VAT-liable businesses. The portal's FAQ says it also applies if you use the small-business exemption scheme. Some B2B transactions are excluded, and the FAQ links to a separate article that lists them. Check that list before you assume a given transaction is in scope.

Standard and network

The FAQ refers to the European standard for e-invoicing, EN 16931. It says you need software connected to the Peppol network to send, receive and process e-invoices.

What this means for your software

  • Produce structured invoice data in the EN 16931 standard. A file that only looks like an invoice does not meet the rule.
  • Connect your invoicing flow to the Peppol network, directly or through a provider.
  • Make sure you can receive structured invoices as well as send them.
  • Record which B2B transactions are excluded, so your product applies the right path to each one.

Dates to track

The mandate has been in force since 1 January 2026. Work on Belgian integrations should be aimed at the current rule, not at a future start date.

Next step

Read the developer documentation to scope a Belgian integration.

Start with one workflow, not a whole rewrite

Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.