What Your CFO Should Demand from Your ESG Tool
Last week, we laid the groundwork: what ESG software is, and why a non-financial ERP truly changes the game for executive management. But there's still one question to address: what should the CFO, who drives value, deals with banks, and signs off on budgets, demand from the tool they're presented with? Our answer in 4 concrete requirements.
Temps de lecture estimé : X min
What Your CFO Should Demand from Your ESG Tool
Why Finance Teams Are Underserved by Existing Tools
There's an irony in the current state of ESG tools. The audience with the most to lose from poor non-financial data infrastructure – the Chief Financial Officer – is also the one these tools address least directly.
Most ESG solutions on the market were designed for CSR teams. Their logic is document-centric: collecting, consolidating, formatting, and publishing. They are good tools for producing a report, but not for strategic management.
However, for a CFO, the question isn't "how are we going to publish our CSRD report?" It's: "what metrics am I using to drive an increasing portion of this company's value?"
Today, 60 to 70% of the value of a mid-sized or large company is non-financial: human capital, reputation, climate footprint, supplier relations, governance. If this value isn't structured within an adequate information system, the CFO is operating with a blind spot.
What the CFO Cannot Accept
Data That Only Exists at Reporting Time
In a financial ERP, accounting data is continuously available within the system. It can be queried at any time. It feeds financial controlling, treasury management, and investment decisions, not just the annual balance sheet.
A standard ESG software operates the opposite way: data is imported or entered in an annual cycle to produce a document. We detailed this distinction in a previous article — what this difference truly changes. The following goes a step further: what the CFO should specifically demand from it.
Between campaigns, the data isn't live. It doesn't provide alerts. It doesn't feed any management dashboard.
For a CFO, this is unacceptable. You wouldn't manage your cash flow based on an annual snapshot. Why manage your carbon risk, social exposure, or supplier compliance on that basis?
Reconstructed traceability, not native
In your financial ERP, an auditor can trace any figure back to its source in a few clicks. Traceability is native, not manually reconstructed before each closing.
Most ESG tools do not guarantee this level of rigor. Who entered what, using which methodology, on what date? These questions too often require laborious answers — Excel files found in email inboxes, scattered notes, exports that don't exactly match published figures.
Now, with CSRD, your non-financial data is subject to verification by an independent third party. The level of rigor is that of an audit. Your tool must be up to the task.
Data that doesn't communicate with your financial systems
A non-financial ERP must be able to communicate with your financial ERP, your HRIS, and your procurement management tools. Only then will your ESG data become actionable for the decisions the CFO needs to make: investment prioritization, dialogue with investors, and preparation for risk committees.
An ESG tool that operates in a silo reproduces exactly the problem it is supposed to solve. The data exists somewhere, but it remains unusable for the finance department.
Data hosted outside France, without sovereignty guarantees
For a CFO of a mid-sized or large French company, data sovereignty is not a secondary technical issue. It's a governance question: who accesses your non-financial data, in which country, and under what rules?
Some market players host their data in non-European environments. In a context of increasing pressure from regulators and investors on the quality and confidentiality of published information, this is a risk that financial management cannot take lightly.
What the CFO should demand instead
1. A single source of truth for non-financial data
Just as your financial ERP is the single source of truth for accounting data, your ESG tool must be the single source of truth for your non-financial data. Every indicator, whether it's scope 3 emissions, accident rates, energy consumption per site, exposure to physical climate risks, or anything else, must be defined with a precise methodology, an identified source, an update frequency, and a designated owner.
The same data must feed both your non-financial reports, your response to an investor questionnaire, and your management dashboard. If not, you'll have multiple versions of the truth, and none will be truly reliable.
2. Permanent access to information, not just during reporting cycles
The CFO should be able to query the carbon performance of a business line just as they would query a gross margin. Track carbon intensity by revenue stream, quarter by quarter. See in real-time which sites are exceeding their energy consumption targets. Monitor compliance risks without waiting for the next annual cycle.
This is what a non-financial ERP offers: live data, continuously queryable, not just an annual snapshot.
3. Native traceability, guaranteed auditability
Your tool must allow tracing the origin of any indicator at any time, without reconstruction work. This is not just a requirement from the OTI under the CSRD. It is a governance requirement for any financial department that takes the quality of its data seriously.
4. Sovereign hosting, in Europe
Always check where your non-financial data is hosted and who has access to it. For French companies, data sovereignty is a matter of governance and, in some sectors, regulatory compliance.
What the Omnibus I Directive changes (and doesn't change)
Since February 24, 2026, the Omnibus I Directive has simplified certain reporting obligations for intermediate-sized enterprises. Some management teams are tempted to conclude that they can slow down their investments in this area.
This is a misjudgment for the finance department.
Regulatory simplification reduces the scope of reporting for certain companies. It does not reduce the pressure from investors, banks, and rating agencies on the quality of non-financial data. It does not eliminate audit requirements for companies that remain within scope. And it changes nothing about the strategic value of a well-built non-financial information system.
Companies building this infrastructure today are not doing so solely to comply with the CSRD. They are doing it because they have understood that non-financial data is an asset, and an asset deserves the same infrastructure as financial data.
In summary: the right level of rigor
ESG software produces documents. A non-financial ERP governs an asset.
For the CFO, the question to ask before choosing a tool is not "will this software help us produce our report?" It is: "does this tool provide me and my executive committee with a non-financial information system that meets the same level of rigor I apply to finance?"
If the answer is no, you haven't bought a management tool. You've bought a document production tool.
Harnest was designed to answer the first question, not just the second.