Practical examples: markets most affected

• Digital and data-heavy markets: cloud services, digital identity, cybersecurity, AI deployment, data spaces.

• Industrial tech and manufacturing: machinery, robotics, industrial IoT, cross-border conformity assessment.

• Energy systems: grid components, interoperability of energy data, hydrogen/smart grids, EV charging ecosystems.

• Health and life sciences: medical devices, diagnostics, cross-border data governance.

• Finance products: standardizing disclosure, product passports, supervisory reporting interfaces.

4) Enforcement That Scales: From “Rules on Paper” to “Market Reality”

Definition

A Single Market is only as real as its enforcement layer. If enforcement is slow, fragmented, politicized, or under-resourced, then the market is functionally 27 markets.

So the principle is: enforcement must be engineered as a scalable system with:

• clear escalation paths,

• measurable performance,

• fast dispute resolution,

• and real penalties for persistent barriers.

This includes normal times and crises—IMERA is an explicit attempt to ensure the internal market keeps functioning under emergency modes rather than re-fragmenting.

What “scales” means in enforcement

“Scale” here means:

A) Speed at volume

• Thousands of cross-border frictions exist. Enforcement must handle volume like a service platform, not like bespoke litigation.

B) Predictability

• Same barrier should produce the same outcome across the Union.

C) Low transaction cost

• SMEs must be able to trigger enforcement without hiring elite legal teams.

D) Deterrence

• The expected cost of violating the Single Market must exceed the political benefit of protectionism.

E) Data-driven oversight

• You can’t manage what you don’t measure: enforcement must have KPIs and transparency.

Instruments of scalable enforcement (a concrete toolkit)

1) Fast administrative redress

• A Single Market “complaint-to-decision” mechanism with tight deadlines.

2) Injunction-style interim measures

• Ability to suspend barriers quickly while merits are assessed, preventing “win by delay.”

3) Systemic infringement acceleration

• When a Member State repeatedly blocks access, escalation must be automatic and time-bound.

4) Mutual recognition arbitration track

• Specialized dispute resolution for mutual recognition conflicts.

5) Enforcement transparency dashboard

• Public metrics per Member State:

  • average time to recognize,

  • number of barriers reported,

  • resolution time,

  • compliance rates after decisions.

Five analytical points

1. Enforcement is the economic meaning of the law

   • Without enforcement, rights become optional and the market becomes an illusion.

2. Time is the core currency

   • Market entry is time-sensitive.

   • Enforcement must be designed around business timelines, not court calendars.

3. Fragmented enforcement recreates borders

   • If each authority interprets rules differently, firms face 27 compliance realities.

4. Deterrence requires credible penalties and reputational pressure

   • If violations carry minimal consequence, protectionism persists.

5. Crisis governance must be pre-committed

   • Emergencies are where integration breaks first.

   • IMERA-like structures exist precisely because ad hoc national measures were shown to fracture the market in crises.

Practical examples: markets most affected

• Cross-border services (again the biggest beneficiary): enforcement speed determines whether the market exists.

• Food & consumer products: rapid border checks, labeling disputes, conformity claims—enforcement must stop arbitrary blockage.

• Medical and crisis-relevant supply chains: PPE, medicines, essential industrial inputs—exactly where crisis governance matters.

• Digital cross-border business: platform compliance, consumer law enforcement, cybersecurity demands—without consistent enforcement, firms geofence and retreat.

• Labour mobility & qualifications: individuals need fast recognition outcomes (weeks, not years).

5) Enforcement Pipeline With Escalation

(SOLVIT → SMET → infringement → court) as a single integrated system

Definition

A “completed” Single Market requires an enforcement stack that functions like an operating system: fast, repeatable, low-friction, and capable of escalating from individual cases to systemic correction.

In a fragmented reality, the biggest barrier is not always the law—it is how long it takes to make the law real. If enforcement is slow, delays become tariffs, and “rights” become theoretical. The enforcement pipeline solves that by ensuring that:

• small cases can be solved quickly (SOLVIT-like problem solving),

• recurring barriers become a “systemic issue” (SMET-like coordination),

• stubborn non-compliance becomes legally unavoidable (infringement/CJEU).

SMET’s own public reporting frames it explicitly as a mechanism where Commission + Member States work together to remove concrete obstacles to the Single Market and address recurring “barriers on the ground.”

SOLVIT’s quality standards (as used by national SOLVIT centres) include the expectation that once a case is accepted by the lead centre, a solution is proposed within 10 weeks—this is the key “speed advantage” versus litigation.

What this principle means operationally

A) A single “barrier lifecycle”

Any barrier should travel through a defined lifecycle:

1. Case intake (citizen/company reports barrier)

2. Fast resolution attempt (problem-solving network)

3. Classification (one-off vs systemic)

4. Systemic removal project (best practices, deadlines, one-stop shops, digitalization)

5. Escalation (formal infringement if unresolved)

6. Recurrence prevention (rule changes / administrative reforms / monitoring)

The killer is when these are disconnected: individual cases get patched, but the system never changes.

B) Systemic pattern detection

The pipeline must detect patterns:

• Same barrier appears across regions,

• Same barrier reappears every year,

• Same barrier affects multiple sectors.

That’s the difference between customer support and product engineering.

C) Administrative remedies must beat market timelines

If it takes 2 years to resolve a barrier, the market opportunity is gone.
This pipeline’s “north star” is time-to-market, not “time-to-judgment.”

D) Public accountability + measurable performance

A completed enforcement pipeline requires:

• measurable service-level targets,

• a dashboard of barrier categories,

• transparent tracking of Member State follow-through.

Otherwise, enforcement becomes political theatre.

E) Enforcement must include “prevention”

Enforcement is not only reacting to barriers. It must prevent new fragmentation:

• ex ante scrutiny of national measures likely to fragment,

• “proportionality-by-default” checks,

• early warning mechanisms before barriers harden.

Five analytical points (deep logic)

1. Without a fast enforcement layer, the Single Market becomes a rich-firm privilege

   • Large firms can litigate and lobby; SMEs cannot.

   • Speed is the equality mechanism.

2. The core economic harm is not the barrier itself; it’s uncertainty + repetition

   • Even small frictions destroy scale if they repeat 27 times.

3. A pipeline is a learning system

   • Every case teaches the system: what barriers exist, which institutions cause them, what fixes work.

4. Coordination platforms (like SMET) matter because barriers are often “administrative culture,” not formal law

   • Many obstacles persist because ministries, regions, or agencies operate with local assumptions.

   • SMET describes workstreams precisely on “administrative burdens,” “mutual recognition,” and concrete obstacles, which are often administrative rather than legislative.

5. Escalation credibility is the deterrence

   • If Member States believe no escalation will follow, barriers persist.

   • A credible threat converts “nice-to-fix” into “must-fix.”

Practical examples: markets most affected

• Cross-border services: licensing, declarations, proof-of-insurance, posting rules, local establishment demands.

• Banking / retail finance: account opening barriers and IBAN discrimination are recurring SMET topics.

• Energy permitting & infrastructure: SMET cited elimination of process barriers and promotion of one-stop shops, deadlines, tacit approval for permitting (high relevance to renewables and grids).

• Biopesticides / biosolutions: cited as a mutual recognition/authorisation acceleration target (innovation barrier).

• E-commerce / distribution: recurring barriers around product compliance, territorial supply constraints, and national enforcement differences.

6) Services Single Market Through Sectoral Deepening + Administrative Integration

(rights are not enough; procedures must become interoperable)

Definition

Services are where the EU Single Market is most incomplete because services are:

• regulated through professional requirements,

• enforced through local administrations,

• dependent on labour, tax, and consumer rules,

• delivered through “processes,” not just products.

A completed Services Single Market means:
a service provider can operate cross-border with predictable requirements, portable compliance evidence, and minimal redundant procedures, while still protecting workers, consumers, and public safety.

SMET itself identifies reduction of administrative burden for cross-border service providers and promoting best practices (information, deadlines, one-stop shop, digital procedures) as a core multi-year focus.

What this means operationally

A) Services need a “compliance packet,” not endless bespoke filings

For services, market access is mostly:

• registrations,

• declarations,

• insurance proof,

• professional credentials,

• consumer obligations,

• labour mobility rules.

A completed market creates a standard cross-border service packet that is:

• reusable,

• digitally verifiable,

• accepted across Member States unless an exception applies.

B) Administrative integration is the true frontier

The practical barrier is not “the law”—it’s the administrative graph:

• different portals,

• different document formats,

• different steps,

• different interpretations,

• different deadlines.

Completion requires:

• one-stop shops that actually process end-to-end,

• standardized workflows,

• common data schemas for filings.

C) Sectoral deepening beats one-size-fits-all

Services vary massively:

• construction services differ from telemedicine,

• logistics differs from consulting.

So the path is:

1. horizontal simplification (procedures, deadlines, digitalization),

2. sectoral “deep packages” where fragmentation is worst.

D) Worker protection must be built in

If the system makes it easier to provide services but enables abuse (bogus self-employment, letterbox firms), political support collapses.
Therefore the services market must integrate:

• labour compliance verification,

• clear posting worker rules,

• enforcement cooperation (see Principle 8).

E) Data-driven risk enforcement, not blanket restrictions

Instead of blocking cross-border services, use:

• risk classification,

• targeted audits,

• data-driven detection.

Five analytical points

1. Services fragmentation is the EU’s biggest “scale tax”

   • Most EU value creation is services-heavy; fragmentation prevents pan-EU scaling.

2. Administrative burden functions like a tariff with compounding effects

   • A 2-hour friction repeated across 10 countries becomes a strategic blocker.

3. Services need portable identity of the provider

   • For goods, the object is inspected.

   • For services, the provider is inspected: qualifications, insurance, reputation, compliance history.

4. “Rights without workflow” is the EU’s classic implementation gap

   • Treat services freedom like software: it must ship with the runtime environment (portals, credentialing, process integration).

5. The legitimacy constraint is fairness

   • If cross-border services look like “race to the bottom,” Member States reintroduce barriers.

   • So completion requires joint enforcement capacity (ELA, joint inspections, etc.).

Practical examples: markets most affected

• Construction & installation services: the single biggest sector for cross-border service friction, and a major posted-worker sector.

• Professional & technical services: engineering, scientific, administrative activities are explicitly among sectors with posting.

• Transport services: road transport posting has specific rules; high cross-border intensity.

• Health & social work services: increasingly cross-border; also among posting sectors.

• Digital services (B2B): marketing, analytics, IT services—high scalability, but blocked by administrative heterogeneity.

7) Mobility of Qualifications as a Core Single Market Infrastructure

(a labour-and-services interface, not a “nice to have”)

Definition

Qualification mobility means that human capital can move and be legally usable across the Union without re-credentialing from scratch, while safeguarding public interest and maintaining professional standards.

This principle is the “identity layer” of the services economy:

• without qualification recognition, many services cannot cross borders,

• labour mobility becomes “physical movement without economic use.”

What it means operationally

A) A “professional credential object” that is verifiable across borders

Completion requires that qualifications and professional status become:

• digitally verifiable,

• up to date (revocation/discipline visible),

• scoped (what the person is authorised to do),

• trusted (issued/verified by competent authorities).

B) Time-bounded recognition processes

Delays are the hidden barrier:

• for a professional, a 6–12 month delay is effectively a ban.
  So: deadlines + escalation must be built in.

C) Recognition logic should be risk-based, not protectionist

Where risks are high (health, safety), compensatory measures may be justified.
But they must be:

• evidence-based,

• proportionate,

• bounded (not indefinite, not reinvented in each region).

D) Prevent “regulation as rent”

Regulated professions can become cartel-like if:

• entry barriers are maintained under “quality” language,

• cross-border recognition is systematically slowed.

A complete market needs:

• transparency of requirements,

• proportionality review of restrictions,

• peer comparison across Member States.

E) Integrate with services packets + labour enforcement

Qualifications should plug into:

• services market access workflows,

• labour mobility verification,

• posting worker compliance when relevant.

Five analytical points

1. Qualification mobility is the “compute portability” of the human economy

   • If talent cannot be re-used across jurisdictions, the EU runs on underutilised capacity.

2. The main barrier is not recognition law; it’s administrative trust

   • Authorities hesitate because they lack fast, reliable verification channels.

3. Digital credentials reduce both friction and fraud

   • A verifiable credential makes recognition easier and reduces forged documents.

4. Risk-tiering avoids political deadlock

   • High-risk professions can have stronger safeguards; low-risk professions should be close to automatic mobility.

5. Without mobility, the EU loses in the global competition for talent

   • A fragmented EU becomes less attractive than integrated markets like the US for mobile professionals.

Practical examples: markets most affected

• Healthcare professions (high stakes, strong regulation): doctors, nurses, allied health.

• Construction and engineering: architects, engineers, safety inspectors.

• Skilled trades tied to safety: electricians, gas fitters, heavy equipment operators.

• Education services: teachers, specialized trainers (where regulated).

• Cross-border corporate services: compliance, auditing, legal-adjacent roles.

8) Labour Mobility With Portable Social Rights

(fairness as a market-enabling condition)

Definition

Labour mobility must be easy enough to enable the services market and fair enough to sustain political legitimacy.

This principle is the “social contract layer” of the Single Market:

• if mobility is easy but unfair → backlash and re-fragmentation,

• if mobility is fair but too complex → mobility collapses in practice.

The European Labour Authority (ELA) exists specifically to improve cooperation between Member States, coordinate joint inspections, carry out analyses on cross-border mobility issues, and mediate disputes—i.e., it is a core part of making fair mobility workable.

ELA describes posting of workers as based on freedom to provide services, and gives an estimate of ~3.6 million postings (2.6 million workers), with major sectors including construction, manufacturing, transport, warehousing, professional/scientific/admin activities, and health/social work.

What it means operationally

A) Portability as “instant verifiability” (not paper trails)

Social rights portability requires that authorities and firms can verify:

• coverage status,

• contributions,

• entitlement,

• applicable rules
  in a fast, interoperable way.

If verification is slow, enforcement fails. If enforcement fails, trust fails.

B) Anti-abuse architecture is mandatory

Common abuse patterns:

• subcontracting chains used to obscure responsibility,

• letterbox companies,

• bogus self-employment,

• underpayment / contribution evasion.

ELA explicitly points to these types of enforcement challenges (complex mobility patterns, letterbox companies, bogus self-employment) and emphasizes cross-border administrative cooperation and data-driven insights.

C) Joint inspections + operational cooperation

Fairness requires capacity, not just rules:

• joint and concerted inspections,

• information exchange,

• shared risk targeting,

• shared tooling.

ELA’s mandate includes supporting joint inspections and improving administrative cooperation.

D) Digitalization reduces both friction and evasion

Digital procedures are not bureaucracy—they’re the mechanism that makes:

• mobility scalable,

• enforcement possible,

• compliance simpler.

(You can see industry actors pushing exactly this direction via ESSPASS and digital control tools; but the key policy point is that digital portability is the structural solution, regardless of who advocates it.)

E) Protecting workers is not anti-market; it is pro-market

If workers are protected:

• competition becomes fairer,

• local labour markets don’t perceive mobility as exploitative,

• Member States are less likely to reintroduce barriers.

So fairness is an integration technology.

Five analytical points

1. Fairness is the political license for mobility

   • Without fairness, national governments face pressure to re-nationalize controls.

2. Enforcement is a coordination problem

   • Abuse often exploits jurisdictional seams; only cross-border cooperation closes them.

3. Digital portability is the only way to scale

   • Paper-based coordination cannot handle millions of postings and mobile workers.

4. Mobility requires symmetry: easy for legitimate actors, hard for abusive ones

   • The system must reduce compliance cost for normal firms while raising detection probability for fraud.

5. Labour mobility is the services market’s hidden dependency

   • If labour mobility tools fail, service providers face unpredictable constraints, and the services market stays fragmented.

Practical examples: markets most affected

• Construction (largest posting sector; complex subcontracting chains).

• Road transport / logistics (special posting rules; cross-border intensity).

• Manufacturing + maintenance (installation and servicing teams moving cross-border).

• Professional/scientific/admin services (consultancy and project-based mobility).

• Health and social work (growing cross-border staffing and service provision).

9) European Digital Identity + Paperless Administration as the Single Market’s “Seamless Layer”

Definition

A completed Single Market requires a shared trust fabric so that cross-border transactions are not blocked by identity uncertainty, manual document checks, and incompatible administrative portals.

That trust fabric has two pillars:

1. European Digital Identity Wallet / eIDAS framework: a cross-border-accepted digital identity and attribute system that users can voluntarily employ to authenticate and present verified credentials. The revised eIDAS framework explicitly creates obligations for acceptance in defined contexts (public services requiring eID/auth; many private relying parties needing strong authentication; and very large online platforms when they require user authentication).

2. Single Digital Gateway + once-only principle: cross-border administrative procedures must be online and usable for cross-border users, with a “once-only” logic (users shouldn’t have to re-submit data authorities already have), including a list of key procedures meant to be fully online.

Put simply:

• Identity answers: “who are you, and what verified attributes do you have?”

• Paperless administration answers: “can you do the procedure end-to-end online, across borders, without re-filing?”

Without these two, the Single Market remains legally open but administratively closed.

What this principle must mean operationally

A) The “cross-border user” must be a first-class citizen of government IT

A cross-border system is not “a translation of a domestic portal.”
It must support:

• authentication from another Member State,

• document/evidence presentation from another Member State,

• payment (where relevant),

• status tracking,

• redress path.

If it fails for cross-border users, it is not a Single Market procedure.

B) Identity must be more than “login”

The wallet is not just authentication. It is also:

• attributes (e.g., professional qualifications, corporate roles, licenses),

• qualified signatures and seals (legal validity across borders),

• selective disclosure (share only what’s necessary, data minimisation).

In practice, this turns many cross-border steps from “manual verification” into “cryptographically verifiable attestations.”

C) “Once-only” must be engineered as evidence exchange, not rhetoric

The once-only principle isn’t magic; it requires:

• interoperable data models,

• evidence exchange infrastructure,

• consent flows,

• clear legal bases for cross-border sharing.

The SDG framework explicitly frames once-only as avoiding repeated submission of evidence already held by authorities.

D) Acceptance obligations matter (or adoption remains patchy)

A typical EU failure pattern is “optional adoption” → patchwork → no network effect.

The revised eIDAS framework includes explicit acceptance obligations for:

• public sector online services requiring eID/auth,

• many private relying parties (except micro/small enterprises) where strong authentication is legally/contractually required in sectors listed (transport, energy, banking/financial services, social security, health, education, telecom, etc.),

• and VLOPs under the DSA definition when they require user authentication, on voluntary request of the user.

This is crucial: acceptance rules create adoption gravity.

E) Identity + procedures must connect to enforcement and market access

The “seamless layer” is not a convenience product; it is a competitiveness lever:

• reduces time-to-start-business in a new Member State,

• reduces compliance cost,

• reduces fraud,

• increases cross-border participation of SMEs.

Failure modes (what breaks in real life)

• Wallet exists but is not accepted: relying parties refuse, provide degraded experience, or demand redundant documents anyway.

• Portals exist but are not transactional: they give information but still require in-person steps or local-only credentials.

• Once-only fails: because authorities don’t share evidence; users must re-upload PDFs.

• Interoperability fragmentation: divergent national implementations break cross-border flows.

• Trust backlash: poor privacy design or insecurity reduces adoption.

Five analytical points

1. This is the Single Market’s “identity and routing layer”

   • In a digital economy, cross-border movement requires a trust mechanism analogous to passports + notaries + registries—just runnable online.

2. It reduces the SME fixed-cost barrier

   • Large firms can hire local counsel; SMEs need procedural portability or they stay domestic.

3. Acceptance obligations create network effects

   • Identity systems fail when adoption is voluntary and benefits are diffuse. Legal acceptance requirements create the necessary pull.

4. Selective disclosure is non-negotiable for legitimacy

   • Data minimisation is not just privacy virtue; it prevents identity systems from becoming surveillance triggers, which would kill adoption.

5. Paperless procedures are not “digitalisation,” they are border removal

   • If a procedure is cross-border usable end-to-end, the border is functionally reduced. If not, the border still exists.

Markets most affected (where this moves the needle hardest)

• Financial services onboarding (banks, payments, fintech): strong authentication requirements + KYC heavy processes align with the wallet’s design.

• Telecom and utilities: contracts, authentication, identity checks (listed sectors in eIDAS acceptance rules).

• Company formation + cross-border operations: director/UBO attestations, corporate certificates, signatures.

• Education + qualifications: admissions, recognition, credential verification (also listed sectors).

• Labour mobility: social security evidence, employment registrations, posted worker workflows (when integrated).

10) Data Mobility and Interoperability as a “Fifth Freedom” Infrastructure

Definition

In a modern Single Market, many borders are not customs borders—they are data borders:

• lock-in to cloud providers,

• non-portable formats,

• high switching costs,

• contractual barriers (termination penalties, opaque egress fees),

• technical barriers (no interfaces, no documentation, missing functional equivalence).

Therefore “free movement” must be complemented by data mobility: the ability to move data, configurations, and workloads across providers and across borders.

The EU Data Act explicitly includes a chapter on switching between data processing services, requiring providers to meet minimum requirements to facilitate interoperability and enable switching.

What this must mean operationally

A) Switching rights must be real, not theoretical

A switching right is real only if:

• the user can actually export data + metadata + configurations,

• in a structured and widely supported machine-readable format,

• with documentation and interfaces that make migration feasible.

The Data Act framing explicitly points to requirements that facilitate interoperability and enable switching in Chapter VI.
Practical commentary summarising Chapter VI commonly emphasises removal of contractual/technical barriers, transparent conditions, and elimination of certain switching charges over time.

B) Interoperability must target workload viability, not just data download

A fake portability regime allows you to download a pile of data but not re-run the system elsewhere.

A serious interoperability regime includes:

• export of configurations and dependencies where feasible,

• functional equivalence goals,

• documented APIs,

• migration toolchains.

C) Contract law becomes part of market design

Lock-in is often contractual:

• notice periods,

• renewal traps,

• penalties,

• restrictions on parallel running,

• unclear ownership.

So minimum contractual standards are not “private law niceties”; they are market-integrity infrastructure.

D) Cross-border data use must be compatible with rights and security

Data mobility must be compatible with:

• GDPR (for personal data),

• cybersecurity obligations,

• trade secrets.

The principle is not “data flows with no rules.”
It is “data flows are possible with clear governance,” not blocked by arbitrary localisation or lock-in.

E) Interoperability must be testable

Like standards, data portability needs:

• conformance tests,

• reference formats,

• certification or auditability.

Otherwise it becomes “portability in marketing language.”

Failure modes

• “Export exists” but is incomplete, undocumented, or unusable.

• Egress fees and migration costs make switching economically irrational.

• Providers comply on paper but degrade performance or functionality after migration.

• Fragmented national interpretations recreate borders.

• Security is used as an unlimited veto for interoperability.

Five analytical points

1. Data mobility is the modern equivalent of capital mobility

   • If you can’t move your workloads, the “market” is captive. Switching rights are competition rights.

2. Interoperability is a competition instrument, not just a technical feature

   • It prevents artificial moats created by closed ecosystems.

3. The growth prize is pan-EU scale in cloud/AI services

   • European firms will only scale if they can switch, multi-home, and combine providers across the Union.

4. This is essential for AI adoption

   • AI systems depend on data pipelines and compute platforms. Lock-in creates structural dependency and raises costs.

5. Without portability, regulation can unintentionally entrench incumbents

   • Compliance burdens plus lock-in advantage can lock the market into a few dominant stacks.

Markets most affected

• Cloud and edge computing (IaaS/PaaS/SaaS): directly impacted by switching and interoperability rules.

• AI infrastructure and model operations: data pipelines, vector databases, inference hosting.

• Industrial IoT and manufacturing platforms: co-generated data, interoperability across systems.

• Public sector digital services: avoiding vendor lock-in is strategic.

• Health data ecosystems: portability + compliance governance is critical for cross-border care and innovation.

11) Digital Market Governance That Enables EU-Wide Scale Without Fragmented “27 Enforcements”

Definition

Even if states remove barriers, digital gatekeepers and fragmented enforcement can recreate borders:

• inconsistent platform rules,

• inconsistent supervisory demands,

• inconsistent procedural expectations for the same EU regulation.

Completion requires that digital governance behaves like a Single Market:

• one compliance surface as much as possible,

• consistent enforcement logic,

• interoperability obligations where needed to prevent gatekeeper fragmentation.

Two pillars matter here:

1. DMA (Digital Markets Act): targets gatekeeper behaviors and includes obligations around interoperability in certain contexts (e.g., operating systems providing effective interoperability).

2. DSA (Digital Services Act): creates an enforcement system with national Digital Services Coordinators, a European Board for Digital Services, and exclusive Commission competence for VLOPs/VLOSEs—explicitly designed to support consistent enforcement.

What this must mean operationally

A) “One enforcement architecture” for the biggest platforms

For VLOPs/VLOSEs, the DSA assigns the Commission a central enforcement role, while DSCs handle others and cooperate via the Board.
This matters because inconsistent national enforcement would trigger platform geofencing and compliance fragmentation.

B) Coordinators must actually exist and be empowered

If Member States don’t designate/empower DSCs or set penalty regimes, enforcement gaps appear and market trust collapses. Reuters reported Commission referrals to the CJEU against several Member States for failing to implement DSA elements such as DSC designation/empowerment and penalty rules.

C) Interoperability obligations must target the right choke points

Interoperability is not “everything open.” It targets specific platform bottlenecks that prevent cross-border contestability:

• OS feature access,

• device integration,

• messaging interop (where applicable),

• app store gatekeeping behaviors.

The Commission’s DMA interoperability Q&A frames the goal as enabling effective interoperability for third-party services with the same hardware/software features available to the gatekeeper’s own services, subject to necessary integrity protections.

D) The governance goal is contestability + predictability

Digital governance must reduce:

• arbitrary delistings,

• opaque review timelines,

• inconsistent rules across EU markets.

Predictability is how smaller EU firms can invest confidently.

E) Compliance should be standardised, not bespoke

If compliance is bespoke per platform, per country, per regulator, only giants survive.
Completion means:

• standard reporting formats,

• standard audit interfaces,

• standard redress mechanisms.

Failure modes

• National fragmentation in enforcement produces inconsistent outcomes.

• “Forum shopping” by platforms to friendlier jurisdictions.

• Overly burdensome compliance surfaces that crush SMEs.

• Interoperability obligations that are too vague to be actionable (or too broad to be secure).

Five analytical points

1. Gatekeepers can create private borders

   • Even with free movement, a dominant platform can control access to markets.

2. Consistent enforcement is a competitiveness issue

   • Fragmented enforcement = higher fixed compliance costs = less innovation.

3. Interoperability is the antidote to ecosystem lock-in

   • It converts monopoly interfaces into competitive surfaces.

4. Enforcement capacity is part of sovereignty

   • If EU rules exist but are not enforced consistently, the EU imports governance from private platforms.

5. The objective is not punishment; it’s market architecture

   • The goal is a contestable environment where EU firms can scale without being blocked by closed systems.

Markets most affected

• App ecosystems and device ecosystems (smartphones, wearables, headphones, connected devices).

• Online marketplaces and e-commerce: cross-border selling depends on platform rules and enforcement.

• Digital advertising: transparency, access rules, and enforcement consistency.

• Social media and video platforms: DSA due diligence, ad transparency, researcher access (and enforcement credibility).

• Enterprise software distribution: OS interoperability and platform policies influence market access.

12) VAT / Tax-Facing Simplification as a Border-Removal Requirement (Not a Tax Policy Detail)

Definition

For a firm, a border is often not a customs barrier—it is tax complexity:

• multiple VAT registrations,

• divergent invoicing and reporting requirements,

• high compliance costs,

• slow refund processes,

• audit uncertainty.

So completing the Single Market requires a taxation-facing layer that is:

• digitally integrable,

• cross-border consistent,

• scalable for SMEs.

The EU’s VAT in the Digital Age (ViDA) package (adopted 11 March 2025) is explicitly a modernisation and digitalisation reform, rolled out progressively, including digital reporting requirements for cross-border B2B transactions and expansion of OSS schemes to reduce registration impediments.

What this must mean operationally

A) “One VAT-facing workflow” for cross-border operations

The target user experience is:

• you sell across borders,

• your accounting system outputs standardised e-invoice/reporting data,

• you file once through a harmonised scheme (OSS-like),

• obligations are predictable and automation-friendly.

ViDA’s roadmap includes digital reporting for cross-border B2B and pushes toward e-invoicing standards.

B) Digital reporting requirements must be standardised (or they become new fragmentation)

A major risk is Member States adopting incompatible real-time reporting/e-invoicing systems that force firms to build 27 integrations.

ViDA includes a long timeline culminating in alignment of domestic real-time transaction reporting systems with EU standards for Member States that have such obligations.

C) Platform economy needs coherent VAT logic

Platforms in accommodation rental and passenger transport are explicitly in scope of “deemed supplier” reforms under ViDA (phased).
That matters because the platform layer is where cross-border commerce increasingly lives.

D) Fraud control must move from paperwork to data intelligence

VAT fraud thrives in cross-border complexity. The solution is:

• better data,

• faster reporting,

• interoperable analytics,
  not endless paperwork that punishes compliant firms.

E) Integrations must be easy for SMEs

If compliance requires big ERP projects, SMEs will self-restrict to domestic markets.
So completion requires:

• standard APIs,

• standard data schemas,

• clear guidance and test environments.

Failure modes

• Member States create incompatible e-invoicing requirements.

• Reporting becomes “high frequency bureaucracy” rather than automation.

• Small firms face compliance cliffs, not gradual scaling.

• Platforms restructure to arbitrage tax complexity.

Five analytical points

1. VAT complexity is a hidden tariff

   • It raises per-market fixed costs and kills the SME expansion path.

2. Digital reporting can either integrate markets or fragment them further

   • Standardisation is the key: digitalisation without harmonisation can worsen fragmentation.

3. Tax simplification increases competition

   • Lower compliance fixed costs allow more entrants, not just incumbents with legal teams.

4. Platforms are now fiscal chokepoints

   • Treating platforms coherently is necessary because they mediate cross-border supply at scale.

5. A modern Single Market needs “compliance as software”

   • Tax compliance should be integrable into systems, not manual processes repeated across borders.

Markets most affected

• E-commerce and cross-border retail (especially SMEs selling across multiple Member States).

• Digital services and subscriptions (B2C and B2B cross-border).

• Platform-mediated services: short-term rentals and passenger transport (explicit ViDA focus).

• Logistics and supply-chain heavy firms: intra-EU movement creates VAT reporting burdens.

• Fintech and invoicing software ecosystem: standardised e-invoicing/reporting creates a huge interoperability market.

13) Payments Single Market

Instant, interoperable, secure-by-default payments as core market utility

Definition

A completed Single Market requires that moving money across borders is as seamless as moving information: instant, low-friction, predictable, and safe. Payments are not “a financial sector feature”—they are core market infrastructure. When payments are slow, expensive, unreliable, or fragmented, every cross-border activity becomes harder: trade, e-commerce, subscriptions, labour mobility, and SME scaling.

The EU’s Instant Payments Regulation (Regulation 2024/886) is essentially an integration instrument: it pushes ubiquitous instant euro credit transfers, applies price parity (instant not more expensive than standard), and introduces strong safety logic like Verification of Payee (IBAN-name matching) and streamlined sanctions checks.

What this principle must mean operationally

A payments single market is not achieved by “allowing instant payments to exist.” It is achieved when instant payments are a universal default capability, with consistent safety controls and broad access.

A) Ubiquity: “receive” and “send” must both be universal

A market is “instant” only if recipients can reliably receive and send anywhere. The EU regulation staggers deadlines, with euro area PSPs required to be able to receive instant payments earlier and send later (e.g., receiving by January 2025; sending by October 2025 in the euro area per ECB summary).

Design implication: you don’t have a single market if large parts of the network can’t receive or send.

B) Price parity removes a major adoption killer

If instant payments cost more, many firms will keep using legacy transfers. The regulation requires charges for instant transfers not to be higher than charges for standard credit transfers.
Design implication: adoption must be driven by default economics, not only by “better UX.”

C) Fraud resistance must be engineered into the default (VoP)

Instant payments increase “speed of irreversibility.” That makes fraud risk politically and commercially existential. That’s why the regulation introduces Verification of Payee and requires PSPs to offer it (and do so free for the payer per ECB summary).

VoP is not a feature; it is a trust primitive: it reduces misdirected payments and scams by warning the payer of mismatches before the payment is initiated.

D) Sanctions screening must be compatible with instant speed

The regulation includes a “simplified” approach where PSPs check lists at least daily rather than per transaction (as summarized by the ECB) so compliance does not break speed.
Design implication: if legal controls aren’t redesigned to match instant systems, the market reverts to slow rails.

E) Broad participation requires access to payment systems for more actors

The Council summary highlights that the regulation changes the settlement finality framework to grant access to payment systems for payment institutions and e-money institutions, with safeguards.
Design implication: a single market is about who can compete—not just what banks can do.

Failure modes (how payments still fragment even with rules)

• Partial ubiquity: many can receive but not send, or only in certain banks/countries.

• Degraded experience: “instant” is offered but with tight limits, downtime, slow exception handling.

• Security backlash: fraud spikes produce public pressure to reintroduce friction or restrictions.

• Inconsistent VoP implementation: if results and user flows differ wildly, trust and usability suffer.

• Non-euro fragmentation: different timelines can create a two-speed payments market.

Five analytical points

1. Payments are the “circulatory system” of the Single Market

   • If money doesn’t move seamlessly, trade and services do not scale seamlessly.

2. Ubiquity + price parity are adoption design

   • Capability without adoption is symbolic; parity makes adoption rational by default.

3. Trust primitives (VoP) turn speed into safety

   • Instant speed without verification is politically unstable; VoP is what allows instant to become the default.

4. Regulation here is effectively “protocol governance”

   • The EU is defining the baseline characteristics of a payment protocol: speed, cost constraints, verification, compliance logic.

5. Payments completion unlocks second-order integration

   • Once payments are instant and standardised, other layers (e-commerce, payroll, subscriptions, platform economy) become simpler and more EU-wide.

Markets most affected

• E-commerce, marketplaces, cross-border retail (refunds, payouts, settlement).

• SME B2B trade (invoice settlement, cash flow).

• Platform economy (payouts to hosts/drivers/creators).

• Labour mobility (salary payments, cross-border living).

• Fintech and payment institutions (competition and scaling as access broadens).

14) Banking Union Completion

Remove ring-fencing, stabilize trust, enable cross-border banking scale

Definition

A completed Single Market in finance requires banks to operate under a credible, integrated safety and resolution architecture, so that cross-border banking is not structurally punished by national “ring-fencing” and inconsistent crisis handling.

In practice, “banking fragmentation” shows up as:

• capital and liquidity trapped nationally,

• supervisors reluctant to trust cross-border group support,

• national crisis politics dominating resolution choices.

The Council’s 2025 political agreement on reforming the crisis management and deposit insurance (CMDI) framework is explicitly described as “another step towards completion of the EU’s banking union,” strengthening resolution processes (especially for small/medium banks) and improving access to industry-funded safety nets in resolution.

What this principle must mean operationally

A) A resolution regime that works for mid-sized banks

Historically, resolution frameworks tend to be credible only for the biggest institutions; others are handled via national insolvency-like approaches. The CMDI reforms aim to improve resolution tools for smaller/medium banks and access to industry-funded safety nets.

Design implication: if mid-sized banks aren’t resolvable in a consistent way, trust remains national and fragmentation persists.

B) Predictable use of safety nets and least-cost logic

Bank runs and failures are partly about expectations: what will happen to depositors? will there be chaos? who pays? A credible union reduces uncertainty and prevents panic-driven national fragmentation.

C) Reduce national ring-fencing incentives

Ring-fencing is often a rational national response: “protect local depositors.”
A union has to create enough shared stability to make ring-fencing less necessary—otherwise cross-border banks can’t behave as integrated groups.

D) Integrate supervision, resolution, and deposit protection logic

Fragmentation often arises when:

• supervision is EU-aligned,

• but resolution/deposit realities remain national,

• so supervisors and finance ministries act defensively.

Completion requires coherence across these layers.

E) Crisis playbooks must be pre-committed

In real crises, political dynamics quickly override ideal rules. The union needs credible, rehearsed “playbooks” that reduce ad hoc national divergence.

Failure modes

• Two-tier credibility: only big banks are handled well; others trigger national improvisation.

• Persistent ring-fencing: capital/liquidity remains trapped, undermining cross-border integration.

• Legitimacy gap: taxpayers fear backstopping foreign banks; politics blocks further integration.

• Slow interventions: lack of shared operational capacity creates delays.

• Moral hazard fears: integration stalls because of “who pays” disputes.

Five analytical points

1. Banking union is fundamentally a trust architecture

   • The entire point is to replace national distrust with credible shared stability mechanisms.

2. Fragmentation raises the cost of capital in the real economy

   • If banking is fragmented, financing conditions differ more across Member States, hurting cohesion and competitiveness.

3. Ring-fencing is the symptom, not the disease

   • The disease is insufficient shared crisis credibility; fix that and ring-fencing pressure drops.

4. “Completion” is about making cross-border banking economically rational

   • If cross-border banks cannot deploy capital/liquidity efficiently, Europe remains financially under-scaled.

5. CMDI reform is a concrete step, but completion is structural

   • CMDI helps resolution credibility; deeper integration depends on sustained political and institutional alignment.

Markets most affected

• Cross-border SME lending and trade finance.

• Retail banking access for mobile EU citizens.

• Banking competition and consolidation (ability to scale EU-wide).

• Crisis resilience across EU economies.

• Fintech dependence on banking rails (stable partner banks).

15) Capital Markets Integration

“Savings & Investment Union” logic: remove supervisory fragmentation, enable pan-EU scale

Definition

A completed Single Market for capital means:

• savings can flow EU-wide into productive investment,

• issuers can raise money EU-wide,

• intermediaries can operate EU-wide,

• supervision is sufficiently harmonised that firms don’t face 27 different “compliance realities.”

This is the logic behind renewed pushes for deeper capital market integration and more harmonised supervision. ESMA explicitly welcomed a Commission legislative proposal on market integration and supervision (Dec 2025), highlighting fragmentation from divergent national rules and supervisory practices and the aim to enable more harmonised supervision and smoother operation across the Single Market.

There is also visible political and institutional debate about centralising selected supervisory powers at EU level. Reuters has reported resistance among some Member States to expanding ESMA powers, even while there is broad support for deepening capital markets.
And Reuters (Feb 2026) reported ECB economists arguing that ESMA should oversee the biggest asset managers to reduce “blind spots” arising from nationally fragmented supervision.

What this principle must mean operationally

A) Reduce “supervisory borders” that segment capital markets

In capital markets, the border is often: “which supervisor has jurisdiction, and what do they require?”
Completion requires:

• standardised supervisory expectations,

• consistent enforcement,

• targeted centralisation where cross-border activity is high.

B) Build a scalable “passport” for financial firms that is real in practice

Passporting exists, but national supervisory practices still diverge. The goal is: if you’re authorised and supervised under a harmonised EU approach, you can scale without reinventing processes per country.

C) Deepen trading and post-trading integration

Fragmentation in trading, clearing, settlement, and market data creates inefficiencies and reduces liquidity. ESMA’s press release frames the Commission package as addressing barriers across trading, post-trading, and asset management.

D) Protect investors while reducing compliance duplication

Investor protection isn’t in tension with integration—poor protection reduces participation and liquidity. But protection should be consistent and digitally integrable, not 27 separate compliance builds.

E) Target the scale-up financing gap

A key “completion” objective is to prevent European growth companies from needing to list or raise capital outside Europe due to shallow markets—a theme repeatedly raised in policy debates and media coverage around capital market integration.

Failure modes

• Member State resistance to centralisation → incrementalism stalls.

• Fragmented supervision persists → firms choose one “home” but can’t truly scale.

• Liquidity fragmentation → higher cost of capital, lower valuations.

• Regulatory arbitrage (“race to the bottom”) if supervision differs.

• Over-complex rules reduce retail participation, undermining depth.

Five analytical points

1. Capital market depth is a competitiveness lever

   • If the EU can’t mobilise savings into innovation, it loses tech and scale-ups to deeper markets.

2. Supervision is the real integration bottleneck

   • Harmonised rules without harmonised supervision still produce fragmentation in practice.

3. Selective centralisation is the plausible path

   • Full centralisation faces political resistance; targeted EU-level oversight for highly cross-border activities may be feasible.

4. Post-trade integration matters as much as issuance

   • Without efficient clearing/settlement, liquidity stays shallow and fragmented.

5. Integration must preserve legitimacy

   • If citizens see capital markets as unsafe or unfair, participation remains low and the depth never arrives.

Markets most affected

• Equity markets and listings (scale-up financing).

• Venture capital and growth equity (cross-border funds, exits).

• Asset management (especially large cross-border managers; focus of ECB argument).

• Market infrastructure (clearing, settlement, market data).

• Crypto/Fintech (where inconsistent national supervision creates uneven playing fields).

16) Corporate Mobility + Optional “28th Regime”

Remove the legal scale penalty for firms operating EU-wide

Definition

Even with free movement of goods/services/capital, Europe still imposes a “legal scale penalty” because company law and corporate procedures are deeply national:

• incorporation rules differ,

• conversion/merger processes differ,

• registers differ,

• filing and disclosure differ,

• employee participation rules interface differently.

A completed Single Market needs:

1. high-functioning corporate mobility (conversion, cross-border mergers, divisions), and

2. an optional, well-designed EU-wide corporate regime (often called a “28th regime”) that allows firms to operate under one coherent corporate law option EU-wide—while preserving high standards to avoid “race to the bottom.”

What this must mean operationally

A) Corporate mobility must be fast, predictable, and digital

“Freedom of establishment” is operational only if:

• cross-border conversions/mergers/divisions are routine,

• procedures are digital and time-bounded,

• corporate registers interoperate,

• and there’s clear recognition of corporate identity across borders.

If corporate mobility is slow or legally risky, firms avoid it and the market stays fragmented.

B) Interoperable business registries are essential

Registers are where corporate reality lives:

• who owns the company,

• who can sign,

• what filings exist,

• what status the company has.

Completion requires:

• interoperable identity of legal entities,

• verifiable credentials for directors/signatories,

• cross-border evidence exchange (ties directly to Principle 9).

C) The “28th regime” must be optional and high-standard

A 28th regime works politically because it doesn’t force uniformity on Member States. It lets firms opt in for scale benefits.

But it must be high-integrity:

• strong creditor protection,

• clear worker-information safeguards,

• anti-abuse design,

• transparency requirements.

Otherwise, it becomes a “Delaware-style forum shopping” flashpoint that triggers backlash.

D) Worker participation interface must be explicit

Corporate mobility intersects with worker rights (information, consultation, participation in some models). If the framework doesn’t handle this explicitly, it becomes politically toxic and legally contested.

E) Insolvency / restructuring compatibility becomes a scale condition

Investors discount uncertainty. If insolvency outcomes differ radically, cross-border scaling and financing become riskier. Corporate mobility and capital market integration therefore depend on a minimum convergence of insolvency/restructuring expectations (even if not complete uniformity).

Failure modes

• Legal uncertainty: firms fear that restructuring across borders triggers unknown liabilities or litigation.

• Administrative fragmentation: register interoperability is poor, filings are not trusted, evidence is duplicated.

• Political backlash: 28th regime perceived as regulatory arbitrage.

• SME exclusion: if mobility is too costly/complex, only large firms benefit.

• Patchwork implementation: Member States implement mobility rules differently, reintroducing fragmentation.

Five analytical points

1. Corporate form is the container for scale

   • Europe can’t have EU-scale firms if firm containers are nationally bounded and costly to move.

2. Mobility is the “firm-level” equivalent of mutual recognition

   • Like mutual recognition allows products/services to travel, corporate mobility allows organizations to travel and reorganize without being reborn 27 times.

3. Optionality is the political strategy

   • A 28th regime can bypass unanimity deadlocks by offering a voluntary high-standard path.

4. Interoperability beats uniformity

   • The practical win is not identical company law everywhere; it is interoperable evidence, predictable procedures, and portable corporate identity.

5. This principle is upstream of innovation competitiveness

   • If Europe wants firms to scale without relocating headquarters or listing elsewhere, corporate mobility and predictable EU-wide corporate structures matter as much as venture funding.

Markets most affected

• Tech scale-ups expanding EU-wide (high sensitivity to setup friction).

• Cross-border platforms needing consistent entity structure and contracting.

• Manufacturing groups optimizing supply chains and corporate structures across borders.

• Financial services groups operating under multiple licenses/entities.

• Venture capital / private equity (deal structuring, exits, cross-border reorganizations).