NEC4 Disallowed Cost: What Gets Struck Out (And How to Stop It)

The final account meeting opens with a number nobody asked for. Not a claim, not a compensation event, a deduction. £94,000 of Defined Cost the client's QS has flagged as disallowed: a plant hire invoice with no matching allocation sheet, a subcontractor payment with no linked instruction, three weeks of a foreman's time nobody can place on an activity. None of it was fraudulent. All of it was real cost. It just cannot be proved, and under NEC4 that is the same as it not existing.

Disallowed cost is not a penalty clause. It is the mechanism that makes cost reimbursable contracts work at all: the Contractor gets paid what the work actually cost, provided the cost can be shown to be Defined Cost, properly incurred, and not one of the specific categories NEC4 rules out. This post covers what actually falls into disallowed cost under Options C to E, the record gaps that turn legitimate spend into a deduction, and how to keep the number at zero.

What NEC4 actually defines as disallowed cost

Disallowed cost is defined in clause 11.2(25) (numbering shifts slightly by option), and it does two jobs at once. It rules out cost that should never have been incurred, and it rules out cost that cannot be substantiated, whether or not the work happened.

The categories that consistently catch people out:

Cost not justified by the Contractor's records. This is the big one. NEC4 does not ask whether the cost is plausible. It asks whether the accounts and records support it. Labour with no timesheet, plant with no hire ticket, subcontractor invoices with no corresponding measured work: all disallowed, whatever actually happened on site.

Cost that should not have been paid to a subcontractor or supplier under their contract terms. If you pay a subcontractor more than their own contract entitles them to, the excess does not pass through. The Project Manager is not obliged to fund your poor subcontract administration.

Cost of correcting Defects caused by the Contractor's failure to comply with the contract. Rework you caused is not reimbursable rework. The distinction that matters here is fault: a defect caused by a design the client provided is a different animal from one caused by your own workmanship, and the records need to show which is which.

Cost incurred only because the Contractor did not follow an accepted plan or a stated procedure, for example working out of sequence without notifying the Project Manager, or resourcing a task differently to how the Accepted Programme assumed.

The Fee itself, and cost already covered by it. Overheads the Fee percentage is meant to cover cannot also be claimed as Defined Cost. Double counting between the two is a common and entirely avoidable source of disallowance.

For the definitions of Price for Work Done to Date and how Defined Cost feeds the monthly certificate, the NEC4 payment guide covers the assessment mechanics. This post is about the layer underneath: what makes cost count as Defined Cost in the first place.

Why real spend gets struck out anyway

Almost none of the disallowed cost QSs actually fight over is fraud or padding. It is spend that happened, cost the business, and simply was not proven to the standard the contract requires. Three patterns explain most of it.

The paper trail and the site record tell different stories. A plant sheet says an excavator was on site for six weeks. The diary mentions it twice. The Project Manager cannot tell whether the machine sat idle for four of those weeks or worked flat out, so the safe assessment is the low one.

Cost gets allocated to the wrong bucket, or no bucket at all. A labour gang splits its time across three activities in a day. If the timesheet just says "site works" with no activity code, none of that labour can be tied to a specific compensation event or Defined Cost head. It sits there, unclaimable, until someone reconstructs it from memory months later.

The record exists somewhere, just not where the reviewer can find it. Delivery notes in a site office folder. Plant tickets photographed on a supervisor's phone and never uploaded. Subcontractor certificates sitting in an inbox. The evidence is real. It is just invisible to whoever is assessing the application, and invisible evidence gets treated as absent evidence.

None of these are disputes about entitlement. They are gaps between money that was spent and money that can be shown to have been spent, on the day it mattered rather than months later under final account pressure.

What keeps Defined Cost inside the boundary

Four things separate cost that survives scrutiny from cost that gets struck out.

A cost code on everything, from the day it is incurred. Every timesheet, plant ticket, delivery note and subcontractor certificate needs to carry the activity or compensation event it belongs to, logged at the point of entry, not reconstructed afterwards.

A record that matches the site diary. If the diary says the piling rig worked a nine hour shift and the plant sheet says twelve, that gap is exactly what a client's QS goes looking for. Consistency between the diary, the timesheets and the invoices is worth more than any single strong piece of evidence.

A visible separation between the Fee and Defined Cost. Anything the Fee percentage is meant to cover, general management, head office overhead, needs to stay out of the Defined Cost claim entirely. Mixing the two invites a line by line strip out that costs more than it saves.

Substantiation attached at the point of application, not promised for later. "Available on request" is functionally the same as absent. A reviewer with a fixed assessment window has no reason to chase down evidence you could have attached in the first place.

This is where the QS AI Agent does the actual work. Gather reads every site diary entry as it lands, ties it to the cost code and activity behind it, and keeps the Defined Cost trail assembled and consistent in real time, rather than reconciled under deadline pressure at final account. When a client's QS asks where a cost came from, the answer is already sitting behind the line, not scattered across a site office and four phones. If you want to see what a disallowed cost defence looks like when it is built from live site records rather than reconstructed after the fact, book a 15-minute demo.

Common mistakes that turn real spend into a deduction

• Letting timesheets record hours without an activity or cost code, so the labour cannot be matched to anything specific later.
• Treating disallowed cost as a final account problem, something to argue over at the end, rather than a monthly discipline that keeps the number at zero throughout.
• Allowing the diary and the cost records to drift, so the two accounts of the same week contradict each other.
• Mixing Fee-covered overhead into the Defined Cost claim, which invites scrutiny of everything else on the same application.
• Assuming a subcontractor's invoice is automatically Defined Cost, when it needs its own check against what their contract actually entitles them to.

A worked example

A £22m highways package under NEC4 Option C. At final account, the client's QS reviews the cumulative Defined Cost and flags £94,000 as disallowed: £41,000 of plant hire with no matching allocation, £30,000 of labour with no activity code, and £23,000 of subcontractor cost exceeding what their own contract allowed.

Run it the usual way. The commercial team spends two weeks trying to reconstruct six months of plant usage from delivery dockets and a foreman's memory. Half the plant hours get restored with evidence found late. The labour cost stays disallowed because nobody can now say which activity absorbed which shift. The subcontractor overpayment is genuine and gets written off. Net recovery: £51,000 of the £94,000, after three weeks of unbilled commercial time spent proving it.

Run it record-referenced instead. Every plant hour and every labour shift was logged against an activity code in the site diary the week it happened. The QS responds to the £94,000 flag within four days: plant hours matched hour for hour to the diary, labour hours matched to activity codes, and only the genuine subcontractor overpayment conceded. Recovery: £71,000 of the £94,000, the maximum that was ever going to be defensible, resolved in days rather than weeks.

Same contract, same client QS, same flagged amount. The only variable was whether the record existed at the point of spend or had to be rebuilt from memory five months later.

Frequently asked questions

What is disallowed cost under NEC4?

Disallowed cost is cost that is not accepted as part of the Contractor's Defined Cost, defined under clause 11.2(25). It covers cost not justified by the Contractor's records, cost that should not have been paid to a subcontractor under their own contract terms, cost of correcting Defects the Contractor caused, and cost incurred only because the Contractor did not follow an accepted plan or procedure.

How is disallowed cost different from Defined Cost?

Defined Cost is the amount of cost the Contractor is entitled to be reimbursed for the actual resources used, calculated per the contract's rules for people, Equipment, Plant and Materials, and Subcontractors. Disallowed cost is the subset of that spend which NEC4 excludes because it either should not have been incurred or cannot be justified by the Contractor's records, so it is deducted from the total before payment.

What records prevent cost being disallowed?

Cost survives scrutiny when every element carries a cost code and activity reference logged at the point of spend: timesheets tied to specific activities, plant tickets matched to days actually worked, subcontractor payments checked against their own contract entitlement, and materials evidence tied to delivery. A site diary that matches the cost records, rather than contradicting them, is what usually decides a disputed line.

Can disallowed cost be challenged after it is deducted?

Yes. Disallowed cost deductions are assessments, not final rulings, and can be challenged with better substantiation at the next assessment or escalated through the standard NEC4 dispute mechanisms if unresolved. The strength of that challenge depends entirely on whether contemporaneous records exist to support the disputed spend. See our guide to NEC4 payment disputes for how that escalation plays out.

The bottom line

Disallowed cost is not a judgement on whether you did the work. It is a judgement on whether you can prove it. The reviewer assessing your Defined Cost is not looking for the biggest number, and they are not looking for perfection either. They are looking for a cost code on every line, a diary that agrees with the timesheet, and substantiation that was there when the application went in, not promised for later.

Get that right every month and there is nothing left to strip out at final account. The Defined Cost you claim is the Defined Cost you keep.

Want a Defined Cost trail that stays inside the boundary from day one? Gather links every site diary entry to your programme and cost codes as the work happens. Book a 15-minute demo.

Source: Gather Insights, the AI-powered site diary and commercial record management platform for UK construction.