Most ESG conversations in Malaysian businesses right now are about reporting.
Which framework. Which disclosures. Which transition reliefs. Whether the FY2026 filing will be ready on time. Whether Scope 3 data can be assembled before the 2027 requirements arrive.
These are real questions. But they sit on top of a more fundamental one that rarely gets asked in the same room.
The reporting cycle is not where ESG succeeds or fails. It is only where the underlying system becomes visible.
If a business is struggling to produce its sustainability disclosure, the reporting process is not usually what is broken. The business is running on operational systems that were not built to capture what ESG now requires, and the reporting cycle is where that mismatch finally shows up.
This is the ESG data infrastructure gap. And it is why most of the effort currently going into reporting improvements produces smaller returns than expected.
What infrastructure means in this context
When we say ESG data infrastructure, we do not mean a reporting platform or a disclosure template.
We mean the underlying systems that run the business every day — the ERP that tracks purchasing and inventory, the accounting system that records expenses, the HR system that holds workforce data, the operational tools that log energy use, fleet movement, and procurement decisions.
These systems are where ESG-relevant data originates. They record what the business actually does. Energy consumption sits in utility records. Purchase emissions originate in procurement. Workforce metrics live in HR. Governance records are created by how the business operates, not by the sustainability team reviewing it later.
Reporting sits downstream of all of this. A report is an organised summary of what the operational systems have already captured.
When the operational systems are set up to capture the right data at the right granularity, reporting becomes an extraction problem. When they are not, reporting becomes an assembly problem — and an assembly problem gets harder, not easier, every year.
This is the distinction that matters. Reporting improvements optimise the assembly step. Infrastructure improvements make the assembly step unnecessary.
Why the reporting-first approach hits a ceiling
Businesses that build the report first tend to follow a predictable pattern.
In year one, a small team is assigned responsibility. Data is collected through spreadsheets, email requests, and manual reconciliation across departments. The report gets produced. It is imperfect but it is filed.
In year two, the same team is asked to produce a better report with more detail. The manual effort from year one does not scale, so tools get added. A sustainability reporting platform. A carbon accounting tool. A consultant engagement to support the heavier sections.
By year three, the business has a reporting capability but still does not have reporting ease. Each cycle still requires coordination across departments that do not share a data structure. New disclosure requirements still require new manual processes to capture what was not captured before. The cost of the reporting cycle keeps rising even as the reports themselves get marginally better.
This is the ceiling. The underlying operational systems were not designed to produce ESG data as a native output, so every reporting cycle is still an assembly exercise, just with better tools attached.
Breaking through that ceiling requires a different decision. Not a better reporting tool, but a different relationship between the operational systems and the reporting output.
Why this matters more in 2026 than it did in 2024
Two shifts have happened in the Malaysian context that change the cost of getting this wrong.
The first is the National Sustainability Reporting Framework. FY2026 is the first mandatory IFRS S2 climate reporting year for Group 2 Main Market issuers outside the RM2 billion market cap tier. ACE Market issuers and large non-listed companies follow in FY2027. The regulatory floor has moved, and it will keep moving — external assurance requirements begin phasing in from 2027.
The second is the ripple into the supply chain. Scope 3 reporting requirements mean that listed companies are now asking their suppliers — many of which are SMEs — for emissions and governance data as a condition of the commercial relationship. SMEs are not mandated to produce an ISSB-aligned report, but they are increasingly expected to answer questions that presume the underlying data exists.
Both shifts make the reporting cycle heavier every year. Both shifts expose the infrastructure gap earlier and more publicly than before.
The businesses that treated ESG as a reporting problem in 2022 are finding that 2026 is when the approach stops working. The businesses that treated it as an infrastructure problem are finding that each additional requirement lands on a system that was already designed to absorb it.
The cost of the gap is rarely where businesses expect it
The most common assumption is that ESG data gaps create compliance exposure. They do. But the compliance cost is usually the smallest part of the total cost.
The larger costs sit in commercial and financial relationships that are quietly sensitive to ESG data quality.
Lending terms. Financial institutions now factor climate data into how they classify lending exposure. Weak data from a borrower affects how the lender reports that exposure upstream. Over time, this shapes pricing and availability of credit — not through a formal ESG penalty, but through how the risk is categorised.
Supplier positions. Listed companies preparing Scope 3 disclosures are actively reviewing their supplier base. Suppliers that can produce structured emissions data keep their positions. Suppliers that cannot are quietly replaced at the next renewal — often without the ESG reason being stated explicitly.
Investor scrutiny. Institutional investors read ESG data as a proxy for management quality. Poor data is read as poor operational discipline, which shapes valuation conversations long before it shapes disclosure conversations.
Carbon tax readiness. As carbon pricing mechanisms expand across the region, the ability to measure what you emit determines what you pay. Businesses that cannot measure accurately cannot optimise — they absorb whatever the default calculation produces.
None of these costs show up in an audit finding. They show up in the lending review, the supplier renewal, the funding round, the tax return. By the time the pattern is visible, the underlying gap has usually been in place for 18 to 24 months.
A note on where this leads
The reason ESG data infrastructure matters is that the operational systems doing the capturing are the same systems that run the rest of the business. Finance, operations, HR, procurement, inventory. If those systems already work as one connected platform, ESG data becomes a natural output. If they do not, ESG becomes one more reporting silo on top of the silos that already exist.
This is the deeper version of the ERP conversation. Most businesses treat ERP modernisation and ESG readiness as separate projects. They are, increasingly, the same project seen from two angles.
At Wiz.Asia, this is the work we do. We implement Odoo as a unified business system across finance, operations, HR, and inventory, with the structure to capture the data ESG now requires as part of normal operations. Not as an ESG tool bolted on, but as the infrastructure underneath.
If your reporting cycle is currently the place where your infrastructure gap is becoming visible, the next question is which risks that gap is actually exposing — and how fast they move.