Electronic invoicing is usually presented as an accounting and tax reform. From a technical perspective, however, it also represents a transition toward structured, standardized transaction data.
At the same time, other European digital infrastructures are developing around product identification, environmental information, electronic credentials, and payments.
Each infrastructure has its own purpose, architecture, legal framework, and implementation timeline.
The technical question is how these systems can exchange information, what interfaces already exist or are being developed, and where the documented evidence stops.
This article examines these infrastructures from a data architecture perspective, distinguishing documented interoperability from technically possible but unestablished integrations.
1. Electronic Invoicing as Structured Transaction Data
A conventional invoice is primarily a document intended to communicate commercial and accounting information.
An electronic invoice adds another dimension: its contents can be represented as structured data that software can process.
Depending on the applicable standard and document structure, this information can include:
- Supplier and customer identifiers
- Invoice references and dates
- Product or service descriptions
- Quantities and unit prices
- Tax information
- Payment amounts and terms
The distinction between visual presentation and structured information is particularly important.
Invoice
│
├── Human-readable representation
│ └── PDF document
│
└── Machine-readable representation
└── Structured invoice data
A structured invoice does not necessarily require a separate PDF. Some electronic invoicing formats use structured XML, while hybrid formats combine a human-readable document with embedded structured data.
The central architectural change is that invoice information becomes directly accessible to software without requiring manual transcription or interpretation of a visual document.
2. From Documents to Interoperable Data
Once information is structured, it can be processed by different systems.
Consider a simplified transaction record:
{
"invoice_id": "INV-2026-001",
"seller_id": "SELLER-001",
"buyer_id": "BUYER-001",
"items": [
{
"product_id": "PRODUCT-042",
"quantity": 2,
"unit_price": 100.00
}
],
"currency": "EUR",
"total": 200.00
}
This is an illustrative JSON representation, not an official electronic invoicing format.
The important element is that each value has an identifiable role.
A software system can distinguish an invoice identifier from a product identifier, a quantity from a price, or a buyer identifier from a seller identifier.
Structured data makes automated processing possible, but interoperability requires more than the ability to read a file.
Several conditions must be met:
| Requirement | Purpose |
|---|---|
| Shared identifiers | Identify corresponding entities |
| Compatible formats | Exchange information between systems |
| Semantic consistency | Preserve the meaning of data fields |
| Accessible interfaces | Enable authorized data exchange |
| Access rules | Define who can retrieve information |
Two systems may both use XML or JSON without being interoperable.
They must also agree on the meaning of the exchanged information, the identifiers used to reference entities, and the conditions under which access is permitted.
3. Product Identification and Digital Product Passports
Electronic invoicing is not the only infrastructure developing around structured commercial information.
Digital Product Passports introduce a separate approach to organizing information associated with products.
Depending on the product category and applicable requirements, a passport may provide information relating to:
- Product identification
- Materials and composition
- Repairability or durability
- Environmental characteristics
- Other product-specific information
The connection with electronic invoicing can be examined through product identification.
Electronic invoice
│
▼
Transaction data
│
▼
Product identification
│
▼
Digital Product Passport
│
▼
Product characteristics
This diagram represents a potential data relationship, not a universally deployed processing pipeline.
An invoice may contain an identifier associated with a product. A product passport may contain information associated with that same product.
If the identifiers can be resolved across the two systems, a relationship between transaction information and product information becomes technically possible.
However, an invoice containing a product description does not automatically establish a connection with a Digital Product Passport.
The identifier, its scope, and the mechanism used to resolve it all matter.
4. Shared Identifiers as an Architectural Bridge
A common identifier can provide a connection between otherwise independent datasets.
Consider two simplified records.
Transaction data:
{
"transaction_id": "TX-001",
"product_id": "PRODUCT-042",
"quantity": 2
}
Product data:
{
"product_id": "PRODUCT-042",
"category": "Example product category",
"environmental_information": {
"reference": "ENV-042"
}
}
Both records contain the same product identifier.
A conceptual relationship can therefore be represented as:
Transaction record
│
│ product_id
▼
Product record
│
▼
Environmental information
In software architecture, this resembles a relationship between records that can be resolved through a shared key.
However, several practical questions remain.
Does the invoice use the same identifier as the passport?
Does the identifier refer to a product model, a batch, or an individual item?
Can the corresponding product information be retrieved?
Which fields are accessible, and under what conditions?
These questions determine whether a theoretical relationship can become an operational integration.
The example illustrates the architectural principle of identifier-based interoperability. It does not establish that a specific European invoicing system currently performs this lookup.
5. Environmental Data and Transaction Context
Product information and transaction information describe different entities.
A product passport may describe the characteristics of a product.
An invoice describes a commercial transaction involving one or more products or services.
Connecting these datasets could provide additional context about the items involved in a transaction.
For example:
Transaction
├── Product identifier
├── Quantity
└── Commercial information
Product passport
├── Product identifier
├── Product characteristics
└── Environmental information
If the identifiers and interfaces are compatible, the two records could potentially be associated.
That association would not automatically produce an environmental assessment of the buyer.
Additional processing would be required to establish such an assessment, including rules for aggregation, attribution, and interpretation.
The distinction is important:
| Data category | What it describes |
|---|---|
| Transaction data | A commercial transaction |
| Product data | An identified product |
| Environmental data | Characteristics or impacts |
| Individual profile | Information attributed to a person |
Moving from product characteristics to an individual profile is a separate processing operation.
It cannot be inferred simply from the existence of structured invoices or Digital Product Passports.
6. Digital Identity and Electronic Credentials
European digital identity infrastructure introduces another category of structured information.
Digital wallets can carry electronic credentials that allow information or attributes to be presented and verified.
From an architectural perspective, a credential exchange involves several distinct roles.
Credential issuer
│
▼
Electronic credential
│
▼
Digital wallet
│
▼
Credential presentation
│
▼
Verification
An electronic credential may represent an identity attribute, a qualification, an authorization, or another verifiable statement.
The wallet provides a mechanism for managing and presenting credentials.
The verification process determines whether the presented information satisfies the requirements of a particular interaction.
This does not mean that every digital wallet contains a complete personal profile or that every interaction exposes all available identity information.
The data exchanged depends on the credential, the protocol, the requested attributes, and the applicable access rules.
Identity Is Not the Same as Authorization
An identity attribute may establish who a person is.
An authorization may establish whether a person is permitted to perform a specific action.
These are different operations.
Identity verification
│
▼
Attribute verification
│
▼
Authorization decision
A system capable of verifying an electronic credential does not automatically have the authority to impose a restriction on a financial transaction.
That requires a separate authorization mechanism and an applicable legal basis.
7. Payment Systems and External Conditions
Payment infrastructure represents another layer in the broader architecture.
A payment system processes the transfer of value between parties.
A conditional payment introduces a relationship between the execution of a payment and a predefined condition.
A simplified example is a payment executed after a delivery has been confirmed.
Delivery confirmation
│
▼
Condition evaluation
│
▼
Payment execution
The condition exists outside the monetary value itself.
An external system may provide information indicating whether the condition has been satisfied.
The payment can then be executed according to the applicable arrangement.
A conceptual representation might look like:
{
"payment_id": "PAY-001",
"amount": 200.00,
"currency": "EUR",
"condition": {
"type": "delivery_confirmation",
"status": "pending"
}
}
This example illustrates conditional payment logic. It is not an official digital euro message format or a documented implementation of a particular payment platform.
The important architectural distinction is between the payment instruction, the condition evaluation mechanism, and the monetary instrument used to execute the payment.
8. Conditional Payments vs. Programmable Money
The digital euro is relevant to this discussion because European documentation explicitly distinguishes conditional payments from programmable money.
These concepts should not be treated as equivalent.
| Concept | Architectural distinction |
|---|---|
| Conditional payment | Execution depends on defined conditions |
| Programmable money | Restrictions are attached to the money |
| External service | Provides information or triggers |
| Payment execution | Transfers monetary value |
A conditional payment can be linked to an event or contractual condition without changing the general usability of the currency.
Programmable money, by contrast, would involve restrictions attached to monetary units themselves, potentially limiting how or where they can be used.
The proposed digital euro framework distinguishes between these concepts and excludes programmable money.
That distinction must remain visible when examining technical interoperability between payment systems and external services.
The existence of conditional payment functionality does not establish that public authorities can impose arbitrary spending restrictions.
Technical capability, contractual authorization, and legal authority remain separate questions.
9. Interfaces Between Independent Infrastructures
The infrastructures examined so far can be represented as separate domains.
Transaction domain
└── Electronic invoicing
Product domain
└── Digital Product Passports
Identity domain
└── Digital wallets and credentials
Payment domain
└── Payment instructions and execution
Each domain can have its own data models, interfaces, access rules, and operational responsibilities.
Interoperability becomes possible when a relationship can be established between information in different domains.
For example:
Transaction
│
├── Product identifier
│ └── Product information
│
├── Party identifier
│ └── Identity-related information
│
└── Payment reference
└── Payment information
This is a conceptual architecture showing possible relationships between data categories.
It is not a representation of an existing centralized European platform.
The investigation underlying this article identifies technical bridges that are documented, standardized, planned, or have been examined through experiments.
These categories are not interchangeable.
| Evidence category | What it establishes |
|---|---|
| Documented | A connection is described |
| Standardized | An interface or format is specified |
| Planned | An implementation is intended |
| Experimented | A capability has been tested |
| Operational | A connection is deployed and in use |
A standardized interface does not prove that every relevant system implements it.
An experiment does not prove widespread deployment.
A planned integration does not establish current operational use.
The maturity of each connection must therefore be evaluated independently.
10. Interoperability Does Not Require a Centralized Database
One architectural misconception is that interconnected infrastructures necessarily require a single database containing all available information.
Different systems can remain independently operated while exchanging selected information through interfaces.
A conceptual distributed architecture could look like this:
Invoice system
│
├── Authorized product lookup
│ └── Product system
│
├── Authorized credential check
│ └── Identity system
│
└── Payment instruction
└── Payment system
The original records can remain within their respective systems.
Only the information required for a specific operation may need to be exchanged.
However, distributed storage does not automatically eliminate privacy risks.
If a system can repeatedly retrieve and correlate information from multiple sources, it may still create a detailed representation of transactions or entities.
The relevant questions therefore include:
- Which identifiers are shared across systems?
- Which information can be retrieved?
- Who is authorized to retrieve it?
- Can information be retained or combined?
- Are exchanges limited to a specific purpose?
- Can access be audited or revoked?
These are architectural and governance questions rather than evidence that a particular centralized system already exists.
11. Separating Technical Capability From Operational Use
A documented interface establishes that certain information can be exchanged under defined conditions.
It does not establish every possible use of that information.
Consider the following conceptual sequence:
Structured transaction data
│
▼
Product identification
│
▼
Environmental information
│
▼
Individual profile
│
▼
Imposed rule
│
▼
Economic restriction
The first part of the sequence concerns relationships between transaction data, product identifiers, and product information.
The later stages introduce additional operations:
- Attributing transaction information to an individual
- Creating and maintaining an individual profile
- Defining a rule based on that profile
- Applying the rule to an economic or monetary decision
Each operation would require its own technical implementation, data access arrangements, and legal authorization.
The investigation does not establish the existence of this complete operational chain.
In particular, it does not establish that an environmental score is currently used to restrict individual payments, that a centralized consumption-control system exists, or that the infrastructures were designed for a single coordinated purpose.
This boundary is essential.
A technically possible integration should not be presented as an existing system.
12. An Evidence-Based Method for Architecture Analysis
Studying interconnected infrastructures requires a method that distinguishes what documentation establishes from what can only be inferred.
The investigation uses four levels of evidence.
| Evidence level | Interpretation |
|---|---|
| Established | Supported by documented evidence |
| Technically deducible | Follows from documented capabilities |
| Hypothesis | A possible but unconfirmed scenario |
| To be established | Requires additional supporting evidence |
These levels can be applied to individual interfaces, data relationships, or proposed processing chains.
For example:
Documented interface
│
▼
Established capability
│
▼
Potential integration
│
▼
Technically deducible
│
▼
Specific operational use
│
▼
Requires separate evidence
A technically deducible capability may be useful for evaluating architectural risks or future integration scenarios.
However, it does not carry the same evidentiary weight as a documented operational deployment.
The methodology prevents the analysis from moving directly from the existence of an interface to conclusions about how institutions or organizations are using it.
13. Security and Privacy Across System Boundaries
Interoperability creates additional security considerations because information may move between systems with different trust boundaries.
An architecture that exchanges transaction, product, identity, or payment information must address several questions.
| Security consideration | Architectural objective |
|---|---|
| Authentication | Verify the requesting entity |
| Authorization | Restrict access to permitted operations |
| Data minimization | Exchange only necessary information |
| Purpose limitation | Restrict processing to defined purposes |
| Auditability | Record relevant access and exchanges |
| Data integrity | Preserve the accuracy of exchanged data |
| Retention controls | Limit unnecessary data storage |
These are general architectural requirements, not claims that every infrastructure discussed implements identical controls.
For example, verifying a credential does not necessarily require access to all identity information.
Retrieving product characteristics does not necessarily require access to the identity of the purchaser.
Executing a payment does not necessarily require disclosure of every product included in an invoice.
The design of the interfaces determines how much information must cross each boundary.
A useful security principle is to separate the information required for an operation from information that is merely available elsewhere in the architecture.
14. What an Interoperability Assessment Should Examine
Evaluating the relationship between these infrastructures requires more than listing the projects involved.
A technical assessment should examine the actual connections.
System A
│
├── Data model
├── Identifiers
├── Access permissions
└── Interface
│
▼
System B
│
├── Received information
├── Processing purpose
├── Retention rules
└── Possible downstream exchanges
For each connection, the analysis should establish:
- Whether the interface is documented
- Whether compatible identifiers exist
- Whether the exchange is technically supported
- Whether it has been tested or deployed
- Which parties can initiate the exchange
- Which data can be accessed or retained
- Which legal framework governs its use
This approach makes it possible to examine interoperability without assuming that every technically conceivable connection is operational.
It also avoids the opposite mistake of treating independently developed systems as necessarily isolated.
The relevant unit of analysis is the documented relationship between systems, including its technical capabilities and its constraints.
Conclusion
Electronic invoicing, Digital Product Passports, digital identity infrastructure, and payment systems represent distinct domains of digital architecture.
Their development introduces structured data, standardized formats, identifiers, credentials, and interfaces that can support information exchange.
Several technical bridges between these domains are documented, standardized, planned, or have been examined through experiments. Their maturity and operational scope must be assessed individually.
The existence of these bridges does not establish a unified infrastructure controlling individual consumption or payments.
Nor does the independence of the projects establish that information cannot move between them.
The central architectural question is how interoperability changes the relationships between data, systems, and authorized operations.
Answering that question requires a clear distinction between documented capabilities, technical deductions, hypothetical integrations, operational deployment, and legal authorization.
Research Documentation
The complete investigation, its seven chapters, evidence classification methodology, and source register are available in the public documentation repository.
The documentation provides the underlying material for examining the individual infrastructures and their documented technical relationships.
View the investigation and source register on GitHub

Top comments (0)