Validated bill, interval, and tariff data covering 9,000+ commercial sites across Australia, New Zealand, UK, and US. Available via API for one source of truth for your energy.
.webp)
Every retailer formats bills differently. Network tariffs change quarterly across dozens of distribution zones in any single country. Standardised data files like NEM12 in Australia, HHD in the UK, and interval data in the US and New Zealand ship without business context. Embedded networks bill through intermediaries with their own conventions. Official registries (MSATS in AU, ECOES in the UK, ICP in NZ) hold the source of truth, but only for those with access.
The Termina Data Model unifies all of it. One canonical schema for every site, every meter, every interval, every tariff component, every bill line. Reconciled against invoice math and your contract terms, available via a single API.
Termina's data quality isn't theoretical. 9,000+ commercial sites use it to negotiate energy procurement, with real money on the line. When the data is wrong, money goes back. That's the bar.
Native support for the data sources, registries, file formats, and tariff structures of four major energy markets, with a portable data model that extends to anywhere energy is bought, sold, or metered.
Native
Native
Native
Native
Termina's home market. 9,000+ commercial sites validated every month across every retailer, every network, and every state. Native support for the protocols and registries Australian energy data actually moves through.
Emissions calculated from validated bill data, not estimates. Audit-ready from day one. Ready for AASB S2 (Australia), SECR (UK), XRB CS1 (NZ), and SEC climate rules (US).
Scope 2 emissions derived from actual bill consumption that's been reconciled against invoice math and contract terms. No proxy data, no industry-average estimates.
Every kWh tracked back to the bill it came from. Validation flags on every field. Auditable line items, structured for AASB S2 Group 1, 2, and 3 timelines.
AASB S2 location-based emissions for Australian reporting. Equivalent disclosure-ready structures for SECR, XRB, and SEC climate rules. One data layer, every framework.
One source of truth, persistent across retailer changes. Switch retailers tomorrow, the data model doesn't blink. Move from grid to embedded network, the schema stays consistent. Acquire a portfolio overnight in another country, sites onboard without breaking validation.
Same API. Different products. The Termina Data Model is the foundation underneath every commercial energy workflow.
Energy data flowing into Snowflake, BigQuery, Power BI, or Tableau alongside POS, labour, and weather data, without the OCR pipeline that breaks every six months.
Audit-ready Scope 2 emissions and disclosure data for AASB S2 (AU), SECR (UK), SEC climate rules (US), and XRB reporting (NZ), automatically reconciled across every site without Excel assembly.
Automated reconciliation against contracts, network tariffs, and consumption, catching billing errors before they hit the P&L.
Solar, battery, EV charging economics across the portfolio so you can see spend and savings from all of your tariffs in real dollars, so you can optimise for the best pricing or charging pattern.
Cost, consumption, and emissions roll-ups across hundreds of sites, across retailers, networks, and embedded estates, in one query.
Build energy-aware lending, ESG-linked products, or energy dashboards that ingest or display billing data you don't have to build, validate, or maintain.
Developers integrate via REST API in minutes. Finance, sustainability, and operations teams use the Termina dashboard. Both pull from the same validated source of truth.
{
"bills": [{
"id": 823901,
"nmi": "6203780031",
"validated": true,
"period": "2026-03",
"consumption_kwh": 12480,
"total_aud": 3247.18,
"validation": {
"line_items": true,
"contract_match": true
},
"issued_at": "2026-03-31",
"retailer": "Origin Energy"
}, {
"id": 823902,
"nmi": "6203780031",
"validated": true,
"period": "2026-02",
"consumption_kwh": 11832,
...
}]
}
Bills reconciled against invoice math (line items vs subtotal) and your contract terms (correct rates, periods, demand charges).
Data history doesn't disappear when you switch retailers. The model persists; only the active retailer changes.
Whether the site is grid-connected, in an embedded network, or on a market contract, same fields, same shapes.
Not a developer? Use the dashboard directly. Same validated data, no code required.
Whether you're consolidating a portfolio, building a customer-facing product, or scaling a sustainability function, the same data model handles it.
Bills, intervals, tariffs, contracts, and site attributes across hundreds of sites in a single queryable system, including embedded networks and multi-retailer estates.
Comprehensive billing, consumption, and tariff data through automated connections. No manual data entry, no NMI typos, no missed periods.
Standardised schemas and automated validation keep data accurate as you add sites, change retailers, or acquire portfolios, without growing the ops headcount.
The Termina Data Platform is the system of record for commercial energy data. It aggregates and validates bill, interval, and tariff data from every major retailer, network, and embedded network operator across Australia, New Zealand, the UK, and the US, then makes it available via a single API and dashboard. 9,000+ commercial sites use it as the foundation for procurement, sustainability reporting, BI, and asset optimisation. The data model is portable to any energy market.
Termina provides native support for four markets: Australia (NEM12, MSATS, all retailers and DNSPs, AASB S2), New Zealand (ICP registry, major retailers, network charges), the United Kingdom (MPAN/MPRN, ECOES, half-hourly data, DUoS/TNUoS, SECR), and the United States (meter IDs, Green Button, utility and ISO-RTO feeds, state tariffs, SEC climate disclosure). The data model is portable and can be extended to any energy market. Contact us to discuss coverage in markets we haven't listed.
A NMI (National Metering Identifier) is the 10 or 11-digit unique identifier assigned to every electricity connection point in Australia. It appears on every electricity bill and is the primary key used by retailers, networks, and AEMO/MSATS to identify a site's electricity supply. Every NMI has a checksum digit that validates the identifier is genuine. Equivalent identifiers in other markets include the ICP in New Zealand, MPAN and MPRN in the UK, and utility account or meter numbers in the US. Look up any NMI here.
A NEM12 file is the standard format the Australian Energy Market Operator (AEMO) uses to share interval meter data. It contains 5, 15, or 30-minute consumption readings for an electricity connection over a given period, plus quality flags indicating whether readings are actual, substituted, or estimated. NEM12 files are how the market exchanges meter data between retailers, distributors, and metering providers.
Yes. Termina delivers location-based Scope 2 emissions calculated from validated bill consumption, with full audit-ready provenance. Each kWh is traced back to the bill it came from, reconciled against invoice math and contract terms. The data structure supports AASB S2 (Australia, mandatory from 1 Jan 2025 for Group 1, with Groups 2 and 3 to follow), SECR (UK), XRB CS1 (New Zealand), and SEC climate rules (United States). Bills are flagged as validated or unvalidated, so audit and assurance teams can verify the chain of evidence behind every reported figure. Read our guide to mandatory climate reporting in Australia.
Bills are validated against invoice math (do the line items add up to the subtotal? does tax compute correctly?) and against your contract terms (was the agreed rate applied? are demand charges right? is the billing period correct?). Meter identifiers (NMI, ICP, MPAN, meter ID) are checksum-validated where applicable. Anomalies are flagged before data enters the platform, so downstream systems work from a clean dataset and billing errors get caught before they hit the P&L.
OCR APIs read text off a bill. They produce raw fields that you have to parse, validate, structure, and store yourself, and they break when retailers redesign bill formats. The Termina Data Platform is a structured ingestion layer that pulls data directly from retailers and AEMO. There is no OCR in the validation path, so format changes don't break ingestion, and the schema is consistent across every retailer, network, and embedded operator. OCR is one tactical capability; the Data Platform is your system of record. Need bill extraction specifically? See the Termina API for utility bill OCR.
Yes. The Termina Energy Data API returns validated, normalised JSON that can be loaded directly into any data warehouse or BI tool. Common integration patterns include scheduled syncs into BigQuery, Snowflake, or Redshift; direct API calls from Power BI and Tableau; and CSV/XLSX exports from the Termina dashboard for ad-hoc analysis.
Embedded networks bill through an intermediary, with sub-meter breakdowns and a parent-meter structure that standard retail formats don't follow. The Termina Data Platform has specific handling for embedded network operators in each supported market, normalising their data into the same schema as grid-supplied sites so portfolios with mixed grid and embedded estates can be reported on consistently.
Nothing. Termina is the system of record, not the retailer's billing system. When a site changes retailer, the active retailer field updates but the full historical dataset of bills, intervals, tariffs, and emissions stays in place. This is the core difference between a retailer customer portal and a system of record.
Bill redesigns don't break Termina. The platform ingests bills directly via API and stores them in a normalised schema separate from any single retailer's PDF layout. When a retailer redesigns their consumer-facing bill, your historical data and ongoing ingestion continue uninterrupted. This is why Termina is more robust than pure OCR-based approaches for multi-year energy data programs.
Yes. The Data Platform was designed for multi-site, multi-retailer businesses. A typical Termina customer has sites across 3 to 8 retailers, multiple networks, and a mix of grid-supplied and embedded network sites. All of it is normalised into one schema and queryable through a single API or dashboard.
Termina calculates location-based Scope 2 emissions for every site using validated consumption data and current grid emissions factors per region. The dataset is structured to meet AASB S2 (Australia), SECR (UK), SEC climate disclosure rules (US), and XRB reporting (NZ), including site-level breakdowns, methodology documentation, and audit trails. Carbon accounting platforms can integrate directly via API to source emissions data from Termina.
Yes. Termina provides a structured data source for carbon accounting platforms (Sumday, Pathzero, Watershed, and similar) to power their Scope 2 calculations. Rather than having your customers manually upload bills, the platform syncs validated consumption and emissions data directly via API. Contact us to discuss integration options.
Start with the foundation 9,000+ commercial sites are already built on across four markets. Talk to our team or explore the API.
