How to Respond to an Above-Cap Sustainability Data Request Without Damaging the Customer Relationship

The value chain cap is designed to protect smaller value-chain undertakings from disproportionate sustainability reporting requests. That protection is meaningful: a protected undertaking has a statutory right to decline information above the voluntary-standard limits when the request is made for Accounting Directive sustainability reporting. But a practical request rarely arrives as a perfectly labelled list of Annex II datapoints.

A customer workbook may combine reporting data, procurement criteria, due-diligence questions, product information and voluntary supplier-development topics. Some questions may be duplicates, some may be within the cap, and some may be outside the cap’s purpose. A broad refusal can therefore be legally imprecise and commercially damaging. The stronger response identifies the exact issue and offers a proportionate next step.

Figure 1. Five response paths can preserve both statutory protection and the commercial relationship when purpose and scope are verified first. London Reporting Academy learning visual.

The legal test is not simply “small company” or “SME”. The undertaking must be in the value chain of a reporting undertaking and must not exceed, on its balance-sheet date, an average number of 1,000 employees during the preceding financial year. The relevant entity and group basis should be confirmed before the response relies on the protection.

Keep a current self-declaration or internal status memo with the legal entity name, reporting undertaking or relationship, employee measure, period, basis, approver and expiry. If the request concerns a parent, subsidiary or group that is different from the entity issuing the declaration, resolve that boundary first.

The right to decline is linked to a request made for sustainability reporting required by the Accounting Directive. Ask the customer to state whether each disputed item is needed for that purpose. If the workbook also serves due diligence, risk management, procurement, product compliance or another purpose, the fields should be separated or purpose-tagged.

This does not mean that a different-purpose request is automatically mandatory. It means the value-chain-cap conclusion is not the end of the analysis. The supplier should then assess the relevant law, contract, commercial need, confidentiality, feasibility and proportionality on their own terms.

The delegated regulation states that the cap comprises only the datapoints listed in Annex II. A question can appear in the voluntary standard and still be outside the cap. It can also combine one capped datapoint with several additional fields. Map the request to the exact B or C datapoint, employee band, period, boundary and requested level of detail.

Option 1: Clarify the request

Clarification is appropriate where purpose, entity, period, unit, evidence need or duplication is unclear. It is often the fastest way to remove an apparent above-cap issue. Ask the customer to identify the reporting purpose, distinguish required from optional questions, confirm whether a consolidated answer is acceptable and explain why the additional detail is needed.

Option 2: Decline the identified excess

A decline should be precise. Identify the exact questions or data elements, state that they exceed the applicable voluntary-standard cap for the stated reporting purpose, refer to the protected-undertaking right, and answer the within-cap questions normally. Avoid accusing the customer of misconduct unless legal advice supports that conclusion.

Option 3: Provide selected information voluntarily

The Directive does not prohibit voluntary sharing. A supplier may decide that a particular additional answer is low-cost, already public, commonly shared in the sector or valuable to the relationship. The decision should be explicit rather than accidental. Record what is provided, why, to whom, for which period and purpose, under what confidentiality terms, and whether future provision will be reassessed.

Option 4: Negotiate a narrower scope or alternative

The customer may not need the precise form requested. A group-level estimate, percentage range, site sample, redacted policy, assurance statement, evidence index or methodology description may satisfy the underlying need. The supplier should ask which decision the information supports and offer the least burdensome reliable alternative.

Option 5: Phase the data

A phased response is appropriate where the information is commercially useful but the organisation cannot produce it reliably today. Agree what can be supplied now, what method will be developed, who owns the work, the target period, dependencies and whether the commitment is best-efforts or contractual. Do not promise a precision or date that the data owner has not approved.

The statutory analysis should not be left to the account manager, and the commercial relationship should not be decided by legal or reporting teams alone. Establish a small approval model that combines the request owner, reporting owner, data owner, commercial owner and legal/privacy support where relevant.

A voluntary-provision register protects both sides. It demonstrates that the supplier made a deliberate, approved choice and helps the customer understand the limits of the answer. It also prevents a one-off response from quietly becoming an uncontrolled annual expectation.

Context. Solent Fasteners has 170 employees and supplies a large listed manufacturer. The customer asks for the Annex II emissions datapoint, plus product carbon footprints for 600 SKUs, site-level climate scenarios and all renewable-energy contracts. The stated purpose is the customer’s Accounting Directive sustainability report and supplier programme.

Assessment. Solent confirms protected status and separates the purposes. The undertaking-level estimated gross emissions datapoint is within the cap for its employee band. The SKU footprints, scenarios and contracts are not Annex II datapoints as requested. The customer also confirms that the supplier programme uses some of the information for procurement, a different purpose.

Response. Solent provides the emissions datapoint and method. It declines unrestricted contract disclosure, offers a redacted renewable-energy summary, and proposes a voluntary pilot footprint for ten material SKUs under an NDA. It declines the site scenarios for the current year but offers a phased climate-risk assessment. The email clearly separates the reporting-purpose right from the voluntarily negotiated procurement support.

Outcome. The customer accepts the mapped response because it receives reliable information and a clear improvement plan. Solent records the voluntary pilot, cost owner, confidentiality conditions and future reassessment instead of allowing the request to become an undocumented precedent.

Questionnaire operations: How to Answer Customer and Bank ESG Questionnaires Using the EU Voluntary Standard.

Requester redesign: How Large Companies Should Redesign Supplier ESG Questionnaires Around the Value Chain Cap.

Status evidence: Protected Undertaking Self-Declaration: What Suppliers and Requesters Should Document.

Publication channels: Must an EU Voluntary Sustainability Report Be Public?