AI Vendor Clauses That Allocate EU AI Act Liability: A Clause-by-Clause Guide
The Act allocates duties by behaviour, not by contract — put your name on a system or modify it and you can inherit the provider's obligations. Eight clauses that keep those duties where they belong, with wording you can paste into a vendor agreement today.
Here is the uncomfortable starting point: the EU AI Act does not care who your contract says is responsible. It allocates roles by facts — who places the system on the market under their name, who substantially modifies it, who changes its intended purpose. Under Article 25, a distributor, importer or deployer who does those things becomes the provider and inherits the full conformity burden. Contracts cannot rewrite that rule; what contracts can do is make sure the facts stay on the vendor’s side of the line, and that the evidence flows to you when authorities or customers come asking.
For mid-market buyers signing paper drafted before2026, these eight clauses are the difference between a vendor relationship and an accidental provider role.
The Article 25 trap, in one paragraph
Three acts convert you into a provider: putting your name or trademark on the AI system, substantially modifying it, or modifying its intended purpose in a way that requires compliance with new requirements. The mid-market versions of these are mundane and everywhere: rebranding a white-label model with your logo, self-hosting and patching a vendor’s weights, extending a contract-analysis tool to make employment decisions it was never specified for. Every clause below exists to prevent one of those three conversions — or to make sure the vendor supports you if one happens anyway.
The eight clauses
1. Role and compliance warranty. Anchor the vendor’s statutory identity before anything else:
Supplier warrants that it is the “provider” of the AI System under Regulation (EU) 2024/1689, that the System has completed its applicable conformity assessment route, and that it is (or will, prior to the Transfer Date, be) listed in the EU database reference required for high-risk systems. Supplier warrants that Customer’s use as documented does not convert Customer into a provider under Article 25.
2. Documentation access on demand. Annex IV technical documentation, instructions for use, and the classification reasoning must be producible — not “available on request” to enterprise customers only:
Supplier shall provide, within ten Business Days of request, the technical documentation, classification rationale and instructions for use necessary for Customer to meet its deployer obligations and to respond to competent-authority information requests.
3. Change notification and re-assessment trigger. Model updates shift decision boundaries; your register and assessments depend on knowing when:
Supplier shall notify Customer at least thirty days before any update materially changing the System’s intended purpose, decision logic or risk classification, and shall state whether the change constitutes a substantial modification under Article 25 and which conformity steps follow.
4. Incident cooperation with a clock. The Act’s serious-incident reporting window is measured in days; you cannot meet it if facts sit in the vendor’s ticketing system:
Supplier shall supply all information necessary for Customer’s regulatory incident notifications within five Business Days of request, including input data, decision logs and mitigation history, for incidents or near-misses involving the System.
5. Transparency artefact delivery. Article 50 disclosures (AI interaction notices, synthetic-content marking) only work if the components reach the deployer:
Supplier shall deliver machine-readable marking and disclosure components enabling Customer to inform natural persons that they are interacting with an AI system, and shall keep such components current for the Term.
6. Audit and inspection support. Market-surveillance authorities can ask you about their system:
Supplier shall cooperate, at no additional charge, with competent-authority reviews concerning the System, including provision of test access, logs and evaluation reports held under its control.
7. Liability and indemnity split. Match indemnity to statutory duty: the supplier covers provider-side non-conformity (defective conformity assessment, missing documentation, undisclosed training-data or copyright exposure); you cover your deployer-side misuse — feeding unlawful input data, operating outside instructions, disabling safeguards:
Each party indemnifies the other against fines, claims and reasonable costs arising from obligations allocated to it under Regulation (EU) 2024/1689 and this Agreement, provided the indemnified party gave prompt notice and reasonable control of defence.
8. Termination for compliance change. If the vendor’s route collapses — conformity withdrawn, registration cancelled, the model prohibited or designated systemic-risk without mitigation — you need an exit that is not a dispute:
Customer may terminate affected Orders without penalty if the System’s conformity assessment is withdrawn, its EU database registration is cancelled, or the System becomes subject to prohibited-practice or systemic-risk obligations that Supplier does not meet within ninety days.
Mapping clauses to articles
| Clause | Protects you from | Article hook |
|---|---|---|
| Role warranty | Accidental provider status | Art. 25 conversion rules |
| Documentation access | Authority requests you cannot answer | Art. 21 cooperation, Annex IV |
| Change notification | Stale assessments after silent updates | Art. 25 substantial modification |
| Incident cooperation | Missing the 15-day reporting clock | Art. 73 serious-incident reporting |
| Transparency delivery | Personal-facing disclosure gaps | Art. 50 transparency |
| Audit support | Unanswered market-surveillance enquiries | Market-surveillance cooperation duties |
| Liability/indemnity | Fines for duties you never controlled | Penalty allocation (Arts. 99–101) |
| Termination trigger | Riding a non-compliant product into enforcement | Whole-of-Act exposure |
The legacy vendor: side letter, not rewrite
Contracts signed before the Act existed rarely contain any of this, and reopening a signed MSA for a “regulatory addendum” invites a commercial conversation you may not want. The pragmatic instrument is a short AI Act side letter: warranty of provider status, documentation access, incident clock, transparency delivery, termination trigger — five paragraphs, signed by both parties, referenced from the master agreement. Vendors with real compliance programmes will already have something similar prepared (many began shipping one after the Code of Practice); asking for it is itself a diligence signal about how far their programme has actually progressed.
What to do when the vendor refuses everything: treat refusal as an answer. A supplier unwilling to warrant provider status or meet a five-day incident clock is telling you that either their conformity work does not exist or that you would be carrying it — both are decision-relevant facts before you carry their system into your own register.
How to check your own position in three minutes
The free exposure scan asks twelve questions about your AI usage and governance and returns an exposure score, your ranked exposures with the exact article that fired, and your first three moves — mapped to the dates that apply. Confirm your email and the full report unlocks.
Frequently asked questions
Can a contract move AI Act liability entirely to the vendor?
No. Statutory roles follow Article 25 facts, not contractual labels — if you put your name on the system, substantially modify it, or change its intended purpose, you are the provider regardless of what the MSA says. What contracts control is conduct: keeping you inside documented use, forcing change notification, and making the vendor support your side of the evidence chain.
Do we need these clauses if the vendor is already EU AI Act compliant?
You need them more, in one sense: compliance is a moving target, and the vendor’s obligations evolve with updates, redesignations and enforcement. The clauses convert “we are compliant today” into an ongoing, enforceable duty to keep you informed and supplied — which is exactly what your own register, incident reporting and audit responses depend on.
Our vendor contract predates the AI Act — must we renegotiate?
No — a side letter is the standard fix. Five to eight paragraphs covering provider-status warranty, documentation access, incident cooperation, transparency delivery and a termination trigger, referenced from the master agreement, close the gap without reopening commercial terms. Bundling the request with a renewal conversation usually makes it easier, not harder.
What is the single most dangerous clause to leave out?
Change notification tied to the substantial-modification definition. Silent model updates are how a compliant deployment drifts into non-conformity: your classification, register entry and assessments were true when you signed, and become fiction at the next model drop. Without a notice period and a stated re-assessment position, you are certifying a system you have not seen.
How long should the vendor’s incident response window be?
Shorter than the regulatory clock it feeds. With a serious-incident notification horizon of up to fifteen days depending on severity, a five-Business-Day vendor window leaves room to assemble, review and file — anything longer than a week, and the vendor’s facts arrive after your deadline, not before it.
Should procurement score vendors on AI Act clause acceptance?
Yes — treat willingness to sign as a diligence signal alongside their documentation. Vendors with a real conformity programme offer these terms unprompted; vendors without one negotiate them away one by one. The negotiation itself tells you more about their compliance maturity than the questionnaire they filled in.
Put this guide to work on your own estate.
Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.
- Free forever plan
- No credit card
- EU-hosted · GDPR-native
Build a live AI register in minutes — upgrade only when you need the audit pack.