Three times one equals one: Several disputed payment applications amount to a single dispute
Michael Comba considers a case in which the High Court dismissed an employer’s argument that an adjudicator lacked jurisdiction because the referral concerned three separate payment applications and, therefore, comprised three separate disputes.
- Details
Quadro Services Limited v Creagh Concrete Products Limited[2021] EWHC 2637 (TCC).
The facts
Quadro Services Limited (the Contractor) entered into an oral contract with Creagh Concrete Products Limited (the Employer). The Contractor made payment applications throughout the contract and raised invoices for the amounts claimed. Three invoices totalling approximately £40k were not paid by the Employer.
For two of the invoices, the Employer had previously approved the content of the respective payment applications; however, it did not pay these invoices nor issue a pay less notice. For the remaining invoice, the Employer had made no response, had not paid, and had not issued a pay less notice. The Contractor referred the matter to adjudication.
The Employer made only one argument in defence, that the adjudicator lacked jurisdiction. The Employer’s reasoning was that the matter concerned three separate payment applications and so comprised three separate disputes. Because an adjudicator only had jurisdiction to determine a single dispute, the Employer invited him to resign. The adjudicator declined and found in favour of the Contractor.
The judgment
The court considered the jurisdiction argument in line with the principles in Witney Town Council v Beam Construction (Cheltenham) Limited[1]. As was noted by the Employer, in Witney the judge had noted a ‘rule of thumb’ that:
“…if disputed claim No 1 cannot be decided without deciding all or parts of disputed claim No 2, that establishes such a clear link and points to there being only one dispute.”
The court accepted that this rule of thumb could be applied to this case and found that each of the payment applications and their validity could be decided independently from each other. However, the court also noted Prater Limited v John Sisk & Son (Holdings) Limited[2] in which it was noted that:
“Clearly a single dispute in the context of a construction contract may include several distinct issues… One needs to look at the facts of each case and to use some common sense.”
The court held that on these facts (and using common sense) there was a single dispute, which was whether the Contractor was owed the sums due from the outstanding invoices.
It was also noted that the Employer’s argument would have meant that, where several payment applications were in question, parties would need to commence individual adjudications. This would have been contrary to public policy as adjudication is designed to offer efficient and cost-effective dispute resolution, particularly in respect of payment disputes.
Analysis
This case should remind parties and practitioners that the meaning of a ‘single dispute’ should not be taken overly literally. It is common for a dispute to concern several sub-issues and the courts will tend towards common sense when determining whether a single dispute has arisen.
The courts will also have the wider aims of adjudication in mind when determining enforcement proceedings. Adjudication is designed to be a quick form of ‘rough justice’; convoluted arguments that run contrary to this will be given short shrift.
[1] [2011] EWHC 2332 (TCC).
[2] [2021] EWHC 1113 (TCC).
Michael Comba is a Solicitor at Sharpe Pritchard LLP
For further insight and resources on local government legal issues from Sharpe Pritchard, please visit the SharpeEdge page by clicking on the banner below.
This article is for general awareness only and does not constitute legal or professional advice. The law may have changed since this page was first published. If you would like further advice and assistance in relation to any issue raised in this article, please contact us by telephone or email enquiries@sharpepritchard.co.uk
Click here to view our archived articles or search below.
|
OUR RECENT ARTICLES
Jul 03, 2025
IPA guidance 2025: Managing PFI distress and preparing for expiryAanya Gujral and David Owens dive into the recent guidance published on managing the risks associated with Private Finance Initiative (“PFI”) projects.
Jul 03, 2025
Data (Use and Access) Act – Updating Data Protection Law and moreOn the 19th June 2025, the Data Use and Access Bill (“DUA Bill”) received Royal Assent to become the Data Use and Access Act 2025 (“DUA Act”).
Jun 24, 2025
Modifying subsidies: What is permitted and what is not?Beatrice Wood and Oliver Slater explore recent developments and discuss the process of awarding subsidies.
Jun 24, 2025
Getting new PPP right: Smarter tools for smarter infrastructureNicola Sumner, Steve Gummer and Roseanne Serrelli discuss the 'dos and don'ts' of Public-private Partnerships in their new form.
Jun 19, 2025
Zones/RABs and heat networks: The path to an investible infrastructure asset class?The UK’s new heat network zoning framework (the outlines for which were drawn by the Energy Act 2023) is set to redefine how low‑carbon heating is delivered by creating geographic zones, where district heat networks are the mandated, optimal solution.
Jun 17, 2025
Partial debt guarantees- Reviving Investment in UK Water InfrastructureIs it Time for a Public Sector Major Infrastructure Debt Guarantor?
|
ABOUT SHARPE PRITCHARD We are a national firm of public law specialists, serving local authorities, other public sector organisations and registered social landlords, as well as commercial clients and the third sector. Our team advises on a wide range of public law matters, spanning electoral law, procurement, construction, infrastructure, data protection and information law, planning and dispute resolution, to name a few key specialisms. All public sector organisations have a route to instruct us through the various frameworks we are appointed to. To find out more about our services, please click here. |
OUR NEXT EVENT
|
OTHER UPCOMING EVENTS
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |