Binding corporate rules: the EDPB specifies processor BCR scope and the 2028 alignment process
The EDPB adopts recommendations 1/2026 on processor BCRs. Scope, processing agreements, approval limits and alignment in 2028.

The European Data Protection Board (EDPB) adopted the final version of its recommendations 1/2026 on processor binding corporate rules, known as BCR-P, on 10 November 2026. Its public communication on the 11th highlights their application to holders and applicants, with alignment during the procedure or in the 2028 annual update, depending on the situation. The document develops that transition and also defines which transfers the instrument covers and what its approval does not mean.
The announcement predates this 15 November edition's 48-hour window. Its professional relevance lies not in presenting it as today's decision, but in explaining a final version replacing earlier documents and shaping review work for business groups and their advisers. Version 2.0 identifies adoption after public consultation; version 1.0, dated 15 January, concerned the consultation stage.
An instrument within the group, not universal authorisation
Section 1.2 explains that BCR-P apply to data processed by group members within the GDPR's territorial scope as processors for a controller outside the group. Those processors then transfer data to other members of the same group acting as sub-processors in third countries, including onward transfers between bound members. The route described matters as much as the instrument's name.
The recommendations clarify that BCR-P do not cover a direct transfer from an external controller subject to the GDPR to a group processor in a third country. That flow requires a different Article 46 instrument. This distinction prevents approval of a provider's rules being used as an automatic answer to every transfer to its international companies.
The same document distinguishes BCR-P from controller rules, BCR-C. The latter concern transfers from controllers subject to the GDPR to other controllers or processors within the same group established in third countries. The names are not interchangeable. Each entity's position and the specific flow determine the problem the documentation must address.
An agreement with the controller is still needed
Section 1.3 maintains, alongside BCR-P, a contract or other binding legal act with the external controller containing the elements required by Article 28(3) GDPR. The agreement must be signed with one or more group members within the Regulation's territorial scope, refer to the BCR-P and allow the controller to enforce them against group members.
Binding corporate rules therefore do not simply replace the processing agreement with the client. The document separates the two levels and allows the lead authority to request a template of the proposed agreement during the procedure. It also recalls that a general description of transfers in BCR-P does not remove the requirement to specify covered processing in the corresponding agreements.
For the internal relationship between a processor and group sub-processors, the recommendations explain that BCR-P are also intended to meet Article 28(4). A member that has implemented them will not need a sub-processing agreement with every internal sub-processor in the group within that framework. This does not remove the passing on of the controller's instructions or permit weakening the safeguards in the rules.
What approval confirms and what it excludes
Section 1.4 distinguishes the authority approving BCRs from the authorities competent for the controller and exporting processor in a particular transfer. The draft approval decision is submitted for an EDPB opinion. Approval confirms that Article 47 requirements are met and that the commitments provide appropriate safeguards within Article 46.
The document immediately adds a relevant limit: approving BCR-P does not confirm that processing activities actually meet their conditions in practice, nor assess every GDPR requirement applicable to each processing activity. Approval of the instrument and operational compliance are different levels. Advisers should not present the first as a general audit resolving the second.
The recommendations give the example of case-by-case assessment of whether supplementary measures are needed for each transfer. The exporter, meaning the processor, must implement them when needed, and the controller on whose behalf data are transferred must verify them. The text clarifies that those measures are not assessed as part of the BCR-P approval procedure.
Global policy and the decision's scope
A group may use BCR-P as a global data protection policy for bound entities acting as processors or sub-processors, inside or outside the European Economic Area. But section 1.4 warns that approval is limited to transfers subject to the GDPR to third countries without an applicable adequacy decision and onward transfers to bound group members.
For entities in countries with a relevant adequacy decision, transfers covered by that decision are not subject to BCR approval while it applies to them. The document allows the group to prepare conditional application in case of future invalidation and identify this in its member list. It does not turn that option into a statement that any particular decision has been invalidated.
The distinction between a voluntary global policy and the scope of approval is useful when reviewing commercial documentation. Saying a group applies a common policy does not itself establish that every flow is covered by one transfer basis. Legal analysis requires preserving the categories of controller, processor, exporter, importer and bound member, rather than reducing them to the group's name.
How alignment is organised
Section 1.5 says the recommendations take effect from publication of the final version. New applicants and those with applications in progress must align them with the document. A specific provision concerns applications that had already reached the consolidated-draft stage at publication and for which the EDPB issues an opinion by 30 June 2027: alignment will take place with the 2028 annual update.
BCR-P holders must also adapt their rules in the 2028 annual update. The text adds that, generally, these changes will not require new approval because they improve safeguards for data subjects. This is not a universal exemption for every future amendment. This article is limited to the transition described in the section cited.
For context on other European priorities, readers can consult our coverage of automated candidate selection in 2027. These are separate announcements from the same plenary. Data protection for self-employed lawyers and the analysis of professional secrecy and client data in AI offer related contexts, not substitutes for checking the actual international flow.
Further context
Adopting common recommendations does not automatically approve a particular group's rules: assessing its commitments and authorising them remain separate stages.
Sources
Recommendations 1/2026, version 2.0 of 10 November, sections 1.1–1.5, and the EDPB's official communication of the 11th, consulted on 15 November 2026. This article does not audit a company's BCRs or develop every element of the document's application form and technical table. Alignment dates depend on the situation described, not a single undifferentiated deadline for every applicant.
Fuentes
The specific data in this article come from the official sources cited.


