Sector · Financial services

The one sector the Act names twice.

Credit scoring and life-and-health insurance pricing are high-risk by name. The EU AI Act also gives financial institutions two narrow routes into existing governance.

No card · EU-hosted · 5 minutes to a first classification
Risk registerEthical
Shortlisting disadvantages a protected group
Critical+CriticalHighMediumLow
51015202548121620369121524681012345
RareUnlikelyPossibleLikelyCertain
Inherent
12 · Act now
Treatment
Mitigate · bias testing per release
Residual
4 · Accepted
Residual risk signed off Art. 9
Illustrative record · articles are real, the system is not
The reality

What financial firms get wrong.

What we hear

“Our model risk framework already covers this.”

What the product does

It covers much of the evidence and none of the classification: which systems are in scope, and why.

What we hear

“We assumed the fraud carve-out covered the scoring model too.”

What the product does

The carve-out attaches to purpose. The same model used for scoring is not carved out.

What we hear

“We did the DPIA and stopped.”

What the product does

Credit and insurance-pricing deployers also owe an Art. 27 rights assessment. It builds on the DPIA but asks more.

What you get

The routes the Act grants, with their conditions.

01

Art. 17(4), stated precisely

Fold the Art. 17(1) aspects into internal governance, with (g), (h) and (i) accounted for separately.

02

Annex III scoping that holds

Creditworthiness and life-and-health insurance pricing in scope, with the fraud carve-out applied by purpose.

03

Art. 27 and DPIA in step

The rights assessment builds on your DPIA, its answers laid under the DPIA's headings.

04

You declare the reliance

A statutory route prefills a form and records your reliance. It never ticks the obligation: that judgement is yours.

In practice

Three financial deployments.

Use case 01

A lender running a bought credit-scoring model.

  • Annex III 5(b): high-risk by listing, with Art. 26 deployer duties.
  • Art. 27 rights assessment applies, feeding the DPIA view.
  • Art. 26(5) monitoring folded in, declared rather than assumed.
Obligation registerDerived by the engine
12obligations applyDeployerHigh

12 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register0
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend and inform where use may present a risk
Art. 25(1)Watch for the changes that make you the provider
Computed by the engine for one system · switch the role to compare
Use case 02

An insurer pricing life cover with a model it built.

  • Annex III 5(c) and the provider set, Art. 9 to Art. 49.
  • Art. 17(4) folds most Art. 17(1) aspects into internal governance.
  • The reliance recorded, naming the instrument it rests on.
Annex IV — Technical DocumentationRecruitment assistant
§1General DescriptionArt. 11
§2System Elements & Development ProcessArt. 11
§3Training, Validation & Testing DataArt. 10
§4Testing & Validation ResultsArt. 15
§5Human Oversight MeasuresArt. 14
§6Risk Management SummaryArt. 9
§7Cybersecurity MeasuresArt. 15
§8Pre-determined Changes & Continuous LearningProvider narrative · to write
Sealedsha256sha256 fingerprint e4d4b64e5aeabf734f6512c3249ff428c83229491c30f20c63c233614049e0227 of 8 filled from the register
Illustrative file · the sections are the builder's own; §8 is always yours to write
Use case 03

A bank running fraud detection and scoring on related models.

  • The fraud model sits inside the Annex III 5(b) carve-out.
  • The scoring model does not, even on shared architecture.
  • Classification asks about purpose, so the two separate cleanly.
AI systems4 in the register
SystemRole · riskStageDone
Recruitment assistantDeployerHighBuild & document5/12
Credit-scoring modelProviderHighBuild & document8/25
Meeting summariserDeployerMinimalOperate & monitor2/2
Document searchDeployerMinimalOperate & monitor2/2
One register, each system its own role
Illustrative workspace · roles, tiers and obligations are the engine's
Also included

What sits beside the sector duties.

Straight answers

Questions on the EU AI Act for financial services.

Which financial use cases are high-risk?

Annex III point 5(b): creditworthiness and credit scoring, except to detect financial fraud. Point 5(c): risk assessment and pricing in life and health insurance. Both are high-risk by listing; what matters is how you evidence the duties.

We already run internal governance under CRD or Solvency II. Does that count?

Yes, in two places. Article 17(4) lets a provider that is a financial institution fold the Article 17(1) aspects, except (g), (h) and (i), into its internal governance under Union financial-services law. Article 26(5) does the same for deployer monitoring. Neither is a general exemption.

Does a fundamental rights impact assessment apply to us?

Article 27 binds deployers of the creditworthiness and insurance-pricing systems, alongside public bodies. It can build on your DPIA (Art. 27(4)); Veritome lays its answers under the DPIA's headings so the two stay consistent.

Is fraud detection caught?

Annex III point 5(b) carves out fraud detection, and the carve-out attaches to purpose. A model used for fraud detection and separately for scoring is not covered in the second use.

How does this sit with DORA and existing model risk management?

Alongside them. Much of their evidence is reusable as input; the EU AI Act adds a classification, the obligations derived from it and the article behind each.