BILLINGDAYTRK
BILLINGDAYTRK is key for matching settlement versions with billing runs. BILLINGDAYTRK displays the billrunnos per billing week, and the settlement version numbers per settlement day comprising the billrunno.
BILLINGDAYTRK is public data, and is available to all participants.
Source
BILLINGDAYTRK is populated by the posting of a billing run, being several times each week.
Volume
Each billing run inserts approximately 7 records, being about 77 records 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.
Examples:
8, 996
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.
Example: 2026
SETTLEMENTDATE
Calendar Settlement Date contained in the billing run.
SQL Type: DATE
Polars Type: pl.Date()
This column is mandatory, and a primary key.
Example: 2026/02/01 00:00:00
Note that AEMO represents dates as datetimes with a midnight time component.
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.
Examples:
6, 40
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/08/24 09:31:10
RUNNO
Settlement run number used for each settlement date in that billing run.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is not mandatory.
Examples:
1, 11
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"
# Dates are represented as datetimes at midnight
d_fmt = "%Y/%m/%d 00:00:00"
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),
pl.col("SETTLEMENTDATE").str.strptime(pl.Date, d_fmt),
)
.cast(
{
"BILLRUNNO": int, # or pl.UInt16
"CONTRACTYEAR": int, # or pl.UInt16
"SETTLEMENTDATE": pl.Date(),
"WEEKNO": int, # or pl.UInt16
"RUNNO": int, # or pl.UInt16
}
)
# Deduplicate
# We want one row per ['BILLRUNNO', 'CONTRACTYEAR', 'SETTLEMENTDATE', 'WEEKNO']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=["BILLRUNNO", "CONTRACTYEAR", "SETTLEMENTDATE", "WEEKNO"], keep="last"
)
)
Nemosis
This table is not yet available in Nemosis.
Example File
From PUBLIC_ARCHIVE_BILLINGDAYTRK_FILE01_202609010000.zip
| CONTRACTYEAR | WEEKNO | BILLRUNNO | SETTLEMENTDATE | RUNNO | LASTCHANGED |
| 2026 | 36 | 991 | 2026/08/31 00:00:00 | 1 | 2026/09/01 01:23:00 |
| 2026 | 16 | 14 | 2026/04/12 00:00:00 | 10 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/13 00:00:00 | 10 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/14 00:00:00 | 10 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/15 00:00:00 | 10 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/16 00:00:00 | 9 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/17 00:00:00 | 8 | 2026/08/27 07:53:39 |
| 2026 | 16 | 14 | 2026/04/18 00:00:00 | 7 | 2026/08/27 07:53:39 |
| 2026 | 36 | 992 | 2026/09/01 00:00:00 | 1 | 2026/09/02 01:25:50 |
| 2026 | 35 | 9 | 2026/08/23 00:00:00 | 7 | 2026/09/02 09:06:59 |
| 2026 | 35 | 9 | 2026/08/24 00:00:00 | 7 | 2026/09/02 09:06:59 |
| ... |
| C | SETP.WORLD | DVD_BILLINGDAYTRK | AEMO | PUBLIC | 2026/10/09 | 15:24:53 | 001791523493881 | MONTHLY_ARCHIVE | 001791523493881 |
| I | BILLING | DAYTRK | 5 | CONTRACTYEAR | WEEKNO | BILLRUNNO | SETTLEMENTDATE | RUNNO | LASTCHANGED |
| D | BILLING | DAYTRK | 5 | 2026 | 36 | 991 | 2026/08/31 00:00:00 | 1 | 2026/09/01 01:23:00 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/12 00:00:00 | 10 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/13 00:00:00 | 10 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/14 00:00:00 | 10 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/15 00:00:00 | 10 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/16 00:00:00 | 9 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/17 00:00:00 | 8 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 16 | 14 | 2026/04/18 00:00:00 | 7 | 2026/08/27 07:53:39 |
| D | BILLING | DAYTRK | 5 | 2026 | 36 | 992 | 2026/09/01 00:00:00 | 1 | 2026/09/02 01:25:50 |
| D | BILLING | DAYTRK | 5 | 2026 | 35 | 9 | 2026/08/23 00:00:00 | 7 | 2026/09/02 09:06:59 |
| D | BILLING | DAYTRK | 5 | 2026 | 35 | 9 | 2026/08/24 00:00:00 | 7 | 2026/09/02 09:06:59 |
| ... | |||||||||
| C | END OF REPORT | 194 |
CONTRACTYEAR,WEEKNO,BILLRUNNO,SETTLEMENTDATE,RUNNO,LASTCHANGED
2026,36,991,"2026/08/31 00:00:00",1,"2026/09/01 01:23:00"
2026,16,14,"2026/04/12 00:00:00",10,"2026/08/27 07:53:39"
2026,16,14,"2026/04/13 00:00:00",10,"2026/08/27 07:53:39"
2026,16,14,"2026/04/14 00:00:00",10,"2026/08/27 07:53:39"
2026,16,14,"2026/04/15 00:00:00",10,"2026/08/27 07:53:39"
2026,16,14,"2026/04/16 00:00:00",9,"2026/08/27 07:53:39"
2026,16,14,"2026/04/17 00:00:00",8,"2026/08/27 07:53:39"
2026,16,14,"2026/04/18 00:00:00",7,"2026/08/27 07:53:39"
2026,36,992,"2026/09/01 00:00:00",1,"2026/09/02 01:25:50"
2026,35,9,"2026/08/23 00:00:00",7,"2026/09/02 09:06:59"
2026,35,9,"2026/08/24 00:00:00",7,"2026/09/02 09:06:59"
...
C,SETP.WORLD,DVD_BILLINGDAYTRK,AEMO,PUBLIC,2026/10/09,15:24:53,001791523493881,MONTHLY_ARCHIVE,001791523493881
I,BILLING,DAYTRK,5,CONTRACTYEAR,WEEKNO,BILLRUNNO,SETTLEMENTDATE,RUNNO,LASTCHANGED
D,BILLING,DAYTRK,5,2026,36,991,"2026/08/31 00:00:00",1,"2026/09/01 01:23:00"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/12 00:00:00",10,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/13 00:00:00",10,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/14 00:00:00",10,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/15 00:00:00",10,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/16 00:00:00",9,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/17 00:00:00",8,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,16,14,"2026/04/18 00:00:00",7,"2026/08/27 07:53:39"
D,BILLING,DAYTRK,5,2026,36,992,"2026/09/01 00:00:00",1,"2026/09/02 01:25:50"
D,BILLING,DAYTRK,5,2026,35,9,"2026/08/23 00:00:00",7,"2026/09/02 09:06:59"
D,BILLING,DAYTRK,5,2026,35,9,"2026/08/24 00:00:00",7,"2026/09/02 09:06:59"
...
C,"END OF REPORT",194
Availability
Visibility: Public
This table is in the public monthly MMSDM archive.
I have collated the list of all those files into one place, in this CSV metadata file. (Columns year, month, url, compressed_size in bytes).
The earliest available data is month 1 of 2015. The most recent available data is month 9 of 2026.
Every month in between has a file. (No gaps.)
Data Size
Each year of data is approximately 21 KB when zipped, 209 KB as unzipped CSV.
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 | DAYTRK | 5 |
This means that the CSV files start with metadata columns:
Indexes
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