NEM Settlement Statement and Billing Data (participant-confidential)
Detects a NEM market participant's own AEMO settlement and billing data: extracts of the MMS Data Model tables that AEMO marks Private (visible only to the participant they belong to) - SET_ENERGY_TRANSACTIONS, SET_ENERGY_GENSET_DETAIL, SETGENDATA, SETCPDATA, SET_FCAS_PAYMENT / SET_FCAS_RECOVERY, SET_RECOVERY_ENERGY, SETMARKETFEES, SETREALLOCATIONS and the BILLING_RUN equivalents (BILLING_ENERGY_TRANSACTIONS, BILLINGGENDATA, BILLINGCPDATA, BILLINGASPAYMENTS, BILLINGFEES, BILLINGPRIORADJUSTMENTS, ...) - and AEMO preliminary, final and revision settlement statements for a billing week. The data gives a participant's metered energy, settlement amounts by connection point or generating unit, ancillary-service payments and recoveries, market fees and reallocations. The tables AEMO publishes (DAYTRACK, BILLINGRUNTRK, BILLINGDAYTRK, SETCPDATAREGION, SET_ENERGY_REGION_SUMMARY, SET_ANCILLARY_SUMMARY, SETIRSURPLUS, SET_RUN_PARAMETER, BILLINGREGIONFIGURES) are deliberately not anchors. Companion to au-nem-bid-file (bids) and au-energy-hedge-position-report (contract positions).
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- Medium: the Private table names are distinctive, but they also appear in AEMO's public MMS Data Model Report and in vendor loader documentation, which list the same column names; documentation framing is excluded within the window only. Visibility (Private / Public) of each anchored table was checked against the published data model. The statement path leans on generic statement wording and is gated on independent NEM settlement terms plus dollar amounts. 85/75 are heuristic evidence tiers, not measured accuracy.
- Jurisdictions
- au
- Regulations
- National Electricity Rules, Competition and Consumer Act 2010 (Cth), Security of Critical Infrastructure Act 2018 (Cth)
- Frameworks
- ISO 27001
- Data categories
- energy-market, trading, financial
- Scope
- narrow
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Unsupported, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?i)\b(?:SET_ENERGY_TRANSACTIONS|SET_ENERGY_GENSET_DETAIL|SET_RECOVERY_ENERGY|SET_FCAS_PAYMENT|SET_FCAS_RECOVERY|SETGENDATA|SETCPDATA|SETMARKETFEES|SETREALLOCATIONS|BILLING_ENERGY_TRANSACTIONS|BILLING_ENERGY_GENSET_DETAIL|BILLING_DAILY_ENERGY_SUMMARY|BILLING_GST_SUMMARY|BILLINGCPDATA|BILLINGGENDATA|BILLINGASPAYMENTS|BILLINGASRECOVERY|BILLINGFEES|BILLINGFINANCIALADJUSTMENTS|BILLINGPRIORADJUSTMENTS|BILLINGREALLOC)\b|\b(?:(?:preliminary|final|revision)\s+(?:settlement\s+)?statement|settlement\s+statement|billing\s+week\s+\d{1,2})\b
Corroborative evidence keywords
AEMO, billing week, bill run, settlement run, trading interval, ancillary services, FCAS, market fees, reallocation, DUID, TNI
Proximity: 300 characters
Should match
I,SETTLEMENTS,SET_ENERGY_TRANSACTIONS,1,SETTLEMENTDATE,VERSIONNO,PERIODID,PARTICIPANTID,CONNECTIONPOINTID,REGIONID,RRP,TLF,CE_MWH,TOTAL_MWH,TOTAL_AMOUNT D,SETTLEMENTS,SET_ENERGY_TRANSACTIONS,1,2026/09/14 00:00:00,2,17,EXAMPLEGEN,QABC1X,QLD1,84.12,0.9876,52.4,52.4,4407.89— Participant settlement extract with run keys and an amount column - intended 85Weekly reconciliation: BILLING_ENERGY_TRANSACTIONS for CONTRACTYEAR 2026 WEEKNO 38 BILLRUNNO 3 loaded into the settlement ledger.— Billing table with three run-key columns, no amount column - intended 75AEMO Final Statement - billing week 38, contract year 2026 Energy (QLD1): $1,284,516.20 Ancillary services (FCAS) payments: $42,118.75 Market fees: -$3,904.11— AEMO final statement with region, context and several dollar amounts - intended 85Revision statement received from AEMO for the bill run; prior period adjustment $18,240.00 owed to the participant.— Revision statement with AEMO / bill run and one amount - intended 75
Should not match
Package: SETTLEMENT_DATA. SET_ENERGY_TRANSACTIONS - Visibility: Private. Primary Key Columns: SETTLEMENTDATE, VERSIONNO, PERIODID, PARTICIPANTID, CONNECTIONPOINTID. Table schema: TOTAL_AMOUNT NUMBER(18,8).— MMS Data Model documentation page for the table (public)I,SETTLEMENTS,DAYTRACK,6,SETTLEMENTDATE,REGIONID,EXANTERUNSTATUS,EXPOSTRUNNO I,BILLING,BILLINGRUNTRK,1,CONTRACTYEAR,WEEKNO,BILLRUNNO,STATUS,POSTDATE— Public settlement tracking tables (DAYTRACK, BILLINGRUNTRK) that AEMO publishesYour final statement for the credit card account shows a closing balance of $2,431.18 due on 14 November.— Bank final statement - no NEM settlement contextThe final settlement statement for the property purchase was issued by the conveyancer; balance payable $412,000.— Conveyancing settlement statement - no NEM settlement contextNotes to the financial statements: AEMO final statement receivables for the June billing week were $14.2m across QLD1 and NSW1 ($9,800,000 and $4,400,000).— Annual-report note quoting settlement receivables (public)
Known false positives
- AEMO's public MMS Data Model Report and vendor loader documentation list the Private table and column names. Mitigation: Documentation framing (Data Model Report, MMS Data Model, Primary Key Columns, Table schema, Official MMS Datatype, NEMWEB) is excluded within the proximity window at every tier.
- AEMO publishes some settlement tables (DAYTRACK, BILLINGRUNTRK, BILLINGDAYTRK, SETCPDATAREGION, SET_ENERGY_REGION_SUMMARY, SET_ANCILLARY_SUMMARY, SETIRSURPLUS, SET_RUN_PARAMETER, BILLINGREGIONFIGURES). Mitigation: Those tables are not in the primary; only tables the data model marks Private are anchors.
- Bank, conveyancing and legal "final statement" / "settlement statement" wording. Mitigation: The statement path needs an independent NEM settlement term and a dollar amount for 75, and a NEM region ID plus two distinct amounts for 85.