Every EINF must undergo independent verification by an authorised assurance provider before it is approved by the board and filed with the annual accounts. Good EINF audit preparation makes the difference between a smooth review and weeks of back-and-forth. Companies that treat verification as a project with owners, evidence and deadlines avoid late corrections and give the board a report it can sign with confidence.
This guide explains what verifiers look at, where reports usually fail, how to build an evidence pack and how to organise the weeks before filing. If you need the basics first, start with our guide on what the EINF is and who must file it.
What auditors verify
Under Law 11/2018 the EINF currently requires limited assurance. That is a moderate level of confidence, less demanding than a financial audit, but the verifier still needs documentation for what you report. The review covers four questions:
- Completeness: does the report address all five EINF pillars (environment, social and employee matters, human rights, anti-corruption and bribery, and diversity)? Are the mandatory data points included?
- Accuracy: do the reported figures match the source documentation? Are calculations and methodologies applied correctly?
- Consistency: do numbers align internally (for example, total headcount versus the breakdown by gender, age and contract type) and with the financial statements?
- Compliance: does the report meet the content requirements of Law 11/2018?
Verifiers also check that the reporting boundary is clearly defined. If your group has subsidiaries, joint ventures or facilities abroad, they will ask which entities are included, why, and whether each pillar uses the same boundary. A consolidated EINF only exempts a subsidiary if it actually covers that subsidiary’s operations and data.
How verifiers work in practice
Expect three types of request. First, walkthroughs: interviews with the people who produce each metric, to understand how the number was built. Second, sample testing: the verifier picks specific data points (a month of electricity invoices, a set of payroll records, a training log) and asks for the documents behind them. Third, analytical review: large changes against the previous year will be questioned, so prepare a short explanation for every significant variance before it is asked.
Common findings
These are the findings we see most often when companies prepare their EINF:
- Missing evidence: data reported without supporting documentation, or with documents that cannot be located when the sample request arrives.
- Calculation errors: emission factors applied incorrectly, wrong unit conversions (kWh versus MWh, litres versus m³) or factors from the wrong year.
- Scope gaps: facilities, subsidiaries or vehicle fleets left out of the reporting boundary without explanation.
- Stale data: previous year’s figures reused without justification.
- Policies without outcomes: describing a diversity or anti-corruption policy without the metrics that show its results.
- No year-over-year comparison: verifiers and readers expect trend data; if this is your first year, say so clearly.
All of these are avoidable. The key is treating evidence management as a continuous process rather than a last-minute exercise.
Who owns what
A verification goes faster when every data point has a named owner who can answer questions. A typical split looks like this:
| Pillar | Typical data owner | Examples of evidence |
|---|---|---|
| Environment | Operations, facilities, fleet | Energy and fuel invoices, meter readings, waste records, water bills |
| Social and employees | HR, health and safety | Payroll and headcount extracts, accident registers, training records |
| Human rights | Compliance, procurement | Due diligence procedures, supplier assessments, grievance channel logs |
| Anti-corruption | Legal, compliance | Code of conduct, training completion, whistleblowing records |
| Diversity | Company secretary, HR | Board composition, diversity policy, pay data by gender and category |
The sustainability team coordinates, but it should not be the only point of contact. If only one person can explain how a number was built, the verification stalls when that person is unavailable.
Building your evidence pack
For each data point, prepare three things:
- The source document: invoice, HR extract, meter reading, signed policy.
- The calculation methodology: emission factors used and their source, allocation rules, conversions and any estimates (with the reason for estimating).
- The approval trail: who provided the data, who validated it and when.
Organising the evidence by EINF pillar makes it easier for verifiers to navigate and reduces clarification requests. Use the same names and indicator codes in the report and in the evidence folders, so that every figure in the draft points to exactly one file.
Pre-verification checklist
Before you send the draft to your verifier, check that:
- The reporting boundary is documented and applied consistently across all five pillars.
- Every quantitative figure has a source document and a named owner.
- Emission factors are listed with their source and year, following a recognised methodology such as the GHG Protocol.
- Headcount totals match across the employee section, the diversity section and the financial statements.
- Significant changes against last year have a written explanation.
- Estimates are flagged, with the method and the reason.
- Qualitative sections describe policies, risks and results, not policies alone.
- Management has reviewed the draft and knows the board approval date.
Timeline
Start preparing at least 8 weeks before your planned filing date, and earlier if this is your first EINF:
- Weeks 1–4: data collection and internal review, including variance explanations.
- Weeks 5–6: draft report review with management and data owners.
- Weeks 7–8: external verification, answers to sample requests and final corrections.
The EINF is approved by the board and filed alongside the annual accounts as part of the management report, so the verification must fit inside your financial closing calendar, not after it. Our step-by-step guide on how to prepare an EINF report covers the earlier phases in more detail.
Companies preparing for CSRD reporting should keep the same habits. Assurance under the CSRD is also limited, and the evidence logic is identical, so a well-documented EINF is the best starting point.
How Dcycle helps
In EINF and GRI projects with our clients, the hardest part of verification is rarely the calculation itself; it is finding the document behind a number months after it was entered. Dcycle links every data point to its source file, calculation log and approval chain, so when your verifier requests evidence for a metric you can share it in one click. With automated data collection, invoices and spreadsheets are read and classified on upload, which keeps the methodology consistent between periods, and evidence traceability keeps the audit trail in the same place as the report. Request a demo to see how it works with your own data.
Frequently asked questions (FAQs)
Is verification of the EINF mandatory?
Yes. Law 11/2018 requires the EINF to be verified by an independent assurance provider. The current level is limited assurance, which still requires solid documentation for every figure you report.
What is the difference between limited and reasonable assurance?
Limited assurance gives a moderate level of confidence that the information is free from material misstatement. Reasonable assurance is closer to a financial audit and involves more extensive testing. The EINF currently requires limited assurance.
How early should we start preparing for verification?
Plan for at least eight weeks before the filing date, and more if it is your first EINF or your data sits in many systems. Data collection is usually what takes longest.
What should we do if a figure has to be estimated?
Flag it as an estimate in the report, document the method and the reason, and keep the inputs. Verifiers generally accept reasonable estimates when they are transparent and applied consistently.
