Why agricultural Scope 3 under AASB S2 needs a data chain, not another spreadsheet

For a lot of Australian buyers, the first year of climate reporting came with a breather on value-chain emissions. AASB S2 lets an entity skip Scope 3 disclosure in its first annual reporting period (paragraph C4(b)). From the second year, that relief has run out, and the buyer has to measure.

That's when the requests land on the farm gate. A processor wants one template, a retailer wants another, and a third buyer wants "the same thing, but by product line". Each ask is reasonable on its own. Together they produce three slightly different numbers for the same season, and nobody can say which one is right.

The problem isn't effort. It's traceability. A buyer can defend an estimate. What it struggles to defend is a number with no clear origin, method or date. A better template won't fix that. A data chain will: a short, fixed path from what happened on the farm to what each buyer is allowed to see.

What the standard actually asks of the buyer

AASB S2 doesn't tell a buyer which inputs to use. It tells them how to rank inputs: direct measurement, data specific to their value-chain activities, timely data that reflects the jurisdiction and technology involved, and verified data (paragraph B40). It expects estimation; paragraph B38 says Scope 3 measurement "is likely to include the use of estimation rather than solely comprising direct measurement".

It also builds in proportionality. A reporting entity uses "all reasonable and supportable information" available "without undue cost or effort" (paragraph B39). Averages and industry estimates stay legitimate. Supplier-specific data is preferred where a buyer can reasonably get it, not compulsory everywhere.

Two boundaries matter here. The obligation to prepare a sustainability report sits with entities caught by section 292A of the Corporations Act, not with the mid-tier suppliers and producers they buy from. And nothing in AASB S2 mandates a particular farm calculator, sharing format or level of detail. When a supplier provides data, that's a commercial arrangement, not a filing.

Four links in the chain

1. Enter activity data once. A producer records what actually happened (herd, feed, fertiliser, fuel, area sown, yield) once per period, in the structure a livestock or cropping calculation already expects. The point isn't to collect more fields. It's to stop re-keying the same season into every buyer's template.

2. Calculate on a shared engine. The Agricultural Innovation Australia (AIA) Environmental Accounting Platform, known as the AIA EAP, describes itself as a pre-competitive, standardised carbon calculation engine for Australian agriculture, fisheries and forestry. Its calculators cover livestock and cropping enterprises, and its stated design is that other software and service providers drive their calculations through it rather than compete with it. Running activity data through a recognised engine gives every downstream buyer the same method label, instead of one bespoke spreadsheet per relationship.

3. Freeze each result as a version. The AIA's calculator documentation says its interface is strictly versioned: call the same version with the same inputs and you get the same result. A data chain carries that idea through. Once a result is produced, that version doesn't change. If the inputs are corrected or the method moves, the result becomes a new version, and the old one stays on record. That's how a buyer's auditor can line up a disclosed figure with the exact calculation behind it, a year later.

4. Share on purpose, at the right slice. The producer, not the buyer, decides what goes where. They attach a specific result version to a specific buyer, or attach an allocation percentage of it when that buyer takes only part of the output. Each buyer sees what's been attached to them, and nothing else: not the full farm record, not other buyers' shares.

Why the order matters

Each link closes a gap the others leave open. Single entry without a shared engine just moves the re-work to the calculation step. A shared engine without fixed versions means last month's figure can quietly drift. Fixed versions without explicit sharing leave the producer either over-sharing or re-exporting for every request. Put together, they produce what paragraph B40 is reaching for: activity-specific, timely data with a traceable origin, delivered within what's reasonable for a supplier to provide.

What it does not settle

A data chain doesn't make a number "compliant" by itself. The buyer still decides how supplier data fits its own Scope 3 inventory and still owns its disclosure.

Two other instruments sit nearby, and it helps to keep them apart. The GHG Protocol's Land Sector and Removals Standard takes effect on 1 January 2027 for companies reporting under the GHG Protocol corporate and Scope 3 standards. AASB S2 refers to the 2004 edition of the GHG Protocol Corporate Standard by name (paragraph 29(a)(ii) and B23). On that basis, some advisers take the view that the new standard doesn't automatically change what an Australian filer must disclose under AASB S2, though filers should confirm the position with their own advisers. And buyers setting land-sector targets under the Science Based Targets initiative's Forest, Land and Agriculture guidance (version 1.2) are working to a target-setting framework, not a disclosure rule. A clean data chain can feed either, but neither is a reason to send a producer a longer form.

The practical takeaway for producers is modest: record the season once, calculate it on an engine your buyers recognise, keep every result you've shared, and decide deliberately who sees which slice.

Supplier Share isn't affiliated with or endorsed by AIA.