Skip to content

SETREALLOCATIONS

SETREALLOCATIONS shows the trading interval value of reallocations processed, for those participants whose reallocation submissions have been accepted by AEMO.

SETREALLOCATIONS data is confidential to participants party to the reallocation.

Source

SETREALLOCATIONS updates by the posting of a billing run.

Volume

Generally, there are approximately 550 records inserted per week.

Column Schema

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.

PERIODID

Settlements Trading Interval.

SQL Type: NUMBER(3,0) Polars Type: pl.Int16

This column is mandatory, and a primary key.

REALLOCATIONID

Reallocation contract identifier

SQL Type: VARCHAR2(20) Polars Type: str

This column is mandatory, and a primary key.

RUNNO

Settlement run no

SQL Type: NUMBER(3,0) Polars Type: pl.UInt16

This column is mandatory, and a primary key.

SETTLEMENTDATE

Calendar 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

ENERGY

Energy in MWh if reallocation agreement type is MWh

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

REALLOCATIONVALUE

Reallocation value in $

SQL Type: NUMBER(15,5) Polars Type: pl.Float64

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.

New Data Timing

Updates by the posting of a 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("SETTLEMENTDATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast(
        {
            "PARTICIPANTID": pl.Categorical,
            "PERIODID": int,  # or pl.Int16
            "REALLOCATIONID": str,
            "RUNNO": int,  # or pl.UInt16
            "ENERGY": pl.Float64,
            "REALLOCATIONVALUE": pl.Float64,
            "RRP": pl.Float64,
        }
    )
    # Deduplicate
    # We want one row per ['PARTICIPANTID', 'PERIODID', 'REALLOCATIONID', 'RUNNO', 'SETTLEMENTDATE']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(
        subset=[
            "PARTICIPANTID",
            "PERIODID",
            "REALLOCATIONID",
            "RUNNO",
            "SETTLEMENTDATE",
        ],
        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.

PDR Loader configuration is:

Report Name Report Subtype Version
SETTLEMENTS REALLOCATIONS 5

This means that the CSV files start with metadata columns:

I,SETTLEMENTS,REALLOCATIONS,5,...
D,SETTLEMENTS,REALLOCATIONS,5,...

Indexes

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