March 2026 · 12 min read · Written for settlement managers, compliance directors and operations leads at UK electricity suppliers
The Market-wide Half Hourly Settlement migration is underway. What is less well understood by many operational teams is that migration and qualification are not the same thing — and that the consequences of failing to qualify by 28 October 2026 are immediate, commercial, and irreversible until the issue is resolved.
MHHS qualification is the formal process through which every electricity supplier in Great Britain must demonstrate to the Code Bodies — Elexon under the Balancing and Settlement Code (BSC) and the Retail Energy Code (REC) — that their systems, processes, operational controls, and governance frameworks are capable of operating under the new half-hourly settlement arrangements.
Migration — the process of moving your MPAN portfolio from non-half-hourly to half-hourly settlement — cannot proceed at scale until qualification is complete. And if qualification is not achieved by Milestone 14 on 28 October 2026, the BSC will suspend your ability to register new MPANs in the Central Switching Service. You will not be able to take on new customers until you are qualified.
Milestone 14 is set for 28 October 2026. Suppliers that have not qualified by this date will be suspended from completing registrations in the Central Switching Service — meaning no new customers until compliance is achieved. There is no extension mechanism.
This article explains what MHHS qualification actually involves operationally, what the testing and evidence requirements are, what the M14 consequences mean in practice, and what your operations team needs to have in place. It is written for the people carrying the operational weight of this programme — settlement managers, compliance leads, and operations directors.
Qualification and Migration Are Different Things — and the Distinction Matters
This is the most important clarification to make at the outset. Many suppliers are focused on their MPAN migration programme — the process of transitioning individual meter points to half-hourly settlement arrangements. Migration is visible, measurable, and tracked through the Migration Control Centre.
Qualification is the prior step. It is the regulatory process that certifies your organisation is capable of operating within the MHHS Target Operating Model before you migrate at scale. You cannot proceed with MPAN migration in the new arrangements until your organisation has been through qualification testing, submitted the Qualification Assessment Document, had it approved by the Code Bodies, and completed Service Activation.
Suppliers who participated in the first wave of MHHS migration — those who began moving MPANs from 22 October 2025 as part of Milestones 11 and 12 — had already completed Systems Integration Testing and were qualified to do so. The suppliers working through the qualification process now are those in subsequent waves, using the Non-SIT Qualification Testing route.
By Milestone 14 in October 2026, all market participants that have completed qualification will be authorised to operate under MHHS arrangements. Current plans indicate approximately 80 per cent of meters will have migrated by October 2026. — Elexon, February 2026
That means 20 per cent of meters will still be migrating as M14 arrives. For the suppliers responsible for those meters, the qualification status of their organisation determines whether they can continue trading normally or face the M14 sanctions. Understanding where your organisation sits in the qualification process is not a programme management question. It is a commercial risk question.
The Two Routes to MHHS Qualification
All suppliers must achieve MHHS qualification, but the route depends on the wave the supplier was allocated to and whether they participated in the Programme’s Systems Integration Testing.
Route 1: Systems Integration Testing (SIT)
SIT was the primary qualification route for larger suppliers and early cohorts. SIT participants worked directly with the MHHS Programme to complete functional, non-functional, migration and operational testing across the full MHHS architecture. Those suppliers who completed SIT successfully were qualified to begin MPAN migration in October 2025.
Route 2: Qualification Testing (Non-SIT)
Non-SIT qualification is the route for the remaining suppliers, agents, and new entrant LDSOs. It follows a structured process managed independently through Qualification Testing waves. The Qualification Testing execution window ran from 22 August 2025 through to 9 January 2026, and the Final QAD submission window ran from 25 August 2025 through to 16 January 2026.
Suppliers who have not yet submitted their Final QAD, or whose QAD is still under review by the Code Bodies, are in a critical position relative to the October 2026 deadline. The Code Body review process is not instantaneous — submissions require assessment, clarification rounds, and in some cases resubmission before approval is granted.
If your Final QAD submission has not yet been approved, you should be treating this as an operational priority, not a programme task. The time available between now and M14 is significantly shorter than it appears.
What the Qualification Assessment Document Actually Requires
The Qualification Assessment Document is the central mechanism through which all suppliers provide evidence of readiness to the Code Bodies. It must be completed at an organisation level, covering every market role the supplier intends to operate within MHHS. Both BSC and REC Code Bodies must approve the QAD — and they assess it through different lenses, meaning a response that satisfies one body may still require clarification from the other.
The QAD is submitted in two stages:
Initial QAD Submission
The Initial QAD covers preparatory evidence that does not depend on completed testing. It must include:
- Confirmation of Pre-Integration Testing completion, including a test completion report and any defect work-off plans agreed with Code Bodies
- Service designs and Local Work Instructions covering each relevant operational process
- Evidence of operational readiness including exception management procedures and controls
- Data Integration Platform onboarding evidence and information security responses reviewed and agreed by the DIP Manager
- Organisation-specific information requested in the submission template
Final QAD Submission
The Final QAD must be completed after Qualification Testing and covers:
- Confirmation of QT or SIT completion, including a test completion report and agreed work-off plans for any remaining defects
- Confirmation that all DIP User requirements have been met and contractual agreements with the DIP Manager are signed
- Verification of all sections covered in the Initial submission
- Sign-off by a Company Director confirming that all information provided is accurate and complete
The director sign-off requirement is significant. It means qualification is not purely a technical matter — it requires a director-level commitment to the accuracy of everything submitted. For suppliers where the QAD spans multiple systems, agent relationships, and operational processes, ensuring that commitment is justified requires thorough internal review before sign-off.
The Operational Evidence That Code Bodies Are Looking For
The Code Bodies are not simply checking whether your systems work. They are assessing whether your controls and governance are sufficient to manage those systems reliably within the MHHS operating environment. Key areas of operational evidence include:
- Market message management controls — evidence that messages are processed within the required 60-minute window, including controls in systems connecting directly to the DIP and any middleware such as DIP adapters
- Exception management procedures — documented procedures demonstrating how exception management operates in practice, including escalation triggers and resolution timescales, not high-level descriptions
- Service designs and Local Work Instructions — process documentation covering all MHHS market roles, reflecting actual processes your team will follow rather than aspirational descriptions
- Supplier agent oversight controls — if your model involves agents for data services or metering, documentation of how you monitor agent performance and enforce compliance with MHHS timescales
- Complete system architecture documentation — your full architecture including any DCP involvement, with each QAD submission standing alone without referencing other participants’ submissions
The Code Bodies use different assessment lenses for BSC and REC obligations. A response that satisfies one may still require clarification from the other. Build time for this into your submission timeline.
The MHHS Milestone Timeline: Where the Programme Stands Now
Understanding the full milestone sequence puts the October 2026 qualification deadline in context. The period between now and M14 is the most operationally compressed phase of the entire programme.
| Milestone / Date | Operational Meaning |
| Sept 2025 M10 | Central MHHS systems go live. Elexon’s new settlement infrastructure ready to receive half-hourly data. First SIT-qualified suppliers cleared to begin MPAN migration. |
| Oct 2025 M11 / M12 | 18-month MPAN migration window opens. SIT-qualified suppliers begin migrating Advanced Metered and Unmetered Supply MPANs. Migration Control Centre becomes operational. |
| Oct 2025 M13 | Load Shaping System switched on. Required for accurate consumption allocation for non-smart meter points under MHHS arrangements. |
| 28 Oct 2026 M14 — CRITICAL DEADLINE | ALL suppliers must be MHHS Qualified and Service Active. Unqualified suppliers are suspended from registering new MPANs in the Central Switching Service. Reverse migration ceases permanently. |
| 7 May 2027 M15 | All MPANs must be migrated into MHHS arrangements. Market completion assessed against M15 Acceptance Criteria. Legacy settlement systems begin wind-down. |
| July 2027 M16 | Settlement Timetable Transition. Market cuts over from 14-month legacy timetable to new 4-month settlement window. Elexon processing up to 500 billion half-hourly readings per year. |
The most significant long-term operational change is M16: the compression of the settlement timetable from 14 months to four months. The 14-month window that currently provides buffer for retrospective corrections closes permanently at M16. Exception management, data flow accuracy and settlement monitoring must be embedded into daily operations before then — not developed reactively afterwards.
What M14 Non-Compliance Actually Means in Practice
The sanctions for failing to achieve MHHS qualification by M14 are set out in BSC Section C under BSC Modification P487, and in Annex 4 of the Qualification Approach and Plan. They are specific, immediate, and apply at the Party ID level.
Suspension from the Central Switching Service
A supplier that has not qualified by M14 will be suspended from completing registrations in the Central Switching Service. This applies to both MHHS and legacy NHH registrations — the supplier cannot register new MPANs in either arrangement. In practice, the business cannot sign up new electricity customers.
The Suspension Applies to All MPIDs Under Your Party ID
The consequences apply at the Party ID level. If any MPIDs registered to a Party ID that is not MHHS qualified remain live or de-energised at M14, the entire Party ID faces the CSS suspension. This is important for suppliers with complex corporate structures or multiple operating entities.
Legacy MPIDs Must Be Exited or Surrendered Before M14
Suppliers with Legacy MPIDs they do not intend to qualify under MHHS must exit or surrender those MPIDs before M14. If a surrender is related to a wider system or process change, disclosure to the BSC under the Material Change and Triggers for re-Qualification Guidance Note is also required. Failure to action this means Annex 4 applies and the CSS suspension follows.
No Automatic Extensions
Ofgem and the Code Bodies have confirmed there are no further extensions to the M14 milestone. The qualification deadline was already extended by 7.5 months through CR055 in late 2024 — from March 2026 to October 2026. That extension is already in the current timeline. There is no further flexibility.
Suppliers that cannot evidence qualification readiness by M14 face a hard commercial stop — no new customer registrations — until the qualification process is completed and approved. This is a revenue impact, not a compliance process issue.
The Operational Readiness Checklist: What Your Team Needs in Place
For settlement, compliance and operations teams assessing their current position relative to M14, the following checklist reflects the core operational requirements that the qualification process tests.
Systems and Technical Readiness
- your systems can receive, validate and process HH consumption data from smart and advanced meters within required submission windows — Half-hourly data flows are operational
- DIP onboarding is complete, information security responses have been reviewed and agreed, and contractual agreements with the DIP Manager are signed — DIP connectivity is established
- controls are in place in your systems and any DIP adapter middleware to ensure messages are processed within MHHS timescales — Market message processing meets the 60-minute requirement
- your QAD covers your full architecture, including any DCP involvement, without referencing other participants’ submissions — Complete system architecture is documented
Process and Governance Readiness
- documentation covers all MHHS market roles your organisation operates and reflects actual processes — Service designs and Local Work Instructions are completed and current
- your team has defined escalation triggers, resolution timescales and prioritisation frameworks for MHHS data flow exceptions — Exception management procedures are documented and operational
- if your model involves agents for data services or metering, documented controls demonstrate how you monitor and ensure agent compliance with MHHS timescales — Supplier agent oversight controls are in place
- PIT has been completed and a test completion report is available, including any defect work-off plans agreed with the Code Bodies — Pre-Integration Testing is complete
QAD Submission Status
- if clarifications were requested, responses have been provided and confirmed as satisfactory — Initial QAD has been submitted and Code Body feedback addressed
- QT has been completed with a signed-off test completion report and agreed work-off plans for any remaining defects — Qualification Testing is complete
- the complete Final QAD submission is either submitted or in the final stages of preparation — Final QAD has been submitted
- a Company Director has reviewed the Final QAD and is prepared to confirm that all information is accurate and complete — Director sign-off is secured or in progress
- the steps required for Service Activation following QAD approval are understood and resourced — Service Activation is planned
If your answers to the QAD submission questions are anything other than confirmed completed, your M14 risk exposure is material. The Code Body review process takes time — and the time available between now and 28 October 2026 is measurable in months, not quarters.
What Changes Operationally After Qualification
Completing MHHS qualification is not the end of the operational challenge — it is the beginning of operating at scale in the new settlement regime.
Half-Hourly Data Volumes Increase Dramatically
At full migration, Elexon will be processing up to 500 billion half-hourly readings per year. For individual suppliers, exception handling volumes, flow monitoring requirements and data validation workloads all increase significantly relative to today’s non-half-hourly operations.
The Settlement Window Compresses at M16
The transition to the four-month settlement timetable at M16 removes the buffer that operational teams currently rely on for retrospective correction. A data flow rejection or registration error that is currently manageable over a 14-month correction window becomes more financially significant when that window compresses to four months.
Reverse Migration Ceases at M14
From M14 onwards, MPANs cannot be moved back into the non-half-hourly regime on change of supplier. If a customer changes supplier after M14, the new supplier receives that MPAN in the MHHS arrangements. There is no unwinding mechanism.
Exception Management Must Be Structured, Not Reactive
The combination of higher data volumes, a compressed settlement window, and no reverse migration option means that exception management must be structurally embedded in operations. Partial flow failures that persist undetected for weeks under the current model become compounding settlement exposure under the four-month timetable.
How Optiflow Utilities Supports MHHS Qualification and Ongoing Operations
Optiflow Utilities is an AI agentic platform built for UK energy suppliers managing the operational complexity of MHHS migration, qualification readiness and post-qualification settlement governance.
For suppliers in the qualification process, Optiflow provides:
- Real-time monitoring of data flow submission and acceptance rates across your MPAN portfolio, surfacing exception patterns before they affect your QAD evidence or testing outcomes
- Structured exception management with automated classification by settlement criticality, reducing manual triage burden during the qualification testing period
- Audit trail generation and compliance reporting that supports QAD evidence requirements and Ofgem regulatory documentation
- Settlement divergence alerts that identify reconciliation exposure before it materialises in settlement adjustments
For suppliers managing ongoing operations after qualification, Optiflow provides the operational intelligence infrastructure needed to run efficiently inside the new MHHS regime — with the exception management capacity and settlement monitoring capability that the four-month settlement window demands.
Talk to the Optiflow team about MHHS qualification support. support@optiflowtechnologies.io
Read more: Optiflow Utilities — AI Platform for MHHS, Billing and Settlement | optiflowtechnologies.io/optiflow-utilities
Optiflow Technologies · optiflowtechnologies.io · March 2026