BILLING_NMAS_TST_PAYMENTS

BILLING_NMAS_TEST_PAYMENTS publish the NSCAS/SRAS Testing Payments data for a posted billing week. 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.

Column Schema

BILLRUNNO

The current Billing RunNo for the week

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

This column is mandatory, and a primary key.

CONTRACTID

The NMAS Contract Id

SQL Type: VARCHAR(10) Polars Type: pl.Categorical

This column is mandatory, and a primary key.

CONTRACTYEAR

AEMO Contract Year number starting in week containing 1 January

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

This column is mandatory, and a primary key.

PARTICIPANTID

The Participant from whom the amount is recovered

For more information, see the dedicated documentation page.

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

This column is mandatory, and a primary key.

SERVICE

The type of NSCAS service. Current value values are: - REACTIVE - LOADSHED

SQL Type: VARCHAR(10) Polars Type: str

This column is mandatory, and a primary key.

WEEKNO

Week no within the contract year. Week no 1 is the week containing 1 January

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.

PAYMENT_AMOUNT

The Testing Payment Amount to recover

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

This column is not mandatory.

New Data Timing

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

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",
    ).cast(
        {
            "BILLRUNNO": int,  # or pl.UInt16
            "CONTRACTID": pl.Categorical,
            "CONTRACTYEAR": int,  # or pl.UInt16
            "PARTICIPANTID": pl.Categorical,
            "SERVICE": str,
            "WEEKNO": int,  # or pl.UInt16
            "PAYMENT_AMOUNT": pl.Float64,
        }
    )
    # Deduplicate
    # We want one row per ['BILLRUNNO', 'CONTRACTID', 'CONTRACTYEAR', 'PARTICIPANTID', 'SERVICE', 'WEEKNO']
    .unique(
        subset=[
            "BILLRUNNO",
            "CONTRACTID",
            "CONTRACTYEAR",
            "PARTICIPANTID",
            "SERVICE",
            "WEEKNO",
        ],
        keep="any",
    )
)

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:

• BILLRUNNO

• CONTRACTID

• CONTRACTYEAR

• PARTICIPANTID

• SERVICE

• 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	NMAS_TST_PAYMENTS	1

This means that the CSV files start with metadata columns:

I,BILLING,NMAS_TST_PAYMENTS,1,...
D,BILLING,NMAS_TST_PAYMENTS,1,...

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