What to Do When Your EcoVadis Documents Are Not Accepted?

Updated: July 26, 2026

If your EcoVadis documents were not accepted, start by separating two different problems: a file or upload issue, and an evidence-quality issue. A file can fail because of format, size, password protection, readability, or document-limit rules. A document can also upload successfully and still receive little or no credit because it does not match what the analyst needs to verify.

This page is the immediate triage guide for situations where your EcoVadis document was not accepted, rejected, or failed during upload. It helps you check the technical rules first, then decide whether you need a deeper proof-rejection diagnosis, an evidence-gap review, or a specific Scorecard Inquiry question.

First, Clarify What “Not Accepted” Means

When people say their EcoVadis document was not accepted, they often mean one of three different things:

That distinction matters. A technical upload issue is fixed differently from an analyst not crediting evidence. A factual-error question is different again.

Technical Upload Checks for EcoVadis Documents

Start with the technical checks because they are usually fastest to confirm. These are the basic EcoVadis document upload rules to review before assuming the evidence itself is the problem. EcoVadis says supporting documents should be recent, relevant, complete, and related to the corresponding assessment scope. It also advises companies to prepare machine-readable documents where text can be selected or copied, and to avoid locked, encrypted, corrupted, scanned, or image-only files.

Analytical Evidence Checks: Why a Document May Upload but Still Not Count

If the file uploaded successfully, the next question is whether it was strong enough to support the answer. This is where many companies confuse “submitted” with “credited.” EcoVadis assesses documented evidence, and the document needs to match the question, scope, and evidence type.

1. Relevance mismatch

The document is on the right general topic, but it does not answer the specific question. For example, an Environmental Policy may support a policy question, while a KPI question needs performance data.

• What to do: Identify whether the question asks for a Policy, Action, or Result. Then match the document type to that need.

2. Outdated evidence

EcoVadis expects current evidence. Policies and actions normally have a longer validity window than KPI and reporting documents.

• What to do: Check the document type, issue or review date where applicable, reporting year, KPI period, and relevant validity period before upload. For policies, include an issue, approval or effective date and review information so it is clear that the policy is current. KPI and reporting evidence should clearly state the reporting period.

3. Credibility gap

The document may look informal, incomplete, or created only for the assessment. Screenshots, draft files, unlabelled spreadsheets, and unapproved documents can be hard to credit.

• What to do: Use official documents with a clear title, company identity, owner, approval or review status, and scope where possible. For policies, include an issue, approval or effective date and a clear review mechanism or review date. For internal exports and KPI evidence, add context such as system name, reporting period, responsible team, and company scope.

4. Scope mismatch

The evidence may relate to the wrong legal entity, site, business unit, parent company, subsidiary, or geography. Group-level evidence can be useful, but it needs to clearly apply to the entity being assessed.

• What to do: Check whether the document names the assessed entity or clearly states that it applies to that entity. Add explanation in the relevant questionnaire comment where scope could be unclear.

5. Findability problem

The evidence may be present, but difficult to locate in a long report, certificate pack, policy manual, or KPI dashboard.

• What to do: Use clear filenames, page references, section names, and concise comments. Make the analyst's job easier by pointing directly to the evidence.

Scorecard Inquiry or Reassessment Work?

Once you know whether the issue is technical or analytical, choose the right route. Not every document problem should become a Scorecard Inquiry. Some issues need a specific clarification question. Others need stronger evidence before the next reassessment.

Next Steps Checklist

Use this sequence when an EcoVadis document is not accepted or appears not to have been credited.

1. Confirm the problem type. Was it an upload problem, a document-limit issue, or an analytical evidence problem?
2. Check the technical rules. Review file size, format, password protection, readability, corruption, and whether unrelated documents were combined.
3. Check the evidence fit. Review relevance, date, credibility, scope, completeness, and findability.
4. Map the issue to the question. Identify the exact question code, evidence type, document name, and page reference.
5. Decide the route. Use Scorecard Inquiry only for specific clarification issues. Use reassessment planning for weak or missing evidence.
6. Fix the evidence library. Replace weak files, update expired evidence, clarify scope, and build a stronger evidence map for next time.

Frequently Asked Questions

Need an Answer?
Is there a part of the EcoVadis process you're stuck on? Click here to submit your question, and it could be featured in a future edition of The Answer.