What kills construction firms is usually not losing money — it is timing. The firm executes a million in work, pays for materials and wages immediately, then waits sixty or ninety days to collect part of its value after retention is deducted. That gap between spending and collecting is what does the damage, and it widens as the company grows. This is a guide to managing the gap with a contractor’s tools rather than an accountant’s.
Key takeaways
- Profit is an accounting opinion; cash is a bank fact. Companies close because of the second, not the first.
- A rejected application is not a week late — it is a whole extra cycle, another month of financing the work yourself.
- Retention is earned money deferred, and belongs on a tracked asset register rather than in a deduction you forget.
- Growth consumes cash: a new project means immediate spending and collection two months later.
- A simple three-month cash curve surfaces the crisis with enough warning to still have options.
Why profitable firms stop trading
In the accounts, revenue is recognised when work is executed. In the bank, money arrives when the payment is collected. Weeks or months pass between those two moments, and during that period the firm has already paid wages, materials and plant hire out of its own funds. The accounts say "profit"; the bank balance says "wait".
| Stage | Approximate timing | Cash effect |
|---|---|---|
| Work executed, materials and wages paid | Day 1 | Full cash out |
| Month closed, application prepared | Day 30–35 | Nothing |
| Consultant review and certification | Day 45–60 | Nothing |
| Client approval and certificate issued | Day 60–75 | Nothing |
| Actual collection | Day 75–105 | Cash in, less retention |
That table explains the whole paradox: three months of self-financing for every month of work. And a growing firm opens a second and third project on the same basis, so the gap multiplies while the profit ledger looks excellent.
What an application looks like to the person reviewing it
A payment application is not an invoice. It is a claim supported by measurement, reviewed item by item by somebody looking for a reason to reduce it. Understanding its structure from the reviewer’s side is the fastest route to fewer rejections.
Work executed to date
A cumulative value, not a monthly one. Each item at its executed quantity and contract rate, supported by a measurement sheet signed off on site — not by an estimated percentage complete.
Materials on site, not yet installed
Where the contract permits it. Usually requires proof of ownership, secure storage on site and insurance. Good for cash flow and frequently left unclaimed.
Approved variations only
Approved ones. Including a variation that has not been certified exposes the whole application to rejection; the correct treatment is to show it separately as value at risk.
Advance payment recovery
Normally recovered as a percentage of each application. Track the outstanding balance; the common error is applying the percentage to the wrong base, producing a cumulative difference that is painful to explain later.
Retention
A percentage withheld from each application up to a capped limit. It comes off the value of work, not off the tax-inclusive total, and confusing the two is one of the most common causes of dispute.
Net due this application
Cumulative total, less previously certified, less deductions. That single number is what will reach the bank.
Retention: money you have already earned
Retention is an amount withheld from every application — commonly 5% to 10% — until it reaches a capped share of the contract value. Half is typically released at practical completion and half after the defects liability period ends. The problem is that many firms treat it as a closed deduction and simply forget it.
The arithmetic is stark: retention at 5% on a ten-million contract is half a million. A sum that size could fund an entire small project, and it is your money — just a year or more away. Not tracking it means extending free finance and forgetting to collect it back.
- Keep a retention register per project: accumulated amount, due date of each release, and the status of the claim for it.
- Set a reminder before practical completion — release rarely happens automatically without being asked for.
- Close snags fast; one open item can hold up release of an entire tranche.
- Compare the cost: a retention bond is often cheaper than waiting a year for the cash.
- Put expected releases into the cash curve at their dates, rather than treating them as a frozen figure.
Retention is not a deduction. It is an interest-free loan to your client — and failing to track the repayment date is what turns a loan into a gift.
Why applications get returned
A rejection is not a delay of a few days. A returned application usually waits for the next cycle — another full month of financing the work yourself. Which is why an extra hour of internal review is dramatically cheaper than any amount of chasing afterwards.
| Cause | Preventive action |
|---|---|
| Quantities not matching the measurement sheet | Get measurement signed off on site before preparing the application, not after |
| Uncertified variation work included | Keep it out and report it separately as value at risk |
| Missing attachments or undated photographs | A fixed checklist closed out before submission |
| Errors in retention or advance recovery | Calculate from contract data automatically instead of re-keying each month |
| Cumulative total disagreeing with the previous application | One cumulative sequence rather than separate files per month |
| Submitted after the contractual date | A fixed monthly close calendar that starts before month end |
A cash curve that gets ahead of the crisis
Most liquidity crises are visible six to eight weeks before they happen, but nobody is looking. A basic cash curve needs no sophisticated system — it needs a weekly sheet with three rows.
Expected inflows, dated
Every expected certificate at a realistic collection date — based on this specific client’s historic delay, not on what the contract says.
Committed outflows
Wages, issued purchase orders, plant instalments, statutory payments. Known commitments before estimates.
Running balance, week by week
The only number that matters. The week it turns negative is the date of the crisis — knowable now rather than later.
The slippage scenario
Re-run it assuming your largest application slips thirty days. If the curve collapses under that, you are relying on a single payment more than you should be.
The value of the curve is not precision but early warning. Knowing that week eleven will be tight gives you options: accelerate an application, defer a purchase order, arrange a facility on reasonable terms. Discovering it on payroll day leaves only the expensive ones.
The monthly discipline that makes the difference
All of the above collapses if application preparation starts a week after month end. Firms that collect faster are not necessarily better negotiators — they are simply more disciplined about a fixed calendar.
- One week before month end: measure the major items on site and get them agreed with the consultant’s engineer.
- Close day: freeze quantities and close the month’s daily reports.
- Within 48 hours: build the application directly from the agreed quantities.
- Before submission: an adversarial review by a second person, plus the attachment checklist.
- One week after submission: a written follow-up if no acknowledgement or comments have arrived.
- Weekly: update the cash curve with realistic collection dates.
The conclusion is that cash flow is not an accounting matter to be left to the finance office. It is a direct product of measurement quality on site, the speed of the monthly close, the accuracy of the application, and retention follow-up. Every one of those sits with the project team, not with the bank.
Frequently asked questions
What is the difference between a payment application and an invoice?
An invoice claims an agreed amount for a supply or service. A payment application claims the value of work actually executed, supported by site measurement, subject to review and certification, and then reduced by retention and advance recovery. An invoice is paid; an application is certified first and paid second.
Can we claim variation work before it is approved?
Including it usually exposes the whole application to rejection, so it is better left out. It should still appear in the status report as value at risk, with the instruction date and reference, so the cash effect is visible to management rather than a surprise.
What is a typical retention percentage?
Commonly 5% to 10% of each application, capped at somewhere between 5% and 2.5% of the contract value, released in two tranches — at practical completion and after the defects liability period. Percentages vary by contract and market; read them from the contract rather than from custom.
Is there an alternative to cash retention?
A retention bond, where the contract allows one. Its annual cost is usually far lower than the cost of being without the cash for a year or more, particularly if you are funding working capital through more expensive bank facilities.
How do we handle a client who always pays late?
First with data: keep an actual average payment period per client and use it in pricing and planning, not only in complaints. Second with the contract: review interest-on-late-payment and suspension provisions. Third with concentration: a client representing more than half your revenue is a cash risk before it is an opportunity.
From measurement sheet to payment application, in one place
Link quantities agreed on site straight through to the BOQ and the application, and track retention and collection — in Arabic and English.