The Financial Controller's Carbon Month-End Close

The carbon ledger arrived in the finance function without an operating manual. AASB S2 landed as a financial disclosure standard, sitting under the same audit regime as the statutory accounts, and quietly transferred a significant piece of monthly work to people who did not sign up for it: the Financial Controller and their team.

The Sustainability Lead can still own the methodology, the emission factors, and the narrative. But the discipline of period cut-off, materiality review, reconciliation to source, and sign-off before the period closes belongs in finance. It has to, because that is where the audit committee will point when ASSA 5010 assurance starts looking for control evidence.

This is a working piece on what the carbon month-end close actually looks like, what reconciles, what does not, and where the sensible split of ownership sits.

Why the carbon ledger needs a month-end close at all

Voluntary sustainability reporting could survive on an annual roll-up. You pulled the year of data in July, worked it up through August and September, and published in October. If a number moved, you fixed it in the next year's report.

AASB S2 does not allow that. It sits under the same financial reporting framework as your statutory accounts, which means:

Period cut-off matters. Emissions incurred in June belong to the June period, not the July period when the utility bill arrives.
Restatements are visible. Change a factor mid-year and the auditor wants to see the version history, the sign-off, and the retrospective impact.
Materiality applies. Not every kilogram is worth reconciling, but the threshold has to be documented, applied consistently, and defensible.
Sign-off is discrete. Someone has to close the period, log it, and lock it.

Once you accept that the carbon ledger sits under the same rules as the GL, monthly close becomes obvious. You cannot post a July journal after August has closed. You should not be able to post July emissions after August has closed either.

That is why period locking is now a standard capability in carbon accounting systems, not a nice-to-have. It is the same control your finance system already enforces on the GL, applied to the emissions ledger.

What actually reconciles

Three categories of reconciliation work cleanly at month-end. These are the ones a Financial Controller can put on a checklist and expect to close.

Utility spend to activity data

Electricity bills, gas bills, and water bills all have a spend line (dollars) and an activity line (kWh, MJ, kL). Both flow through to different systems: the spend line hits accounts payable, the activity line hits the emissions ledger via the emission factor library.

The reconciliation is: for each site, does the activity data in the emissions ledger match the activity data on the utility bill that was paid? If yes, the period ties. If no, one of three things is wrong: the AP entry was coded to the wrong site, the emission record was assigned to the wrong period, or a bill is missing.

Practical rule: match on invoice number and billing period end-date. If both agree between the AP subledger and the emissions ledger for the period, the utility line is clean.

Fuel card statements to Scope 1 diesel

Fuel card statements are structured, consolidated, and arrive on a monthly cadence. They are the cleanest input the emissions ledger has. Each transaction has a date, a litre count, a fuel type, and a vehicle identifier.

The reconciliation is: total litres per fuel type on the fuel card statement equals total litres in the Scope 1 diesel line on the emissions ledger. Any difference is a data pipeline issue, not an emission issue.

Where this breaks: fleet vehicles refuelled at bulk on-site tanks (not on the fuel card), owner-operator subcontractors who invoice separately, or fuel used in stationary plant (Scope 1 but not fleet). These need separate reconciliations, but each one is tractable if the source data lands in the system.

Procurement PO to Scope 3 Category 1 (activity-based)

This one reconciles only if you are running Scope 3 Category 1 on activity data (physical quantities of goods purchased), not on spend. If you have supplier invoices that carry quantities (tonnes of steel, cubic metres of concrete, litres of chemical), the reconciliation is: purchased quantity in the ERP ties to purchased quantity in the emissions ledger.

We wrote about the quantity-versus-spend gap that most tools default to. The short version: if you cannot extract physical quantities from supplier documents, you are on spend-based Category 1, and spend-based data does not reconcile in the same way. It ties to accounts payable dollars, not to a physical activity flow.

What does not reconcile (and why that is fine)

Three categories of emissions data will not tie neatly at month-end. Trying to force them to reconcile creates false confidence and eats time you should be spending on the lines that do reconcile.

Spend-based Scope 3 estimates

Spend-based Scope 3 (using EEIO factors or industry averages against dollars spent) is an estimate by construction. It will move whenever the AP ledger moves, but the underlying emissions did not necessarily move. A supplier invoice that was posted in July for a June delivery does not mean the emissions occurred in July.

The right approach is to review spend-based Category 1 at quarter-end, not month-end, and to caveat it explicitly in the audit trail as an estimation methodology. AASB S2 paragraph 29(a)(vi) allows estimation for Scope 3 categories where measured data is not available, but the estimation approach has to be disclosed. That disclosure lives in the Basis of Preparation, not in the month-end reconciliation.

Physical intensity metrics

Intensity metrics (tCO2e per tonne of product, tCO2e per FTE, tCO2e per A$M revenue) will not reconcile month-on-month because both the numerator and the denominator are moving. Production varies. Headcount changes. Revenue lumps. Trying to explain why the intensity moved from 12.4 to 12.7 in a single month is analytical work, not reconciliation work.

Intensity metrics belong in the quarterly variance pack, alongside the board variance analysis that already lives in the finance team's workflow. Not in the month-end tie-out.

Refrigerant top-ups

Refrigerant is a Scope 1 line but the emission event is a leak, which is invisible until someone tops up the system. The top-up invoice arrives whenever it arrives. Trying to reconcile refrigerant emissions to a monthly cadence gives a false pattern.

The pragmatic control is: log every refrigerant top-up as it happens, apply the leak factor at the time of top-up, and reconcile the annual total against the refrigerant asset register once a year. Do not try to force it into monthly.

The monthly close checklist

Six steps, in order. This is the sequence a Financial Controller should own end-to-end for the emissions ledger, treating it as a subledger to the statutory accounts.

1. Period cut-off. Set the close date. Everything with an activity date on or before the cut-off belongs to the period. Everything after does not. If a utility bill arrives in July covering June consumption, it goes to June. This is the same accrual logic you already use for the GL. The Custom Dashboards view of open items by site is the fastest way to see what is missing.

2. Factor version pin. Confirm the emission factor version applied to the period. NGA 2025 factors are current. If DCCEEW publishes an update, the update applies from its effective date forward, not retrospectively. Factor version pinning is what protects you when the auditor asks "which factor did you use for June" in month 11. The emission factor versioning and audit trail piece covers this in detail.

3. Currency preservation for multi-country activity. If any activity data is denominated in a currency other than AUD (US diesel prices, EU electricity contracts, NZ freight), preserve the original currency alongside the AUD-converted figure. Auditors will want to see both, and the FX rate used for the conversion. Multi-currency supply chain patterns are covered in carbon accounting for multi-currency supply chains.

4. Materiality threshold review. Every close needs a materiality threshold documented and applied. The materiality threshold for emissions errors under AASB S2 and NGER piece runs through the mechanics. As a starting point, most Group 2 reporters are landing on 5 percent of total Scope 1 plus Scope 2, or 1 percent of the group's total gross emissions, whichever is lower. Anything above the threshold gets investigated before the period closes. Anything below gets logged and reviewed at quarter-end.

5. Exception review. Run Anomaly Detection over the period. Refrigerant top-ups above baseline, fuel line items with implausible litres-per-vehicle, utility bills with kWh readings that jump 40 percent month-on-month. Each exception either resolves (data entry error, meter reset, holiday shutdown) or promotes to an investigation item. This is the same discipline the AP team applies to variance reports.

6. Sign-off and period lock. The Financial Controller signs off the period. The system locks it. New activity data with a date inside the locked period cannot be posted directly; it must be posted as a prior-period adjustment with a documented reason. This is exactly how the GL works, and it is exactly how the emissions ledger should work.

The six steps should take a monthly cadence of one to three business days in a system with automated ingestion. In a spreadsheet, they take a week and are never fully complete.

Who owns what

The workable split we see modelled between finance and sustainability:

Financial Controller owns:

Period cut-off and lock
Reconciliation to source (utility spend, fuel cards, procurement PO)
Materiality threshold application
Sign-off before period close
Prior-period adjustment approval
Audit trail evidence pack

Sustainability Lead owns:

Emission factor selection and methodology
Boundary decisions (operational, financial, equity share)
Scope 3 category prioritisation
Anomaly investigation for physical causes (was there a plant outage, a fleet change, a refrigerant leak)
Narrative for variance reporting
Framework interpretation (AASB S2, NGER, ISSB updates)

Shared:

Materiality threshold setting (Financial Controller proposes, Sustainability Lead reviews for climate-relevance)
Exception review (finance runs the check, sustainability interprets the anomaly)
External auditor engagement (finance for control evidence, sustainability for methodology evidence)

The split matters because when the external auditor arrives under ASSA 5010, they are going to test two different things: whether the numbers tie to source (finance's problem) and whether the methodology is defensible (sustainability's problem). Both need an owner who can produce evidence on demand.

What the auditor is going to ask about the close

Three questions consistently show up in ASSA 5010 fieldwork. The Financial Controller should be able to answer all three without leaving the room.

"Show me the sign-off for period X." The date, the person, the version of the data at the point of sign-off, and the factor version applied. If this lives in a signed one-pager filed with the audit committee papers, or in a system's typed audit event log, it takes 30 seconds. If it lives in someone's Outlook, it takes a week and does not survive scrutiny.

"Show me how you handled the June invoice that arrived in August." This is the prior-period adjustment test. The auditor wants to see the adjustment, the reason, the approver, and the impact on the previously-signed period. Baseline snapshots protect the previously-signed period from being overwritten; the adjustment sits as a delta.

"Show me your Basis of Preparation." The document that says which factors, which boundaries, which methodologies, which materiality thresholds, which estimation approaches, which exclusions. The Basis of Preparation is the single most important document in the AASB S2 disclosure. It also happens to be what the audit committee chair reviews before signing.

Where it lands with the CFO

The CFO does not want to know about kilograms. The CFO wants to know that the number in the AASB S2 disclosure is the same discipline as the number in the statutory accounts, that the audit trail will survive assurance, and that the monthly variance to plan is understood.

The way the CFO's playbook for the first AASB S2 disclosure reads it: the emissions ledger becomes a normal subledger, closed monthly, reconciled to source, signed off by the Controller, and reported to the CFO alongside the treasury and management accounts pack. That is the target state.

The reason to run it that way is not compliance elegance. It is that assurance testing is line-by-line, and the only defence against a line-by-line challenge is a control that ran monthly, was signed off monthly, and can produce evidence monthly. Trying to reconstruct 12 months of controls in July after the year has closed is where Group 1 reporters lost the most ground.

Where Carbonly fits

The Carbonly platform runs a period-lock service on the emissions ledger. Once a period is closed and signed off by the Controller, activity data inside that period cannot be silently amended. Prior-period adjustments require an approver and log a typed audit event with the reason.

Baseline snapshots preserve the version of the data at the point of sign-off, so when the auditor asks "what did June look like when you closed it" in month 11, the system returns the same numbers that were signed off. The Custom Dashboards module gives the Financial Controller a live view of open items by site, missing bills, and reconciliation exceptions. Anomaly Detection runs the five rule types (baseline deviation, factor-version drift, missing periods, unit-of-measure outliers, per-gas anomalies) before sign-off. The Evidence Pack export bundles the source documents, the factor versions, the sign-off records, and the typed audit events into an ASSA 5010-ready package.

Bring a recent month-end close checklist, or a reconciliation between one of your utility spend lines and your emissions ledger, to hello@carbonly.ai. We will show you what the same check looks like inside a system built for the Financial Controller's discipline rather than for annual roll-up.