BusinessThe Management Accountant

Sustainability Reporting Controls: 10 COSO-Based Checks Financial Controllers Should Implement

Ten COSO-based sustainability reporting controls for finance leaders covering metric ownership, data quality, estimates, reconciliations, review evidence and disclosure.

Sustainability information is increasingly used in strategy, risk management, financing, customer decisions and external reporting. Yet the data may originate in facilities, procurement, fleet systems, HR, spreadsheets, suppliers and specialized software—often outside the finance team’s normal close controls. Financial controllers can help turn sustainability reporting from an ad hoc data exercise into a repeatable, reviewable process.

COSO’s 2023 supplemental guidance on Internal Control over Sustainability Reporting (ICSR) adapts its Internal Control—Integrated Framework to sustainability information. It is useful as a control-design reference, not a universal reporting mandate. Start with the information your organization actually needs or is required to report, then scale controls to materiality, risk, complexity and available resources.

1. Establish ownership and a reporting inventory

Assign an accountable executive, a metric owner, a data steward and a finance reviewer for each disclosed metric. Build a reporting inventory listing the metric, purpose, reporting framework or stakeholder request, organizational boundary, source system, frequency, calculation method, preparer, reviewer and retained evidence. Avoid the common gap where sustainability owns the narrative, operations owns raw data, and nobody owns the final number.

2. Define metrics, boundaries and methodology before collection

Write a controlled definition for every measure: unit of measure, included activities, excluded locations, consolidation boundary, estimation approach and period. For emissions, document the selected methodology and factor sources. For energy, water, waste, safety or workforce metrics, specify exactly what is counted and how sites classify events. Do not change definitions mid-cycle without approval and an explanation of comparability effects.

3. Validate source data at the point of capture

Identify authoritative source records—utility invoices, meter readings, fuel cards, production records, logistics data, HR records or supplier submissions. Require source identifiers and evidence for manual uploads. Controls should detect missing months, duplicate invoices, inconsistent units, implausible readings, late submissions and unexplained changes. Where suppliers provide data, retain the submission, methodology, period covered and contact responsible for it.

4. Control estimation and calculation files

Some sustainability data will be estimated. Keep a documented hierarchy for actual data, supplier-specific information, proxy data and estimates. Calculation files should use locked formulas, controlled factor tables, version histories and independent review. Require reviewers to challenge the reasonableness of key assumptions, not simply confirm that a spreadsheet total agrees with another spreadsheet.

5. Reconcile sustainability metrics to operational and financial records

Use reconciliations to identify gaps and anomalies. Energy consumption can be compared with utility invoices and facility records; fuel use with fleet logs and card transactions; waste volumes with vendor invoices; headcount metrics with HR reports; and purchased goods data with procurement spend. A reconciliation is a reasonableness check—not proof that a metric is correct. Explain differences such as timing, coverage, unit conversions, estimates or classification changes.

6. Govern supplier and value-chain data

Value-chain metrics can depend on suppliers with uneven data quality. Document which suppliers or categories are included, which are excluded, the coverage percentage, why data is missing, and how proxies are calculated. Use consistent request templates and deadlines. Prioritize high-impact categories and material suppliers, and track improvement plans rather than silently replacing missing data with zero.

7. Apply change management to systems, factors and assumptions

Changes to reporting software, spreadsheets, emissions factors, site boundaries, calculation methods or source mappings should be logged, approved, tested and dated. Preserve the prior version so a reviewer can reproduce last year’s figure. If a method change affects trend comparisons, quantify or explain the impact where appropriate and avoid presenting a methodology-driven change as an operational improvement.

8. Build an effective management review

Design the review around thresholds and questions: large period-over-period movements, missing sites, new estimates, data coverage, unusual ratios, changes in factors and metrics that do not reconcile to operational records. Evidence the reviewer’s challenge, response, correction and conclusion. A signature or email stating “reviewed” is not enough if it does not show what was examined and how exceptions were resolved.

9. Protect access, segregation and disclosure versions

Limit edit rights to approved preparers. Separate calculation changes from review approval where practicable. Maintain access logs for reporting tools and controlled spreadsheets, secure supplier uploads, and restrict final disclosure files. Tie each published number back to an approved calculation, source record and metric definition. Finance should control the final version, with sustainability and legal subject-matter review as appropriate.

10. Document exceptions, evidence and sign-off

Use an exception register with metric, issue, risk, owner, remediation date, disposition and approver. Keep a reporting evidence pack containing the metric inventory, source records, calculations, factor references, reconciliations, review evidence, methodology changes and final disclosure sign-off. Set retention rules that align with applicable requirements and company policy. This makes the reporting process more defensible and easier to repeat.

A practical example: North American manufacturer

A U.S. manufacturer reports electricity use and fuel consumption from several plants, while its Canadian subsidiary provides utility data and transportation estimates. Finance can reconcile electricity and fuel totals to invoices and AP records, compare consumption with production levels, and flag missing months. Operations validates meter readings; procurement confirms supplier information; sustainability owns the methodology; and the controller reviews the consolidated metric pack. When a facility changes meters or an emissions factor is updated, the team records the change and assesses comparability before reporting a trend.

North American reporting landscape: check applicability, not assumptions

  • ISSB / IFRS: IFRS S1 and IFRS S2 were issued on June 26, 2023 and are effective for annual reporting periods beginning on or after January 1, 2024. Adoption and mandatory application depend on jurisdiction. See the IFRS S1 and IFRS S2 pages.
  • Canada: CSDS 1 and CSDS 2 were issued December 18, 2024 and are effective for annual periods beginning on or after January 1, 2025, on a voluntary basis unless adopted or mandated by an applicable regulator or law. The CSA paused development of a new mandatory climate disclosure rule on April 23, 2025; existing disclosure obligations for material climate-related risks remain. See the CSDS overview and the CSA announcement.
  • United States: The SEC’s 2024 climate disclosure rules were stayed on April 4, 2024. On May 29, 2026, the SEC proposed rescinding them; the comment deadline was August 3, 2026. Check the SEC rulemaking page for current status rather than treating the proposal as final. State requirements and litigation may also affect applicability. On November 9, 2026, Reuters reported a Ninth Circuit panel decision partially blocking California climate-disclosure enforcement; see Reuters’ report and obtain current legal advice.
  • Federally regulated Canadian financial institutions: OSFI’s Guideline B-15 includes climate-risk management and disclosure expectations, with institution-specific implementation timelines and updates.

Month-end or reporting-cycle sustainability checklist

  • Reporting boundary, metric definitions and owners confirmed.
  • Source data received from all expected sites, functions and suppliers; missing data tracked.
  • Units, conversions, factors, assumptions and calculation versions validated.
  • Key metrics reconciled to operational and financial source records; variances explained.
  • Estimates, methodology changes and data gaps reviewed and documented.
  • Exceptions remediated or escalated; management approval captured.
  • Final disclosure numbers tied to approved workpapers and version-controlled reporting files.

Conclusion

Controllers do not need to own every sustainability metric to strengthen reporting reliability. They can provide the discipline of clear ownership, controlled definitions, traceable source data, independent review, reconciliations, exception management and version control. A risk-based ICSR framework helps sustainability teams and finance work from one consistent, evidence-backed process—supporting decision-making and credible disclosures without overstating assurance.

Disclaimer: This article is general educational information, not legal, regulatory, accounting or sustainability-assurance advice. Reporting obligations vary by entity, jurisdiction and industry and may change. Confirm current requirements with appropriate advisors and authoritative sources.

Shares: