Essential Public Services AI: High-Risk Under the EU AI Act
AI deciding eligibility for public benefits — granting, reducing or revoking them — is high-risk (Annex III 5(a)). A FRIA is mandatory for deployers.
AI used by — or on behalf of — a public authority to decide who gets essential public benefits and services is high-risk under Annex III point 5(a) of the EU AI Act. That covers evaluating eligibility for benefits, and granting, reducing, revoking or reclaiming them. The obligations apply from 2 December 2027, and for a public-body deployer one of them is non-negotiable: a Fundamental Rights Impact Assessment under Article 27 must be completed before the system is used.
This page sets out what point 5(a) catches, how it relates to its siblings on credit and insurance, and what a benefits agency actually has to do.
What Annex III point 5(a) covers
Annex III point 5(a) designates as high-risk AI intended to be used by public authorities, or on their behalf, to evaluate the eligibility of natural persons for essential public assistance benefits and services — including healthcare services — and to grant, reduce, revoke, or reclaim such benefits and services.
The trigger is the function and the context: a decision about access to essential public support, made by or for a public authority. It reaches an automated means-test for unemployment or housing benefit, a system that scores welfare claims for fraud-risk-led reduction, an algorithm that prioritises social-housing waiting lists, and a tool that flags benefits to be clawed back. The "on behalf of" wording is deliberate: a private contractor running the system for the agency does not take it out of scope — it is still point 5(a) high-risk, and the public authority remains the deployer in substance.
The Article 6(3) filter is narrow here and rarely available, because these systems evaluate and influence decisions about individuals — and any system that profiles a natural person is always high-risk. Document the assessment and register under Article 49.
The siblings: 5(b) creditworthiness and 5(c) insurance
Point 5 has three limbs; keep them straight, because the FRIA rules differ.
| Annex III point | Use | Typical deployer | FRIA? |
|---|---|---|---|
| 5(a) | Eligibility for essential public benefits and services; grant/reduce/revoke/reclaim | Public authority (or its contractor) | Yes — as a public deployer |
| 5(b) | Creditworthiness / credit scoring (excluding fraud detection) | Private lender | Yes — credit is a named FRIA trigger |
| 5(c) | Risk assessment and pricing in life and health insurance | Private insurer | Yes — insurance is a named FRIA trigger |
Two things to note. Point 5(b) explicitly excludes AI used to detect financial fraud — fraud detection is not high-risk on this ground. And although 5(b) and 5(c) sit in the private sector, they are the two private-sector uses the Act singles out for a mandatory Article 27 FRIA, alongside all public deployers. So the FRIA reaches further than "public bodies only" — but it does not reach most other private deployers.
What a benefits agency must do: Article 26 plus the mandatory FRIA
A public authority running a point 5(a) system is the deployer under Article 26. It must use the system per the provider's instructions, assign competent human oversight (Article 14), monitor operation, keep the logs, and report serious incidents up the chain. The provider that built the tool — whether an in-house team or an external vendor — carries the Article 16 stack: risk management (Article 9), data governance (Article 10), technical documentation to Annex IV (Article 11), transparency and instructions for use (Article 13), accuracy and robustness (Article 15), conformity assessment (Article 43), and registration (Article 49).
The decisive extra duty for the public deployer is the Article 27 Fundamental Rights Impact Assessment. Before the first use of a point 5(a) system, the agency must assess the system's impact on the fundamental rights of the people affected — who is impacted, the categories of harm, the human-oversight measures, and what happens if the assessment surfaces a risk. This is mandatory for public-body deployers; it is not the same as a GDPR Article 35 DPIA, though Article 27(4) lets the FRIA build on an existing DPIA rather than duplicate it.
Worked example: Stadt-Sozialamt (a municipal benefits office)
A municipal social-services office, the Stadt-Sozialamt, ~250 staff, serving a mid-sized German city, procures an AI system from a private vendor to triage housing-benefit claims and flag cases for reduction or clawback. Because the office is a public authority deciding eligibility for an essential benefit, the system is high-risk under Annex III point 5(a) — and the "on behalf of" wording means the vendor running it does not change that.
The Stadt-Sozialamt is the deployer (Article 26): it must assign human oversight under Article 14, keep the logs, and — before go-live — complete a mandatory Article 27 FRIA. The vendor is the provider (Article 16) and owes the documentation pack and conformity assessment, and must register the system under Article 49. A "reduce or reclaim" decision taken on the model's output without the oversight and the FRIA in place would breach the high-risk regime — Article 99(4), up to €15 million or 3%.
How Confir helps
Confir registers each public-sector AI use, classifies it under Annex III point 5(a) (and distinguishes the 5(b)/5(c) siblings), derives the deployer/provider split, and flags the Article 27 FRIA as mandatory for a public deployer — then runs the structured FRIA itself. For the provider side it assembles the Annex IV documentation and the Article 43 conformity route. The engine is deterministic and rule-based: same intake, same finding, each cited to the Article or Annex point that fired.
Related guides
- Social benefits AI under Annex III
- Credit scoring AI (Annex III point 5(b))
- Insurance pricing AI (Annex III point 5(c))
- The FRIA under Article 27
- Deployer obligations under Article 26
- How Article 6 classifies high-risk AI
Manage your EU AI Act compliance in one place
Confir automates risk classification, technical documentation, and audit trails for any company. No consultants. No 6-month projects. 14-day free trial.
Start free trial →