BILLING_DAILY_ENERGY_SUMMARY
Billing result table containing daily summary data for customer and generator energy amounts
BILLING_DAILY_ENERGY_SUMMARY data is confidential to the relevant participant.
Source
Populated by the posting of a billing run.
Volume
Approximately 20 records per billrunno.
Column Schema
BILLRUNNO
Billing Run number
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
CONTRACTYEAR
Billing Contract Year
SQL Type: NUMBER(4,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
PARTICIPANTID
participant identifier
For more information, see the dedicated documentation page.
SQL Type: VARCHAR2(20)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
REGIONID
Unique Region Identifier
For more information, see the dedicated documentation page.
The SQL type is VARCHAR2(20).
This is actually a factor/enum, with values:
-
QLD1 -
VIC1 -
TAS1 -
NSW1 -
SA1 -
SNOWY1
This column is mandatory, and a primary key.
SETTLEMENTDATE
settlement date
Warning
Despite what the name suggests, this is a datetime, not a date.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/01/20 00:05:00
WEEKNO
Billing Week number
Warning
There may be 53 weeks in a year, depending on how weeks align to the year start/end.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
ACE_AMOUNT
The Sum of ACE Amount for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
ACE_MWH
The Sum of ACE MWh value for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
ASOE_AMOUNT
The Sum of ASOE Amount for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
ASOE_MWH
The Sum of ASOE MWh value for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
CE_MWH
The Sum of CE MWh value for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
CUSTOMER_ENERGY_PURCHASED
Customer energy amount purchased on this settlement day by the participant in the region. NULL for Billing Week post the IESS rule effective date.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
GENERATOR_ENERGY_PURCHASED
Generator energy amount purchased on this settlement day by the participant in the region. NULL for Billing Week post the IESS rule effective date.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
GENERATOR_ENERGY_SOLD
Generator energy amount sold on this settlement day by the participant in the region. NULL for Billing Week post the IESS rule effective date.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
TOTAL_AMOUNT
The Sum of Total Amount for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
TOTAL_MWH
The Sum of Total MWh value for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
UFEA_MWH
The Sum of UFEA MWh value for the Participant and region for the Settlement Date. NULL for Billing Week prior to the IESS rule effective date
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
New Data Timing
Populated by the posting of a billing run, being several times each week
Code Examples
Polars
Casting is enums, categoricals etc is not essential, but may speed up parsing.
Swapping int for pl.UInt16, pl.Int32 would also speed up parsing. However some of the datatypes are inferred, so they may be wrong.
This code deduplicates for you. Deduplication is normally only required across multiple months.
This code assumes that all columns are present, which may not be true for older files.
import polars as pl
import polars.selectors as cs
# e.g. "2029/03/15 00:05:00"
dt_s_fmt = "%Y/%m/%d %H:%M:%S"
csv_paths = ["SOMEFILE.CSV", "OTHERFILE.CSV"]
lf = (
pl.concat(
[
pl.scan_csv(
csv_path, # must be unzipped beforehand
skip_rows=1, # skip the header
infer_schema=False, # much faster
)
.filter(cs.by_index(0) == "D") # drop the footer
.select(~cs.by_index(range(4))) # drop metadata columns
for csv_path in csv_paths
],
how="diagonal_relaxed",
)
.with_columns(
pl.col("SETTLEMENTDATE").str.strptime(pl.Datetime, dt_s_fmt),
)
.cast(
{
"BILLRUNNO": int, # or pl.UInt16
"CONTRACTYEAR": int, # or pl.UInt16
"PARTICIPANTID": pl.Categorical,
"REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"]),
"WEEKNO": int, # or pl.UInt16
"ACE_AMOUNT": pl.Float64,
"ACE_MWH": pl.Float64,
"ASOE_AMOUNT": pl.Float64,
"ASOE_MWH": pl.Float64,
"CE_MWH": pl.Float64,
"CUSTOMER_ENERGY_PURCHASED": pl.Float64,
"GENERATOR_ENERGY_PURCHASED": pl.Float64,
"GENERATOR_ENERGY_SOLD": pl.Float64,
"TOTAL_AMOUNT": pl.Float64,
"TOTAL_MWH": pl.Float64,
"UFEA_MWH": pl.Float64,
}
)
# Deduplicate
# We want one row per ['BILLRUNNO', 'CONTRACTYEAR', 'PARTICIPANTID', 'REGIONID', 'SETTLEMENTDATE', 'WEEKNO']
.unique(
subset=[
"BILLRUNNO",
"CONTRACTYEAR",
"PARTICIPANTID",
"REGIONID",
"SETTLEMENTDATE",
"WEEKNO",
],
keep="any",
)
)
Nemosis
This table is not yet available in Nemosis.
Availability
Visibility: Private
This table is not available in the public monthly MMSDM archive. Is is only available to registered market participants over FTP inside a VPN.
Deduplication and PDR Loader Configuration
The primary keys are:
The transaction type is "insert", which means that you will usually not see duplicate data. If you do, you can deduplicate based on the primary keys, without sorting first. Rows from different files with the same primary keys should have the same values.
| Report Name | Report Subtype | Version |
|---|---|---|
| BILLING | DAILY_ENERGY_SUMMARY | 2 |
This means that the CSV files start with metadata columns:
Links
This page as JSON (schema documented here, but may change)
Download a JSON Schema specification for this table.
Official AEMO schema documentation
Other Information
Package: BILLING_RUN