What Is an Application for Payment? How UK Subcontractors Actually Get Paid

On a domestic job you finish the work and send an invoice. On a contracted commercial job that is usually not how money moves at all. Instead, each month or at agreed intervals, you send an application for payment: a document that says, as of a stated date, here is the value of the work completed so far. It sets out what has already been paid, and states what is therefore now due.

If you have moved from price work or small jobs into subcontracting on larger sites, the application is the single biggest change in how you get paid — and it is the step most likely to go wrong quietly, because nothing about it feels urgent until a payment is late.

What an application for payment is

An application for payment (often shortened to AFP, or called an interim application) is the subcontractor's claim for the value of work completed to date under a construction contract. Rather than invoicing job-by-job, you value the work at defined cut-off points and deduct what has already been certified — assessed as due — and paid. You deal with any retention the contract provides for, then state the balance you are applying for.

The other party — the main contractor, or their quantity surveyor (QS) acting for them — assesses that claim, and the contract machinery then determines what gets paid and by when.

Two things follow from this that surprise people used to invoicing:

• You rarely "invoice" for the works during the job. The application is the commercial instrument that drives payment; on many contracts an invoice only appears later, if at all, against certified amounts.
• The dates are contractual, not informal. When your application must go in, when it must be assessed, and when money must be paid are all defined by your subcontract — miss the rhythm and your money typically slips a whole cycle.

This guide describes the standard position for construction contracts in England and Wales covered by the Construction Act framework. Some contracts fall outside it, and every point below can be varied by what your own subcontract actually says. It is general information, not legal advice — read your subcontract, and take advice on anything disputed.

The rhythm itself is contractual too. Your subcontract states the valuation interval — monthly is common on longer packages — along with the cut-off or application date and how the resulting due date and final date for payment are calculated.

The four documents people confuse

Most payment confusion comes from treating these as interchangeable. They are not:

Application for payment — what you say is due

Your claim, prepared by you, stating the value of work done to date and the balance now applied for. It starts the assessment cycle.

Payment notice — what the payer says is due

A notice stating the sum considered due at the payment due date and the basis on which it was calculated. The Construction Act framework requires construction contracts to provide for one — from either side, or a person the contract specifies — no later than five days after the payment due date. A zero figure is allowed. Which party gives it is a matter of your contract: many subcontracts put that duty on you, which makes serving your application on time genuinely important rather than administratively polite.

Pay less notice — the payer's intention to pay less than the notified sum

Where the payer intends to pay less than the notified sum, they must serve a notice stating the sum they consider due at the date the notice is served and the basis of calculation. That sum may be zero. The notified sum is whatever the latest compliant notice states — your application, or the payer's payment notice. The pay less notice deadline is a prescribed period before the final date for payment: whatever your contract agrees, and otherwise seven days before the final date under the Scheme for Construction Contracts (the fallback terms that apply where a contract lacks them). If neither a compliant payment notice nor a compliant pay less notice arrives in time, the notified sum — typically fixed by your own compliant application — becomes payable.

Invoice — the commercial and tax document

An invoice is a demand for payment and a VAT document. On contracted work it may be raised against certified amounts, after certification, or not until the end of the job — whenever your contract and process put it. An invoice is not an application, and sending one does not substitute for the contractual process.

One more distinction matters inside the documents themselves: the due date is when a sum becomes due under the contract, and the final date for payment is the last date the payer must pay it. The gap between them is whatever your contract says — or, if it says nothing, the Scheme sets one (17 days from the due date).

The payment cycle, step by step

The exact mechanics vary by contract — treat this as the common shape, and check each labelled point against your own subcontract:

1. Work completed and recorded. Labour, materials and variations happen on site and get captured (or don't) as records. [Varies: whose record counts is often contested later.]
2. Valuation prepared. You measure progress against the contract value — percentage complete per section, measured quantities, or another agreed basis. [Varies: method differs by contract type.]
3. Application submitted. By your contract's application date, for its valuation period.
4. Assessment. The contractor's QS reviews, queries, values work done, and adjusts.
5. Payment notice served. Within five days of the due date, by whoever the contract charges with it, stating the sum considered due and the basis. [Often your application itself serves as this notice — check your subcontract.]
6. Possible pay less notice. If the payer intends to pay less than the notified sum, a compliant notice before the contractual deadline — otherwise the notified sum stands.
7. Certified / notified amount paid. By the final date for payment.
8. Reconciliation. What was applied for, what was certified, what was actually paid — carried into next month's figures and ultimately the final account. [This is where silent value loss happens when records are loose.]

Disputes at any step can escalate to adjudication, a statutory process designed to produce a quick decision. And where payment does not arrive by the final date, the same statutory framework gives an unpaid party a conditional right to suspend performance — though most valuation disagreements are settled long before either lever gets pulled.

What goes into an application

Contracts differ, so treat this as the typical build-up rather than a universal template:

• contract or subcontract reference, and the application number
• the valuation period and cut-off date
• original contract / subcontract value
• variations instructed and valued to date
• value of work completed to date, against the agreed measurement basis
• previous applications, amounts certified, and payments received
• retention applied for the period, where the contract provides for it
• materials on site (and off site, where permitted)
• the gross valuation, and the net amount now applied for
• supporting evidence: site records, timesheets, delivery notes, photographs, signed instructions, daywork sheets

No contract requires every item every month. But almost every QS will ask for the arithmetic to tie: previous figures must reconcile exactly, because the fastest way to lose credibility on a valuation is for last month's numbers to move.

Where retention fits

Many contracts provide for retention: a slice of the value of certified work withheld as security, released later — typically in stages linked to completion and the end of a defects liability period (the post-completion window during which defects must be made good). The specifics are entirely contractual: whether retention applies, at what rate, capped or uncapped, and when tranches fall due.

For your applications, retention does three things: it reduces what you receive now on each certification; it accumulates as a running balance you are owed later; and it creates a second chasing problem at the end of the job, because release rarely happens without being asked for.

Track retention as its own register — per job, accrued, released, outstanding. Subcontractors who track retention inline with general debtors routinely lose sight of what is due back and when.

Variations: where applications are won and lost

A variation is work instructed outside the original scope — and it is the part of the application most likely to be challenged, because unlike the base scope there is no priced line item already agreed.

What strengthens a variation claim is contemporaneous evidence: a written instruction or site instruction, a drawing revision, an email confirming the change, signed daywork sheets (records of labour and materials charged at rates for unpriced extra work), labour and material records for the additional work, photographs showing the condition before and after, and a quotation-and-approval trail where the contract requires one.

Two honest cautions. First, whether an instruction needs to be in writing to be valid depends on the contract — some require written variation instructions, others recognise verbal instructions given on site, and adjudicators simply apply whatever the contract says, so outcomes differ. Second, unsigned or informally-instructed work is neither automatically lost nor automatically payable; it turns on the contract and the evidence around it. What is certainly true is that reconstructing instructions months later, from memory, is the weakest position available — and the most common one.

Why payment problems start before the application

Follow a delayed payment backwards far enough and it usually stops being a payment problem:

a site instruction nobody wrote down → a variation with no evidence → labour records incomplete for the weeks in question → the commercial team rebuilding events from messages long after the fact → an application with gaps the QS can see → lines reduced or removed → certification lower than claimed → cash short, and an argument instead of a number.

The chain is worth naming: site → record → value → application → payment. Every link downstream inherits the quality of the link above it. An application is only ever as strong as the records behind it. That is why the fix for late payment is often upstream of finance altogether — capture at the point of work, not reconstruction at the point of claim. The same field-to-office gap shows up long before applications, in hours nobody can chase accurately; and when records live across email, WhatsApp and spreadsheets, the cost surfaces the first time you need to prove something.

Why applications get challenged or delayed

From the outside these look like bad luck. From the inside they are mostly process failures with names:

• the application missed the contractual submission date, rolling the whole cycle forward
• valued the wrong period — cut-off confusion between site reality and paper dates
• variation lines included without evidence the assessor will accept
• figures inconsistent with previous applications, inviting challenge across the board
• labour or material claims unsupported by records anyone can check
• materials-on-site value challenged as unidentified, unevidenced, or outside the period
• contra-charges or set-offs applied against the application without a basis the contract supports
• previous-payment figures wrong, so the arithmetic fails reconciliation
• retention misapplied — deducted twice, forgotten, or calculated against the wrong base
• served on the wrong entity, or by a method the contract does not recognise
• notice mechanics ignored — including contracts where you owe the payment notice, not just the payer
• site records reconstructed weeks later, when memory is the only source

None of these is exotic. All of them are avoidable with a fixed monthly routine.

Pre-submission checklist

• ☐ correct contract / subcontract reference and recipient entity
• ☐ correct valuation period and submission date under this contract
• ☐ previous applications reconciled — certified and paid tie exactly
• ☐ variations included, each with its evidence trail
• ☐ retention checked against the contract's provisions
• ☐ labour and site records attached where the claim needs support
• ☐ gross valuation, deductions and net applied-for re-added independently
• ☐ submission method and format match what the contract requires
• ☐ acknowledgement or other proof of delivery retained
• ☐ a copy retained, with everything needed to answer a query later
• ☐ due date, final date for payment and any notice deadlines diarised

A checklist does not replace reading your subcontract. It exists so the mechanical parts never undermine the parts that need judgement.

Where GUVNR is on this

GUVNR is being built around the information flow between site records, commercial admin and payment — the chain described above.

We can be concrete about parts of it. We run our own contracting business on GUVNR today: shift reports and timesheets captured, quotes raised, invoices carrying a CIS (Construction Industry Scheme) position and the VAT treatment we set on every one, and purchase orders held against their jobs. That first link — the site record existing when the work happens — runs in our production system on real jobs.

The application-for-payment side — building valuations, reconciling against the previous application, tracking retention — we have built and are currently testing. We are not going to describe it as finished, because on a live job it has not yet earned that description, and no company outside ours can use GUVNR at all yet. If you want to follow what we build, the waitlist at guvnr.ai is the way in; joining it is not a promise of a place.

Whatever software you use, the principle holds: the businesses that get paid smoothly are the ones whose site records make their applications true. For more on why job-management tools that only store admin fall short of this, see what it would take for software to actually do the chasing.