aseXML FAQs

If your B2M Business-to-Market aseXML schema Specification to describe the structure of an aseXML message. preference is Latest The participant is set up to receive both current and next projected future version of aseXML-compliant files., you must be ready to transition with AEMO Australian Energy Market Operator. If you are not ready to transition:

  1. Change your schema preference to Current before the Release Dates.
  2. When AEMO transitions we move you to the Superseded preference.
  3. 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.
  4. Change your schema preference to Current.

See B2B schema transition timing

See Schema versions.

Yes, if you want to use the functionality in the new schema version. The technical specification details the new functionality.

Otherwise you can ignore the upgrade remembering AEMO only support the Latest and Superseded The participant can receive files compliant to the The participant can receive files compliant to the superseded aseXML version, and needs to change over their receiving system before the next aseXML version release. versions.

Dates and information about schema changes are communicated in technical specifications.

See Understanding receiving status.

AEMO only supports one current and one superseded version of the B2M 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. 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. schemas.

See What happens during a B2B schema change?.

No transforms are available or applied between the B2M and B2B schemas

B2B transforms only occur between the current and superseded versions. For example, if the current B2B schema is r41 and you are on the superseded B2B schema r38 then transforms are available. If you are on a non-supported version of the B2B schema then no transforms are available and the transaction is delivered in the version it was sent.

r_any is not a schema version. Selecting this status means you receive files in the version they were sent with no transformation.