NEC4 payment applications: what to submit, what gets certified and when you are paid
Updated: 10 hours ago
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
On an NEC4 contract the month's cash is largely decided before anyone opens the certificate. The assessment date arrives on its own schedule, whatever has been filed. The application is the only route by which the contractor's own figures reach the assessment, and since NEC4 the contract puts a price on leaving it out.
An NEC4 payment application is the contractor's statement, made before each assessment date, of the amount it considers due and how it was assessed. Without one, clause 50.4 holds the amount due at no more than the previous assessment. Certification follows within a week of the assessment date, and payment within three weeks of it.
That makes the application a document worth building properly, and most of what goes into it is not accounting. On Option A it is a statement about which activities are complete. On Options C and D it is a forecast of cost that only the programme can support. On every Option it lands inside a fixed sequence of certificate, notices and deadlines that runs the same way each month and waits for nobody.
How this cycle compares with the JCT forms is set out in the JCT payment cycle against NEC assessment dates, and why the programme decides when the money arrives is covered in the guide to NEC4 cashflow. This article takes the payment clauses themselves, 50 to 53, with secondary option Y(UK)2, the option for UK contracts subject to the Housing Grants, Construction and Regeneration Act 1996, and reads them from the contractor's side of the desk.
One definition first, because everything below hangs on it. The amount due is the Price for Work Done to Date, plus other amounts to be paid to the contractor, less amounts to be paid by or retained from it, and clause 50.3 fixes that structure for every main Option. What changes from one Option to the next is the first term, and that is where the application does its work.
The NEC4 payment timeline, from assessment date to final date
An assessment date is the date on which the project manager assesses the amount due, and the dates recur at the assessment interval stated in the Contract Data, usually a month or four weeks. Under clause 50.1 the project manager assesses at every one of them, whether or not anything has been submitted. Nobody's paperwork creates an assessment date, and nobody's paperwork moves one.
Everything else is counted from that date. The application goes in before it, under clause 50.2. The project manager certifies a payment within one week of it, under clause 51.1, and each certified payment is made within three weeks of it under clause 51.2, unless the Contract Data states a different period.
Secondary option Y(UK)2 lays the statutory dates over the same month. Payment becomes due seven days after the assessment date, and the final date for payment is fourteen days after that, again unless the Contract Data says otherwise. A party that intends to pay less than the notified sum must say so no later than seven days before the final date. On the default periods that means a certificate by day 7, the due date on day 7, the last day for a pay less notice on day 14 and the final date on day 21.
Two features of that clock catch teams out. The first is that it does not stop. A late application moves neither the assessment date nor anything counted from it. It simply arrives after the figure has been set.
The second is that the periods belong to the Contract Data, not to habit. Where the Contract Data states a different period for payment, every date after the due date moves with it, and a finance calendar copied from the last contract will be wrong in exactly the places that matter.
What an NEC4 payment application has to show
Clause 50.2 asks for three things. The application sets out the amount the contractor considers due at the assessment date. It includes details of how that amount has been assessed. And it is in the form stated in the Scope, which on a well-drafted contract means a template the project manager can check line by line against the programme and the records.
The details carry most of the weight. An application that states a number without its build-up gives the project manager nothing to consider and nothing to agree with, and it invites an assessment built from the project manager's own records instead. The build-up depends on the main Option, because each one defines the Price for Work Done to Date differently.
Main Option | Price for Work Done to Date | What the application has to prove |
A, activity schedule | The Prices for completed activities and completed groups of activities | Each activity claimed is complete as the activity schedule describes it |
B, bill of quantities | Completed quantities at the bill rates, with the completed share of each lump sum | The measured quantities, with the method and the records behind them |
C, D and E, cost based | Defined Cost forecast to be paid before the next assessment date, plus the Fee | Actual cost from the records, and a forecast the programme supports |
Option A: nothing for an activity that is nearly done
On Option A the Price for Work Done to Date is the total of the Prices for completed activities and completed groups of activities. An activity that is ninety per cent done earns nothing until it is complete, so the application is a list of completions, and the argument each month is about whether each one is finished as the activity schedule describes it.
That makes the structure of the activity schedule a cash decision taken at tender. It also means change work has no price in the schedule until its compensation event is implemented, which happens when the project manager accepts a quotation or notifies its own assessment, or when a quotation is treated as accepted. Until then, on Option A, the work is being done with no Price to be paid against.
Option B: quantities that survive measurement
On Option B the Price for Work Done to Date is the completed quantity for each item in the Bill of Quantities at its rate, plus the completed share of each lump sum. The application stands or falls on measurement, so it needs the measurement method and the records behind each quantity, in a form the project manager can test without remeasuring the job.
Options C, D and E: actual cost plus a forecast
On the cost-based Options the Price for Work Done to Date is the Defined Cost which the project manager forecasts will have been paid by the contractor before the next assessment date, plus the Fee. Two different things sit inside that sentence. One is cost already incurred, which has to be proved from accounts and records and which excludes Disallowed Cost by definition. The other is a forecast.
The forecast is the part many applications get wrong, and it is a programme question, not an accounting one. What will be built, delivered and paid for before the next assessment date depends on the work the programme shows in that window, and on the payment terms of the suppliers and subcontractors doing it. Materials delivered this month on thirty-day terms may be paid before the next date. The same materials on forty-five-day terms may not. An application that forecasts from last month's spend rather than next month's programme is likely to be cut, and the project manager will be right to cut it.
Where the programme and the cost record drift apart, the damage goes further than one month's forecast, as the QS and planner bridge on Options C and D shows. Spend that the programme no longer explains is spend at risk of being treated as Disallowed Cost.
No application, no increase: the lesser-of rule
NEC3 let the project manager assess without an application and attached no consequence to its absence. NEC4 changed that. Under clause 50.4 the project manager considers the contractor's application in assessing the amount due, and where the contractor has submitted none, the amount due at that assessment date is the lesser of the project manager's own assessment and the amount due at the previous assessment date.
In plain terms, a month without an application is a month without an increase. Work completed in that period earns nothing at that date, however well documented it is. Where the project manager's assessment comes out lower than last month's, which happens when an earlier figure is corrected or a deduction lands, the lower figure stands, and a reduction in the amount due is paid by the contractor to the client.
The money is not forfeited. The amount due is cumulative, so the next application can bring the missed work back in. But it arrives a full cycle late, and on a monthly interval that is a month of the contractor's own working capital spent financing the job. The delay is the contractor's own, so there is nothing to claim for it.
An application that arrives after the assessment date counts for nothing at that date. The assessment has already been made without it.
The certificate, corrections and interest
The project manager gives the contractor details of how the amount due has been assessed and certifies a payment within one week of the assessment date, under clause 51.1. The first payment is the amount due. Every later payment is the change in the amount due since the last certificate, so a certificate is always cumulative arithmetic, and an error carried in one month is carried in every month after it until someone corrects it.
Correction is the project manager's job. Under clause 50.6 a wrongly assessed amount due is corrected in a later payment certificate, and clause 51.3 adds interest on the correcting amount. That works in both directions. An underpayment corrected later carries interest to the contractor, and an overpayment corrected later carries interest back to the client.
Late money carries interest too. Under clause 51.2 interest is due on a certified payment made late, and on a payment that is late because the project manager did not issue a certificate it should have issued. Clause 51.4 calculates it daily, at the interest rate in the Contract Data, compounded annually. The sums are rarely large, but claiming them every time is how a payment culture gets set early in a job.
The practical discipline is short. Check the certificate in the week it arrives, against the application line by line, and raise any difference inside the same cycle. A difference left to next month has already cost a month.
Pay less notices under Y(UK)2
The notified sum is the sum stated in the payment notice, and the Housing Grants, Construction and Regeneration Act 1996, as amended by the Local Democracy, Economic Development and Construction Act 2009, requires it to be paid by the final date unless a valid pay less notice has been given. Under Y(UK)2 the project manager's certificate is the payment notice. If no certificate is issued, the contractor's application can stand in its place under section 110B of the Act, and its figure becomes the notified sum. Every month's application should therefore state a clear amount and its basis.
A party that intends to pay less than the notified sum notifies the other no later than seven days before the final date for payment, stating the sum it considers due and the basis on which it is calculated. The deadline is fixed, the content is fixed, and a notice that misses either is not a valid pay less notice.
The notice also has to answer the cycle it belongs to. In Advance JV v Enisca Ltd [2022] EWHC 1152 (TCC), on an NEC3 subcontract with Y(UK)2, the court held that a pay less notice issued against one application could not serve as the notice for an earlier one, even though the deadlines overlapped. Each cycle needs its own notice, on its own date.
The same discipline runs down the supply chain, often on different numbers. The subcontract in Advance JV made payment due twenty-one days after the assessment date and set the final date twenty-one days after that. A main contractor running its subcontract cycle off the head contract's diary will serve its notices on the wrong day.
Where the programme controls the cash
Three of the contract's payment mechanisms are programme mechanisms in disguise, and a commercial team that does not watch the programme will be surprised by all three.
The first programme and the quarter held back
Where no programme is identified in the Contract Data, clause 50.5 retains a quarter of the Price for Work Done to Date until the contractor submits a first programme showing the information the contract requires. Submission releases it, not acceptance, as the clause 31 guide's section on the 50.5 retention explains, so the first programme is a cash deliverable before it is anything else.
Compensation events and the Prices
On Options A and B a compensation event changes the Prices only when it is implemented, so the speed of quotation and assessment is the speed of payment for change. On Options C and D the cost of change work is paid as Defined Cost as it is incurred, and the event changes the target instead, which decides the contractor's share at the end. Either way, the quotation is where the money is built, as the guide to the NEC compensation event quotation sets out, and NEC compensation events and change support is there for the jobs where that queue has stalled.
Delay damages in the amount due
Where Option X7 applies, delay damages run from the Completion Date and are taken in the project manager's assessments as an amount paid by the contractor. If a compensation event later moves the Completion Date, clause X7.2 repays the damages with interest. The forecast in the programme neither starts nor stops them. The Completion Date does, as the comparison of JCT and NEC liquidated damages shows.
All three are the Programme-to-Money Bridge in its plainest form: the programme decides what is due, and the application reports it. A planner and a quantity surveyor working from different data dates will produce an application that argues with its own programme.
The final assessment under clause 53
NEC3 had no final account process. NEC4 added one, and it runs to a fixed clock. Under clause 53.1 the project manager assesses the final amount due no later than four weeks after the supervisor issues the Defects Certificate, or thirteen weeks after the project manager issues a termination certificate.
If the project manager does not, clause 53.2 lets the contractor issue its own assessment of the final amount due to the client, with details of how it was assessed. Under clause 53.3 the assessment becomes conclusive evidence of the final amount due under or in connection with the contract unless a party takes it into dispute resolution within four weeks.
Four weeks is short for a final account. The contractor that can use it is the one whose applications, certificates and compensation event records were kept in order through the job. Diary the Defects Certificate from the first month, because the clock that follows it is the last one the contract runs.
The author's view
In my view the lesser-of rule is one of the most consequential payment changes in NEC4, and one of the least noticed. It turned the application from a courtesy into a deadline. Payment trouble on NEC jobs often starts with a calendar rather than a disputed valuation: an application filed a day late, a certificate nobody checked within the week, a pay less notice served on the subcontract's dates instead of the head contract's.
The fix is organisational, not legal. The application should be built by the planner and the quantity surveyor together, from the same programme update, on the same data date, and it should go in before the assessment date every month, including the quiet ones. A contractor that does that has a defensible figure, a clean record and, when the time comes, a final assessment it can stand behind. A contractor that does not is arguing about money with the programme it submitted.
NEC4 payment application checklist
The Payment Application Checklist turns this article into the month's routine: the dates to diary, what each main Option's application has to prove, the checks on the certificate, and the notices that protect the cash. Two pages, no sign-up needed.
Frequently asked questions
What must an NEC4 payment application include?
Under clause 50.2 the contractor submits an application before each assessment date, setting out the amount it considers due, with details of how that amount has been assessed, in the form stated in the Scope. The details are what the project manager considers, and their build-up depends on the main Option, from completed activities on Option A to forecast Defined Cost on Options C and D.
What happens if a contractor does not submit an NEC4 payment application?
Under clause 50.4, where the contractor submits no application, the amount due at the assessment date is the lesser of the project manager's own assessment and the amount due at the previous assessment date. In practice the month brings no increase. The work is not lost, because the amount due is cumulative and the next application can include it, but the cash arrives a full cycle late.
What is the pay less notice deadline under NEC4 Y(UK)2?
Under Y(UK)2 payment becomes due seven days after the assessment date, and the final date for payment is fourteen days after that, unless the Contract Data states otherwise. A party intending to pay less than the notified sum must notify the other no later than seven days before the final date, stating the sum it considers due and how it was calculated: day 14 on the default periods.
How is the Price for Work Done to Date assessed on NEC4 Option C?
On Options C, D and E the Price for Work Done to Date is the Defined Cost the project manager forecasts will have been paid by the contractor before the next assessment date, plus the Fee. It combines cost already incurred, proved from records and excluding Disallowed Cost, with a forecast of payments before the next date, which depends on the programme and on supplier and subcontractor payment terms.
What is the final assessment under NEC4 clause 53?
Clause 53, new in NEC4, requires the project manager to assess the final amount due no later than four weeks after the supervisor issues the Defects Certificate, or thirteen weeks after a termination certificate. If the project manager does not, the contractor may issue its own assessment. The assessment becomes conclusive evidence of the final amount due unless a party takes it into dispute resolution within four weeks.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BEng in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Is your payment application built from the programme?
On NEC4 the application, the programme update and the cost forecast are one monthly job, and they hold up best when one team prepares them on one data date. NEC Planning Solutions provides live project controls that keep the programme and the cost forecast on the same data date, so each application has a build-up the project manager can check.
You don't need to send anything first. We reply to every enquiry within one working day. The scope and a fixed fee follow in writing within 48 hours of the first call.
