Joint Venture Emissions Allocation: The Multi-Party Problem Most Platforms Ignore

When you hold a 40% equity stake in a joint venture, you report 40% of its emissions — in theory. In practice, getting that number right requires the operator to share facility-level data you can't verify, a consolidation approach that aligns with both NGER and AASB S2, and a system that handles proportional allocation without double-counting. Most carbon accounting platforms don't even try.

Denis Kargl February 27, 2026 13 min read
Joint VenturesEmissions AllocationNGERASRSEquity ShareCarbon AccountingMining Emissions
Joint Venture Emissions Allocation: The Multi-Party Problem Most Platforms Ignore

Woodside reported gross equity Scope 1 and 2 emissions of 6,616 kt CO2-e for calendar year 2025. That number represents their proportional share across operated and non-operated assets — the NWS Project at 33.33%, Scarborough at 74.9%, Pluto at 100%. Each percentage means a different fraction of facility-level emissions landing in Woodside's consolidated inventory.

Now imagine you're a mid-market mining or energy company with two or three JV interests, no dedicated sustainability team, and a spreadsheet where someone manually multiplies total facility emissions by your ownership percentage. That's how most joint venture emissions allocation actually happens in Australia. And it's a compliance problem that gets worse the moment you need to reconcile it across NGER, GHG Protocol, and AASB S2 — three frameworks that each define your reporting boundary differently.

After 18 years building data systems at BHP, Rio Tinto, and Senex Energy, I watched this problem up close. JV partners arguing about whose emissions belong to whom. Operators sharing annual totals in PDFs with no supporting data. Equity holders plugging those numbers into their own reports with no way to verify them. The data flow between JV partners was — and in most companies, still is — a mess.

The Boundary Problem: Three Frameworks, Three Answers

The core difficulty with joint venture emissions allocation isn't the maths. Multiplying emissions by an equity percentage is straightforward. The difficulty is that NGER, GHG Protocol, and AASB S2 each draw the boundary in a different place — and for companies reporting under multiple frameworks, the same facility can appear in your inventory differently depending on which framework you're using.

Under NGER, the reporting entity is the "controlling corporation," and the test is operational control. Section 11 of the NGER Act says a group entity has operational control over a facility if it has the authority to introduce and implement operating, health and safety, and environmental policies. Only one entity can have operational control at any time. So in a typical mining JV — say, a 60/40 split where the majority partner operates the mine — the operator's corporate group reports 100% of that facility's emissions under NGER. The 40% partner reports zero for that facility.

The GHG Protocol offers a choice. You can report using equity share (40% partner reports 40% of emissions), financial control, or operational control. But you have to choose one approach and apply it consistently across all your operations. BHP, for example, uses equity share — they report their proportional share of Scope 1 and 2 emissions across operated and non-operated assets. Woodside does the same. It's the dominant approach in resources because companies hold complex webs of minority and majority interests, and operational control would exclude emissions from assets they part-own but don't operate.

AASB S2 adds another layer. Paragraph 29(a)(iv) requires entities to disaggregate their Scope 1 and 2 emissions between the consolidated accounting group (parent plus consolidated subsidiaries) and "other investees" — which includes associates, joint ventures, and unconsolidated subsidiaries. So even if you use equity share for GHG Protocol, your AASB S2 disclosure needs to split those numbers into "what's in the consolidated group" and "what isn't."

For a company with three JV interests, this means maintaining three separate views of the same underlying data. NGER: you only report facilities you operate. GHG Protocol equity share: you report your proportional share of every facility you hold equity in. AASB S2: you report both, disaggregated.

Why Double-Counting Is a Real Risk — Not a Theoretical One

The GHG Protocol's own FAQ acknowledges it: when JV partners use different consolidation approaches, the same emissions can be counted twice or not counted at all.

Here's how it happens. Partner A operates a facility and uses the operational control approach. They report 100% of the facility's emissions. Partner B holds a 40% equity stake and uses the equity share approach. They report 40% of the same facility's emissions. The emissions inventory now contains 140% of what the facility actually emitted.

The GHG Protocol says this is "acceptable" for reporting purposes — it's not a flaw, it's a known feature of allowing different consolidation approaches. But it creates real problems when you aggregate emissions across a sector, when investors compare companies, or when a regulator is trying to understand whether a facility's emissions have been adequately accounted for.

In Australia, the risk is amplified because NGER uses operational control exclusively while many companies use equity share for their voluntary GHG Protocol reporting and AASB S2 disclosures. A Covington analysis of GHG accounting in transactions noted that if two organisations have a joint venture but choose different consolidation approaches, some emissions may not be counted by either company — or may be double-counted by both.

The ISS governance team at ESG research found striking differences. Shell and TotalEnergies reported approximately 49% and 41% higher emissions respectively under equity share compared to operational control. Woodside showed the opposite — 61% lower emissions under equity share, because it operates facilities where it holds minority stakes.

These aren't marginal differences. They're large enough to change whether a company exceeds its Safeguard Mechanism baseline. Large enough to shift an SBTi target pathway. Large enough that an auditor will ask how you reconcile them.

The Data Sharing Wall Between Partners

Even if you get the boundary question right, you hit the next problem: data access.

The operator tracks facility-level emissions. They run the meters, collect the fuel receipts, monitor the flue gas analysers. They hold the source data. But the non-operating equity partner — who needs a proportional share of those emissions for their own reporting — typically receives a summary number once a year. Sometimes it's a PDF attachment to an email. Sometimes it's a single line item in a JV committee presentation.

That summary number rarely comes with the supporting documentation an auditor needs. No breakdown by emissions source. No indication of which emission factors were applied. No detail on the measurement method — was diesel consumption based on bulk fuel deliveries or individual vehicle fill records? Was methane measured or estimated using NGER Method 1 defaults?

This matters enormously for mining. As we covered in our mining emissions guide, the difference between NGER Method 1 and Method 2 for fugitive coal mine methane can be a factor of three to ten. If the operator switches methods mid-year, your equity share jumps or drops dramatically — and you may not even know until you get the annual summary.

Under AASB S2, assurance requirements are ramping up. Your auditor is going to want traceability from your reported number back to a source document. "The operator told us" isn't a basis of preparation that will survive a limited assurance engagement.

What We Built — and Why Nobody Else Has

This is the problem we built Carbonly's JV Collaboration module to solve. Not because it's a nice feature to have. Because we sat in enough JV operating committee meetings to know that emissions data sharing between partners is fundamentally broken.

The module supports five JV types — equity, contractual, consortium, partnership, and alliance — with structural templates for equal partnership, majority-minority, multi-party, and tiered arrangements. Each partner is assigned a role (operator, partner, investor, contractor, or advisor) and an equity percentage. The system enforces that total ownership across all partners doesn't exceed 100%.

Each partner sees their proportional share of emissions based on their equity stake. If the operator records 10,000 tonnes CO2-e at a facility and you hold 35%, you see 3,500 tonnes in your dashboard. The underlying data — bills, fuel records, emission factor selections — is available based on 10 granular cross-organisation permissions covering emissions data, reports, targets, incidents, documents, materials, and team members. You can grant a JV partner read-only access to emissions data without exposing your internal targets or incident records.

Consolidation follows the method you've chosen. Full consolidation for subsidiaries. Proportional consolidation for jointly controlled operations. Equity method for associates. Operational control for NGER. The system tracks which method applies to which entity, so the same underlying emissions data can produce an NGER report (operational control, 100% of operated facilities) and an AASB S2 disclosure (disaggregated between consolidated group and other investees) without manual rework.

Data sync between JV partners can run in real-time, daily, weekly, monthly, quarterly, or annually — configurable per JV arrangement. Every data point shared carries a full audit trail.

We reviewed every major carbon accounting platform on the market before building this. None of them have purpose-built JV collaboration with equity-based allocation, cross-org permissions, and multi-method consolidation. The common workaround is exporting a CSV from the operator's system and importing it into the partner's spreadsheet. Which brings us full circle to the original problem.

The NGER Nomination Wrinkle

There's a specific quirk in the NGER Act that most people miss. Section 11B allows JV partners to nominate one entity to report a facility's data. But this is optional. If no nomination is made, the Act allows — and arguably expects — each partner in an unincorporated JV to include the facility data in their own corporate group report.

The Clean Energy Regulator's supplementary guideline on operational control says that where two or more corporations could introduce and implement the relevant policies, the one with "greatest authority" over both operating and environmental policies is taken to have operational control. But what "greatest authority" means in a 50/50 JV is genuinely ambiguous. We've seen partners disagree about this — sometimes for years.

For NGER compliance, getting the operational control determination wrong doesn't just affect the emissions number. It affects which corporate group triggers the 50,000-tonne registration threshold and which entity is liable for late or incorrect reporting. The penalties start at $660 per contravention for civil penalties (at the current unit value of $330), and criminal penalties for dishonest behaviour can reach two years' imprisonment.

If you're a non-operating JV partner sitting below the NGER threshold, you might think this doesn't affect you. But under the ASRS Group 2 pathway, every NGER-registered corporation is automatically pulled into mandatory climate-related financial disclosures. And if the operator's NGER registration captures your facility through a nomination arrangement, changes to that arrangement can shift your own ASRS obligations.

What We're Honest About

We built the JV module because we know this problem intimately from the resources sector. But we won't pretend it solves everything.

Changing ownership stakes mid-reporting period is messy. If your equity interest in a JV changes from 40% to 55% partway through a financial year, emissions need to be apportioned pro rata. Our system handles this — but the underlying data from the operator still needs to be reported in a way that allows the split. If the operator only provides annual totals, you're estimating.

Multi-jurisdictional JVs are harder again. An Australian company with a 30% stake in a Papua New Guinean LNG project faces different emission factor regimes, different reporting calendars, and different measurement standards. We can handle the allocation maths, but the emission factors and regulatory requirements outside Australia aren't in our NGA Factors database. We're working on it, but today, cross-border JVs require manual factor configuration.

And the biggest honest limitation: for the full benefit of the collaboration module, the other JV partner needs to be on the platform too. If they're running their own system (or a spreadsheet), you're back to ingesting their data from a file. We've designed the import process to handle this — you can upload operator-provided data and apply your equity percentage — but you lose the real-time sync, the shared audit trail, and the granular permissions.

We're also not sure our current approach scales cleanly beyond five or six partners in a single JV. The permission matrix gets complicated. We haven't hit a real-world test at that scale yet.

Pick Your Consolidation Method Before You Pick Your Software

The decision between equity share and operational control isn't a software configuration choice. It's a strategic decision that affects your total reported emissions, your Safeguard Mechanism exposure, and your AASB S2 disclosures for every reporting period going forward.

For companies with significant non-operated JV interests — common in mining, oil and gas, and infrastructure — equity share usually captures a more complete picture of your emissions exposure. It also aligns better with how investors think about risk: if you own 40% of a high-emitting asset, they want to see 40% of those emissions in your inventory, regardless of who operates it.

But NGER gives you no choice. It's operational control only. So if you're reporting under both frameworks, you need a system that can maintain both views of the same underlying data without manual reconciliation.

That's the system we built. If you're managing JV emissions allocations in a spreadsheet today — especially if you're approaching your first AASB S2 reporting cycle — the reconciliation gap between what NGER requires and what AASB S2 requires is about to become your biggest data problem. Start by documenting which consolidation approach you've chosen for GHG Protocol, mapping it against your NGER operational control determinations, and identifying every JV where the two approaches produce different numbers.

Related Reading: