European electronic invoicing legislation starts in 2014, in procurement, with a law that obliged nobody to send anything.
Directive 2014/55/EU required contracting authorities and contracting entities to receive and process electronic invoices that comply with a European standard. It did not oblige a single supplier to issue one. To anyone arriving from a national mandate ten years later, that reads like half a law. It was the half that worked, and it is the reason everything since has had something to build on.
What the directive actually does
Three things, and it is worth separating them because they are often collapsed into one.
It removes the receiver's veto. Before it, a public body could decline a structured invoice and demand paper, and many did. The directive makes receipt of a conforming invoice compulsory, which turns "will they accept it?" from a commercial negotiation into a settled question.
It commissions a standard. The Commission was required to ask the European standardisation body for a semantic data model of the core elements of an electronic invoice, together with a limited list of syntaxes that could carry it. That request produced EN 16931 and the two syntax bindings that every European profile still uses.
It defines conformance by reference. The reference to the standard was published in the Official Journal. That publication is what makes "compliant with the European standard" a statement with a determinate meaning rather than a marketing claim.
Why the asymmetry was the right design
A mandate that obliged every supplier to a public body to issue structured invoices in 2014 would have obliged several million small businesses to buy software for a format that did not yet exist. Instead the directive obliged a few thousand well-resourced public bodies to be able to accept one, and let the market work out the rest.
The effect was that by the time national business-to-business mandates started arriving, four things were already in place: a semantic model, two syntaxes, a population of service providers who had built to them, and a generation of public-sector suppliers who had already been through the exercise once. Every national mandate discussed on this site is standing on that.
The directive's obligation is on the receiving side. When a supplier tells you that "e-invoicing has been mandatory in Europe since 2019", they are describing a national implementation, not this directive.
Where Member States diverged
The directive left several choices open, and they were taken differently.
| Choice | What the directive permitted | Practical effect |
|---|---|---|
| Sub-central authorities | Deferred application | Regional and municipal bodies came later than central government |
| Contracts below threshold | Exclusion permitted | Coverage of small contracts differs by country |
| Obligation to send | Not required, not prohibited | Several countries added one; several did not |
| National profile | Permitted as a restriction of the standard | Suppliers face a different profile in each country |
That last row is the one that still bites. A supplier who has built one conforming invoice and expects it to be accepted everywhere discovers that Italy wants a national format, Germany wants its own profile, and a French public body wants delivery through a specific portal. The semantic model is common; almost nothing else is. That is what a core invoice usage specification does, and it is the layer that turns one standard into a dozen targets.
What it means for a supplier today
If you sell to public bodies in more than one Member State, the directive gives you a floor and not a ceiling. The floor is that a conforming invoice cannot be refused for being electronic. The ceiling is set by whatever profile and channel that specific authority uses, and by whether the country has since layered a business-to-business mandate on top with a different format again.
Three practical consequences:
- Do not assume one integration covers both. Business-to-government and business-to-business channels are separate in several countries, including Italy and Spain — different portals, sometimes different formats, always different onboarding.
- The public-sector profile is usually the stricter one. Public bodies add references that a commercial buyer does not: contract numbers, budget lines, project codes. They are carried in the standard, but only if somebody populates them.
- Rejection is quiet. A public portal that rejects an invoice does not usually telephone you. Somebody has to be watching the channel, which is an operational commitment, not a project task. That belongs in exception handling.
What the asymmetry cost, and who paid it
The design was right and it was not free, and it is worth being honest about where the bill landed.
Because the obligation sat on the receiving side, public bodies had to be able to process a conforming invoice whether or not anybody sent them one. A great deal of public money was spent on receiving capability that was, for the first years, substantially idle. That was the price of solving the collective action problem, and it was paid by administrations rather than by suppliers, which is the correct way round when one side is many small businesses and the other is a small number of large institutions.
Suppliers paid a subtler cost. An obligation to receive creates no obligation to send, so adoption depended on each supplier deciding that structured invoicing was worth doing. Many did not, and the ones who did frequently discovered that the public body's receiving capability, while conforming, had been implemented once and then left. A conforming invoice rejected by a portal nobody maintains is a real experience and it is the reason the early reputation of European e-invoicing was worse than the standard deserved.
The lasting consequence is a two-speed picture that persists today: business-to-government invoicing has been possible for years and is still not universal, precisely because possible is not the same as compulsory. Every subsequent national mandate has learned that lesson and put the obligation on both sides.
How this fits the wider picture
Directive 2014/55/EU is the reason the European e-invoicing conversation is about a semantic model rather than about file formats. It solved the collective action problem — nobody builds to a standard that does not exist, and no standard gets written for a market that does not exist — by putting the obligation on the party that could bear it.
Everything national since has taken the same standard and narrowed it. Whether the narrowing happens in a published national profile or in a platform's own validation rules, the shape of the problem is set here.
