RESIDUE_PRICE_BID

RESIDUE_PRICE_BID supports the Settlement Residue Auction, holding the unit and bid price details for each participant.

Source

The participant's own bid file

RESIDUE_PRICE_BID data is confidential to the relevant participant.

The public version of the data is available to all auction participants post the associated auction date in RESIDUE_PRICE_FUNDS_BID.

Volume

RESIDUE_PRICE_BID shows a maximum of 10,000 records per year.

Column Schema

AUCTIONID

Unique id for each auction date (new in March 2003 to support SRA Inter-Temporal Linking)

SQL Type: VARCHAR2(30) Polars Type: pl.Categorical

This column is mandatory, and a primary key.

LOADDATE

Date and Time the batcher loaded the bid

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

OPTIONID

Unique option (bid) identifier (1..800)

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

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.

BIDPRICE

Price offered for each unit

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

This column is not mandatory.

CONTRACTID

Not to be used. Unique id for each SRA contract (specified by AEMO)

SQL Type: VARCHAR2(30) Polars Type: pl.Categorical

This column is not mandatory.

LASTCHANGED

Date and time this record was 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

New Data Timing

Upon participants making a bid

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("LOADDATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast(
        {
            "AUCTIONID": pl.Categorical,
            "OPTIONID": int,  # or pl.UInt16
            "PARTICIPANTID": pl.Categorical,
            "BIDPRICE": pl.Float64,
            "CONTRACTID": pl.Categorical,
        }
    )
    # Deduplicate
    # We want one row per ['AUCTIONID', 'LOADDATE', 'OPTIONID', 'PARTICIPANTID']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["AUCTIONID", "LOADDATE", "OPTIONID", "PARTICIPANTID"], 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:

• AUCTIONID

• LOADDATE

• OPTIONID

• PARTICIPANTID

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
IRAUCTION	RESIDUE_PRICE_BID	1
IRAUCTION_BIDS	PRICE_BID	1

This means that the CSV files start with metadata columns:

I,IRAUCTION,RESIDUE_PRICE_BID,1,...
D,IRAUCTION,RESIDUE_PRICE_BID,1,...

or

I,IRAUCTION_BIDS,PRICE_BID,1,...
D,IRAUCTION_BIDS,PRICE_BID,1,...

Indexes

• LASTCHANGED

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: IRAUCTION

Copy as Markdown