Branch, Passporting & Cross-Border Launch

The problem this solves

Cross-border expansion is planned as though every authorisation travels, every branch is available on request and a third-country firm can reach EU customers through a European affiliate. Those are separate routes with separate conditions, and treating them as one produces a plan the host authority does not recognise.

Who it is for

• EU or EEA authorised firms extending into further Member States.
• Groups deciding between serving a market cross-border and establishing a local presence.
• Third-country firms testing what is genuinely available to them and what would require an authorisation of their own.
• Firms that already hold permissions but need a local operating capability rather than a paper presence.

When this is not the right service

Each of these points to the engagement that fits better, so you are one click away from it.

• The group holds no EU authorisation and the question is which authorisation to seek and where. EU Licence & Jurisdiction Decision Sprint
• The group holds no EU authorisation and has decided to apply for one. End-to-End Authorisation Programme
• A cross-border notification or branch application has already been challenged by a host authority and needs recovery. Application Remediation & Programme Rescue
• You want a confirmation that a particular activity travels on your existing permissions. That is a legal question and belongs with qualified counsel; RenIQ analyses the route and the operating consequences.

What RenIQ needs from you

The engagement cannot start without these. They are listed so you can assess the effort before you commit.

• The existing authorisation, the permissions it actually carries and the entity that holds it.
• The activities intended in each target market, and the customers they would be provided to.
• How the service would be provided in practice: locally present staff, remote provision, intermediaries or digital channels.
• Any existing notification, branch or local registration already in place.
• Group structure, including where the third-country entities sit and what they would do.
• Commercial timing and any local commitments already made.

What RenIQ does

• Analysing the existing authorisation: what it permits, for which entity, and where the edges of those permissions are.
• Working through home state and host state considerations separately, because they are separate relationships with separate expectations.
• Setting out the notification route where the firm and the activity are within its scope, including what the home authority and the host authority each do.
• Setting out branch establishment as a distinct route, with the local governance, staffing and reporting it brings with it.
• Identifying third-country constraints where part of the group sits outside the EU, and where those constraints make a route unavailable rather than harder.
• Mapping local operating requirements: local reporting, language, complaint handling, local representation and market-specific conduct expectations.
• Building the governance and launch dependency plan so the permission and the operating capability arrive together.

What you get

• Existing-authorisation analysis: what the current permissions carry, held by which entity, and what they do not carry.
• Home state and host state considerations, documented separately with the expectations of each.
• Route analysis for the notification route, where it is available to this firm for these activities.
• Route analysis for branch establishment, with its governance, substance and local obligations.
• Third-country constraint analysis, where any part of the intended structure sits outside the EU.
• Local operating requirements per target market, in the form of things the business has to be able to do.
• Governance and launch dependency plan, sequencing permissions, people, reporting and systems.

Who is responsible for what

Stated before the engagement starts, so there is no assumption left to discover halfway through.

Where qualified counsel comes in

How the work is run

Each route is documented on the same template so they can be compared rather than blended, and the launch dependencies are tracked in one plan covering permissions, people, reporting and systems together.

Every engagement runs through the same structured digital delivery method: one agreed plan, one decision log, one evidence register and one set of owned workstreams, maintained by RenIQ and handed over as documents. Digital tools support research, tracking and consistency. They do not replace professional judgement and are not offered to clients as a software platform.

Indicative sequence

Indicative only. The actual sequence is agreed per engagement, and no duration is committed here.

1. 1

   Permissions baseline

   Establish what the existing authorisation actually carries, for which entity, and where its edges are.

2. 2

   Route separation

   Set out notification, branch establishment and any third-country position as distinct routes with distinct conditions.

3. 3

   Host requirements

   Work through what each target market expects of an incoming firm, operationally as well as formally.

4. 4

   Route decision

   Take the comparison to your management, with the legal questions marked for counsel.

5. 5

   Launch dependencies

   Sequence permissions, governance, local reporting and systems so the market entry is operational rather than nominal.

Your next step

Tell RenIQ which entity holds the authorisation, which markets you are targeting and how you intend to serve them. RenIQ will come back on which routes are worth analysing and what the analysis would need.