Almost every payment dispute involves at least one party working from the wrong date. Construction contracts use two, they do different jobs, and the gap between them is where the notices live. Establishing them from the contract rather than from the pattern of previous months is the first thing a payment and pay less notice review does.
The reason this goes wrong so often is that neither date is usually written on anything. Applications carry their own dates, certificates carry theirs, and the contractual dates have to be worked out from the particulars and applied to the calendar.
What the due date does
The due date is the point at which a payment becomes due under the contract. It is the anchor for everything that follows, because the periods for serving notices are normally measured from it.
It is usually fixed by reference to something in the contract particulars: a monthly cycle, a date in a schedule, or a period running from an application or from a valuation date. What it is not, in most contracts, is the date somebody happened to send an application.
Getting this wrong moves every subsequent deadline. A party that believes the due date is a week later than it is will serve notices a week late, and the notices will be ineffective however carefully they are drafted.
What the final date for payment does
The final date is when the money has to be with the other party. It is normally a stated period after the due date, and that period is set in the contract particulars rather than by general practice.
Between those two dates sit the notice deadlines. The payment notice has its own period measured from the due date; the deadline for a notice to pay less is normally fixed by reference to the final date.
Because the pay less deadline is tied to the final date, lengthening the payment period in a contract also moves that deadline. Amendments that change one frequently change the other without anybody noticing.
Establishing them from the contract
Start with the contract particulars. Find the provision that fixes the due date, the period to the final date, and the periods for each notice. Write them down as a sequence rather than as separate facts.
Then apply them to the actual calendar for the cycle in dispute, counting days as the contract counts them. Contracts differ on whether periods run in calendar days or business days and on how a deadline falling at a weekend is treated.
The result should be four dates for every cycle: due date, payment notice deadline, pay less deadline, final date. Once those exist on paper, most arguments about whether something was late answer themselves.
Do it for every cycle on the project rather than for the one in dispute. Patterns of lateness only become visible across a run of months, and a single cycle examined in isolation tells you much less than the sequence does.
Where the pattern misleads
On a long project the parties settle into a rhythm, and the rhythm becomes the assumed timetable. Applications go in around the same date each month, certificates come back around another, and nobody checks either against the contract.
That works until a cycle is contested. At that point the contractual dates reassert themselves, and a practice followed for eighteen months turns out to have no contractual basis.
The pattern is also vulnerable to changes in personnel. A new surveyor inheriting a project inherits the habit rather than the contract, and the habit is what they continue.
What goes wrong at the start and end of a project
The first cycle is the most error prone, because the rhythm has not been established and both sides are working from the contract for the first time. It is worth checking carefully rather than assuming it will settle down.
The last cycles are the second danger point. Payment after practical completion often follows a different mechanism from payment during the works, and the dates can change without anybody treating it as a change.
The same applies where the contract provides for payment to shift at a defined event. Those transitions are written into the contract and are easy to miss in the middle of a busy month.
The dates in a subcontract are not the dates above it
A subcontract has its own payment mechanism with its own due dates and its own notice periods. They are related to the main contract by commercial design rather than by law, and they do not move automatically when the main contract dates move.
That matters because a contractor operating two timetables will eventually apply one to the other. Subcontract notices served on main contract dates are a recurring source of avoidable exposure.
Where a project has several subcontracts with different terms, the only workable approach is a single table showing all of them. Carrying them in somebody’s head works until the month it does not.
Making the dates visible
The practical fix is unexciting. Build the four dates for every remaining cycle at the start of the project, circulate them, and keep them where the people serving notices can see them.
Where a contract is amended during the works, or where a payment term is varied, rebuild the table rather than adjusting the old one by hand. Amended terms are exactly where a dispute is most likely to begin.
Running the cycle properly month to month is ordinary commercial work rather than claims work. It belongs with client side quantity surveying and it prevents the overwhelming majority of these arguments.
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.