Environmental data dashboard consolidating AASB S2, EPBC and NPI reporting across multiple site

Three Deadlines, One Database: Are You Ready for Australia’s Next Reporting Wave?

Three reporting regimes now rely on the same environmental data. First, AASB S2 climate reporting has started for Group 2 entities. Second, a new EPBC data standard applies to project approvals by 1 December 2026. Finally, calendar-year NPI reports are due on 31 March 2027. Each one also has its own regulator and format. However, they all depend on the same data, so they all depend on your database.

In this article, we explain what each obligation means. We also show where they overlap and how to set up your data once to serve all three.

The three obligations at a glance

ObligationKey dateWho it affectsWhat your data needs
AASB S2 (Group 2)Years starting from 1 July 2026. First reports due late 2027.Mid-sized entities, NGER reporters and large asset ownersScope 1 and 2 emissions that pass an audit. Scope 3 follows in year two.
EPBC Data and Information StandardApplies to approvals by 1 December 2026Project proponents under the EPBC ActData you can trace, compare and reuse
NPI (calendar-year reporters)31 March 2027Facilities above NPI thresholdsEstimates for every substance over the threshold

1. AASB S2: Group 2 climate reporting has started

As of this year, climate reporting is mandatory for Group 2 entities. Specifically, it applies to financial years that start on or after 1 July 2026.

So, who is in Group 2? First, your entity must prepare an annual financial report under the Corporations Act. Then it must meet at least two of these three tests:

  • revenue of $200 million or more
  • gross assets of $500 million or more
  • 250 or more employees.

There are also two other ways in. NGER reporters that aren’t in Group 1 are in Group 2, whatever their size. Asset owners with $5 billion or more are also in. For many operators, in fact, the NGER route is the one that applies.

What you need to report

In year one, you report Scope 1 and Scope 2 emissions. Then, from year two, you add Scope 3. After that, you lodge the report with ASIC, together with your annual report.

Most importantly, your auditor must check it. At first, limited assurance applies. Full assurance then follows by 2030.

Why it matters now: for a 30 June year-end, your first reporting year began on 1 July 2026. In other words, your auditor will test data you are creating today. If you don’t capture it well now, it is hard to fix later.

2. The EPBC data standard: data quality becomes a legal test

The Minister made the National Environmental Standard (Data and Information) 2026 on 19 August 2026. It already applies to some EPBC decisions, such as bilateral agreements. However, the big change comes when the new approval tests start, on or before 1 December 2026. From then on, the Minister can only approve a project if the decision is consistent with the standard.

The five principles

As a result, data used in EPBC decisions must be:

  • Representative: fit for the job it is used for
  • Transparent: reliable, with a clear history of where it came from
  • Comparable: consistent in methods, formats and units
  • Reusable: easy for others to use again
  • Ethical: collected and managed in an ethical way.

This is therefore a database issue, not just a reporting one. For example, say your baseline data sits in loose spreadsheets. If nobody recorded how it was collected or changed, it will be hard to prove it meets these principles.

3. NPI: calendar-year reports are due 31 March 2027

First, note that most facilities report to the National Pollutant Inventory on a financial year. They lodge by 30 September. However, some agencies let a facility report on a calendar year instead. In that case, the 2026 report is due by 31 March 2027.

Next, you send the report to your state or territory agency. The agency then checks it before it is published.

Also, you must report every substance that goes over a threshold. Be careful, too, because late or wrong reports can lead to penalties.

Where the three overlap

Each regime has its own regulator and form. Even so, they share the same source data:

  • Fuel and energy use feeds NGER, AASB S2 emissions and many NPI estimates.
  • Monitoring results support NPI, licence reporting and EPBC baseline data.
  • Site boundaries must match in every report. Otherwise, auditors and regulators will notice.

If you run each regime in its own spreadsheet, you handle the same data three times. As a result, you have three chances to get it wrong.

Warning signs your data isn’t ready

  • Different people prepare your NGER, NPI and climate figures in different files.
  • You can’t show your auditor where a number came from.
  • You can’t tell who changed a figure, or when.
  • Your data has no recorded method or units.
  • Staff re-key lab results and telemetry by hand.
  • Nobody has flagged the gaps in your historical data.
  • Only one or two people know how the reports come together, so you are exposed if they leave.

What “one database” looks like

  1. Capture once. Telemetry, lab results and field data flow into one system for every site.
  2. Check on arrival. The system checks ranges, units and required fields as data lands. It also flags missing or unusual values.
  3. Track every change. You can see who changed what, when and why. This is exactly what the EPBC standard and your AASB S2 auditor will look for.
  4. Report many ways. One clean dataset feeds dashboards, regulator reports and exports. As a result, each regime gets its own format without rework.
  5. Grow without rebuilding. You can add new sites, limits and templates as your obligations grow. That includes Scope 3 data from year two.

How DB Gurus can help

Our Environmental Tracking System (ETS) has supported Australian mining since 2008. Today, it manages millions of environmental data points every day.

First, ETS brings together data from your monitoring equipment, labs and spreadsheets. Then it checks the data, sends alerts on exceedances and keeps a full audit trail. It also produces reports that are ready for regulators.

In addition, your data stays in Australia (AWS Sydney). We are also ISO 9001 and ISO 27001 certified.

Need more than monitoring? For example, you may want to link emissions data to your finance systems. Our team can build a custom solution around the way you already work.

This article is general information only. It is not legal, accounting or regulatory advice. Sources: National Environmental Standard (Data and Information) 2026; DCCEEW – National Environmental Standards; DCCEEW – NPI reporting; ASIC Regulatory Guide 280.

View more blogs

Usability & Access

  • Web access anywhere (mobile-friendly where needed)
  • Streamlined workflows to reduce admin effort
  • Search, filters, and drill-down to records
  • Australian-based support

Visualisation & Reporting

  • Dashboards, graphs, trends, and maps
  • Standard and customised reporting templates
  • Export to common formats (CSV/XLSX/PDF as required)
  • Consistent reporting across sites and programs

Data Integrity & Security

  • Role-based permissions and optional 2FA
  • Encrypted connections (TLS/SSL)
  • Change tracking (who/what/when)
  • Hosted in Australia (AWS Sydney) with backups/DR options

Monitoring & Alerts

  • Warning and exceedance limits per site/parameter
  • SMS and email alerts when thresholds are breached
  • Flag anomalous or missing data for follow-up
  • Audit trail of changes for compliance transparency

Data Collection & Management

  • Automated uploads from telemetry and scheduled file imports
  • Manual uploads and easy field data entry
  • Configurable parameters, units, validation rules, and required fields
  • Manage sites, locations, and monitoring points in one place