Getting paid: the JCT payment cycle vs NEC assessment dates
Updated: 8 hours ago
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
JCT anchors payment to an Interim Valuation Date and keeps the programme out of it. NEC anchors payment to an assessment date and wires the programme in: where no programme is identified in the Contract Data, clause 50.5 retains a quarter of the price for work done to date until a first programme is submitted.
Cash is the part of the transition nobody rehearses. Teams moving onto NEC will run training on compensation events and early warnings, then find in month two that the money arrives on a different rhythm, through different notices, against different deadlines, and that the finance calendar built for the last job is quietly wrong.
One caution before the comparison, because it is the mistake most articles on this subject make. JCT is not a single payment mechanism. Under the Standard Building Contract the contract administrator issues an interim certificate and the contractor may apply but does not have to. Under Design and Build, clause 4.7.3 requires the contractor to make an interim payment application before each Interim Valuation Date, which JCT itself describes as a payee-driven mechanism. The two forms share a calendar and differ on who is obliged to act. Which one a team is arriving from changes what NEC feels like.
The shapes are close. All three run on a fixed cycle, all three produce a sum that becomes payable, and for UK construction contracts to which the Housing Grants, Construction and Regeneration Act 1996 applies, all three carry payment provisions drafted to operate inside that statutory regime. The differences sit in the detail, and the detail is where the diary entries live.
The four things that change at once on the move between forms are set out in the guide to what actually changes when a contractor moves from JCT to NEC. Why the programme behaves as a financial instrument under NEC rather than a reporting artefact is covered in the piece on NEC4 cashflow and the construction programme. This article takes the payment cycle itself, set against NEC4 ECC with secondary option Y(UK)2.
The clause that makes the two systems structurally different is 50.5. It is not a payment control. It is a planning control with a commercial consequence, and that is the whole story of this article.
What the JCT payment cycle actually does
JCT 2016 built its payment provisions around one defined term, the Interim Valuation Date. The first date and the interval between them are fixed in the Contract Particulars before anyone reaches site, and the same date runs down the supply chain, so main contractor, subcontractor and sub-subcontractor sit inside a single thirty-day window.
From that date the arithmetic is fixed and common to both forms. The due date falls seven days after the Interim Valuation Date. The payer's notice follows not later than five days after the due date. The final date for payment is fourteen days after the due date, and any pay less notice must arrive not later than five days before it.
Standard Building Contract: the certifier acts
Under clause 4.10.1 the contractor may apply, not later than the Interim Valuation Date, stating the sum it considers will be due and the basis of the calculation. It does not have to. Valuing the works is the quantity surveyor's job and the contract administrator issues the certificate, so a contractor that submits nothing still gets valued and still gets certified.
Design and Build: the contractor must act
Clause 4.7.3 reverses that. The contractor is required to make an interim payment application before each Interim Valuation Date, and the cycle is built around it. Apply late and the due date moves with the application, becoming seven days after the employer receives it. Fail to apply and there is nothing for the cycle to run on. This is the form most contractors reading this will have come from, and its habits transfer to NEC better than the Standard Building Contract's do.
Notice what plays no part in either version. The programme. A JCT contractor can be four months adrift of its master programme, or never have produced one at all on Design and Build, and the payment cycle grinds on untouched.
What NEC assessment dates actually do
NEC replaces the valuation date with the assessment date, and the distinction worth holding onto is that the assessment date exists on its own. It is fixed in the Contract Data, the first one and the interval, commonly monthly or four-weekly. Nobody's paperwork creates it and nobody's paperwork moves it. The project manager assesses the amount due at each one whether or not anything has been submitted.
What the contractor contributes is the application. Clause 50.2 has it submitted before each assessment date, including details of how the amount has been assessed and in the form stated in the Scope, and the project manager considers that application when assessing the amount due. The application feeds the assessment rather than triggering it. That is a small distinction with a large consequence: a late application does not delay the assessment date under NEC the way a late application moves the due date under Design and Build. The date arrives regardless, and the assessment gets made without the contractor's figures in it.
The project manager then certifies within one week of the assessment date under clause 51.1, and NEC4 added a duty NEC3 did not carry: the certificate has to show how the amount was assessed, not merely state it. Payment follows within three weeks of the assessment date under clause 51.2, unless the Contract Data says otherwise.
On UK contracts, secondary option Y(UK)2 layers the statutory machinery on top. The due date lands seven days after the assessment date, the final date for payment fourteen days after that, and a pay less notice has to be served no later than seven days before the final date.
The differences that matter sit in four places.
JCT 2016 | NEC4 with Y(UK)2 | |
Contractor's application | Optional (SBC). Required (DB) | Required, before the assessment date |
If the application is late | Under DB the due date moves with it | The assessment date does not move |
Pay less notice | 5 days before the final date | 7 days before the final date |
Programme link to payment | None | A quarter retained until the first programme is submitted |
The JCT payment cycle versus NEC assessment dates: three shifts
Three shifts do the damage, and only one of them is obvious.
Who is obliged to act, and what happens if nobody does
Coming from the Standard Building Contract, this is the real change: the application stops being optional and starts being the only route by which the contractor's own figures enter the assessment. Coming from Design and Build, the habit already exists and transfers well, but the failure mode is different. Under Design and Build a late application drags the due date with it, which is painful but self-correcting. Under NEC the assessment date holds still and the project manager assesses anyway, on whatever information is to hand. The team has not delayed the payment. It has forfeited its influence over the figure.
The pay less window closes two days earlier
This one is small, mechanical and expensive, and it is worth being precise about what moves. The overall cycle is not two days shorter. What changes is the deadline for a pay less notice measured back from the final date for payment: five days under JCT, seven under Y(UK)2. A main contractor serving down its own NEC subcontracts on the JCT figure serves on day six, and finds the notice worthless and the full applied sum payable. It works the other way too. A pay less notice landing six days out on a contractor's own account is out of time, and worth challenging rather than absorbing.
The programme is wired into the money
Here is the structural difference, and it needs stating precisely because the precision is the point. Where no programme is identified in the Contract Data, clause 50.5 retains one quarter of the price for work done to date in assessments of the amount due, until the contractor has submitted a first programme to the project manager for acceptance showing the information the contract requires. Two conditions matter. The retention only bites where the Contract Data does not already identify a programme. And what releases it is submission of a compliant programme, not acceptance of one. A contractor waiting on the project manager's decision has already done what the clause asks. What a compliant programme has to carry is set out in the guide to NEC clause 31 programme acceptance.
JCT has nothing comparable, which is why a JCT-trained commercial team does not instinctively read programme submission as a cash event. Under NEC it can be the largest single cash event of the first month, and it turns on whether the planner filed a compliant programme rather than on anything the quantity surveyor does.
The proportion is easier to see than to argue with.
The one habit that does transfer
Not everything a JCT team knows about payment is wasted. The most valuable instinct survives the move intact.
Where the Act applies, both regimes run the same notice logic. Under Y(UK)2 the project manager's certificate serves as the payment notice. If it does not arrive, or arrives out of time, the contractor's application can become the notified sum under section 110B of the Act, and the full applied amount falls due whatever anyone thinks of the valuation behind it. That is the same exposure a JCT team already understands, running on a different calendar.
So the discipline transfers even though the dates do not. Apply before the assessment date, show the assessment, and diary the certificate deadline as carefully as the payment deadline. How the same evidence discipline works on the change side sits in the guide to building the money in an NEC compensation event quotation.
Summary
JCT and NEC both pay on a fixed cycle, and where the Act applies both punish a missed notice in much the same way. What NEC does differently is hold the assessment date still regardless of who has filed what, close the pay less window two days earlier, and tie a quarter of the early money to a programme that JCT would never have required.
The last of those is the one that catches teams, because it is not a commercial control at all. It is a planning control with a commercial consequence, it falls due in the first month, and it is settled by a submission rather than a negotiation. What that discipline looks like across a full delivery is set out in the carbon capture plant case study. Rebuilding the finance calendar is the easy half. Learning to read programme submission as a cash event is the half that takes longer.
Frequently asked questions
When is payment due under an NEC4 contract?
Clause 51.2 requires each certified payment to be made within three weeks of the assessment date, unless the Contract Data states a different period. On UK contracts under secondary option Y(UK)2 the due date is seven days after the assessment date and the final date for payment is fourteen days after that.
Does a contractor have to apply for payment under NEC4?
Clause 50.2 provides for the contractor to submit an application before each assessment date, showing how the amount was assessed. The project manager considers it when assessing the amount due. The assessment happens either way, so a contractor that does not apply has not delayed payment, it has left the figure to the project manager.
Is a JCT payment application compulsory?
It depends on the form. Under the Standard Building Contract the contractor may apply under clause 4.10.1 but is not required to, because the contract administrator issues the interim certificate. Under Design and Build clause 4.7.3 requires an application before each Interim Valuation Date, and a late one moves the due date.
What is the pay less notice deadline under NEC4?
Under secondary option Y(UK)2 a pay less notice must be served no later than seven days before the final date for payment. JCT allows until five days before. The overall cycle is not shorter; the pay less window simply closes two days earlier, and teams moving between the forms often carry the JCT figure across.
Can NEC withhold payment for a missing programme?
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 has submitted a first programme for acceptance showing the information the contract requires. The trigger for release is submission, not acceptance. JCT contains no equivalent.
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 a quarter of your first payment sitting behind a programme?
Clause 50.5 makes the first programme a cash flow question rather than a planning deliverable. What releases the retention is a programme containing the information the contract requires, submitted for acceptance, so the work is getting the content right first time rather than chasing a decision afterwards. Clause 31 and 32 compliance support does exactly that.
