Doing Business Abroad Pilot

From DE4A
Revision as of 09:30, 19 January 2023 by Ard.vanderheijden (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


The Doing Business Abroad (DBA) pilot of the DE4A project implements eProcedures for starting and doing business cross-border in Austria, the Netherlands, Romania and Sweden. It improves currently available cross-border procedures by implementing the Once Only Principle (OOP) and Digital-by-default. Under the explicit request of the company’s representative, the eProcedure portal will retrieve company registration evidence directly from the authentic source in the Member State of registration in the first pilot iteration. The second pilot iteration adds - amongst others - a mechanism to notify the eProcedure portal of business events that might impact its eServices (e.g. the company goes bankrupt - subscription & notification pattern) and allows for a light weight updating of company data (Lookup pattern). Piloting solutions to these highly complex processes are an important step in breaking down barriers in the European single market. In the end companies should be able to do business in any other Member State as easy as they do nationally.

The DBA pilot addresses some of the most important (research) questions for successfully implementing the SDGR and SDGR-related processes. Besides validating the OOP technical System for evidence exchange in real use cases, the DBA pilot extends the use of eIDAS to include representation scenarios: a natural person representing a company to apply for a specific eProcedure in another Member State. An adequate solution for authenticating on behalf of companies is needed to implement the eServices to business that have been defined in the second annex of the Regulation. Using eIDAS authentication ‘on behalf of’ to start an eProcedure in the SDGR-domain requires coordination by the eProcedure portal: invoking eIDAS and using the result in an evidence request to the OOP Technical system. The portal can only do this when the concepts and solutions of both domains are fully aligned and the domains are connected. This is of special interest to the DBA pilot. Furthermore, the DBA pilot evaluates several SDGR-specific and related functions, like evidence exchange using the OOP TS components (including the DE4A connector), explicit request and preview, generation and exchange of canonical evidence and record matching. Finally, the DBA pilot provides guidance on future evolution of cross-border information flows by exploring a mechanism to notify public authorities of relevant business events impacting the eServices they provide.


Additional pilots Use Case 1: