
A mid-size supplier selling into several industries can spend a significant share of its reporting effort filling out near-identical ESG questionnaires for different customers, banks and exchanges, each one asking for the same electricity use, fuel consumption or emissions figures in a slightly different format.
Interoperable ESG data solves this: one record, captured once in a common format, that every recipient can read and reuse without the supplier re-entering it each time.
In practice this means the same figure for a supplier's electricity use or Scope 1 and 2 (direct and purchased-energy) emissions could flow into a customer's Scope 3 report, a bank's financed-emissions calculation, and an exchange's disclosure portal, all from a single source record. Today that rarely happens, because each recipient defines metrics, categories and submission formats slightly differently.
Summary
- Duplicate reporting happens because the underlying data is the same but each recipient's format, metric definitions and submission method differ.
- Interoperability requires three things together: common metrics and shared definitions, machine-readable exchange, and permissioned access controlled by the supplier.
- Global sustainability standards and frameworks, including ISSB (International Sustainability Standards Board), the GHG Protocol, SGX Core ESG metrics and the Project Savannah MSME baseline proposal, give data a common reference point without forcing one single format on everyone.
- A worked example follows one supplier's emissions record through four different destinations, a customer, a bank, an exchange and a government register, to show what changes when that record is interoperable versus when it is not.
- Making "report once, reuse everywhere" the default depends on infrastructure decisions, usually made by governments, exchanges or standard-setters, not by any single supplier or buyer.

Why Does the Same Supplier Get Asked for ESG Data Repeatedly?
A supplier's own emissions sit inside its customers' Scope 3 (value chain) inventories and its lenders' financed emissions, which is why so many different parties ask for the same figures. A large enterprise customer wants the data for its own Scope 3 inventory.
A bank wants it to calculate financed emissions on a loan. An exchange wants it because the supplier is itself listed, or because a listed customer needs it for its own disclosure. The underlying facts are the same each time; the request is not.
Each recipient usually asks in a different way. One uses a PDF questionnaire built around its own internal categories. Another uses a procurement portal with its own metric names.
A bank's request is typically built around its lending exposure rather than a supplier's production volumes. None of these differences reflect genuinely different facts, they reflect incompatible formats layered on top of the same facts.
The GHG Protocol's Scope 3 category 1 technical guidance lists four calculation methods, supplier-specific, hybrid, average-data and spend-based, "in order of how specific the calculation is to the individual supplier", and states that companies "need not always use the most specific method as a first preference."
A supplier that readily hands over operational data to one customer may face another buyer working from spend-based estimates who never asks for the underlying record at all. The data exists; a shared channel for it does not.
What does ESG data interoperability actually mean?
Interoperability means three conditions are satisfied together, not just one of them in isolation.
- Common metrics and shared definitions. "Scope 1 emissions" or "energy consumption" must mean the same thing, measured the same way, regardless of who is asking. The GHG Protocol supplies the methodology for measuring emissions; ISSB sets out what climate-related information gets disclosed to investors.
- Machine-readable exchange. The data needs to move as structured, taggable fields, not as free text buried in a PDF. API-based integrations and shared data schemas can automate the flow of supplier sustainability data across supply chains, rather than relying on manual re-entry at each destination.
- Permissioned access. The supplier, not the platform or the recipient, controls who can see which fields. A bank might need aggregate emissions by facility to feed into its own calculation process; a customer might need line-item detail by product. Role-based access lets one record serve both without the supplier maintaining two versions.
The two connect. Under IFRS S2 paragraph 29(a)(ii), an entity measures its emissions in line with the GHG Protocol Corporate Standard unless a jurisdictional authority or listing exchange requires a different method. That link between measurement and disclosure is what lets one emissions figure satisfy more than one reporting obligation.
What happens to one emissions record across four destinations?
A Singapore-based components manufacturer records its monthly electricity consumption and calculates Scope 1 and 2 emissions once, in CO2e, the unit that expresses every greenhouse gas as the equivalent warming effect of carbon dioxide. That single record then needs to reach four different recipients.
| Destination | What they need | What changes if the data is interoperable |
|---|---|---|
| Enterprise customer (Scope 3 Category 1, purchased goods and services) | Supplier-specific emissions data mapped to this GHG Protocol category | The customer pulls the same record instead of commissioning a separate supplier questionnaire |
| Bank (financed emissions) | Emissions data attributable to its loan exposure, consistent with the measurement basis used elsewhere | The bank can use the supplier's disclosed figure as one data point within its own financed-emissions methodology, rather than relying solely on sector-average estimates |
| Stock exchange (listed entity disclosure) | Metrics aligned to SGX Core ESG metrics or equivalent exchange disclosure requirements | The same underlying figure is reformatted automatically to the exchange's required fields |
| Government or sector register | MSME-level (micro, small and medium enterprise) baseline metrics, such as those proposed in the Project Savannah 2024 white paper | The record satisfies a baseline submission without a separate data-entry exercise |
Project Savannah, the UNDP, GLEIF and MAS initiative, published its white paper in March 2024, proposing a baseline metrics set for MSMEs. It explicitly states it does not introduce a standard that diverges from existing ones.
It is a reference point for what a minimum, interoperable MSME data set could look like, not a mandatory reporting regime in force today.
How do global standards like ISSB and the GHG Protocol enable this?
None of these standards eliminate the need for translation between formats, but they narrow what has to be translated.
If every recipient's definition of Scope 1 and 2 traces back to the same GHG Protocol methodology, and every climate disclosure traces back to ISSB's disclosure requirements, the underlying number does not need to be recalculated for each audience, only re-presented.
SGX Core ESG metrics give listed entities and their suppliers a defined, exchange-level metric set to work from.
Singapore companies apply the ISSB standards through SFRS(I) S1 and S2, the local adoption of the international standards, on a phased timetable that varies by type of entity. A supplier reporting into this structure is reporting against a baseline many other recipients already recognise.
Interoperability is an infrastructure property, not a feature any one platform can add on its own. It requires common definitions, structured data exchange and permissioning operating together, across every party that touches the record, not just one vendor's interface.
What does it take for "report once, reuse everywhere" to become the default?
Three conditions tend to recur where this has started to work at scale.
- A common reference infrastructure. A government, exchange or regulator adopts a shared data layer that multiple reporting obligations can draw from, rather than each regulator building its own closed portal.
- Automated data capture at the source. Integrations with utility providers, government databases and accounting systems reduce how much a supplier has to type into any form at all, because the record is pulled rather than submitted.
- Supplier-controlled permissions. The supplier decides which recipients see which fields, so broader data reuse does not mean giving every counterparty full visibility into the underlying record.
A supplier evaluating where to start should prioritise getting one governed record right before worrying about how many destinations it eventually reaches. This trade-off means slower expansion to additional recipients at first, but a more reliable foundation once that record is shared more widely.
Shared definitions and automated capture matter more at the outset than permissioning detail, which can be refined once the record itself is trustworthy.
How to Start
A supplier facing repeat requests for the same data should start by establishing one governed emissions record, measured consistently, rather than maintaining separate figures for each recipient. From there, the question becomes whether that record can be shared under permissioned access instead of re-entered manually each time.
Frequently Asked Questions
Does interoperable data mean giving every buyer the same level of access?
No. Role-based permissions let a supplier share summary figures with one recipient and detailed, line-item data with another, from the same underlying record.
Is Project Savannah a mandatory reporting standard for SMEs today?
No. Its March 2024 white paper proposes a baseline metrics set for MSMEs and states explicitly that it does not introduce a divergent standard. It is not in force as a compliance requirement.
Can a small supplier outside Singapore benefit from this kind of infrastructure?
Yes, where a supplier sits inside a larger customer's reporting boundary under global reporting regulations, reusable, well-defined data reduces the number of separate submissions that customer or its financiers require.
References
- IFRS S2 Climate-Related Disclosures (2024)
- GHG Protocol Corporate Accounting and Reporting Standard (2004)
- GHG Protocol Corporate Value Chain (Scope 3) Accounting and Reporting Standard (2011)
- Project Savannah White Paper (March 2024)
- ACRA and SGX RegCo Updated SGX Core ESG Metrics and Revised Timeline (August 2025)
