Two payment ladders that never line up

A developer collects on one ladder and pays on another.

The collection ladder is written into the buyer's agreement: something on booking, something on agreement, something on each slab, something on possession. The payment ladder is written into the construction contracts: running account bills against measured work, advances against material, retention released at defined points.

The two ladders describe the same building. They are connected by physics — the slab that triggers a demand is the slab the contractor was paid to cast — and by nothing else. Different documents, different counterparties, different triggers, different timing.

The space between them, month by month, is what a developer's working capital actually is. Not a financing line. The arithmetic of two schedules that were never designed to meet.

Why they cannot line up#

Different measuring instruments. Buyers pay on a stage that somebody certifies as reached. Contractors bill on quantity that somebody measures. A stage is a discrete event; measured quantity is continuous. The contractor's bill for the month covers work spread across a stage boundary, and the buyer's demand covers a boundary the bill knows nothing about. The two documents describe the same concrete and cannot be reconciled line to line. That is normal, and worth saying out loud so nobody spends a month trying.

One event, many payers. A slab is cast once. It triggers a demand to every buyer in that tower, and each of them pays on his own schedule — some on the day, some after a reminder, some after a second reminder, some when their loan is disbursed, some not at all. One certain outflow has been matched against many uncertain inflows, and the distribution of those inflows decides whether the month is comfortable.

A defaulting buyer does not pause the contractor. The contractor's entitlement arises from work done. It does not care who has paid. Every collection problem on the sales side lands, unchanged in size, on the construction side, and the developer absorbs the whole of it.

Material is paid for before its stage is reached. Steel and cement for a slab are bought before the slab exists, sometimes months before, because rates were good or supply was tight or the contractor needed mobilisation. The money leaves on the material's schedule and returns on the stage's, and that gap is real cash. Whether the material has actually arrived when the money leaves is a separate discipline — money before material — and the gap is where a timing problem quietly becomes a loss.

Retention is money you hold that the buyer has already paid. You have deducted retention from the contractor. The buyer paid for the completed stage in full. So a balance sits with you which belongs to somebody, will be released later, and is not profit. It is the easiest money on a project to spend by mistake, because nothing about it looks restricted. The mechanics are in retention money; the point here is that any comparison of the two ladders which ignores it is flattering.

A stage completed just after a month-end. The slab is cast on the first of the month rather than the last of the previous one. Nothing has changed about the project. Everything has changed about the month — the demand goes out in the next cycle, collections land a month later, and the contractor's bill for the earlier month is already payable. Two ordinary days move a month's cash.

What to do about it#

You cannot make the ladders meet. You can stop treating them as one thing.

Model them as two schedules with a stated linkage. One schedule of expected collections by stage and by buyer. One of expected certifications and payments by contract. Then, written down, the linkage: which construction event triggers which demand stage, and by what definition. If that mapping lives only in the sales head's memory, the two ladders are connected by a person, and he will be on leave in the month it matters.

Publish the demand on the day the stage is certified. Not when somebody in accounts gets to it. The certification date is the earliest legitimate date; every day after it is financing you have donated, and the delay is almost always administrative rather than deliberate. Drafting the notice properly is its own subject — the demand letter — and is separate from the scheduling discipline of sending it on time.

Keep the deductions visible on both sides. Retention, advance recovery and set-off on the contractor side behave like part-payments and holds on the collection side: balances with a future, not reductions in value. Collapsing them into one net figure destroys the information, which is the argument running account bills make about certificates and which applies just as well to a collection statement.

Keep money and progress as separate facts. Cash collected is not work done, and work done is not revenue. Which is recognised when, and on what basis, is a matter for your auditor and the standards in force — verify that with them rather than from general reading. The operating point stands on its own: staged payments and accounting treat a stage as several distinct events, and a business that conflates them cannot tell a collection problem from a construction one.

Never report collections as progress. It is the most tempting number in a developer's office, because it is the easiest to produce and it moves. A good collection month against a bad construction month is a business getting worse and looking better. The reverse is a business getting better and looking worse. Report the two side by side, always, and never let either stand in for the other.

The short version#

Buyers pay on certified stages. Contractors are paid on measured quantity. The two ladders are joined by the building and by nothing in the paperwork, and the space between them is your working capital.

Model both as schedules, write down which construction event triggers which demand, raise the demand on the day of certification, and keep collections and progress as two numbers that are never allowed to substitute for one another.