Electronic invoicing is usually presented as an accounting and tax reform.
Structured invoices.
Automated reporting.
Standardized data.
New obligations for businesses.
But while working on electronic invoicing systems, I started looking beyond the invoice itself.
What happens to the data once transactions become structured?
What other European digital infrastructures can connect to it?
And how far do those connections actually go?
That question led to a much larger investigation.
Electronic Invoicing Is Only One Piece
Electronic invoicing does not exist in isolation.
At the same time, Europe is developing or deploying other digital infrastructures around products, identity and payments.
Taken separately, they look like different projects.
But their interfaces matter.
A transaction can identify a product.
A product can be connected to a Digital Product Passport.
A Digital Product Passport can contain structured information about that product, including environmental information.
Digital wallets can carry electronic credentials.
Payment infrastructures can interact with external systems and conditions.
The interesting question is therefore no longer whether each system exists independently.
It is whether they can communicate.
Following the Data Changes the Picture
The first chain examined in the investigation looks like this:
Electronic invoicing
↓
Transaction data
↓
Product identification
↓
Digital Product Passport
↓
Environmental data
None of these steps, considered individually, demonstrates the existence of a larger unified system.
But the connections themselves are important.
They show how structured transaction data can progressively be associated with increasingly detailed information about what was purchased.
Identity and Payments Form Another Chain
A second group of infrastructures develops around identity and payments.
Digital identity / wallet
↓
Electronic credential
↓
Payment
↓
External conditions
This is where the distinction between technical capability and actual use becomes essential.
The digital euro, for example, must not simply be described as "programmable money."
The European framework explicitly distinguishes programmable money from conditional payments.
A conditional payment can depend on predefined conditions without turning the currency itself into programmable money.
That distinction matters.
The Bridges Are No Longer Entirely Theoretical
This was one of the most interesting results of the investigation.
I started with a question:
Could these systems eventually be connected?
After examining official documentation, standards, technical architectures and experiments, the question changed.
Several bridges already exist, are standardized, planned or have been experimented with.
So the investigation moved from:
**HYPOTHESIS**
These systems might
one day be connected
to:
**OBSERVATION**
Several connections already exist,
are standardized,
planned
or have been experimented with
That does not mean everything is already connected.
It means the documentary boundary is further down the chain than it initially appears.
And This Is Where the Evidence Stops
There is a final chain that the investigation does not establish.
Environmental data
↓
Individual profile
↓
Imposed rule
↓
Economic or monetary restriction
↓
NOT ESTABLISHED
This distinction is fundamental.
Technical possibility is not the same thing as actual use.
Actual use is not the same thing as legal authorization.
And interoperability between infrastructures does not prove that they were designed for one common purpose.
The investigation therefore does not claim that an environmental score is currently being used to restrict an individual's payments.
It does not establish the existence of a centralized system controlling individual consumption.
And it does not attribute an undocumented intention to the institutions involved.
But the Opposite Conclusion Would Also Be Wrong
Saying that such a unified system exists today would go beyond the evidence.
But saying that the different infrastructures are completely isolated would also ignore documented technical connections.
The reality is more interesting.
Separate projects
↓
Structured data
↓
Standardized interfaces
↓
Increasing interoperability
↓
?
Electronic invoicing, product identification, environmental information, digital identity and payment systems remain separate projects.
But several of the technical bridges between them are real.
And as interoperability increases, studying each infrastructure independently becomes less useful.
The architecture has to be examined as a whole.
Why I Published the Investigation
I wanted the distinction between facts and deductions to remain visible.
So every major element of the investigation is classified according to its level of evidence.
ESTABLISHED
TECHNICALLY DEDUCIBLE
HYPOTHESIS
TO BE ESTABLISHED
The objective is not to prove a predetermined conclusion.
It is to determine exactly where the documentation takes us.
And where it stops.
The complete investigation is public, including the sources, individual chapters and methodology.
Read the Investigation
English version
Version française
GitHub repository — complete investigation and sources
The GitHub repository contains the complete investigation, the seven individual chapters and the source register.
Everything is public so the connections can be verified, challenged or explored further.
One Question Remains
Electronic invoicing is arriving now.
Digital Product Passports are developing.
European digital identity infrastructure is developing.
Payment infrastructure is evolving too.
Each project has its own purpose, legal framework and timeline.
But their ability to exchange structured data is increasing.
So perhaps the most interesting question is no longer:
What does electronic invoicing change?
It is:
What becomes technically possible when systems capable of identifying a transaction, a product, its characteristics, an identity and a payment become interoperable?
That is the question this investigation tries to document.
Top comments (0)