1 Introduction
1.1 Audience
AEMO Australian Energy Market Operator provides this information as a service targeting business analysts and IT staff in Registered Participant See Relevant Rules or Procedures companies.
The primary audience is MCs and MDPs to identify meter data quality and quantity.
1.2 Objective
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. - Technical Specification - 31 May 2026 (Release) describes the projects planned by AEMO from a participant perspective and includes any system related changes for participants.
1.3 Status
|
Version |
Status |
|---|---|
|
0.03 |
In progress. The design is not ready for participants’ builds. |
|
0.02 |
In progress. The design is not ready for participants’ builds. |
|
0.01 |
Presents the MSATS - Technical Specification - May 2026 evolving design. Please send feedback to techwriters@aemo.com.au |
1.4 Release dates
Scheduled for implementation in:
- Pre-production AEMO’s test system available to participants: Tuesday 31 March 2026
- Production AEMO’s live system: Sunday 31 May 2026
1.5 Projects and enhancements
Changes and enhancements for this Release include:
|
No. |
Functionality |
Change |
Affected interface |
Reference |
|---|---|---|---|---|
|
1 |
eMDM |
New type 9 MITC |
n/a |
1.6 Rule and procedure changes
|
Title |
Status |
Effective |
|---|---|---|
|
Final |
31 May 2026 for Type 9 meters |
|
|
Draft |
31 May 2026 |
|
|
Draft |
31 May 2026 |
|
|
Draft |
31 May 2026 |
|
|
MSATS Procedures - Principles and Obligations for All Connection Points v8.0 |
Draft |
31 May 2026 |
|
Retail Electricity Market Procedures – Glossary and Framework v4.6 |
Draft |
31 May 2026 |
|
Draft |
31 May 2026 |
1.7 Related technical specifications
None
1.8 Related documents
These guides and resources are updated according to this technical specification and published for the pre-production Release Date.
|
Title |
Description |
Status |
|---|---|---|
|
Describes reports to help participants manage standing data and B2B transactions and metering data management |
Not started |
|
|
Describes the mapping between the MSATS 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. procedures and the B2B aseXML schema Specification to describe the structure of an aseXML message. |
Not started |
1.9 Related software
|
Software |
Change |
Available |
|---|---|---|
|
New version for Enumerations.xsd and ElectricityEnumerations.xsd file changes introduced in 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. schema r46 |
Pre-production:
|
|
1.10 Approval to change
No approval or agreement to change required from participant change controllers. AEMO is seeking approval in the 2025 Flexible Trading Arrangements consultation.
1.11 Market systems user group meetings
The Market Systems User Group (MSUG Market Systems User Group) is an industry user group established to discuss NEM wholesale and retail IT systems releases. Its purpose is to facilitate the continuing improvement of AEMO's IT systems by seeking feedback and collaboration from participants.
MSUG meetings are open to all interested parties, with invitations sent to all included on the distribution list. If you have a technical question for a project and want to attend the MSUG ask your company’s support team to include your email address in their AEMO Help Desk Bulletin (CRM) distribution list.
1.12 Version numbers
Incremental version numbers such as 1.01, 2.01 and so on mean there is a minor change to the technical specification.
Major version numbers such as 1.00, 2.00 means there are substantial changes to the technical specification. Participants must carefully review these changes, detailed Page 1.
1.13 Changes in this version
This version has the following changes:
-
Adds request for Participant implementation plans in Proposed Timeline.
-
Revises Participant testing dates in Proposed Timeline.
-
Adds FAQs from the MSUG meeting.
-
Adds B2B Validation Module to Related software.