October 2025

Audience

B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. and B2M Business-to-Market Retail Market Participants.

Contents

Summary

Explains the detailing the schema updates, procedural changes, and new functionalities for compliance with the National Electricity Rules See Relevant Rules or Procedures (NER National Electricity Rules. The rules made under the National Electricity Law (NEL). They govern the day-to-day operations of the National Electricity Market (NEM) and provide the framework for network regulation.) and related procedures effective from late 2025.

 

aseXML Schema Updates and Transformations

This release introduces the B2B and B2M aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. r46 schema version updates. Please transition to this version to access new fields and to support upcoming rule changes. The schema includes enhancements such as the introduction of single-occurrence elements BuildingOrPropertyName and BuildingOrPropertyName2, with transitional support for two BuildingOrPropertyName elements until 30 November 2025. From 1 December 2025, the BuildingOrPropertyName and BuildingOrPropertyName2 elements must be used to represent primary and secondary complex names respectively.

If you are not ready to transition you will have new aseXML items removed with flagged comments in transformed payloads during the transition period.

The schema files updated include ElectricityMasterStandingData, Enumerations, ClientInformation, and others. Changes include increased character lengths for address fields to align with the Australian Standard AS4590.1:2017, new enumerated values for service order response codes, and the addition of new service order subtypes such as Install Meter Isolation Device and Temporary Isolation variants.

Legacy Meter Replacement Plan (LMRP)

The LMRP Legacy Meter Replacement Plan mandates replacing existing type 5 and 6 meters with type 4 smart meters by 30 November 2030. The LNSP, in coordination with FRMP Financially Responsible Market Participant, usually a retailer, Generator, Market Customer or a Market Small Generator Aggregator, identified in respect of a connection point. Responsible for dealings with AEMO in relation to a specific load. and MC Meter Coordinator; The Role Code used in MSATS for an MC is RP., must record and maintain the LMRP in MSATS Market Settlement and Transfer Solutions. The procedures published by AEMO under clause 7.2.8 of the National Electricity Rules, which include those governing the recording of financial responsibility for energy flows at a connection point, the transfer of that responsibility between market participants, and the recording of energy flows at a connection point.. The release supports initial population of LMRP values using the Blind Update Tool Allows participants to submit a csv formatted payload containing data for new CATS Standing Data fields requiring a value A limited subset of CATS CR validations is applied to a BUT Submission The History Model is not updated so not suitable for Settlement or Compliance Standing Data (BUT Blind Update Tool) between 26 October and 27 November 2025, after then CR Change Request notifications are used for updates. LMRP values are included in standing data and CATS Customer Administration and Transfer Solution. A set of procedures, principles and obligations made under the National Electricity Rules as part of Market Settlement and Transfer Solutions (MSATS), and applicable to NMI (National Metering Identifier) small and large classifications. reports accessible to authorised participant roles.

 

Site Defects

When defects preventing meter exchanges are identified, Metering Coordinators must record Defect Flag, Defect Type, and Defect Issuing MC in MSATS. These fields are included in change requests and notifications. They are removed automatically when legacy meters are replaced with communication meters. Site The physical location of the connection point, see B2B Procedures: Customer and Site Details and Service Orders Process. defects are supported in B2B transactions, validation module, and MSATS reports.

 

Shared Fuse Meter Replacement (One In All In)

A new procedure addresses meter upgrades on shared fuses, requiring coordinated replacement of legacy meters for multiple customers simultaneously. The release introduces related B2B service order request subtypes and notification types to facilitate this process, including Temporary Isolation-Scoping Request The way information is returned from an API. In a request, the client provides a resource URL with the proper authorization to an API server. The API returns a response with the information requested. and Temporary Isolation-One In All In.

Embedded Network Settlement Anomalies

Changes restrict retrospective updates to embedded network child NMI See Relevant Rules or Procedures datastreams to prevent settlement anomalies. A new Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS. (CR 4060) enables prospective updates to child NMI datastream status. These changes help maintain settlement integrity within the NEM.

Last Consumer Change Date (LCCD) Auto-population

AEMO Australian Energy Market Operator auto-populates the LCCD field in MSATS when a NMI status changes from Greenfield to Active, supporting Consumer An end use customer of energy. Data Right Rule compliance. The updated LCCD is included in change request notifications to authorised participants.

Metering Exemptions

This release introduces new malfunction exemption types with specified rectification timeframes, including Whole Current The participant can receive files compliant to the current aseXML version. Connected NMI and Family Failure categories. The MSATS web portal and Meter Exemptions API Application Programming Interface; a set of clearly defined methods of communication between various software components. are updated to include new fields such as Documentation Provided and Substitution A process undertaken for the replacement of missing (null) or erroneous accumulated metering data or interval metering data where metering data has failed Validation. Method The allowed operation for a resource, e.g. GET, POST, PUT, DELETE, and so on. These operations determine whether you’re reading information, creating new information, updating existing information, or deleting information.. Validation A process to test the veracity and integrity of metering data. rules govern exemption updates and extensions to ensure compliance.

ROLR Reports

The Retailer See Relevant Rules or Procedures of Last Resort (ROLR Retailer of Last Resort. A scheme principally designed to ensure that in the event of retailer failure, arrangements are in place to ensure customers continue to receive electricity and/or gas supply.) reporting process transitions from email to file delivery via Participant File Server The publishing point from AEMO systems to participant systems. Each participant is allocated an account and access to private and public areas. Participants are responsible for interfacing with the participant file server. Outbox in zipped aseXML format with CSV payloads. Several obsolete reports are discontinued from 1 December 2025. New report types include ROLR Raised CR, ROLR Retailer of Last Resort. A scheme principally designed to ensure that in the event of retailer failure, arrangements are in place to ensure customers continue to receive electricity and/or gas supply.Cancel A ServiceOrderStatus indicating the Service Order is cancelled. CR, and ROLR NMI List, providing detailed information about NMIs affected by ROLR events and associated change requests.

 

CATS Standing Data and Reports

New standing data attributes such as LegacyMtrReplacementPlan, Defect Flag, Defect Type, Defect Issuing MC, and BuildingOrPropertyName2 are added to CATS NMI data tables. These are reflected in updated CATS reports (C1, C4, C7, Snapshot) and accessible through MSATS interfaces. RM29 Standing Data Quality reports include new queries to support LMRP tracking.

B2B and B2M System Impacts

Participants must upgrade to aseXML r46 to receive and send new B2B and B2M schema fields. The release includes changes to B2B Browser A web interface supporting the creation and management of a defined set of business-to-business transactions and acknowledgements. Optionally used to manage your B2B inbox and outbox. It remains part of the B2B e-Hub services. interfaces, validation modules, and transaction types to support LMRP, site defects, shared fuse procedures, and IEC enhancements. B2M schema updates align with B2B changes and include new elements and enumerations for address data and defect information.