Skip to content

Group 2 reporting lands in FY2026-27, and a great many of those entities will turn to their accountant first. The awkward part is that the physical risk section of AASB S2 is not an accounting problem — it is a spatial data problem wearing an accounting deadline.

The position firms are in

Buying a seat on an enterprise climate risk platform per client does not pencil out. Building the capability in-house means hiring people who can handle CMIP6 NetCDF files and state flood study geodatabases. Subcontracting to an engineering consultancy per client is defensible but slow and expensive, and clients notice the margin.

What changes

One workspace per client, each scoped separately. Upload the site list, run the assessment, get back the exposure table and the methodology appendix. The appendix is the deliverable that matters for your file — it documents the datasets, vintages and assumptions so that a reviewer can follow the chain without your team reconstructing it from memory nine months later.

Adviser prompt

For this client's 46 leased sites, produce the AASB S2 physical risk table plus a methodology note listing every dataset and its vintage.

Datasetsg_nafcadastrensw_flood_studiesga_bushfirecmip6

Where you still add the value

The judgement calls stay with you: materiality thresholds, how exposure translates to financial effect, what goes in the strategy narrative, and how the whole thing reads to a board. Zenancy handles the part that is genuinely mechanical and currently expensive.

Frequently asked

Can we white-label the output?

Branded methodology appendices and export templates are on the roadmap for the second preview cohort.

How is client data separated?

Every record is scoped to an organisation from the first query. Client workspaces are separate organisations and never share a data reference store.

See it run on your portfolio

Zenancy is in private preview with Group 2 reporters and their advisers.

Request access