Subcontractor payment disputes rarely start with the invoice. They start weeks earlier, when a measurement is not agreed, a variation is not recorded, or a back-to-back clause is signed without anyone checking what it means for cash flow.
By the time the subcontractor chases payment, both sides are working from different numbers. The main contractor points to the certified amount. The subcontractor points to the work on site. Neither has a single record both sides trust.
The result is a relationship that sours mid-project, a crew that slows down, and a programme that pays for it.
Follow a typical monthly cycle. The subcontractor submits a progress claim based on their own measurement. The main contractor’s quantity surveyor measures again, often with a different view of what is complete. The client’s consultant then certifies a third number for the main contractor’s own application.
Three measurements, three versions of progress, and the subcontractor is paid from the lowest. Retention, backcharges and deductions for unapproved variations come off on top. The subcontractor receives a payment far below their claim with no clear breakdown of why.
None of this requires bad faith. It only requires each party to keep its own spreadsheet.
The gap compounds month to month. A disputed item from March is carried into April’s claim, partially paid, then argued again in May. After a few cycles, nobody can say with confidence what is still owed and what was already settled. Every new claim reopens the old ones.
Most subcontracts in the region are written back-to-back with the main contract, and many include pay-when-paid terms. That ties the subcontractor’s cash flow directly to how quickly the client pays the main contractor.
The legal position is less simple than either side often assumes. Al Tamimi’s analysis of a Dubai Court of Appeal decision describes a pay-when-paid clause being treated as a condition precedent, with the burden on the subcontractor to prove the client had paid. In that case the subcontractor’s claim was dismissed as premature.
For the main contractor, that can look like protection. In practice it pushes the problem downstream. A subcontractor who cannot see whether the client has paid, or what was certified for their package, has no way to plan and every reason to distrust the numbers in front of them.
It is also one decision, and the outcome on any project depends on the exact wording of the subcontract and the facts. What it does show is how much rides on records. Whether the client has paid, what was certified, and when, all become evidence. A main contractor who cannot produce that history quickly is exposed whichever way the clause is read.
The obvious cost is time. Commercial managers spend days each month reconciling claims line by line, often reopening items that were settled the month before.
The less obvious cost is on site. A subcontractor under cash pressure reduces manpower, delays mobilisation on the next zone, or quietly prioritises another contractor who pays faster. The programme slips, and the main contractor carries the delay with the client.
Then comes the final account. Unresolved monthly disputes roll forward and land together at the end, usually alongside the main contractor’s own negotiation with the client. Unrecorded changes are often the root, the same issue behind why variation orders turn into disputes at final account.
Fewer disputes come from fewer versions of the truth. Measurements logged against the same BOQ line items the client certifies. Variations recorded when instructed, not when invoiced. Retention and deductions shown line by line, so the subcontractor can see exactly how each payment was built.
That is what construction ERP looks like when subcontract payments run through it. Mismar works with contractors across UAE and KSA to keep site progress, certification and subcontractor payments on one record. If your monthly payment cycle ends in an argument, let’s get on a call.
Start growing with Mismar today.
