UK: Payment In Practice Under Part 8 Of The Local Democracy, Economic Development And Construction Act 2009

Last Updated: 7 January 2015
Article by Lisa Kingston

This final issue of Insight of 2014 focuses on an important subject that has been out of the limelight for some time, but which has come back into focus in time for the Christmas break: the payment regime under the Local Democracy, Economic Development and Construction Act 2009 ("LDEDCA").

We last wrote about the "new" (as it then was) payment regime in issue 18 of Insight, two years ago this month1. The payment regime was preceded by eight years of debate and months of delay before finally being implemented on 1 October 2011, and a flurry of case law was expected to follow in its wake. To the surprise of many, there has been no reported case law on the payment regime until very recently, when the decisions in ISG Construction Ltd v Seevic College [2014] EWHC 4007 (TCC) ("ISG v Seevic") and Harding (t/a MJ Harding Contractors) v Paice and another [2014] EWHC 3824 (TCC) ("Harding v Paice") were handed down by the Judge in Charge of the Technology and Construction Court, Mr Justice Edwards-Stuart, within two weeks of each other earlier this month.

This 42nd issue of Insight (i) provides a reminder of the key principles of the payment regime; (ii) reviews the decisions in ISG v Seevic and Harding v Paice; and (iii) provides practice points in relation to both payment and adjudication going forward in light of Mr Justice Edwards-Stuart's judgments in ISG v Seevic and Harding v Paice.

A reminder of the key principles of the payment regime

The starting point for the payment regime is the payment due date. The payment due date is either prescribed by the contract, or, in default of contractual provision, the Scheme for Construction Contracts (England and Wales) Regulations 1998 (as amended) ("the Scheme") will apply. Under the Scheme, the payment due date is whichever is the later of (a) the expiry of 30 days following the completion of the work, or (b) the making of a claim by the payee.

The payment process is as follows:

  1. The Payment Notice is due from the Employer/Main Contractor or Employer's agent (such as the Architect, QS, Engineer or contract administrator ("Payer"), or, if the contract so provides, Contractor or Subcontractor ("Payee") within five days of the due date for payment (under the Scheme), or as otherwise provided by the contract. The Payment Notice must state the sum which is considered due and the basis on which that sum is calculated. A Payment Notice must be issued even if the sum due is zero, which will most commonly be the case during the defects liability period.
  2. If no Payment Notice is served, any preceding payment application issued by the Payee will stand as the Payment Notice, provided the payment application meets the requirements of a valid Payment Notice in that it states the sum which is considered due and the basis on which that sum is calculated.
  3. If no Payment Notice is issued, or the Payment Notice served is invalid, the Payee must immediately issue a Default Payment Notice stating the sum which is considered due and the basis upon which that sum is calculated. The service of a Default Payment Notice will extend the final date for payment by the number of days between the date on which the Payment Notice should have been served and the date of service of the Default Payment Notice.
  4. If the Payer wishes to dispute the sum that is stated to be due in the Payment Application, Payment Notice or Default Payment Notice, the Payer may serve a Payless Notice stating the sum which is considered to be due and the basis on which that sum is calculated. The Payment Notice is due seven days before the final date for payment under the Scheme, or as otherwise provided by the contract. The effect of the Payless Notice is to revalue the contractor's work as at the date of service of the Payless Notice, and the revaluation can take account of any LADs, set-offs or abatements.

ISG v Seevic

The facts

The Employer, Seevic College ("Seevic") retained ISG Construction Limited ("ISG") to carry out work under the terms of a JCT Design and Build Contract 2011 ("the Contract").

Under the terms of the Contract, ISG was required to submit monthly interim payment applications stating the sum it considered to be due and the basis upon which that sum was calculated. The final date for payment was fourteen days from the due date. The Contract further contained the usual procedure whereby Seevic was to serve a Payment Notice not later than five days after the due date stating the amount it considered to be due. If Seevic intended to pay less than the amount stated in the Payment Notice or interim application, it was to serve a Pay Less Notice no later than five days before the final date for payment.

ISG duly submitted its payment application and Seevic failed to either make payment or issue a Payless Notice, as a result of which ISG referred the dispute to adjudication ("the first adjudication"). In its Notice of Adjudication, ISG asked the adjudicator to determine the contractual value of its work as at the date of the payment application. The adjudicator found that ISG was entitled to the full amount it said was due in its interim payment application (which also stood as the Payment Notice) because Seevic had failed to comply with the notice procedure set out in the Contract and serve a Payless Notice.

Four days before the decision was issued in the first adjudication, in an attempt to circumvent its failure to serve a Payless Notice, and concerned that it might lose the first adjudication, Seevic issued a Notice of Adjudication ("the second adjudication"). Seevic's Notice of Adjudication asked the adjudicator to determine the value of ISG's works as at the date of ISG's payment application.

Seevic argued that, notwithstanding the first adjudication, there was a separate dispute in relation to the value of ISG's works that could be referred to adjudication. This separate dispute provided the adjudicator with jurisdiction to decide the value of ISG's works and, accordingly, the amount that was due to ISG. The second adjudicator (who incidentally also decided the first adjudication) found that the value of the works was lower than that stated in ISG's payment application, and ordered ISG to repay the difference between the sum it had received in the first adjudication and the true value of the interim payment application as determined by the second adjudication.

Following the two adjudications, ISG made an application for (i) summary judgment to enforce the first adjudicator's decision (on the basis that its interim payment application was agreed in the absence of a valid Payless Notice to the contrary under the Contract) and (ii) a declaration that the second adjudicator's decision was unenforceable (on the basis that the second adjudicator lacked jurisdiction).

The decision

Mr Justice Edwards-Stuart noted that ISG v Seevic was very similar to Watkin Jones & Sons Ltd v Lidl UK Gmbh [2001] EWHC 453 (TCC) which was concerned with the payment regime under the JCT Standard Building Contract with Contractor's Design, 1998 edition. In that case, the employer had also failed to comply with the notice provisions under the contract, and had used adjudication proceedings as a means of revaluing the contractor's payment application.

Mr Justice Edwards-Stuart followed the decision in Watkin Jones & Sons Ltd v Lidl UK Gmbh and held that, in the absence of fraud, contractors are entitled to the amount stated in their payment application regardless of the true value of that work in circumstances where the employer does not serve a valid Payless Notice. The first adjudicator had decided that the sum claimed in the payment application was the sum that was due to ISG, that sum had been agreed by Seevic in the absence of a valid Payless Notice, and the contractual notice regime prevented any argument to the contrary. Any decision otherwise would have the effect of completely undermining the statutory regime.

The judge pointed out that the contractor's only entitlement to payment is through the interim application machinery, or at the final account stage at the end of the project: the contractor has no entitlement to be paid the value of his work during the course of the works. Equally, Seevic had no contractual entitlement to a revaluation, let alone a financial award in consequence of it.

As regards the second adjudication, Mr Justice Edwards-Stuart found that the second adjudicator lacked jurisdiction as he had decided the same or substantially the same dispute as that which was decided in the first adjudication, and his second decision was therefore unenforceable.

Harding v Paice

The facts

Mr Paice and Ms Springall (together "Paice") were property developers who engaged MJ Harding ("Harding") to carry out residential works to two properties in Surrey under the terms of a JCT Intermediate Building Contract 2011 (with amendments) ("the Contract") in March 2013.

Work commenced in April 2013, but the relationship between the parties deteriorated and Harding gave notice to terminate the Contract in January 2014. The termination provisions provided that (i) Harding was required to submit a final account in respect of the work it had carried out, including the total value of the work properly executed, up to the date of termination (under Clause 8.12.3); (ii) Paice was to pay the amount that was "properly due" in respect of the account within 28 days of submission of its final account (under Clause 8.12.5); and (iii) Paice had the option to commence adjudication or litigation within 28 days of the issue of the Final Certificate, in which case the Final Certificate ceased to be conclusive (Clause 1.9).

Paice did not make payment, and the scenario was almost identical to that in ISG v Seevic in that Harding commenced adjudication proceedings claiming it was due the sum in its final account on the basis that Paice had failed to serve a valid Payless Notice, and Paice issued counter-adjudication proceedings in an attempt to revalue Harding's final account.

Rather than let Paice's counteradjudication go ahead, Harding applied for an injunction to prevent it from proceeding. Harding argued that the failure by Paice to serve a valid Payless Notice meant that the sum in its final account became the amount that was "properly due" under Clause 8.12.3 of the Contract. Harding further argued (in identical terms to ISG) in the alternative, that the substance of its account had been already referred to adjudication and it could therefore not be revisited.

The decision

Mr Justice Edwards-Stuart noted that Clause 8.12.5 was curious because, unlike the interim payment machinery in the Contract, it did not require the employer to pay the amount stated in the contractor's interim account. Instead, the employer was to pay the amount "properly due" in respect of the account, in order to reflect the reckoning process that is inherent in final accounts.

The judge further noted that the adjudicator appeared to have proceeded on the basis that if Paice wished to pay less than the sum in Harding's account, it had to serve a valid Payless Notice. In the absence of a valid Payless Notice, the adjudicator concluded that Paice had to pay the amount stated in Harding's account (incidentally, Mr Justice Edwards- Stuart came to the same conclusion in relation to Seevic's failure to serve a Payless Notice in ISG v Seevic, albeit the crucial point to note is that ISG v Seevic concerned an interim account, not a final account).

Mr Justice Edwards-Stuart disagreed with the adjudicator's conclusion in relation to Paice's failure to serve a valid Payless Notice. He pointed out that if the adjudicator's conclusion was correct, it would deprive the employer forever of the right to challenge the contractor's account, and in some cases (for example, if the contractor had considerably overvalued its account), the contractor would be permitted to receive a windfall to which he would otherwise not be entitled, and which the employer could never recover.

In terms of the jurisdiction argument (i.e. that the substance of Harding's account had already been referred to adjudication and could therefore not be revisited), Mr Justice Edwards- Stuart held that, as a matter of fact, the adjudicator had not determined the amount "properly due" to Harding under Clause 8.12.3. Instead, the adjudicator had reached the conclusion that the absence of a valid Payless Notice automatically meant that the sum claimed in the final account was due and had to be paid.

Some practice points

  • As yet, there is no reported case law as to the level of detail that might be necessary for the breakdown of the sum due and the basis on which the sum is calculated. You should therefore err on the side of caution and include a detailed breakdown with reference to the contractual matrix, rather than provide insufficient detail and risk your Notice being rendered invalid.
  • If the employer fails to serve a Payment Notice and the contractor serves (i) a valid payment application that qualifies as a Payment Notice or (ii) a Default Payment Notice, and the employer does not serve a valid Payless Notice, then the contractor's payment application/Payment Notice or Default Payment Notice will stand. The amount due to the contractor will be the sum which is set out in the payment application/ Payment Notice or Default Payment Notice. The Notices are in practical terms a "battle of the forms" in that the last served valid Notice will trump all previous Notices, and be determinative of the sum due.
  • If the employer fails to serve a Payless Notice, it is taken to be agreeing the value stated in the payment application/Payment Notice, other than where the final account falls to be considered.
  • If the employer fails to serve a valid Payless Notice, it is no longer entitled to seek a repayment of money paid to the contractor in subsequent adjudication proceedings by seeking a revaluation of the contractor's interim account.
  • As a matter of contractual entitlement, employers can only revalue the contractor's work on (i) the valuation dates for interim applications as determined by the contract upon service of a valid Payless Notice, or (ii) at the final account stage. This is so, irrespective of the true value of any work that might be carried out by the contractor at any given stage during the course of the project.
  • It is likely, following the decision in Paice v Harding, that Payless Notices will not apply to final accounts as this would have the effect of preventing the employer from challenging the contractor's final account.


The decision in ISG v Seevic on interim accounts is entirely in keeping with the "pay, now, argue later" ethos of the LDEDCA, and it ought to improve cash flow for contractors. It should also put an end to the current practice regarding interim accounts, whereby some employers who fail to serve a Payless Notice commence separate adjudication proceedings in order to argue that there is a separate adjudicable dispute in relation to the value of the contractor's works. Such tactics are a throwback to the previous regime that was concerned with the "amount due",2 as opposed to the amount that is said to be due on the face of the Payment Notice or Default Payment.

As for final accounts, following Harding v Paice, it is unlikely going forward that a failure by the employer to serve a Payless Notice will be critical to its ability to challenge the contractor's final account, as this would create a very unfair situation whereby the employer would be prevented from challenging the contractor's final account for all time.


1. See

2. The old system was mired with problems, including how abatements should be dealt with, and it often presented difficulties where the contract provided for payment against certificates but no certificates were ever issued.

Please click here to view previous issues of Insight

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Lisa Kingston
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.