Article 83 of Regulation (EU) 2024/1689 — Formal non-compliance. Official text, practical interpretation, key obligations and compliance implications.
Article 83 is the paperwork enforcement clause: even when nothing dangerous is proven, missing CE marking, absent registration or an unavailable technical file must be corrected — and persistence turns it into a market restriction case.
Official Text Summary
Without prejudice to Article 79, a market surveillance authority requires the relevant provider to end, within a period it may prescribe, any of the following formal non-compliances: the CE marking has been affixed in violation of Article 48 or has not been affixed; the EU declaration of conformity has not been drawn up or has been drawn up incorrectly; the registration in the EU database has not been carried out; an authorised representative has not been appointed where required; or the technical documentation is not available. Where the non-compliance persists, the Member State concerned takes appropriate and proportionate measures to restrict or prohibit the high-risk AI system from being made available on the market, or to ensure that it is recalled or withdrawn without delay.
Key Obligations
- Covers defects such as CE marking affixed in violation of Article 48 or not affixed, missing EU declaration of conformity, missing registration in the EU database, no authorised representative, or technical documentation unavailable
- The market surveillance authority requires the provider to end the non-compliance within a period it prescribes
- If the non-compliance persists, the Member State takes appropriate and proportionate measures to restrict or prohibit the system, or ensure its recall or withdrawal
Compliance Timeline
Applies from 2 August 2026; the 2026 Digital Omnibus deferred the substantive high-risk obligations (Annex III to 2 December 2027, Annex I to 2 August 2028) but did not move this provision.
Official AI Act Compliance Deadline Calendar
Updated · Sources: Regulation (EU) 2024/1689 and the 2026 Digital Omnibus on AI.
| Obligation | Applies to | Original date | New date | Status | Countdown | Legal basis |
|---|---|---|---|---|---|---|
| Prohibited Practices (Art. 5) | All providers and deployers | active | — | AI Act Art. 5 | ||
| GPAI Rules (Chapter 5) | GPAI model providers | active | — | AI Act Art. 51-56 | ||
| Commission Enforcement Powers over GPAI | GPAI model providers | active | — | AI Act Art. 88-94, 101 | ||
| Transparency Obligations (Art. 50) | Providers and deployers of chatbots, generative, emotion recognition systems | active | — | AI Act Art. 50 | ||
| New Art. 5 Prohibition (CSAM / non-consensual intimate imagery) | Providers and deployers of generative AI systems | active | — | AI Omnibus 2026 Art. 5 | ||
| AI-Generated Content Marking (pre-existing systems) | Providers of generative AI systems on the market before 2 Aug 2026 | active | — | AI Act Art. 50(2) — transitional | ||
| Regulatory Sandboxes | National competent authorities | deferred | — | AI Omnibus 2026 Art. 57 | ||
| High-risk AI — Annex III (standalone) | Providers of standalone Annex III systems | deferred | — | AI Omnibus 2026 Art. 6(2) | ||
| High-risk AI — Annex I (embedded) | AI embedded in Annex I regulated products | deferred | — | AI Omnibus 2026 Art. 6(1) |
⬇ Download JSON · CC BY 4.0
AI Act meets DORA and NIS2
Is your organisation subject to both the AI Act and DORA? The two regulations intersect on the operational resilience of financial AI systems. Our sister site regulation-dora.eu covers DORA in depth — including what the AI Act adds on top of an existing DORA programme.
The AI Act for financial institutions ↗ Explore regulation-dora.eu ↗Frequently Asked Questions
Because the paperwork is the enforcement infrastructure. CE marking, the declaration, registration and the technical file are what allow authorities, deployers and the public to verify anything at all — a system without them is unauditable, whatever its actual quality.
Article 79 addresses systems presenting a risk; Article 82 addresses compliant systems that still present a risk; Article 83 addresses formal defects with no proven risk. The escalation path is the same — correction first, market restriction if the operator does not act.
Stay ahead of AI Act changes
Get compliance alerts when deadlines or obligations change.
No spam. One-click unsubscribe.
Take compliance further with the AI Act Academy
Templates, training modules, and live Q&A — everything needed to implement AI Act compliance.