7 min read<\/p>\n
As of: 22 April 2026<\/span><\/p>\n In April 2026, the European Parliament adopted its negotiating position on the Digital Omnibus, and trilogue talks with the Council and Commission have been underway since this week. The Cypriot Presidency of the Council aims to reach a final agreement by May. For Germany\u2019s SME sector, this means a package is now on the table that promises to cut red tape by 25 to 35 percent, with estimated savings of six billion euros by 2029, and deferred compliance deadlines for the EU AI Act. Three key questions will determine whether the package truly eases the burden for your business\u2014or simply shifts bureaucracy elsewhere.<\/strong><\/p>\n Related<\/span>EU AI Act from August: What tech teams need to clarify<\/a> \/<\/span> CSRD Omnibus for SMEs<\/a><\/p>\n What is the Digital Omnibus?<\/strong> The Digital Omnibus is an EU omnibus law that streamlines multiple digital regulations at once to cut red tape. The current package includes amendments to the AI Act, the Digital Services Act (DSA), the Data Act, and related regulations. The initiative was sparked by the Draghi Report, which identified Europe\u2019s regulatory density as a barrier to innovation. It also responds to the political mandate to measurably ease the burden on European competitiveness.<\/p>\n For Germany\u2019s SMEs, this isn\u2019t some abstract Brussels debate\u2014it\u2019s a very real lever. Compliance costs for the EU AI Act are estimated at up to 600,000 Euro in one-off expenses, plus ongoing costs, for mid-sized companies using AI systems in the medium-high risk category. If you\u2019re running a dozen AI use cases\u2014think chatbots, content generators, or recommendation engines\u2014you\u2019re quickly looking at six-figure annual costs just for documentation, audits, and risk management. That\u2019s exactly where the Omnibus aims to ease the pressure.<\/p>\n The key players are the European Commission under Ursula von der Leyen, Cyprus\u2019s Council Presidency, and a cross-party majority in Parliament. Opposition comes, predictably, from digital rights and consumer protection groups, who see excessive deregulation as a watering-down of the AI Act and DSA. The Trilogue compromise won\u2019t deliver everything industry associations are demanding, but substantial relief is on the table.<\/p>\n Source: European Commission, Impact Assessment Digital Omnibus, March 2026<\/p>\n Three core adjustments will directly impact SME tech teams. First, the AI Act: For existing AI systems deployed before 2 August 2026, high-risk obligations will be phased in gradually instead of all kicking in on the deadline. That gives teams breathing room if they\u2019re still knee-deep in risk classification and documentation come spring 2026. Second, DSA reporting: Online services below a certain threshold will see simplified, harmonised annual transparency reports. Third, watermarking for AI-generated content: Requirements will be streamlined and focused on clearly identifiable use cases.<\/p>\n For Germany\u2019s SMEs, the AI Act relief is the headline change. If you\u2019re running an existing customer-service chatbot, an e-commerce recommendation engine, or an AI-powered HR tool, you\u2019ve had just three months to achieve full compliance\u2014until now. The Omnibus stretches that timeline into phased deadlines up to 2027 or 2028, depending on the risk class. It\u2019s not a free pass, but it\u2019s a realistic schedule.<\/p>\n At the same time, the AI Act\u2019s core requirements remain intact. High-risk systems in sensitive areas like hiring, credit scoring, or law enforcement still demand full conformity assessments, transparency documentation, and human oversight. If you\u2019re operating such a use case and think the Omnibus lets you off the hook, you\u2019ve misunderstood the package.<\/p>\n The timeline is ambitious. If trilogue talks drag on or individual member states raise objections, agreement could slip into the second half of the year. For SME teams, this means: don\u2019t wait for the Omnibus, but keep your implementation plan flexible.<\/p>\n First: Which in-house AI use cases are potentially high-risk?<\/strong> If you haven\u2019t inventoried these, you have a gap that must be closed regardless of the Omnibus. Classifying according to the AI Act\u2019s risk categories is mandatory work that can\u2019t be postponed\u2014high-risk obligations will remain in place even with the Omnibus.<\/p>\n Second: Where can I rely on Omnibus relief?<\/strong> For systems below the high-risk threshold and existing AI applications, the new deadlines are realistically manageable once the final text is set. If you\u2019re already preparing documentation, nothing is wasted\u2014the core structure will still be required under the Omnibus.<\/p>\n Third: What costs can I realistically save?<\/strong> The Commission\u2019s \u20ac600,000 estimate won\u2019t apply to every company. If you have just two or three medium-risk use cases, you\u2019re looking at a five-figure sum. With ten or more use cases and your own ML platform, costs easily reach six figures. An honest inventory reveals where the real expenses lie.<\/p>\n The pragmatic take from a business perspective: The Digital Omnibus is a step in the right direction, but not a free pass. AI regulation is coming\u2014and it\u2019s coming hard. The Omnibus buys time, provides breathing room, and introduces more nuanced thresholds. But it doesn\u2019t replace the internal homework. Companies that start building clean AI governance, documenting data classes, and classifying their use cases now will benefit regardless of the final Omnibus text.<\/p>\n Those who wait for the Omnibus and push their own classification to autumn risk losing three to four months\u2014time that could become critically tight under legal pressure. The honest answer to management is: build structure, stay flexible, don\u2019t speculate. Do this now, and you\u2019ll be on the safe side come 2 August 2026, no matter how the trilogue plays out.<\/p>\n The April 2026 Digital Omnibus trilogue presents a real opportunity for Germany\u2019s SME sector to cut compliance costs on a meaningful scale. But let\u2019s keep a level head. High-risk AI will remain strictly regulated, and classifying your own systems is non-negotiable. Implementation takes time. If you wait until May to read the final text and only then start structuring your approach, you\u2019ll lose the entire summer. Start your inventory now, and you\u2019ll have room to manoeuvre by August.<\/p>\n Not yet. Parliament adopted its position in April 2026, trilogue negotiations with the Commission and Council are underway, and a deal is targeted for May 2026. The official text may still change in the fine print.<\/p>\n<\/details>\n Hardly at all. If you don\u2019t operate AI systems or a significant online platform, you won\u2019t be impacted by the AI Act or DSA components of the Omnibus. However, indirect adjustments under the Data Act and other regulations may still apply.<\/p>\n<\/details>\n Keep going. Classifying your AI use cases, auditing your data flows, and building a governance framework are mandatory regardless of the Omnibus. Only the final deadlines for full implementation may shift.<\/p>\n<\/details>\n The core risk classification remains intact. Changes primarily affect transition periods for existing systems and the specifics of watermarking and transparency requirements. High-risk categories like recruitment or credit scoring will stay fully regulated.<\/p>\n<\/details>\n Bitkom, BDI, and DIHK publish trilogue updates, the Commission\u2019s Directorate-General for Connect provides direct briefings, and law firms with Brussels offices offer client updates. Subscribing to two or three trusted sources is enough to track the negotiation status.<\/p>\n<\/details>\n Editor\u2019s Picks<\/p>\n Source: Pexels \/ Petrit Nikolli (px:22046935)<\/p>\n","protected":false},"excerpt":{"rendered":" Parliamentary position set, trilog underway. \u20ac6\u202fbn relief and new AI\u2011Act deadlines for SMEs. What\u2019s important by May.<\/p>\n","protected":false},"author":205,"featured_media":97583,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"Digital Omnibus Mittelstand 2026","_yoast_wpseo_title":"EU Digital Omnibus in Trilogue: What German SMEs Need to Know Now","_yoast_wpseo_metadesc":"Parliament adopts digital omnibus position, trilogue underway: \u20ac6bn relief, new AI Act deadlines for SMEs. What to do now.","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"featured_post_sortierung":0,"featured_post":0,"pre_headline":"","bildquelle":"","teasertext":"","language":"de","_evm_translation_lang":"","_wp_old_slug":[],"footnotes":""},"categories":[1152],"tags":[],"class_list":["post-97717","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-it-tech","entry"],"evm_reading_time_minutes":9,"wpml_language":"en","wpml_translation_of":97584,"acf":[],"yoast_head":"\nKey takeaways<\/h2>\n
\n
What the Digital Omnibus is\u2014and who\u2019s driving it<\/h2>\n
What\u2019s set to change in practice<\/h2>\n
Timeline to Agreement<\/h2>\n
Three Questions That Need Answers Now<\/h2>\n
What Remains for SMEs<\/h2>\n
Conclusion<\/h2>\n
Frequently Asked Questions<\/h2>\n
Has the Digital Omnibus been finalised yet?<\/strong><\/summary>\n
Does the Omnibus affect small businesses that don\u2019t use AI?<\/strong><\/summary>\n
Should we pause our AI Act compliance project or keep going?<\/strong><\/summary>\n
Does the Omnibus change the high-risk classification for certain systems?<\/strong><\/summary>\n
How can I stay updated without reading every Brussels document myself?<\/strong><\/summary>\n
\n