A main contractor receives applications from subcontractors and makes one upwards, under two sets of provisions that are related commercially and independent contractually. Keeping both running correctly is a monthly administrative task that is frequently underestimated, and it is where a payment and pay less notice review most often finds the problem.
The exposure is not evenly distributed. Missing a notice downwards creates an immediate liability to pay a figure you did not intend to pay. Missing one upwards usually only costs the chance to be paid more this month.
Two mechanisms, not one
The subcontract has its own due dates, its own notice periods and its own final date for payment. They are set by the subcontract rather than derived from the main contract, even where they were drafted to sit alongside it.
Where the main contract is amended during the works, the subcontract dates do not move with it. Where a subcontract is signed later than the main contract, it may carry a different timetable altogether.
The practical consequence is that a contractor cannot operate one calendar. It needs the main contract dates and a separate set for each subcontract, which on a busy project means a dozen timetables running at once.
Businesses that handle this well treat it as a scheduled process rather than as something the surveyors remember. The ones that handle it badly discover the problem in a month when somebody is on holiday.
Pay when paid does not generally work
Arrangements making payment to a subcontractor conditional on the contractor being paid are restricted in the United Kingdom, subject to limited exceptions. Whether a particular clause is effective is a legal question rather than a commercial one.
What matters commercially is that a contractor should not assume such a clause will protect it. Operating the subcontract mechanism properly is the reliable protection; relying on a conditional payment clause is not.
The same applies to informal versions of the same idea. Telling a subcontractor that payment will follow when the client pays is not a notice and does not affect what the subcontract requires.
Where cash genuinely is the constraint, that is a conversation to have openly rather than a reason to let a deadline pass. The deadline passing does not improve the cash position; it fixes a higher figure.
Where the chain actually breaks
The commonest point is assessment capacity. A contractor receiving fifteen applications in the same week has to assess all of them before separate deadlines, and the ones assessed last are the ones that go wrong.
The second is personnel. Subcontract notices are often handled by whoever is available rather than by a named person, and the responsibility therefore sits nowhere in particular.
The third is the main contract certificate arriving late or lower than expected, which creates pressure to cut subcontract payments after the point at which they could properly be cut.
All three are operational rather than contractual, which is good news: they can be fixed by process without renegotiating anything.
Cutting an application correctly
Where a subcontractor’s application is overstated, the answer is a notice served in time stating what is considered due and why. The answer is not a reduced payment accompanied by an explanation afterwards.
This is the single most expensive habit in subcontract administration. Paying less than the notified sum without having served the required notice creates an immediate liability for the difference, whatever the merits of the valuation.
The discipline needed is modest: assess early enough to notify, and notify every month rather than only in the contentious ones. The cost is an hour a month per package and the exposure it removes is considerable.
Contra charges and set off
Deductions for defective work, delay or attendance are frequently the reason a subcontract payment is reduced, and they are frequently applied without the notice the subcontract requires.
A deduction that was not notified in the manner and by the time the subcontract requires is exposed, regardless of whether the underlying charge is justified. That is a painful way to pay for somebody else’s defective work.
Where contra charges have accumulated across a package, the position is usually better addressed as a whole than cycle by cycle, which makes it final account work rather than a payment question.
What good administration looks like
A single table carrying every package, its due dates, its notice deadlines and its final dates. A named person responsible for each. Assessment scheduled early enough to leave room for the notice.
Standing templates for the notices, so that the monthly task is filling in a figure and a basis rather than drafting from scratch.
And a filing convention that keeps each package’s cycle documents together, because the alternative is reconstructing them under pressure months later.
None of this is sophisticated. It is the difference between a process that runs itself and one that depends on somebody remembering, and the second kind fails in exactly the months when the business can least afford it.
Why it is worth the effort
Subcontract payment administration is unglamorous and it protects more money than almost anything else a commercial team does. The sums at risk in a single missed cycle across a package of any size are considerable.
It also protects relationships. Subcontractors paid correctly and predictably price better and argue less, which shows up in the next tender rather than in this month’s account, and it compounds across a supply chain you use repeatedly.
The wider discipline is ordinary commercial management, and on the client side the same mechanism is run by a client side quantity surveyor with the same monthly rhythm.
Money held back on a payment cycle?
A payment and pay less notice review examines one cycle end to end: the application, the notices, the dates and what the contract actually required of each party.