SETLSHEDPAYMENT
SETLSHEDPAYMENT shows specific payment details for load shed services by period. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct.
SETLSHEDPAYMENT data is confidential to the relevant participant.
Source
SETLSHEDPAYMENT updates with each settlement run.
Column Schema
CONTRACTID
AS Contract Identifier
SQL Type: VARCHAR2(10)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
PARTICIPANTID
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.
PERIODID
Settlements Trading Interval.
SQL Type: NUMBER(3,0)
Polars Type: pl.Int16
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
VERSIONNO
Settlement Run No.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is mandatory, and a primary key.
ALS
Amount of load shed
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
AVAILABILITYPAYMENT
Payment amount for the Load Shed Availability service
SQL Type: NUMBER(16,6)
Polars Type: pl.Float64
This column is not mandatory.
CCPAYMENT
Compensation Payment
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
CONSTRAINEDMW
Cleared MW of unit at time of load shed usage
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
CONTRACTVERSIONNO
AS Contract Version No.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is not mandatory.
DUID
Dispatchable Unit Identifier
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 not mandatory.
Example: W/HOE#2
FINALDEMAND
Final demand of unit at time of load shed usage
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
INITIALDEMAND
Initial demand of unit at time of load shed usage
SQL Type: NUMBER(15,5)
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
LSCR
Load Shed Control Range
SQL Type: NUMBER(4,0)
Polars Type: pl.Int16
This column is not mandatory.
LSEPAYMENT
Load Shed Enabling Payment
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
LSEPRICE
Load Shed Enabling Price
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
MCPPRICE
Minimum Compensation Price
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
OFFERDATE
Re-offer offer date
Warning
Despite what the name suggests, this is a datetime, not a date.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2026/01/20 00:05:00
OFFERVERSIONNO
Re-Offer Version No.
SQL Type: NUMBER(3,0)
Polars Type: pl.UInt16
This column is not mandatory.
REGIONID
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 not mandatory.
RRP
Regional Reference Price
For more information, see the dedicated documentation page.
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
TLF
Transmission Loss Factor
SQL Type: NUMBER(7,5)
Polars Type: pl.Float64
This column is not mandatory.
UNCONSTRAINEDMW
Unconstrained MW of unit at time of load shed usage
SQL Type: NUMBER(15,5)
Polars Type: pl.Float64
This column is not mandatory.
New Data Timing
After each settlement 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("SETTLEMENTDATE", "LASTCHANGED", "OFFERDATE").str.strptime(
pl.Datetime, dt_s_fmt
),
)
.cast(
{
"CONTRACTID": pl.Categorical,
"PARTICIPANTID": pl.Categorical,
"PERIODID": int, # or pl.Int16
"VERSIONNO": int, # or pl.UInt16
"ALS": pl.Float64,
"AVAILABILITYPAYMENT": pl.Float64,
"CCPAYMENT": pl.Float64,
"CONSTRAINEDMW": pl.Float64,
"CONTRACTVERSIONNO": int, # or pl.UInt16
"DUID": pl.Categorical,
"FINALDEMAND": pl.Float64,
"INITIALDEMAND": pl.Float64,
"LSCR": int, # or pl.Int16
"LSEPAYMENT": pl.Float64,
"LSEPRICE": pl.Float64,
"MCPPRICE": pl.Float64,
"OFFERVERSIONNO": int, # or pl.UInt16
"REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"]),
"RRP": pl.Float64,
"TLF": pl.Float64,
"UNCONSTRAINEDMW": pl.Float64,
}
)
# Deduplicate
# We want one row per ['CONTRACTID', 'PARTICIPANTID', 'PERIODID', 'SETTLEMENTDATE', 'VERSIONNO']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=[
"CONTRACTID",
"PARTICIPANTID",
"PERIODID",
"SETTLEMENTDATE",
"VERSIONNO",
],
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 |
|---|---|---|
| SETTLEMENTS | LSHEDPAYMENT | 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: SETTLEMENT_DATA