Art.83

Article 83 – Formal Non-Compliance

High-Risk Systems SME Relevant ~2 min read · 486 words

Article 83 deals with formal or procedural non-compliance — situations where an AI system may or may not be safe, but the provider has failed to meet specific administrative and documentation obligations. Missing CE marking, incorrect EU declarations of conformity, absent technical documentation, failure to register, or no authorised representative: these are the formal violations Article 83 addresses.

! High compliance impact for SMEs

WHAT THE ARTICLE IS ABOUT

Enforcement for procedural and documentation failures

Article 83 establishes the procedure market surveillance authorities follow when they identify formal compliance failures — not necessarily substantive safety or rights violations, but failures to meet the Act’s administrative requirements. It is the counterpart to Article 79 (which addresses substantive risks) and Article 82 (which addresses compliant but risky systems).

WHAT IT SAYS

Specific formal violations trigger corrective demands and then market measures

Authorities must require operators to correct formal non-compliance in the following specific situations: the CE marking has been affixed in violation of Article 48; no CE marking has been affixed where required; the EU declaration of conformity has not been drawn up or has been drawn up incorrectly; the EU declaration of conformity has not been registered in the EU database; the technical documentation is not available or not complete; the provider has not appointed an authorised representative where required
Where any of the above applies, the authority requires the operator to correct the non-compliance within a specified timeframe
If the operator fails to comply, the authority may take any appropriate measure to restrict, prohibit or recall the AI system from the market
The authority must notify the Commission and other member states where measures are taken
The Union Safeguard Procedure under Article 81 may be triggered where other member states object

WHO IS AFFECTED

All providers of high-risk AI systems with formal compliance obligations

Providers who have failed to affix CE marking or done so incorrectly
Providers who have not drawn up or incorrectly completed their EU declaration of conformity
Providers who have not registered in the EU database under Article 49
Non-EU providers who have not appointed an authorised representative under Article 22
Providers whose technical documentation is incomplete or unavailable

WHAT IT MEANS FOR SMES

The most common enforcement trigger — fix these before launch

Article 83 violations are the most likely first enforcement encounter for SMEs — they are the procedural failures that market surveillance authorities can identify quickly without deep technical assessment
The list of formal violations in this article is essentially your pre-launch compliance checklist: CE marking affixed correctly, EU declaration of conformity complete and signed, EU database registration done, authorised representative appointed if needed, technical documentation available
Unlike substantive risk violations which require technical evaluation, formal violations are immediately visible — an authority can identify a missing CE mark or absent EU database registration with minimal investigation
The corrective action deadline is set by the authority — unlike Article 79’s 15-working-day default, Article 83 gives the authority discretion on the timeframe; engage promptly when notified
Fixing formal non-compliance is generally straightforward — the obligations are clear and the corrective actions are well-defined; use this article as your final pre-market checklist

Article 48 — CE marking (the first formal obligation whose violation triggers this article)
Article 47 — EU declaration of conformity (the second formal obligation)
Article 49 — Registration (the EU database registration obligation)
Article 22 — Authorised representatives (the representative obligation for non-EU providers)

← Back to the Guide