Why Payment Applications Get Cut, and How the Argument Is Lost

Most reductions to a construction payment application are caused by the application itself. Seven recurring failures, what each one costs in cash flow, and how to close it.

A payment application is an evidence submission, not an invoice. When a certifier reduces it, the usual reason is that the evidence for part of the claim was absent, not that the work was disputed. The failures below cost contractors real money every month, and almost all of them are fixed by changing how the submission is assembled rather than by arguing harder.

Why these keep happening

Applications are often prepared at the last minute by someone under pressure, using last month spreadsheet with the numbers moved up. The measurement that supports the increase happens informally or not at all, the supporting documents are promised rather than attached, and anything contentious is included at its full claimed value in the hope that it survives. A certifier facing that submission has little choice but to cut what is unproven, and each cut becomes a month of lost cash flow that is rarely recovered in full.

1. Claiming progress the measurement does not support

An application built from a percentage judgement rather than a measure invites the certifier to apply a different judgement, and the certifier judgement is the one that gets paid. Percentages are also impossible to audit cumulatively, so errors compound month on month until a reconciliation forces a large correction.

• Avoid it by: Measure against the agreed breakdown, attend the joint measure, and submit the measured basis with the application rather than a percentage.
• Proof it is closed: The application arithmetic can be rebuilt from the attached measurement without reference to anyone judgement.

What it costs you: A reduction every month, and a painful adjustment when the cumulative position is finally reconciled.

2. Including unagreed variations at full claimed value

An instructed variation that has not been priced and agreed will be valued by the certifier at a fair interim figure, usually well below the claim. Putting the full claim in makes the whole application look optimistic and reduces the credibility of the parts that are sound.

• Avoid it by: Show variations in three columns: agreed, submitted and awaiting assessment, instructed but not yet priced. Claim a reasonable interim value for the unagreed ones and say so.
• Proof it is closed: The variation register attached to the application has a status against every entry and matches the certifier own register.

What it costs you: A large visible reduction that triggers closer scrutiny of every other line.

3. Materials claimed without the supporting evidence

Most contracts allow unfixed materials to be valued only on conditions: proper storage, protection, reasonable delivery timing and evidence of value and ownership. An application listing materials with no invoices, no location and no photographs fails those conditions on its face, however genuine the delivery was.

• Avoid it by: Attach invoices, a location schedule, dated photographs of storage and any required ownership or insurance evidence, every month without being asked.
• Proof it is closed: The materials schedule can be checked on site by someone walking round with the list.

What it costs you: The whole materials line removed, which on a procurement heavy month can be the largest single cut.

4. Ignoring the quality evidence that releases the work

Work awaiting a test or an inspection sign off is not work properly executed, so it will be held. Contractors often treat quality records as a paperwork chore for the engineer, not realising that the inspection and test file is a cash flow document.

• Avoid it by: Close the inspection and test records for each element before the valuation date, and attach the sign offs for anything newly claimed.
• Proof it is closed: Every newly claimed element has a corresponding inspection record dated before the valuation.

What it costs you: Completed physical work sitting unvalued for a month or more, funded entirely by the contractor.

5. Missing the procedural requirements of the clause

Contracts specify when an application may be submitted, in what form, with what breakdown and supported by what statements. An application submitted two days late, or without a required statement, can be deferred to the next cycle regardless of its merits. Procedural requirements differ between forms and are revised over time, so they need reading rather than assuming.

• Avoid it by: Extract the payment clause into a one page procedure with dates and required attachments, and run the submission against it as a checklist.
• Proof it is closed: A signed checklist accompanies each application, with the submission date inside the stated window.

What it costs you: An entire payment cycle lost, which on a long contract can be a very large sum of working capital.

6. Treating the certifier reduction schedule as an insult

When reductions arrive, the productive response is to work through them item by item and supply what is missing. A response that disputes the certifier good faith, or that simply resubmits the same figures, achieves nothing and consumes the month in which the evidence could have been assembled.

• Avoid it by: Reply within a week with a line by line response: accepted, evidence attached, or genuinely disputed with reasons. Keep the genuinely disputed list short.
• Proof it is closed: Each reduction from the previous month has a documented outcome before the next application goes in.

What it costs you: A reduction that becomes permanent because it was never properly answered.

7. Letting unpaid subcontractor claims distort the application

Where a main contractor passes subcontractor applications upward without checking them, it submits claims it cannot support and absorbs the reductions itself. The subcontractor expects to be paid on its own numbers, and the gap is funded by the main contractor margin.

• Avoid it by: Measure and assess subcontractor applications on the same basis the main contract will be assessed, before including anything upward.
• Proof it is closed: The sum of assessed subcontract values plus own work reconciles to the main application without an unexplained balance.

What it costs you: A cash gap between what the subcontract chain expects and what the contract will certify.

A short check before you sign

• The application is supported by a measurement that a third party could rebuild.
• Variations are split by status and unagreed items are claimed at a defensible interim value.
• Materials are evidenced by invoice, location, storage photograph and any required ownership document.
• Every newly claimed element has a closed inspection or test record.
• The submission meets the date, form and attachment requirements of the payment clause.
• Last month reductions each have a documented response.

If it has already happened

If the cuts have already accumulated into a serious cash position, stop submitting and spend a fortnight rebuilding the cumulative measurement from the contract breakdown. Produce one reconciliation that shows the gross value properly measured, the evidence for each contested element and the sums you accept were overclaimed. Then meet the certifier with that document rather than with a letter. Where the gap turns out to be a matter of entitlement rather than evidence, follow the contract dispute procedure in sequence and take advice from a licensed legal adviser before issuing any notice, because a procedural misstep at that point can cost more than the money in question.

Domira builds and supervises projects across Saudi Arabia, and the commercial discipline above is how its projects stay inside their budget and their programme. Send the drawings, the contract or the site and Domira will tell you where the risk actually sits.