Scope 3 Emissions Software in Australia: Supplier Invoices Turned Into Line Items You Can Show an Auditor
Scope 3 emissions software should turn supplier invoices and dockets into quantity-based line items, each traced to its source document. Here is what to check before you buy.
Good Scope 3 emissions software does one job well. It reads the supplier invoices, delivery dockets and EPDs you already receive, pulls out physical quantities line by line, and matches each line to a defensible emission factor. Then it keeps the original line text beside every number, so an assurer can trace a tonne back to the page it came from.
That is the test. A tool that only maps your accounts payable ledger to spend factors will give you a total. It won't give you a total that moves when you buy better materials, and it won't survive a sample.
This matters now. AASB S2 gives Scope 3 relief in the first reporting year only. Many Group 1 entities are into their second year as at November 2026, and Group 2 started on 1 July 2026. Limited assurance under ASSA 5010 applies from year one. So the Scope 3 figure you disclose next is the one an assurer will test.
We build carbon accounting software, and we've spent a lot of time on construction documents. Below are the six ways Scope 3 data breaks in practice, what software has to do about each, and how Carbonly handles it. A buyer checklist and FAQ sit at the end.
Why spend-based Scope 3 won't carry you past year one
Most organisations start Scope 3 the same way. Export the AP ledger, group spend by category, multiply by an economy-wide spend factor. It takes a week and it produces a number.
The problem is what the number can't do. Say your project switches to a lower-carbon concrete mix at the same price per cubic metre. Your spend didn't change, so your reported emissions didn't change either. Your best decarbonisation decision of the year is invisible in your own disclosure.
The GHG Protocol Corporate Value Chain (Scope 3) Standard and its calculation guidance rank data sources for exactly this reason. AASB S2 makes a similar point in its measurement guidance (paragraphs B40 to B44). It prioritises data from direct measurement and specific inputs from the value chain over estimates.
| Method (purchased goods, Category 1) | Data it uses | Where it sits |
|---|---|---|
| Supplier-specific | Cradle-to-gate data from the supplier, such as a product EPD | Highest |
| Hybrid | Supplier data for some inputs, secondary data for the rest | High |
| Average-data | Physical quantity times an industry-average factor | Middle |
| Spend-based | Dollars times an economy-wide spend factor | Lowest |
Spend-based has a place. It's a fair way to screen categories and find where the tonnes probably sit. We've written more on that in our piece on spend-based emissions accounting in Australia. But for your material categories, the ones that carry most of the tonnes, you want quantities. And quantities live in documents.
Six places Scope 3 data breaks, and what the software must do
Material ambiguity: "N32" is a strength grade
A concrete docket rarely says "low carbon mix, 312 kg CO2-e per m3". It says something like "N32 20mm 100 slump, 42 m3". N32 tells you the strength. It tells you nothing about the binder.
Supplementary cementitious materials such as fly ash and slag change the footprint a lot. In one set of published Hanson EPDs for a single Brisbane plant, carbon per cubic metre varied by about 78% across nine 40 MPa mixes. Same grade, same supplier, same site. We walk through those numbers in our post on concrete emission factors for Scope 3.
What software must do: match the line to the most specific factor available, show how confident that match is, and stop to ask when it isn't sure.
How Carbonly handles it: five-tier material matching checks each line against Australian NGA factors, EPD factors and the organisation's own factor library. Each match carries a confidence score. Low-confidence matches go to a reviewer queue instead of quietly landing in the ledger. When a reviewer corrects a match, that line text is saved as an alias for your organisation only. The next docket with the same wording matches through it.
Unit chaos: ordered in m3, factored in tonnes
Concrete is ordered by the cubic metre. Plenty of factors are expressed per tonne. Reinforcing steel turns up in kilograms per metre, lineal metres or tonnes, depending on who raised the invoice.
Converting m3 to tonnes needs a density. If the docket doesn't state one, any conversion means inventing a figure. Normal-weight structural concrete in real Australian EPDs sits around 2,170 to 2,380 kg per m3, which is a spread wide enough to matter. Our guide to converting concrete m3 to tonnes argues that you often shouldn't convert at all.
What software must do: refuse to guess a missing figure.
How Carbonly handles it: extraction is quantity-first. A unit that can't be converted without an unstated number, like m3 to tonnes with no density, goes to a reviewer. Carbonly does not apply a default density automatically. A person decides, and that decision is recorded.
Double counting: one delivery, two documents
The same concrete pour can appear on the supplier's docket, on the supplier's monthly invoice, and inside a subcontractor's progress claim. Supply-and-install packages make it worse. So do joint ventures, where operational control and equity share can put one tonne on several ledgers. Our post on Scope 3 double counting in construction covers the boundary rules.
What software must do: treat one docket as one record, net off credits, ignore lines that aren't material, and flag likely duplicates.
How Carbonly handles it: multi-docket invoices become one record per docket. Credit lines with negative quantities reduce the total. Fee, hire, time and dollar-only lines are skipped. A duplicate-file warning catches the same document uploaded twice. Deterministic anomaly checks run daily at 6am and after each document batch, and they flag likely duplicates for a person to resolve.
Here's our honest doubt. We don't think any rule set reliably untangles a lump-sum subcontract that bundles concrete, labour and pumping into one dollar figure. That needs a boundary decision from someone who knows the contract. Software can surface it. It can't make the call.
Spend-based signal loss
We covered the core problem above. The software point is simpler: a spend-based line should never look as good as a quantity-based one.
How Carbonly handles it: spend-based Scope 3 lines are automatically floored to low data quality, consistent with the AASB S2 measurement framework in B40 to B44. Your disclosure can show which share of Category 1 rests on physical data and which rests on dollars. Expect an assurer to ask about that share.
Suppliers send evidence: EPDs locked in PDFs
EPDs arrive as twenty-page PDFs. Waste transfer notes arrive as phone photos. Freight records arrive as spreadsheets with merged cells.
What software must do: read the documents as they come, without asking suppliers to change their paperwork.
How Carbonly handles it: the document AI engine reads eight file formats, including PDF (scanned or native), images, Excel, CSV, Word, PowerPoint and RTF. Documents arrive by email ingestion per project or through OneDrive and SharePoint sync. Each extracted line keeps its verbatim source text, stored separately from the resolved value. You can read more on the mechanics on how it works.
Subcontractor gaps
Your largest Scope 3 sources are often subcontractors who have never been asked for emissions data. Many don't have a sustainability lead. Our subcontractor emissions guide goes into what a reasonable ask looks like.
How Carbonly handles it: a Supplier Portal lets suppliers and subcontractors upload the invoices and EPDs they already hold, scoped to each project. A Supplier Data Chase Agent follows up on a cadence you configure. Every submission carries the supplier user's name. There's more on that workflow in our Supplier Portal post.
Traceability is the feature an assurer actually tests
An assurer under ASSA 5010 won't re-perform your whole inventory. They'll sample. Pick one Category 1 figure, ask where it came from, and follow the chain.
That chain needs four links. The source document. The exact line on it. The factor applied, with its version. And who approved any human decision along the way.
Carbonly snapshots the emission factor version, GWP set and method onto each ledger record when it's confirmed. Typed audit events are written on every ledger write. Periods can be locked, and a restatement needs a recorded reason. An evidence pack and a read-only Auditor Workspace are designed to support a limited assurance engagement. None of that makes a disclosure correct on its own. The reporting entity and its assurer stay responsible for the figure.
One more detail worth knowing. Carbonly calculates on AR5 global warming potentials, the NGER basis. AASB S2 references AR6, and AASB S2025-1 lets the NGER-covered portion keep AR5. If your Scope 3 needs AR6 figures, plan for that step with your adviser.
A 10-point checklist for buying Scope 3 software
Run every item against your own documents. A trial on last quarter's real dockets tells you more than any demo.
- Does it extract physical quantities from supplier documents, or only map spend?
- Does every figure keep the verbatim source line it came from?
- Does each match show a confidence score, with a review queue for weak ones?
- Does it refuse to convert units when a figure like density is missing?
- Can it use supplier EPD factors and your own factor library as well as national averages?
- Do reviewer corrections stay inside your organisation?
- Does it handle credits, skip fee and hire lines, and flag duplicates?
- Does it label spend-based lines as lower data quality in the output?
- Can suppliers submit documents directly, with follow-ups you don't have to chase by hand?
- Can an assurer get read-only access and follow one number back to its page?
If a tool fails items 1 or 2, the rest barely matter. You'll be rebuilding the evidence trail by hand in March.
We'd also suggest reading what first-wave reporters ran into. Our AASB S2 year two Scope 3 lessons post covers it, and the broader rules sit in Scope 3 reporting under AASB S2. The Scope 3 topic hub collects the rest.
The next step is small. Pull twenty concrete and steel dockets from one live project and see how many of them you could trace to a specific factor today. If you'd like to run that set through Carbonly, book a 30-minute walkthrough at calendly.com/carbonly/30min or email hello@carbonly.ai.
FAQ
What is Scope 3 emissions software? It's software that calculates emissions from your value chain, such as purchased materials, freight, waste and subcontracted work. The useful kind reads supplier documents for physical quantities and keeps the source evidence for each figure.
Is spend-based Scope 3 acceptable under AASB S2? It can be used, and many entities start there. But AASB S2's measurement framework (B40 to B44) favours direct measurement and specific value-chain inputs. Spend-based data also can't show reductions from buying lower-carbon materials at the same price.
When does Scope 3 become mandatory for Australian reporters? AASB S2 gives relief from Scope 3 in an entity's first reporting year. Group 1 started on 1 January 2025 and Group 2 on 1 July 2026, as at November 2026. Group 3 starts on 1 July 2027.
Can Scope 3 software convert concrete from m3 to tonnes automatically? Carbonly doesn't. If a docket has no density, the line goes to a reviewer, because any automatic conversion would rest on a figure the supplier never stated. Using the supplier's per-m3 EPD factor often avoids the conversion entirely.
Can software make my Scope 3 figure assurance-ready on its own? No. Carbonly keeps the source line, factor version and reviewer decisions for each record, and provides an evidence pack. The reporting entity and its assurance provider remain responsible for the disclosure.
Do suppliers need to fill in a questionnaire? No. Through the Supplier Portal they can upload the invoices, dockets and EPDs they already hold. Carbonly extracts the quantities from those documents.
Which industries is this built for? Construction first, because concrete, steel and subcontract data are where Scope 3 gets hardest. The same workflow serves property, mining, manufacturing and other sectors that buy physical materials.