BILLINGCPDATA
BILLINGCPDATA shows energy quantity and $ value purchased per participant connection point. The table is populated for participants using Data Model 5.2. For participants using Data Model 5.3 or higher,
BILLING_ENERGY_TRANSACTIONSANDBILLING_ENERGY_GENSET_DETAILreplace BILLINGCPDATA.
Deprecation Warning
This table is in the HISTORICAL TABLES package, so is likely deprecated.
BILLINGCPDATA data is confidential to relevant participant.
Source
Populated by the posting of a billing run, being several times each week.
Volume
The number of records depends on the number of Transmission ConnectionPointIDs a participant may use to purchase energy. An indicative maximum is approximately 150 records per billrunno, or about 1,500 records inserted per week.
Column Schema
BILLRUNNO
Unique run no within a given contract year and week no
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
CONNECTIONPOINTID
Unique connection point identifier
SQL Type: VARCHAR2(10)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
CONTRACTYEAR
AEMO Contract Year number starting in week containing 1st January
SQL Type: NUMBER(4,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
MDA
relevant MDA for this connection point.
SQL Type: VARCHAR2(10)
Polars Type: str
This column is mandatory, and a primary key.
PARTICIPANTID
Unique participant identifier
For more information, see the dedicated documentation page.
SQL Type: VARCHAR2(10)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
WEEKNO
Week no within the contract year. Week no 1 is the week containing 1st January
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.
AFE
Adjusted Gross Energy for this Market Customer FRMP and TNI in the Billing run, excluding any UFEA component.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
AGE
Adjusted Gross Energy for this Market Customer FRMP and TNI in the trading interval. This will include the UFEA value once financial settlement of UFE commences with GS.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
AGGREGATEENERGY
Aggregate energy purchased/sold by customer, in MWh, plus UFEA. When GS commences, this includes the UFEA amount in the settlement runs.
SQL Type: NUMBER(16,6)
Polars Type: pl.Float64
This column is not mandatory.
DME
Sum of ME- for all NMIs at this Market Customer FRMP and TNI in the Billing run.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
LASTCHANGED
Last date and time record changed
For more information, see the dedicated documentation page.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2026/01/20 00:05:00
PURCHASEDENERGY
The energy consumed at the connection point by the participant in this billing run
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
PURCHASES
The Purchase column has the dollar value of the Energy Purchased rather than Aggregate Energy Dollar
SQL Type: NUMBER(16,6)
Polars Type: pl.Float64
This column is not mandatory.
SALES
The total cost of energy sold at the connection point by the participant in this billing run
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
SOLDENERGY
Energy sold at the connection point by the participant in this billing run
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
UFEA
Share of UFE allocated to this FRMP and TNI in the Billing run.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
New Data Timing
After posting of a billing run (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("LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
)
.cast(
{
"BILLRUNNO": int, # or pl.UInt16
"CONNECTIONPOINTID": pl.Categorical,
"CONTRACTYEAR": int, # or pl.UInt16
"MDA": str,
"PARTICIPANTID": pl.Categorical,
"WEEKNO": int, # or pl.UInt16
"AFE": pl.Float64,
"AGE": pl.Float64,
"AGGREGATEENERGY": pl.Float64,
"DME": pl.Float64,
"PURCHASEDENERGY": pl.Float64,
"PURCHASES": pl.Float64,
"SALES": pl.Float64,
"SOLDENERGY": pl.Float64,
"UFEA": pl.Float64,
}
)
# Deduplicate
# We want one row per ['BILLRUNNO', 'CONNECTIONPOINTID', 'CONTRACTYEAR', 'MDA', 'PARTICIPANTID', 'WEEKNO']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=[
"BILLRUNNO",
"CONNECTIONPOINTID",
"CONTRACTYEAR",
"MDA",
"PARTICIPANTID",
"WEEKNO",
],
keep="last",
)
)
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 | CPDATA | 7 |
This means that the CSV files start with metadata columns:
Indexes
There is more than one index.
Index 1:
Index 2:
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: HISTORICAL TABLES