Make your website GDPR compliant today — Cookiebot automates cookie consent, scanning, and compliance so you don't have to.
Try Cookiebot Free
Article 47
Binding corporate rules
Chapter 5|International Transfers|📖 7 min read
1. The competent supervisory authority shall approve binding corporate rules in accordance with the consistency mechanism set out in Article 63, provided that they:
(a) are legally binding and apply to and are enforced by every member concerned of the group of undertakings, or group of enterprises engaged in a joint economic activity, including their employees;
(b) expressly confer enforceable rights on data subjects with regard to the processing of their personal data; and
(c) fulfil the requirements laid down in paragraph 2.
2. The binding corporate rules referred to in paragraph 1 shall specify at least:
(a) the structure and contact details of the group of undertakings, or group of enterprises engaged in a joint economic activity and of each of its members;
(b) the data transfers or set of transfers, including the categories of personal data, the type of processing and its purposes, the type of data subjects affected and the identification of the third country or countries in question;
(c) their legally binding nature, both internally and externally;
(d) the application of the general data protection principles, in particular purpose limitation, data minimisation, limited storage periods, data quality, data protection by design and by default, legal basis for processing, processing of special categories of personal data, measures to ensure data security, and the requirements in respect of onward transfers to bodies not bound by the binding corporate rules;
(e) the rights of data subjects in regard to processing and the means to exercise those rights, including the right not to be subject to decisions based solely on automated processing, including profiling in accordance with Article 22, the right to lodge a complaint with the competent supervisory authority and before the competent courts of the Member States in accordance with Article 79, and to obtain redress and, where appropriate, compensation for a breach of the binding corporate rules;
(f) the acceptance by the controller or processor established on the territory of a Member State of liability for any breaches of the binding corporate rules by any member concerned not established in the Union; the controller or the processor shall be exempt from that liability, in whole or in part, only if it proves that that member is not responsible for the event giving rise to the damage;
(g) how the information on the binding corporate rules, in particular on the provisions referred to in points (d), (e) and (f) of this paragraph is provided to the data subjects in addition to Articles 13 and 14;
(h) the tasks of any data protection officer designated in accordance with Article 37 or any other person or entity in charge of the monitoring compliance with the binding corporate rules within the group of undertakings, or group of enterprises engaged in a joint economic activity, as well as monitoring training and complaint-handling;
(i) the complaint procedures;
(j) the mechanisms within the group of undertakings, or group of enterprises engaged in a joint economic activity for ensuring the verification of compliance with the binding corporate rules. Such mechanisms shall include data protection audits and methods for ensuring corrective actions to protect the rights of the data subject. Results of such verification should be communicated to the person or entity referred to in point (h) and to the board of the controlling undertaking of a group of undertakings, or of the group of enterprises engaged in a joint economic activity, and should be available upon request to the competent supervisory authority;
(k) the mechanisms for reporting and recording changes to the rules and reporting those changes to the supervisory authority;
(l) the cooperation mechanism with the supervisory authority to ensure compliance by any member of the group of undertakings, or group of enterprises engaged in a joint economic activity, in particular by making available to the supervisory authority the results of verifications of the measures referred to in point (j);
(m) the mechanisms for reporting to the competent supervisory authority any legal requirements to which a member of the group of undertakings, or group of enterprises engaged in a joint economic activity is subject in a third country which are likely to have a substantial adverse effect on the guarantees provided by the binding corporate rules; and
(n) the appropriate data protection training to personnel having permanent or regular access to personal data.
3. The Commission may specify the format and procedures for the exchange of information between controllers, processors and supervisory authorities for binding corporate rules within the meaning of this Article. Those implementing acts shall be adopted in accordance with the examination procedure set out in Article 93(2).
Understanding This Article
Article 47 establishes the framework for Binding Corporate Rules (BCRs)—comprehensive internal data protection policies that allow multinational organizations to transfer personal data between entities within their corporate group, even to countries without adequacy decisions. BCRs are particularly valuable for large multinational corporations with complex data flows across many jurisdictions.
Unlike Standard Contractual Clauses which govern bilateral relationships, BCRs create a unified data protection framework across an entire corporate group. They must be legally binding on all group members (often through incorporation into employment contracts, corporate governance documents, or enforceable agreements), apply to all employees, and expressly confer enforceable rights on data subjects against any group member.
The 14 requirements in paragraph 2 are comprehensive. They cover not just data protection principles, but also practical implementation mechanisms: complaint procedures (point i), compliance verification through audits (point j), change management (point k), supervisory authority cooperation (point l), and reporting of adverse legal requirements in third countries (point m). This last requirement became particularly significant post-Schrems II, as organizations must notify authorities if they face surveillance demands that could undermine BCRs.
Crucially, paragraph 2(f) requires an EU-established entity to accept liability for breaches by non-EU group members. This means data subjects can bring claims in EU courts even if the breach occurred in Asia, Africa, or Latin America. This liability provision ensures BCRs have real teeth and aren't just paper commitments.
The approval process is rigorous, often taking 12-18 months, and involves coordination with multiple supervisory authorities through the consistency mechanism. However, once approved, BCRs provide long-term legal certainty for complex global data operations.
Key Points
BCRs are internal policies for multinational organizations to govern intra-group data transfers
Must be legally binding on all group members and confer enforceable rights on data subjects
Require supervisory authority approval through consistency mechanism
Must specify 14 core elements including structure, rights, liability, and compliance monitoring
EU entity must accept liability for breaches by non-EU group members
Include audit mechanisms, complaint procedures, and training requirements
Practical Application
Example 1 - Global Technology Company: A multinational tech company with subsidiaries in 40 countries implements BCRs for controller data (employee HR data, customer data, supplier data) and separate BCRs for processor data (cloud services provided to customers). The BCRs specify that the Irish subsidiary (EU headquarters) accepts liability for breaches by any group member. They establish a Global Data Protection Office to monitor compliance, implement quarterly audit programs, create an internal complaint portal accessible to employees and customers worldwide, and require all staff with data access to complete annual BCR training. The BCRs are incorporated into all employment contracts globally.
Example 2 - Financial Services Group: An international bank with operations in 25 countries develops BCRs to govern transfers of customer financial data, employee records, and transaction data. The BCRs specify that customer data from EU branches can be accessed by fraud detection teams in Singapore and back-office operations in India. They establish detailed security requirements, purpose limitations, access controls, and retention periods. When Singapore introduces new financial surveillance laws, the bank's compliance team evaluates the impact, determines the laws could trigger BCR reporting requirements under paragraph 2(m), and notifies the lead supervisory authority along with impact assessment and proposed supplementary measures.
Example 3 - Healthcare and Pharmaceutical Group: A global pharmaceutical company implements BCRs covering clinical trial data, employee health data, and research data. The BCRs specify that the German entity accepts liability for the entire group. They establish strict access controls, requiring documented justification for each access to clinical trial data from non-EU entities. When a Brazilian subsidiary experiences a data breach due to ransomware, EU data subjects can bring claims in German courts under the BCRs' liability provisions. The German entity must compensate affected individuals and can seek recourse from the Brazilian subsidiary internally.
Example 4 - BCR Audit and Compliance: A retail group with BCRs conducts annual audits of all entities transferring personal data. The audit in the Mexican subsidiary reveals inadequate implementation of data subject rights procedures specified in the BCRs. The Global Data Protection Officer documents the finding, requires corrective action within 90 days, reports to the board, and notifies the lead supervisory authority as required by BCR paragraph 2(l). The Mexican entity implements improved procedures, and the follow-up audit confirms compliance.