5 B2B

5.1 B2B aseXML schema

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

This schema release r46 affects 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..

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

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

5.1.1 Schema changes summary

Affected files	New	Modified
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	n/a	Included file versions: Common Electricity Electricity Enumerations Transactions Service Order One Way Notification
Common_r46	n/a	HazardDescription – Increase maximum length from 80 to 100 characters
Electricity_r46	Additional enumerated values for SORDResponseCode to support MP-initiated Service Orders Responses for defects and One In All In to FRMPs: Appointment Required Comms Refused Coordination Failure Defect Demolished Dog Incorrect Service Order Mismatch with Standing Data Natural Event No Access - Network Support Required Not FRMP No Adult Present Obstruction Shared Fuse - Scoping Required Site Not Ready Unable To Isolate Unable To Locate Site New enumerated values for ServiceOrderSubType: Temporary Isolation - Scoping Request: For supporting FRMP-initiated Service Orders to the DNSP for a One In All In shared fusing scoping request Temporary Isolation One In All In: For supporting FRMP-initiated Service Orders to the DNSP for a One In All In shared fuse scoping request	The following values are updated to support the alignment of NEM B2M and B2B fields: FormNumber – Increase maximum length from 15 to 20 characters FormReference – Reduce maximum length from 30 to 20 characters
Electricity Enumerations	Enumerations for the LMRP and One In All In process: RegClassification PurposeOfRequest SORDResponseCode Adds Remediation Advised to the enumerated list for PurposeOfRequest element, to support FRMP initiating Metering Service Works Service Orders Requests for defects to MPs Adds One In All In to the enumerated list for ReasonForNotice element, to support DNSP initiated Meter Fault And Issue Notification One Way Notifications for shared fuse outages to an FRMP	n/a

5.2 B2B browser

In the r46 aseXML schema , the maxoccurs=2 attribute remains in BuildingOrPropertyName for using 2 instances from 26 October to 30 November 2025. From 1 December 2025, BuildingOrPropertyName and BuildingOrPropertyName2 must be used to represent primary and secondary complex names.

The 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. changes include:

Updates to B2B transaction create, view, and edit interfaces to include enumerated values.
New create, view, and edit interfaces to support Service Order A request to perform specified work, see B2B Procedures: Service Order Process. transaction with new Sub Types.

5.3 B2B transactions

Enhancement	Transaction	Description
Site defects	Metering Service Works	In the B2B Browser interface, a FRMP can set Purpose Of Request to Defect Resolved to notify the MP the customer has advised the defect is resolved Updates to B2B Validation Module and ElectricityEnumerations.xsd in B2M schema to include Defect Resolved
Site defects	Service Order Response	In the B2B Browser, an MP can set numerous SORDResponseCode to cover One In All In exemptions B2B Validation Module adds Defect to the list for SORDResponseCode Adds Defect to the SORDResponseCode enumerated list in the Electricity_r44.xsd
Shared fuse meter replacement LMRP	Service Order Request	FRMP can initiate Temporary Isolation - Scoping Request Service Orders for shared fusing to DNSP. FRMP initiated Temporary Isolation – One In All In Request Service Orders and Install Meter Isolation Device for shared fuse to DNSP Metering Service Works subtype Install Meter Isolation Device
Shared fuse meter replacement	One Way Notification	DNSP can initiate Meter Fault And Issue Notification to FRMP for shared fuse outage

B2B transactions has changes to support the site defects process.

5.4 B2B validation module

The B2B Validation A process to test the veracity and integrity of metering data. Module provides the following validations:

LMRP Legacy Meter Replacement Plan and One In All In are permitted values for RegClassification
Remediation Advised is a permitted value for PurposeOfRequest
Permitted values for SORDResponseCode:
Appointment An agreement between a retail customer (or their agent), a retailer and a participant for the participant to perform requested work at a specified time. Required
Comms Refused
Coordination Failure
Defect
Demolished
Dog
Incorrect Service Order
Mismatch with Standing Data
Natural Event
No Access - Network Support Required
Not 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.
No Adult Present
Obstruction
Shared Fuse - Scoping Required
Site The physical location of the connection point, see B2B Procedures: Customer and Site Details and Service Orders Process. Not Ready
Unable To Isolate
Unable To Locate Site

One In All In is a permitted value for ReasonForNotice
New validation rules when MCs update the Site Defect flag