The application went in on time. The certificate came back £310,000 light, with a one-line explanation: insufficient substantiation. Now you have seven days of cash burn for every week the argument runs, a director asking why the forecast moved, and a Project Manager who assessed what he could see, not what you spent.
Most NEC4 payment disputes are not really disputes about money. They are disputes about proof. This guide covers how the payment machinery at clauses 50 and 51 actually works, what the Y(UK)2 Construction Act overlay changes, where the smash and grab risk sits on both sides, and why the team with the better records almost always wins.
How payment works under NEC4: clause 50 and 51
The core mechanism is short. Under clause 50, the Project Manager assesses the amount due at each assessment date. 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 the Contractor. Under clause 51, the PM certifies payment within one week of each assessment date, and payment follows within three weeks of the assessment date unless the contract says otherwise.
Two features matter more than QS teams tend to notice.
First, the assessment is the PM's job, not yours. NEC4 introduced the Contractor's application at clause 50.2, and on a Y(UK)2 contract that application has real legal weight, but the contractual assessment still belongs to the PM. The PM assesses what the records support. If your application says £2.1m and the evidence in front of the PM supports £1.8m, the certificate says £1.8m, and the contract has worked exactly as written.
Second, the definition of Price for Work Done to Date shifts by main option. On Options A and B it follows completed activities or quantities. On Options C to F it follows Defined Cost, which means the same records that defend you in a disallowed cost audit are the records that get you paid each month. One evidence base, two mechanisms drawing on it.
For the full clause-by-clause timeline, assessment dates and interest provisions, the NEC4 payment guide walks through the machinery in detail. This post is about what happens when that machinery produces a number you do not accept.
What Y(UK)2 changes: the Construction Act overlay
On UK projects, NEC4 is almost always used with secondary Option Y(UK)2, which amends the payment clauses to comply with the Housing Grants, Construction and Regeneration Act 1996. This overlay is where payment disputes are actually fought.
Y(UK)2 turns the Contractor's application into the trigger. The application becomes the basis of the notified sum: if the PM fails to certify, the sum you applied for is, by default, the sum that is due. The certificate under clause 51 acts as the payment notice, stating the sum the payer considers due and the basis on which it is calculated.
Then comes the document that decides most disputes: the pay less notice. If the client intends to pay less than the notified sum, a pay less notice must be issued before the prescribed deadline, stating the sum considered due and the basis of the calculation. No valid pay less notice, no reduction. The notified sum must be paid by the final date for payment, whatever the payer thinks of the underlying merits.
That is the smash and grab mechanism, and it cuts both ways.
For the Contractor, a missed or defective payment notice and pay less notice means the full applied sum is payable, and adjudication to enforce it is quick and hard to resist. But the entitlement is only as strong as the application. A vague application, one that does not clearly state the sum and the basis of calculation, can fail to qualify as a valid application at all, and the whole position collapses.
For the client, a missed pay less notice means paying an application they believe is overstated, then fighting to get the money back through a true value adjudication afterwards. Cash flows the wrong way first.
The practical consequence for a QS is blunt. Your application is a legal document, not a spreadsheet summary. Every month it needs the sum, the basis, and the substantiation behind both, because on the month the notices go wrong, that application is the only thing standing.
Where payment disputes are actually decided: the records
Strip away the procedure and nearly every NEC4 payment dispute reduces to the same three questions.
Can you substantiate the application? On Options C to F, that means Defined Cost with the chain intact: timesheets to cost codes, plant hire records to the days claimed, subcontractor payments to assessed work. On Options A and B it means progress evidence, completed activities you can demonstrate rather than assert. An application built on a percentage-complete gut feel invites an assessment built on the PM's gut feel, and the PM's gut feel is the one on the certificate.
Can you challenge the assessment? When the certificate comes back short, you need to identify exactly which lines moved and why. A PM who writes "insufficient substantiation" against £310,000 has made a specific claim about specific records. If you can produce the diary entry, the timesheet and the delivery ticket behind each queried line within days, the assessment usually corrects at the next certificate. If you need three weeks to assemble the same evidence, you are funding the gap in the meantime, and the correction argument gets tangled with the next application.
Does the story hold up in adjudication? If it does escalate, the adjudicator is not on site and never was. They decide on documents. Contemporaneous records, made at the time by the people doing the work, carry weight that a witness statement written eight months later never will. The party that can show a daily, dated, consistent record of what happened tends to win, because the other party is asking the adjudicator to prefer recollection over evidence.
Notice what is missing from all three questions: who was right about the money. Payment disputes are decided on proof, and proof is built months before the dispute exists.
This is the layer where the QS AI Agent earns its keep. Gather reads every site diary entry as it lands, links it to the programme activity and the cost code, and builds the substantiation trail behind each application line as the work happens. When a certificate comes back light, the evidence behind every queried line is already assembled, not scattered across spreadsheets and someone's inbox. If you want to see an application substantiation pack built from live site records, book a 15-minute demo.
Common mistakes that turn a short certificate into a long dispute
- Submitting applications without a clear stated sum and basis of calculation, so the application may not qualify as a valid notified sum at all.
- Treating the application as a summary and holding the backup "in case it's asked for", which guarantees the PM assesses on less than you spent.
- Missing the assessment date rhythm, so applications land late and lose their Y(UK)2 status for that cycle.
- Letting an under-certification ride for two or three cycles before challenging it, by which point the gap is six figures and the trail is cold.
- Assuming a strong site story equals a strong paper story. Adjudicators read documents, not memories.
- Chasing a smash and grab on a technically defective notice while your own application would not survive the same scrutiny.
A worked example
Take a £45m rail enhancement under NEC4 Option C with Y(UK)2, monthly assessment dates, Defined Cost running at about £1.9m a month. At month eleven, the Contractor applies for £2.14m. The certificate comes back at £1.83m. The PM's stated basis: insufficient substantiation on labour across two possession weekends, and plant claimed against a package where the diary shows standing time.
Run it the usual way. The commercial team spends nine working days pulling timesheets from the labour agency, chasing the possession shift records from a supervisor's notebook, and reconstructing why the piling rig stood for four days. By the time the pack is together, the next application is due, the two arguments merge, and the £310,000 gap rolls forward. Cash is funded at the Contractor's cost for two more cycles. Legal gets asked about adjudication. The relationship with the PM sours over what was, underneath, a filing problem.
Now run it record-referenced. The possession shifts were logged in the site diary on the night, each entry tied to the activity and the labour on shift. The piling rig standing time carries a diary entry recording the instruction that held it there, which also happens to be the evidence for the compensation event. Within three days the Contractor issues a line-by-line response: every queried labour hour matched to a dated record, the standing time shown as instructed. The PM corrects £285,000 of the £310,000 at the next certificate and the residual £25,000 is a genuine measurement difference, resolved in one meeting. No adjudication, no rolled-forward gap, one month of funding cost instead of three.
Same project, same money, same PM. The difference was whether the proof existed on the night or had to be manufactured after the certificate.
Frequently asked questions
How does payment work under NEC4 clause 50 and 51?
The Project Manager assesses the amount due at each assessment date under clause 50, based on the Price for Work Done to Date plus other amounts due to the Contractor, less amounts due from the Contractor. Under clause 51 the PM certifies payment within one week of the assessment date, and payment is made within three weeks of the assessment date unless the contract states a different period. On UK projects, secondary Option Y(UK)2 overlays this with the Construction Act notice regime.
What does Option Y(UK)2 add to NEC4 payment?
Y(UK)2 amends NEC4 to comply with the Housing Grants, Construction and Regeneration Act 1996. The Contractor's application becomes the basis of the notified sum, the PM's certificate acts as the payment notice, and the client must issue a valid pay less notice before the deadline to pay less than the notified sum. If the notices are missed or defective, the notified sum is payable in full regardless of the underlying merits.
What is a smash and grab adjudication under NEC4?
A smash and grab adjudication enforces payment of the notified sum where the payer failed to serve a valid payment notice or pay less notice in time. The adjudicator does not value the works; they check the notices. If the notices fail, the applied sum is due. The payer's remedy is to pay first and then pursue a separate true value adjudication to correct any overpayment.
Why do records decide NEC4 payment disputes?
Because every stage of the dispute is an evidence test. The PM assesses what the records support, a challenge to an under-certification succeeds by producing the documents behind each queried line, and an adjudicator decides on contemporaneous records rather than recollection. The party with dated, consistent, activity-linked site records usually wins, whichever side of the argument they are on.
What should an NEC4 payment application include?
A clearly stated sum, the basis on which it is calculated, and substantiation for each element: on Options C to F, Defined Cost evidence such as timesheets, plant records and subcontractor assessments; on Options A and B, evidence of completed activities or quantities. Under Y(UK)2 the application can become the notified sum, so it needs to stand alone as a document that would survive scrutiny in adjudication.
The bottom line
NEC4 payment disputes look procedural. Notices, deadlines, certificates. Underneath, they are evidence contests, and the evidence is created long before the argument starts. The application that gets paid is the one the PM can verify. The challenge that succeeds is the one that answers the query with a dated record inside a week. The adjudication that wins is the one built on what the diary said that night, not what the team remembers now.
Get the notices right, always. But the notices only protect a position; they do not build one. The position is built on site, one record at a time.
Ready to put a substantiation trail behind every application line? Gather links every site diary entry to your programme and cost codes, so the proof exists the day the cost does. Book a 15-minute demo.
Source: Gather Insights, the AI-powered site diary and commercial record management platform for UK construction.
.webp)
