EU AI Act Compliance: A 2026 Guide for German Businesses

Someone on your team has just read Article 6, found one of your systems in Annex III and asked the question that starts every AI Act project: is this one ours to worry about?
This guide is for that moment. It is written for German industrial, automotive and healthcare companies that build or use AI, and it takes the Act in plain order: how the tiers work, what a high-risk system has to show, what you can reuse from the GDPR, and what to do this month.
Start with the tier, because everything else follows from it
The EU AI Act sorts AI systems into four tiers:
- Unacceptable risk: banned outright. This includes social scoring by public authorities, real-time remote biometric identification in publicly accessible spaces (with narrow exceptions), and manipulative AI that could cause harm.
- High risk: the tier with the heavy obligations. It covers the use cases listed in Annex III, such as recruitment, critical infrastructure and law enforcement, and AI that is a safety component of a regulated product, medical devices under the MDR among them.
- Limited risk: transparency duties. A chatbot, for example, has to make clear that the user is talking to an AI.
- Minimal risk: most systems, such as spam filters or AI in video games. The Act sets no specific obligations here, though voluntary codes of conduct are encouraged.
Classification is where a mistake costs the most. Place a system too high and you carry paperwork it never needed. Place it too low and you face penalties for obligations you did not know applied to you.
What a high-risk system has to show
If you develop or deploy a high-risk AI system, the Act asks for six things:
- Risk Management System: A continuous, iterative process to identify, analyze, and mitigate risks throughout the AI system's lifecycle.
- Data Governance: Ensuring that training, validation, and testing data sets are of high quality, relevant, and free of biases.
- Technical Documentation: Comprehensive documentation must be created before the system is placed on the market. This includes the system's purpose, capabilities, limitations, and the conformity assessment results.
- Record-Keeping & Logging: Automatic logging of events is required to ensure a level of traceability of the AI system's functioning.
- Transparency & Human Oversight: Systems must be designed to be transparent to deployers and allow for effective human oversight to prevent or minimize risks.
- Accuracy, Robustness, and Cybersecurity: High-risk systems must perform consistently and be resilient against errors and attempts to alter their use or performance.
The dates from which these duties apply are set in the Act, and the EU has been discussing adjustments to them. Confirm the date that applies to your system type with your counsel before you build a plan around one. The order of work does not change either way: you cannot document a system you have not classified.
What you already have from the GDPR
If your company has done the GDPR properly, you are not starting from zero. You know which personal data you process, you keep records, and you have probably written at least one data protection impact assessment. The AI Act asks for related things: a risk assessment (for certain deployers, a fundamental rights impact assessment next to the DPIA), data of good quality, and documentation that someone other than its author can follow.
What is new is the product side: technical documentation before the system goes on the market, automatic logging, human oversight designed into the system, and for providers a conformity assessment.
Where Marsstein stands today
Marsstein is live for GDPR. EU AI Act support is in preparation: an inventory of your AI systems, risk classification and technical documentation. It will be described as live only once it is.
What you can do now is put the GDPR half in order, because the AI Act builds on it. The agent reads your public website and the documents you upload, lists the gaps against the GDPR article by article, and drafts the records of processing, the DPIAs and the processing agreements with the vendors behind your AI tools. Each document waits for your team's decision before it counts.
A plan for this month
- List every AI system you build, buy or use, including the ones hidden inside other software.
- Put each one in a tier and write down why.
- Give every high-risk system an owner and a folder for its documentation.
If you would like to see the GDPR half on your own company, or tell us what your AI inventory looks like, talk to us.
