Construction Payment Applications: What UK Contractors Need to Include

Last reviewed: 13 May 2026. This guide is practical workflow guidance for UK contractors and subcontractors. It is not legal advice, and contract-specific payment dates should always be checked against the signed contract.

Construction payment applications are easy to underestimate. They look like monthly paperwork, but they control when work is assessed, what value is certified, how much retention is held, and when cash should arrive.

A good payment application gives the client, main contractor, or quantity surveyor enough information to assess the value without chasing basic details. A weak one creates avoidable queries, missed dates, disputed deductions, and slower payment.

This checklist explains what UK contractors need to include in a construction payment application, how to structure the figures, and where retention, variations, previous payments, and evidence should sit.

What Is a Construction Payment Application?

A construction payment application is a formal request for payment based on work completed during a valuation period. It is usually submitted before an invoice, because the amount still needs to be assessed, certified, or agreed under the contract.

For subcontractors, the application is normally part of the monthly valuation cycle. It shows the value of work done to date, less previous certified amounts and any deductions such as retention. Once the application is reviewed, the agreed amount can be invoiced or exported into the accounting system.

The important point is that the application should show both this period's movement and the cumulative position. If the reviewer cannot see what has changed since the previous application, the application is harder to assess and easier to query.

Payment Application vs Invoice

A payment application is not the same as an invoice. The payment application asks for the amount due to be assessed. The invoice records the amount to be paid once the value has been approved, certified, or otherwise agreed.

That difference matters because the certified amount may not match the applied amount. A contractor might apply for £28,250, but the payer may certify £26,900 after reviewing measurements, evidence, or variations. If the invoice has already been raised for the higher amount, the accounts team then has to issue credits, amendments, or awkward explanations.

A cleaner workflow is to prepare the application, submit it with evidence, record the assessed amount, then raise the invoice for the agreed value. That keeps the valuation record and the accounting record aligned.

The Core Details Every Application Should Include

The first job is to make the application identifiable. If the commercial team has to work out which contract, period, revision, or company the application relates to, the document is already creating friction.

• Project name and reference: use the same project reference the client or main contractor uses.
• Contractor and payer details: include legal names, trading names where useful, and contact details.
• Application number: keep the sequence consistent, for example Application 04 rather than changing format each month.
• Valuation date: state the date the valuation is measured to.
• Submission date: record when the application was sent.
• Payment due dates: show the due date and final date for payment if these are known from the contract.
• Contract sum and approved changes: separate original contract value from instructed or agreed variations.

These details sound basic, but missing references and unclear dates are common reasons for avoidable email chains. The reviewer should be able to file, assess, and respond to the application without asking what it is.

The Valuation Breakdown

The valuation breakdown is the heart of the application. It should show how the applied value was built up, not just the final number. A single total may be quick to submit, but it gives the payer very little to assess.

• Description of each work item: match the contract schedule, bill, quote, or agreed valuation breakdown.
• Original value: show the agreed value for each item.
• Previous cumulative completion: show the percentage or value certified in the previous application.
• Current cumulative completion: show the total progress now being claimed to date.
• This application value: show the movement between previous and current completion.
• Cumulative value to date: show the total value completed across the project so far.

For example, if a £40,000 roofing package was 35% complete last month and is 60% complete this month, the current cumulative value is £24,000. The movement this application is 25%, so the value this application is £10,000 before retention and other deductions.

Showing the calculation this way makes it easier for the payer to see what is new. It also helps directors and finance teams understand whether the business is applying for the right amount each month.

Variations and Change Items

Variations should be visible and separate. Do not hide them inside the original contract works unless the contract process specifically requires that format. A variation has a different commercial status from base scope, so the application should make that clear.

• Variation reference: use the instruction, quote, or change reference.
• Description: explain the change in plain language.
• Submitted value: show the amount claimed or priced.
• Agreed value: separate agreed items from pending items.
• Value included this application: show what is being applied for now.
• Supporting evidence: attach instructions, emails, drawings, dayworks, photos, or measurements.

This avoids a common dispute pattern: the main works are mostly agreed, but the whole application is slowed down because variation evidence is unclear. Keeping changes separate lets both sides deal with the base valuation and the variation questions more cleanly.

Retention, Deductions, and Net Due

Retention needs to be shown clearly because it affects both today's payment and future cash flow. The application should show the gross value, retention percentage, retention deducted, retention held to date, retention released if relevant, previous payments, and the net amount due.

If the contract uses 5% retention and this application has a gross value of £10,000, the retention deducted for this application is £500. The net before other deductions is £9,500. The application should also show cumulative retention held, because that money may need to be recovered later at practical completion, after the defects period, or under a 6+6 or 12-month release schedule.

For retention-specific planning, use the retention release schedule generator or read Retention Release Schedules: 6+6 vs 12 Months Explained.

Previous Certified Amounts

A construction payment application is usually cumulative, so previous certified amounts matter. The net amount this month is not simply the current total value of the job. It is the value now due after previous certificates, prior payments, retention, and any agreed adjustments.

At minimum, show the previous gross certified value, previous retention deducted, previous net certified amount, and previous paid amount if that is tracked separately. If the previous certified value differs from the previous applied value, make that visible. Otherwise, the next application can drift away from what was actually agreed.

This is where spreadsheet-based applications often go wrong. Someone copies last month's file, changes a few percentages, but forgets to update the previous certified amount or a retention release line. The summary still looks professional, but the net due is wrong.

Supporting Evidence

Good supporting evidence reduces queries. The aim is not to attach every file on the project. The aim is to attach enough evidence for the reviewer to understand why the claimed value is reasonable.

• Progress photos: useful for visible site progress and completed work areas.
• Marked-up drawings: useful where measurement or location matters.
• Delivery notes: useful for materials on site or supplied items.
• Signed daywork sheets: useful for dayworks, labour-only changes, or instructed extras.
• Variation instructions: useful for change items and disputed scope.
• Previous certificates: useful where the current application reconciles against prior certification.

Evidence should be named and organised. Files called final-final-v3.pdf, IMG_4821.jpg, and scan.pdf are harder to review than files named Application-04-Variation-07-Daywork-Sheet.pdf or Application-04-Roofing-Progress-Photos.pdf.

Submission Checklist Before You Send

Before submitting the payment application, review it from the payer's perspective. The best applications answer obvious questions before they are asked.

• Does the application number follow the previous sequence?
• Is the valuation date correct?
• Do current cumulative percentages exceed previous percentages?
• Are any line items above 100% complete without explanation?
• Are variations separated and evidenced?
• Is retention calculated from the right base?
• Do previous certified amounts match the last certificate?
• Does the net due reconcile back to the summary?
• Are the attachments named clearly?
• Is the application being sent through the agreed channel?

If the answer to any of these is no, fix it before submitting. A few minutes of review can prevent a full month of payment delay.

Common Mistakes to Avoid

Most payment application mistakes are not dramatic. They are small admin errors that repeat across projects until they become cash flow problems.

• Submitting late: missing a valuation deadline can push payment into the next cycle.
• Mixing invoices and applications: invoice after the value is agreed unless your workflow and contract say otherwise.
• Forgetting retention: either omitting it, deducting it twice, or failing to track release dates.
• Using old spreadsheet versions: old formulas and copied tabs create underclaims and overclaims.
• Not recording certification differences: the next application should start from what was certified, not only what was claimed.
• Weak variation evidence: unsupported change items are easy to query and can slow the wider application.

How BuildQS Handles Payment Applications

BuildQS gives contractors a structured payment application workflow instead of a folder of spreadsheets. Projects contain phases, tasks, values, completion percentages, variations, retention settings, and application status in one place.

When an application is created, BuildQS calculates this application value, cumulative value, retention deducted, previous values, and net due from the live valuation data. That reduces manual rekeying and makes each monthly application easier to check before it goes to the client or main contractor.

BuildQS also connects the application workflow to retention tracking, cash flow forecasting, and Xero handoff. For a deeper product view, see payment applications, retention management, cash flow forecasting, and Xero integration.

If you are still comparing spreadsheet workflows, read BuildQS vs Spreadsheet Payment Applications or try the payment application template generator.

Prefer to walk through your workflow live first? Book a Demo

Frequently Asked Questions

What should a construction payment application include?

It should include project and contract details, application number, valuation date, submission date, valuation breakdown, variations, retention, previous certified amounts, net amount due, and supporting evidence.

Is a payment application the same as an invoice?

No. A payment application asks for the value to be assessed under the construction contract. An invoice is normally raised for the approved, certified, or agreed amount.

Should retention be shown on every application?

Yes. Retention should be visible on each application so the payer, contractor, and finance team can see what has been deducted and what should be released later.

Can I use a spreadsheet for payment applications?

Yes, especially for simple projects. The risk grows when you manage several live projects, multiple team members, variations, retention release dates, and Xero handoff from separate files.

What is the biggest mistake contractors make?

The biggest practical mistake is failing to reconcile the new application against the previous certified amount. That can make the net due wrong even when the current valuation looks sensible.

Sources

• Housing Grants, Construction and Regeneration Act 1996, section 110A, payment notices
• The Scheme for Construction Contracts (England and Wales) Regulations 1998, Part II
• Ashfords, Payment notices: why form matters, 2025