EU AI Act's GPAI Rules Are Now Enforceable: What Changed on August 2, 2026 (And What Your Team Missed)

For twelve months, Brussels asked nicely. As of August 2, 2026, it doesn't have to anymore.

If your compliance team spent the summer congratulating itself on a "quiet" AI Act rollout, it's time for an uncomfortable conversation. The obligations for general-purpose AI (GPAI) providers didn't just appear this month — they've technically applied since August 2, 2025. What changed on August 2, 2026 is that the European Commission's AI Office can finally do something about non-compliance: audit models, demand corrective action, restrict market access, and issue fines of up to €15 million or 3% of global annual turnover, whichever is higher.

That distinction — obligation versus enforcement — is exactly what most European boardrooms missed while they were busy tracking the wrong deadline.

The Grace Period Is Over

When the EU AI Act entered into force in August 2024, it built in a deliberate one-year runway for GPAI providers. Chapter V obligations — training-data summaries, copyright compliance, technical documentation, and systemic-risk management for the most powerful models — became legally binding on August 2, 2025. But the AI Office needed time to build its own supervisory machinery before it could act on any of it.

That runway has now ended. From August 2, 2026, the Commission can request technical documentation, run model evaluations, order risk-mitigation measures, and pull non-compliant GPAI models from the EU market. Models placed on the market before August 2, 2025 get a slightly longer runway — they must be fully compliant by August 2, 2027 — but every model launched after that date has already been operating on borrowed time.

Signing the voluntary GPAI Code of Practice helps, but it isn't a shield. Regulators have indicated that Code signatories will have their good-faith commitments weighed when calculating penalties, yet enforcement applies "signatures or not." A partial signature — committing to some chapters of the Code while skipping others — is a detail worth scrutinising in any vendor's compliance claims, not taking at face value.

Article 50 Is the Deadline Everyone Underestimated

While GPAI enforcement grabbed the headlines, Article 50 transparency obligations quietly went live the same day — and this one reaches far beyond model providers. Any organisation deploying a chatbot or conversational AI system must now disclose, clearly and at the start of the interaction, that the user is talking to an AI. AI-generated or manipulated content, including deepfakes, requires machine-readable labelling. The same €15 million / 3% turnover penalty ceiling applies here too.

This is the requirement that catches European businesses off guard, because it isn't aimed at Silicon Valley labs — it's aimed at every customer service bot, marketing assistant, and generative content workflow running inside ordinary companies across Germany, France, Ireland, and the Netherlands. If your team's AI inventory doesn't already flag which systems talk directly to customers, that's the gap to close first.

Don't Confuse This With the Digital Omnibus Delay

Here's where a lot of internal risk registers went wrong this year. The Digital Omnibus, finalised by the European Parliament on June 16, 2026 and given final Council sign-off on June 29, 2026, pushed high-risk AI system obligations under Annex III from August 2026 out to December 2, 2027. That's a genuine, significant delay — but it applies to a completely different track of the Act.

It does nothing to soften GPAI enforcement powers or Article 50 disclosure duties. If your compliance roadmap assumed the Omnibus bought extra breathing room on chatbot transparency, it was working from an outdated script. Two separate clocks, two separate consequences — and conflating them is precisely how well-resourced teams end up caught flat-footed on the deadline that actually mattered.

What Your Team Likely Missed

1. Treating "GPAI obligations" and "GPAI enforcement" as the same milestone. They weren't. The rules existed for a year with no teeth; now they have teeth.
2. Assuming the Omnibus delay covered everything. It covered high-risk systems only — not GPAI supervision, not Article 50.
3. Ignoring deployer-side exposure. Being a "deployer" rather than a "provider" doesn't create a safe harbour under Article 50. Disclosure duties reach anyone whose customers interact with AI.
4. No live AI inventory. Regulators, national market surveillance authorities, and even downstream providers can now trigger scrutiny. Without a current inventory of AI systems, owners, and purposes, an inquiry response starts from zero.
5. Reading "Code of Practice signatory" as full compliance. It's a mitigating factor in penalty calculation, not an exemption.

What To Do Before the Next Inquiry Lands

European organisations — not just AI labs — now sit inside an active enforcement regime. Practical next steps look less like a policy rewrite and more like an operational audit: build (or refresh) a complete AI systems inventory, classify which tools are GPAI-adjacent versus deployer-only, confirm chatbot disclosure is actually implemented at the interaction level, and stress-test whether your documentation would survive a Commission request this quarter.

VISTA InfoSec's own EU AI Act compliance checklist is a useful starting point for scoping classification and Annex IV documentation gaps, and their breakdown of 10 controls every organisation should implement in 2026 maps well against exactly the gaps regulators are now empowered to act on. For organisations that haven't yet run a structured gap assessment, VISTA InfoSec's practitioner-led AI governance assessments are built around operational audit experience rather than template-driven paperwork — a meaningful difference now that "we have a policy" is no longer enough to satisfy an AI Office inquiry.

The Bottom Line

August 2, 2026 didn't introduce new rules. It introduced consequences. For European businesses running customer-facing AI, procuring GPAI models, or quietly letting departments adopt generative tools without central oversight, the honest question isn't "are we compliant on paper" — it's "could we produce evidence of compliance inside a week if the AI Office asked." If the answer is uncertain, the runway to find out just got a great deal shorter.