The most consequential sentence in European e-invoicing was not about invoicing at all. It was about consent.
The VAT directive provided that the use of an electronic invoice was subject to acceptance by the recipient. Read in isolation it is a sensible consumer-protection style provision: nobody should be forced to accept a document in a form they cannot read. Read as a constraint on national legislatures, it was the single largest obstacle to mandatory e-invoicing in Europe, and it shaped the entire landscape this site describes.
Why the sentence blocked mandates
A national law compelling a business to receive a structured invoice removes the recipient's ability to decline it. That is a departure from the directive, and a Member State cannot simply legislate a departure from a directive it is bound by.
The route available was Article 395, which allows the Council, acting unanimously on a proposal from the Commission, to authorise a Member State to apply a special measure derogating from the directive in order to simplify collection or prevent evasion.
So every national business-to-business mandate in Europe followed the same procedure. The Member State applied. The Commission examined the request and put a proposal to the Council. The Council decided. Only then could the national timetable start.
What that procedure did to the shape of the mandates
Three effects, and all three are still visible in the mandates in force today.
It added delay at the front. A derogation is not granted quickly. A government that decided in one year to mandate invoicing was legislating in the next, and applying it the year after. Some of the postponements that businesses experienced as administrative incompetence were the timetable meeting a process that could not be compressed.
It made mandates expire. Derogations were granted for a defined period. That produced the odd situation of a national obligation with a legal end date, requiring renewal, which in turn made businesses reasonably uncertain about how much to invest in complying with it.
It rewarded going first. Because each derogation was examined individually, the earliest applicants defined what a plausible request looked like. That is one reason so many national designs resemble one another: they were drafted with an eye on what had already been authorised. Italy's clearance model is upstream of several later designs for exactly this reason, and France's platform model is a deliberate departure from it.
It did not settle the format, the network or the reporting. A derogation authorises a departure from the directive; the substance of the national mandate was always national law. That is why two countries with comparable derogations produced quite different systems.
What the procedure actually required
It is worth being concrete about the mechanism, because its shape explains the mandates it produced.
A Member State wanting to depart from the common rules had to apply, setting out the measure and the reason for it — normally the simplification of collection or the prevention of evasion. The Commission examined the request and put a proposal to the Council, and the Council decided. The authorisation that resulted was specific: it permitted a defined departure, for a defined period, on the terms described in the application.
Three features of that follow directly into the design of the national mandates.
It was time-limited. An authorisation ran to an expiry date and had to be renewed, which meant a Member State building a mandate on one was building on a permission it would have to ask for again. That is a strong incentive to demonstrate that the measure works, and a reason several administrations were unusually attentive to publishing statistics about it.
It was specific. The authorisation covered the measure applied for, so the scope of the mandate was in effect fixed at application. Widening it later — bringing in new taxpayer categories, new transaction types — was not always a purely domestic decision.
And it was slow. The application, the examination, the proposal and the Council decision took time that had to be built into the legislative timetable before any implementation work could safely start. That is a large part of why the mandates of the last decade were announced years ahead and then amended: the lead time was procedural rather than technical, and technical readiness caught up unevenly.
The removal
The VAT in the Digital Age package removes the acceptance requirement for domestic supplies, so a Member State can require structured invoicing without seeking authorisation first.
That is the change that altered the pace. It does not change what any existing mandate requires, and it does not retroactively simplify anything. What it does is remove a year or more from the front of every future national reform, and remove the expiry dates that made the earlier ones feel provisional.
The mistake to avoid
The removal is routinely described as a step towards harmonisation. It is close to the opposite.
Requiring a derogation meant every mandate passed through a common process, was examined against a common standard of justification, and was visible to every other Member State before it took effect. Removing that requirement removes the friction — and the visibility with it. There is no reason to expect that twenty-seven legislatures, each free to act alone, will converge on the same thresholds, the same profiles or the same reporting.
What does push towards convergence is a different part of the same package: a common set of rules for digital reporting of intra-Union supplies, and the requirement that national systems for domestic reporting be consistent with it. Convergence, where it comes, will come from that direction rather than from the removal of an obstacle.
What this means for planning
Two practical consequences.
First, expect more mandates rather than fewer, and expect them to be announced with shorter lead times than the ones that came before. The procedural brake is gone.
Second, stop treating any national timetable as protected by a European process. It is not, and it never really was. The country articles on this site each carry the source that fixes the dates, because that source is now the only thing standing between a published date and a rewritten one.
