Emission factors and their mappings collected via ESG Value Chain solution has very limiting restrictions compared to importing them through the regular routes.

More specifically, ESG Value Chain uses "Account" as the primary reference data, which seems reasonable, but forces "Spend type" to be assigned as a secondary one.

This means that collecting revenue intensity-based, account-wide and global emission factors to use for a each given account is impossible, unless an irrelevant spend type is assigned.

In many cases, forcing external suppliers to see and choose values from our internal spend types would be firstly confusing, and secondly might allow them to see confidential data from internal systems.

When importing emission factors with regular methods, user can define how many (1-4) reference data fields are used as factor mappings and what reference data tables should they refer to. I believe this functionality should be added to the ESG Value chain survey setup window, and these user inputs should carry over to the survey that the supplier sees and fills out.

This way ESG Value Chain would have more flexibility to suit different demands for different customers and different supplier relationships.