Carbon Accounting Supply Chain: The Multi-Currency Problem Nobody Warned You About

Last quarter, we ran a test. We took a single invoice from an Australian construction company — US$380,000 for structural steel from a Chinese supplier — and calculated the Scope 3 emissions three different ways. Same invoice. Same emission factor database. The only variable was how we handled the currency conversion.

The results: 247 tonnes, 312 tonnes, and 198 tonnes CO2-e.

A 58% spread. Not from different methodologies. Not from different emission factors. From exchange rate choices alone.

This is the carbon accounting supply chain problem that's hiding in plain sight for Australian importers. And with Scope 3 reporting becoming mandatory for ASRS Group 1 entities in their second year and Group 2 coming online from July 2026, it's about to become everyone's problem.

Australia's Multi-Currency Supply Chain Reality

Australia imported $629.9 billion in goods and services in 2024-25, according to the ABS. Our top five import partners — China ($120B), the United States ($96.8B), Japan ($32.4B), Singapore ($26.4B), and Thailand ($23.5B) — trade in five different currencies. Add Germany ($8B+), the UK, South Korea, and Malaysia, and you're looking at eight or nine currencies flowing through Australian procurement systems before anyone thinks about carbon.

That matters because the emission factor databases used for spend-based Scope 3 calculations are denominated in specific currencies. EXIOBASE — the most widely used global database with 9,800 emission factors across 49 regions — is denominated in EUR, calibrated to a 2019 base year. The UK DESNZ factors (formerly BEIS) are in GBP. USEEIO factors from the US EPA are in USD. Australia's own spend-based factors (published through Zenodo, derived from ABS input-output tables) are in AUD — but they cover fewer sectors and are less frequently updated.

So here's what happens in practice. You receive an invoice from a Chinese supplier in USD. You want to apply an EXIOBASE emission factor, which is in EUR. You need to convert USD to EUR. But which exchange rate? The rate on the invoice date? The annual average for 2026? The 2019 rate matching EXIOBASE's base year? Each choice gives you a different number.

And that's the simple case. The hard case is when you're consolidating emissions across 200 suppliers in twelve countries, with invoices in AUD, USD, EUR, GBP, CNY, JPY, and SGD, all flowing into a single ASRS disclosure denominated in metric tonnes of CO2-e. The currency problem compounds at every step.

Why the Conversion Maths Breaks Down

The spend-based emissions formula looks simple: Spend (in factor currency) x Emission Factor (kgCO2e per unit of factor currency) = Emissions.

Three things make it not simple.

The base year mismatch. EXIOBASE 3.8.2 factors reflect the economic and environmental structure of 2019. The AUD averaged 0.695 against the USD in 2019. In 2025, it averaged 0.645. That's a 7.2% shift in the exchange rate alone. But the economic relationship between currencies isn't just about the spot rate — it's about what a dollar actually buys in each economy, which changes with inflation.

If you're applying 2019 EUR-denominated factors to 2026 AUD-denominated invoices, you need to do two things: deflate your 2026 spend back to 2019 prices (using CPI or producer price indices), and convert from AUD to EUR using the 2019 exchange rate. Skip the deflation step — which most companies do — and you're effectively treating inflation as if it were real procurement growth. Australia's CPI rose roughly 20% between 2019 and 2025. That's a 20% overstatement of emissions before you've made a single methodological choice about anything else.

The Climatiq guidance on EXIOBASE is explicit about this: "if companies use expenditure data from recent years in their emissions calculations, they must apply inflation correction in order to compare to older data from IOTs." They recommend using sector-specific producer price indices, not just headline CPI. But in practice, who does this? We haven't seen a single mid-market Australian company apply sector-specific inflation adjustment to their spend-based Scope 3 calculations. Not one.

The purchasing power parity problem. This is the one that really keeps us up at night, and we're honestly not sure the carbon accounting industry has grappled with it yet.

A dollar of steel fabrication services purchased in China is not equivalent to a dollar of steel fabrication services purchased in Germany. The PPP adjustment factor between China and the Eurozone is roughly 2:1 — meaning a dollar buys about twice as much physical output in China as in Germany. But EXIOBASE emission factors treat every euro of output from a given sector the same way within a region.

In practice, this means that if you convert a US$380,000 invoice from a Chinese supplier into EUR and apply a European emission factor, you're massively understating the physical volume of production that invoice represents. The Chinese factory produced far more steel per dollar than a German factory would for the same price. More production means more emissions. The spend-based factor doesn't capture this.

We don't have a clean solution for this. The GHG Protocol doesn't address PPP in its Scope 3 calculation guidance. EXIOBASE has region-specific factors (so the China factor differs from the Germany factor), which partially accounts for it. But when you're using the factor for one region and the invoice is denominated in another region's currency, PPP distortions creep in.

The exchange rate timing question. Even if you get the base year and PPP issues right, you still have to pick an exchange rate. There are at least four defensible options:

Transaction-date rate (the rate on the day each invoice was issued)
Period-average rate (the average for your reporting period)
Factor-base-year rate (the 2019 rate, matching EXIOBASE's vintage)
Year-end rate (closing rate for your financial year)

AASB S2 doesn't prescribe which exchange rate to use for Scope 3 spend conversions. AASB 121 (The Effects of Changes in Foreign Exchange Rates) applies to financial transactions, but the intersection with emissions calculations is genuinely uncharted territory. What your auditor will care about is consistency. Pick a method, document it in your Basis of Preparation, apply it uniformly, and don't change it between periods without explaining why.

Our position: use the factor-base-year rate for the conversion into the emission factor's currency, after deflating your spend to that base year. It's methodologically the cleanest approach because it keeps the economic structure consistent — your deflated spend reflects what it would have cost in 2019, converted at what the exchange rate actually was in 2019. But we'll be the first to admit this isn't established best practice yet. It's our best interpretation of how the numbers should work.

A Worked Example: Four Invoices, Four Currencies

Consider a mid-market Australian manufacturer with an international supply chain. In Q3 2026, they process four invoices for Scope 3 Category 1 (purchased goods and services):

Invoice 1: US$180,000 for electronic components from a US supplier. USEEIO emission factor: 0.42 kgCO2e/USD for "Electronic component manufacturing." No currency conversion needed — factor and invoice are both in USD. Emissions: 75,600 kgCO2e (75.6 tonnes).

Invoice 2: EUR 95,000 for precision bearings from a German supplier. EXIOBASE factor for "Machinery and equipment" in Germany: 0.38 kgCO2e/EUR (2019 base year). The invoice is already in EUR, so no currency conversion. But the spend is in 2026 euros, and the factor reflects 2019 economic conditions. Eurozone CPI rose roughly 22% from 2019 to 2025. Deflated spend: EUR 95,000 / 1.22 = EUR 77,869. Emissions: 29,590 kgCO2e (29.6 tonnes). Without the inflation adjustment? 36,100 kgCO2e — a 22% overstatement.

Invoice 3: A$420,000 for steel from a Chinese supplier (invoiced in AUD). Now it gets interesting. The emission factor is from EXIOBASE (EUR). Steps: deflate AUD spend from 2026 to 2019 prices (Australian CPI ~1.20), giving A$350,000. Convert to 2019 EUR using the 2019 AUD/EUR rate (~0.62), giving EUR 217,000. Apply the EXIOBASE factor for "Basic metals" in China: ~0.85 kgCO2e/EUR. Emissions: 184,450 kgCO2e (184.5 tonnes).

What if you skip deflation and use the current exchange rate instead? A$420,000 at 2026 AUD/EUR (~0.59) = EUR 247,800 x 0.85 = 210,630 kgCO2e. That's 14% higher — a 26-tonne difference from one invoice.

Invoice 4: GBP 45,000 for engineering consultancy from a UK firm. DESNZ 2025 factor for "professional, scientific and technical activities": 0.21 kgCO2e/GBP. Factor and invoice are both in GBP, and the DESNZ factors are updated annually (unlike EXIOBASE's 2019 vintage), so the inflation adjustment is minimal. Emissions: 9,450 kgCO2e (9.5 tonnes).

Total across all four invoices using the deflation method: 299 tonnes. Without deflation and using current exchange rates: 331 tonnes. That's an 11% difference. Across a full year of international procurement, that gap compounds fast.

Where the Real Errors Hide

The worked example above is actually the easy version. In reality, most Australian companies face three additional problems that make the currency issue worse.

Problem 1: You don't know the invoice currency. This sounds ridiculous. But when your accounts payable team processes 500 invoices a month, currency metadata often doesn't make it into the ERP cleanly. A "

quot; symbol on an invoice could mean AUD, USD, SGD, or NZD depending on the supplier's country. If someone in AP coded a US supplier's USD invoice as AUD, your Scope 3 calculation just shifted by 35-55% (depending on the AUD/USD rate that year).

In Carbonly, our AI document extraction is trained to recognise currency patterns across formats — $45,000, A$45,000, AUD 45,000, US$12,000, EUR 8,500 — and maps them to the correct ISO currency code. It sounds like a small detail. It's not. We've seen procurement datasets where 8-12% of invoices had the wrong currency recorded in the source system. On a $50 million import portfolio, that's $4-6 million of spend attributed to the wrong currency. The carbon error follows directly.

Problem 2: Your suppliers don't invoice in their home currency. A Chinese manufacturer might invoice in USD because that's standard for international trade. A German equipment maker might quote in EUR but invoice an Australian subsidiary in AUD. The invoice currency doesn't tell you where the goods were produced or which regional emission factor to apply.

This matters because EXIOBASE factors are region-specific. The emission intensity of "basic metals" in China (0.85 kgCO2e/EUR) is very different from "basic metals" in Germany (0.35 kgCO2e/EUR). If your system defaults to applying the emission factor based on invoice currency rather than country of origin, you'll understate emissions from high-intensity manufacturing regions and overstate emissions from low-intensity ones.

Problem 3: Mixed-currency contracts. Some supply chain arrangements involve multiple currencies in a single contract. A construction company might have an equipment supply agreement with a Japanese manufacturer, priced in USD, with installation services billed in AUD, and spare parts invoiced in JPY. Each component needs separate treatment. Most procurement systems don't capture this granularity. The whole contract ends up under one currency code.

What ASRS Actually Requires (And What It Doesn't)

AASB S2 paragraph 29(a)(iii) requires entities to disclose "the measurement approach, inputs and assumptions the entity uses" for its greenhouse gas emissions. That's broad. It doesn't say "disclose your exchange rate methodology for Scope 3 spend-based calculations." But an auditor performing limited assurance under ASSA 5010 will ask how you got from a pile of multi-currency invoices to a single tCO2e number. And they'll want to see that the method was applied consistently.

The good news: Scope 3 disclosures fall under the modified liability protections running through December 2027. Only ASIC can take enforcement action, and only through injunctions or declarations — not penalties. So getting your currency methodology imperfect isn't a compliance catastrophe. Getting it undocumented is.

Here's what we think the minimum documentation looks like for multi-currency Scope 3:

Which emission factor databases you used, and why
The base year and currency denomination of each database
Whether you applied inflation deflation (and which price index)
Which exchange rate methodology you used (transaction-date, period-average, or base-year)
How you determined the country of origin for imported goods (invoice currency, supplier address, or goods classification)
Any assumptions made for invoices where currency was ambiguous

That list isn't in AASB S2. It's what we've seen auditors ask for from Group 1 entities in their first reporting cycle. Write it up. Put it in your Basis of Preparation. It takes half a day and it saves weeks during assurance.

A System That Handles This Automatically

We built multi-currency support into Carbonly because we kept watching companies get this wrong in spreadsheets. The workflow runs like this.

Documents come in through email ingestion or OneDrive sync — invoices, purchase orders, freight bills. Our AI document engine reads each one, identifies the currency from the notation (A$, US$, EUR, GBP, or explicit ISO codes), and tags the extracted spend with the correct currency code.

When the system calculates emissions using spend-based factors, it checks whether the invoice currency matches the emission factor currency. If the invoice is in AUD but the best-fit emission factor is from EXIOBASE (EUR), the system converts automatically. It uses the factor-base-year exchange rate and applies CPI deflation to adjust the spend to the factor's vintage. The conversion is logged — every step, every rate, every adjustment — so your auditor can trace a single emission figure back to the source invoice, the currency detected, the conversion applied, and the factor selected.

We support AUD, USD, EUR, GBP, NZD, CAD, and SGD as invoice currencies, with emission factors denominated in kgCO2e per unit of AUD, USD, EUR, GBP, and NZD. That covers the vast majority of Australian import trade. For the occasional invoice in JPY, CNY, or THB, the system flags it for manual currency assignment rather than guessing — because getting it wrong silently is worse than asking the user to confirm.

Is it perfect? No. We're using static annual-average exchange rates, not transaction-date rates. For most companies, the difference between annual-average and transaction-date conversion is 2-5% — material enough to acknowledge, small enough that the cost of implementing daily rate lookups isn't justified for Scope 3 estimates that already carry 30-40% uncertainty from the emission factors themselves.

The Categories Where Currency Hits Hardest

Not all Scope 3 categories are equally exposed to currency risk. Here's where it matters most for Australian companies.

Category 1 — Purchased Goods and Services. This is the big one. For companies with international supply chains, Category 1 is typically 40-70% of total Scope 3 emissions. If you're importing raw materials from China in USD, components from Germany in EUR, and professional services from the UK in GBP, you've got the full currency conversion stack on your largest emissions category. A construction company importing $20 million of steel annually could see a 2,000-4,000 tonne swing in reported emissions depending on currency methodology. That's material by any definition.

Category 4 — Upstream Transportation and Distribution. International freight is almost always invoiced in USD, regardless of origin or destination. The emission factors for freight (in tonne-km) are typically physical, not spend-based, so the currency issue is less severe here. But when you only have freight cost data (no tonne-km), you're back to spend-based, and the USD/AUD conversion matters.

Category 6 — Business Travel. Flights booked through US-based platforms (Concur, Amex GBT) are often processed in USD. Hotels in international destinations are in local currency. If you're using spend-based factors for travel rather than distance-based methods, every international trip involves a currency conversion.

Category 15 — Investments. For financial institutions and companies with investment portfolios, financed emissions calculations involve the investee's emissions allocated by ownership share. If the investee reports in USD or EUR and the investor reports in AUD, the financial attribution calculation needs consistent currency treatment. This category is growing in importance as APRA-regulated entities face ASRS requirements.

The Three Mistakes We See Every Time

After processing thousands of international invoices through our system, we've noticed three currency-related errors that show up repeatedly.

Mistake 1: Using national-average emission factors for all imports. If you import steel from both China and Sweden, applying the same emission factor to both because your factor database only has a global average is a significant error. China's steel industry emits roughly 1.8 tCO2e per tonne of crude steel production. Sweden's is around 0.5 tCO2e (high proportion of electric arc furnace using clean grid electricity). A global average of ~1.2 tCO2e per tonne understates your Chinese imports and overstates your Swedish imports. Always use region-specific factors when available. EXIOBASE provides them for 49 regions.

Mistake 2: Double-counting currency effects. This happens when someone deflates the spend amount using Australian CPI, then converts to EUR using the current exchange rate instead of the base-year rate. You've partially adjusted for Australian inflation but used an exchange rate that already reflects the inflation differential between Australia and Europe. The result is an inconsistent number that's neither properly inflation-adjusted nor properly converted.

Mistake 3: Treating all "

quot; as AUD. We mentioned this above, but it bears repeating because of how common it is. In one procurement dataset we reviewed, a company had US$2.3 million in software licensing (from a US vendor) recorded as A$2.3 million. At a 0.65 AUD/USD rate, the actual AUD-equivalent spend was A$3.54 million. The carbon understatement was proportional — roughly 35% on that line item.

What We'd Do Differently If Starting Today

If we were building a carbon accounting supply chain measurement system from scratch — knowing what we know from processing thousands of multi-currency documents — here's the approach we'd take.

First, fix the currency at the point of data entry. Don't let invoices into your system without a confirmed currency code. Train your AP team (or your AI extraction engine) to tag every invoice with the correct ISO 4217 code. AUD, USD, EUR, GBP, NZD. Not "

quot;. Not "dollars." The three-letter code.

Second, maintain a supplier master with country of origin. The invoice currency tells you how you paid. The country of origin tells you which regional emission factor to apply. They're different pieces of information, and you need both. A Chinese manufacturer invoicing in USD still needs a China-region emission factor. Link your supplier records to their primary manufacturing or service delivery location.

Third, choose one emission factor database as your primary source and document the decision. If you're using EXIOBASE for purchased goods and DESNZ for UK services, write that down. Explain why. Don't mix databases for the same category unless you have a good reason, because each database uses slightly different sector classifications and the factors won't be comparable.

Fourth, build the deflation and conversion into your calculation pipeline. This isn't something to do manually once a year. Every spend-based calculation should automatically deflate to the factor base year and convert at the base-year rate. In Carbonly, this happens at the individual line-item level, with a full audit trail for each step. If you're doing this in spreadsheets, build the formula chain once and never touch it again. A broken VLOOKUP in a currency conversion column can cascade into every Scope 3 number in your report.

Fifth, accept that you're working with estimates. The combined uncertainty from emission factor selection, sector classification, inflation adjustment, exchange rate timing, and PPP distortion means your spend-based Scope 3 number is probably accurate to plus or minus 30-50%. That's okay for initial reporting. It's not okay forever. Use the spend-based screen to identify your highest-impact suppliers, then invest in collecting activity data from those top 20-30 relationships. Currency problems disappear when you switch from kgCO2e/dollar to kgCO2e/tonne-of-steel or kgCO2e/kWh.

The Honest Admission

We're still working through some of this ourselves. The PPP adjustment for spend in developing economies is genuinely unsolved in the carbon accounting literature. EXIOBASE's region-specific factors help, but they're calibrated to 2019 economic structures that have shifted since then. We don't know what "best practice" looks like for an Australian company importing $50 million of manufactured goods from Southeast Asia, where PPP ratios to the Eurozone range from 2:1 to 3:1 depending on the country.

And the emission factor databases themselves are ageing. EXIOBASE 3.8.2 reflects 2019. The global economy — and its emissions intensity — has changed. Some sectors have decarbonised. Others haven't. Applying 2019 factors to 2026 procurement with only an inflation adjustment doesn't capture real changes in industrial emissions intensity. Better databases are coming (EXIOBASE 3.9, updated USEEIO), but they're not here yet.

What we can say is this: documenting your methodology clearly matters more than getting the methodology perfect. AASB S2's modified liability protections give Australian companies three years to refine their approach. Use that time. Start with what you have, make the currency conversions explicit, log every assumption, and improve the data quality year on year. That's what auditors want to see. That's what makes a Scope 3 disclosure defensible.

Your supply chain emissions number is going to be wrong. The question is whether it's wrong in a documented, traceable, improvable way — or wrong because someone put the wrong currency code on a spreadsheet six months ago and nobody noticed.

Start with your top 20 import suppliers. Confirm the currency on every invoice. Map each supplier to a country of origin. Run the numbers with explicit deflation and base-year conversion. Then write down exactly what you did. That's the foundation everything else builds on.

Related Reading: