Changes to Supply Number Format for MHHS (Alternative)
Date of latest update
Type
Change
ID
R0083A
Priority
Urgent
No
Latest Update
17/11/2023 - The Authority has rejected R0083A, but has approved R0083 for implementation on MHHS M8 *This Change Proposal is a consequential change from the Market-wide Half Hourly Settlement programme
Summary
The Electricity Supply License requires Suppliers to provide the Supply Number to each Consumer on every bill, or at least once per year where no bill has been sent. The Supply Number format is prescribed by the REC and is detailed in the Energy Market Data Specification. The MHHS design is changing the data associated with each individual metering point, including those data items currently displayed within the Supply Number top line. This is an Alternative Change Proposal to R0083, which proposes to replace the format of the top line in the Supply Number Format. This Change Proposal proposes to remove the top line completely from the S Number format. Both solutions are being progressed together to allow for a clear assessment of the benefits and drawbacks and impacts to consumers.
Original CP
Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As an electricity Consumer I want to be able to provide my prospective Energy Supplier with the necessary information for them to provide a suitable tariff. As a Non-Domestic Consumer, I want to have the necessary information that will allow me to access tariff information, specific to my business, to help me manage my energy. As an electricity Consumer, I want to have access to the data that will help me appoint my own Metering Equipment Manager (MEM) where permitted.
- As a Supplier, I want to know how to populate and format the Supply Number, so that I can meet my obligations to include it in Consumer bills or statements. As a Third Party Intermediary (TPI), I want Consumers to be able to provide me with the right information to provide appropriate quotes.
- As an independent Distribution Network Operator, I want to be able to identify and use the DUoS Tariff Id so that I can provide transparency on charging that is being applied to my customers. As the Electricity Enquiry Service (EES) Provider, I want to know how to populate the Supply Number so that I can make it available on the EES
Problem Statement
The Market-wide Half Hourly Settlement design is impacting the Data Items that are used in the top line of the Supply Number, which Energy Suppliers are obliged to provide to Consumers at least once a year under their Licence. A revised definition of the Supply Number format is required so that Electricity Suppliers have a clear understanding of the approach to populating the Supply Number for metering points that have migrated to the new MHHS arrangements.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0083A - Change Proposal Form 05.12.2022
Decision to Reject Change Proposal R0083A - Change to Supply Number Format Alternate
Company Name
-
Review status
Review required
Formalising the Submission of PPMIP Unallocated Transaction Report (UTR) Files
Date of latest update
Type
Change
ID
R0082
Change Category
Change Path
Priority
Urgent
No
Latest Update
09/04/2024 - Due to the MHHS impact on Service Providers, the technical code freeze and any MHHS impacts on the proposed solution, the Code Manager has reconsidered the priority of R0082 and believes that should be progressed following MHHS go-live. This Change Proposal has been withdrawn, and the Code Manager will consider raising a new change at the appropriate time following MHHS with consideration of the Codes Roadmap.
Summary
This CP seeks to address the following issues regarding the Unallocated Transaction Report (UTR) files provided by PPMIPs to the Code Manager each month: 1. There is no REC requirement for PPMIPs to submit a monthly file to the Code Manager 2. PPMIPs are currently submitting files in two different file formats 3. C&C is only able to load one of the two file formats The CP has been raised to introduce a requirement in the REC for PPMIPs to provide monthly Unallocated Transaction Report (UTR) files to the Code Manager in a single file format, set out in the REC Data Specification. With this format being one that can be loaded by C&C.
Change Plan
Solution analysis and development
Completed
Start:
28 Nov 2022Due:
12 Jan 2024Completion:
11 Jan 2024Service Provider Impact Assessment start date
Completed
Start:
12 Jan 2024Due:
15 Jan 2024Completion:
15 Jan 2024Service Provider Impact Assessment close
Completed
Start:
15 Jan 2024Due:
11 Mar 2024Completion:
11 Mar 2024Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a PPMIP, I want to have clear guidance on how and when I should submit my Unallocated Transaction Report files.
- As a Supplier, I want to receive accurate Unallocated Transactions in relation to prepayment meters that are not smart meters.
- As the Code Manager, I want visibility of the Unallocated Transaction Report.
- As the EES Provider, I want to be able to efficiently upload the Unallocated Transaction Reports.
Problem Statement
PPMIPs aren’t submitting UTR files in the same format, and one of these formats cannot be loaded by the EES Provider. There is also no obligation in the REC for these reports to be provided.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
rosalind.timperley
R0082 - Change Proposal Form
R0082 - Change Proposal Plan (Approved) 17.10.2023
R0082 Initial Assessment Report (Approved) 17.10.2023
Company Name
REC Code Manager
Review status
Review required
CSS Market Message Retry Strategy
Date of latest update
Type
Change
ID
R0081
Priority
Urgent
No
Latest Update
15/11/2023 - Change Proposal has been withdrawn. Market message success data for September 2023 was reviewed to ensure that a stable period was analysed which represented ‘normal’ conditions. Upon completion of the review, it has been concluded that the success of the current retry strategy has significantly improved since this change proposal was raised. The Code Manager will introduce cyclical reviews of performance to ensure this continues at the expected levels.
Summary
The prescriptive nature of the Market Message retry drafting is currently impeding on the CSS Service Provider’s ability to ensure all Market Messages are sent and received successfully between the CSS and the CSS User. This CP proposes a move to a principles-based obligation that allows for flexibility to ensure the CSS and CSS User are able to attempt retries but not have to follow specific timings or have a maximum number of retries.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0081 - Change Proposal Form
Proposed legal text submitted with the CP
Company Name
-
Review status
Review required
Improvements to ‘Failed to Deliver’ CSS Messages
Date of latest update
Type
Change
ID
R0080
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal has been implemented as part of the REC Release on 27 June 2025.
Summary
Since CSS Go-Live a large number of messages have not been successfully delivered due to failures of CSS User's gateways, resulting in CSS exhausting the 12-hour retry period. This Change Proposal has been raised to explore and address this issue
Change Plan
Service Provider Impact Assessment close
Completed
Start:
09 Nov 2022Due:
25 Jan 2024Completion:
25 Jan 2024Party Impact Assessment trigger
Completed
Start:
25 Jan 2024Due:
02 Feb 2024Completion:
02 Feb 2024Party Impact Assessment close
Completed
Start:
02 Feb 2024Due:
23 Feb 2024Completion:
23 Feb 2024Preliminary Change Report and Consultation issued
Completed
Start:
23 Feb 2024Due:
10 May 2024Completion:
10 May 2024Consultation close
Completed
Start:
10 May 2024Due:
03 Jun 2024Completion:
03 Jun 2024Responsible Committee Decision
Completed
Start:
24 Jul 2024Due:
31 Jul 2024Completion:
31 Jul 2024Final Change Report Issued
Completed
Start:
03 Jun 2024Due:
24 Jul 2024Completion:
19 Jul 2024Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
27 June 2025
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer, I want the Switching process to work successfully, so that I can switch Energy Supplier without delays or issues.
- As the CSS Provider I want the messages I send to CSS Users to be received and processed successfully, so that there is no interruption to the Switching process or the Consumers’ Switching experience.
- As the CSS User I want to receive CSS messages in a timely manner following any outage of my own gateway or systems, so that there is no interruption to the Switching process or the Consumers’ Switching experience.
Proposed Solution Document
Document title
R0080 - Solution Development Report 11.01.2024
Archive
Off
Document title
CSS Interface Design Specification v8.9.0 R0080 - REDLINE
Archive
Off
Document title
CSS Failed To Deliver Detailed Design (R0080) v1.3 (19.06.2024)
Archive
Off
Document title
Business Data Validation Rules v1.5.0 R0080 - REDLINE
Archive
Off
Document title
Schedule 24_Switching Data Management v1.2_R0080 Draft (19.06.2024)
Archive
Off
Problem Statement
Following an unexpected or extended period of gateway outage for a CSS User, there is currently no automated process to resend any CSS messages from the CSS Provider that were triggered during the period of outage. This results in the CSS Provider needing to manually correct any issues, which is time consuming and may affect Consumer Switches due to delays in messages being processed.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
SME Role
Lead Assurance Analyst
R0080 - Change Proposal form
R0080 Onboarding document
R0080 - Change Proposal Plan (Approved) 16.01.2024
R0080 - Rebaselined Change Plan (26.04.2024)
R0080 - Initial Assessment Report (Approved) 16.01.2024
R0080 Consolidated Party IA Responses v1.0 (10.05.2024)
R0080 - Preliminary Change Report v1.0 (Published for Consultation) 10.05.2024
R0080 Consolidated Consultation Responses (19.06.2024)
R0080 - Final Change Report v2.0 (Approved) 31.07.2024
Company Name
-
Review status
Review required
DNOs notifying Suppliers about Crossed Meters
Date of latest update
Type
Change
ID
R0076
Priority
Urgent
No
Latest Update
28/05/2024 - R0076 has been withdrawn as the issue was addressed through R0121 - SDEP Review Improvements (1) - Process Types. The adoption window is closed.
Summary
The Change seeks to introduce a way for the DNOs to raise a crossed meter issue with the Supplier, in a way that directly feeds into the Supplier’s list of crossed meter issues. The supplier will be required to feed back progress to the DNO who has raised the issue with them, this should be defined as a process within the REC.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0076 - Change Proposal Form v1.0
Company Name
-
Review status
Review required
Introduction of a new Meter Asset Condition Code
Date of latest update
Type
Change
ID
R0072
Other Industry Codes impacted
Priority
Urgent
No
Latest Update
19/09/2024 - Change Proposal R0072 has been rejected and raised to Ofgem to consider. Despite earlier acceptance, the Code Manager believes that the proposal is not relevant to the REC and cannot progress any further.
Summary
This change seeks to introduce a new Asset Condition Code where further investigation is required by a Distribution Network Operator, where is there suspected asbestos in the metal encased cut-out
Impacted Consumers
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0072 - Change Proposal Form
Company Name
Consumer
Review status
Review required
Provision of Enduring Test Environments
Date of latest update
Type
Change
ID
R0070
Change Category
Change Path
Priority
Urgent
No
Latest Update
28/06/2024 - Change implemented as part of the June 2024 REC Release
Summary
Currently the REC does not require the Central Switching Service (CSS) and Switching Operator (SO) to provide the enduring test environments and test data for use by REC Parties when making necessary system changes for REC Change Proposals or internal system updates. This Change Proposal has been raised to introduce these obligations in to the REC.
Change Plan
Solution Analysis and Development
Completed
Start:
09 Sep 2022Due:
06 Jun 2023Completion:
06 Jun 2023Service Provider Impact Assessment Period
Completed
Start:
06 Jun 2023Due:
06 Oct 2023Completion:
06 Oct 2023Service Provider Impact Assessment
Completed
Start:
24 Nov 2023Due:
03 Jan 2024Completion:
03 Jan 2024Party Impact Assessment Issued
Completed
Start:
06 Oct 2023Due:
24 Nov 2023Completion:
24 Nov 2023Preliminary Change Report Issued
Completed
Start:
03 Jan 2024Due:
16 Jan 2024Completion:
16 Jan 2024Responsible Committee Review
Completed
Start:
16 Jan 2024Due:
23 Jan 2024Completion:
23 Jan 2024Consultation Issued
Completed
Start:
23 Jan 2024Due:
26 Jan 2024Completion:
26 Jan 2024Final Change Report Issued
Completed
Start:
26 Jan 2024Due:
23 Feb 2024Completion:
23 Feb 2024Responsible Committee Decision
Completed
Start:
23 Feb 2024Due:
05 Mar 2024Completion:
05 Mar 2024Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
28 June 2024
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a CSS User I want access to a CSS Test Environment, to enable me to test my systems and processes ahead of the implementation of complex or significant changes, so that I can identify any issues prior to go-live.
- As the SO, I want clarity on the obligations placed on me regarding the provision and maintenance of CSS Test Environments and data, so that I can meet my obligations and provide CSS Users and Service Providers with access to appropriate Test Environments.
- As a Switching Data Service Provider (SDSP), I want clarity on the obligations placed on me regarding the provision and maintenance of Test Environments and data, so that I can meet my obligations to test CSS changes. As a Switching Data Service Provider (SDSP), I want access to a CSS Test Environment, to enable me to test my systems and processes ahead of the implementation of complex or significant changes, so that I can identify any issues and address prior to go-live.
Proposed Solution Document
Document title
R0070 legal text v1.0 - Published with Impact Assessment
Archive
Off
Document title
R0070 Legal Text v2.0 - Published with Preliminary Change Report
Archive
Off
Document title
R0070 - Legal Text v3.0 - Approved for Implementation
Archive
Off
Document title
REC Category 3 - Environment Management Plan
Archive
Off
Document title
REC Category 3 Test Data Management Plan
Archive
Off
Problem Statement
For specific types of changes, industry system testing will be required to ensure the end-to-end Switching processes will work as expected following implementation. If Test Environments and Test Data are not available, CSS Users will not be able to complete testing to confirm their systems will operate correctly in the live environment. The REC currently doesn’t define specific obligations on Service Providers regarding enduring test systems and Test Data for Switching processes. The lack of specific obligations may impact the availability of appropriate Test Environments. This could impact the progression of improvements to Switching processes that require a technical change.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
beth.brown@capgemini.com
R0070 Initial Assessment Report v1.0 (Approved)
R0070 - Preliminary Change Report (Approved 23.01.2024)
R0070 - Change Proposal Plan v2.0 (Approved)
R0070 - Change Proposal Form
R0070 - Consolidated Impact Assessment Responses
R0070 - Consolidated Consultation Responses
R0070 - Final Change Report V2.0 (Post-Vote) 05.03.2024
Company Name
-
Review status
Review required
Resolution of invalid CSS data by Data Owners
Date of latest update
Type
Change
ID
R0061
Change Category
Other Industry Codes impacted
Change Path
Priority
Urgent
No
Latest Update
04 March 2024 - Change has been withdrawn following implementation of a solution outside of the REC Change Process. 10WD window to adopt change will close on 18 March 2024.
Summary
Data is sent via the Supplier or MEM to update MPRS, which is then sent to CSS. If the data is considered invalid at CSS, an error is returned to MPRS. MPRS is the conduit of data from the Suppliers & MEMs to CSS, and ERDAs are not responsible for the data, therefore only the supplier/MEM can correct the data. The incidents must be put on hold until the owner of the data corrects the issue, this is to prevent SLA breaches. SLAs does not apply to the Supplier/MEM explicitly, so the incidents remain in the DNOs/IDNOs queue with the need to chase every few days to prevent the incident being closed. The responsibility for the incidents should be on the data owners (Suppliers/MEMs).
Change Plan
Solution Analysis and Development
Completed
Start:
22 Aug 2022Due:
15 Aug 2023Completion:
15 Aug 2023Service Provider Impact Assessment Due
Completed
Start:
15 Aug 2023Due:
19 Oct 2023Completion:
19 Oct 2023Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer, I want data relating to my energy supply to be accurate, so that I can have a consistent and faultless switching experience. As a Consumer, I want any data issues related to my switch to be resolved quickly and by the party responsible, to ensure a fast and efficient switching experience.
- As a DNO, I want my service level requirements to be reflective of my data ownership responsibilities, so that data queries can be resolved more efficiently. As the CSS Service Desk provider, I want my tickets to be allocated to the most appropriate party able to resolve them.
Proposed Solution Document
Document title
R0061 Solution - Service Desk Guidance Article
Archive
Off
Problem Statement
DNO/iDNOs are obligated to resolve data mismatches identified by the CSS during the switch process. However, they are unable to do so in cases where the Supplier/MEM owns data required to resolve the mismatch. Tickets assigned to the DNO (via MPRS) are therefore not going to the party best placed to resolve them, resulting in DNOs chasing the incident resolution every few days to prevent them being closed incorrectly.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0061 - Change Proposal Form
R0061 - Initial Assessment Report v1.0 (Approved) - 18.07.2023
R0061 - Change Proposal Plan v1.0 (Approved) - 18.07.2023
R0061 Change Proposal Re-Plan (Approved) v1.0 - 19.10.23
Company Name
St Clements Services
Review status
Review required
Maintenance of Qualification Schedule Change
Date of latest update
Type
Change
ID
R0059
Change Category
Change Path
Priority
Urgent
No
Latest Update
03/11/23 - This change was implemented on 03 November 2023 as part of the November 2023 REC Release
Summary
This change seeks to clarify, strengthen and simplify a number of requirements within REC Schedule 9 – Qualification and Maintenance.
Change Plan
Solution Development
Completed
Start:
05 Aug 2022Due:
01 Mar 2023Completion:
01 Mar 2023Impact Assessment Start
Completed
Start:
01 Mar 2023Due:
10 Mar 2023Completion:
10 Mar 2023Impact Assessment End
Completed
Start:
10 Mar 2023Due:
24 Mar 2023Completion:
24 Mar 2023Preliminary Change Report Issued
Completed
Start:
24 Mar 2023Due:
14 Apr 2023Completion:
14 Apr 2023Responsible Committee Review
Completed
Start:
14 Apr 2023Due:
25 Apr 2023Completion:
25 Apr 2023Consultation Start
Completed
Start:
25 Apr 2023Due:
28 Apr 2023Completion:
28 Apr 2023Consultation End
Completed
Start:
28 Apr 2023Due:
22 May 2023Completion:
22 May 2023Final Change Report Issued
Completed
Start:
22 May 2023Due:
16 Jun 2023Completion:
15 Jun 2023Responsible Committee Decision
Completed
Start:
16 Jun 2023Due:
27 Jun 2023Completion:
27 Jun 2023Appeal Window Closure
Not Started
Start:
27 Jun 2023Due:
11 Jul 2023Completion:
Impacted REC Parties and Market Participants
Status
Implementation Date
03 November 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0104 | Clarifying requirement for continuous billing following an Erroneous Switch |
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 08 Jun 2026 |
|
|
| 1.0 | 08 Jun 2026 |
|
Download
Copy link
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As an Energy Supplier, DNO, GT, MEM and REC Service User, I want to understand precisely what obligations apply to me under the Schedule 9 – Qualification and Maintenance, so that I can provide the required information to the Code Manager in a timely manner and be compliant.
- As the REC Code Manager, I want REC Parties and REC Service Users to have a clear understanding of the information they need to submit relating to the maintenance of their qualification, so that necessary information can be submitted for review and consideration in the most efficient way.
Proposed Solution Document
Document title
R0059 - Draft legal text for IA v1.0 10.03.2023
Archive
Off
Document title
R0059 - Draft legal text for Consultation v1.0 14.04.2023
Archive
Off
Document title
R0059 - Draft legal text for FCR v1.0 01.06.2023
Archive
Off
Document title
R0059 - Final approved draft legal text v1.0 27.06.2023
Archive
Off
Document title
EMAR Link - R0059 - Draft legal text for FCR v1.0 01.06.2023
Archive
Off
Problem Statement
REC Service Users are required to submit Maintenance of Qualification Annual Statements to the Code Manager, the requirements differ depending on the User category. The lack of clear obligations for REC Service Users surrounding the Maintenance of Qualification reporting, set out in Schedule 9 – Qualification and Maintenance results in missing or partially completed submissions. Considerable time is spent by the Code Manager requesting and following up on individual submissions.
Stages Selection
R0059 - Change Proposal Form
R0059 - Change Proposal Plan v1.0 (Approved) 07.02.2023
R0059 - Initial Assessment Report v1.0 (Approved) 07.02.2023
R0059 - Impact Assessment Responses V1.0 14.04.2023
R0059 - Preliminary Change Report v1.0 (approved) 25.04.2023
R0059 - Consolidated Consultation Responses v1.0 23.05.2023
R0059 - Final Change Report v2.0 (post-vote) 27.06.23
Company Name
-
Review status
Review required
Clarification of Supplier of Last Resort Obligations under the REC
Date of latest update
Type
Change
ID
R0057
Change Category
Change Path
Priority
Urgent
No
Latest Update
04/08/2023 - Change Proposal has been withdrawn as agreed with the Proposer. The Problem Statement was addressed through C3-0047 - Updates to PAB Procedures.
Summary
Within Schedule 19 – Market Exit and Supplier of Last Resort there is currently no consideration of circumstances where the Replacement Supplier is unable to fulfil its REC obligations in respect of Consumers transferred to them, due to them having little or no control over the processes of the failed supplier or it’s administrator. This change seeks to define when the Replacement Supplier is responsible for obligations relating to the Consumers gained through a Supplier of Last Resort (SoLR) Process.
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer when my Energy Supplier goes out of business and I am transferred to a Replacement Supplier, I want my supply transfer to be handled quickly and have confidence that my new Supplier has all the necessary data to set up my account and bill me correctly from the transfer date, and if the Replacement Supplier fails to provide the expected level of service they will be appropriately held accountable.
- As a Replacement Supplier, I want the limitations affecting my ability to meet my REC obligations to be understood by the REC Code Manager and the Performance Assurance Board, so that any breaches of obligations are considered fairly and any limitations are taken into consideration.
- As the Code Manager I want to apply appropriate and proportionate Performance Assurance Techniques, taking in to account the ability of a Replacement Supplier to meet their obligations under the REC.
Proposed Solution Document
Document title
R0057 Draft Legal Text
Archive
Off
Problem Statement
Currently, Replacement Suppliers are responsible for all obligations of the failed supplier from the date and time set out in the Last Resort Supply Direction, this includes a period of time prior to Consumer accounts transferring to the Replacement Supplier’s systems, limiting their ability to fulfil these obligations. This means that a Replacement Supplier may experience issues with the Performance Assurance obligations for which they are responsible, but do not have direct control over. Any breaches of obligations by a Replacement Supplier need to be considered fairly and any limitations the Replacement Supplier may face are taken into consideration.
Stages Selection
R0057 - Change Proposal Form
R0057 - Solution Options
R0057 - Consolidated Impact Assessment Responses
R0057 - Change Proposal Plan v1.0
R0057 - Initial Assessment Report v1.0 (Approved)
R0057 - Preliminary Change Report V1.0 (Approved)
Company Name
EDF
Review status
Review required