6 B2M

6.1 B2M aseXML schema

To obtain schemas, guidelines, whitepapers etc, see aseXML Standards.

This schema release r46 affects B2M Business-to-Market.

For help with schema transitions, see Guide to Transition of aseXML.

For potentially impacted files, transactions, and versioned types for r46, see Impact summary.

6.1.1 Schema changes summary

Affected files	New	Modified
aseXML_r46	n/a	Included file versions: ElectricityMasterStandingData Enumerations ClientInformation
ElectricityMasterStandingData_r46	Elements to support requirements related to the LMRP, Site Defects, and Site Defect Notifications: LegacyMtrReplacementPlan DefectFlag DefectIssuingMC DefectType
Enumerations	4 new enumerations: LL - LOWER LEVEL PTHS - PENTHOUSE PL - PLATFORM PD - PODIUM	AustralianFloorOrLevelType - Maximum length updated from 2 to 4 characters Adds comment to describe the name mapping from AS4590.1:2017 to the 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. for AustralianStreetName: AS4590.1:2017 abbreviation – aseXML Abbreviation - Name FRTL - FITR - FIRETRAIL AV - AVE - AVENUE CR - CRES - CRESCENT GLDE – GLD - GLADE PWY – PKWY - PARKWAY Adds comment to describe the name mapping from AS4590.1:2017 to the aseXML for AustralianFlatOrUnitType: AS4590.1:2017 abbreviation – aseXML Abbreviation - Name DUPL - DUP - DUPLEX FCTY - FY - FACTORY FLAT – F - FLAT MBTH – MB - MARINE BERTH OFFC – OFF - OFFICE ROOM - RM - ROOM STLL - SL - STALL UNIT - U - UNIT WHSE - WE – WAREHOUSE
ClientInformation_r46	New element BuildingOrPropertyName2	BuildingOrPropertyName Updates maximum length from 30 to 50 characters Removes the MaxOccurs value StreetName – Updates maximum character length from 30 to 45 characters FloorOrLevelType – Updates maximum character length from 2 to 4 characters

To minimise significant changes in participants’ systems, AustralianStreetName and AustralianFlatOrUnitType retains certain enumerations rather than changing them as defined in AS4590.1:2017. The enumerations schema file includes comments to map the AS4590.1:2017 Abbreviation to the aseXML abbreviation.

6.1.2 B2M schema release implementation

During the pre-production and production implementations, participants’ preferences for their B2M transaction receiving schema version is transitioned by AEMO Australian Energy Market Operator in the 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. Web Portal > Participants > Participant Schema See aseXML Schema. as follows:

Before MSATS release		During implementation		After MSATS release
Transaction See Relevant Rules or Procedures group	B2M participant schema	Outbound schema version		B2M participant schema	Outbound schema version
CATS	LATEST	r44	AEMO transitions participants on LATEST to r46 for continued compliance	LATEST	r46
NMID	LATEST	r44		LATEST	r46
MDMT	LATEST	r44		LATEST	r46
CATS	CURRENT	r44	Participants on CURRENT remain on , with the setting changed to Superseded. Participants can choose when to transition to the new Current/Latest setting	SUPERSEDED	r44
NMID	CURRENT	r44		SUPERSEDED	r44
MDMT	CURRENT	r44			r44
CATS	SUPERSEDED	r43	AEMO transitions participants on the Superseded version r43 to the new Superseded version r44. r43 and earlier versions are unsupported; all responses return in r44	SUPERSEDED	r44
NMID	SUPERSEDED	r43		SUPERSEDED	r44
MDMT	SUPERSEDED	r43		SUPERSEDED	r44

6.1.3 Assign null value to site defect elements

To assign a null value for the DefectFlag, DefectType, and DefectIssuingMC elements, use the attribute xsi:nil="true" as shown in the following example.

Copy

<MasterData>
      <DefectFlag xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
      <DefectType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
      <OriginatingMC xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</MasterData>

6.2 Blind update tool

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) has the following changes:

LEGACY_METER_REPLACEMENT_PLAN field to support initial population between 26 October 2025 to 27 November 2025.
Updates to the LEGACY_METER_REPLACEMENT_PLAN values where the AER See Relevant Rules or Procedures has approved amendments to the LMRP Legacy Meter Replacement Plan schedule Energy Rules Terms over the acceleration period (2025-2030).

When the LEGACY_METER_REPLACEMENT_PLAN attribute is set in BUT, all entitled roles can request and receive the updated value in a C1 or MSATS Snapshot report.

BUT updates do not trigger CATS notifications. AEMO recommends only performing BUT updates when participants can capture and ingest changes.

6.2.1 csv submission example

A csv payload Payload example for submitting legacy meter replacement plan values is shown below.

Copy

C,TEST,BLIND_UPDATE_SUBMISSION,PARTICIPANTID,NEMMCO,2025/05/02,16:12:00,,,,NEM,BUT02050415
I,BUS,NMI_DATA,1,NMI,FIELD,NEW_VALUE
D,BUS,NMI_DATA,1,9998887771,LEGACY_METER_REPLACEMENT_PLAN,2026/05/10
D,BUS,NMI_DATA,1,9842723212,LEGACY_METER_REPLACEMENT_PLAN,2026/05/10
D,BUS,NMI_DATA,1,9483292123,LEGACY_METER_REPLACEMENT_PLAN,2026/05/10
C,END OF REPORT,6

For information about the BUT payload format, see Create Payload and CSV Data Format Standard in Markets Portal Web applications for registered participants only. Requires access to MarketNet. Help.

6.2.2 BUT interfaces

There are no changes to the BUT interface in MSATS Web Portal or BUT API Application Programming Interface; a set of clearly defined methods of communication between various software components..

6.3 CATS standing data

New standing data items using existing cats_nmi_data CNDnn fields.

Field	MSATS standing data table	Description
Legacy Meter Replacement Plan	CATS_NMI_DATA	The scheduled replacement date for legacy meters
Defect Flag	CATS_NMI_DATA	A flag identifying the defect at site which prevents a metering upgrade
Defect Type	CATS_NMI_DATA Enumeration values stored in MSATS_CODES_DATED	The type of defect preventing the repair of a meter or replacement of a legacy meter
Defect Issuing MC	CATS_NMI_DATA	The MC that raised the defect
Building or Property Name 2	CATS_NMI_DATA	A secondary address field for capturing additional building or property name information

The standing data items are:

Displayed in the NMI Master and NMI Master Summary interfaces in MSATS.
Contained in the C1, C4, C7, and Snapshot reports. For information about roles that have access to the standing data fields, see Table 17-C – NMI Standing Data See National Electricitiy Rules Items and CATS Standing Data The data held in the following database tables: • CATS_NMI_Data_Stream • CATS_NMI_Data • CATS_Meter_Register • CATS_NMI_Participants_Relationships • CATS_Register_Identifier NMI Standing Data is a sub-set of the CATS Standing Data. NMI See Relevant Rules or Procedures Discovery Data Access Rules The National Gas or Electricity rules. in MSATS Procedures - Principles and Obligations for All Connection Points v7.1.

6.4 Change requests and notifications

6.4.1 LMRP

Existing 5050/5051 CRs and validation rules updated to allow DNSPs to update the LMRP value.

Notifications for LMRP updates are sent to participants with an active association to the NMI.

6.4.2 Site defects

CRs and notifications:

CR Change Request 5301 – Change Defect Information - retrospective for MCs updating the Defect flag, Defect Type, and Defect Issuing MC Meter Coordinator; The Role Code used in MSATS for an MC is RP.:
Notifications for the Defect flag, Defect Type, and Defect Issuing MC updates are sent to participants with an active association to the NMI.
For CR 3004/3005 (Exchange See Relevant Rules or Procedures of Metering Information) or 3090/3091 (Advanced Meter Exchange), the NMI’s Defect flag, Defect Type, and Defect Issuing MC values are automatically set to null when a meter installation code BASIC or MRIM is removed, and a new meter installation code of COMMS or MRAM is activated. The LegacyMtrReplacementPlan value remains populated.

6.4.3 Embedded network settlement anomalies

To ensure the NMI datastream status code does not change retrospectively:

CR 4050/4051 includes a validation to check the embedded network child name is not populated.
New CR 4060 Change NMI Datastream Details – A child NMI datastream can be updated to set the datastream status as active or inactive.

A retrospective Change NMI Datastream is not available for child NMIs.

6.4.4 ICF-077 Auto populate LCCD field for new NMIs

When an NMI status is updated from Greenfield “G” to Active “A”, AEMO auto-populates the LCCD field and includes the updated LCCD field in the CR 5050/5051 and CR5060/5061 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. notification to all participants who are entitled to receive the notifications.

6.4.5 ICF-078

Affected CR Codes for new field BuildingOrPropertyName2

Change Reason Code	Impacted
2000/1	New LNSP initiating the CR
2020/1	New ENM initiating the CR
2500/1	New LNSP initiating the CR
2520/1	New ENM initiating the CR
5001	New LNSP (who must be Current LNSP where the NMI exist) initiating the CR
5021	New ENM (who must be Current ENM where the NMI exist) initiating the CR
5050/1	Current LNSP initiating the CR
5060/1	Current ENM initiating the CR
5100/1	AEMO initiating standing data update

6.5 NMI master and NMI master summary interfaces

The NMI Master and NMI Master Summary interfaces include new fields:

LegacyMtrReplacementPlan
Defect flag
Defect Type
Defect Issuing MC
BuildingOrPropertyName2

6.6 RM29 standing data quality report

The RM29 SDQ report includes new queries to support the LMRP.

6.6.1 LMRP_IS_NULL query

Query ID	LMRP_IS_NULL
Purpose	Identifies BASIC or MRIM NMIs with no LMRP value. Victorian Type 5 Advanced Metering Installation (VICAMI) meters are excluded
Recipient The receiver of a B2B Transaction or B2B Acknowledgement. This can be either a notification, request for data or request to perform work.	MC
Delivery	Participant Outbox every week
Data source	CATS
Format	aseXML compliant XML message with csv payload

Output

H row	D row example	MSATS Standing Data element name	Description
QueryId	LMRP_IS_NULL	n/a	Query identifier
Stat_Date	2024-07-08	n/a	Query run date in the format YYYY/MM/DD
ParticipantId	MCPID	Party	The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is MC
RoleId	RP	Role	The Participant relationship (Role) with the NMI in CATS_NMI_PARTICIPANT_RELATIONS
Source	CATS	n/a	[Fixed value]
Table	n/a	n/a	n/a
NMI_ID	20001000048	NMI	NMI. This number is unique for each connection point within the NEM.
METER_SERIAL	2319099	SerialNumber	NMI serial number
SDR_KEY_3	n/a	n/a	n/a
StartDate	25/11/2026	Fromdate	The NMI start date or start date of the record update
EndDate	31/12/9999	Todate	Date the record ends
Field	n/a	n/a	n/a
FRMP	FRMP	Party	The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is FRMP
LNSP	LNSP	Party	The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is LNSP
MITC	BASIC	InstallationTypeCode	Meter Installation Type Code
LMRP	12-JAN-2026	LegacyMtrReplacementPlan	Legacy Meter Replacement Plan date
Defect_Flag	Y	Defect Flag	Indicates a defect exists for a given NMI

Example

More information provided in a technical specification update.

6.6.2 LMRP_IN_PAST query

Query ID	LMRP_IN_PAST
Purpose	Identifies BASIC or MRIM NMIs with a LMRP date in the past and no defect is assigned
Recipient	MC
Delivery	Participant Outbox every week
Data source	CATS
Format	aseXML compliant XML message with csv payload

Output

H row	D row example	MSATS Standing Data element name	Description
QueryId	LMRP_IN_PAST	n/a	Query identifier
Stat_Date	2024-07-08	n/a	Query run date in the format YYYY/MM/DD
ParticipantId	MCPID	Party	The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is MC
RoleId	RP	Role	The Participant relationship (Role) with the NMI in CATS_NMI_PARTICIPANT_RELATIONS
Source	CATS	n/a	Fixed value
Table	n/a	n/a	n/a
NMI_ID	20001000048	NMI	NMI. This number is unique for each connection point within the NEM.
METER_SERIAL	2319099	SerialNumber	NMI serial number
SDR_KEY_3	n/a	n/a	n/a
StartDate	2026-11-25	Fromdate	The NMI start date or start date of the record update
EndDate	2027-12-31	Todate	Date the record ends
Field	n/a	n/a	n/a
FRMP	FRMP	Party	FRMP Participant ID
LNSP	LNSP	Party	LNSP Participant ID
MITC	BASIC	InstallationTypeCode	Meter Installation Type Code
LMRP	12-JAN-2026	LegacyMtrReplacementPlan	Legacy Meter Replacement Plan date
Defect_Flag	Y	Defect Flag	Indicates a defect exists for a given NMI

Example

More information provided in a technical specification update.

6.6.3 COMMS_MTR_WITH_DEFECT query

Query ID	COMM_MTR_WITH_DEFECT
Purpose	Identifies NMIs with site defects that are not Basic (Type 6) or MRIM (Type 5) meters. Site defect details should only be provided for Basic and MRIM meters
Recipient	FRMP and MC
Delivery	Participant Outbox every week
Data source	CATS
Format	aseXML compliant XML message with csv payload

Output

H row	D row example	MSATS Standing Data element name	Description
QueryId	DEFECT_ON_COMMS_MTR	n/a	Query identifier
Stat_Date	2024-07-08	n/a	Query run date in the format YYYY/MM/DD
ParticipantId	MCPID	Party	The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is MC
RoleId	RP	Role	The Participant relationship (Role) with the NMI in CATS_NMI_PARTICIPANT_RELATIONS
Source	CATS	n/a	[Fixed value]
Table	n/a	n/a	n/a
NMI_ID	20001000048	NMI	NMI. This number is unique for each connection point within the NEM.
FRMP	FRMPID	ParticipantID	FRMP Participant ID
LNSP	LNSPID	ParticipantID	LNSP Participant ID
StartDate	2026-11-25	Fromdate	The NMI start date or start date of the record update
EndDate	2027-12-31	Todate	Date the record ends
Defect_Flag	Y	Defect Flag	Flags whether a defect exists for a given NMI
Field	n/a	n/a	n/a
MITC	Basic	InstallationTypeCode	Meter Installation Type Code
Defect_Flag	Y	Defect Flag
Defect_Type	LIVEWIRING	Defect Type	Defect classification
Defect_ Issuing_MC	ENERGYX	Defect Issuing MC	MC Participant ID who issued the defect
Not used	n/a	n/a	n/a
Value4	n/a	n/a	n/a
Value5	n/a	n/a	n/a

Example

More information provided in a technical specification update.

6.7 Meter exemptions

Meter exemptions include new exemption categories and a malfunction duration.

6.7.1 Meter malfunction exemption types

4 new malfunction exemption types for rectifying a meter malfunction.

Type	Nature of exemption	Timeframe to rectify
Whole Current Connected NMI	Faulty meter Faulty comms module	30 business days
LV CT Connected NMI	Faulty meter Faulty comms module Faulty CT CT cabling or test block	As specified by the MC
HV Connected NMI	Faulty meter Faulty metering unit Faulty comms module Faulty CT Faulty VT Blown fuse VT CT cabling or test block Marshalling box	As specified by the MC
Family Failure	Whole current meter LV CT meter LV current transformer	140 business days for whole current meter

If the end date entered in the exemption exceeds the mandated timeframe to rectify the malfunction, the status is updated to More Info for the Participant to update.

If the status of the exemption is More Info and the required information has not been updated or received by the end date, it will be rejected.

6.7.2 MSATS web portal > Meter exemptions

For MCs, the Participant details interface includes the following changes:

A Documentation provided checkbox indicating additional documentation has been sent to AEMO. This is available when creating an exemption or the exemption has a status of More Info.
The NMI details section includes a substitution method field to specify the substitution method when the 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 value is Y.

A screenshot of a computer

AI-generated content may be incorrect.

6.7.3 Metering Exemption API

The Submit Meter Exemption request payload and the Get Meter Exemption Details responses include new fields.

Field	Data type	Mandatory	Description
docProvided	CHAR (1)	Conditional	Documentation is sent after creating or updating an exemption. Values are Y or N
substitutionMethod (JSON) SUBSTITUTION_METHOD (csv)	NUMBER (2)	Conditional	The substitution method when the substitution flag is set. It must be provided when substitutionReq is Y

Field

Data type

Mandatory

Description

docProvided

CHAR (1)

Conditional

Documentation is sent after creating or updating an exemption. Values are Y or N

substitutionMethod (JSON)

SUBSTITUTION_METHOD (csv)

NUMBER (2)

Conditional

The substitution method when the substitution flag is set. It must be provided when substitutionReq is Y

Submit meter exemption

The Documentation provided field is added to first part of the payload request containing the meter exemptions details. The Substitution method is added in the second part of the JSON JavaScript Object Notification or csv Comma Separated Values. A file format for data using commas as delimiters. payload containing the meter exemption NMIs, shown in the examples below.

Meter exemption details payload example

Copy

{ 
"meterExemption":
  {
           "exemptionDate": "2022-08-12",
            "endDate": "2022-09-06",
           "exemptionCategory": "MALFUNCTION"
           "exemptionType": "DEFECTIVE"
           "exemptionNature": "ACCESS"
           "actionTaken": "Issue logged with Telstra. Fix ETA 13/10/2022"
           "actionReason": "Checked communications"
        “conditions”: “XYZ”,
           "docProvided": "Y"    
  }
}

Meter exemptions NMIs JSON payload example

Copy

{ 
"meterExemptionNMIs": [
   {
      “action”: “NEW”
      "NMI": "1234567890",
      "planDate": "2022-08-06",
      "substitutionReq": "Y",
      "substitutionMethod": "01"
   }
      ]
}

Meter exemptions NMIs csv payload example

Copy

C,PRODUCTION,METER_EXEMPTION_NMI,POWERCOR,NEMMCO,2022/04/07,22:04:05,,,,NEM,0
I,MEN,ACTION,NMI,PLAN_DATE,SUBSTITUTION_REQ,SUBSTITUTION_METHOD
D,MEN,NEW,1234567890,2023/08/06,Y,01
C,END OF REPORT,4

Get meter exemption details

The new fields are included in the response when requesting metering exemption details by meterExemptionId, shown in the example below.

Copy

{
    "transactionId": "12345-abcd-27",
    "data": {
        "participantContact": {
            "contactName": "John Smith",
            "phoneNumber": "0123456789",
            "email": "john.smith@company.com"
        }
"meterExemption": {
            "meterExemptionid": "123456789012345",
            "participantId": "ENERGYCOMC",
            "startDate": "2026-08-06",
            "endDate": "2026-09-06",
            "status": "ACTIVE",
            "statusDate": "2026-08-06",
            "exemptionDate": "2026-08-12",
            "exemptionCategory": "MALFUNCTION"
            "exemptionType": "DEFECTIVE",
            "exemptionNature": "ACCESS",
            "actionTaken": "Issue logged with Telstra. Fix ETA 13/10/2026",
            "actionReason": "Checked communications",
            "conditions": "This exemption is conditional on receipt of a plan for 
    the rectification of the metering installation containing the     
    matters referred to in section 3.2 of the Exemption Procedure –   
    Metering Installation Malfunctions",
           "docProvided": "Y",
           "extendCount": "1"
        }
"meterExemptionHistory": [
            {
                "status": "MORE DATA",
                "statusDate": "2026-07-01",
                "conditions": "This exemption is conditional on receipt of a plan for 
    the rectification of the metering installation containing the     
    matters referred to in section 3.2 of the Exemption Procedure –   
    Metering Installation Malfunctions"
            }
        ]
"meterExemptionNMIs": [
            {
                "NMI": "1234567890",
                "status": "NEW",
                "planDate": "2026-08-06",
                "substitutionReq": "Y",
                "substitutionMethod": "01",
                "statusMessage": "XYZ"
            }
        ]
    }
}

6.7.4 Validation rules

AEMO validates all NMIs when processing the metering exemption request. The following table describes the validation and rejection reason.

Validation	Reason for rejection
Substitution method information is not provided	Substitute Required is selected but method is not provided
An exemption with More Info status is updated within 25 calendar days	The exemption is not updated in the required timeframe
Family Failure type exemption is sent for an extension	An extension is not allowed for this exemption type
Whole Current Connected NMI type exemption is sent for an extension	An extension is not allowed for this exemption type
Reject NMIs that recently had an exemption	NMIs assigned to a Family Failure exemption is included in another Family Failure exemption within the NMI duration validation period
Reject a NMI that recently had an exemption	A NMI assigned to a whole current connected NMI exemption is also included in another individual NMI exemption within the NMI duration validation period