Government Handover Explained: Payment Certificates, Completion Certificates, and Tracking What You're Owed
Term 28 Sep 2026 government contractscash flowcontract managementproject deliveryCRM
Handover to a government client is the documentary chain that turns completed work into money you're actually owed: a payment certificate (mustakhlas) is submitted, a completion certificate is approved, then an invoice and claim enter the disbursement cycle. Finishing the work on the ground does not create a financial entitlement. Only documented approval does.
Why this matters
What drains liquidity in firms working with government entities is rarely a loss on the job. It's the gap between "we're done" and "the money landed." The project gets closed in the sales system and booked as revenue, while the payment certificate is still sitting on a government engineer's desk waiting for a signature — and nobody can say whose desk.
The problem is organisational, not accounting. The rep considers the job finished at delivery, finance is waiting for the document, and in between sits a gap with no owner. Naming an explicit owner for every payment certificate — a person, not a department — solves half of it.
How to apply it
Treat every contractual payment as its own record with just five fields:
| Field | Why |
|---|---|
| Payment number and value | Reconciles against the contract schedule |
| Entitlement condition | What unlocks the claim: a completion percentage? A site handover? |
| Date the certificate was submitted | Starts the clock |
| Who currently holds the document | Kills the "we don't know where it is" problem |
| Expected approval date | Generates the alert automatically |
Then set two alerts: one when a certificate exceeds its usual approval window, and one before the final guarantee or maintenance period expires. In Effistar, these payments are linked to the contract record itself, so outstanding amounts appear in a single report instead of a side spreadsheet.
The rule: no project is closed in the system until the final payment is collected, no matter how complete the work is.
A hypothetical example
Take a fit-out contractor with a SAR 2 million contract across four payments. The third payment (SAR 500,000) was delivered and the certificate submitted — then sat for six weeks with the receiving engineer, who was waiting on a missing attachment nobody had been told about. With an owner and an expected approval date on that certificate, the alert would have fired in week three and the question would have been asked early.