Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

EU Digital Omnibus: AI Act Delay, GDPR Changes and What They Mean for Your ERP

AI Act high-risk rules delayed to December 2027, GDPR changes still under negotiation: what is law, what is only proposed, and an ERP action plan for CIOs and DPOs.

EU Digital Omnibus: AI Act Delay, GDPR Changes and What They Mean for Your ERP

In a year, “Digital Omnibus” has become a catch-all label for two very different texts. The first, on the AI Act, is adopted and in force: obligations for high-risk AI systems have been postponed. The second, which touches the GDPR, the ePrivacy Directive, the Data Act and incident reporting, is still under negotiation. Confusing the two leads either to suspending compliance work that is still required, or to planning around rules that do not exist yet.

This article takes stock as of 20 November 2026 (the date the cited sources were last checked), separates law from proposals, and turns both into actions for the CIO and DPO of a mid-sized company running an ERP.

What the Digital Omnibus Is

Two texts, two statuses

On 19 November 2025, the European Commission presented a digital simplification package made up of two proposed regulations:

  • The AI Digital Omnibus, which amends the AI Act (Regulation (EU) 2024/1689) and shifts its timeline.
  • The “data” Digital Omnibus (COM(2025) 837), which touches the GDPR, ePrivacy, the Data Act and incident notification rules (eudigitalpolicy.eu, status as of 28 October 2026).

Their progress is not comparable:

TextStatus on 20 November 2026Legal value
AI Digital OmnibusAdopted: political agreement on 7 May 2026, Parliament vote on 16 June, Council adoption on 29 June, publication in the Official Journal on 8 July, entry into force on 27 July 2026 (Usercentrics)Binding law
”Data” Digital OmnibusCouncil mandate agreed on 21 October 2026, no Parliament position adopted, trilogues not opened (eudigitalpolicy.eu)Proposal, no legal effect

For the first, the timeline is confirmed by several law firms: the postponement schedule was already part of the provisional agreement in June (Sidley, 22 June 2026). For the second, keep in mind that a text under negotiation can still be deeply amended. The European Parliament’s tracking pages could not be consulted at the time of writing: the dates above rely on the secondary sources cited, and the monitoring list at the end lets you re-check them.

AI Act: The New Timeline and What Still Applies

The dates that change

According to the cited sources, the revised deadlines are:

  • Annex III high-risk systems (employment, credit scoring, education, biometrics, critical infrastructure): 2 December 2027, instead of 2 August 2026.
  • AI embedded in regulated products (Annex I, for example medical devices or machinery): 2 August 2028.
  • Marking of generated content: a grace period until 2 December 2026 for generative AI systems already on the market before 2 August 2026. Systems placed on the market after that date do not benefit from it.
  • New prohibition on systems generating non-consensual intimate images or child sexual abuse material, applicable from 2 December 2026.

Source: Usercentrics, cross-checked with Sidley. Sidley also notes a simplified registration procedure for systems relying on the Article 6(3) exemption, and a narrower scope for AI functions that merely assist the user.

What does not move: the Article 5 prohibitions (in force since February 2025) and the obligations on general-purpose AI models stay in place. The Article 50 transparency obligations for deployers due in August 2026 are not postponed, apart from the marking grace period above.

ERP cases: HR scoring, recruitment, credit

The ERP use cases that fall under Annex III are those identified in our guide to the AI Act and ERP: CV screening and employee evaluation in an HRIS module, and creditworthiness scoring of individuals. For these, the delay changes the timeline, not the classification: a CV-screening module remains a high-risk system, with its deadline pushed back by sixteen months.

Note that the article above was written before the Omnibus was adopted and still gives 2 August 2026 as the high-risk deadline. For any planning decision, 2 December 2027 is the date that counts.

The narrower scope (assistive functions with no risk to health or safety) is good news for ERP data-entry or search copilots, but it does not remove the need to map function by function: it is the vendor and the use that determine the classification, not the product name.

GDPR: Proposed Changes and Areas of Uncertainty

Here, everything is still proposed. These are the four structural points of the Commission’s text, with the Council’s position where known.

Definition of personal data

The Commission proposes adding an entity-relative test to Article 4(1): information is not necessarily personal data for every entity that receives it, merely because another entity can identify the person. This echoes the Court of Justice ruling of 4 September 2025 (EDPS v SRB, C-413/23 P) on pseudonymised data (Lexology).

The European Data Protection Board (EDPB) and the European Data Protection Supervisor (EDPS), in Joint Opinion 2/2026, consider that the change would go beyond a targeted adjustment and significantly narrow the notion of personal data (EDPB-EDPS, Joint Opinion 2/2026). In its mandate, the Council removed this change from the definition and added a new Article 25a on pseudonymisation instead (Addleshaw Goddard, 26 October 2026).

Legitimate interest and AI

The Commission wanted to expressly recognise legitimate interest (Article 6(1)(f)) as a legal basis for developing and operating AI systems or models. The Council did not keep the amendment: it adds a recital stating that developing and operating an AI system is not, in itself, a legitimate interest (Addleshaw Goddard). In other words, case-by-case analysis (the balancing test) remains the rule.

Breach notifications

The Council mandate keeps the high-risk threshold for notification. According to Addleshaw Goddard, the 72-hour deadline is unchanged; other summaries of the mandate mention a longer period. Readings diverge: until the final text is stable, keep applying 72 hours.

Cookies and ePrivacy

The Council mandate provides that consent would no longer be required for aggregated audience measurement, security and contextual advertising, with a one-click refusal button (Addleshaw Goddard). For an ERP, this mainly concerns customer portals, supplier portals and connected storefronts.

A distant timeline

Parliament has not adopted a position: the joint ITRE-LIBE report was still awaiting a committee decision at the end of October, with a very high volume of amendments (Praxikon, status as of 28 October 2026). Addleshaw Goddard expects negotiations after March 2027. No GDPR change is applicable for several months, and probably not before 2027 at best.

Data Act, ePrivacy and Incident Reporting: the Single Entry Point

The Commission’s proposal provides for a single entry point, run by ENISA, to report incidents under NIS2, DORA, eIDAS or CER, so the same incident does not have to be reported to several authorities (eudigitalpolicy.eu).

The Council has reshaped this scheme: national entry points in each Member State, with an information point kept at ENISA level (Addleshaw Goddard). For a mid-sized company the practical benefit is clear: one form for several regimes. But the final shape will depend on the trilogues.

On the Data Act, the “data” package provides for consolidation measures. The Council strengthens trade-secret protection: confidentiality measures required before disclosure, and possible refusal where serious economic harm is demonstrated. For the portability and cloud-switching obligations that affect your SaaS ERP, see our analysis of the European Data Act and cloud ERP (in French): the Data Act itself remains applicable, and the Omnibus only adjusts it.

Concrete Impact on Your ERP

Record of processing and DPIA

Nothing requires you to overhaul the record of processing activities. However, if your ERP activates AI functions (scoring, summarising employee files, a copilot), those functions must appear in it with their legal basis. Do not switch your legal bases to an “AI” legitimate interest: that basis is only a proposal, and the Council has explicitly set it aside.

AI modules

Inventory the AI functions enabled, by module and legal entity. Classify them (prohibited, high-risk, transparency, minimal) and attach a date to each function: 2 August 2026 for transparency, 2 December 2027 for Annex III. This is the only timeline enforceable today.

Access rights and segregation of duties

The delay does not lower the requirement for human oversight. Access rights to the HR and financial data used by AI, and the traceability of assisted decisions, remain a substantial workstream. Our guide to the ERP audit trail (in French) details the reusable foundation.

Vendors and processors

Ask your vendors about three things: which AI functions are enabled by default, which AI Act classification they apply, and their documentation timeline. Contracts must specify the provider/deployer split and the handling of sub-processors. A vendor that uses the delay to slow down its documentation is a risk signal, not a reason to relax.

What to Do Now: Do Not Suspend Compliance

The delay buys time; it does not remove the obligation. Here is a prioritisation for 2026-2027.

ObligationStatus2026-2027 action
Prohibited AI practices (Article 5)Applicable since February 2025Check that no ERP function falls within them
Article 50 transparencyAugust 2026, marking grace period until 2 December 2026 for earlier systemsTell users when your copilots use AI
Annex III high-risk AI (HR, credit)2 December 2027Map, document, plan human oversight
AI embedded in products (Annex I)2 August 2028Track the vendors concerned (industry, healthcare)
GDPR (definition, AI legitimate interest)Proposal, under negotiationNo overhaul needed, monitoring only
Breach notificationCurrent rules: 72 hours, risk thresholdKeep the process as is
Single incident entry pointProposal, final form uncertainPrepare a unified NIS2/GDPR incident process
Cookies and ERP portalsProposalAudit customer and supplier portals

Action list for the DPO

  • Maintain the record of processing and current legal bases.
  • Document each AI function enabled in the ERP, with its purpose.
  • Do not anticipate changes to the definition of personal data in your anonymisation analyses.

Action list for the CIO

  • Produce the inventory of AI functions by module by the end of Q1 2027.
  • Ask vendors for their classification and compliance schedule.
  • Lock down access rights and logging for AI modules.
  • Add an “Annex III compliance” milestone to the roadmap before 2 December 2027, with a six-month margin.

For non-financial reporting, which falls under a different Omnibus, see our analysis of the CSRD and CSDDD simplification.

Monitoring: Official Sources to Follow

These links point to general or tracking pages: check the status there before any structural decision, as the “data” file may still change before the trilogue.

To follow these developments without losing your evenings, subscribe to the regulatory watch newsletter: one update a month on the AI Act, the GDPR and what they mean for your ERP.