Carbon Accounting for Property Managers: Tracking Emissions Across 50+ Sites

Managing emissions across a multi-site property portfolio means hundreds of utility accounts, tenant data you don't control, and base building splits that change every lease cycle. Here's how to do it without losing your mind or your compliance standing.

Carbonly.ai Team March 17, 2026 10 min read
Property ManagementCarbon AccountingNABERSNGERASRSMulti-Site
Carbon Accounting for Property Managers: Tracking Emissions Across 50+ Sites

Consider a typical property manager's reporting reality: 47 buildings across three states, each with between two and nine utility accounts. That's roughly 280 individual meters. Every quarter, collecting bills from six different energy retailers, three water authorities, and two waste contractors — all using different formats, different billing cycles, and different portals. Copying the consumption data into a spreadsheet with 1,400 rows.

Three years of this. Facilities managers call it "the monster."

Carbon accounting for property managers is a different beast than it is for a single-site manufacturer or a logistics company. The volume alone changes the problem. But it's not just volume. It's the split between base building and tenant energy. It's the NABERS ratings that need different boundary definitions than your NGER submission. It's the tenant who won't share their electricity data because their lease says they don't have to.

And now ASRS mandatory reporting is pulling mid-size property companies into the compliance net. Group 2 entities — those with more than $25 million in assets and $50 million in revenue — start reporting from July 2026. That captures most commercial property trusts and a lot of property management companies that assumed this was someone else's problem.

This post is about how multi-site property portfolios should actually approach emissions tracking. Not the theory. The plumbing.

The utility bill collection problem nobody talks about

Here's the thing about a 50-site portfolio. It's not 50 utility bills. It's 50 sites multiplied by the number of meters per site, multiplied by the number of billing periods per year. A typical commercial office building might have separate accounts for base building electricity, common area gas, water, and waste. Some have sub-meters for car parks, loading docks, or retail tenancies at ground level.

For a portfolio of 50 buildings, you're realistically looking at 150 to 400 individual utility accounts. Quarterly billing means 600 to 1,600 bills per year. Monthly billing — which some retailers default to — pushes that north of 2,000.

Now consider that these bills arrive via six different channels. Some come through retailer portals. Some land in a facilities manager's inbox as PDF attachments. Some get forwarded from site managers. Some still arrive by post (yes, in 2026) and get scanned on a multi-function printer at reception. A few show up as photos on someone's phone because the site caretaker snapped the bill before it disappeared under a pile of maintenance requests.

Every one of those documents needs to be opened, read, and transcribed into whatever system you're using to track consumption. Even at five minutes per bill — and that's optimistic when you're dealing with a scanned PDF where the consumption figure sits between a demand profile graph and a solar feed-in credit table — you're looking at 130 to 170 hours per year just on data entry. At a loaded cost of $110 to $120 per hour for a sustainability analyst, that's $14,000 to $20,000 annually. On typing.

That number gets worse when you factor in the error correction cycle. Based on the research we've seen — including a JAMIA study that found a 3.7% discrepancy rate across 6,930 manual data entries — a portfolio of 1,600 bills will contain somewhere between 16 and 60 errors per year. Some of those are harmless. Some cascade through your emission calculations and show up as material misstatements in your NGER report. The ANAO found that 72% of 545 NGER reports contained errors, and 17% had errors the Clean Energy Regulator classified as significant.

For property portfolios, the problem compounds because you're aggregating hundreds of small data points into corporate-level totals. One wrong decimal place on a bill from a shopping centre in Parramatta can shift your portfolio's Scope 2 emissions by hundreds of tonnes.

Base building versus whole-of-building: pick the wrong boundary and your numbers are meaningless

This is where property gets genuinely complicated, and it's where we see the most confusion — even from experienced sustainability consultants.

A base building boundary covers the energy consumed by central services: HVAC plant, lifts, common area lighting, fire systems, car park ventilation. It's the energy the landlord controls and pays for. A whole-of-building boundary adds tenant energy on top of that. Same building, same physical asset, completely different emissions numbers.

NABERS uses both. A NABERS Energy base building rating only counts landlord-metered energy. Under the Commercial Building Disclosure (CBD) program, any office building of 1,000 sqm or more must disclose a NABERS rating at point of sale or lease. That rating is almost always base building. It's the standard the market understands.

But NGER doesn't care about your NABERS boundary. NGER requires you to report emissions from facilities you have "operational control" over. For a property owner who operates the base building and has sub-metered tenants, the NGER boundary might only capture base building energy. But if you're also the landlord on a gross lease where you pay the electricity bill and recover costs from tenants — you operationally control that energy consumption. It goes in your NGER report.

ASRS adds another layer. Under AASB S2, you report Scope 1 and 2 emissions for the reporting entity — the corporate group. And from your second reporting year, you need material Scope 3 emissions too. For a property company, tenant energy use is downstream Scope 3 (Category 13: downstream leased assets). It's not optional. If it's material — and for a commercial office portfolio, tenant energy typically makes up 40% to 60% of total building energy — then you need to disclose it.

So you end up maintaining three different boundary definitions for the same portfolio:

Framework Boundary What's Included
NABERS Energy Base building (most common) Central services, common areas, landlord-metered energy
NGER Operational control All energy where the entity has operational control — varies by lease structure
ASRS (AASB S2) Reporting entity + material Scope 3 Scope 1 & 2 for controlled assets, plus tenant energy as downstream Scope 3 if material

Getting this wrong isn't academic. We've seen a property trust report whole-of-building energy as their base building NABERS figure, which inflated their energy intensity and tanked their star rating. We've also seen the opposite — a company that excluded tenant energy from its NGER report because "NABERS doesn't include it," not realising the boundary definitions are completely different.

The tenant data problem

Let's be honest about something. Tenant energy data is the single hardest piece of carbon accounting for property managers. And there isn't a clean solution.

When a tenant has their own electricity account — common under net leases and most modern green leases — the landlord doesn't see that data. The bill goes directly to the tenant. The landlord has no legal right to access it unless the lease explicitly includes a data-sharing clause.

Older leases (pre-2015, roughly) almost never include such clauses. Even newer green leases with data-sharing provisions often lack enforcement mechanisms. We've heard from property managers who send quarterly data requests to 200 tenants and get responses from maybe 30% to 40%. The rest ignore the email, provide partial data, or send a PDF that's for the wrong period.

This matters because AASB S2 requires disclosure of material Scope 3 emissions from your second reporting year. For a property company, Category 13 (downstream leased assets) is almost certainly material. ASIC through RG 280 has signalled that directors must engage with climate risks personally — you can't just shrug and say "the tenants wouldn't give us the data."

So what do you actually do?

First, estimate where you can't measure. The GHG Protocol allows estimation methods for Scope 3 categories where primary data isn't available. For tenant electricity, you can use floor area proportioning: if the whole building consumes X kWh and the base building consumes Y kWh, then tenant consumption is approximately X minus Y. If you only have the base building meter, you can estimate whole-of-building consumption using NABERS benchmarks for the building type and star rating.

Second, renegotiate leases. Every lease renewal is an opportunity to add a data-sharing clause. It doesn't need to be onerous. A simple requirement that tenants provide quarterly energy consumption data — or authorise the landlord to access it directly from the retailer — solves the problem for the next lease term.

Third, sub-meter. Where lease negotiation fails and estimation isn't precise enough, installing sub-meters on tenant floors or tenancies gives you actual consumption data. The cost is typically $2,000 to $5,000 per meter installed, but for a large building with a poor NABERS rating, the improvement in data quality can pay for itself through better star ratings and higher rental premiums.

We're not going to pretend any of these solutions are quick or painless. Tenant data remains the messiest part of property emissions accounting, and we don't think that changes until the market standardises data-sharing requirements across all commercial leases. We're probably five years away from that.

NABERS, NGER, and ASRS: three frameworks, one data set

Here's the good news buried in all this complexity. Despite the different boundaries and methodologies, all three frameworks draw from the same underlying data: utility bills.

NABERS needs 12 months of energy consumption data to calculate your star rating. NGER needs 12 months of energy and emissions data for your facility-level report. ASRS needs the same consumption data converted to Scope 1, 2, and 3 emissions using appropriate factors.

The input is the same. The emission factors differ slightly — NABERS uses its own greenhouse coefficients (updated annually), while NGER and ASRS both use NGA Factors published by DCCEEW. And the boundaries differ, as we covered above. But the consumption data sitting on those utility bills is the single source of truth for all of it.

This is why automated document processing has such an outsized impact on property portfolios specifically. When you're processing 1,600 bills per year, the ability to extract consumption data once and route it to multiple frameworks — applying the right factors and boundaries for each — eliminates enormous amounts of duplicate work.

At Carbonly, our AI Document Processing engine reads eight document formats (PDF, CSV, multi-sheet Excel, Word, PPT, RTF, images, and scanned documents), applies 5-tier material matching with confidence scoring, and extracts the raw consumption figure, the billing period, the meter ID, and the site address from every bill. That single extraction feeds into NGER calculations using NGA Factors (location-based, with state-specific grid emission factors — 0.64 kg CO2-e/kWh for NSW, 0.78 for Victoria, 0.67 for Queensland under the 2025 NGA workbook). The same data can feed a NABERS assessment through your accredited assessor. And it forms the basis of your ASRS Scope 2 disclosures.

One extraction. Three compliance outputs. That's the efficiency gain that makes property the highest-ROI sector for automated carbon accounting.

But for property portfolios specifically, three other Carbonly modules change the workflow entirely. The Projects module with dedicated email ingestion means each property in your portfolio gets its own email address — building23@inbox.carbonly.ai — and any utility bill forwarded to that address is automatically processed and allocated to the correct site. No more shared drive folders. No more manual sorting. The site caretaker who snaps a bill on their phone can email it directly. The same module supports OneDrive sync, so if your portfolio's bills are already landing in a shared drive structure, Carbonly pulls and processes them automatically on import.

The Scheduled Reports module delivers building-by-building or portfolio-level emissions reports — NGER, GHG Protocol, Custom, or Executive Summary format — on a recurring schedule directly to building owners, fund managers, or your GRESB reporting team. Monthly summaries to the asset manager, quarterly reports to the trust board, annual NGER data to your compliance team — configured once and delivered without anyone remembering to run the export.

Why property managers are the first to benefit from automation

We built Carbonly — an 18-module platform — because we spent 18 years watching enterprises drown in manual data processing — at BHP, Rio Tinto, Senex Energy, Schneider Electric. The pattern was always the same: smart people spending dumb time on data collection.

But property is where the problem is most acute and most solvable. Here's why.

The data is structured. Utility bills follow a finite set of formats. There are maybe 15 to 20 major energy retailers in Australia, plus a handful of water authorities and waste contractors. Each has a small number of bill templates. Compare that to Scope 3 supply chain data, where you might be dealing with invoices from 500 different suppliers in different industries, currencies, and languages. Property portfolio utility bills are hard because of volume, not because of variety.

The volume justifies the investment. A manufacturer with three facilities and 12 utility accounts doesn't have a document processing problem. They have a Tuesday afternoon. A property manager with 50 buildings and 300 utility accounts has a full-time job's worth of data entry. The time savings from automation scale linearly with portfolio size.

The regulatory pressure is immediate. If your portfolio crosses the NGER threshold of 50 kt CO2-e or 200 TJ — and a commercial property portfolio of 50+ buildings probably does — you're already reporting. If your parent entity or trust meets ASRS Group 2 thresholds, you're reporting from July 2026. The CBD program already requires NABERS ratings on any office sale or lease above 1,000 sqm. Property is one of the most heavily regulated sectors for energy and emissions disclosure.

And the penalty for getting it wrong is real. The Beach Energy enforceable undertaking from July 2025 — three years of mandatory external audits for misstated NGER reports — is a cautionary tale. For a property trust managing investor capital, that kind of compliance failure affects more than just the sustainability team. It hits the fund's reputation with institutional investors, GRESB ratings, and tenant negotiations.

What a working system actually looks like

Forget the theory for a minute. Here's what day-to-day carbon accounting looks like for a property portfolio that's actually doing it properly.

Bills arrive. Doesn't matter how — email, portal download, scanned at reception, forwarded from a site manager's phone. They go into a central intake point. Not a shared drive folder called "Utility Bills 2026" that nobody organises.

Each bill gets processed automatically. The system reads the document, extracts consumption, billing period, meter number, and site address. It validates the data against historical patterns — if Building 23 in Melbourne usually draws 85,000 kWh per quarter and this bill says 8,500, something's off. It flags anomalies for human review instead of silently accepting bad data.

The consumption data gets tagged to the correct site, the correct meter, and the correct reporting boundary. Base building meter? That flows into your NABERS data, your NGER report, and your ASRS Scope 2. Tenant meter you happen to have data for? That goes into your ASRS Scope 3 Category 13 disclosure but stays out of your base building NABERS calculation.

Emission factors get applied automatically. The system knows that a Victorian building uses 0.78 kg CO2-e/kWh and a Queensland building uses 0.67, because those are the 2025 NGA location-based factors. It knows the difference between location-based and market-based methods — and that AASB S2 paragraph 29(a)(v) requires location-based as the primary disclosure.

And every step is logged. Every bill, every extracted value, every factor applied, every calculation — linked in a chain you can hand to an auditor. That's the part most spreadsheet-based systems can't deliver, and it's the part that keeps your compliance standing intact when the CER or ASIC comes asking.

The honest bit

We're not going to claim that automation solves everything for property portfolios. It doesn't.

Tenant data gaps remain genuinely difficult. If a tenant won't share consumption data and you don't have sub-meters, you're estimating — and estimation introduces uncertainty that needs to be disclosed under AASB S2.

Refrigerant emissions from HVAC systems — which are Scope 1 for the building operator — still rely on maintenance logs from contractors. No amount of AI document processing helps if the chiller maintenance report is handwritten on a job card and stuffed in a filing cabinet at the site.

And NABERS assessments still require an accredited assessor. You can feed them better, cleaner, faster data. But you can't skip the human in that loop. Nor should you — the assessor's independence is what gives a NABERS rating its credibility.

What automation does solve is the 130 to 170 hours of manual data entry, the error rates that compound across hundreds of bills, and the audit trail gaps that turn a compliance exercise into a compliance crisis. For a 50-site portfolio, that's the difference between a reporting process that runs for weeks and one that runs for days.

If you manage a property portfolio and your emissions data still lives in a spreadsheet with 1,400 rows that only one person understands — forward this to your CFO. They're about to get very interested in this problem when the ASRS Group 2 deadline hits.


Related Reading: