When a UAE contractor has a cash problem, the instinct is to treat it as a cash problem. The conversation is about the client paying slowly, the certifier being conservative, and the need to chase the next certificate harder. That framing feels right because the symptom is cash and the pressure is real. It is also why the same contractors keep having the same problem certificate after certificate: payment certification is not primarily a cash chase. It is a data problem. The certified amount is a stack of evidenced lines, and a contractor that assembles the evidence at certification rather than capturing it as work happens is certified down to what it can prove that week, not what it built.
This piece is a perspective on why payment certification in UAE construction is a data problem before it is a cash problem. The argument is opinionated. We are not arguing that slow-paying clients do not exist, or that quantity surveyors are at fault. We are arguing that the certified figure is only as strong as the evidence behind each component, that the components which carry the most cash are the ones whose evidence is assembled latest and contested most, and that the durable fix is capturing the evidence as work happens so the valuation arrives defensible rather than defended after it is queried. The cash follows the data. The contractor that fixes the cash chase without fixing the data keeps running the same exercise every month.
The audience for this analysis is owners, commercial directors, and senior quantity surveyors of UAE contractors who feel their certified amounts are consistently below what they have delivered and treat it as a client-payment behaviour rather than an evidence one. The useful diagnostic question is not "how do we get paid faster" but "of the amount we are certified down each month, how much is genuinely not due and how much is due but not provable at the moment the valuation is cut".
What the Certified Amount Is Actually Made Of
Below is a representation of an interim valuation as the stack of components it actually is, each shaded by how well its evidence typically holds at the moment of certification. The point is not the proportions; it is that the components carrying the most cash, measured work, materials on site, and variations, are the ones whose evidence is thinnest or most contested when the valuation is cut, and that this is where the certified amount is lost. Tap any component to see what it should be backed by, where the cash is lost, and what capturing it changes.
An interim valuation as an evidence stack
Tap a component for what backs it, where the cash is lost, and what capturing it changes
Why the Cash Follows the Data
The reason this is a data problem is the structure of certification itself. An interim valuation is a claim that has to be substantiated, and a certifier can only certify what is supported when the valuation is assessed. Under the FIDIC-family contracts common in the UAE, the interim payment certificate reflects what the engineer or certifier is satisfied is due at that point, against the evidence available at that point. Evidence that exists in the contractor's heads, in an engineer's notebook, or in records that will be assembled next week does not exist for the purpose of that certificate. The cash is not withheld out of behaviour; it is not certified because it is not yet provable, and provable is a property of the data, not the relationship.
The components are not equally exposed. Measured permanent work and materials on site are cash-heavy and routinely under-certified when the measure and the delivery evidence are reconstructed rather than captured. Variations are the sharpest case: a variation is an instruction, the work done under it, and a valuation basis, and when those three live in different places the line is certified late, partially, or not at all, and delivered work quietly becomes a claim and then a dispute. Retention and backcharges run the other way, as deductions the contractor finances or absorbs when it cannot track or contest them inside the contractual windows. Every one of these is an evidence-timing problem wearing a cash costume.
This is why the failure is structural rather than a negotiation weakness. A strong commercial team can argue hard at every valuation and still be certified down, because argument at certification cannot substitute for evidence that was never captured when the work was done. The contractor that is exposed here is not the one with a tough client; it is the one whose evidence is always one week behind the valuation, so every certificate is a partial reconstruction of a month it did not record.
The shift in one observation
A cash problem in UAE construction is usually a data problem that has travelled downstream. The certified amount is the sum of what each line can prove at the moment the valuation is cut, and a contractor that captures the proof a week after the work is certified down to last week's records every month. Fixing the chase without fixing the capture changes the conversation and not the cash.
Where the Cash-Chase Model Breaks
The treat-it-as-cash model breaks in four predictable places at every valuation.
Measured work certified to last week
When the measure is reconstructed at valuation, the certifier supports only what is substantiated on the spot. The contractor is paid for what it can prove that week, and the gap between built and certified is financed by the contractor until, and if, it is recovered.
Materials on site under-claimed
Payment for materials on site depends on linking delivery and storage to the contract conditions. When that link is assembled late, real cash sits uncertified for want of a record that existed but was never connected to the claim in time.
Variations becoming disputes
A variation whose instruction, work, and valuation live in different places is certified late or not at all. Delivered work turns into a claim, the claim into a dispute, and the cash that should have been certified in month three is argued in month nine.
Deductions accepted by silence
Retention releases missed and backcharges the contractor cannot quickly contest are deductions accepted by silence. Without a live position and the evidence to test a deduction inside its window, the contractor finances or absorbs cash it was entitled to keep.
The Numbers
Two Ways to Treat Certification
The difference between contractors certified close to what they build and those certified down every month is whether the evidence is captured as work happens or assembled at the valuation.
| Component | Assembled at valuation | Captured as work happens |
|---|---|---|
| Measured work | Reconstructed from memory, certified to what is provable that week. | Captured against the bill as built, certified to what was done. |
| Materials on site | Under-claimed because the link to conditions is late. | Linked to claim conditions at delivery, supportable on the day. |
| Variations | Instruction, work, and valuation separate. Becomes a dispute. | One chain from instruction to valuation, evidenced when claimed. |
| Retention | Tracked loosely, releases missed. | A live position, releases claimed on time. |
| Deductions | Accepted by silence, cannot be tested in time. | Captured with evidence, contestable inside the window. |
A contractor that is certified down every month does not usually have a tough client. It has evidence that is always one week behind the valuation, so every certificate is a partial reconstruction. The cash follows the data, and the contractor that fixes only the chase runs the same exercise again next month.
What Capturing the Evidence Looks Like
The pattern in contractors certified close to what they build is recognisable. Progress and measurement are captured against the bill as the work is done, so the valuation line arrives evidenced rather than defended after it is queried. Materials on site are linked to the claim conditions at delivery. Variations are tracked from instruction through executed work to valuation as one chain, so entitlement is provable when claimed instead of argued later. Retention is a live position against the contract and its milestones, and deductions arrive with the evidence and notice that let the contractor test them inside the window. The certificate becomes an assessment of evidence that already exists, which is faster, less contested, and closer to what was actually delivered.
This does not necessarily mean replacing the cost or commercial systems already in place. In many contractors the evidence capture can be built around the existing systems so substantiation becomes a by-product of doing the work rather than a monthly reconstruction. Replacement becomes the better option mainly where the existing systems cannot link measurement, materials, and variations to the claim at the point they occur. Which applies is specific to the systems in place, and is established in scoping before any build commitment.
How This Sits Alongside the Contractor's Own Responsibilities
The configuration keeps a clear separation. The contractor runs the works, prepares and owns its claims, holds the relationships with the client, engineer, and certifier, makes every commercial and contractual decision, and is responsible for its own contractual compliance. The software is the instrumentation: capturing the substantiation as work happens so the claim is defensible and the certified amount reflects what was delivered.
This is the role BY BANKS is positioned for. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the contractor who runs it. We do not prepare or certify valuations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. The contractor owns its claims, its commercial decisions, and its own compliance; we build the system that captures the evidence the claim is built from. The accountable party leads and owns the obligations; we build to their direction.
Where This Analysis Is Useful
The conversations where this perspective is most useful tend to be at three moments: a contractor whose certified amounts are persistently below delivered value and has been treating it as client behaviour; a commercial director who realises every valuation is a reconstruction; or an owner reviewing why variations keep ending up in dispute rather than in a certificate. The honest answer is usually the same: the cash follows the data, the evidence is captured too late, and chasing the certificate harder does not change a number that was fixed by what was provable that week.
For broader related work, see our perspective on why construction programmes in Dubai recover the wrong way and our perspective on the hidden cost of fragmented construction systems. The applied work sits across our construction cost tracking software, construction reporting dashboard, and construction workflow automation capabilities, within the broader construction software practice and our operational platforms work. Get in touch if a 45-minute conversation about a specific certification picture would be useful.
Frequently Asked Questions
No. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the contractor who runs it. We do not prepare or certify valuations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. On any engagement, the contractor owns its claims, its commercial decisions, and its own contractual compliance. We build the system that captures the substantiation; the contractor and the contract administration own the valuation process.
No, and that is not the claim. Capture does not create entitlement; it evidences entitlement that already exists. Where a contractor is certified down because genuinely delivered work was not provable at valuation, instrumentation closes that evidence gap. It does not support claiming work not done, and it does not change what the contract entitles the contractor to. It changes whether genuine entitlement is provable when the valuation is cut rather than reconstructed and discounted.
No. They are an observational generalisation of how interim valuations are commonly substantiated, used to make the data point clear. They describe no specific contract, project, certifier, or determination. Entitlement is governed by the contract terms in each case, not by this article, and contractors should rely on their contract and qualified commercial and legal advice for any specific position.
Often not. In many contractors the evidence capture can be built around the cost and commercial systems already in place, so substantiation becomes a by-product of doing the work. Replacement becomes the better option mainly where the existing systems cannot link measurement, materials, and variations to the claim at the point they occur. Which applies is specific to the systems in place and is established in scoping before any build commitment.
It is sequenced and does not require pausing the works. The usual starting point is the component with the most cash and the weakest evidence timing, often variations or measured work, captured as a chain from the next valuation cycle. Materials on site and the retention and deduction positions follow. The order is driven by where the largest provable-but-uncertified cash currently sits, which scoping establishes for the specific project.
Payment certification in UAE construction is widely treated as a cash chase and is in practice a data problem that has travelled downstream. The certified amount is the sum of what each component can prove when the valuation is cut, and a contractor that assembles the proof a week late is certified to last week's records every month. The contractors certified close to what they build are the ones who capture the substantiation as the work happens, so the valuation is an assessment of evidence that already exists. The build is software work; the claims, the commercial and contractual decisions, and contractual compliance remain entirely the contractor's, and the system simply captures the evidence the certified amount is built from so the cash is not lost in the week between doing the work and being able to prove it.
References to FIDIC-family contracts and UAE construction certification practice are descriptive of publicly known frameworks. This article cites no market figures; the valuation components and evidence states are an observational generalisation, not a specific contract, valuation, or determination. Patterns and observations reflect our perspective and are observational estimates rather than measured statistics. BY BANKS is an independent software engineering company; we do not prepare or certify valuations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. On any engagement, the contractor owns its claims, its commercial decisions, and responsibility for its own contractual compliance. This article is not contractual, commercial, quantity-surveying, or legal advice; contractors should obtain qualified advice for their specific obligations. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation