Artifact GuideEU

EU GDPR Lead Authority and One-Stop-Shop

This guide helps decide whether GDPR one-stop-shop routing is available, which establishment anchors the lead supervisory authority, and what evidence should support that position.

Focused on main establishment, cross-border processing, Article 56 competence, Article 60 cooperation, and evidence records that avoid unsupported national-procedure assumptions.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

Use the GDPR only for cross-border processing carried out by a controller or processor with a qualifying main establishment or single establishment in the Union. The organisation cannot choose its regulator. It must identify the processing-specific decision-making establishment, document why Article 56 points to that supervisory authority, identify the other supervisory authorities concerned, and prepare for the Article 60 cooperation procedure.

Section 1

When GDPR one-stop-shop routing is available

Start with the processing activity, not the corporate group. GDPR Article 4(23) treats processing as cross-border when it is carried out in the context of establishments in more than one Member State, or when processing in one Member State substantially affects or is likely to substantially affect data subjects in more than one Member State.

Article 56 connects that cross-border processing to the supervisory authority of the controller's or processor's main establishment or single establishment. A company subject to the GDPR only because Article 3(2) applies, but with no establishment in the Union, cannot use an Article 27 representative to create a main establishment and does not receive routing.

Article 55(2) is another limit: Article 56 does not apply when public authorities process personal data or when private bodies process it on the basis of Article 6(1)(c) or (e). The supervisory authority of the Member State concerned is competent for that processing.

  • Identify the specific processing operation, product, data flow, or incident before naming a lead authority.
  • Record each Union establishment involved in deciding or carrying out the processing.
  • Separate cross-border processing evidence from unrelated multinational presence.
  • List Member States where data subjects are substantially affected or likely to be substantially affected.
  • Stop the analysis if there is no qualifying Union establishment or Article 55(2) applies; then identify the competent national authority or authorities for the actual processing.
Section 2

How to evidence the main establishment

For a controller with establishments in more than one Member State, GDPR Article 4(16) points first to the place of central administration in the Union. That changes if decisions on the purposes and means of the processing are taken in another Union establishment and that establishment has power to implement those decisions.

The central-administration presumption depends on that establishment making the decisions on the purposes and means of the processing and having power to implement them. If those decisions are taken outside the Union and no Union establishment takes and can implement them, the controller has no main establishment in the Union for that processing. Formal designation, headquarters paperwork, or a convenient contact point does not supply the missing decision-making facts.

For a processor with establishments in more than one Member State, the main establishment is its central administration in the Union. If there is no central administration in the Union, Article 4(16) points to the Union establishment where the processor's main processing activities take place, to the extent the processor is subject to specific GDPR obligations. A controller and its processor must each assess their own role and establishment facts.

  • Keep signed governance records, decision minutes, reporting lines, role descriptions, and approvals showing where purposes and means are decided for this processing activity.
  • Keep implementation evidence showing that the same establishment can direct and secure implementation across the relevant Union establishments.
  • For processors, document the Union central administration or the Union establishment carrying out the main processing activities.
  • Do not treat a sales office, representative, group headquarters, or local contact point as the main establishment unless the Article 4(16) facts support it.
  • Reassess the position when decision rights, reporting lines, establishments, processing purposes, or implementation power change.
Section 3

Article 56 lead authority mechanics

Article 56(1) makes the supervisory authority of the main establishment or single establishment competent to act as lead supervisory authority for cross-border processing, using the Article 60 cooperation procedure.

Article 56 also preserves local competence for complaints or possible infringements that relate only to an establishment in one Member State or substantially affect data subjects only in that Member State. In those cases, the local supervisory authority informs the lead authority, and the lead authority has three weeks to decide whether it will handle the case under Article 60. A lead authority is therefore not exclusive for every GDPR issue involving the organisation.

  • Record the proposed lead supervisory authority and the Article 4(16) facts supporting it.
  • Identify supervisory authorities concerned because a controller or processor is established in their Member State, data subjects there are substantially affected or likely to be substantially affected, or a complaint was lodged there.
  • When Article 56(2) may apply, preserve the local-establishment or local-effect facts separately from the lead-authority analysis.
  • If the lead supervisory authority handles an Article 56(2) matter, Article 60 applies; if it declines, the local supervisory authority handles that matter under Articles 61 and 62.
  • Treat the proposed authority as a reasoned position, not a self-certified outcome; supervisory authorities can examine and dispute the establishment facts.
Section 4

What Article 60 means for one-stop-shop evidence

Article 60 is a cooperation procedure between the lead supervisory authority and the other supervisory authorities concerned. The lead authority must exchange relevant information, submit draft decisions for opinion, and take the views of concerned authorities into account.

A concerned authority has four weeks to make a relevant and reasoned objection to the first draft decision and two weeks for a revised draft. If the lead authority does not follow an objection it considers relevant and reasoned, the matter goes to the consistency mechanism. Those periods are authority-to-authority steps, not a promised deadline for resolving the whole case.

The record should anticipate more than one authority's involvement. Preserve the facts, establishments, affected Member States, complaint locations, processing descriptions, and compliance measures needed for the draft-decision process and implementation across Union establishments.

  • Maintain a single processing fact record that can be shared consistently across concerned authorities.
  • Track which establishments and Member States the decision would cover.
  • Record remedial measures in a form that can be implemented across all relevant Union establishments.
  • Track draft decisions, concerned-authority views, objections, revisions, final notices, and measures taken to comply.
  • Do not promise a fixed Article 60 case timeline; the GDPR specifies objection periods but no single end-to-end duration.
Section 5

One-stop-shop evidence checklist

Use this checklist when opening a new market, changing a processing model, responding to a complaint, or preparing a breach route for cross-border processing. It records an auditable lead-authority position without adding unsupported national-procedure claims.

If a fact is uncertain, mark it as unresolved instead of selecting a convenient authority. Name the missing governance, establishment, affected-data-subject, public-authority, lawful-basis, or complaint-location evidence and assign an owner to obtain it.

Does having customers in several EU Member States automatically create a GDPR lead supervisory authority?

No. Customer location alone does not identify a lead authority. The processing must meet Article 4(23)'s cross-border test, and Article 56 must attach that processing to a qualifying main establishment or single establishment in the Union.

Can the company choose the most convenient supervisory authority?

No. The lead supervisory authority follows the GDPR facts: the main establishment or single establishment for the relevant cross-border processing, subject to Article 56 mechanics.

What should be saved as evidence?

Save the processing description, controller or processor role, Union establishment map, decision and implementation records, Article 4(16) main-establishment analysis, Article 4(23) cross-border-processing analysis, Article 55(2) exclusion check, concerned-authority list, complaint locations, and Article 60 cooperation records.

Does an EU representative give a non-EU controller access to the ?

No. An Article 27 representative is distinct from an establishment and does not create a main establishment. If a controller has no establishment in the Union, it cannot obtain routing through its representative, even when Article 3(2) makes the GDPR applicable.

  • Processing operation is described with controller or processor role, establishments involved, and affected data-subject Member States.
  • Cross-border processing analysis is tied to Article 4(23), not only to customer geography or group structure.
  • Main establishment analysis is tied to Article 4(16) facts about central administration, purpose-and-means decisions, implementation power, or processor main processing activities.
  • Exclusion check confirms that a qualifying Union establishment exists and that Article 55(2) does not remove the processing from Article 56.
  • Lead supervisory authority, concerned supervisory authorities, and any Article 56(2) local-case facts are recorded separately.
  • Article 60 evidence pack includes facts, measures, decision owners, affected establishments, and implementation records for all relevant Union establishments.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • GDPR Articles 4(16), 4(23), 55, 56, and 60 support the checklist fields for one-stop-shop evidence.
"sole interlocutor of the controller or processor"
Related guides

Explore more topics

Does the EU GDPR apply outside the EU under Article 3?
A GDPR Article 3 territorial-scope FAQ covering EU establishment, non-EU targeting, monitoring in the EU, public-international-law cases, and Article 27 representatives.
EU GDPR Applicability Test for Products, Vendors, and Data Flows
A concrete GDPR scope test for personal data, controller and processor roles, EU establishment, EU targeting or monitoring, special-category and child data, transfers, vendors, and evidence.
EU GDPR Article 30 RoPA Intake Workflow
This GDPR Article 30 RoPA intake workflow helps capture controller and processor fields, owners, transfers, retention, security measures, and evidence before a processing activity goes live.
EU GDPR Article 6 Legal Bases FAQ
FAQ on the six Article 6 GDPR lawful bases, consent caveats, legitimate interests, public-task and legal-obligation limits, and Article 9 special-category data.
EU GDPR Automated Decision-Making and Profiling: Article 22 Scope, Safeguards, and Evidence
GDPR guide to profiling and Article 22 decisions: scope, transparency, lawful basis, DPIA triggers, safeguards, human intervention, challenge rights, and evidence.
EU GDPR Breach Notification 72 Hours: Article 33 and 34 workflow
Official source EU GDPR breach notification workflow covering awareness, 72-hour supervisory authority notices, processor escalation, high-risk data-subject communication, delay reasons, and evidence logs.
EU GDPR Breach Notification Workflow: 72-hour clock, risk assessment, and records
A concrete EU GDPR breach notification workflow for detecting and triaging incidents, starting the awareness clock, assessing risk, notifying authorities or data subjects, and keeping Article 33 records.
EU GDPR Checklist: scope, lawful basis, DSARs, DPIA, RoPA, transfers
This GDPR checklist helps review scope, lawful basis, notices, DSAR handling, DPIAs, RoPA, processor contracts, SCC transfers, breach notification, retention, security, and evidence.
EU GDPR Children and Special-Category Data Guide
GDPR guide to children's consent and special-category data: Article 8 national age variation, Article 9 conditions, transparency, DPIA triggers, safeguards, and evidence.
EU GDPR Compliance Checklist: scope, rights, DPIA, RoPA, transfers
Practical EU GDPR compliance guide for mapping scope, lawful basis, notices, data-subject rights, DPIAs, RoPA, processor terms, breaches, transfers, retention, security, and penalties.
EU GDPR Controller, Processor, and Joint Controller Roles
Classify GDPR controllers, processors, and joint controllers from actual decision-making, then document Article 26 allocation, Article 28 terms, instructions, and vendor evidence.
EU GDPR Data Subject Rights and DSAR Workflow
GDPR rights-request workflow for intake, identity checks, request scope, the one-month response clock, extensions, refusals, processor coordination, and evidence.
EU GDPR deadlines and compliance calendar
EU GDPR calendar for calculating rights-request deadlines, breach notification, DPIA and prior-consultation gates, transfer reviews, and retention checks.
EU GDPR DPIA and Prior Consultation Workflow
Screen high-risk processing, run a GDPR Article 35 DPIA, record mitigation, and identify when Article 36 prior consultation is required.
EU GDPR DPIA and risk management under Articles 35 and 36
EU GDPR DPIA guide covering Article 35 triggers and contents, CNIL and DPC PIA methods, residual risk, mitigation records, and prior consultation limits.
EU GDPR DSAR Exceptions: refusal, extensions, identity checks
FAQ on when EU GDPR controllers may extend, charge for, narrow, redact, or refuse a data subject access request under Articles 12 and 15.
EU GDPR DSAR Workflow: Intake, Clock, Rights, and Evidence
Run a GDPR DSAR workflow for intake, identity checks, rights scoping, one-month response timing, extensions, refusals, processor handoffs, and evidence records.
EU GDPR FAQ: scope, lawful basis, rights, DPIA, breaches, transfers
Direct EU GDPR FAQ answers on scope, controller and processor roles, lawful basis, data subject rights, DPIAs, breach notification, international transfers, and Article 83 fine tiers.
EU GDPR International Transfers and SCCs: Chapter V evidence guide
GDPR Chapter V guide to adequacy decisions, SCCs, transfer assessments, supplementary measures, Article 49 derogations, and EU-US DPF checks.
EU GDPR Lawful Basis and Consent Guide
Focused GDPR guide to Article 6 lawful bases, consent conditions, legitimate interests, special category data, withdrawal, and evidence records.
EU GDPR Lawful Basis and LIA Workflow for Article 6(1)(f)
Assess GDPR legitimate interests with a purpose, necessity, balancing, Article 21 objection, and evidence-record workflow based on Article 6(1)(f).
EU GDPR LIA Template for Article 6(1)(f)
This EU GDPR legitimate interests assessment template helps document Article 6(1)(f) purpose, necessity, balancing, safeguards, objection rights, and evidence.
EU GDPR penalties and fines: Article 83 tiers and evidence
EU GDPR penalties guide covering Article 83 fine ceilings, the EDPB calculation method, CJEU conditions, Article 58 powers, and evidence.
EU GDPR Processor Contracts and Vendor Management | Article 28 Evidence Guide
EU GDPR Article 28 guide for processor contracts, sub-processor controls, controller-processor role boundaries, vendor evidence, and SCC transfer clauses where applicable.
EU GDPR Record of Processing Activities Template: Article 30 RoPA Fields
Build a GDPR Article 30 record of processing activities with separate controller and processor fields for purposes, data categories, recipients, transfers, erasure time limits, and security measures.
EU GDPR Requirements: scope, rights, security, DPIA, RoPA, and transfers
Overview of core EU GDPR requirements covering scope, principles, lawful basis, notices, data-subject rights, processors, RoPA, security, breaches, DPIAs, and international transfers.
EU GDPR Retention and Erasure Schedule
Build an EU GDPR retention and erasure schedule with purpose-based periods, expiry actions, Article 17 decisions, recipient notices, and deletion evidence.
EU GDPR SCC Transfer Impact Assessment FAQ
FAQ on when SCC transfer impact assessments are needed, what Clause 14 records, and when supplementary safeguards or transfer suspension are required.
EU GDPR Transfer TIA and SCC Workflow
A GDPR workflow for checking adequacy, selecting SCC modules, documenting transfer impact assessments, and recording supplementary measures for third-country transfers.
EU GDPR Transparency Notices: Articles 12, 13 and 14
GDPR privacy-notice guide for Articles 12, 13, and 14: direct collection, other data sources, purposes, lawful bases, recipients, transfers, retention, rights, and timing.
EU GDPR vs Brazil LGPD: scope, legal bases, rights, incidents, and transfers
Compare EU GDPR and Brazil LGPD scope, actors, legal bases, rights timing, security incidents, international transfers, evidence, regulators, and penalties.
EU GDPR vs California CCPA: scope, rights, opt-outs, and evidence
Compare EU GDPR and California CCPA scope, roles, consumer rights, response times, sale and sharing opt-outs, risk assessments, contracts, transfers, and enforcement.
EU GDPR vs ePrivacy Directive: personal data, cookies, consent, and communications
Compare the EU GDPR and ePrivacy Directive for personal data processing, consent and lawful basis, cookies and terminal access, electronic communications, and parallel compliance.
EU GDPR vs UK GDPR: Scope, Rights, Transfers, and Evidence
Compare the EU GDPR and amended UK GDPR across scope, rights, automated decisions, accountability, breaches, regulators, and international transfers.
GDPR processor vs controller: role boundaries and evidence
Decide whether a party is a GDPR controller, processor, or joint controller using purpose-and-means tests, Article 28 terms, Article 26 arrangements, and Article 30 records.
GDPR vs EU AI Act: privacy controls for AI systems
Map the GDPR work that remains necessary when an AI system processes personal data, including lawful basis, notices, DPIAs, Article 22, rights, security, records, and transfers.
GDPR vs EU Data Act: personal data, connected products, and access rights
Compare GDPR privacy duties with EU Data Act rights and duties for connected-product data, third-party access, data holders, users, contracts, cloud switching, and enforcement.
When does the EU GDPR require a DPIA?
Answer the EU GDPR DPIA threshold question with Article 35 triggers, high-risk criteria, supervisory-authority list checks, and DPIA content requirements.
When does the GDPR 72-hour breach notification clock start?
GDPR breach-awareness FAQ covering the Article 33 clock, processor escalation, delayed or phased notifications, risk assessment, and records to keep.