Belgium's Structured Invoicing Obligation

Belgium's mandate is the least interesting one in Europe to write about and among the most instructive to study, because of what it declined to do.

It did not commission a national format. It did not build a clearance platform. It did not invent an addressing scheme. It took an existing network with an existing specification and an existing population of accredited providers, and pointed the law at it.

Why that matters more than it sounds

A national mandate has to answer four questions: what the document is, how it travels, who is allowed to carry it, and how a sender finds a receiver. Every country that answers them from scratch produces a fifth problem — a target that exists nowhere else — and every multinational then pays for it.

Belgium answered all four by reference. The result is that a business already exchanging structured invoices over the Peppol network has almost nothing new to build. The format is a European profile, the addressing is the network's participant identifier scheme, the transport is the network's transport profile, and the providers are already accredited.

What is still work

Three things, and none of them is the format.

Addressing. Being on a network means being registered in it, discoverable, and correctly identified. That is a data problem: you need each Belgian customer's participant identifier, in the right scheme, and they need yours. Collecting company numbers without the scheme that qualifies them produces a file that looks finished and cannot be used. The mechanics are in addressing on Peppol.

The receiving side. The default network delivers to whatever endpoint your provider registered for you. Something has to be on the other end of that endpoint: validation, a queue, a route to the ledger, and a defined behaviour when a document fails. That is accounts payable redesign, and it is the piece with no format dependency at all, which means it can be started immediately.

Provider selection. With no state platform, your provider is your compliance interface: it validates, it transmits, it produces your delivery evidence, and in many arrangements it archives. That makes provider choice a controls decision, not a procurement one. Choosing an access point or service provider sets out what to ask.

The timetable

The absence of staging is a genuine difference. Countries that stage by turnover give small businesses time and give large businesses an early deadline; a single date gives everyone the same one. In practice that puts more weight on the receiving obligation, because the smallest counterparties are in scope from the start.

Scope, and the word doing the work

The obligation is framed around taxable persons established in Belgium, issuing to other taxable persons for domestic supplies. Every phrase in that sentence narrows it, and the one that produces mistakes is the first.

Being registered for Belgian VAT is not the same as being established there. A foreign company holding a Belgian registration because it stores goods in the country may have no establishment at all, and whether it is caught turns on the national test rather than on the registration. The consequence for a group is that the scope question has to be asked entity by entity, with the reasoning recorded, because the answer is not stable — a change in where staff sit or where a branch is incorporated can move an entity across the line without any law changing.

The other boundary worth establishing early is the transaction one. A domestic business-to-business mandate does not catch consumer sales, and it does not catch cross-border supplies. Those continue on whatever route they used before, which means the project is designing two channels rather than one, and the second is normally discovered late because nobody scoped it.

Receiving comes before issuing

The obligation people plan for is the obligation to issue. The one that arrives first, in Belgium as everywhere else that has staged a mandate, is the ability to receive.

That is a smaller technical task and a larger organisational one. Being reachable means holding a registration in the network's addressing so that documents sent to you resolve to somewhere you monitor — the mechanics of which are in how a participant identifier becomes a delivery. It also means somebody has decided what happens when a structured document arrives: what validates it, where the data goes, and who works the exceptions.

A business that registers an address and points it at an unmonitored destination has satisfied the letter of the requirement and created the worst available outcome, which is invoices that are delivered, acknowledged and never seen. Deciding where they land is a question about accounts payable rather than about compliance, and it is the part with the longest lead time.

What to take from it if you are not Belgian

Belgium is the cleanest available answer to a question that comes up in every implementation: should we build to the national target or to the European one?

Where a country has adopted a European profile on a shared network, building to the profile is building to the mandate, and the same artefact serves several jurisdictions. Where a country has its own schema and its own platform — as Italy does — you are maintaining a second target, and the mapping between them is a permanent cost rather than a project cost.

That distinction is worth making explicit in an architecture decision, because it is the difference between one output and a growing set of them. It is examined in the layers of the European standard.