BILLING_MR_PAYMENT
BILLING_MR_PAYMENT shows aggregate payments on a dispatchable unit/MR Event basis for accepted MR capacity
Deprecation Warning
This table is in the HISTORICAL TABLES package, so is likely deprecated.
BILLING_MR_PAYMENT data is confidential, and is available only to the relevant participant.
Source
Ad hoc - MR events only.
Volume
3500 rows per year
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.
DUID
Unique identifier for DUID / MNSP LinkID
Warning
This column may contain funny characters such as / (slash) or # (hash). This may break hive-style partitioning.
For more information, see the dedicated documentation page.
SQL Type: VARCHAR2(10)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
Example: W/HOE#2
MR_DATE
Trading Date of Mandatory Restriction event; Mandatory Restriction imposition 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
REGIONID
Unique Region Identifier
For more information, see the dedicated documentation page.
The SQL type is VARCHAR2(10).
This is actually a factor/enum, with values:
-
QLD1 -
VIC1 -
TAS1 -
NSW1 -
SA1 -
SNOWY1
This column is mandatory, and a primary key.
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.
LASTCHANGED
Date/Time record inserted/modified
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
MR_AMOUNT
Payment amount by AEMO
SQL Type: NUMBER(16,6)
Polars Type: pl.Float64
This column is not mandatory.
PARTICIPANTID
Unique Participant identifier
For more information, see the dedicated documentation page.
SQL Type: VARCHAR2(10)
Polars Type: pl.Categorical
This column is not mandatory.
New Data Timing
Ad hoc, when there is a MR event
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("MR_DATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
)
.cast(
{
"BILLRUNNO": int, # or pl.UInt16
"CONTRACTYEAR": int, # or pl.UInt16
"DUID": pl.Categorical,
"REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"]),
"WEEKNO": int, # or pl.UInt16
"MR_AMOUNT": pl.Float64,
"PARTICIPANTID": pl.Categorical,
}
)
# Deduplicate
# We want one row per ['BILLRUNNO', 'CONTRACTYEAR', 'DUID', 'MR_DATE', 'REGIONID', 'WEEKNO']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=["BILLRUNNO", "CONTRACTYEAR", "DUID", "MR_DATE", "REGIONID", "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:
PDR Loader configuration does not mention this table, so it is unclear how to choose which row to keep when there are multiple rows for a given set of primary keys.
You should probably take the row with the maximum LASTCHANGED.
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: HISTORICAL TABLES