3 Participant Impact

To comply with this Release, participants must:

Decide if you need to implement B2B schema transforms. For help, see B2B Browser in Markets Portal Help.
Schedule staff and resources to upgrade your B2B and B2M aseXML schemas to r46 For help, see Guide to Transition of aseXML.
Download and install upgraded software versions. For help, see Related software.

3.1 B2B impact

Item	Project or enhancement	Changes
B2B aseXML schema	IEC enhancements Site Defects LMRP Shared Fusing Meter Replacement (One In All In)	LMRP, Site Defects (One In All In), address and B2B field length alignment changes to support B2B Procedures v3.9
B2B Validation Module	Site defects LMRP IEC enhancements Shared Fusing Meter Replacement (One In All In)	New permitted values for B2B transactions
B2B Browser	Site Defects LMRP IEC enhancements Shared Fusing Meter Replacement (One In All In)	Updates to Create Transaction interfaces
B2B transactions	Site Defects LMRP IEC enhancements	New: Service Order Request sub types for Metering Service Works and Supply Service Works. Updates: Enumerated values for One Way Notification subtype Meter Faults and Issues Notification and Service Order Response Field length for Service Order and Customer and Site Detail Notification fields, HazardDescription, FormNumber, and FormReference

3.2 B2M impact

Item	Project or enhancement	Change
aseXML B2M schema	ERCF and IEC enhancements LMRP Site Defects	New version
CATS NMI Standing Data	LMRP Site Defects	New CATS_NMI_DATA attributes: LMRP Defect Flag Defect type Defect Issuing MC BuildingorPropertyName2 Changes to address elements to align with AS4590.1:2017
Blind Update Tool (BUT)	LMRP	LMRP field to support initial population between 26 October 2025 to 27 November 2025 as per rule change
Change requests and notifications	LMRP Site Defects Embedded Network Settlement Anomalies ICF 077 and 078	New and updated CRs and notifications
CATS reports	LMRP Site Defects	Changes to CATS Reports (C1, C4, C7, C29) and MSATS Snapshot Report. It includes five new attributes: LMRP Defect Flag Deflect type Defect Issuing MC BuildingorPropertyName2 Changes to address elements to align with AS4590.1:2017
Last Consumer Change Date (LCCD)	ICF077	AEMO auto-populates the LCCD field in the NMI create process, i.e. populate the NMI’s LCCD with the activation date for NMIs moving from a greenfield status to active status

3.3 aseXML r46

The r45 aseXML schema changes only applies B2B gas retail. Gas participants are scheduled to adopt r45 in Q2 2026.

r46 aseXML schema Specification to describe the structure of an aseXML message. includes changes for MSR Package 1 and ERCF Electricity Retail Consultative Forum and 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. Working Group enhancements.

Effective 26 October 2025, participants affected by the B2M Business-to-Market change in MSATS Procedures All of the following procedures: CATS Procedures, WIGS Procedures, MDM Procedures, NMI Standing Data Schedule, NMI Procedure, and Part A of the NEM RoLR Processes. v7 must implement r46. This allows:

Capturing changes to the LMRP Legacy Meter Replacement Plan value set by BUT Blind Update Tool through the 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. C1 ReportResponse.
Ensuring B2M CRs referencing 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. elements 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. Procedures v7.1 before 1 December 2025 fail validation in MSATS.

From the effective date 1 December 2025 with the MSR Package 1 Defect, ICF changes, and B2B v3.9 Procedures changes, participants must implement r46 to meet defect and address alignment obligations.

For help transitioning, see Transition of aseXML.

3.3.1 aseXML B2B schema r46

Current B2B aseXML schema	Superseded B2B aseXML schema
r46	r43

3.3.2 B2B schema transforms

Receiving version	Transforms
r46	r43 to r46
r43	r46 to r43

For details, see .

3.3.3 aseXML B2M schema r46

Latest	Current	Superseded
r46	r46	r44

If you are not ready to transition your B2M aseXML schema with AEMO Australian Energy Market Operator:

Change your schema preference to Current before the Release Dates.
When AEMO transitions, we move you to the Superseded preference.
When ready, complete your upgrade and observe the processing is correct. You may still receive some older aseXML versions for a short time during the transition period, around 24 hours.
Change your schema preference to Current.

For details, see B2M aseXML schema.

3.3.4 B2M aseXML schema preference lower than r46

For participants having a B2M aseXML schema preference lower than r46, the new aseXML items are removed from Message Responses with a comment flagging the removal in the transformed aseXML payload.

3.3.5 B2M aseXML schema transition

For details, see B2M schema release implementation.

3.3.6 aseXML schema change impact summary

For details, see:

3.3.7 BuildingOrPropertyName element transition

The aseXML r46 schema introduces the use of single-occurrence elements BuildingOrPropertyName (primary) and BuildingOrPropertyName2 (secondary).

In the BuildingOrPropertyName element, the maxOccurs="2" attribute remains to support two BuildingOrPropertyName values for B2B transaction until 30 November 2025. From the B2B Procedures The documents that comprise the B2B Procedures prescribing the content of, the processes for, and the information to be provided to support B2B communication. effective date 1 December 2025, 2 values must be sent using the BuildingOrPropertyName and BuildingOrPropertyName2 elements.

3.4 AEMO MSATS configurable code fields

AEMO uses the CND CATS NMI Data_[nn] framework to map field names in the CATS_NMI See Relevant Rules or Procedures_DATA table to the C1 CATS Transaction See Relevant Rules or Procedures Field Validations report. Where possible, participants should use the procedural field names defined in Standing Data for MSATS.

Existing cats_nmi_data CND_nn fields are assigned to the following field names:

Legacy Meter Replacement Plan = CND_14
Defect flag = CND_15

Defect Type = CND_16
Defect Issuing MC Meter Coordinator; The Role Code used in MSATS for an MC is RP. = CND_17
Building or Property Name 2 = CND_18

AEMO is increasing the CND_[nn] framework to cater for new fields in the future.

AEMO recommends participants do not hard code the AEMO MSATS configurable fields.

3.5 ROLR reports

Changes include:

Discontinuing obsolete reports from 1 December 2025, as described in the 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. Procedures.
ROLR reports added to the CATS transaction group for delivery to the Participant File Outbox by API Application Programming Interface; a set of clearly defined methods of communication between various software components. or FTP File transfer protocol.

See ROLR Reports.