Companies and other organisations with fewer than 1,000 employees would no longer have to keep records of their low-risk data processing under the General Data Protection Regulation, according to the text the European Parliament has prepared for a plenary vote in Strasbourg. The relief has a hard edge. Any processing activity likely to result in a high risk to people's rights, and any activity that amounts to large-scale monitoring of people as a core business, would still have to be documented - activity by activity rather than across the whole organisation.
The wording sits in two European Parliament documents dated November 18, 2026, filed under report A10-0041/2026 on the regulation known as Omnibus IV. One contains 43 amendments from three parliamentary committees. The other, Amendment 44, is a 39-page consolidated text of the entire regulation, tabled on behalf of the same three committees and drafted as the finished act, "Regulation (EU) 2026/...". Parliament's legislative procedure file lists November 23, 2026, the opening day of the session, as the indicative plenary date. If Parliament adopts the text and the Council approves it, the GDPR's record-keeping threshold would move from 250 employees, where it has stood since the regulation began to apply in May 2018, to 1,000.
In Short
The EU is close to a final vote on a change that frees companies and organisations with fewer than 1,000 staff from keeping GDPR records for processing that is not high risk. It matters to mid-sized businesses between 250 and 1,000 employees, including agencies, publishers and ad tech firms, which lose today's exemption as soon as they pass 250 staff. Records would still be required for each specific activity that is high risk or that involves large-scale monitoring of people as a core business, which under long-standing EU guidance can include behavioural advertising. The text also creates a legal category of "small mid-cap enterprises" and extends lighter rules to them in five other EU regulations.
Two documents, one vote
The two documents have different authors and different jobs. Amendments 001-043 are signed by the Committee on Economic and Monetary Affairs, the Committee on the Environment, Climate and Food Safety, and the Committee on Civil Liberties, Justice and Home Affairs. They are the amendments of the joint report by rapporteurs Mariateresa Vivaldini, Niels Flemming Hansen and Lukas Mandl. According to Parliament's procedure file for 2025/0130(COD), the committees adopted that report on February 25, 2026, and it was tabled for plenary on March 3, 2026. It formed the basis of Parliament's mandate for talks with the Council.
Amendment 44 is a different kind of document. It is tabled by Aurore Lalucq on behalf of the economic affairs committee, Pierfrancesco Maran on behalf of the environment committee and Javier Zarzalejos on behalf of the civil liberties committee, and it rewrites the whole Commission proposal in one block. A note on its first page says new or amended text is marked in bold italics and deletions with a marker symbol. Its second footnote reads: "Position of the European Parliament of ... [(OJ ...)/(not yet published in the Official Journal)] and decision of the Council of ...." That is the format of a text already agreed with the Council and awaiting formal adoption.
The procedure file supports that reading. It records that Parliament confirmed the decision to open interinstitutional negotiations on March 11, 2026, and that the committees approved "the text agreed at 1st reading interinstitutional negotiations" on July 2, 2026. Parliament announced the provisional agreement on June 9, 2026, saying the deal would extend SME exemptions to small mid-caps "to avoid cliff-edge situations where a company's obligations drastically increase when they grow beyond the SME threshold."
The timing drew comment from Luis Alberto Montezuma, who works on data and privacy policy and labels his LinkedIn posts as personal opinion. In a post published on November 21, 2026, he wrote that the next plenary sitting would take place in Strasbourg from November 23. "Regarding the Article 30 GDPR reform, the next step is for the European Parliament to approve the final text," he wrote. He added that it remained unclear whether Parliament would consider further amendments before approving its position, and linked both documents.
What Article 30 requires now
Article 30 of the GDPR obliges every data controller to keep a written record of its processing activities: who the controller is, the purposes of processing, the categories of people and personal data involved, the recipients, transfers outside the EU, retention periods where possible, and a general description of security measures. Processors keep a parallel record. Paragraph 5 holds the only exemption, and it is narrow. Under the current text, it applies to enterprises and organisations employing fewer than 250 persons, and it falls away if the processing is likely to result in a risk to people's rights and freedoms, if the processing is not occasional, or if it includes special categories of data or data on criminal convictions.
The "not occasional" condition is the reason the exemption has meant little in practice. Payroll, a customer database or a newsletter list are not occasional, so most small businesses that process personal data at all end up outside it. A survey of 510 data protection professionals published by noyb in March 2026 found records of processing activities at the top of the list of GDPR tasks that consume the most work. The same survey found that about 43% of respondents at organisations with fewer than 250 employees already kept records voluntarily, and the report concluded that a rise to 750 was unlikely to have a meaningful impact. Regulators still treat the record as a working document: the Saxony-Anhalt data protection authority's deletion guide for small businesses, published in September 2026, builds its first step on the Article 30 record.
The new Article 30(5), word for word
Amendment 44 replaces paragraph 5 with the following text:
"5. The obligations referred to in paragraphs 1 and 2 shall not apply to an enterprise or an organisation employing fewer than 1000 persons unless and to the extent that a specific processing activity carried out by that enterprise or organisation is likely to result in a high risk to the rights and freedoms of data subjects, as referred to in Article 35, in particular with regard to the cases referred to in paragraph 3 of that Article and, in any event, where the processing activity constitutes a core activity requiring the appointment of a data protection officer pursuant to Article 37(1), point (b) or (c).
The obligations referred to in paragraphs 1 and 2 of this Article shall only apply to the specific processing activity that meets the conditions established in this paragraph."
Four changes stand out against the current law. The headcount rises fourfold. The trigger moves from "risk" to "high risk", tied to Article 35, the provision on the DPIA, or data protection impact assessment. The "not occasional" condition disappears entirely, as does the automatic loss of the exemption for any processing of special categories of data. And when a trigger applies, the record covers only the activity that triggered it, not every processing operation in the organisation.
The text also adds a condition that neither the current law nor the Commission's proposal contained: records are required "in any event" for core activities that oblige an organisation to appoint a data protection officer under Article 37(1)(b) or (c). Those provisions cover organisations whose core activities consist of regular and systematic monitoring of people on a large scale, or large-scale processing of special categories of personal data and data on criminal convictions.
Three versions of one paragraph
| Element | Current GDPR (applies since May 25, 2018) | Commission proposal (May 21, 2025) | Committee amendments (report A10-0041/2026) | Agreed text (Amendment 44) |
|---|---|---|---|---|
| Who qualifies | Fewer than 250 persons | Fewer than 750 persons | SMEs, small mid-caps, or organisations with fewer than 1,000 persons | Any enterprise or organisation with fewer than 1,000 persons |
| What removes the exemption | Processing likely to result in a risk; processing not occasional; special categories or criminal data | Processing likely to result in a high risk (Article 35) | A specific activity likely to result in a high risk (Article 35, in particular Article 35(3)), or a core activity under Article 37(1)(b) or (c) | A specific activity likely to result in a high risk (Article 35, in particular Article 35(3)) and, in any event, a core activity requiring a DPO under Article 37(1)(b) or (c) |
| Scope of records when triggered | Not limited in the text | Not limited in the article | Only that specific activity | Only that specific activity |
| Public authorities | Not addressed | Not addressed | New paragraph 5a: records always required | Recital 10: should not benefit from the derogation; no paragraph 5a |
Sources: Regulation (EU) 2016/679 (current text, paraphrased); amendments 001-043 and Amendment 44 to report A10-0041/2026, dated November 18, 2026 (Commission, committee and agreed wording).
What the committees wanted and did not get
The committees' version, Amendment 26, listed three groups by name: "micro, small, and medium-sized enterprises, to small mid-cap enterprises or to organisations employing fewer than 1000 persons." The agreed text drops the categories and keeps only headcount. In practice, this means the turnover and balance sheet limits that define a small mid-cap elsewhere in the regulation play no role in Article 30(5). A company with 900 employees and turnover far above 200 million euros would fall under the 1,000-person line as the agreed article is written.
The committees also wanted a new paragraph, Amendment 27, stating that "the obligations referred to in paragraphs 1 and 2 shall apply to public authorities and bodies." That paragraph is not in the agreed article. The point survives only in recital 10, which says "it is important to clarify that public authorities and bodies are not concerned by the objectives of that amendment" and "therefore should not benefit from that derogation." Recitals explain how an EU act should be read; they are not operative provisions in their own right.
How the test works, according to the agreed text
Read together with recitals 10 to 13, the agreed Article 30(5) sets out a sequence of conditions:
- Headcount. The derogation covers any enterprise or organisation "employing fewer than 1000 persons." Recital 10 says public authorities and bodies should not benefit.
- High risk, activity by activity. Records are required for each "specific processing activity" likely to result in a high risk under Article 35. Recital 11 says the processing listed in Article 35(3) "should be considered as requiring the data controller or the processor to maintain up-to-date records of those processing activities." Article 35(3) covers systematic and extensive evaluation of personal aspects based on automated processing, including profiling, where decisions with legal or similarly significant effects follow; large-scale processing of special categories or criminal data; and large-scale systematic monitoring of publicly accessible areas.
- Core monitoring activities. Regardless of the risk assessment, records are required where the activity is a core activity requiring a data protection officer under Article 37(1)(b) or (c). Recital 13 says such cases present "structural or recurring risks and should therefore require that records of related processing activities are always maintained."
- Ancillary processing. Recital 13 adds that core activities "relate to its primary activities and do not relate to the processing of personal data as ancillary activities." Its example: "in the private sector, where the processing of personal data would constitute an ancillary activity and would not result in a high risk to the rights and freedoms of data subjects, it would not be required to maintain records for that particular processing activity."
- Employment data. Recital 12 says processing of special categories of data for employment, social security and social protection law under Article 9(2)(b) "would not always be likely to result in a high risk" and "should not, as such, require that records of those processing activities be maintained, unless it is assessed that the processing is likely to result in a high risk."
- Limited scope. Where any trigger applies, the record covers only "the specific processing activity that meets the conditions established in this paragraph."
The text does not say who carries out the assessment in step 2 or how it is documented. Its wording, "unless and to the extent that", appears to place the judgment with the organisation claiming the derogation.
What it means for advertising and ad tech
For advertising businesses, the core-activity clause is likely to decide how much changes. The Article 29 Working Party's 2017 guidelines on data protection officers, later endorsed by the European Data Protection Board, list behavioural advertising, email retargeting, data-driven marketing activities and loyalty programmes among examples of regular and systematic monitoring. Where such monitoring is large scale and forms part of an organisation's core business - as it does for many tracking, measurement and audience data companies - the agreed text keeps records mandatory for those activities, whatever the company's size.
So who gains? The changes are larger for businesses where personal data processing supports the primary activity rather than being it. An agency, a publisher or an online retailer with 600 employees currently cannot rely on the 250-person exemption at all. Under the agreed text, it could stop documenting ancillary processing that is not high risk and keep records only for the specific activities that cross the high-risk or core-activity line. That is the "ancillary activity" case recital 13 describes.
Two caveats limit the practical effect. First, the record is not the only accountability document in the GDPR: Article 5(2) still requires controllers to demonstrate compliance, and Article 35 still requires impact assessments for high-risk processing, which overlaps with the processing that keeps the record obligation alive. Second, what counts as "high risk" could shift if the separate Digital Omnibus is adopted as the Council wants. Its mandate agreed on October 21, 2026 would have the European Data Protection Board establish EU-wide lists of processing that does and does not need an impact assessment under Article 35 - the same article the new Article 30(5) relies on.
The link to data protection officers is new. A CNIL-published study in July 2025 found that 36% of data protection officers worked in small companies. Under the agreed text, the circumstances that oblige an organisation to appoint one under Article 37(1)(b) or (c) would also keep its record obligation alive for those activities.
Defining a small mid-cap
Beyond Article 30, the regulation introduces a legal definition of "small mid-cap enterprises" in the GDPR and in four other acts. The agreed definition in the GDPR's new Article 4(28) reads: "enterprises that are not micro, small and medium-sized enterprises, that employ fewer than 1000 persons, and that either have an annual turnover not exceeding EUR 200 million or an annual balance sheet total not exceeding EUR 172 million." The numbers are calculated under the Annex to Commission Recommendation (EU) 2025/1099 of May 21, 2025.
| Definition | Employees | Annual turnover | Balance sheet total | Source |
|---|---|---|---|---|
| SME (Recommendation 2003/361/EC) | Fewer than 250 | Up to EUR 50 million | Up to EUR 43 million (turnover or balance sheet) | Footnote 7 of the Commission text, amendments 001-043 |
| Small mid-cap, Commission proposal | Fewer than 750 | Up to EUR 150 million | Up to EUR 129 million | European Parliament press release, June 9, 2026; Commission prospectus wording |
| Small mid-cap, agreed text | Fewer than 1,000 | Up to EUR 200 million | Up to EUR 172 million (turnover or balance sheet) | Amendment 44, Article 1(1) and recital 8 |
| Small mid-cap, prospectus rules (agreed) | Average fewer than 1,000 | Up to EUR 200 million | Up to EUR 172 million (two of three criteria), or a MiFID II small mid-cap | Amendment 44, Article 4(2)(b) |
Recital 8 says the definition "covers enterprises that are up to four times the size of SMEs without extending to large mid-caps or large enterprises." The Commission's text had said "up to three times." By PPC Land's calculation, each agreed threshold is exactly four times the SME limit: 1,000 against 250 employees, 200 million against 50 million euros in turnover, and 172 million against 43 million euros in balance sheet total. Recital 8 also says references to the two Commission recommendations "should be understood as referring to the original version," so later changes to those recommendations would not automatically move the thresholds.
The GDPR also gains small mid-caps in two softer provisions. Articles 40 and 42, which ask Member States, supervisory authorities, the Board and the Commission to take account of the needs of micro, small and medium-sized enterprises when encouraging codes of conduct and certification, would name small mid-caps too. Recital 14 adds that "those codes of conduct comply inter alia with the objectives of minimising the regulatory burden and promoting digitalisation."
Beyond data protection: five other regulations
Omnibus IV amends six regulations in total. The GDPR changes take up Article 1 of the agreed text; the rest concern trade defence, prospectuses, batteries and fluorinated gases.
| Regulation | Agreed text (Amendment 44) | Commission proposal |
|---|---|---|
| 2016/1036 (anti-dumping) | An "SME and SMC Helpdesk" replaces the SME Helpdesk; standard questionnaires in all official languages; investigations concluded within one year whenever possible and within 14 months in all cases; investigation periods should coincide with the financial year "especially in the case of diverse and fragmented sectors largely composed of SMEs or SMCs" | Extend existing SME provisions to small mid-caps |
| 2016/1037 (anti-subsidy) | Same helpdesk; investigations concluded within 13 months in all cases | Extend existing SME provisions to small mid-caps |
| 2017/1129 (prospectus) | SMEs, small mid-caps and issuers on SME growth markets may draw up an EU Growth issuance prospectus for public offers, "provided that they have no securities admitted to trading on a regulated market"; prospectus exemption for securities from resolution conversions, including in third countries | Small mid-caps defined as fewer than 750 employees, EUR 129 million balance sheet, EUR 150 million turnover (two of three) |
| 2023/1542 (batteries) | Due diligence chapter does not apply below EUR 200 million net turnover; report "at the latest by 18 August 2028 and at least every five years thereafter, and without undue delay after a significant change occurs"; may be included in sustainability reporting, "including through a single consolidated report" | EUR 150 million threshold; report at least every three years |
| 2024/573 (F-gas) | F-gas Portal registration limited to imports and exports of fluorinated gases, products and equipment containing 10 tonnes of CO2 equivalent or more of hydrofluorocarbons or 100 tonnes of other fluorinated gases per calendar year, and certain permitted exports; licence needed only where registration is required | Registration limited to imports subject to reporting and exports under an export limitation |
Recital 21 says the battery report is currently annual. Recital 2 restates the Commission's commitment to reduce administrative burden "by at least 25% for all enterprises and at least 35% for small and medium-sized enterprises." Recital 4 says SMEs "represent 99% of all Union companies" and that "approximately 20% of all SMCs were SMEs three years earlier."
How the file got here
The Commission published the proposal, COM(2025)0501, on May 21, 2025, as part of its fourth simplification package. It originally set the Article 30 line at 750 employees and defined small mid-caps by reference to Commission Recommendation C(2025) 3500. PPC Land reported on July 9, 2025 that the European Data Protection Board and the European Data Protection Supervisor had backed the change in a joint opinion adopted on July 8, 2025, while asking for more justification of the wider eligibility. Recital 15 of the agreed text records that opinion, dated July 8, 2025.
Pressure for more went in both directions. In a 19-page submission reported in November 2025, Germany argued that Omnibus IV's GDPR changes fell short and pressed for broader reform. Parliament's committees then raised the line to 1,000, narrowed the record to specific activities and added the core-activity clause in their February 2026 report, before the trilogue negotiations with the Council produced the June 9 deal.
Most of the committees' Article 30(5) wording survived, except the named categories and the public authorities paragraph. A recurring review fell away too. The committees' proposed Article 6a would have required a review of the thresholds "at least every five years" with the aim of "one fully harmonised definition." The agreed Article 7 asks for a single report within five years of entry into force on the definition and its thresholds "in light of inflation, scope, and economic and market developments," accompanied "where appropriate, by a legislative proposal."
A separate track for the GDPR
Omnibus IV is not the only GDPR revision in progress, and it is the narrower one. The Digital Omnibus, which the Commission proposed in November 2025, reaches much further: a November 2025 draft covered the definition of personal data, a legitimate interest basis for AI development and limits on access rights. In February 2026, the EDPB and EDPS rejected the narrowing of the personal data definition in their joint opinion on that package.
That file is at an earlier stage. The Council agreed its mandate on October 21, 2026, and said at the time that negotiations could begin only once Parliament had adopted its own position. In Parliament, the file drew more than 1,000 amendments, and noyb counted 248 amendments from the EPP group that it rated as weakening privacy. Omnibus IV, by contrast, reached a provisional agreement in June and now awaits only formal adoption.
Why this matters for the marketing community
The record of processing activities is the inventory behind most GDPR compliance work in marketing: consent management, vendor due diligence, data subject requests and breach response all draw on it. Lifting the duty for low-risk processing below 1,000 employees removes a document that mid-sized agencies, publishers and retailers have had to maintain since 2018. Yet the clause that keeps records mandatory for large-scale monitoring as a core activity points at the business model of much of ad tech. The result is uneven by design. A company whose product is tracking keeps its records for that product; a company that merely uses personal data to run its business gains the most.
The headcount-only test is the other feature with commercial consequences. Because Article 30(5) refers to "an enterprise or an organisation employing fewer than 1000 persons" and not to the small mid-cap definition, turnover is irrelevant for this derogation. High-revenue, low-headcount companies, a profile found in software and ad tech, sit inside the line even when they are far too large to count as small mid-caps under the rest of the regulation.
What happens next
According to Parliament's procedure file, the indicative plenary date is November 23, 2026. If Parliament adopts Amendment 44, the Council still has to approve Parliament's position, as the footnote on the document's second page anticipates. Under Article 8 of the agreed text, the regulation "shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union" and is directly applicable in the Member States. The agreed text sets no later application date for the GDPR changes; the only later date in the text is August 18, 2028, for the first battery due diligence report under the revised rule.
The documents do not include an estimate of how many organisations would gain the exemption, and they do not say how employees are counted for Article 30(5), for example whether staff of linked companies in a group are included; the calculation rules referred to in the text apply to the small mid-cap definition. They also contain no transitional arrangement for records organisations already hold, and neither document confirms the day of the vote within the session.
Key facts
- Act: Regulation (EU) 2026/... amending Regulations (EU) 2016/679, (EU) 2016/1036, (EU) 2016/1037, (EU) 2017/1129, (EU) 2023/1542 and (EU) 2024/573 as regards the extension of certain mitigating measures available for small and medium-sized enterprises to small mid-cap enterprises and further simplification measures (Omnibus IV)
- Procedure: 2025/0130(COD); Commission proposal COM(2025)0501, C10-0092/2025, published May 21, 2025
- Report: A10-0041/2026, rapporteurs Mariateresa Vivaldini (ECR, ECON), Niels Flemming Hansen (EPP, ENVI) and Lukas Mandl (EPP, LIBE); adopted in committee February 25, 2026; tabled March 3, 2026
- Documents: P10_A(2026)0041 amendments 001-043 (30 pages, PE788.402) and Amendment 44 (39 pages, PE788.402v01-00), both dated November 18, 2026
- Amendment 44 tabled by: Aurore Lalucq (ECON), Pierfrancesco Maran (ENVI) and Javier Zarzalejos (LIBE), on behalf of the committees
- Provisional agreement: June 9, 2026; approved in committee July 2, 2026
- Indicative plenary date: November 23, 2026 (Strasbourg)
- New GDPR threshold: Article 30(5), fewer than 1,000 persons (currently 250; Commission proposed 750)
- Small mid-cap definition: not an SME, fewer than 1,000 persons, turnover up to EUR 200 million or balance sheet up to EUR 172 million, per Commission Recommendation (EU) 2025/1099
- EDPB-EDPS joint opinion: July 8, 2025
- Entry into force: twentieth day after publication in the Official Journal
- Review: Commission report within five years of entry into force (Article 7)
- Legal bases: Articles 16, 114, 192(1) and 207(2) TFEU
Timeline
- May 25, 2018 - The GDPR begins to apply, with a 250-employee threshold in Article 30(5)
- May 21, 2025 - The Commission publishes the Omnibus IV proposal, COM(2025)0501, setting the Article 30 line at 750 employees
- July 8, 2025 - The EDPB and EDPS adopt a joint opinion backing simpler record-keeping
- July 23, 2025 - CNIL publishes a study finding 36% of data protection officers work in small companies
- November 2025 - Germany argues the Omnibus IV GDPR changes fall short
- November 2025 - A draft of the Commission's Digital Omnibus targets the personal data definition and access rights
- February 10, 2026 - EDPB and EDPS reject the Digital Omnibus narrowing of GDPR protections
- February 25, 2026 - Parliament's ECON, ENVI and LIBE committees adopt report A10-0041/2026 and open negotiations
- March 3, 2026 - Report A10-0041/2026 tabled for plenary
- March 5, 2026 - noyb survey finds Article 30 records top the list of GDPR workload
- March 11, 2026 - Plenary confirms the decision to enter interinstitutional negotiations
- June 9, 2026 - Parliament and Council negotiators reach a provisional agreement
- July 2, 2026 - Committees approve the agreed text
- September 2026 - Saxony-Anhalt's deletion guide for small businesses builds on the Article 30 record
- October 12, 2026 - noyb counts 248 EPP Digital Omnibus amendments it rates as weakening privacy
- October 21, 2026 - The Council agrees its Digital Omnibus mandate, including EU-wide impact assessment lists
- November 18, 2026 - Parliament publishes amendments 001-043 and Amendment 44 to report A10-0041/2026
- November 21, 2026 - Luis Alberto Montezuma posts that the next step is for Parliament to approve the final text
- November 23, 2026 - Indicative plenary date in Strasbourg
Related PPC Land coverage
- GDPR relaxes record-keeping for companies under 750 employees - The July 2025 report on the EDPB-EDPS opinion on the Commission's original Omnibus IV proposal.
- GDPR pros want less paperwork, not fewer rights - noyb survey - A survey of 510 data protection professionals that ranked Article 30 records as the heaviest GDPR task.
- Germany pushes for sweeping data protection simplification beyond EU proposal - Germany's submission calling for GDPR changes beyond Omnibus IV.
- Saxony-Anhalt regulator says recycle bin does not count as GDPR deletion - A state regulator's small-business guide that starts from the Article 30 record.
- EU Council agrees 4-month cookie re-ask wait for Digital Omnibus talks - The Council's Digital Omnibus mandate, including EU-wide lists for impact assessments.
- EPP tabled 248 omnibus amendments weakening privacy, noyb finds - noyb's ranking of Parliament amendments to the Digital Omnibus.
- Europe's privacy watchdogs reject Commission's plan to narrow GDPR protections - The EDPB and EDPS opinion on the Digital Omnibus.
- European Commission proposes major GDPR changes for AI and data processing - The November 2025 draft of the Digital Omnibus GDPR amendments.
- CNIL study reveals economic benefits of data protection officers in companies - CNIL's study of 3,625 data protection officers.
Summary
Who: The European Parliament, through its Economic and Monetary Affairs, Environment and Civil Liberties committees and rapporteurs Mariateresa Vivaldini, Niels Flemming Hansen and Lukas Mandl, together with the Council and the Commission; affected are companies and organisations with fewer than 1,000 employees, including agencies, publishers, retailers and ad tech firms.
What: Amendment 44 to report A10-0041/2026, the agreed Omnibus IV text, rewrites GDPR Article 30(5) so that organisations with fewer than 1,000 employees need not keep records of processing activities, except for specific activities likely to result in a high risk or core activities involving large-scale monitoring or large-scale processing of special categories of data. It also defines small mid-cap enterprises and changes five other EU regulations.
When: The documents are dated November 18, 2026; the provisional agreement dates from June 9, 2026; the indicative plenary date is November 23, 2026; the regulation would enter into force 20 days after publication in the Official Journal.
Where: The European Union, with the plenary vote indicated for Strasbourg; the regulation would apply directly in all Member States, and the text is marked as having EEA relevance.
Why: The Commission and co-legislators aim to reduce administrative burden by at least 25% for all enterprises and 35% for SMEs, and to soften the "cliff effect" companies face when they outgrow the SME definition, while keeping records for processing that carries structural or recurring risks.
Discussion