NVDA 215.38 ▼1.17%GOOGL 324.89 ▲1.34%MSFT 531.01 ▼0.06%AMD 578.44 ▲3.24%INTC 95.53 ▲1.91%TSMC 439.51 ▲0.60%AMZN 254.60 ▲0.59%META 612.49 ▼1.24%AAPL 343.83 ▼0.94%PLTR 196.81 ▼0.97%
Markets at last close

Policy

Banks and insurers face layered rules for AI pilots

·1 min read

Banks and insurers can adopt AI in supporting workflows, but must establish accountability, classify each use and assess overlapping regulatory requirements. Under the amended AI Act timetable, transparency obligations apply from 2 August 2026, while requirements for high-risk systems under Annex III begin on 2 December 2027. Relevant high-risk uses include assessing individuals’ creditworthiness, life and health insurance risk assessment and pricing, and recruitment or employee evaluation. Building a system under an institution’s own name, or substantially changing its purpose, can create provider obligations rather than only deployer duties.

The AI Act does not replace GDPR or financial-sector rules. Meaningful human oversight matters: an employee merely approving an automated recommendation does not resolve concerns about automated decisions. Personal-data pilots may require a data protection impact assessment. Cloud-based language models also fall within DORA’s third-party ICT framework, making pre-contract risk assessment and contractual safeguards important. Supplier checks should cover training restrictions, processing locations, retention, subprocessors, model changes and usable data exports.

Suitable initial projects include document triage, internal-policy search, draft customer replies and form prefilling, with staff checking outputs before external effects. Teams should define permitted data, approved tools, ownership and measurable success criteria before starting. Pilots should not proceed when accountability is unclear, suppliers cannot document data handling, or unreliable source data prevents meaningful evaluation.

Originally reported by siboconsulting.comRead the source →
Related coverage