Quirin Schlegel

Loading

The agent is a subcontractor — Deutsche Bank co-designs Google's finance agent, and DORA is the clock that already ran out

Google Cloud launched Gemini Enterprise for Financial Services on 25 August 2026 with Deutsche Bank as a named key design partner, deploying a Google-managed Financial Research agent in the Corporate Bank for German MidCorp clients — and the instrument that binds the bank is not the one the coverage reaches for. Article 25(1) of the AI Act converts a deployer into a provider only by name, substantial modification or changed intended purpose, none of which is contributing requirements, and Annex III 5(b) reaches creditworthiness of natural persons rather than corporate research. DORA has applied since 17 January 2025: Article 30(2)(a) makes the contract state whether subcontracting of an ICT service supporting a critical or important function is permitted, 30(2)(b) makes it name the countries where those functions run and data is processed, 28(3) puts every such arrangement in the register of information and 28(8) demands a tested exit strategy — so the five third-party agents from four outside firms that ship beside Google's own are a subcontracting chain that can grow without a contract amendment, and Google Cloud EMEA's own CTPP designation and Lead Overseer, in Google's words, "does not replace your own responsibilities under DORA".

28 August 202613 verified claims9 sources

Deutsche Bank helped design a Google agent, then put it in the Corporate Bank. The compliance question everyone will ask about it is the wrong one.

On 25 August, Google Cloud launched Gemini Enterprise for Financial Services: 50+ purpose-built financial skills, 13 connectors to market data, filings and internal databases, and a Google-managed Financial Research agent. Deutsche Bank is named a key design partner — in its own words it helped shape requirements around security, auditability, data residency and user needs. First deployment: the Corporate Bank, serving German MidCorp clients.

Three corrections before you reach for the AI Act.

1. Co-design does not make you a provider. Article 25(1) converts a deployer into a provider in three cases: your name goes on it, you substantially modify it, or you modify the intended purpose so it becomes high-risk. Writing requirements is none of them.

2. It probably is not high-risk anyway. Annex III 5(b) covers creditworthiness of natural persons. MidCorp clients are legal persons, and a briefing agent is not scoring anybody.

3. The instrument that binds here is older and has no transition left. DORA has applied since 17 January 2025.

DORA is where the agent roster becomes the problem. Beside Google's own agent, the platform ships five third-party agents from four outside firms — Dun & Bradstreet, FlowX, Obin, S&P Global. Article 30(2)(a) says the contract has to state whether subcontracting of an ICT service supporting a critical or important function is permitted at all. Article 30(2)(b) says it has to name the countries where those functions run and the data is processed. Article 28(3) puts every one of those arrangements in your register of information.

Google Cloud EMEA was designated a critical ICT third-party provider on 18 November 2025 and has its own Lead Overseer. Google's own wording: that oversight "does not replace your own responsibilities under DORA."

What I would do Monday:

1. Put every third-party agent in the register as a subcontractor, not a platform feature. 2. Check the contract names countries, not just a cloud region. 3. Test the exit strategy against the agent and its grounding, not the infrastructure. 4. Keep Article 26 logs regardless. Annex III moves on 2 December 2027 and your use cases will drift first.

An agent marketplace is a subcontracting chain that grows without an amendment.

Which of your agents is in the register?

#DORA #AIAct #AgenticAI #EUCompliance #FinTech

Evidence

What this rests on

Every factual claim in the edition above, stated on its own and checked before publication. If one of these is wrong, the argument is wrong — so they are listed where you can check them.

On 25 August 2026 Google Cloud launched Gemini Enterprise for Financial Services, a purpose-built agentic AI solution for capital markets and corporate banking, shipping a Google-managed Financial Research agent, more than 50 purpose-built financial skills and 13 connectors to market data, news feeds, regulatory filings and internal databases.
Why it mattersIt dates the event from the vendor's own release rather than from the 26-27 August aggregator coverage, and it fixes what is actually in scope when a bank adopts the platform.
googlecloud2026google
Beside Google's own managed agent, the platform ships five named third-party agents supplied by four outside firms: the D&B Business Verification Agent, FlowX Agents, the Obin Financial Agent, the S&P Global Data Retrieval Agent and the S&P Global Energy Horizons Agents.
Why it mattersEach of those is a separate party in the service chain. Under DORA they are candidates for the register of information, not platform features.
googlecloud2026google
Deutsche Bank is named a key design partner for Gemini Enterprise for Financial Services and states that it contributed banking expertise and helped shape requirements around security, auditability, data residency and user needs; first deployment is in its Corporate Bank serving German MidCorp clients.
Why it mattersIt establishes the bank's role in the bank's own words, which is what the Article 25 analysis turns on, and it fixes the deployment scope as corporate rather than retail.
deutscheban2026deutsche
DORA, Regulation (EU) 2022/2554, has applied since 17 January 2025 under its Article 64.
Why it mattersThere is no transition period left to plan against. Every obligation discussed here is live today.
eurlex2022regulatio
DORA Article 30(2)(a) requires the contractual arrangement to contain a clear and complete description of all functions and ICT services and to state whether subcontracting of an ICT service supporting a critical or important function is permitted, and under which conditions.
Why it mattersAn agent supplied by an outside firm inside a platform is subcontracted ICT service. If the contract is silent, the permission question is unanswered rather than answered yes.
eurlex2022regulatio
DORA Article 30(2)(b) requires the contract to state the locations, namely the regions or countries, where the contracted or subcontracted functions and ICT services are to be provided and where data is to be processed, including the storage location.
Why it mattersA cloud region in a configuration console is not the contractual statement the article asks for, and third-party agents may not run where the platform does.
eurlex2022regulatio
DORA Article 28(3) requires financial entities to maintain and update, at entity level and at sub-consolidated and consolidated levels, a register of information on all contractual arrangements for the use of ICT services provided by ICT third-party service providers, distinguishing those covering critical or important functions.
Why it mattersThe register is the artefact a supervisor asks for. An agent roster that grows inside a platform changes what belongs in it without any procurement event.
eurlex2022regulatio
DORA Article 28(8) requires financial entities to have exit strategies for ICT services supporting critical or important functions, documented and periodically tested, so that they can exit without disruption to business activities, without limiting compliance with regulatory requirements and without detriment to the continuity and quality of client services.
Why it mattersThe thing to test is the agent and its grounding, not the infrastructure underneath it: reproducing a research output elsewhere is a different problem from moving a workload.
eurlex2022regulatio
The ESAs announced the designation of critical ICT third-party providers under DORA on 18 November 2025, and Google states that Google Cloud EMEA Limited together with its subsidiaries was designated and assigned a dedicated Lead Overseer, adding that CTPP oversight does not replace a customer's own responsibilities under DORA.
Why it mattersSupervision of the provider is not a substitute for the financial entity's own register, contract terms and exit plan — a point the provider itself makes in writing.
europeanban2025the · googlecloud2025supportin
AI Act Article 25(1) treats a distributor, importer, deployer or other third party as a provider of a high-risk AI system in three circumstances only: putting their name or trademark on it, making a substantial modification to it, or modifying the intended purpose of a non-high-risk system so that it becomes high-risk.
Why it mattersContributing requirements to a vendor's product is none of the three. Co-design does not transfer provider obligations.
euartificia2024responsib
AI Act Annex III point 5(b) classifies as high-risk those AI systems intended to be used to evaluate the creditworthiness of natural persons or establish their credit score, excepting systems used to detect financial fraud.
Why it mattersA corporate research agent serving MidCorp clients — legal persons — is outside that item, which is why the AI Act is the wrong first instrument to reach for here.
euartificia2024annex
Commission Delegated Regulation (EU) 2025/532 of 24 March 2025 sets the regulatory technical standards specifying the elements a financial entity has to determine and assess when subcontracting ICT services supporting critical or important functions, and entered into force on 22 July 2025.
Why it mattersIt is the checklist that applies before a bank permits a third-party agent into a critical or important function, and it has been in force for over a year.
eurlex2025commissio
Regulation (EU) 2026/1744, in force since 27 July 2026, moved the Annex III high-risk obligations of the AI Act to 2 December 2027.
Why it mattersIt dates the Article 19 and Article 26(6) log duties for Annex III: the runway for deciding which logs are genuinely under your control runs to 2 December 2027.
eurlex2026regulatio

Sources

Every source for this edition, as one PDF BibTeX — all editions

Corrections

What changed after publication

- Took the launch date from Google Cloud's own press corner release and Deutsche Bank's own release, both 25 August 2026, not from the aggregator listings that placed it on 26 or 27 August. A coverage date is not an event date. - Did not treat co-design as a provider trigger. Article 25(1) is quoted in full in the archived source; contributing requirements matches none of its three circumstances, and the article only operates on high-risk systems in the first place. - Did not assert the Financial Research agent is or is not a high-risk system as a verified claim. What is claimed is the wording of Annex III 5(b) — creditworthiness of natural persons — and that MidCorp clients are corporate. The inference that the agent falls outside Annex III is presented as the edition's argument, not as a claim about Google's system. - Did not take the identity of any designated CTPP from the ESAs' press release, which does not name providers in its body. Google Cloud EMEA Limited is named from Google's own post about its own designation. - Dropped the Official Journal publication date of 2 July 2025 for Delegated Regulation (EU) 2025/532, which came only from law-firm commentary. The EUR-Lex record supports the act date of 24 March 2025 and entry into force on 22 July 2025, and only those are used. - Used artificialintelligenceact.eu solely for the verbatim text of Article 25(1) and Annex III point 5, graded secondary. No date comes from that site. The 2 December 2027 Annex III date is carried from CLAIM-2026-08-23-08, verified against Regulation (EU) 2026/1744 on EUR-Lex. - Did not repeat Google's marketing line that the platform is "engineered from the ground up to address key regulatory and data residency requirements". It is vendor language about vendor architecture and it is not evidence about the deployer's obligations. - Issued new cite keys for all eight new sources after checking the published vault: none of these URLs was previously archived, and no existing key was overloaded.