The crosswalk

The EU AI Act GDPR crosswalk: where the frameworks meet, and where they only look alike.

Vendors often sell framework overlap as a mapping. The EU AI Act grants six explicit routes for earlier work, a GDPR DPIA among them, to count. The rest we label a resemblance.

Three relations

Only one of them counts toward completion.

Closes

A step closes a requirement of its own framework. The only relation that moves a completion figure or appears in the coverage matrix.

Counts toward completion.

Related · unverified

A requirement in another framework on the same ground. Shown so you can see the neighbours, never credited; every EU AI Act link here is marked unverified.

Shown for orientation only.

Statutory reuse

One of the six routes below, where the EU AI Act's own text lets earlier work be drawn on. It prefills a form and explains itself; it does not change a status.

Saves typing. The judgement stays yours.

Statutory routes

The places the Act itself lets earlier work count.

Each row quotes the provision that grants it, and any condition on who may use it: offering a route to someone with no right to it is worse than none.

EU AI Act Art. 27(4)

Fundamental-rights impact assessment / DPIA

What the Act says: Where any of the obligations of Art. 27 is already met through the data-protection impact assessment carried out under GDPR Art. 35, the deployer may cross-refer to the relevant sections of that assessment in the fundamental-rights assessment, or include the relevant parts of it.

What you are asked to confirm: Draw the overlapping parts from your data-protection impact assessment, then check they reach the fundamental-rights questions the DPIA was never written to answer.

EU AI Act Art. 26(9)

Provider's instructions for use, feeding the DPIA

What the Act says: Deployers of high-risk systems shall use the information provided under Art. 13 to carry out their data-protection impact assessment under GDPR Art. 35.

What you are asked to confirm: Bring the provider's instructions for use into the impact assessment, then check they describe this deployment rather than the product in general.

EU AI Act Art. 8(2)

Technical documentation and testing

What the Act says: Where a product is covered both by this Regulation and by the Annex I harmonisation legislation, the provider may integrate the testing, reporting, information and documentation into procedures that legislation already requires.

Open only where: Only where the product also falls under Annex I harmonisation legislation — a medical device, machinery, a vehicle and so on.

What you are asked to confirm: Name the Annex I procedure the documentation is integrated into, then check it carries the Art. 11 content as well as its own.

EU AI Act Art. 17(3)

Quality management system

What the Act says: Providers already subject to quality-management obligations under sectoral Union law may include the Art. 17(1) aspects within that existing system.

Open only where: Only where sectoral UNION LAW already imposes a quality-management duty. A voluntary standard is not sectoral Union law — ISO/IEC 42001 does not open this route.

What you are asked to confirm: Name the sectoral instrument and the system it requires, then check the Art. 17(1) aspects are written into it rather than assumed.

EU AI Act Art. 17(4)

Quality management system

What the Act says: For providers that are financial institutions subject to internal governance requirements under Union financial-services law, the quality-management duty is deemed fulfilled by complying with those rules — except for the aspects at Art. 17(1)(g), (h) and (i).

Open only where: Only for financial institutions subject to internal governance requirements under Union financial-services law. Points (g), (h) and (i) stay yours whatever those rules say.

What you are asked to confirm: Name the internal governance arrangements you rely on, then account separately for Art. 17(1)(g), (h) and (i), which this route does not reach.

EU AI Act Art. 26(5)

Post-deployment monitoring

What the Act says: Deployers that are financial institutions subject to internal governance requirements under Union financial-services law are deemed to fulfil the monitoring obligation by complying with those arrangements.

Open only where: Only for financial institutions subject to internal governance requirements under Union financial-services law.

What you are asked to confirm: Name the internal governance arrangements that monitor this system, then check they observe it in operation rather than only at approval.

Declaring one prefills a form and records your reliance. It does not tick the obligation: whether your governance reaches far enough is your judgement, kept in your name.

What we do not claim

The part most crosswalks leave out.

No requirement equivalence. Veritome never asserts that an ISO/IEC 42001 control meets an EU AI Act article: that needs a cited harmonised standard. EN 18286 (cited 14.10.2026) covers the Article 17 quality management system; ISO/IEC 42001 is not cited.

Shared artefacts are not built. Sometimes two frameworks plainly want the same document without either saying one stands in for the other. We have not built that, and name the gap so you do not assume the crosswalk is complete.

A related link is never credit. Where requirements share ground, the register shows the link and marks it unverified. Reading a signpost as credit is how an organisation reaches an audit believing work was done that nobody did.

How the five frameworks run on one register
Straight answers

Questions about the EU AI Act and GDPR crosswalk.

Does running one framework get me credit against another?

Only where the law says so, and the law says so in six places. Everything else is a resemblance. A step in one programme can close a requirement of that framework, and it may be related to a requirement of another. A related link is a signpost, and Veritome never counts it as credit.

Why not map ISO 42001 controls onto EU AI Act articles?

Because saying a control meets an article is a claim of requirement equivalence, and a presumption of conformity attaches only to a cited harmonised standard, for the requirements it covers. One is now cited, EN 18286, for the Article 17 quality management system; ISO/IEC 42001 is not. A 42001-to-Act mapping presented as compliance is still somebody's opinion in a table.

So what does a reuse route actually do?

It changes what a form is prefilled with and what the screen explains. It never moves a completion percentage, an obligation's status or coverage. You declare the reliance; the status stays yours, because whether you truly comply with your own internal governance is not a fact this product can observe.

What are Tier B and Tier C?

Tier B is shared artefacts: two frameworks plainly want the same document, without either saying one satisfies the other. Tier C is interpretive mapping. Neither is built. They are named so the ladder is legible, and nobody assumes the six statutory routes are the whole story.