Evidence Supporting an Article 6(3) Non-High-Risk Exemption for Financial Services AI Systems
An Article 6(3) exemption is a documented claim, not a label.
The claim holds up only if the assessment is recorded before the system is placed on the market or put into service, registered where required, backed by testable evidence, and kept true by monitoring in production.
From exemption claim to defensible record
| Stage | What it involves |
|---|---|
| 1. Map | Tie each system to its Annex III use case and a named owner. |
| 2. Test | Check the system against one exemption condition and the profiling exclusion. |
| 3. Document and register | Record the assessment before deployment and meet registration duties. |
| 4. Sustain | Use monitoring and audit logs to show the system stays within its declared scope. |
What Article 6(3) allows and where it stops
For an Annex III system, you must show three things:
- The system does not pose a significant risk of harm to health, safety or fundamental rights.
- The system meets at least one of the narrow conditions in the article.
- The system does not profile natural persons.
The profiling exclusion in credit and insurance
The exemption does not apply to a system that profiles natural persons. This is the point where financial services use cases are most likely to fall outside it.
Mapping each exemption condition to evidence
The claim must be backed by testable evidence. Tie each system to its Annex III use case and a named owner, then check the system against one exemption condition and the profiling exclusion.
Documentation and registration under Article 6(4) and Article 49(2)
The assessment must be recorded before the system is placed on the market or put into service, and registered where required. Record the assessment before deployment and meet registration duties under Article 49(2), so that documentation can be produced on request.
Keeping the determination valid in production
The claim stays true only while the system stays within its declared scope. Use monitoring and audit logs to show that it does, and treat changes as a trigger for reassessment.
Would your assessment records withstand scrutiny?
- Each system is mapped to an Annex III use case, with a named owner for the mapping.
- The assessment is dated and approved before deployment or market placement.
- The profiling exclusion was tested and the reasoning recorded.
- Evidence shows human review is substantive, including cases where reviewers disagreed with or overrode outputs.
- Monitoring can detect use beyond the declared intended purpose, and changes trigger a reassessment.
- Registration under Article 49(2) is complete and documentation can be produced on request.