EU AI Act Harmonised Standards: The Decision 2026/2274 Guide
What you need to know: EU AI Act Harmonised Standards: The Decision 2026/2274 Guide
Commission Decision 2026/2274 establishes official harmonised standards for high-risk AI. Learn how European SMEs use Article 40 presumption of conformity.
EU AI Act Harmonised Standards: The Decision 2026/2274 Guide
Commission Implementing Decision (EU) 2026/2274 establishes official harmonised European standards for high-risk AI systems under Regulation (EU) 2024/1689. By adhering to these published CEN-CENELEC standards, European SMEs earn a legal presumption of conformity under Article 40, streamlining CE marking, cutting auditing costs, and shielding against statutory penalties.
Who is actually in scope?
Scope covers any European organisation developing or deploying AI systems categorized as high-risk under Annex III of the EU AI Act. This includes software used in recruitment and CV filtering, employee evaluation, credit scoring, biometric identification, and critical business infrastructure.
If your startup sells B2B software that evaluates job candidates, your product is a high-risk AI system under Annex III, Point 4. Under Article 16, providers must complete a conformity assessment before placing systems on the EU market. Small teams building these tools often lack in-house legal departments. For them, Decision 2026/2274 provides the technical playbook they need.
How does presumption of conformity work under Article 40?
Article 40 of Regulation (EU) 2024/1689 contains a powerful legal mechanism: the presumption of conformity. If your engineering team builds a high-risk AI system in accordance with harmonised standards cited in the Official Journal, regulators must presume your system meets the corresponding essential requirements in Articles 8 through 15.
Implementing Decision (EU) 2026/2274 lists these recognised CEN-CENELEC standards. They address risk management systems, training dataset governance, technical documentation, automatic event logging, transparency, and human oversight. Instead of proving compliance from scratch to a notified body or national market authority, your team points directly to standard-compliant design choices. It cuts audit cycles from months to days.
What documentation is required for Annex IV technical files?
To claim presumption of conformity, founders must assemble a structured Annex IV technical dossier before market launch. Regulators will demand:
- A risk management file detailing identified risks and mitigation measures across the AI lifecycle.
- Data governance records proving training, validation, and testing datasets meet quality benchmarks and bias checks.
- Continuous technical specifications, system architecture diagrams, and algorithmic design rationale.
- Automated event-logging logs showing runtime operational parameters and traceability.
- Clear user instructions detailing performance limits, intended purpose, and human oversight controls.
EuroComply generates source-linked compliance readiness outputs and structured evidence packs so SMEs can organize these Annex IV files systematically.
What are the penalties for non-compliance?
Ignoring high-risk AI obligations carries heavy statutory liabilities under Article 99 of Regulation (EU) 2024/1689. Non-compliance with essential requirements under Articles 8 to 15 triggers fines up to €15,000,000 or 3% of worldwide annual turnover for large enterprises.
European lawmakers built an explicit financial safeguard for startups: under Article 99(6), penalties for SMEs and startups are capped at whichever amount is lower between the fixed sum and the turnover percentage. However, national regulators can also order market withdrawal, model deletion, or immediate commercial bans. For early-stage companies, losing market access is far deadlier than the fine itself.
What should SMEs do first?
Building a compliant AI system does not require halting development. Take these four practical steps:
- Run your models through our High-Risk AI Classifier to determine if your product falls under Annex III classification.
- Cross-reference your feature pipeline against the harmonised standards in Decision (EU) 2026/2274 to identify technical gaps in logging, oversight, or bias testing.
- Establish continuous logging and assemble your initial Annex IV technical file before deploying updates.
- Prepare review-ready evidence packs and have them reviewed by qualified legal counsel prior to formal CE marking declaration.
Disclaimer: EuroComply provides compliance readiness tools and evidence drafts. This guide is for informational purposes and does not constitute legal, regulatory, or compliance advice. Have technical documentation and assessments reviewed by qualified counsel.
Key takeaways: EU AI Act Harmonised Standards: The Decision 2026/2274 Guide
This article covers: Who is actually in scope?, How does presumption of conformity work under Article 40?, What documentation is required for Annex IV technical files?.
- Who is actually in scope?
- How does presumption of conformity work under Article 40?
- What documentation is required for Annex IV technical files?
- What are the penalties for non-compliance?
- What should SMEs do first?
EuroComply Editorial Team
EU regulatory compliance specialists covering the AI Act, GDPR, NIS2, and related legislation. Content reviewed against official EU regulation texts and enforcement guidance.
For informational purposes only. Consult qualified legal counsel.
Get the weekly EU compliance briefing — 2 minutes, every Thursday.
Related Regulation
EU AI Act
Official EuroComply guide to EU AI Act