European Business Wallet trilogue: one European standard or 27 national variants

The European Business Wallet trilogue will not settle a technical footnote. It will settle the shape of a product that companies and their integrators have to work with from the moment the acceptance clock starts running. Either Europe ends up with one wallet carrying one legal effect and one set of requirements, or it ends up with twenty-seven national implementations sharing a European label. In practice that is the difference between one integration and twenty-seven, and between a cross-border process that behaves identically everywhere and one that has to be rebuilt for each member state.

The Council of the European Union fixed its negotiating position on 9 June 2026. The European Parliament has not yet fixed its own. This interval, with one co-legislator finished and the other still working, is exactly the point at which a company or an integrator can separate the design decisions that are safe to make now from the ones that have to wait.

Where the file stands on 5 September 2026

The file is 2025/0358(COD), the ordinary legislative procedure on the Commission proposal COM(2025) 838 final of 19 November 2025. As of 5 September 2026 the position is as follows.

• The Council adopted a general approach on 9 June 2026 and therefore holds a negotiating mandate.
• The European Parliament has not adopted a position. In ITRE, the lead committee, the draft report was tabled on 1 April 2026 and amendments were tabled on 23 April 2026. The IMCO and JURI opinions were delivered on 4 June and 8 June 2026 respectively. LIBE and BUDG decided not to give an opinion.
• The Legislative Observatory still lists the procedure as awaiting committee decision. No ITRE vote date, no plenary date and no trilogue date have been scheduled and published.
• Trilogues can only begin once Parliament has its position. EU leaders have called for a political agreement before the end of 2026, with formal adoption expected after that.

That is the honest state of play. Any supplier or adviser currently describing a settled European wallet specification is describing something the legislator has not yet decided.

Why this phase already affects you

Use of the European Business Wallet (EBW) is voluntary for businesses. The obligation sits on the other side of the counter: public sector bodies must accept the wallet for its core functionalities within twenty-four months of entry into force. That asymmetry changes the calculation for you. Nobody forces you to adopt the wallet, but you are handed a channel that public administrations are required to keep open. Once that channel exists, staying off it becomes a cost rather than a preference, particularly for organisations that tender, invoice or apply for permits in more than one member state.

The Commission estimates savings of up to five billion euro in administrative costs by 2029. The frequently quoted figure of at least 160 billion euro per year in broader savings is the Commission’s own estimate and deserves caution, because it depends entirely on how much harmonisation the trilogue delivers. That dependency is the reason to study the open points of disagreement now rather than after the deal is struck.

Open point one: the legal effect of the wallet

What the Council wants. The general approach keeps the equivalence principle intact: an action carried out through qualified trust services within a business wallet has the same legal effect as if that action had lawfully been carried out in person, in paper form or by any other means. The Council then qualifies it. National administrative and procedural requirements continue to apply, and procedural requirements that wallet functionalities cannot satisfy remain in force unchanged. The authorisation regime leaves existing legislation on powers of representation untouched.

What the Parliament is likely to want. The draft report by rapporteur Eero Heinäluoma (S&D) puts its weight on the shift away from exchanging documents towards machine-readable structured data and full digital interoperability, with the wallet acting as a unifying layer across existing systems, the EUDI wallet and the European data spaces. That logic sits awkwardly with an equivalence that individual member states can claw back through procedural carve-outs. Trade press has read the Council text as a weakening of the legal effect, set against a more ambitious line emerging in Parliament. Parliament has not adopted that line as a text, so this is a direction of travel and not a negotiating position.

What it means for the company. Under the Council line you can use the wallet to identify yourself and sign documents, but each member state retains a residual category of actions that still requires a national form, a notarial step or a paper confirmation. Your compliance process becomes hybrid by design: digital where possible, national handwork where required. Under the Parliament line that residual category shrinks and the wallet becomes a full substitute more often than a supplement.

What it means for the builder. Under the Council line you have to model, per member state, which actions can validly be performed through the wallet. That is not a configuration parameter but a legal decision table, and one that somebody with local knowledge has to populate and maintain. Under the Parliament line the table stays thin, equivalence can be treated as the default, and national deviations become exceptions rather than the rule.

Open point two: national discretion against a single European standard

What the Council wants. Member states may continue applying their existing administrative requirements. That is the substance of the expanded national discretion: the wallet is layered on top of national practice instead of replacing it.

What the Parliament is likely to want. The draft report reasons in the opposite direction. If the objective is structured, machine-readable exchange, then attributes, semantics and the receiving side’s acceptance conditions have to vary as little as possible between countries. A wallet that means something different in every jurisdiction does not produce interoperability, it produces a shared visual identity.

What it means for the company. This is where the cost spread across the two outcomes is widest. In the harmonised outcome you register your company data, representation powers and declarations once and reuse them across all twenty-seven member states. In the discretion outcome you repeat that work country by country, with country-specific evidence, validity periods and acceptance criteria. For a company selling into three or four markets, that is the difference between a project and a programme.

What it means for the builder. In the harmonised outcome you build one credential model and one set of validation rules. In the discretion outcome you build a configurable layer of country profiles, and that layer is the most expensive component in the chain because it is never finished. For an integrator or Peppol Serviceprovider this is the point where architecture is most exposed to the trilogue: an implementation that does not treat country profiles as a first-class concept becomes untenable under the Council line, while an implementation built heavily around them turns out to be needless complexity under the Parliament line.

Open point three: supervision and authorisation of wallet providers

What the Council wants. Higher authorisation thresholds for wallet providers on cybersecurity grounds, and sixty days instead of thirty for national supervisory bodies to assess a provider’s application. The Council adds an obligation for the Commission to specify through implementing acts what documentation a prospective provider must submit, and provides for heavier involvement of the national supervisory body where a provider shows systemic non-compliance.

What the Parliament is likely to want. This is probably the smallest gap of the three. Stricter security requirements enjoy broad political support. The argument is more likely to be about whether an authorisation granted in one member state travels automatically to the others, and about how responsive supervision has to be, than about whether supervision should be strict.

What it means for the company. Expect a smaller and later provider market than the original proposal suggested. A doubled assessment window combined with heavier entry requirements means the first providers go live later, and that smaller member states may end up with only one or two. Factor this into supplier selection: ask not only whether a party intends to become a wallet provider, but in which member states and on what timeline.

What it means for the builder. If you intend to become a wallet provider yourself, plan for a longer and more document-heavy authorisation process whose precise content will only be fixed by implementing acts after adoption. If you integrate rather than provide, the same change works in your favour: fewer providers means less variation in the interfaces you have to support.

The two outcomes of the European Business Wallet trilogue

Put the three open points together and two recognisable outcomes remain.

Outcome A, one European standard. Parliament wins substantial ground on equivalence and harmonisation. The wallet carries the same legal effect everywhere, attributes are defined at European level, and a credential issued in the Netherlands is accepted in Spain without additional national conditions. For the company: configure once, then scale. For the builder: one integration, with national specificity as an edge case.

Outcome B, twenty-seven variants under one label. The Council line prevails. The wallet is technically identical everywhere but legally and procedurally different per member state. For the company: an implementation track per country and a permanently hybrid way of working. For the builder: a country-profile layer requiring continuous maintenance, and a revenue model that rests on configuration and management rather than on a one-off connection.

The realistic result sits somewhere between the two, which is precisely why it pays to work out now which of your design decisions survive either way.

Checklist: what to lock in now and what to postpone

Trilogue-independent, safe to do today

None of the following changes with the outcome of the negotiations, because all of it is needed in either scenario.

1. Clean up your organisational identity data. Company register details, legal form, establishments, VAT registrations and foreign registrations. The wallet exposes this data, it does not correct it. Inaccurate base registration blocks you in either outcome.
2. Document who may act on behalf of the organisation. Representation and mandates are a core EBW function. Record which role may perform which action, up to what value and subject to what limitation. This is company policy rather than European law, and you need it whichever way the file goes.
3. Map your cross-border processes. List the actions for which you currently have to prove identity or authority in another member state: tenders, permits, VAT registrations, customer onboarding, customs procedures. That list will drive your prioritisation later and can be produced now.
4. Get e-invoicing in order through Peppol. The EBW changes nothing about the obligations already approaching through ViDA and national mandates. Organisations that have arranged e-invoicing through a Peppol Serviceprovider are in a better position when the wallet arrives, regardless of the trilogue.
5. Separate identity from transaction in your architecture. For integrators: keep authentication and attribute verification out of your transaction logic. A clean separation turns plugging in a wallet provider later into a connection rather than a rebuild. This is sound architecture independently of the final text.
6. Support structured data instead of documents. Both co-legislators are moving towards machine-readable exchange. Anyone still treating PDFs as the source of truth falls behind in either outcome.
7. Track the WE BUILD pilot. The consortium is testing thirteen use cases across the business, supply chain and payments domains, with the Netherlands Chamber of Commerce and the Dutch Tax Administration among the participants. This is where the practical shape of the wallet becomes visible before the legislator finishes.

Postpone until the agreement lands

Each of the following depends directly on the outcome, and deciding now most likely means paying twice.

1. Final selection of a wallet provider. Authorisation requirements are not settled and will partly be filled in by implementing acts after adoption. Hold the conversations, do not sign multi-year exclusivity.
2. Building a country-profile layer. This is the most expensive component and the one most directly governed by open point two. Design it on paper, do not build it yet.
3. Fixing your per-member-state legal decision table. Which actions are legally valid through the wallet is exactly what open point one puts on the table. Work on the structure of that table, do not populate it.
4. Communicating hard internal deadlines. The twenty-four month acceptance period only starts on entry into force, and that date does not yet exist. Communicate internally in scenarios, not in a single date.
5. Investing in your own provider authorisation. Worth it only if you were going down that route anyway, since the concrete documentation requirements are still to be specified.
6. Freezing the semantic mapping of attributes. Whether attributes end up defined at European or national level is still open. Build the mapping modularly, do not freeze it.

What to watch over the coming months

Three signals genuinely matter and can be followed without a trade press subscription. The first is the ITRE vote on the Heinäluoma report, which is the moment Parliament’s ambition turns into a text. The second is the plenary decision confirming the negotiating mandate, because only then can trilogues formally open. The third is the first trilogue round itself, and specifically whether equivalence and national discretion are handled as one package or as separate items. A package approach usually signals a compromise in which both sides take something home, and that is the scenario in which the country-profile layer turns out to be necessary after all.

Until those three signals arrive, the European Business Wallet trilogue remains an open question, and the split between the two lists above stays your best protection against doing the work twice. Build what holds value in either outcome, design what depends on the result, and hold off on building it until the political agreement exists.

Sources

1. European Commission, Proposal for a Regulation establishing European Business Wallets, COM(2025) 838 final, 19 November 2025
2. European Parliament, Legislative Observatory, procedure file 2025/0358(COD)
3. Council of the European Union, European business wallets: Council adopts negotiating position, 9 June 2026
4. Council of the European Union, general approach, document ST 9684/26, 2 June 2026
5. EPRS, briefing on European business wallets, PE 774.703
6. European Parliament, Legislative Train Schedule, European business wallets
7. EDPS, Opinion 5/2026, 20 January 2026
8. European Commission, policy page on European Business Wallets
9. Table.Briefings, European Business Wallet: Council seeks to expand country-level discretion, 10 June 2026
10. WE BUILD Consortium, news overview

Further reading and independent comparison

The full legislative calendar for this file is set out in our European Business Wallet timeline, and the legal foundation underneath the wallet is explained in European Business Wallet and eIDAS 2.0. How the wallet relates to the addressing problem in e-invoicing is covered in European Business Wallet and e-invoicing.

The first item on the checklist above, getting e-invoicing in order through a Peppol Serviceprovider, can be actioned today and pays off whichever way the negotiations go. The independent Peppol.now comparison tool lets you filter more than one hundred and twenty certified service providers by software environment, invoice volume, target countries and company size, without your details ending up with a sales team. That strengthens the part of your chain that does not depend on the European Business Wallet trilogue, while the rest of your roadmap stays open until the political agreement is in place.