Retention Is a Loan You Made Without Deciding To

Retention is money you have earned, certified, and are not being paid yet. A percentage of every payment certificate is withheld by the client, accumulates as the job runs, stops accumulating once it reaches a ceiling written into the contract, and comes back to you in two separate instalments — one at practical completion, the balance at the end of the defects liability period.

Two things make it harder than a deduction line. The first is the ceiling: retention accrues at one percentage of each certificate only until the total reaches a cap expressed against the contract value, after which it must stop, and a system that keeps deducting past that point is quietly taking money out of your own certificates. The second is that it runs in both directions at once. Your client holds retention from you. You hold retention from every subcontractor. The two do not release on the same dates, and the gap between them is a real cash position that appears nowhere on a profit and loss.

That is the mechanism. The rest of this article is what it does to a balance sheet, and what to make a system prove before you rely on it.

The cap is the rule systems get wrong

Every retention arrangement has at least two numbers in it, and they are not the same number.

The rate is the percentage withheld from each certificate. The cap is the total amount that may be held at any point, usually expressed as a percentage of the contract sum. Retention accrues at the rate until the accumulated balance hits the cap, and then accrual stops while the balance stays held.

This is the most commonly mis-implemented rule in contract accounting, and the reason is that it is invisible for most of the job. On a contract where the cap sits at half the rate, accrual continues untroubled until roughly the halfway point of the works. Everything looks correct for months. Then the balance crosses the cap and a system that does not know about caps carries on deducting, certificate after certificate, until somebody in commercial notices that the retention held against them exceeds what the contract permits.

By then the money has already been withheld across several certificates, the recovery is a conversation rather than a correction, and — because the same logic runs on your subcontract certificates — you may have been over-deducting from your own subcontractors for the same period, which is a different and less comfortable conversation.

The requirement is simple to state and rarely met: the rate and the cap are both fields on the contract, the accrual is computed rather than typed, and the accrual stops itself. Nobody should have to remember.

Retention runs in both directions at once

A main contractor is simultaneously the party retained from and the party retaining. These are two ledgers with opposite signs and no relationship to each other except that they sit in the same business.

	Held from you	Held by you
Counterparty	The client	Each subcontractor
Balance sheet	An asset — money owed to you	A liability — money owed by you
Rate and cap	Your main contract	Each subcontract, separately
Release trigger	Your completion and defects period	Each subcontractor's completion and defects period

The last row is the one that costs money. The subcontract defects period and the main contract defects period are rarely the same, and where a subcontractor finished their package eighteen months before the project completed, their release falls due long before yours does. You pay out before you are paid in. That is not an error — it is the ordinary consequence of the dates — but it is only manageable if somebody can see it coming, and it is invisible in any system that stores retention as a percentage on a document rather than as a balance with a date.

The single question that tests whether the two ledgers exist: what is our net retention position, today, and on what dates does each side of it move? If answering it requires opening a file, the ledgers are a spreadsheet.

Release is two events, not one

Retention does not come back when the job finishes. It comes back twice, and the second time is much later than most people carry in their heads.

The first release is tied to practical completion — or substantial completion, or taking-over, depending on which form the contract is based on and how the particular conditions amended it. A portion of the held balance is released against the certificate that marks it.

The second release is tied to the end of the defects liability period, which begins at completion and runs for a duration written into the contract. The balance is released against the final certificate, subject to whatever the client has spent making good defects you did not.

Both of those durations are contract fields, not constants. UAE construction contracts are commonly built on a FIDIC form with the particular conditions amended, and the completion and defects provisions are amended as routinely as the payment period is. Any system, template or article that states a fixed number of months is describing a different contract than yours.

What follows from this is the part worth acting on: the release dates are knowable years in advance and almost nobody records them. The date the defects period ends is fixed the day completion is certified. A system that stores it produces a release schedule; one that does not produces a quarterly question to the QS and an amount that gets chased only when cash is tight.

Where the money actually is

Here is the part that changes how the number is read.

Retention is not an expense and it never was. It is your revenue, certified, sitting on the balance sheet as a receivable with a long and known maturity. Model it as a discount and it disappears from the balance sheet entirely — the profit and loss shows a reduced revenue figure, nothing shows an asset, and the money is genuinely lost to the accounts even though it is contractually owed.

Model it as a manual journal and it survives, but only as well as the person who posts it. The recurring shape here is a retention ledger held in one finance file, reconciled by hand once a quarter, owned by one person, and correct as of whenever that person last had a clear afternoon. That reconciliation cost is real and measurable — it is the same category of work the cost of chaos calculator turns into an annual figure — and it is being paid to maintain a number the system could have derived.

The reason it matters beyond tidiness is that retention is often a substantial multiple of a contractor's annual profit. A business with several contracts running carries a retention receivable that would materially change the picture if it were visible, and the working capital conversation with a bank goes differently when the answer to "what is held against you and when does it come back" is a schedule rather than an estimate.

That question sits alongside the other three numbers a contractor's system has to produce, which the wider picture for contractors sets out together — because retention on its own is only one line of the cash position.

What to make a vendor show you

Retention is a good demonstration test for the same reason the certificate is: it is unremarkable to describe and awkward to build, so it separates a product that contains it from one that will need it written.

1. Set a rate and a cap on a contract, run certificates until the balance reaches the cap, and show accrual stopping without an instruction.
2. Show the retention balance for one contract as a query — held to date, released to date, outstanding — not as a report someone assembles.
3. Show the same figure across all contracts at once, with the release dates.
4. Certify practical completion and show the first release calculated, not typed.
5. Do the same on a subcontract certificate, and then show the net position across both directions.
6. Change the defects period on one contract and show the release schedule move.

Anything on that list that cannot be done in front of you is either configuration nobody quoted or a spreadsheet with a longer life than the contract. It is also worth asking the question the payment certificate itself raises: whether retention is a derived field on a cumulative valuation, or a number somebody types each month. Only the first one survives a downward remeasure.

The short version

Retention has a rate, a cap, two release events and two directions. Four of those six are contract fields that change from job to job, and the two release dates are knowable years ahead.

A system that holds all six produces a schedule of money coming back and a warning before money goes out. A system that holds a percentage on a document produces a deduction line and a quarterly conversation, which is what most contractors have and why most contractors cannot state their retention position without asking somebody.

What that looks like built, with the rest of the contracting chain around it, is on the contracting page.