DNSH Appendix C under the EU Taxonomy: chemicals evidence
What is DNSH Appendix C under the EU Taxonomy?
Appendix C to Annexes I and II of Delegated Regulation (EU) 2021/2139 sets generic DNSH criteria for pollution prevention and control where an activity's technical screening criteria refer to that appendix. The Commission FAQ describes it as covering the use and presence of chemicals, especially substances of very high concern and other hazardous substances referred to in EU chemicals legislation.
A team should therefore start by checking the activity-specific technical screening criteria. Appendix C is relevant only when that activity points to it, for example through a pollution prevention and control DNSH criterion requiring compliance with Appendix C.
Confirm the exact economic activity and annex section before applying Appendix C.
Keep the Appendix C review tied to the activity's DNSH pollution prevention and control criterion.
Do not turn Appendix C into a generic chemicals policy claim unless the activity-specific criteria actually call it up.
DNSH Appendix C under the EU Taxonomy: chemicals evidence
Which substances are covered by the Appendix C amendments?
The 27 June 2023 amendments revised the former "essential use for society" derogation. For point (f), the Commission FAQ says the focus is substances identified as substances of very high concern under REACH Article 57 and Article 59 procedures; those substances are found on ECHA's candidate list.
The paragraph added after point (f) covers substances meeting CLP criteria for the hazard classes or hazard categories mentioned in REACH Article 57. The Commission notes that the ECHA classification and labelling inventory includes harmonised classifications and self-classifications, and that self-classified entries may differ between undertakings and are not currently subject to verification or quality control.
Check REACH SVHC status against the ECHA candidate list when point (f) is relevant.
Check CLP hazard classification for substances covered by the paragraph added after point (f).
Record whether the conclusion relies on a harmonised classification, a supplier classification, or another documented classification source.
Commission FAQs 134 and 135 distinguish SVHCs under REACH from CLP hazard classes and categories mentioned in REACH Article 57, and point readers to ECHA's candidate list and C&L inventory.
DNSH Appendix C under the EU Taxonomy: chemicals evidence
What evidence is needed for suitable alternatives and controlled conditions?
If a covered substance is present and an operator relies on the derogation, Appendix C is not satisfied by a bare statement that the substance is necessary. The Commission FAQ says operators have to assess and document that no other suitable alternative substances or technologies are available on the market and, if there are no such alternatives, that the substances are used under controlled conditions.
For suitable alternatives, the Commission FAQ treats an alternative as suitable only if it is safer, technically feasible, economically feasible for the operator, and available. For controlled conditions, the FAQ points to risk assessment and management processes that minimise emissions, exposures, and resulting risks in line with existing legal requirements.
Document the safer, technically feasible, economically feasible, and available tests for each rejected alternative.
Where a REACH Annex XIV authorisation is relied on, retain the authorisation number, authorisation decision, and required compliance documents.
For controlled conditions, retain the risk assessment, risk management measures, exposure and emissions controls, and evidence of compliance with relevant legal requirements.
Do not rely on the 'essential use' concept as the current Appendix C derogation test; the Commission FAQ says the current conditions remain absence of suitable alternatives and use under controlled conditions.
EU Taxonomy 2026 simplification: what should teams do?
What should teams do about EU Taxonomy 2026 simplification?
Start by identifying which simplification item is being discussed. The source pack supports one adopted 2026 item: Commission Delegated Regulation (EU) 2026/73, described as amending the Disclosures Delegated Act on the content and presentation of information to be disclosed and amending the Climate and Environmental delegated acts for certain DNSH technical screening criteria.
Do not turn that into a broad statement that EU Taxonomy reporting has been removed, that a new threshold applies, or that all 2026 usability proposals are already law. Keep the decision record tied to the exact source status, affected delegated act, affected disclosure or DNSH workflow, and evidence owner.
Confirm whether the question concerns the adopted Regulation (EU) 2026/73 or a later public-feedback item.
Map the change to Article 8 presentation/content, DNSH technical screening criteria, or both.
Keep existing Article 3 alignment checks in view: substantial contribution, DNSH, minimum safeguards, and applicable technical screening criteria.
Record any unsupported request for thresholds, dates, exemptions, or proposal details as an unresolved legal-content gap.
Grounds the continuing Article 3 criteria that simplification does not erase: substantial contribution, DNSH, minimum safeguards, and technical screening criteria.
EU Taxonomy 2026 simplification: what should teams do?
Does 2026 simplification change Article 8 reporting work?
The grounded answer is limited: the Commission page describes Regulation (EU) 2026/73 as simplifying the content and presentation of information disclosed concerning environmentally sustainable activities. It does not, in this source pack, support replacing the Article 8 scope analysis or removing the need to explain how and to what extent activities are associated with environmentally sustainable economic activities.
For implementation, keep the Article 8 population, activity mapping, KPI calculation files, and presentation templates under change control. Update the disclosure format only where the adopted simplification source and the current delegated-act text support the change.
Retain the source showing why a presentation or content change is allowed.
Keep numerator, denominator, eligibility, alignment, and limitation notes traceable to the reporting source used.
Do not remove Article 8 scope evidence merely because the presentation of disclosed information has been simplified.
Label management assumptions separately from adopted legal text.
EU Taxonomy 2026 simplification: what should teams do?
How should teams treat March 2026 usability proposals?
Do not implement a public-feedback item as if it were already binding. The Commission page lists public feedback open from 17 March 2026 until 14 April for proposed delegated regulations on enhancing the usability of technical screening criteria, and it states those items were not yet adopted and not in force until publication in the Official Journal.
Teams can track those items in a watchlist, but public copy, KPI changes, criteria changes, and assurance files should not present them as adopted unless a later source in the approved source pack supports that status.
Create a separate watchlist row for public-feedback items.
Do not change published Taxonomy claims based only on a not-yet-in-force proposal.
Capture the source status, feedback closing date, affected delegated act, and decision owner.
Escalate any request to cite proposal thresholds or final implementation dates because this source pack does not provide them.
EU Taxonomy 2026 simplification: what should teams do?
What evidence should be retained for 2026 simplification?
Keep a short evidence pack that can be read by reporting, legal, sustainability, product, and assurance teams without guessing which 2026 item was applied. The pack should show whether the change came from the adopted 2026 delegated regulation or from a monitored proposal that has not yet become binding.
For any activity-level conclusion, keep the core Taxonomy test visible. Article 3 still requires a substantial contribution, no significant harm to the other environmental objectives, minimum safeguards, and compliance with the technical screening criteria established by the Commission.
Source status record: adopted, public feedback, not yet in force, or unresolved.
Affected workflow: Article 8 content and presentation, DNSH technical screening criteria, or monitored usability proposal.
Current disclosure or criteria file before the change.
Approved change note with owner, reviewer, effective source, and review date.
Exception log for unsupported claims, missing final text, or requests to use proposal material as final law.
EU Taxonomy activity evidence packs: what to retain
What should teams do about EU Taxonomy activity evidence packs?
Create a separate evidence pack for each economic activity that may be reported as Taxonomy-eligible or Taxonomy-aligned. The Regulation defines an environmentally sustainable activity through a four-part test: substantial contribution to at least one environmental objective, no significant harm to the others, minimum safeguards, and compliance with the applicable technical screening criteria.
The pack should therefore start with the activity mapping and end with the disclosure consequence. A reviewer should be able to see the delegated-act activity description used, the objective assessed, the criteria applied, the facts checked, any limits on the conclusion, and whether the result affects turnover, CapEx, OpEx, GAR/GIR inputs, or only a qualitative explanation.
Map the business activity to the relevant Taxonomy activity description before testing alignment.
Separate eligibility evidence from alignment evidence so a listed activity is not mistaken for a compliant one.
Keep substantial-contribution, DNSH, minimum-safeguards, and technical-screening evidence in the same activity record.
Record whether the activity affects Article 8 turnover, CapEx, OpEx, financial-undertaking KPI inputs, or voluntary reporting only.
Name the owner, approver, source version, accounting period, and review trigger for each activity decision.
EU Taxonomy activity evidence packs: what to retain
What should each activity evidence pack contain?
A useful pack should be short enough to maintain but specific enough to support assurance. It should contain the source citation, the business facts used for the activity mapping, the criterion-by-criterion conclusion, the KPI treatment, and the unresolved questions that prevent or limit alignment.
For non-financial undertakings, Article 8 disclosures are tied to turnover, capital expenditure, and operating expenditure associated with environmentally sustainable activities. That makes traceability important: the evidence pack should connect operational facts and accounting treatment rather than leaving finance teams to infer the link at year end.
Activity boundary: product, service, asset, facility, project, counterparty, or revenue stream covered by the assessment.
Source basis: delegated act, annex, activity name or description, environmental objective, criteria version, and short quote.
Eligibility conclusion: why the activity is or is not described by an applicable delegated-act activity.
Alignment conclusion: evidence for substantial contribution, DNSH, minimum safeguards, and technical screening criteria.
KPI bridge: turnover, CapEx, OpEx, GAR/GIR input, or no KPI impact, with the accounting period and allocation method.
Review controls: evidence owner, approver, source refresh trigger, and exception note where data is incomplete.
EU Taxonomy activity evidence packs: what to retain
How should teams handle missing or partial evidence?
Do not fill evidence gaps with broad sustainability wording. If the activity is eligible but the team cannot demonstrate substantial contribution, DNSH, minimum safeguards, or a technical screening criterion, the pack should say which condition is unverified and keep the conclusion narrower.
The Taxonomy Regulation recognises that financial market participants may sometimes lack complete, reliable, and timely information for activities outside mandatory reporting. In those cases, complementary assessments and estimates must be limited, prudent, and explained. That principle is a useful control even for internal activity packs: estimates should be labelled, sourced, and separated from verified evidence.
Mark the activity as eligible only when the delegated-act description is met but alignment evidence is incomplete.
Do not count turnover as Taxonomy-aligned until the relevant alignment conclusion is supported.
For CapEx or OpEx, document the plan, measure, timing, allocation basis, and activity-level presentation before including it in the KPI numerator.
Keep estimates and management judgments separate from third-party records, accounting data, permits, technical test results, or supplier confirmations.
Escalate outdated delegated-act criteria, missing counterparty KPIs, unresolved DNSH tests, and minimum-safeguards red flags before publication.
EU Taxonomy activity evidence packs: what to retain
What is the most common mistake with EU Taxonomy activity evidence packs?
The common mistake is treating the evidence pack as a generic compliance checklist. That misses the point: Taxonomy reporting is activity-specific, criteria-specific, and KPI-sensitive. A pack that does not identify the activity, criteria, evidence, and disclosure impact will not reliably support a public KPI or an investor-facing explanation.
Another mistake is letting public sustainability claims drift away from the evidence record. The same pack should support the claim language, the Article 8 disclosure treatment, and the internal control conclusion, or it should clearly state why one of those uses is not supported.
Avoid activity packs that cite the Regulation but do not identify the delegated-act activity and criteria applied.
Avoid mixing eligible, aligned, potentially aligned, and voluntary information in one conclusion.
Avoid stale screenshots or private working notes when an external legal or Commission guidance URL is the source of the rule.
Avoid KPI allocations without the non-financial metric, accounting basis, and contextual explanation used to support them.
Avoid reusing a prior-year conclusion after delegated-act updates, business-model changes, new assets, supplier changes, or assurance findings.
Article 8 of Regulation (EU) 2020/852 applies to undertakings that are subject to the obligation to publish non-financial information under Article 19a or Article 29a of Directive 2013/34/EU. Those undertakings must include information on how and to what extent their activities are associated with economic activities that qualify as environmentally sustainable.
The practical scope decision should therefore begin with the reporting entity and consolidation boundary. If the undertaking is in scope, the next question is which disclosure route applies: non-financial undertaking KPIs under Annexes I and II of Commission Delegated Regulation (EU) 2021/2178, or the financial undertaking rules for asset managers, credit institutions, investment firms, and insurance or reinsurance undertakings.
Confirm whether the entity or group prepares non-financial information under Article 19a or consolidated non-financial information under Article 29a.
Classify the reporter as a non-financial undertaking or as the relevant type of financial undertaking before selecting KPI templates.
Document the reporting boundary separately from the later assessment of Taxonomy eligibility or Taxonomy alignment.
Which KPI framework applies once an undertaking is in scope?
For non-financial undertakings, Article 8(2) points to the proportion of turnover, capital expenditure, and operating expenditure related to assets or processes associated with environmentally sustainable economic activities. The Disclosures Delegated Act then requires those disclosures as specified in Annex I and presented using the templates in Annex II.
For financial undertakings, turnover, CapEx, and OpEx do not describe lending, investment, insurance, or similar financial activities in the same way. Commission Delegated Regulation (EU) 2021/2178 therefore provides separate KPI methodologies for asset managers, credit institutions, investment firms, and insurance or reinsurance undertakings.
Use turnover, CapEx, and OpEx KPIs for non-financial undertakings.
Use the relevant financial undertaking annexes for asset managers, credit institutions, investment firms, insurers, and reinsurers.
Do not treat activity eligibility as proof of alignment; eligibility means the activity is described in Taxonomy delegated acts, while alignment requires the Article 3 conditions.
The Disclosures Delegated Act requires additional disclosures accompanying the KPIs to appear in the same part of the non-financial statement as the indicators, or to be cross-referenced from that part. The same Article 8 provisions also require KPIs to cover the previous annual reporting period and to use the same currency as the financial statements.
That makes the evidence file more than a legal memo. It should tie the in-scope entity, financial statement currency, previous reporting period, chosen KPI route, and cross-references to the non-financial statement into one reviewable record.
Record where the Article 8 disclosures appear in the non-financial statement or consolidated non-financial statement.
Keep the previous annual reporting period and reporting currency consistent with the Article 8 disclosure basis.
Preserve cross-references to KPI tables, qualitative information, and any voluntary information that is kept separate from mandatory disclosures.
What evidence should teams keep for the Article 8 scope decision?
Keep evidence that explains why the entity is in scope, which undertaking type was used for the KPI framework, and how the disclosure record connects to the annual reporting package. A useful record should be readable by sustainability, finance, legal, and audit reviewers without relying on undocumented assumptions.
For financial undertakings, the record should also capture scope exclusions and numerator limits where relevant, such as the common Article 7 treatment for exposures to central governments, central banks, supranational issuers, derivatives, and undertakings not obliged to publish non-financial information.
Entity or group scope memo referencing Article 19a or Article 29a where applicable.
Undertaking classification memo: non-financial undertaking or specific financial undertaking type.
KPI route selection with annex references and template owner.
Disclosure placement record showing the non-financial statement section or cross-reference.
Evidence log for assumptions, voluntary disclosures, exclusions, and unresolved scope questions.
EU Taxonomy auditor evidence: what to keep for alignment review
What should teams do about auditor evidence under the EU Taxonomy Regulation?
Build the evidence file around the four alignment conditions in Article 3 of Regulation (EU) 2020/852: substantial contribution to at least one environmental objective, no significant harm to the other objectives, compliance with minimum safeguards, and compliance with the Commission's technical screening criteria.
Do not describe every review as a mandatory audit. The Commission's Climate Delegated Act notice says some technical screening criteria contain specific verification requirements for certain activities; where the criteria require verification, the external verifier's report is evidence of compliance. For other activities, the file still needs enough documentation to let a reviewer trace the eligibility, alignment, DNSH, safeguards, and KPI decisions.
Map the reported activity to the delegated-act activity description and environmental objective before collecting evidence.
Keep the technical screening criteria applied, the supporting data, and the conclusion for substantial contribution and DNSH in one review record.
Attach minimum-safeguards evidence that shows procedures aligned with Article 18 references to OECD Guidelines, UN Guiding Principles, ILO fundamental principles and rights, and the International Bill of Human Rights.
Add verifier reports only where the applicable technical screening criteria or activity-specific guidance requires external verification.
Clarifies that checking compliance with technical screening criteria requires collecting and assessing relevant information, and that verifier reports evidence compliance where verification is required.
EU Taxonomy auditor evidence: what to keep for alignment review
Which evidence belongs in a review-ready Taxonomy file?
A review-ready file should let a person who was not involved in the original assessment reproduce the conclusion. Start with the activity boundary and the applicable delegated-act criteria, then connect each data point to the published disclosure line or KPI value it supports.
For Article 8 reporting, non-financial undertakings disclose turnover, CapEx, and OpEx proportions associated with environmentally sustainable economic activities. The Disclosures Delegated Act also requires contextual information for financial undertakings, including scope, data sources, and limitations, so evidence should preserve the source and limitation story behind each KPI.
Activity scoping: legal entity, business line, activity description, objective, and applicable delegated act section.
Eligibility and alignment matrix: substantial-contribution criteria, DNSH criteria, minimum-safeguards check, and conclusion.
KPI support: turnover, CapEx, OpEx, GAR, GIR, or other applicable Article 8 calculation support, including allocation logic.
Data provenance: source systems, external data providers, study references, estimates used, and known data limitations.
Disclosure bridge: where each evidence item appears in the management report, sustainability statement, Taxonomy table, or narrative explanation.
Article 8 requires covered undertakings to disclose how and to what extent their activities are associated with environmentally sustainable economic activities.
EU Taxonomy auditor evidence: what to keep for alignment review
How should teams handle technical screening criteria and DNSH evidence?
Treat every technical screening criterion as an evidence requirement, even when the criterion does not prescribe a formal verifier. The Climate Delegated Act notice says compliance checking requires collecting and assessing relevant information; it also explains that all substantial-contribution criteria, DNSH criteria, and minimum social safeguards must be met for an activity to be considered Taxonomy-aligned.
Evidence depth should match the criterion. For example, the Commission notice discusses adequate evidence for building top-15-percent assessments, coherent adaptation plans for DNSH climate adaptation where climate risks are identified, and supplier information or testing for some Appendix C pollution-prevention checks.
Keep the exact criterion text or citation used for each activity and reporting period.
Record the data, certificate, technical study, supplier statement, test result, adaptation plan, or verifier report used to support each criterion.
Separate evidence for substantial contribution from DNSH evidence so a reviewer can see that both tests were performed.
Reassess dynamic criteria when criteria change or an activity falls out of compliance; do not rely on a stale historic conclusion for current alignment.
Provides practical interpretation on checking technical screening criteria, verification reports, adequate evidence for building benchmarks, adaptation-plan documentation, and Appendix C evidence examples.
Article 19 says technical screening criteria should facilitate verification of compliance and should be based on evidence, thresholds where possible, and life-cycle considerations.
EU Taxonomy auditor evidence: what to keep for alignment review
What is the most common mistake with Taxonomy auditor evidence?
The common mistake is presenting a broad sustainability policy as evidence for a specific Taxonomy-aligned activity. That does not show how the activity met the relevant technical screening criteria, DNSH checks, minimum safeguards, and KPI allocation rules.
A stronger file is narrower and more traceable: it names the activity, the criteria version, the reporting period, the data source, the calculation or allocation method, the reviewer, and the unresolved limitations. For CapEx allocated across mixed-use assets, the Commission notice says the allocation methodology should be based on verifiable evidence.
Avoid claiming external audit or assurance is required for every Taxonomy decision unless the applicable criterion or reporting rule says so.
Avoid unsupported allocations of mixed-use CapEx, OpEx, revenue, or assets; preserve the non-financial metric and methodology used.
Avoid relying on proxies where the Commission guidance says adequate evidence, a technical study, or the specified certificate is needed.
Avoid dropping data limitations from the final disclosure narrative when they affected the KPI or alignment conclusion.
Explains that CapEx allocation to Taxonomy-aligned activities should be accurate and based on verifiable evidence, with contextual information on allocation methodology.
Use the CapEx plan route only when the CapEx KPI numerator is relying on Annex I Section 1.1.2.2 point (b): expenditure that is part of a plan to expand Taxonomy-aligned activities or upgrade Taxonomy-eligible activities so they become Taxonomy-aligned.
Do not use the label for every sustainability budget. Annex I also has separate CapEx numerator routes for assets or processes already associated with Taxonomy-aligned activities and for certain purchases of Taxonomy-aligned output or individual measures. The file should identify which route is being used before the amount is reported.
Confirm the undertaking is reporting Article 8 turnover, CapEx, and OpEx KPIs.
Map the expenditure to a Taxonomy economic activity and environmental objective.
Classify the amount as already aligned CapEx, CapEx plan expenditure, or purchase of aligned output and individual measures.
Use the CapEx plan route for multi-period expansion or upgrade cases where the activity is expected to become Taxonomy-aligned.
Keep eligibility, alignment, DNSH, minimum safeguards, and CapEx-plan treatment separate in the evidence file.
Article 8 requires undertakings in scope to disclose how and to what extent their activities are associated with environmentally sustainable economic activities.