Does the EU Value Chain Cap Apply to Banks, Customers and Procurement Platforms?

How reporting, lending, due diligence, product compliance and voluntary procurement purposes change the legal treatment of the same datapoint

A supplier may receive the same greenhouse-gas question from a customer, bank and platform. One request can sit inside Annex II, another can be outside the statutory cap but commercially important, and a third can be required by a separate legal regime. Treating the datapoint as inherently 'capped' or 'not capped' produces the wrong answer.

1. Identify the ultimate organisation that will use the data, not only the person or platform collecting it.

2. Ask which decision, report or legal obligation the information supports.

3. Separate CSRD sustainability reporting from lending, investment, due diligence, product compliance and voluntary procurement.

4. Confirm whether the respondent is a protected undertaking and which Annex II column applies.

5. Classify each datapoint and granularity separately; a mixed request can contain within-cap, above-cap and outside-cap lines.

6. Apply the relevant contract, legal basis, rights, notices and approvals to each purpose lane.

Figure 5. The same emissions datapoint can be within the cap for a customer's CSRD reporting, outside the cap for lending or due diligence, and subject to separate contract or legal controls. Purpose changes the treatment.

A bank can act as a CSRD reporting undertaking, a lender, an investor, a financial market participant or several of these at once. The request should therefore state the bank's role and purpose. Where the bank seeks information from a protected undertaking for the bank's own Article 19a or 29a sustainability reporting, the cap can apply. Where the bank seeks the same information for credit risk, pricing, loan monitoring or another financial-services obligation, the request is outside this statutory cap.

The directive covers information requested directly or indirectly. A platform cannot turn an above-cap CSRD request into a valid mandatory field merely by acting as an intermediary. Equally, the platform may collect information for several lawful purposes outside the cap. The configuration must therefore preserve purpose, requester and legal-basis metadata.

For an 8-employee supplier, the same Scope 1/2 datapoint is not in the special Annex II column. Even for a customer's CSRD purpose, it would therefore be above the cap, illustrating why purpose and employee band must be tested together.

A procurement platform collects energy, GHG, grievance and product-compliance data for a large retailer. The retailer confirms that energy and GHG support its CSRD report, grievance data support due diligence, and product information supports market-access compliance. The supplier has 75 employees.

The platform maps energy and GHG to Annex II and marks them potentially within cap; grievance and product fields are labelled outside the statutory cap with their separate legal/contract basis. A transition-plan request is marked above cap and voluntary, with the right-to-decline notice. The supplier can now make a controlled line-by-line response instead of treating the whole questionnaire as one legal category.

Classifying the request from the requester's industry rather than its legal role and purpose.

Assuming banks are always outside the cap or always entitled to the full Comprehensive Module.

Failing to separate a bank's CSRD reporting from credit-risk use.

Treating due-diligence or product-compliance requests as capped because the datapoint also appears in Annex I.

Using a procurement platform's 'mandatory' setting as evidence of a legal duty.

Bundling several purposes without line-level labels and notices.

Ignoring data-sharing, confidentiality and permitted-use controls when one platform serves multiple customers.