Disputes
Once trading parties have considered the alternative approaches to resolution and attempted to resolve issues relating to the market codes informally between themselves, as set out in the Quick Start Guide, they may consider raising a formal Dispute. Where a Dispute is raised, the trading parties continue to attempt to resolve the matter between themselves but then either may refer the matter to the Disputes Committee (DC) and following the DC’s decision either may go to arbitration as set out in the Disputes Process – Stage by Stage Outline.
There are four types of Dispute, as described below, which trading parties can raise if they believe another party in the market is operating incorrectly. These are in relation to: incorrect data items, other aspects of the Wholesale-Retail Code (WRC), the Market Arrangements Code (MAC) and inaccuracy of settlement reports (with the Market Operator).
Where a trading party wishes to raise a formal Dispute their Contract Manager should submit the required information using the Disputes Form Information, Referral and Evidence Template (see documents below) to the email address as directed. The information should include details on the other trading party (or parties) involved, the type of Dispute and the specific aspects of the market codes the Dispute relates to, the details of the issue in dispute, information on the attempts to resolve it informally, and evidence of notification to the other trading party of the intent to raise a Dispute.
A list of active and recent disputes is provided below.
Trading Disputes
These are in relation to any errors in (including omission from) any Data Item contained within CSD 0301 (Data Catalogue) and so impact on Settlement and Primary Charges. Where the DC finds that there was an error, parties are required to correct it and MOSL to run a Dispute Settlement Run in certain cases.
Non-Trading Disputes
These relate to other aspects of the Wholesale-Retail Code (WRC). These are categorised into Operational, Market and Business Terms Non-Trading Disputes as well as Miscellaneous Non-Trading Disputes. The DC can decide whether there has been a breach of the Wholesale Contract or the WRC.
MAC Disputes
These are in respect of any act or omission of a trading party relating to the Market Arrangements Code (MAC). The DC can decide whether there has been a breach of the MAC.
Market Operator (MO) Disputes
These relate to Inaccurate Settlement which MOSL, as the MO, has investigated and potentially put in place a rectification plan under Section 5 of the Market Terms. Inaccurate Settlement is where a Wholesaler or Retailer
considers that a Settlement Report is inaccurate for any reason (other than due to any error in or omission of any Data Item). If the Wholesaler or Retailer has concerns with the MO’s response or lack of it, they may raise a Dispute. The DC can decide whether than has been an Inaccurate Settlement or whether the MO has provided or implemented a rectification plan.
Disputes List
Please find the list of all open disputes below, and disputes closed in the last 12 Months.
Dispute type | Description | Publication date | Title | Documentation |
---|---|---|---|---|
Unified | Updated 13/09/21: Closed. From the original volume there are a handful of SPIDs awaiting resolution which can be resolved by ongoing work between Thames Water and Castle Water. Original Dispute wording: Castle Water Limited (Castle) asserts that Thames Water Limited (Thames) have not used Visual reads when submitting Final reads in the case of 417 SPIDs . This is contrary to Section 3.3.3 of CSD0202 Meter Read Submission: Process - “The only permitted Meter Read Method for a Final Read is “Visual”. |
26/03/2021 Closed 13/09/21 |
DIS0032 |
- |
Unified | Thames Water state that Castle Water are incorrectly withholding settlement charges relating to SPIDs where Castle Water state that Thames Water as a Wholesaler have a responsibility to provide remote reading systems. | 20/11/2020 | DIS0021 |
- |
Non Trading | Marston’s PLC has raised a dispute with Severn Trent Water in relation to Wholesale Retail Code: Business Terms – Schedule 3: Alternative Eligible Credit Support. The parties are yet to agree on a resolution and the dispute remains open. | 06/05/2020 | COD00060 |
- |
MAC | Thames Water provided Castle Water with a list of supply points, where an issue has been identified concerning to defective meter pit covers. As a result, meter reads were unable to be taken. | 19/11/2018 | COD00054 |
- |
MAC | A list of supply points held by Thames Water have been identified by Castle Water as having meters located in an unsafe location and subsequently meter reads were unable to be taken. | 19/11/2018 | COD00053 |
- |
MAC | A list of supply points held by Thames Water have been identified by Castle Water as having an issue related to damaged meters. As such, meter reads are unable to be input. | 19/11/2018 | COD00051 |
- |
MAC | Castle Water has identified a number of supply points held by Thames Water with meters associated with defective reading systems. As such, meter reads are unable to be input. | 19/11/2018 | COD00049 |
- |
Unified | Thames Water state that Castle Water are incorrectly withholding settlement charges relating to SPIDS which Castle Water have stated are outside the SLA for completing the bilateral requests. Thames Water escalated 2159 out of the 3257 SPIDs to the DC. The DC found in Thames Water’s favour and required Castle Water to pay the outstanding wholesale charges. Castle Water has referred this decision to arbitration. Thames Water and Castle Water continue to work to agree resolution for the remaining Disputed SPIDs not escalated to the DC. |
20/11/2020 Closed 21/09/22 |
DIS0020 |
Resolved through London Court of International Arbitration |
Unified | The Disputes Committee (DC) held a closed session to hear DIS0031, which had been brought by Elis UK Limited (ELIS) and in which the responding party was South West Water Ltd (SWW). In this Dispute, ELIS asserted that SWW had not complied with Schedule 3 of the Business Terms (Alternative Eligible Credit Support) in that they failed in their consideration to develop and introduce a credit offering that is in alignment with what Ofwat indicated to be notable examples of best practice. The DC found that SWW had not breached Schedule 3 of the Business Terms on the basis that the code contains no obligation to reach agreement. The DC noted that SWW had recently documented an agreement for Alternative Eligible Credit Support with ELIS, which was signed by both parties on 23rd June 2021 and posted on the MOSL website. |
06/05/2020 Closed 02/09/2021 |
DIS0031 (COD00061) |
Please click here for full findings |
Unified | Update 28/09/21. Both parties have confirmed this as closed. Meter was running backwards due to a cross connection within the customer’s premises which is causing backflow through meter. Original wording from 6/9/21: Castle Water Limited (Castle) have raised a non-trading dispute against Thames Water Limited (Thames) alleging that Thames is in breach of 4.2.1 of the Wholesale Contract Schedule 1, Part 2: Business Terms in that, as Contracting Wholesaler, it their responsibility to “provide, maintain, repair and, either routinely or where faulty, replace the meter(s)”, which in the case of the listed meters, they have failed to do. | 06/09/2021 Closed 28/09/21 | DIS0034 |
- |
Unified | Castle Water Limited (Castle) have raised a dispute DIS0035 regarding a SPID which they assert entered the market with two actual reads from the wholesaler (Thames Water Limited (Thames) that have since been found to be estimates. Castle asserts that the pre-loaded reads were under-estimating the actual consumption; actual reads since market opening, compared to the pre-market opening reads suggest a rise in consumption that is not in line with the comparison of year on year actual reads since market opening. The primary charge has therefore been significantly inflated. No evidence exists of any leakage or explanation for the increased consumption. | 06/10/2021 Closed 08/12/21 (resolved) | DIS0035 |
- |
Unified | Castle Water Limited (Castle) has raised a dispute against Thames Water (Thames) alleging that errors in data items have resulted in incorrect wholesale charges based on meters serving another customer’s premises. Castle also considers that Thames has not properly investigated its or the customer’s concerns and Castle has not received a response to its notice in October 2020 requesting resolution. As the customer switched to Sutton and East Surrey Water Services Limited (SES), that retailer may also have received incorrect wholesale charges. | 27/01/22 Closed 10/02/22 (Resolved) | DIS0036 |
- |
Unified | ConservAqua Limited has raised a non-trading dispute against Severn Trent Water Limited (STW) alleging that STW is in breach of the Operational Terms’ Process H7 - Application for Vacancy Incentive Scheme Payment with fundamental control failures leading to many claims being outstanding or rejected in error. Update 29 April 2022: ConserveAqua requested that this dispute be regarded as "Urgent". The Disputes Committee concurred, the Dispute is confirmed as Urgent and will be heard on 18 May 22. Closed: In the case of Non-Trading Disputes the DC’s remit is to assess whether there has been a breach of the Codes. The DC reached a majority decision regarding DIS0038 and found that Severn Trent Water had breached Process H7, Part B Step 2 of the Operational Terms on the basis that the Code contains an obligation on the Wholesaler to provide materially complete data to the registered Retailer from the applying Retailer. |
20/04/22 Closed 25/5/22 Resolved |
DIS0038 |
Please click here for full findings |
Unified | Castle Water Limited (Castle) has raised a dispute against Severn Trent Water Limited (Severn Trent) alleging that a new SPID was created in error and incorrectly allocated to Castle, which, along with the customer, questions that SPID’s charges. Castle considers that Severn Trent has not properly investigated this issue and has not received a response to its email sent in November 2021 requesting resolution. | 11/02/22 Closed 10/3/22 (Resolved) | DIS0037 |
- |
Unified | ConservAqua Limited has raised a non-trading dispute against Water Plus (WP) alleging that WP is in breach of the Operational Terms’ Process H7 - Application for Vacancy Incentive Scheme Payment with fundamental control failures leading to many claims being outstanding or rejected in error. Update 29 April 2022: ConserveAqua requested that this dispute be regarded as "Urgent". The Disputes Committee concurred, the Dispute is confirmed as Urgent and will be heard on 18 May 22. Closed: The DC considered DIS0039 on 18/5/22 and reached a majority decision, finding that Waterplus had technically breached a stated SLA within Process H7, Part B Step 3 of the Operational Terms. |
21/04/22 Closed 25/5/22 Resolved |
DIS0039 |
Please click here for full findings |
Unified | Castle Water Limited (Castle) has raised a dispute against Thames Water Utilities Limited (Thames) alleging that Thames has failed to correct data items, including allocating the appropriate meters to a Supply Point and not deregistering a Supply Point, or to follow the Codes, which has prevented it from accurately billing the customer. Castle also notes that this follows months of correspondence between the parties. Update on 8/6/22: Both parties have reached a resolution on this Dispute | 09/05/22 Closed (resolved) 8/6/22 | DIS0041 |
- |
Unified | Castle Water Limited (Castle) has raised a dispute against Thames Water Utilities Limited (Thames) alleging that Thames erroneously deregistered a Supply Point in breach of Section 4.8.2(d) of the Market Terms as well as failing to correct other data items or to follow the Codes, which has prevented it from accurately billing the customer. In Castle’s view this follows protracted correspondence between the parties. Update on 8/6/22: Both parties have reached a resolution on this Dispute | 09/05/22 Closed (resolved) 8/6/22 | DIS0040 |
- |
FAQs
As the disputing party, you must ensure that you adhere to any SLAs which have been set for you. These are code-obligated SLAs which will help to ensure that all disputes are completed within a justified timeframe. Furthermore, it is important that, as the disputing party, you submit only accurate and correct data, when requested by MOSL.
MOSL, as market operator, retains an overall responsibility to provide independent case management capabilities for disputes in the market. Where MOSL is also a disputing party, we will ensure that we maintain separation when dealing with the dispute in our capacity as Case Manager. We will also ensure that no one making decisions regarding the resolution is involved in the overall management of the dispute. In all cases, MOSL will operate to a Code of Conduct to ensure appropriate behaviour and neutrality.
The 'expert' is appointed through mutual consent by participating disputing parties, to aid the resolution of a dispute. Experts can be nominated by any party or through a list of recommended 'subject matter experts' from the Academy of Experts.
The role of the expert is to act as an independent decision maker, who will deliver an overall judgement, oversee the creation of a remediation plan and disperse the total expenses and fees incurred through the MO Dispute process.
The expert will provide the MO disputing parties with a breakdown of fees and any reasonable expenses incurred. The disputing parties are required to share the fees and expenses equally, unless directed otherwise by the expert. The expert has the authority to direct one party to pay a larger sum (which includes, but is not limited to, fees and expenses).
Both MAC and Non-Trading Disputes are raised and managed through Kissflow. You will need to complete all necessary fields as part of your submission and submit any attachments you believe strengthen the cause for raising a dispute.
Prior to raising a MAC or Non-Trading Dispute, you should first raise a Statuatory Query wih MOSL to confirm any differences of interpretation. If you believe another trading party is not acting in alignment with the market codes, you should attempt to resolve the issue directly with the associated party prior to raising the dispute.
Once your dispute is accepted, you will need to work with MOSL to attempt to resolve your issue successfully. This can be done by:
- Working efficiently to make sure that all code obligated deadlines related to the dispute process are met
- Ensuring that you provide accurate data throughout the processing of your dispute
- Making sure you set up and honour the dates of any scheduled meetings and that the appropriate individual attend all meetings
- Maintaining appropriate contact with MOSL, especially where MOSL is not a disputing party and is acting instead as a Case Manager. (Where MOSL is acting as a Case Manager, we will operate to a Code of Conduct to ensure complete neutrality.)
- Entering the dispute process in good faith and with an openness to reach a resolution.
Further details on the MAC Dispute Resolution process can be found in Sections 17.2 to 17.9 of the MAC. Additional Information concerning a Non-Trading Dispute can be found within Section 17 of the Business Terms.
The outcome of either the MAC or Non-Trading Dispute will depend on its nature, and the levels of escalation required through the MAC and Non-Trading Dispute resolution process. The overall decision will be determined either between the disputing parties or by arbitration, if a resolution is not possible. Outcomes can include, but are not limited to:
- Code change. If both parties agree that the section of code which has led to the dispute is ambiguous, a code change proposal may be submitted to the Panel who will consider the change
- Change in process. This may be a change to how MOSL or the trading party operates
- Rectification of previous errors. This may include revisions to previous determinations made by MOSL.
There are no fees associated with raising a dispute, however fees will be incurred if the dispute gets referred to arbitration. All parties involved will be jointly liable for paying costs, the total amount of which will be determined by the LCIA Court as its Schedule of Costs. The arbitration tribunal will determine the proportion of the total costs payable by each involved party. The tribunal may also recover expenses in connection with arbitration and further costs may be incurred as a result of rectification activities, which may arise as part of a dispute's resolution.
If your dispute is rejected it will be closed in Kissflow and no further actions are required, unless you wish to raise another dispute. MOSL will provide a rationale for the rejection, which can be found on your submission.
Please click here to download an outline of the MO Disputes process. This outline map clearly shows key stages of the process, including resolution and the steps disputing parties need to take.
An MO Dispute is the end product of when a trading party believes an error or omission regarding the production of the Settlement Report has occurred by the Market Operator (MOSL).
An MO Dispute may only be initiated upon attempting a resolution through either mediation/informal meetings - as an attempt to resolve the issue or query with associated disputing parties or by raising a Statutory Query. If a resolution has not been found via the Statutory Query Process, the initiating party will be required to initiate an MO Dispute.
Prior to raising an MO Dispute, trading parties must have attempted to resolve their issues through the Statutory Query process. If this does not achieve a suitable resolution, they will then be required to attempt a mediation step with MOSL. Only when both the Statutory Query process and mediation fail to provide a resolution, will the trading party be able to initiate the MO Dispute Process.
MO Disputes should be raised through Kissflow, where the initiator of the dispute will be required to provide a completed MO Disputes Form which will be submitted also through Kissflow. In order for the dispute to qualify, the initiator will be required to ensure the dispute meets all criteria listed within the form prior to submission. The application form may be rejected if the dispute request fails to meet the criteria outlined.
The initiator will be required to ensure all forms and supplementary documentation have been submitted within the allotted period and that the form has been completed accurately and submitted by the relevant Contract Manager.
Upon receipt of the application, MOSL will provide acknowledgement of the dispute within a suitable period of time. Kissflow will also generate an MO Dispute Number for your application, which will be associated with your dispute logged with MOSL.
Upon submission of the Dispute Application via Kissflow, a Case Manager will be assigned to the application. The Case Manager will determine if the dispute meets the criteria and if so, progress it through Kissflow. This includes tracking decisions made by an appropriate expert, where required. Upon a decision being made, remediating actions will be taken within Kissflow as needed.
Where the dispute is successful, remediation measures will be taken to rectify the issue, including re-running settlement and/or the formation of a remediation plan. Other affected parties and/or broader audiences will be notified of the dispute findings; MOSL will publish any findings on its website.
If you are raising an MO Dispute it must meet any of the following criteria in order for it to be considered valid:
- MOSL produced an inaccurate settlement, that is not caused by any data item of the trading party raising the dispute, or another trading party
- MOSL failed to provide a rectification plan within two months
- MOSL failed to implement its rectification plan in a timely manner
- MOSL provided a rectification plan that is unclear, incomplete or materially incorrect.
Trading Disputes should be raised and managed through Kissflow. Any additional information which you believe would strengthen the case for raising a dispute can also be attached to the application. MOSL will acknowledge the application within five business days.
The activities involved depend on the specific dispute, however it will follow these four key stages:
- Raise Trading Dispute
- Hold resolution meeting with disputies parties
- Raise to Disputes Committee for decision
- Refer to arbitration.
The objective of arbitration is to obtain a fair resolution of disputes by an impartial tribunal, without unnecessary delay or expense. If it has not been possible to resolve the dispute at three previous meetings, either disputing party can refer the dispute further to arbitration. This is done by submitting a written request to the The London Court of International Arbitration (LCIA). The disputing parties will have the opportunity to agree and nominate a sole arbitrator, who will review the dispute and come to an impartial decision. If the disputing parties are unable to agree on a nominated sole arbitrator, a request can be submitted to the Panel Chairman who will instead nominate a proposed sole arbitrator to the LCIA. In the event that neither party nominates a sole arbitrator to the LCIA within 20 business days of the filing of the response, the LCIA will nominate a sole arbitrator in accordance with the LCIA rules.
MOSL do not play an active role beyond monitoring the arbitration process once the dispute has been escalated. Responsibility remains solely on a trading party to organise, communicate to MOSL, and undergo the arbitration process, which must be raised under London Court of International Arbitration (LCIA) rules.
For more information on the a trading party’s obligations during the arbitration process, please refer to Section 19 of the Business Terms.
The decision of the sole arbitrator will be final and binding for all the disputing parties. In referring a dispute to arbitration, the disputing parties waive any right to challenge or appeal any outcome of the arbitration tribunal to the full extent permitted by law.
The Disputes Committee has responsibility to resolve disputes relating to Primary Charges, therefore disputes cannot be raised for invoice periods prior to April 2017. However, in certain circumstances historical data (e.g. meter reads) that relate to periods prior to April 2017 may be considered included within the scope of a Trading Dispute, should that data impact an invoice period over which the Dispute Committee has remit.
In order for a Trading Dispute to be valid, it must meet the following criteria:
- Trading parties are disputing a data item
- The disputing party has notified the other disputing party(ies) in writing of the dispute and held a meeting to attempt resolution
- The Trading Dispute is not in respect of Non-Primary Charges, which are outside of MOSL’s remit
- The same data item/error has not been previously investigated.
If you are unhappy with the decision proposed by the Dispute Committee, you can refer the Trading Dispute to arbitration. You will have 20 business days from the Dispute Committee decision to refer the dispute to arbitration. If a Trading Dispute is not referred to arbitration within that time, then the decision of the Disputes Committee will be final and binding for all trading parties, and each must comply with the decision made.
Prior to escalating a Trading Dispute to the Disputes Committee, trading parties must first have:
- Notified the other disputing party(ies) in writing of the existence and subject matter of the dispute
- Held a meeting involving all disputing parties to try and resolve the dispute.
To support the Trading Dispute, MOSL will accept additional relevant information from impacted parties.
One of the following steps may be taken to rectify the issue:
- Undertake the next Planned Settlement Run after the 20 business days the parties have to refer trhe dispute to arbitration
- Undertake a Dispute Settlement Run, which will be determined by the Disputes Committee. It is decided by looking at the period to the next Planned Settlement Run, alongside the severity of the Trading Dispute
- Where a Trading Dispute is not decided until after the relevant final Settlement Run, undertake a Post-RF Settlement Run.
Fees for any such rectification will be distributed across the disputing parties as decided upon by the Disputes Committee.