Supplier evidence: what a certificate does not prove
A certificate proves a scope, not a service. The six pieces of evidence you should request instead, and what ISO/IEC 42001 A.10.3 says about it.
In short
A certificate proves that a defined scope was audited at a point in time. Whether this scope includes the service you are buying is stated in the annex to the certificate. So request the scope in its exact wording, the Statement of Applicability, the change notification and the escalation path.
Auf Deutsch lesen: deutsche Fassung
The scene repeats itself in almost every supplier meeting. I ask for evidence, and a PDF certificate comes across the table: company name, standard number, a seal, two signatures at the bottom. Very neat. Only it does not answer my question, and you only notice that when you turn it over and read the annex.
A certificate proves that a body audited a defined scope at a point in time and found it to conform. It does not prove that the service you are buying lies within this scope. Nor does it prove how the system behaves today. Both are separate questions, and both are only answered by someone who requests the right documents.
I sit in both roles: I audit suppliers for customers, and I am myself a supplier who has to hand over evidence. So here is the list I actually request, and the one question I start with.
The question I start with
It is not “Are you certified?” but: “Does the scope cover what you do for us?” This question sounds like a formality and is the most frequent hit.
A scope is one sentence, and it is narrow. It names activities, often sites, sometimes product lines. A provider can be certified for the development and sale of its software at the main site, while the operation of your instance runs in a subsidiary that is not in the scope. The certificate is genuine, the statement is correct, and for your use case it still carries nothing.
That is why the certificate document is never enough. You need the scope in its exact wording, and you need it lying next to your own service description. If the two do not match, that is not grounds for exclusion, but it is the point at which the conversation begins instead of ending.
A certificate answers the question of whether an audit took place. It does not answer the question of whether what was audited is your case.
Six documents I request
None of this is exotic, and none of it demands trade secrets. These are documents that a provider with a functioning management system keeps anyway.
- The certificate with the scope in its exact wording, not just the certificate document. Plus the issuing body and its accreditation. A certificate from a non-accredited body is not worthless, but it is a different statement, and you should know which one you are holding.
- The Statement of Applicability, at least for the controls that concern your case. It states what the provider considers applicable and what it has excluded. An exclusion is permissible and must be justified; the justification is the actual evidence.
- The technical documentation of the supplied component and a description of how it is integrated into your systems. The implementation guidance on A.10.3 of ISO/IEC 42001 (Annex B.10.3) recommends documenting how a supplied system is integrated.
- The change notification. By which route and with how much notice do you learn that the model version, system prompt or subcontractors are changing? Without this point every other piece of evidence is a snapshot on one date with no updating.
- The escalation path for corrective actions: whom you contact, within what period there is a response, and what happens if the component does not work as intended. The guidance on A.10.3 provides for the organisation requiring the supplier to take corrective actions.
- The list of subcontractors, as far as they touch your data or your processing. For commissioned data processing that is mandatory anyway; with AI services it is the point at which it turns out that there is a third-party model behind the product.
What I deliberately do not demand as a matter of course is the full audit report. Hardly any provider hands that over, and it does not have to. What is negotiable as a rule is a summary with the status of open nonconformities. Anyone who refuses that and at the same time advertises with the certificate is saying something by doing so.
The supplier nobody evaluates
There is one nonconformity I see very often: AI suppliers run along in general supplier management, and that prioritises by contract value. The provider of a foundation model costs less per month than the cleaning service and at the same time determines how your quotation review, your pre-selection or your document capture behaves.
It therefore falls through every grid that takes money as the yardstick. The guidance on A.10.3 therefore recommends distinguishing suppliers by type, by product supplied and by risk, not by invoice total. The guidance in Annex B lists how differently that can turn out: datasets, algorithms, models, individual software libraries through to the complete system that sits inside another product.
For practice this means: what a supplier costs is secondary. The question is how far its output feeds through into your decisions and how quickly you would notice if it tipped.
What has to go into the contract so that you get anything at all
Evidence that has not been agreed you will not get later. After signing, your negotiating position is weaker than before, and at the provider it is then support that decides, not sales.
The standard says the same from its own direction. ISO/IEC 42001 requires in A.10.2 that responsibilities in the life cycle be allocated between the organisation, partners, suppliers and customers, and in A.10.3 a process that ensures that the use of supplied services fits your own approach. Securing this contractually is your task, the standard does not prescribe the form. In ISO/IEC 27001 this corresponds to A.5.19 for supplier relationships and A.5.20 for what actually has to be in the agreements. And for personal data, Article 28 GDPR supplies a mandatory catalogue anyway, which includes the sub-processors and the duty to provide evidence.
For me, four points belong in every contract with an AI supplier: the right to request the documents mentioned annually and upon material changes; a duty to notify when the model version or a subcontractor changes; a deadline for responding to reported malfunctions; and consent to a supplier audit, at least as a remote audit. The last one costs you one round of negotiation and later saves you the discussion about whether you are allowed to ask at all.
When the supplier hands over nothing
That happens, and it is not always ill will. Large providers have standardised information packages and do not deviate from them, small ones simply have nothing in writing. Both are a result you can work with if you record it.
In such cases I write down what was requested, what came, what did not come and with what justification. This turns into a risk decision that someone takes by name, instead of a gap that belongs to nobody. Anyone who skips this step has not audited the supplier, only asked.
And then there is the third option, which is often the best for small and mid-sized companies: you audit yourself. A second-party audit at the supplier answers in two days questions to which a certificate never gives an answer, and it costs less than the damage that a silently swapped model causes in a year.
If you want to know which of your AI suppliers really need auditing and in what order, a supplier audit is the direct route to a robust answer.
To the supplier auditPrimary sources
Checking a supplier certificate robustly in ten minutes
Obtain the scope in its exact wording
Request the scope as a sentence, together with the issuing body and its accreditation. Without this sentence none of the following checks is possible.
Place it against your own service description
Put your contract or your requirements specification next to it. Does the scope name the activity, the site and the product line from which your service is delivered? If something differs, note the difference verbatim.
Check validity and point in time
A certificate is valid for a limited period and is based on an audit on a given date. Note the date of issue and the term, and ask when the last surveillance audit took place.
Request the Statement of Applicability for your case
Ask for at least the controls that concern your use case. Exclusions are permissible; read the justification, because it is the actual evidence.
Ask about the change notification
By which route and with how much notice do you learn of a change of model version or of a subcontractor? Without this point everything before it is a snapshot on one date with no updating.
Record the result as a decision
Write down what was requested, what came, what did not come and with what justification. This turns into a risk decision with a name under it instead of a gap that belongs to nobody.
Frequently asked questions
Is a supplier’s certificate sufficient as evidence?+
No. It proves that a body audited a defined scope at a point in time. Whether this scope includes the service you are buying is stated in the annex to the certificate. Request the scope in its exact wording and place it next to your own service description.
Does a supplier have to give me its audit report?+
No, and hardly any provider does. What is negotiable as a rule is a summary with the status of open nonconformities. Anyone who refuses even that and at the same time advertises with the certificate is itself making a statement that you can include in your risk decision.
How do I identify the AI supplier that is really critical?+
Not by contract value. The guidance on ISO/IEC 42001 A.10.3 recommends a distinction by type of supplier, product supplied and risk. The provider of a foundation model can cost less per month than the cleaning service and still determine how your quotation review behaves. Ask how far its output feeds through into your decisions.
What belongs in the contract for this?+
Four things: the right to request documents annually and upon material changes; a duty to notify when the model version or a subcontractor changes; a response deadline for reported malfunctions; and consent to a supplier audit, at least as a remote audit. After signing you will no longer get this.
Author & expert review: Lars Zimmermann · ISO/IEC 42001 Senior Lead Auditor & Senior Lead Implementer · ISO/IEC 27001 Lead Auditor & Lead Implementer (PECB)
Last updated: 10 November 2026. Researched and reviewed to the best of our knowledge; not a substitute for individual legal advice.
Questions about your own case?
In a free 15-minute intro call we assess where you stand on ISO 42001, ISO 27001 and the EU AI Act, honestly and without a sales pitch.