Qualified Electronic Delivery – the foundation of the European Business Wallet

Obserwatorium biz » articles

Table of contest:

Abstract 

The European Business Wallet is planned to be a real instrument for the digital economy. It extends their main functions of digital identity, electronic seals, or the presentation of business attributes by supporting legally effective communication among companies, public authorities, and other market participants. This is where qualified electronic registered delivery becomes essential. eDelivery provides the parties with proof that a message was sent, made available, received, or refused, and it creates a reliable evidence trail for business and administrative processes. The experience of Poland and Italy shows that electronic delivery can become a large-scale economic infrastructure, but it needs to be levelled up to become a pan-European solution.  

The Business Wallet is more than a digital identity tool 

The European Business Wallet is usually presented as a tool that will allow a company to identify itself, prove its attributes, act through authorised representatives, sign documents and exchange verified data. All these functions are important. They can reduce paperwork, simplify cross-border processes and make business interactions more reliable. However, they do not answer one basic question: how should a company formally communicate with another company or with a public authority in a way that is legally effective across the European Union? 

In traditional business and administrative processes, this role has been played by registered letters, official notifications, certified mail or national public portals. These tools are not only about sending information. They also create legal evidence. They show when a document was sent, when it was delivered, who was the sender, who was the recipient, and whether the communication can be relied on in court or in an administrative procedure. This is why qualified electronic registered delivery should be treated as a core element of the wallet ecosystem. 

Qualified electronic delivery as the legal transport layer 

Qualified electronic registered delivery is a digital equivalent of registered mail, but with stronger technical control and better evidence. The service not only transports a message. It identifies the sender and the recipient, protects the content against unauthorised change, records important events and produces evidence that can later be verified. 

For the European Business Wallet, qualified electronic delivery should become the legal transport layer. The wallet can identify a company, electronic attestations can prove that the company exists, or that a person is authorised to act on its behalf. Electronic signatures and seals can protect declarations and documents. But the delivery service addresses a different need: providing evidence that the document was effectively sent and delivered to the right party. 

For many business and public-sector processes, the moment of delivery starts deadlines, creates obligations or proves that a party was informed.  

Qualified trust service providers  

The European Business Wallet will need a broad range of trusted functions: identification, onboarding, certificates, electronic seals, electronic signatures, timestamps, attribute management, delivery, evidence and possibly long-term preservation. These are not ordinary IT services. They are functions that must be reliable, auditable and trusted by other parties. 

Qualified trust service providers are therefore natural operators or key partners in the Business Wallet ecosystem. They already operate under a regulated trust framework. They understand audit, assurance, evidence, certificates, key management and legal reliability.  

A qualified provider could offer a practical business bundle: business onboarding, electronic address, electronic seal, qualified delivery mailbox, signature support, mandate management and evidence storage. This would make the Business Wallet useful in everyday operations, not only in high-level policy scenarios. 

The EBW will work only if businesses and public bodies are reachable 

A wallet is useful only if other parties can be reached through it or through a connected trusted channel. For this reason, the central issue is reachability. Every economic operator and every public authority in the European Union should have a legally recognised electronic delivery address, or at least a clearly defined method for receiving qualified electronic delivery. This does not necessarily mean that every company must use the same wallet application. It means that every company should be reachable in a trusted, standardised and legally effective way. 

This is similar to the role of a bank account number in payments. A person or company may use different banks, interfaces, and mobile applications, but the payment system works because the account number can be routed to the correct institution. Electronic delivery needs the same logic. A delivery address should identify the recipient and allow the sending operator to find the correct receiving operator. 

Public and private communication must be treated together 

One of the key lessons from national electronic delivery systems is that a model limited to communication with public administration alone is insufficient. It may help offices send decisions or receive applications, but it does not create a real digital economy. Businesses need a reliable channel for communication with other businesses, employees, consumers, banks, insurers, suppliers, and regulated partners. 

The European Business Wallet should therefore support communication in several directions: from business to administration, from administration to business, between businesses, and in selected cases also between businesses and natural persons. A company should be able to receive a tax notice, send a regulated notification, exchange contract documents, communicate with a supplier, handle formal employee correspondence and receive legally relevant consumer requests through one coherent trust framework. 

The experience of the Polish market shows the risk of creating a special public service that covers only part of the communication landscape. If the public operator is privileged and the service is designed mainly for public-sector needs, the private market may remain weak. Businesses may receive a formal address, but the system may not reflect their real operational needs, such as multiple functional addresses, integration with document management systems, automated workflows or commercial service levels. 

Lessons from Poland and Italy 

Poland and Italy are two of the most interesting examples for the European debate on electronic delivery. They show two different paths and two different sets of lessons. 

Italy has long experience with certified electronic mail. Its system became widely used because businesses and many professionals were required to have a certified address. This created a large base of reachable entities and made electronic delivery a normal part of economic life. The Italian model also shows the value of a competitive provider market. Many providers can offer services, compete on usability and price, and build additional solutions for businesses. 

Poland, on the other hand, is building a newer system designed around electronic delivery addresses, interoperability and qualified trust service providers. The Polish model is important because it tries to create a unified delivery environment in which different operators can exchange messages and evidence. It also shows how important addressing, routing and shared infrastructure are for the system to function. 

At the same time, both experiences show risks. A market can become fragmented if national standards are not aligned with European ones. A system can become too centralised if a single public operator or platform is given too much control. A delivery infrastructure can become difficult to use if address registration or operator discovery is not simple and reliable. These lessons should be used when designing the Business Wallet communication layer. 

Standardisation is the condition  

Qualified electronic delivery cannot work at European scale if each Member State defines its own formats, events, evidence models and interfaces. A sender in one country must know that a message sent to a company in another country will be processed according to predictable rules. The receiving party must know how to verify the evidence. Courts and public authorities must understand the legal meaning of the delivery record. 

This requires standardisation at several levels. First, the technical exchange between delivery operators must be standardised. Operators should exchange messages and evidence using the same or compatible interfaces. Secondly, the evidence model must be standardised. The same types of events should be recorded in a comparable way: submission, acceptance, making available, delivery, refusal, expiry or failure. Thirdly, addressing and discovery must be standardised. It must be possible to find the operator responsible for a delivery address without relying on manual checks or national portals. 

Europe should avoid central national hubs 

One tempting design would be to create national hubs and route all wallet-related communication through them. This may look simple from the perspective of a public administration. Each country would have one gateway, and other countries would connect to that gateway. However, this approach creates several risks. 

A national hub will become a bottleneck, and if it fails, a large part of communication may fail. Communication based on central hubs concentrates operational and political control over communication. National hubs may reduce competition between providers because all providers must adapt to the hub and its rules, an in the end, it may slow innovation because any change must pass through central governance. 

A better model is closer to the internet or to payment networks. Many operators should be able to connect with each other directly or through agreed network arrangements. They should follow the same rules, use the same standards and trust each other through a common supervisory and certification framework. The user should be able to choose a provider, while the system should still guarantee that messages can be delivered to users of other providers. 

This is the logic of the four-corner model: sender, sender’s service provider, recipient’s service provider and recipient. It gives the market room to grow, while preserving interoperability. It also avoids turning the Business Wallet into a set of national communication silos. 

Addressing is the hidden foundation 

Electronic delivery depends on addresses. This may sound obvious, but addressing is one of the most important and most difficult parts of the system. A delivery address is not just a contact detail. It is a legal identifier used to deliver important communications. It must therefore be stable, trustworthy and easy to resolve. 

A good European addressing model should meet two basic conditions. First, the identifier should be durable. Once a delivery address is assigned to a company, authority, or person, it should not later be reassigned to someone else in a way that could cause confusion. The address should remain linked to the same entity, or the lifecycle rules should clearly explain what happens when the entity changes, merges, closes or moves to another provider. 

Secondly, the address must be discoverable. A sender should be able to check whether a recipient has an electronic delivery address, which operator serves it and how to route the message. This discovery mechanism should not be fragile. It should not depend on one overloaded central database. A distributed or federated model may be more suitable, provided that it gives reliable answers and supports cross-border use. 

The address should also support real business needs. Large organisations often need more than one address. A municipality may have many units. A company may want separate addresses for legal notices, procurement, employment, claims, regulated reporting or customer relations. The system should support a single official address, as well as functional addresses and automated routing. 

European electronic delivery policy  

Member States have different legal and technical traditions in electronic delivery. Some rely on certified email other rely on public portals and some building new electronic delviery systems. Others may have sectoral solutions for courts, tax, procurement or social security. This diversity cannot simply disappear. However, the Business Wallet needs a common layer above national differences. 

A common European delivery policy should define what it means to deliver a message through the EBW ecosystem. It should clarify when a message is considered sent, when it is made available, when it is considered delivered, what happens if the recipient does not open it, and what evidence must be created. It should also define how long evidence should be available and who is responsible for preserving it. 

Such a policy should also address the role of operators. It should specify minimum obligations for service availability, incident handling, identity verification, cooperation with other operators, dispute resolution and audit. The goal is not to eliminate national law, but to ensure that cross-border EBW communication has the same practical meaning in all Member States. 

Without this policy layer, the same electronic message may have different legal effects depending on the country. That would be unacceptable for a tool that is supposed to support the Single Market. 

Support for real business processes 

The European Business Wallet should be designed around real processes, not only around technical capabilities. Businesses will use it if it solves everyday problems. Electronic delivery can help in many such processes. 

In company formation, the wallet could support the exchange of verified data, mandates and official notifications. In public procurement, it could support formal communication between contracting authorities and bidders. In tax and regulatory procedures, it could provide a secure channel for notices, requests and decisions. In contract management, it could support the exchange of signed documents and evidence that all parties received them. In employment relations, it could help deliver formal notices securely and in a documented manner. In consumer relations, it could provide consumers with a reliable channel to contact large companies on matters often hidden behind portals and call centres. 

This last point is important. Many large service providers control communication through their own portals. The user can do only what the portal allows. A recognised electronic delivery address would rebalance this relationship. A consumer, employee or smaller business could send a formal message through a trusted channel and receive evidence that it was delivered. 

For public administrations, electronic delivery through the Business Wallet could reduce paper, improve automation and support cross-border services. For businesses, it could reduce uncertainty and make formal communication easier. For citizens and consumers, it could create a more equal channel for important interactions with companies. 

Market participation  

The EBW communication layer should not be designed only by public authorities and central IT contractors. It must be designed with and for the market. Qualified trust service providers, business software vendors, ERP providers, banks, chambers of commerce, legal tech platforms, public administrations, document management providers and large regulated businesses should all be involved. 

This is not only a matter of consultation. It is a matter of usability. If the system is misaligned with business processes, companies will treat it as just another compliance obligation. If it aligns with their workflows, it may become a useful tool that reduces costs and risk. 

Market participation is also necessary for competition. A wallet and delivery ecosystem built around one or a few privileged public operators will not create enough innovation. A market based on qualified providers, common standards and open interfaces can support different business models and service levels. It can also allow national and sectoral specialisation without breaking European interoperability. 

Conclusion 

The European Business Wallet can become one of the most important tools for the digital Single Market. But its success will depend on whether it supports complete business interactions, not only electronic identity and electronic seals. A company must be able to prove who it is, prove who may act on its behalf, sign or seal documents, and communicate with legal effect. Qualified electronic delivery is the element that connects these functions into a real process. 

The main challenge is not only technical. It is organisational and regulatory. Europe needs a delivery network that is interoperable, provider-neutral, standardised and useful for both public and private communication. It needs durable addresses, reliable discovery mechanisms, common evidence and clear operator obligations. It also needs a competitive market of trusted providers, not a set of isolated national portals. 

Poland and Italy show that electronic delivery can be deployed at scale and can become part of everyday economic life. Qualified electronic registered delivery should be treated as the communication backbone of the European Business Wallet, and with it, the wallet can become a trusted environment for legally effective business communication across Europe. 

Publication date: 15.05.2026