Additional Registration Data (Gas) under Smart Energy Code

Date of latest update
Type
Issue
ID
I0262
Change Category
Other Industry Codes impacted
Priority
Urgent
No
Latest Update
19/06/2026 - Change Report Re-Plan V4.0 approved by Change Panel.
Summary
Gas Transporters (GTs) only have a single obligation in the Smart Energy Code (SEC). This obligation relates to the provision of Registration Data to the DCC. This issue is exploring whether these obligations may be transferred to the REC.
Proposer
Tracey Saunders
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
Problem Statement
Gas Transporters have very few obligations under the Smart Energy Code; those that they do have relate to provision of data owned by the REC. If these obligations were to be moved from the SEC to the REC, then the regulatory burden on GTs may be reduced as they would be able to completely secede from the SEC.
SME
SME Role
Lead Technical Analyst
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
Change Proposal Submission form
I0262 Change Report (Plan) (Approved) V5.0 19.06.26
I0262 Change Report Re-Plan V4.0 19.06
Company Name
-
Review status
Review required

In-year CRS budget amendment

Date of latest update
Type
Change
ID
R0226
Urgent
No
Latest Update
21/01/25 - Change Panel approved final recommendation for immediate implementation.
Summary
DCC has identified that the CRS budget for the current Financial Year (2024-2025) can be reduced, and as per the Code, a REC Change Proposal must be raised for the agreed budget to be amended.
Proposer
Bradley Baker
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
REC Decision Maker
Lead Analyst
holly.law
Date of Update to Priority
Solution Development
Change Proposal Form
R0226 Change Report - Final Recommendation approved.
Company Name
-
Review status
Review required

Agile Reporting within CSS

Date of latest update
Type
Change
ID
R0224
Change Path
Priority
Urgent
No
Latest Update
18/03/2026 - An update to plan has been published for consideration at the Technical Expert Panel on 25 March 26.
Summary
As part of the impact assessment process for R0115, it was identified that it is very costly and time consuming to make reporting changes within the CSS architecture. As such, we would like to explore enabling agile reporting within the CSS ecosystem, by creating a functionality that consolidates all necessary data into a single, centralised database.
Proposer
Maxime Van Eyseren
Change report - Final Change Report
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Date of Update to Priority
Solution Development
Problem Statement
Current CSS arrangements mean that REC Changes designed to facilitate access to CSS data are more onerous that they need to be. Current arrangements are costly and have relatively long lead-times. This Issue seeks to explore changing the way that the CSS data can be accessed.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
Proposal Form - Agile reporting within CSS
I0224 Change Report (Plan) (Approved) V1.0 21.01.25
Change Proposal Re-Plan Approved
Solution/Business Case report
R0224 update to plan 18.03.26
R0224 update to plan 19 May 2026
Company Name
-
Review status
Review required

Sequence order of CSS00200 message

Date of latest update
Type
Issue
ID
I0204
Urgent
No
Latest Update
08/11/2024 - The Proposer has withdrawn this issue as it is being progressed under MHHS CR056. The adoption window has now closed. * This is Issue relates to the Market-wide Half Hourly Settlement design.
Summary
Empty
Proposer
Madison Layton
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
Stages Selection
Company Name
St.Clements
Review status
Review required

Review of the REC's Address Management Service

Date of latest update
Type
Issue
ID
I0200
Change Category
Change Path
Priority
Urgent
No
Latest Update
13/05/2026 - The REC Code Manager is establishing a new REC working group to support the progression of I0200 – Review of the REC’s Address Management Service. If you would like to attend the I0200 Working Group, please register your interest by contacting the Code Manager at change.management@recmanager.co.uk. The first meeting will take place in June 2026, with the exact date and time to be confirmed in due course and communicated via the REC Change Bulletin and via email to all those who register their interest.
Summary
Having the incorrect address can lead to a range of Consumer issues, including switching, billing and meter reading problems. The Meter Point Location (MPL) and Retail Energy Location (REL) have been added to the Code to resolve this issue. Whilst there had been progress resolving address data issues, there is not currently a mechanism to establish Code level targets for address improvement, resulting in around 2.8 million unmatched addresses.
Proposer
Claire Hemmens
Change Report - Initial Assessment and Change Plan Report

Comments deadline
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
James Hardy
Date of Update to Priority
Solution Development
Problem Statement
There has been progress resolving address data issues, but there is no mechanism to clearly establish Code level targets for address improvement, or overall market performance.
SME
SME Role
Lead Assurance Analyst
SME User
amoden@deloitte.co.uk
I0200 - Improving Address Management Targets (Issue Form)
I0200 - Change Issues Group paper
I0200 - Change Report (Proposal Plan) V1.1 (Approved) 18.02.2025
I0200 - Update to Plan (Pre Approval) 14.04.2026
Company Name
REC Code Manager
Review status
Review required

Changes to Terms of reference following acceptance of R0167

Date of latest update
Type
Change
ID
R0188
Change Path
Urgent
No
Latest Update
20/08/2024 - Approved for implementation on 06/09/2024.
Summary
This Housekeeping Change Proposal seeks to update the Terms of Reference of the REC Change Panel and the Performance Assurance Board, following the acceptance of R0167, to reflect Issues.
Proposer
Glenn Sheern
Impacted Consumers
Status
Implementation Date
Status Live
EMAR Version 06.09.2024_live
Included changes Affected REC Items
R0003 Market-wide Half-Hourly Settlement Implementation
Implementation Status
Date Raised
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed Solution Document
Document title
REC Change Panel - Terms of Reference
Archive
Off
Document title
REC Performance Assurance Board (PAB) - Terms of Reference
Archive
Off
Problem Statement
This Housekeeping Change Proposal seeks to update the Change Panel and Performance Assurance Board, Terms of Reference to reflect that these Committees consider change Issues as well as Change Proposals.
R0188 - Change Proposal Form
R0188 - Housekeeping Change Report (Post Approval)
Company Name
Rec Manager
Review status
Review required

Amendment Proposal: RECCo Access Provision to RECCo Services

Date of latest update
Type
Change
ID
R0185
Change Path
Priority
Urgent
No
Latest Update
08/08/2024 - the Proposer has withdrawn this Change Proposal.
Summary
RECCo is tasked with fulfilling several obligations. This proposal has been raised to amend some of the wording within the REC, which would benefit from reassessment. When the REC was originally drafted, references to RECCo in the code were originally intended to refer to the activities directly managed and overseen by the REC Board, and were considered separately to activities managed by the Code Manager.
Proposer
Andres Alvarez
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
R0185- CP Form Amendment Proposal RECCo Access Provision to RECCo Services.docx
Company Name
RECCo
Review status
Review required

Improvements to CSS Business Process Logic

Date of latest update
Type
Change
ID
R0178
Change Category
Change Path
Priority
Urgent
No
Latest Update
17/06/2026 - The Code Manager has published an Update to Plan. This will be presented to the REC Technical Expert Panel at their meeting on 24 June 2026.
Summary
This change proposal is aimed towards rectifying a collection of issues that were identified with the CSS Business Process Logic. These have been identified as follows: 1. Deactivation of an active reg. whilst in-flight switch in progress 2. Deactivation of a prior cancelled registration 3. OFAF switch containing multiple MPxN
Proposer
Caroline Milner
Change Report - Initial Assessment and Change Plan Report

Comments deadline
Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Implementation Date
Status Live
EMAR Version 25.06.2027_live
Implementation Status
Date Raised
Fuel
REC Decision Maker
Lead Analyst
holly.law
Date of Update to Priority
Solution Development
Proposed solution summary
  1. Deactivation of an active reg. whilst in-flight switch in progress As mentioned previously, the ‘Deactivation of an active reg. whilst in-flight switch in progress’ issue did have an existing REC CP raised and therefore is further along the discussion process compared to the other two issues identified. Initial discussion outlined that the most appropriate solution for this change proposal should consider the business needs and the desired outcomes. It was noted that from a business perspective, if the switch has already been accepted, then it should still go through and not be cancelled. Therefore, the following points were raised: • It was acknowledged that there are multiple solution options/approaches that could potentially be employed to resolve this issue. As such, and to avoid being overly prescriptive, it is requested that CSS provider investigate all possible options and outline their recommendation for the most suitable approach, which would be developed/progressed further through the subsequent Impact Assessments. • However, the aim is for an effective solution to be developed which would ensure that the consumer is switched with the original effective date being used and that CSS systems could cater for such registration events whilst following the normal Gate Closure processes. • Where possible, the solution should also look to proactively mitigate the impact of this scenario, as opposed to working on a retrospective basis which can lead to the issue persisting over an extended period of time. It was also noted that consideration would need to be given to state of the meters as this would also have an impact on whether switches are able to progress: Therefore, the following points were raised: • The solution would need to consider how the incumbent supplier has deactivated the meter and whether it has been moved to a ‘terminated’ state or a ‘dormant’ state. o Dormant – The meter is inactive. Note that this is a temporary state and therefore the meter could be put back into service. o Terminated – The meter has reached end of life and cannot be reinstated. Note that this is a permanent state. • If the incumbent supplier has moved the meter into a ‘terminated’ state, the in-flight switch would then need to be cancelled. • However, for the ‘dormant’ state, the following two options would be available in terms of what could happen to the status of the meter and thus the in-flight switch: o Moves from ‘inactive’ to ‘active’ (continue with the switch) o Moves from ‘inactive’ to ‘cancelled’ (cannot continue with the switch)
  2. Deactivation of a prior cancelled registration and OFAF switch contains multiple of the same MPxN It is noted that the initial approach discussed was to add new Business Data Validation Rules (BDVR) to stop these issues from occurring. However, this was only discussed at high-level and therefore we request that the CSS provider confirm this approach and provide further details as this change proposal progresses.
Problem Statement
1) Deactivation of an active reg. whilst in-flight switch in progress: There are instances where the incumbent supplier is withdrawing prior to the ‘Supply Effective from Date’, causing the accepted switch to fail at Gate Closure which occurs at 17:00hrs. This creates the scenario in which there is no longer a losing supplier for the consumer to switch from, and therefore the switch process stalls and cannot be progressed. Therefore, this has a direct impact on consumers who have a switch request which has already been accepted but CSS is not able to progress further as the switch process stops. Indeed, there have been a total of 82 missing messages observed since 1st January 2023, of which 66 messages have been related to switches where there was no registered Supplier recorded at Gate Closure. The 30th September 2023 Gate Closure was particularly impacted by this scenario and resulted in 45 registrations which did not become effective on 14th October 2023 as planned. It should also be noted that the 1st October is one of the key contracting dates for large Industrial and Commercial (I&C) consumers, consequently increasing the impact to consumers in this instance. 2) Deactivation of a prior cancelled registration: This scenario occurs when the registered supplier of a MPxN (via the active registration) is the same supplier that cancelled a previous switch for the same MPxN. In this case there is the possibility that the supplier could attempt to deactivate the active registration by accidentally providing the cancelled registration identifier. Currently, CSS still accepts the deactivation request and erroneously changes the cancelled registration state from cancelled to inactive, sending out securedInactive messages. Currently, after an MPxN is disconnected, the Supplier is required to submit a deregistration request to CSS. Therefore, there is a possibility that the suppliers could submit this request for a cancelled registration not active registration. CSS would still accept this request as the Business Data Validation Rules (BDVR) lack coverage of this case; in such cases the Supplier may incorrectly believe that they have deregistered the MPANs. 3) OFAF switch containing multiple MPxN: This is the instance where the end user sends through a One Fail All Fail (OFAF) switch with the same MPxN contained within the payload 2 or more times. Multiple registration IDs are created for the same MPxN, and the registration is left in an incorrect state given a lack of appropriate BDVRs. Indeed, there has been a further reported incident regarding an OFAF transaction of the same MPxN. The primary MPxN was associated with a secondary MPxN and therefore two registrations were created for the primary and secondary MPxN, equating to four registrations in total. There was then an objection raised but this only cancelled 1 of the 2 registrations for each MPxN. The remaining 2 registrations proceeded through gate closure.
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
R0178 - Change Proposal Form
R0178 - Change Report (Proposal Plan) V2.0 (18.02.2025)
R0178 - Update to Proposal Plan V1.0 (Approved) 18.02.2025
R0178 - Consolidated Impact Assessment Responses (Non-Confidential) 18.03.2026
R0178 - Change Report (For Consultation) V1.0
R0178 - Update to Plan (17.06.2026) Pre-Approval
Company Name
REC Technical Services
Review status
Review required

Clarifying Event of Default requirements

Date of latest update
Type
Change
ID
R0129
Priority
Urgent
No
Latest Update
04/10/2023 - Following the approval of R0138, this change has been withdrawn.
Summary
Following several recent events of non-payment for services and REC defaults it is clear that the event of default provisions in the Code are unclear. This change seeks to introduce clarity to the REC Main Body.
Proposer
admin
Impacted Consumers
Impacted REC Documents
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
R0129 - Change Proposal form (downloadable version) 16.06.2023
Company Name
REC Code Manager
Review status
Review required

Frequency and content of CSS reports on switching via the DCC portal

Date of latest update
Type
Change
ID
R0115
Change Category
Priority
Urgent
No
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
Summary
This change has been raised by Ofgem to make updates to CSS reports provided by the Switching Operator; for these be provided on a weekly basis and be designed in such a way that only genuine Switches between Suppliers are reported. At present the latter is not possible as all switches at MPID level are reported with no indication of switching flows.
Proposer
Monica Gandolfi
Change Plan

Preliminary Change Report published

Completed

Start:

27 Apr 2023

Due:

15 Dec 2023

Completion:

15 Dec 2023

Consultation issued

Completed

Start:

15 Dec 2023

Due:

15 Dec 2023

Completion:

15 Dec 2023

Consultation close

Completed

Start:

15 Dec 2023

Due:

19 Jan 2024

Completion:

19 Jan 2024

Final Change Report published

Completed

Start:

19 Jan 2024

Due:

26 Jan 2024

Completion:

26 Jan 2024

Responsible Committee Decision

Completed

Start:

26 Jan 2024

Due:

06 Feb 2024

Completion:

06 Feb 2024

Send to Authority for determination

In Progress

Start:

06 Feb 2024

Due:

07 Feb 2024

Completion:

Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
Status Live
EMAR Version 08.11.2024_live
Included changes Affected REC Items
R0105 Review of ONAGE SLAs
  • Schedule 14 - Metering Operations
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
  1. As a Consumer, I want Ofgem to effectively monitor the market to ensure the right policy decisions are made.
  2. As Ofgem, I need accurate and timely data to ensure that I can make informed decisions on any interventions in relation to market stability.
Proposed Solution Document
Document title
Attachment A_R0115 Solution Requirements Matrix v2.0
Archive
Off
Document title
Attachment B_R0115 Report Templates v1.0
Archive
Off
Document title
Switching Operator (SO) Service Definition_redline 15.12.2023
Archive
Off
Problem Statement
Without appropriate reporting, Ofgem cannot effectively monitor the level of Switching in the market in a timely and accurate manner. This hinders its ability to act and inform any policy interventions in relation to market stability.
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
R0115 - Change Proposal Form
R0115 - Change Proposal Plan v2.0 (Approved) 05.12.2023
R0115 Initial Assessment Report v2.0 (Approved) 05.12.2023
R0115 - Preliminary Change Report v1.0 (Published for Consultation) 15.12.2023
R0115 - Consolidated Consultation Responses_Non Confidential (26.01.2024)
R0115 - Final Change Report v1.0 (Post-Vote) 06.02.2024
R0115 Authority Decision (23.04.2024)
Company Name
Ofgem
Review status
Review required