Scope 3 Category 1 for Australian Companies: The...

The pattern in mid-tier Australian construction and infrastructure is consistent. The procurement team is asked for "the carbon number" against tens or hundreds of millions of dollars of materials and subcontract spend, with a six-to-eight-week window before the AASB S2 disclosure deadline. The ERP gives spend by supplier and GL code. It does not give tonnes of concrete, kilograms of rebar, or litres of bitumen. So the team does what many Group 1 reporters did last year: runs spend-based factors and writes a paragraph in the Basis of Preparation explaining the limitations.

That paragraph is going to age badly. By the second or third reporting year, auditors expect movement. Spend-based is a starting point, not a destination.

This is the sequencing built to survive an ASSA 5010 assurance engagement without the auditor flagging "data quality" as a material limitation.

Why Category 1 is the line that gets argued about

Category 1 of the GHG Protocol Scope 3 Standard covers all upstream emissions from goods and services a company buys. For a construction company, that is concrete, steel, asphalt, timber, subcontractor labour, plant hire, and consultancy. For a property manager, it is fit-out materials, cleaning services, security, and capex projects. For a miner, it is diesel (the part you do not burn yourself), explosives, tyres, grinding media, and EPCM contracts.

It is usually the biggest single category in the Scope 3 inventory. For most Australian companies outside financial services, Category 1 plus Category 11 (use of sold products) dominate the full footprint. Screening exercises commonly put the two together somewhere in the 60 to 80 percent range, though the split moves sharply by sector.

Under AASB S2 paragraph 29(a)(vi), Scope 3 disclosure is mandatory. Paragraph B32 requires entities to use direct measurement where possible and to disclose the methods, inputs, and assumptions used. Paragraph 33(b) requires disclosure of the targets and metrics the entity uses to measure progress. Translation: you cannot just publish a number. You have to publish a number and defend how you got it.

That defence is what this post is about.

Three methods, in order of credibility

The Scope 3 Standard recognises four calculation methods for Category 1. In practice, Australian reporters use three:

Spend-based. Multiply dollars spent with a supplier by an emissions factor per dollar. Factors come from environmentally extended input-output (EEIO) models, most commonly the Industrial Ecology Lab (IELab) dataset or international equivalents. Easy. Cheap. Inaccurate. A supplier that switches to renewable power gets no credit. A supplier that doubles its prices looks like it doubled its emissions.

Average-data (activity-based). Multiply physical quantity (tonnes of concrete, litres of fuel, kg of steel) by an industry-average emission factor from a database like NGA, the ICE database, or a national LCA library. Better. The signal now reflects what you bought, not what you paid.

Supplier-specific. Use an emissions factor the supplier has calculated for their own product, ideally from a verified Environmental Product Declaration (EPD), a third-party assured corporate inventory, or a documented LCA. Best. The signal reflects what that particular supplier did.

Most ASX-listed companies will use a blend. The argument is about which suppliers sit in which bucket, and how fast you move them across.

The realistic sequencing

We do not believe any mid-market Australian company should try to go fully supplier-specific in Year 1. That is a recipe for a delayed disclosure, a frustrated procurement team, and a CFO who never wants to hear the word "Scope 3" again.

Here is the sequencing that holds up.

Year 1 (FY26-27 for Group 2 reporters). Spend-based for the full supplier base. Activity-based for the top 5 to 10 categories where you already have quantity data sitting in invoices, dockets, or delivery records. Disclose the split. Set a target: by Year 3, X percent of Category 1 emissions covered by supplier-specific or activity-based data.

Year 2. Move the top 20 suppliers by spend to supplier-specific data where they have it, activity-based where they do not. Build a data request workflow with procurement. Update master data agreements to include carbon data clauses on renewal.

Year 3. Top 50 suppliers on supplier-specific or activity-based. Remainder on spend-based with documented improvement plan.

This is not Carbonly's framework. It mirrors how PCAF's data quality scoring works in financed emissions and how the GHG Protocol's Scope 3 Standard talks about "data quality indicators" in Chapter 7. Auditors recognise it because it is consistent with how financial materiality assessments are supposed to work: focus the effort where the dollars are.

What to actually ask suppliers

The most common mistake is the long carbon survey emailed to the entire supplier base. Cold, unincentivised supplier surveys draw low response rates, and a good share of what comes back is partially completed or unusable. Your procurement team has burned months and a lot of supplier goodwill for a thin return.

Start smaller. For the top 20 suppliers (by spend or by emissions intensity, whichever ranks higher), ask for four things:

Product-specific carbon footprint or EPD for the product or service category you buy from them, with the declared unit (per tonne, per square metre, per dollar) and the system boundary (cradle-to-gate is standard for materials).
The corporate Scope 1 and Scope 2 footprint for the operating entity that supplies you, with the reporting period and any third-party assurance statement.
Allocation method they used if the EPD is for a product line, not a specific SKU.
Update frequency: when will the next version be available, and what triggers a recalculation.

That is it. Four asks. A supplier with mature reporting can answer in a week. A supplier without can tell you so, and that becomes useful data for your data quality scoring.

For everything else, work backwards from what you already have. We covered the data extraction side of this in our guide on collecting Scope 3 data from suppliers, but the procurement angle is worth its own treatment.

Procurement data is half the battle

Your ERP already knows most of what Category 1 requires. The problem is that it is organised around dollars, not carbon.

A typical pattern in SAP or Oracle: line items contain supplier ID, GL code, dollar value, sometimes a unit of measure and quantity, sometimes not. The quantity field is reliable for inventory items (cement, fuel, tyres) and unreliable for services (consultancy, plant hire, subcontract labour). The unit of measure field is often free text. It is common to find "ea", "EA", "each", "unit", "lot", and "1" all used in the same procurement system to mean the same thing.

Three things to do with procurement data before you touch carbon factors:

Map GL codes to GHG Protocol categories. Most ERPs have between 200 and 1,500 active GL codes for purchases. You probably need 30 to 60 carbon categories. This mapping is a one-week job and you only do it once.

Identify the inventoried-vs-expensed split. Inventoried items (concrete, steel, fuel) usually have clean quantity data. Expensed items (consultancy, software licences, building services) usually do not. You will use spend-based factors for the expensed bucket for years to come. Accept that.

Tag controlling versus equity-shared spend. If you operate in JVs, the JV consolidation question matters here too. AASB S2 follows the consolidation approach used in the financial statements. Procurement spend on a 50/50 JV operated by your partner should not be in your Category 1 if the financial statements equity-account it. This is commonly miscounted.

Where the quantity-first approach changes the maths

This is where we draw a line.

Across the carbon platforms we reviewed, we could not find public documentation of reliable physical-quantity extraction from supplier invoices as at September 2026. The documented pattern is an ERP spend feed with EEIO factors applied on top. That works for the first year. It does not survive contact with an audit team three years in.

Carbonly's AI document engine reads supplier invoices, delivery dockets, and statements and extracts physical quantities (tonnes of concrete by mix, kilograms of rebar by grade, litres of diesel by site) along with supplier ID, date, and document reference. Those quantities then match against the material library, which holds NGA factors, EPDs uploaded by the user, and a growing set of supplier-specific factors. Every line item carries a source reference back to the original document.

That closes off a line of audit challenge reported in Group 1 engagements: spend-based factors used where activity data was already sitting in the source documents. If the docket says 32 cubic metres of 40 MPa concrete and you reported it as $9,840 of "Concrete - Ready Mixed" multiplied by an EEIO factor, the auditor will ask why.

A construction company taking delivery dockets from dozens of suppliers across multiple sites cannot do this manually. We have written about that exact pain point before. The point is not the volume. The point is that the quantity data exists in the source documents the procurement team is already receiving. Extracting it changes the conversation with the auditor from "trust our spend factors" to "here is the underlying invoice."

Data quality scoring without overengineering it

PCAF's five-point data quality score for financed emissions (1 = best, 5 = worst) has become the de facto language for talking about Scope 3 data confidence. The Scope 3 Standard's Chapter 7 has a similar concept. Variations of it are a practical option for Category 1.

A workable scoring framework:

Score 1: Supplier-specific factor from a verified EPD or assured corporate inventory, matched to the specific product purchased.
Score 2: Supplier-specific factor from an unverified self-reported source, matched to the specific product purchased.
Score 3: Industry-average factor from NGA or equivalent national database, applied to a physical quantity (kg, tonnes, litres) extracted from purchase records.
Score 4: Spend-based factor from an EEIO database, applied at the GL code or supplier level.
Score 5: Spend-based factor applied to estimated or proxied spend.

Report the weighted average across the Category 1 inventory. Set a target to move the average down each year. That is what auditors want to see: a credible improvement trajectory, not a one-off heroic year.

Carbonly tracks the data source on every emission record (document reference, factor source, calculation method) through its audit trail. The scoring overlay is something a sustainability team can implement against that source-of-truth data without needing a separate "PCAF engine." Honesty: we do not have a built-in PCAF scoring module. The data lineage is there. The scoring schema is a reporting view on top of it.

What ASSA 5010 auditors look for

The AUASB's ASSA 5010 standard for sustainability assurance is now in effect for Group 1 reporters at limited assurance level. Group 2 will get the same treatment from FY26-27. By 2030, reasonable assurance kicks in.

For Category 1, published assurance guidance and reported Group 1 experience point to five things auditors test:

Completeness of supplier population. Did you cover all material spend, including capex, intercompany, and contractor pass-through?
Boundary alignment. Is the consolidation approach for Scope 3 the same as the financial statements?
Factor traceability. For each factor used, can you produce the source document (EPD certificate, NGA workbook page, EEIO methodology)?
Method consistency. Did you change methods mid-year, and if so, did you restate the comparative?
Basis of Preparation disclosure. Did the BoP describe the methods, the data quality split, and the known limitations honestly?

We have written a longer piece on the eight checks ASSA 5010 auditors actually run. For Category 1 specifically, the factor traceability and method consistency points are where most reporters struggle.

The honest limitations

A few things we are still working through, and you should be too.

Subcontractor reporting is messy in construction. A subcontractor delivering a $4 million electrical fit-out is bringing labour, materials, and their own subcontractors. The Scope 3 Standard says you should capture their Scope 1 and 2 emissions plus their upstream Scope 3 in your Category 1. In practice, subcontractor data is patchy at best. Spend-based with a documented improvement plan is defensible.

EPD coverage in Australia is uneven. Concrete and steel have reasonable EPD coverage through EPD Australasia. Aluminium, timber, and most building services trade do not. Some categories will sit on spend-based for the next five years and that is fine if you say so.

Capex is its own problem. Major project capex moves through procurement systems differently than operational spend. A $50 million pipeline build will look like four or five large supplier line items rather than a thousand small ones. Activity-based factors are usually achievable here because the engineering documentation exists. The trick is getting Finance and Engineering talking to each other.

Where to start tomorrow

Pull a 12-month export of supplier spend from your ERP. Sort by total spend. In most portfolios the top 50 suppliers account for the large majority of Category 1 emissions. Of those, identify which ones already provide EPDs or carbon data (as at September 2026, Boral, Adbri, BlueScope, Liberty Steel and InfraBuild publish EPDs for major products). That is your Year 1 supplier-specific bucket without sending a single survey.

Everything else gets spend-based or activity-based depending on whether you have quantity data. Document the split in the Basis of Preparation. Set the Year 3 target.

Then build the data extraction workflow so by Year 2 you are pulling quantities out of invoices, not multiplying dollars by EEIO factors. That is the line that takes a Category 1 number from "best we could do" to "audit-ready."

Scope 3 Category 1 for Australian Companies: The Supplier Engagement Workflow That Actually Works