ESG Global We are currently experiencing 3 issues resulting in the rejection of the D0312 Notification of Meter Information to MPAS Scenario 1 Meter A is assigned ESME ID A at the property 10 The Sands Meter A ESME ID Ais then removed and installed in property 12 The Grove As the ESME ID pertains to the meter, it is then rejected using rejection reason V - Rejected - ESME ID exists in MPRS. Not Removed Meter, Associated Import/Export MSID or Related MPAN Scenario 2 Meter A is assigned ESME ID A at the property 10 The Sands but it should have been installed at 12 The Sands Therefore, the meter is removed and installed in the correct property and a default ESME ID is used. In this scenario, the ESME ID is silently accepted but appears to be using the same ESME ID. Scenario 3 When another MOP A uses MOPB's ESME ID incorrectly and MOP B is unable to update MPAS with the correct details, there is no mechanism to identify who is using the ESME ID. There is no current facility in EES to search by ESME ID . Similarly, we don't believe there is a no way for the MOP to default it which again links to scenario 2 as its being silently accepted and not updating MPAS with the default value EDF (MEM) EDF (as a MEM) are finding that we are unable to resolve certain crossed meter cases in ECOES due to receiving Rejection Code V when issuing the D0312. The meter we are trying to update is existing, or has previously existed against another MPAN in ECOES on the installation date we are using. Points to note: 1. The issue seems to be affecting SMETS 2 meters with ESME IDs. 2. This has only been a problem since the MPRS validations implemented last year. 3. The same issue was previously raised at a RIG committee meeting on 08.03.2024, under the title Updating ESME ID. I would like to formally raise this as an issue as we are unable to find resolution (after reaching out to C&C developers and speaking to other REC parties). We are receiving queries and escalations from suppliers due to ECOES not being correct. I have attempted to attached a document which contains examples and further explanation, but the form is not allowing the upload. I will attempt to send separately via the service desk. OVO EMSE ID's cannot be added against an MPAN on ECOES via a D0312 if they were previously against a different MPAN on ECOES. This is causing D0312 rejections and will increase the volume of ESME IDs populated as 000000000000