MSATS - aseXML B2B schema r48 - November 2026

Audience

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. Retail Market Participants along with business analysts and IT staff.

Contents

Summary

• What’s changing
  • New B2B aseXML schema version r48
  • B2B only – no changes to B2M schema
• Why
  • Supports Flexible Trading Arrangements (FTA)
• Key dates
  • Draft schema: 17 April 2026
  • Participant approval due: 4 May 2026
  • Pre‑production: 1 September 2026
  • Production: 1 November 2026
• Effective dates for schema population
  • FTA changes: 1 November 2026
• Schema See aseXML Schema. changes (r46 → r48)

  • aseXML_r48.xsd

    • Updated schema version/namespace to r48 and references included r48 files (rename/version uplift).

  • Common_r48.xsd

    • Adds new simple types/elements:

      • ChangeRequestFieldName (string, maxLength 64)

      • ChangeRequestValueRequired (string, maxLength 240)

  • Electricity_r48.xsd

    • Adds new ServiceOrderType: Update Standing Data

    • Adds new ServiceOrderSubType: Commission Meter

    • Adds new elements to support standing data updates and Allocate-NMI scenarios:

      • ChangeRequestFieldName, ChangeRequestValueRequired, EffectiveDate

      • PremisesNMIWithChecksum (uses existing NMI type)

      • NMIClassificationRequired (uses existing NMIClassificationCode type)

    • Adds new SORDResponseCode values for FTA-related rejections:

      • Device Not Supported, MSATS Exception, Service Not Supported, Unable to Commission Meter

  • ElectricityEnumerations.xsd

    • Adds new PurposeOfRequest enumeration values:

      • Customer Requested

      • Service Not Required

    • Updates version attributes of key service order structures to r48 (for example, ElectricityServiceOrderType, ElectricityServiceOrderDetails, ElectricityServiceOrderNotificationData).

  • Events_r48.xsd

    • Registers ReleaseIdentifier r48 and renames file to r48.

• Participant impact
  • LATEST r46 → LATEST r48
  • CURRENT r48 → SUPERSEDED r46
  • Upgrade required to receive new fields
• What participants need to do
  • View schema changes
  • Assess system impacts
  • Upgrade systems to support r48
  • Test in pre‑production before go‑live