Why Your Carbon Software Can't Tell You Your Number...

Try this on Monday morning. Open your carbon accounting platform. Ask it: what are our total Scope 1 and 2 emissions for this quarter, right now?

Not last quarter. Not as of the last upload. Right now.

If you can get an answer in under 60 seconds, you're in the top 1% of Australian companies we've spoken to. Everyone else opens a support request with their sustainability team, who opens three spreadsheets, emails two site managers for missing invoices, and starts assembling a number they won't have until Wednesday. By then the number is already six weeks stale.

This is the problem nobody in our industry talks about honestly. Most carbon accounting platforms aren't really accounting systems. They're filing cabinets with a calculator attached. You put documents in. Periodically, someone runs the numbers. Between uploads, the system doesn't know your position. It knows your last known position, which could be months old.

Real-time carbon reporting shouldn't be a luxury feature. Under AASB S2 and NGER, it's quickly becoming a governance requirement.

The batch processing trap

Here's how most carbon platforms actually work. Your sustainability team collects utility bills and fuel invoices over the quarter. They batch those documents together. They upload them, sometimes manually, sometimes via CSV. The system processes them, applies emission factors, generates a report. Everyone celebrates. Then nobody touches it again until next quarter.

That cycle creates a data gap that's invisible until someone asks for the number.

Think about what happens during those 12 weeks between uploads. Your fleet is burning diesel. Your buildings are consuming electricity. Your sites are generating waste. All of those activities produce emissions that exist in reality but don't exist in your system yet. Your carbon platform shows Q1 results while Q2 is already half over.

Financial accounting doesn't work this way. Your CFO can see revenue by division, by month, whenever they want. They don't wait until quarter-end to find out if the business is making money. But that's exactly how most companies track their emissions, a metric that now carries the same regulatory weight as financial data under ASRS.

PwC's 2025 Global Sustainability Reporting Survey found that more than 60% of organisations increased senior leadership time spent on sustainability reporting in the past year. A huge chunk of that time goes to answering ad hoc questions. The board wants a number. A tender requires it. A customer asks. And every time, it triggers a multi-day data assembly project instead of a 2-second lookup.

AASB S2 turned this into a governance problem

Before mandatory climate reporting, the data lag was annoying but survivable. You could batch-process your way through voluntary disclosures once a year and nobody asked too many questions.

AASB S2 changed the equation. Paragraphs 6 through 8 require entities to disclose the governance processes they use to monitor and oversee climate-related risks and opportunities. Specifically, entities must disclose how often the governance body is informed about climate-related risks, whether the board has the skills to understand what they're seeing, and how climate considerations factor into strategic decisions and target-setting.

That's not describing an annual exercise. It's describing an ongoing governance rhythm.

The AICD's 2024 Climate Governance Study surveyed 1,057 Australian directors and found that 58% said their board doesn't have a dedicated sustainability committee. Only 26% had undertaken climate governance training. And here's the part that connects back to data: directors who want to exercise oversight can't, because the data is always stale by the time it reaches them.

Group 1 entities (those with $500M+ revenue or 500+ employees) are already filing. Group 2 entities must report for financial years starting from 1 July 2026. Group 3 follows from 1 July 2027. For every one of these companies, the board's ability to demonstrate active climate oversight depends on having emissions data that's current, not data from a batch run that happened two months ago.

And it's not just AASB S2. Companies reporting under NGER face their annual 31 October deadline with data that needs to be accurate for the full reporting year. If your last batch upload was in March and your reporting year ends in June, you've got three months of emissions data sitting in inboxes and SharePoint folders, invisible to your compliance team until someone manually processes it. The Clean Energy Regulator can issue infringement notices for incorrect reports at $222 per penalty unit. That risk compounds when your system doesn't reflect reality.

What "knowing your number" actually requires

The gap between a batch-processing carbon platform and one that can answer "what's our number?" in real time isn't a single feature. It's an architectural difference. Five things have to be true simultaneously.

Documents get processed as they arrive. Not batched monthly. Not queued for the next reporting cycle. When an electricity bill lands in your system, whether via email, cloud sync, or manual upload, it gets read, extracted, and calculated within minutes. This is where AI document processing changes the game. A system that can read 8 file formats (PDF, CSV, Excel, Word, images, and more) and automatically extract consumption data doesn't need a human to schedule a processing run. Bills arrive. Numbers appear. Carbonly processes documents as they're received, so your data reflects what's actually happening, not what happened last time someone ran an upload.

Emission factors get applied automatically. The NGA Factors 2025 edition lists different grid emission factors by state: 0.64 kg CO2-e/kWh for NSW, 0.78 for Victoria, 0.20 for Tasmania. When a document is processed, the right factor for the right state needs to be applied without someone looking it up in a spreadsheet. And when factors are updated annually, the system needs to know which version applies to which period. We've written about emission factor matching in detail because getting this wrong silently corrupts every number downstream.

Quality checks run continuously. Not at year-end when it's too late. Anomaly detection only works if it has fresh data to compare against historical baselines. A spike in diesel consumption at a construction site means something different in week 3 of a project versus week 40. But if the system only sees data quarterly, it can't distinguish a genuine anomaly from a gap that was always there.

Your dashboard shows live totals. Scope 1, Scope 2, Scope 3 by category, with the ability to drill into any number by site, by source, by period. Not a report that someone generated last Tuesday. A live view that updates as data flows in. We've seen companies where the sustainability manager maintains a separate "live" spreadsheet alongside their carbon platform because the platform itself can't show current numbers. That's two systems doing one job, badly.

Someone (or something) can answer the question directly. When the CFO walks in and asks "what's our Scope 1 this quarter?", the answer shouldn't require a person to open a platform, apply filters, export a CSV, and email a summary. Carbonly Co-Pilot answers plain-English questions against your live data. "What were our diesel emissions across Queensland sites this quarter?" returns a number, from your actual records, in seconds. We built that because the ad hoc question problem eats more sustainability team hours than most people realise.

The Monday morning test

Here's a simple way to evaluate whether you have a carbon accounting system or a carbon filing cabinet. Open it on Monday morning, first thing. Don't run anything. Don't upload anything. Don't ask your sustainability team to prepare a report.

Can you see your current emissions position? Scope 1, 2, and 3 totals that reflect data processed up to last week, not last quarter?

If yes, you've got a system. You can answer the board, respond to tender questions, track against reduction targets, and demonstrate the active governance oversight AASB S2 requires.

If no, you've got a filing cabinet. An expensive one, maybe, with nice charts. But a filing cabinet nonetheless. It stores what you've already processed. It doesn't tell you where you stand.

We're not going to pretend that getting to continuous data is easy. Scope 3 in particular is still messy. Supplier data arrives late, in inconsistent formats, with varying quality. We're still working through the best approaches for categories like purchased goods and services where primary data is genuinely hard to get in real time. But for Scope 1 and 2, the data sources are well-defined (utility bills, fuel records, gas invoices), the emission factors are published by DCCEEW, and there's no reason a system should need a human to manually trigger processing every quarter.

Reduction targets need a live scoreboard

There's a second-order problem with batch processing that doesn't get enough attention. If your emissions data is always 2-3 months behind reality, how do you know if you're on track against your reduction targets?

Australia's federal target is 43% reduction by 2030. Companies setting science-based targets commit to specific annual reduction pathways. The Safeguard Mechanism imposes declining baselines on covered facilities. All of these require you to know where you are today, not where you were in March.

Without live data, target tracking becomes a rear-view mirror exercise. You find out you've overshot your quarterly carbon budget weeks after it happened, when it's too late to adjust operational decisions. Imagine managing a financial budget where you only see actual spend every 90 days. Nobody would accept that.

With continuous data flow, you can spot a trajectory problem in week 6 instead of month 5. A site that's trending 15% above its baseline shows up in the dashboard while there's still time to investigate. Maybe a piece of equipment is running inefficiently. Maybe a fuel supplier changed blends. Maybe there's a data error. Whatever the cause, catching it early is worth more than catching it late.

Carbonly's carbon planning module connects reduction targets to live data so you can see projected versus actual in the same view. But the planning features are only as good as the data feeding them. Stale data in, stale plans out.

The filing cabinet era is ending

The carbon accounting industry grew up around annual reporting cycles. NGER once a year. GHG Protocol inventories once a year. Voluntary disclosures once a year. Batch processing was fine for that world.

That world is gone. AASB S2 requires governance disclosures that imply ongoing oversight. Boards want quarterly updates. CFOs want emissions data that ties to financial periods. Customers want supply chain data on demand. The Clean Energy Regulator is tightening its compliance approach, and the NGER 2025-26 amendments (effective for reports due 31 October 2026) add complexity around market-based reporting for biomethane, hydrogen, and updated Scope 2 electricity methods.

The question isn't whether your organisation will need real-time carbon reporting. It's whether your current system can deliver it, or whether you're running a filing cabinet that just happens to have a login screen.

If you want to see what it looks like when the answer to "what's our number?" takes seconds instead of days, reach out at hello@carbonly.ai. We price per project, and we're happy to show you the difference.

Why Your Carbon Software Can't Tell You Your Number Right Now