Chasing payment for Saudi contractors — chase the certificate first, the date second
Most late payment for Saudi contractors does not happen in the accounts department; it happens two steps earlier, at certification of the mustakhlas. This guide explains the approval chain as it actually runs, where money sticks at each link, and how a small firm follows its claim until certification becomes a payment.
Where does a claim actually stick?
An interim claim usually passes three stations before payment is even discussed: the consultant or owner's engineer reviews the quantities, certifies the claim, and it is then raised to the client's finance side and paid per the contract terms. Two weeks lost at the first station means the payment clock itself has not started — most contracts count the payment period from certification, or from completion of named documents, not from the day you submitted.
The productive question is therefore not "when will you pay?" but "where is my claim now, and what does it need to move?". The answer sets your step: a disputed quantity is fixed by a joint measurement; a certified claim waiting on a finance cycle is fixed by dated follow-up, not random pressure.
Follow-up habits that move certification
Submit on the client's dates, not yours, backed by dated progress photos and signed measurements where possible — a claim that enters the certification cycle complete does not come back with gaps. Keep one follow-up log per claim: submission date, who reviewed it, what was asked, when it arrived — disputes about "I submitted a month ago" are settled by the log, not by memory.
Remind before the due date, not after: a short, professional message at certification asking for the expected payment date builds the relationship and surfaces trouble early. The general reminder rhythm is in the late-payment guide; this one adds the Saudi certification chain on top.
When do you escalate, and how?
When delay clearly exceeds the contract terms and after documented follow-up, communication moves from reminder to formal letter: the contract and claim references, its value and certification date, and the amount due — without threats the writer does not intend to carry out. On large disputes, legal advice is a calculated cost: a single claim for a small contractor can exceed the profit of whole projects.
And before escalating, audit your own file: are the handover documents and guarantees the payment depends on complete? A fair share of contractor "delay" is a missing document in their own file — and that fix is in your hands today.
Keep reading
Guides
Plain answers for small trade firms in the UAE and Saudi Arabia: chasing payment, retention, VAT invoices, deposits…
Read →Chasing late payment
A reminder ladder for late invoices: what to send, when to send it, and when to pause work — firm, polite, and writ…
Read →Retention money
How retention works on UAE construction jobs: what is held from each payment, when each half comes back, and how to…
Read →Tax invoice anatomy
The anatomy of a UAE tax invoice: the words Tax Invoice, your TRN, a sequential number, VAT per line — each field e…
Read →Asked often, answered straight.
Why is my payment late when the work is done?+
Because payment follows certification of the claim, not execution of the work: quantity review, the consultant's certification and the claim's journey to finance all precede the start of the payment period in most contracts. Knowing your claim's current station is half the follow-up.
Who do I chase first?+
Whoever holds the current station: the certifying engineer if the claim is under review, finance if it is certified and waiting on a cycle. The right question: where does it stand, and what does it need to move?
Should I stop work when payment is late?+
That is a contract decision with notice procedures in most contracts. Follow yours in writing rather than stopping informally, and take legal advice if the sum is large.
What is the best record for following claims?+
One line per claim: its value, submission date, who is reviewing it, what they asked for, the certification date and the expected payment date — a dated log settles "since when" arguments and exposes stalls early.