Why Audit-Ready Sustainability Reporting Needs Connected Data, Not Spreadsheets

AASB S2 is not just a reporting framework — it’s a connected disclosure system. The standard expects that governance disclosures link to the strategy section, that strategy links to risk management, and that all of these link to specific metrics and targets. When an assurance provider reviews your report, they’ll be looking for coherence across the whole document — not just correctness of individual numbers.

That coherence requires connected data. And connected data is fundamentally incompatible with the spreadsheet-per-person, shared-drive-per-team approach that most Australian businesses currently use for sustainability information.

What “connected information” means in AASB S2

The standard explicitly expects that the information across its four pillars is connected and consistent:

• If your governance section says the board reviews climate metrics quarterly, the metrics section should show those metrics — and there should be evidence they were actually reviewed
• If your strategy section identifies coastal flooding as a material physical risk, the risk management section should describe how it’s managed, and the metrics section should include any relevant exposure metric (assets in flood zones, insurance costs, business interruption exposure)
• If your targets include a 30% Scope 1 reduction by 2030, the metrics section must show your current Scope 1 baseline and annual progress — and the methodology should be consistent year to year

Disconnects between these sections are red flags. An assurance provider finding that a risk mentioned in strategy has no corresponding risk management process, or that a metric doesn’t connect to any target, will note the inconsistency.

Why spreadsheets break the connection

A spreadsheet is an isolated artefact. It contains whatever its creator chose to put in it, with no inherent linkage to the other spreadsheets that make up your reporting process.

The typical spreadsheet-based sustainability reporting workflow looks like this:

1. An analyst collects utility invoices in one spreadsheet
2. A different analyst collects fuel card data in another spreadsheet
3. A sustainability coordinator consolidates these into a “master emissions” spreadsheet
4. A consultant writes the narrative disclosures in a Word document, copying numbers from the master spreadsheet
5. The Word document gets formatted into a PDF
6. The assurance provider receives the PDF and asks for the underlying spreadsheets
7. The spreadsheets don’t match the PDF because the consultant made a last-minute change
8. Three rounds of back-and-forth follow before the assurance engagement completes

This process produces a report that may be technically accurate but is operationally fragile: any change in one place isn’t automatically reflected elsewhere, and the connection between numbers and source documents exists only in someone’s head or email history.

What connected data looks like in practice

A connected data approach means:

Source documents are stored and linked to data points. An electricity invoice isn’t just filed — it’s associated with the specific consumption figures extracted from it. When a number is queried, the invoice is one click away.

Calculations reference versioned factors. The Scope 2 figure for a site links to the NGA factor version used, not just the calculated result. Anyone reviewing the data can see exactly how the calculation was done.

Data flows consistently from collection to report. The figure reported in the AASB S2 climate statement is the same figure that came from the same invoice, processed through the same methodology, every time — not a number manually typed into a Word document that may have been transcribed differently across two drafts.

Narrative disclosures cross-reference data. When the strategy section says “Scope 2 electricity emissions represent X% of our total footprint and are concentrated in Victoria,” that percentage and that geographic concentration come from the same dataset that produces the metrics table.

Changes are tracked. If a figure changes during the reporting process (an invoice was revised, an error was found), there’s a record of what changed, why, and when — not just the final number.

The assurance advantage

Assurance providers working with connected data spend far less time in fieldwork because:

• Sampling is faster — they can select transactions and immediately access the source document
• Methodology verification is immediate — the factor reference is stored with the calculation
• Consistency checking is straightforward — the same data source feeds narrative and metrics

Assurance providers working with a spreadsheet ecosystem spend most of their time reconstructing how the numbers were calculated — which is time the entity pays for.

From spreadsheets to connected infrastructure

The transition from spreadsheets doesn’t require a massive ERP implementation. The right approach for most organisations entering Group 2 or Group 3 reporting is a focused platform that:

• Ingests utility invoices, fuel records, and meter readings from their source
• Maintains the link from each data point to its source document
• Applies and records the NGA factor used in each calculation
• Produces metrics output that feeds directly into the climate statement narrative
• Maintains an audit log of all changes

This is the infrastructure layer that makes both the data and the narrative defensible — to assurance providers, to regulators, and to the board before they sign the directors’ declaration.

---

Ayika is built as exactly this kind of connected infrastructure — source-to-report with lineage at every step. See how it works for your reporting obligations.