The compliance trigger

Under SGX Listing Rules, all companies listed on the Singapore Exchange have been required to report Scope 1 and Scope 2 emissions since FY2025. For the 30 constituents of the Straits Times Index, the obligation now extends to Scope 3: mandatory disclosure begins for financial years commencing on or after 1 January 2026. The August 2025 ACRA/SGX RegCo roadmap update explicitly retained this deadline while extending others. That signal is worth taking seriously.

The framework these companies must apply is IFRS S2, Singapore's ISSB-aligned climate disclosure standard, embedded directly into SGX Listing Rules. And with Singapore's carbon tax at effective this year — rising to by 2030 — supply chain emissions are on a trajectory toward material cost visibility. For listed companies with significant purchased goods and services, the Scope 3 figure is increasingly a number boards and investors care about in dollar terms, not just tonne terms.

FY2026 does not create a reporting problem for STI-30 companies. It creates a data problem — and those two challenges require entirely different solutions. Reporting skill cannot substitute for data infrastructure.

Why Scope 3 is structurally harder

Scope 1 and 2 emissions live within an organisation's operational boundary. The data sources are known, finite, and largely already exist within financial and facilities records. Scope 3 is a different problem entirely.

Category 1 — purchased goods and services — is typically the dominant Scope 3 category for Singapore's listed companies, and it lives entirely outside the organisation's operational control. Every supplier invoice represents a potential emissions data point. A mid-size STI constituent may have between 500 and 2,000 active suppliers. That is not a spreadsheet problem. That is a data infrastructure problem.

In most listed companies today, responsibility for assembling Scope 3 data sits somewhere between finance, procurement, and the sustainability team — with no single function having both the data access and the methodology expertise to do it properly. That gap is precisely where advisory firms are being asked to step in.

What audit-ready actually means

There is an important distinction between a Scope 3 number that appears in an annual report and one that can withstand independent verification. As assurance requirements approach, that distinction is becoming consequential for both companies and their advisors.

Audit-readiness in the Singapore context has four practical dimensions:

Traceable data lineage. Each emissions figure must be traceable from its source — whether a supplier-provided Product Carbon Footprint (PCF) or Environmental Product Declaration (EPD), an invoice-level activity calculation, or in limited cases a spend-based proxy — through the emission factor applied, to the final reported number. A figure that cannot be traced back to its underlying data does not meet this standard.

Methodology documentation. The calculation approach — including the emission factors used, their source, vintage, and applicability — must be documented and defensible. IFRS S2 notes that while primary supplier data is preferred, secondary data may be used, but the methodology must be explicit and consistently applied across reporting periods.

Category-level coverage. A single aggregate number does not satisfy IFRS S2 requirements. Individual categories must be assessed for materiality and reported accordingly.

Period-to-period consistency. Verifiers need to assess whether reported figures represent genuine emissions changes or methodological artefacts. Ad hoc spreadsheet processes cannot reliably provide this.

The GHG Protocol recognises several calculation methods for Scope 3, and they are not interchangeable. The most precise input is a Product Carbon Footprint (PCF) or Environmental Product Declaration (EPD) — supplier-provided, product-level carbon data specific to what was actually purchased. Where a PCF or EPD exists, it is used directly. Where it doesn't, activity-based calculation applies: invoice-level transaction data is mapped to the most specific emission factor available, reducing uncertainty to below 10 percent and preserving full data lineage. Spend-based proxies — which apply economy-wide emission intensity factors to procurement spend — are a last resort, used only where no PCF, EPD, or activity-based factor exists for a specific line item. Their uncertainty ranges can exceed 50 percent, and under IFRS S2's materiality thresholds, that uncertainty becomes a disclosure liability. Treating spend-based as a standard methodology rather than a fallback is one of the most common gaps in current Scope 3 practice.

Methodology comparison

Where current approaches break down

Three methods dominate current Scope 3 practice. Each has limits that Singapore's mandatory deadline will expose:

Spend-based proxies are fast and useful for initial baselines — but EEIO uncertainty is exposed under assurance and is not defensible as a primary method in a verified report.

Supplier survey consolidation captures genuine primary data where available, but response rates typically run 20–40%. The remaining 60–80% still requires a methodology, and supplier-provided figures are often spend-based themselves.

Spreadsheet aggregation is familiar to advisory teams but produces no data lineage for verifiers, doesn't scale to 500+ supplier relationships, and breaks period-to-period consistency.

Current approaches: where they stand

What FY2026 requires is a methodology that applies the most precise available data for every line item — PCF or EPD where it exists, activity-based where it doesn't, spend-based only as a genuine last resort — and produces full data lineage at each tier. Most current workflows don't operate that way. They default to spend-based across the board, or apply activity-based calculation inconsistently, without the systematic waterfall that verification requires.

The window

STI-30 constituents need verified Scope 3 data for their annual reports, typically published within four to five months of financial year end. That means data collection, calculation, and verification need to be substantially complete by Q3 2026 for December year-end companies.

Firms that have resolved the data infrastructure question become significantly more competitive for these mandates. Firms that haven't will be exposed in delivery — and the reputation consequences in Singapore's small, interconnected professional services community are asymmetric.

The engagement window is now. Not the next financial year.

Advisory firms and GHG verifiers seeking to understand how invoice-level activity data integrates with existing sustainability practice workflows are welcome to reach out directly.