Many small companies assume the AI Act is lighter for them. That is partly true. The Act contains a set of measures for micro, small and medium-sized enterprises (SMEs) and, since the summer of 2026, for small mid-cap enterprises (SMCs) as well. But nowhere does it say that a small company may skip a rule. Article 62 and Article 63 are the core: the first says what Member States, the AI Office and notified bodies must do for small players, the second gives one simplification for the quality management system.
Suppose it is November 2026. A Dutch municipality wants to buy software that ranks applications for social assistance by urgency. The supplier is a software company with 22 employees. May that supplier do less than a large company? And does that change anything for the municipality? Then the same question for a bank buying from a fast-growing company with 400 employees. The examples are invented.
In short
Article 62 is addressed to the Member States and the AI Office and, in paragraph 2, to whoever sets conformity assessment fees, in practice the notified bodies. It gives small companies support, not duties. Member States give SMEs priority access to the AI regulatory sandbox, organise awareness raising and training, keep a channel open for questions and help SMEs take part in standardisation (paragraph 1). Conformity assessment fees charged by a notified body are reduced proportionately for SMEs (paragraph 2). The AI Office provides templates, a single information platform and communication campaigns (paragraph 3). The Digital Omnibus on AI (Regulation (EU) 2026/1744) did not amend Article 62. It has applied since 2 August 2026 (Article 113).
Article 63 lets SMEs comply in a simplified manner with certain elements of the quality management system of Article 17, provided that they do not have partner enterprises or linked enterprises. Until the Omnibus this applied to microenterprises only. Which elements may be simplified has to follow from Commission guidelines. On 19 November 2026 these have not yet been published.
Neither article exempts anyone. Article 63(2) says so in terms. The risk class of an AI system depends on what the system does, not on the size of the company.
Small mid-cap enterprises, companies above the SME ceiling with fewer than 750 persons employed, have appeared in a number of other articles since the Omnibus (including Articles 11, 17 and 99), but not in Articles 62 and 63.
This piece is about the support measures themselves. What a quality management system involves is set out in the quality management system of Article 17, and the sandbox in the Dutch AI regulatory sandbox.
Who is an SME, and who a small mid-cap enterprise?
Since the Omnibus both terms are defined in Article 3. An SME is a micro, small or medium-sized enterprise as defined in Article 2 of the Annex to Recommendation 2003/361/EC (Article 3, point (14a)). An SMC is a small mid-cap enterprise as defined in point (2) of the Annex to Recommendation (EU) 2025/1099 (Article 3, point (14b)).
| Type of enterprise | Persons employed | Financial ceiling |
|---|---|---|
| Microenterprise | fewer than 10 | annual turnover or balance sheet total of at most EUR 2 million |
| Small enterprise | fewer than 50 | annual turnover or balance sheet total of at most EUR 10 million |
| SME (upper limit) | fewer than 250 | annual turnover of at most EUR 50 million or balance sheet total of at most EUR 43 million |
| Small mid-cap enterprise | not an SME and fewer than 750 | annual turnover of at most EUR 150 million or balance sheet total of at most EUR 129 million |
Persons employed are counted in annual work units: part-time work counts proportionately. The AI Act refers only to the ceilings themselves. In our reading the calculation rules in the same annexes come with them.
Three things often go wrong in practice.
First, you do not count your own company alone. If another enterprise holds 25 per cent or more of your capital or voting rights, or the other way round, the figures of that partner enterprise are added in proportion. For a linked enterprise, for example a parent holding the majority of the voting rights, the figures are added in full. A subsidiary of a large group is therefore not an SME, however small it is itself.
Second, an enterprise in which one or more public bodies jointly control 25 per cent or more of the capital or voting rights is not an SME. Both recommendations say so, with an exception for a few types of investor, including small autonomous local authorities with an annual budget of less than EUR 10 million and fewer than 5 000 inhabitants. A software company half-owned by three medium-sized municipalities therefore falls outside the SME rules of the AI Act, and outside the rules for small mid-cap enterprises too.
Third, status does not change after one good or bad year. An enterprise gains or loses the status only if it is above or below the ceilings for two consecutive accounting periods.
The word start-up has no definition of its own in the AI Act. The Act almost always names start-ups as part of the SMEs ("SMEs, including start-ups"). In our reading a start-up therefore gets the benefits only if it also meets the SME definition.
Article 62(1): what the Member State must do
Paragraph 1 gives the Member States four tasks.
Priority access to the sandbox. SMEs having a registered office or a branch in the Union get priority access to the AI regulatory sandboxes, to the extent that they fulfil the eligibility conditions and selection criteria. Priority is not a guaranteed place, and the sandbox is open to any provider or prospective provider that fulfils the eligibility and selection criteria (Article 58(2), point (a); recital 143). The Commission's implementing rules must ensure that access is free of charge for SMEs, without prejudice to exceptional costs that the authority may recover in a fair and proportionate manner (Article 58(2), point (d)). Each Member State must have a sandbox operational by 2 August 2027 (Article 57(1)).
Awareness raising and training. Member States organise awareness raising and training activities on the application of the AI Act, tailored to the needs of SMEs, deployers and, as appropriate, local public authorities.
A channel for questions. Member States use existing dedicated channels, and where appropriate set up new ones, to provide advice and respond to queries about the implementation of the AI Act. Here too the Act names deployers, other innovators and local public authorities next to SMEs.
Taking part in standardisation. Member States facilitate the participation of SMEs and other relevant stakeholders in the standardisation development process.
Two caveats. The task is addressed to the Member State. Article 62 does not say which organisation in the Netherlands does this, and it gives a company no time limit within which it must receive an answer. And the priority access of paragraph 1 is for SMEs. Small mid-cap enterprises are not mentioned there. They do get priority access to a sandbox at Union level, if the AI Office sets one up. That sandbox only covers systems supervised by the AI Office itself: systems based on a general-purpose AI model of the same provider or the same undertaking, and systems that constitute or are integrated into a very large online platform or very large online search engine (Article 57(3a) read with Article 75(1)).
For municipalities paragraph 1 matters more than the title suggests. A municipality is not an SME, but it is a local public authority and usually a deployer. The awareness raising and the channel for questions are therefore meant for it as well. In addition, national competent authorities may provide guidance and advice on the implementation of the AI Act, in particular to SMEs and SMCs (Article 70(8)). That is a power, not a duty.
Article 62(2): lower fees for the assessment
When setting the fees for conformity assessment under Article 43, the specific interests and needs of SME providers are taken into account. The fees are reduced proportionately to their size, market size and other relevant indicators. Recital 143 says this applies when notified bodies set conformity assessment fees. The Act names no percentage or amount.
The reach is smaller than it looks. For most Annex III systems, points 2 to 8, the provider carries out the assessment itself through internal control, without a notified body (Article 43(2)). Then there is no fee to reduce. Paragraph 2 mainly counts for biometrics (point 1 of Annex III), where an assessment by a notified body is mandatory as long as the provider has not fully applied harmonised standards or common specifications (Article 43(1)), and for Annex I products. How that choice works is explained in internal control or notified body. Apart from Article 62, notified bodies must avoid unnecessary burdens and minimise administrative burdens and compliance costs for micro- and small enterprises, without giving up rigour (Article 34(2)).
Article 62(3): what the AI Office does
The AI Office has four tasks: provide standardised templates for the areas specified by the Board in its request, develop and maintain a single information platform providing easy to use information for all operators across the Union, organise communication campaigns, and evaluate and promote the convergence of best practices in public procurement procedures in relation to AI systems.
The platform exists. The Commission calls it the AI Act Single Information Platform, with among other things an explorer of the legal text, a compliance checker and a service desk where you can ask questions. Since the Omnibus the platform has one more job: the Commission publishes practical examples there of how organisations can comply with the AI literacy obligation (Article 4(2)).
The last task, procurement, touches municipalities and other contracting authorities directly. The Act only promises that the AI Office evaluates practices and promotes convergence. No mandatory procurement model follows from it.
Article 63: the quality management system in a simplified manner
A provider of a high-risk AI system must have a quality management system (Article 17). Recital 146 calls that one of the most costly obligations. Article 63(1) therefore lets SMEs comply in a simplified manner with certain elements of that system.
There are three conditions and limits.
- Only SMEs without partner enterprises or linked enterprises within the meaning of Recommendation 2003/361/EC. An SME in which another enterprise holds 30 per cent of the shares therefore falls outside it in our reading, unless that enterprise comes under one of the exceptions in the recommendation.
- Only certain elements. Which ones has to follow from guidelines developed by the Commission. Those guidelines may not affect the level of protection. The Commission reports that the AI Office is still working on these guidelines; on 19 November 2026 they have not been published (Commission overview). The Commission speaks there of SMEs and SMCs, but Article 63 names SMEs only.
- No exemption from the rest. Paragraph 2 says that paragraph 1 exempts no one from any other requirements or obligations, including those in Articles 9, 10, 11, 12, 13, 14, 15, 72 and 73: risk management, data, technical documentation, logs, transparency, human oversight, accuracy and robustness, post-market monitoring and the reporting of serious incidents.
The Omnibus widened paragraph 1. In the original text the simplification applied to microenterprises only. According to recital 28 of the Omnibus it was extended to all SMEs to give more innovators this possibility. Small mid-cap enterprises are not covered. For them, and for SMEs that do not meet the condition, the general rule does apply that the implementation of the quality management system is proportionate to the size of the provider's organisation (Article 17(2)). The limit is stated there as well: the degree of rigour and the level of protection remain required in any event.
What else the Act holds for small providers
The main provisions at a glance. The list is not exhaustive.
| Provision | What | SME | Small mid-cap |
|---|---|---|---|
| Article 11(1) | Technical documentation in a simplified manner, using a Commission form that notified bodies must accept | yes | yes |
| Article 17(2) | Quality management system proportionate to size | yes | yes |
| Article 63 | Certain elements of the quality management system simplified | yes, without partner or linked enterprises | not mentioned |
| Article 62(1), point (a) | Priority access to the national sandbox | yes | not mentioned |
| Article 57(3a) | Priority access to an AI Office sandbox (only systems under Article 75(1)) | yes | yes |
| Article 58(2), point (d) | Access to the sandbox free of charge | yes | not mentioned |
| Article 62(2) | Lower conformity assessment fee | yes | not mentioned |
| Article 70(8) | Guidance and advice from the authority (a power) | yes | yes |
| Article 99(6) and (6a) | The lower fine cap | yes, for paragraphs 3, 4 and 5 | only for paragraphs 4 and 5 |
| Article 99(1) | Interests and economic viability taken into account when imposing penalties | yes | yes |
| Article 4(2) | Support with AI literacy | yes | not mentioned |
| Article 34(2) | Burdens of the assessment kept to a minimum | micro and small only | not mentioned |
| Article 95(4) | Attention when codes of conduct are drawn up | yes | yes |
| Article 96(1) | Particular attention in Commission guidelines | yes | yes |
The simplified technical documentation form has to come from the Commission. A company that opts for the simplified route uses that form (Article 11(1)). On 19 November 2026 the form is not in the Commission overview and is not mentioned on the home page of the information platform. We have not been able to establish whether it has been published elsewhere. More on the documentation itself is in the technical documentation of Article 11 and Annex IV.
Fines: the lower amount, but not always
Article 99 has three fine caps: EUR 35 million or 7 per cent of total worldwide annual turnover for the prohibited practices of Article 5 (paragraph 3), EUR 15 million or 3 per cent for the obligations listed in paragraph 4, and EUR 7.5 million or 1 per cent for supplying incorrect, incomplete or misleading information to an authority or notified body in reply to a request (paragraph 5). For an undertaking the higher of amount and percentage normally applies.
For SMEs this is reversed: the lower of the two applies, for all three paragraphs (paragraph 6). For small mid-cap enterprises the lower applies only for paragraphs 4 and 5 (paragraph 6a). For a prohibited practice the ordinary cap therefore applies to a small mid-cap enterprise.
A worked example for an infringement under paragraph 4. An SME with EUR 4 million turnover: the cap is 3 per cent, so EUR 120 000. A small mid-cap enterprise with EUR 120 million turnover: 3 per cent, so EUR 3.6 million. A large company with the same turnover, for example because it employs 800 persons: EUR 15 million, because then the higher applies. These are caps. When setting the fine in a specific case, Member States also take into account the interests and the economic viability of SMEs and SMCs (Article 99(1)). For public authorities each Member State decides for itself to what extent they can be fined (Article 99(8)). How that works out for municipalities is in fines under the AI Act and the GDPR for municipalities.
Main example: the municipality and the small supplier
Back to the municipality. The software ranks applications for social assistance by urgency. In our reading such a system is in principle high-risk: Annex III, point 5(a), lists systems that public authorities use to evaluate the eligibility of natural persons for essential public assistance benefits and services. Article 6(3) can provide a derogation, but not where the system performs profiling of natural persons. In our reading a system that ranks applicants on the basis of their data performs profiling as a rule. That way out then does not exist.
The supplier with 22 employees is an SME if the financial ceiling is also met and no large company or public body holds 25 per cent or more behind it. Then it may provide the technical documentation through the Commission form once that exists. If it has no partner or linked enterprises, it may also set up certain elements of the quality management system more simply. All substantive requirements stay in place: risk management, data quality, logs, instructions for use, human oversight.
For the municipality nothing changes in its own obligations. As a deployer it follows the instructions for use and organises human oversight (Article 26). As a body governed by public law it carries out a fundamental rights impact assessment (Article 27). And it registers the use in the EU database and does not use the system if the provider has not registered it (Article 49(3) and Article 26(8)). None of those obligations becomes lighter because the supplier is small.
The GDPR also keeps applying. In our reading a DPIA is almost certainly required for this system (Article 35 GDPR). The fundamental rights impact assessment may refer to that DPIA (Article 27(4)). An urgency score can itself be a decision within the meaning of Article 22 GDPR: the Court of Justice held this for a credit score on which another party draws strongly (SCHUFA, C-634/21). The municipality informs applicants that they are subject to the use of the system (Article 26(11)), and anyone who receives a decision based on the output has a right to explanation (Article 86). The limit lies in Article 5(1), point (c): a score based on social behaviour or personal characteristics that leads to detrimental treatment outside the original context, or to treatment that is unjustified or disproportionate, is prohibited.
What the municipality can do:
- Ask the supplier whether it is an SME and which simplification it relies on, and record that in the procurement file.
- Ask for the documentation it needs itself, even if the supplier uses a shorter form towards the authority. The instructions for use of Article 13 are not part of the simplification.
- Use the awareness raising and the channel for questions of Article 62(1) itself, which are also meant for local public authorities.
The high-risk obligations for Annex III systems apply from 2 December 2027. If the system was placed on the market or put into service before that date and is intended to be used by public authorities, provider and municipality must comply by 2 August 2030 at the latest, and earlier if the design is significantly changed from 2 December 2027 (Article 111(2)).
Example 2: the bank and the fast-growing company
A bank buys a credit scoring model from a company with 400 employees and EUR 60 million turnover. Evaluating the creditworthiness of natural persons is listed in Annex III, point 5(b), so the system is in principle high-risk. The exception in that point covers only the detection of financial fraud.
If the supplier has been above the SME ceiling for two consecutive accounting periods, it is no longer an SME, but if it is autonomous it is a small mid-cap enterprise. If it has only just grown past the ceiling, it still keeps its SME status. It may use the simplified technical documentation form and set up its quality management system proportionately. Article 63 does not apply to it, and for an assessment it gets no lower fee under Article 62(2). For an insurer buying a model for risk assessment and pricing in life and health insurance (Annex III, point 5(c)) it works the same way.
The bank and the insurer carry out a fundamental rights impact assessment themselves as deployers, because Article 27 expressly names points 5(b) and (c). Here too the size of the supplier makes no difference. For the credit score Article 22 GDPR applies as well: according to the Court of Justice the automated establishment of a score is already automated individual decision-making where the lender draws strongly on it (SCHUFA, C-634/21).
Example 3: the start-up with a selection tool
A start-up with eight employees builds a tool that filters job applications. That is listed in Annex III, point 4(a). With eight persons employed the start-up is a microenterprise and so an SME, if its turnover or balance sheet total also stays below EUR 2 million and it is autonomous. Once the Dutch sandbox is open, by 2 August 2027 at the latest, it can apply for a place with priority, in principle free of charge (Article 58(2), point (d)). If a prospective provider observes the plan and the terms and conditions there and follows the guidance of the authority in good faith, the authority imposes no administrative fine for infringements of the AI Act in those experiments (Article 57(12)). Liability for damage to third parties remains.
An employer that uses the tool keeps its own obligations as a deployer. It informs applicants that they are subject to the use of the system (Article 26(11)) and, if it also applies the system to its own staff, informs workers' representatives and the affected workers beforehand (Article 26(7)). If the tool infers emotions from face or voice, the prohibition on emotion recognition in the workplace comes into view (Article 5(1), point (f)). And here too Article 22 GDPR and Article 35 GDPR apply.
From when?
| Provision | Applies from |
|---|---|
| Articles 62 and 63 (Chapter VI) | 2 August 2026 |
| National sandbox operational | 2 August 2027 at the latest |
| Articles 11 and 17 for Annex III systems | 2 December 2027 |
| Articles 11 and 17 for Annex I products | 2 August 2028 |
| Article 99 (fines) | 2 August 2025; paragraph 6a since 27 July 2026 |
The Omnibus was published on 24 July 2026 and entered into force on the third day after that, 27 July 2026. In our reading the widening of Article 63 has applied since 2 August 2026, the day on which Chapter VI became applicable. In practice it only counts once Article 17 applies, because before that a quality management system is not yet mandatory.
What to do now
If you are a small provider:
- Determine the risk class of your system first. The size of your company plays no part in that.
- Establish whether you are an SME or a small mid-cap enterprise, including partner enterprises, linked enterprises and any public shareholding, and record it. Both recommendations allow a declaration by the enterprise itself.
- Do not wait for the form or the guidelines. The substantive requirements of Articles 9 to 15 do not change because of them.
- Follow the Commission's information platform and put your questions to the service desk.
- Consider the sandbox if you have a real legal question about a system under development.
If you buy from a small supplier:
- Ask about the supplier's status and the simplifications it uses.
- Arrange in the contract that you receive the documentation you need for your own obligations.
- Plan your own work independently of the supplier: oversight, registration and the fundamental rights impact assessment.
Want to know which obligations apply to your own situation? The case check lists them on the basis of your answers.
Frequently asked questions about SMEs, start-ups and the AI Act
Sources
Newsletter
Every Tuesday, the AI Act week ahead in 5 minutes
A practical briefing on deadlines, new guidance and enforcement, so you know what matters this week. No spam and you can unsubscribe in one click.
Practical and short · No spam · One-click unsubscribe