What Must a Bank's Contract With an AI Vendor Include Under DORA?

7 min readAbleneo AI transformation team

Short answer. DORA (Regulation (EU) 2022/2554), which has applied to EU financial entities since 17 January 2025, requires a bank’s contract with an AI vendor to carry a defined set of clauses under Article 30. Every ICT contract needs a baseline tier: a full description of the service, rights and obligations allocated in writing, data location and protection terms, and whether subcontracting is allowed. When the AI supports a critical or important function, a second, stricter tier adds quantitative service levels, unrestricted on-site audit rights, incident assistance, resilience-testing participation, and a tested exit strategy under Article 28.

1What This Means in Practice

DORA treats an AI vendor as an ICT third-party service provider. The moment a bank runs an AI system that a supplier builds, hosts, or maintains, the contract behind it falls under Article 30. The regulation sets two tiers. The baseline tier applies to every ICT contract. The enhanced tier applies when the AI supports a critical or important function, for example a model inside credit decisioning, fraud detection, or claims handling.

This changes procurement. A bank cannot sign a short order form for a production AI service and treat the governance as an afterthought. The contract itself has to carry audit rights, service levels, incident duties, and exit terms before the system goes live. The gap between a working pilot and a DORA-ready production contract is where most AI projects stall. At Ableneo, 4 of 5 AI projects reach production, and getting the contract and governance right is part of why.

2Why This Matters for Regulated Industries

For banks and insurers in Central Europe, two regulations now meet in the same contract. DORA has applied since 17 January 2025 and governs the operational resilience of every ICT service, AI included. The EU AI Act adds obligations on top: high-risk systems under Annex III, which cover credit scoring and insurance risk assessment and pricing, carry their own requirements from 2 December 2027. A single AI vendor contract for a credit model therefore has to satisfy both regimes at once.

The supervisory weight is real. Competent authorities can inspect the contract, and under DORA they can examine the vendor on-site. A contract that names an audit right the bank can never exercise does not satisfy the regulation. For a mid-market bank or insurer, the practical risk is a supervisor finding that a production AI system sits on a contract that cannot be audited or exited. Writing the clauses correctly before signature is cheaper than retrofitting them under a supervisory finding.

DORA Article 30 sets two tiers of contract clauses for an AI vendor: a baseline for every ICT service, and a stricter set when the AI supports a critical or important function.

3Which Clauses Does DORA Require in Every AI Vendor Contract?

Article 30(2) sets the baseline for all ICT contracts. The contract must give a clear and complete description of every function and service the vendor provides. It must state whether subcontracting of a service supporting a critical or important function is allowed, and on what conditions. It must name the locations where the service runs and where data is processed and stored, with advance notice of any change. It must set out data availability, integrity, and confidentiality terms, and the vendor’s duty to assist during an ICT incident. Rights and obligations of both sides have to be allocated clearly and in writing. These apply even to a low-risk AI tool.

4What Extra Clauses Apply When the AI Supports a Critical Function?

Article 30(3) adds the stricter tier. The contract needs full service level descriptions with precise quantitative and qualitative targets, so the bank can monitor the AI and act when it drifts. It needs notice periods and reporting duties, including any development that could materially affect the vendor’s ability to meet those targets. It needs unrestricted rights of access, inspection, and audit for the bank, its appointed third party, and the competent authority, including on-site. The vendor must take part in the bank’s threat-led penetration testing where required, and support the bank during and after an incident at a cost agreed in advance. A documented exit strategy closes the set.

5What Must the Contract Say About Subcontracting and the AI Supply Chain?

Most AI vendors sit on other providers. The model may run on a hyperscaler, the data may pass through a separate pipeline, and a foundation model may come from a third party. DORA treats that whole chain as in scope. The Subcontracting RTS, Commission Delegated Regulation (EU) 2025/532, has applied since 22 July 2025 and sets what a bank must assess before allowing a subcontractor to support a critical or important function. The contract has to name the material subcontractors, state the conditions under which the chain can change, and preserve the bank’s audit and exit rights down the chain. For an AI system, data residency and changes to the model provider are the clauses that need the most attention.

6How Do You Build an Exit Strategy for an AI Vendor?

Article 28 requires an exit strategy for every ICT service that supports a critical or important function. For an AI vendor that means a written, tested plan to move the service to another provider or bring it in-house without breaking operations. The plan has to cover return of the bank’s data in an accessible format, handover of model configuration and documentation, and a transition period during which the vendor keeps the service running. Article 28(7) lists the termination triggers, among them a material breach, evidenced weaknesses in the vendor’s ICT risk management, and a supervisor that can no longer oversee the bank through the contract. An exit clause that has never been tested is the one that fails in an audit.

7Can an AI Startup Sign a DORA-Compliant Contract?

This is where many AI deals stall. Hyperscalers carry these clauses as standard. Smaller AI vendors often cannot, and the contract becomes the procurement blocker. The question for a bank is not whether the model performs well. It is whether the vendor can grant on-site audit rights, name its subcontractors, meet quantitative service levels, and stand behind a tested exit. A vendor that has shipped regulated AI to production before will already have answered these questions. A vendor that has only run pilots usually has not.

8The Ableneo Perspective

Ableneo operates as the ICT third-party provider on the other side of these contracts. The obligations DORA places on an AI vendor are ones we meet rather than negotiate away. The production record is the reason: 4 of 5 of our AI projects reach production, we shipped 34 production AI projects in 2025 for regulated clients in the Czech Republic, Slovakia, and Austria, and our document-validation system for T-Mobile Czech Republic runs 14x faster than the manual process at over 90% accuracy. A vendor that has already stood behind audit, incident, and exit terms on live systems can sign the contract a bank’s risk function needs. For the risk-management side of the same work, see our guide on how to manage AI vendor risk under DORA.

Key takeaways

Sources

Planning AI in a regulated business? Ableneo takes systems from classification to governed production.

Talk to Ableneo