An application for payment
that does not come back rejected.
Four reasons account for most rejections, and none of them is the price. What the document has to contain, what has to sit behind it, and the date that matters more than the total.
Published ·5 min read·Written by Unibuild
An application for payment states the sum claimed for a valuation period and the basis on which it is calculated, supported by measure, instructions and records. Where the contract provides for it, a properly made application can stand as the payment notice, which makes the sum in it the notified sum the payer has to serve a valid pay less notice to reduce.
It is not an invoice, and the difference is the whole article
An invoice says you owe me this. An application says this is what has been built, here is what it is worth under the contract rates, and here is the evidence.
That distinction has a statutory consequence. Under the Construction Act, the notified sum for a payment cycle is the figure in whichever payment notice validly stands. Normally that is the payer's notice. But where the payer fails to give one, section 110B allows the payee's notice to take its place, and where the contract provides for the payee to make an application, that application can be the notice.
So a well-made application is not a request that somebody may or may not grant. It is the document that sets the number the other side must actively knock down, in writing, before a deadline. A badly made one is a request. The difference costs nothing to close and it is worth a great deal.
Firms rewrite their application every month and never once read the clause that says what an application has to be. That clause is where the money is.
What it has to contain
Six things, and the order matters less than the completeness.
- The reference and the period. Application number, the valuation period it covers, and the date it is made. The date drives every subsequent deadline, so it is not administrative.
- The sum claimed, and how it was reached. Not a total. The build-up: measured work against contract rates, variations valued separately, materials on site if the contract allows them, less previous payments, less retention. The statutory language is the sum and the basis on which it is calculated, and a total with no basis fails that test.
- Measured quantities that somebody can check. Cumulative to date and this period, against the rate. Where the work was quoted through a priced schedule, the application should be measured against those same sections rather than re-described.
- Variations, itemised with their instruction reference. Each one separately, with the date and source of the instruction, not folded into a general uplift.
- Retention shown, not netted silently. The percentage, the sum this period and the cumulative figure held. A retention figure that only appears as a smaller total is a figure nobody is tracking.
- The supporting pack. Signed dayworks, delivery notes, timesheets, site records, photographs where they evidence progress. This is the half most applications are missing and the half that decides whether it is argued.
The four reasons applications come back
In our experience the reasons cluster, and none of them is the price.
- It was late against the contract dates. An application submitted after the period the contract allows can be treated as belonging to the next cycle, which moves your money a month and hands the payer a clean answer that has nothing to do with your work.
- The measure is unsupported. A quantity with no record behind it invites a lower quantity from the other side, and the argument is then between two assertions rather than about a document.
- A variation has no instruction behind it. The commonest single rejection, and the subject of its own article, because the answer is about evidence rather than entitlement.
- The labour is not evidenced. Hours claimed with no signed record. Where operatives clock in and the record carries a date and a job, this stops being arguable.
The date matters more than the total
Worth stating plainly because it is counter-intuitive: getting the application in on the contractual date, slightly under-claimed, is almost always better than getting it in three days late with a perfect build-up.
A late application starts a later cycle. A slightly light one can be corrected next month. The contract's dates are not a courtesy, and they drive the whole notice timetable that decides whether you get paid in full. If you are not certain what your dates are, the payment timetable calculator works them out, and pay less notices, and the timetable behind them explains why they matter.
This is the document Unibuild produces. Applications are held against the project with their dates, receipts against them, and retention withheld captured against the receipt it came off, so the cumulative figure held is arithmetic rather than archaeology. Where the project was quoted through the platform, the works schedule draws on the priced sections of that quotation with their tendered values, so the measure has a documented origin rather than being retyped from a spreadsheet. Gross applied and gross balance are calculated as at each row's own date rather than only as at today, which is what lets you answer a question about March in November. Hours come from clock-ins with a date and a job attached, which is the evidence behind the labour line. It does not decide what your contract requires an application to contain: read the clause once and set the format to match it.
Where to start, on Monday
Read one clause: the one in your subcontract that says what an application must contain and when it must be made. Then compare it against the application you sent last month, line by line. Most firms find at least one requirement they have never met, and it is usually the basis of calculation.
Then fix the template rather than next month's application, so the improvement applies to every job you have.
The follow-up questions.
The rights behind all of this are in what the Construction Act actually gives you.
What should a construction application for payment include?+
What is the difference between an application for payment and an invoice?+
Why do main contractors reject applications for payment?+
Can my application for payment count as a payment notice?+
Is it better to submit a late application or an under-claimed one?+
More from Insights.
RAMS that hold upWhat an inspector is actually looking for in a risk assessment and method statement, and the difference between a document that exists and one that is doing its job.Read it →
Retention, and the money that goes missing after practical completionWhere cash quietly disappears between the last valuation and the release of the second half of retention, and the four dates that decide whether you ever see it.Read it →
Why field rollouts stall in week threeMost site software is not rejected. It is quietly outlived by the paper route nobody switched off. What the firms that got it to stick did differently.Read it →