BILLINGPRIORADJUSTMENTS
BILLINGPRIORADJUSTMENTS sets out prior period adjustments and associated interest inserted in subsequent Final Statements arising from Revision Statement postings.
BILLINGPRIORADJUSTMENTS data is confidential to the relevant participant.
Source
BILLINGPRIORADJUSTMENTS is populated on the posting of a Final billing run only.
Volume
Approximately two records inserted per week.
Note
Actual adjustment payable is
ADJAMOUNT- PERAMOUNT + INTEREST AMOUNT.
Column Schema
ADJBILLRUNNO
Bill run number of the posted revision statement inserted to the Final Statement
SQL Type: NUMBER(3,0)
Polars Type: pl.Int16
This column is mandatory, and a primary key.
ADJCONTRACTYEAR
ContractYear of the posted revision statement inserted to the Final Statement
SQL Type: NUMBER(4,0)
Polars Type: pl.Int16
This column is mandatory, and a primary key.
ADJWEEKNO
WeekNo of the posted revision statement inserted to the Final Statement
SQL Type: NUMBER(3,0)
Polars Type: pl.Int16
This column is mandatory, and a primary key.
BILLRUNNO
Billing run number.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
CONTRACTYEAR
Settlement year.
SQL Type: NUMBER(4,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
PARTICIPANTID
Participant ID
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
Settlement 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.
ADJAMOUNT
Adjusted amount.
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
INTERESTAMOUNT
Interest amount.
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
IRN
Interest rate applied to the revision adjustment
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
LASTCHANGED
Last 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
PREVAMOUNT
Statement total of the previous posted revision statement inserted to the Final Statement.
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
IRP
unused; always null
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is unused.
IRSR_ADJAMOUNT
unused; always null
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is unused.
IRSR_INTERESTAMOUNT
unused; always null
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is unused.
IRSR_PREVAMOUNT
unused; always null
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is unused.
New Data Timing
After posting of a final billing run
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(
{
"ADJBILLRUNNO": int, # or pl.Int16
"ADJCONTRACTYEAR": int, # or pl.Int16
"ADJWEEKNO": int, # or pl.Int16
"BILLRUNNO": int, # or pl.UInt16
"CONTRACTYEAR": int, # or pl.UInt16
"PARTICIPANTID": pl.Categorical,
"WEEKNO": int, # or pl.UInt16
"ADJAMOUNT": pl.Float64,
"INTERESTAMOUNT": pl.Float64,
"IRN": pl.Float64,
"PREVAMOUNT": pl.Float64,
"IRP": pl.Float64,
"IRSR_ADJAMOUNT": pl.Float64,
"IRSR_INTERESTAMOUNT": pl.Float64,
"IRSR_PREVAMOUNT": pl.Float64,
}
)
# Drop deprecated/unused columns
.drop("IRP", "IRSR_ADJAMOUNT", "IRSR_INTERESTAMOUNT", "IRSR_PREVAMOUNT")
# Deduplicate
# We want one row per ['ADJBILLRUNNO', 'ADJCONTRACTYEAR', 'ADJWEEKNO', 'BILLRUNNO', 'CONTRACTYEAR', 'PARTICIPANTID', 'WEEKNO']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=[
"ADJBILLRUNNO",
"ADJCONTRACTYEAR",
"ADJWEEKNO",
"BILLRUNNO",
"CONTRACTYEAR",
"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 | PRIORADJUSTMENTS | 5 |
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: BILLING_RUN