BILLING_APC_COMPENSATION

Billing result table for APC compensation payments.

Updated with each billing run

Warning

This is a different table to BILLINGAPCCOMPENSATION

Column Schema

APEVENTID

AP Event Id

SQL Type: NUMBER(6) Polars Type: pl.Int32

This column is mandatory, and a primary key.

BILLRUNNO

Billing run number

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

This column is mandatory, and a primary key.

CLAIMID

AP Event Claim Id

SQL Type: NUMBER(6) Polars Type: pl.Int32

This column is mandatory, and a primary key.

CONTRACTYEAR

Billing contract year

SQL Type: NUMBER(4) Polars Type: pl.UInt16

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) Polars Type: pl.UInt16

This column is mandatory, and a primary key.

COMPENSATION_AMOUNT

Payment amount to the participant

SQL Type: NUMBER(18,8) Polars Type: pl.Float64

This column is not mandatory.

COMPENSATION_TYPE

The Type of Administered Price Compensation Claim. Valid values: DIRECT_COST, OTHER_COST

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

This column is not mandatory.

EVENT_TYPE

The Administered Price Event Type. Valid values: ENERGY, FCAS, BOTH

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

This column is not mandatory.

LASTCHANGED

The date and time of last changed record

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

PARTICIPANTID

Participant identifier

For more information, see the dedicated documentation page.

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

This column is not mandatory.

New Data Timing

Generated when a billing run is posted

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(
        {
            "APEVENTID": int,  # or pl.Int32
            "BILLRUNNO": int,  # or pl.UInt16
            "CLAIMID": int,  # or pl.Int32
            "CONTRACTYEAR": int,  # or pl.UInt16
            "WEEKNO": int,  # or pl.UInt16
            "COMPENSATION_AMOUNT": pl.Float64,
            "COMPENSATION_TYPE": pl.Categorical,
            "EVENT_TYPE": pl.Categorical,
            "PARTICIPANTID": pl.Categorical,
        }
    )
    # Deduplicate
    # We want one row per ['APEVENTID', 'BILLRUNNO', 'CLAIMID', 'CONTRACTYEAR', 'WEEKNO']
    # Tie-breaker: greatest value of LASTCHANGED
    .sort(LASTCHANGED, descending=False)
    .unique(
        subset=["APEVENTID", "BILLRUNNO", "CLAIMID", "CONTRACTYEAR", "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:

• APEVENTID

• BILLRUNNO

• CLAIMID

• CONTRACTYEAR

• WEEKNO

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
BILLING	APC_COMPENSATION	2

This means that the CSV files start with metadata columns:

I,BILLING,APC_COMPENSATION,2,...
D,BILLING,APC_COMPENSATION,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

Copy as Markdown