A Bank Guarantee Is the Only Document You Own That Expires by Being Ignored
· 10 min read · Written by Faceela Research & Editorial Team
A contractor finishes a job in 2024. The final account is settled, the retention is released, the file is closed, and the project appears on no report anybody runs.
The performance bond issued against it is still live at the bank in 2026. Nobody cancelled it, because cancelling it required somebody to ask the client to return the original, and asking was nobody's job once the job was over. The contractor has been paying commission on it for two years and carrying its face value against a facility limit that is the reason the last tender came back unbonded.
This is not rare. It is the ordinary condition of a contracting business with more than about four completed projects, and the reason is structural rather than careless.
Every other document a contractor produces ends by being completed. A payment certificate is superseded by the next one. A variation reaches a certificate and stops existing as an open item. A subcontract closes at its final account. A guarantee does none of that. It is discharged by the passage of a date, or by the beneficiary handing back a piece of paper, and neither of those is caused by anything happening on site.
So the guarantee is the only instrument in the business whose end state has to be chased. And it is simultaneously the only one that appears on no ledger, because a contingent liability is by definition not a liability yet.
That combination — an obligation nothing closes, recorded nowhere anyone looks — is the whole of this article.
The bank pays. Your dispute is not its problem.
Start with what the instrument actually is, because a great deal of contractor behaviour makes sense only if you believe it is something else.
The governing law is Federal Decree-Law No. 50 of 2022 on Commercial Transactions, in force from 2 January 2023, which replaced Federal Law No. 18 of 1993. Its Article 414 defines a letter of guarantee as an undertaking by the guarantor bank, at its customer's request, to pay "unconditionally and without restrictions" a certain or determinable sum to the beneficiary — unless the letter itself is conditional — where payment is demanded within the time limit stated in the letter.
Article 417(1) then closes the door most contractors expect to be open. The bank may not refuse payment for a reason arising out of the bank's relationship with the applicant, or out of the applicant's relationship with the beneficiary.
Read that plainly. Your client can call the bond while you are in a live dispute with him about whether he is entitled to. The bank pays. It is not adjudicating your contract, and it is not permitted to. Article 411(2) makes the bank's liability joint, and Article 413 makes issuing the guarantee a commercial activity regardless of the capacity or purpose of the person guaranteed — the instrument is designed to be liquid, and liquidity is exactly what it is being paid for.
There is one route to stopping payment and it is a court's, not yours. Article 417(2) allows the bank to refrain where an enforceable order or judgment imposes seizure on the guarantee amount, and puts the burden on the applicant to have "serious and confirmed grounds." That is an injunction, obtained in advance, on evidence. It is not a phone call to your relationship manager on the morning the demand lands.
The practical consequence is the one to carry into everything below: an on-demand guarantee is cash you have already given the client, held at a bank, releasable at his signature. Model it as a contract claim and every decision downstream is wrong.
The only thing that discharges it is a date
Article 418(1) is the load-bearing sentence, and it is worth quoting the shape of it exactly, because the tail is where the money is.
The bank is discharged if, within the validity period, no request for payment is received from the beneficiary — "unless it had been expressly agreed to renew said term prior to its expiry." Article 418(2) then returns the applicant's securities when the term expires without payment, unless otherwise agreed.
Three things follow, and each of them is a systems requirement wearing legal clothes.
The expiry date is the instrument. Not the project status, not the taking-over certificate, not the final account. A guarantee against a job you completed two years ago and whose expiry is open-ended is a live, callable exposure. Nothing you did on site touched it.
Renewal is agreed before expiry or not at all. The article is explicit about the ordering. Which means the deadline you actually have to manage is not the expiry date — it is the notice window that sits some weeks in front of it, and that window belongs to your bank's own terms and to whatever the contract requires by way of notice to the beneficiary. A guarantee discovered to be expiring next Tuesday is a guarantee that has already cost you something, whichever way it goes.
"Otherwise agreed" is doing an enormous amount of work in that second clause. The particular conditions on a UAE construction contract are amended as routinely as the payment period is, and the arrangement that most often replaces the default is the one your bank will call evergreen or an extend-or-pay provision: unless the guarantee is extended, the beneficiary may demand payment. Under that shape, letting an expiry arrive without acting does not release you — it triggers the call. The default in Article 418(1) and the clause in your letter can point in opposite directions, and only one of them is in the file.
Which is the point. There is no reading of any of this in which the answer lives anywhere but in the dates on the instruments, and the dates on the instruments live in a folder.
Four instruments, four clocks, and only one of them belongs to the same person
"Bank guarantee" is not one thing. A contractor of any size is carrying several kinds at once, and they are secured against different risks, die on different events, and are chased — where they are chased at all — by different people.
| Instrument | What it secures | What should end it | Who notices |
|---|---|---|---|
| Tender / bid bond | That you will sign if you win | Award to someone else, or the contract being signed | Nobody, once the tender is lost |
| Advance payment guarantee | Repayment of the advance | The advance balance reaching zero | Commercial, if anyone |
| Performance bond | Your performance of the works | Taking over, or the end of the defects period | Whoever closes the project |
| Retention guarantee | Money released early in place of cash retention | The retention release dates | Finance |
| Labour / visa guarantees | Statutory obligations, not the contract at all | A regulatory event | HR, on a different calendar |
The first row is the cheapest to fix and the most frequently missed, because the trigger is an event that produces no document in your business at all. You do not win the tender. Nothing arrives. There is no record created by not being awarded a job, and so the bond sits there, quietly consuming facility, until an annual review finds it.
The second row is the one already covered in the advance payment as a loan with three numbers that must move together — the guarantee's face value should step down as the advance balance is recovered from your certificates, and it usually does not, because the balance lives in the commercial system and the guarantee lives in a finance folder with nothing joining them.
The fourth row is the one contractors misread as a favour. A retention guarantee is not the client being generous; it is a swap. You get the cash released now, and in exchange the security against your defects obligations moves from money the client was already holding to an instrument your bank issues and you pay for. Whether that trade is worth it is an arithmetic question about your own cost of funds against the commission — and the position you are trading out of is the one sized in retention as the largest interest-free loan most contractors make without deciding to.
What an instrument nobody killed actually costs
Two costs, and the smaller one is the one people notice.
The commission is visible, because it appears on a bank statement. It is charged on the face value, for as long as the instrument is live, at whatever your facility letter says — which is a figure you have and I do not, and it is the only rate that matters here.
The facility consumption is invisible and usually the larger cost. A guarantee occupies a limit. That limit is finite, and it is the same limit the next project's bonds have to come out of. A dead guarantee nobody cancelled does not just cost its commission; it costs the tender you could not bond, and that cost appears on no statement, in no variance report, and in no conversation — because the shape of it is an absence.
The numbers below are illustrative. Yours are on your own facility letter and your own guarantee register, and assembling them is an afternoon.
| Amount | |
|---|---|
| Guarantees outstanding, face value | 12,000,000 |
| Of which relate to projects closed more than a year ago | 3,500,000 |
| Commission on the dead portion, at an illustrative 1.5% per annum | 52,500 |
| Facility headroom the dead portion occupies | 3,500,000 |
The bottom row has no currency figure that means anything, and that is precisely why it never gets discussed. It is not a cost. It is a capacity that was spent on nothing, and the only way it becomes visible is if somebody produces the list.
Which takes one question: what guarantees are live against projects that are closed? In a business where that is a query, it gets asked quarterly and the answer is small. In a business where it is a filing exercise, it gets asked when the bank declines something, which is the point at which the answer is expensive.
Where a system either holds this or does not
None of the above requires judgement once the facts are recorded. All of it requires the facts to be records rather than scans, and this is the class of problem most contractors' systems have not been asked to solve, because guarantees are felt to be a banking matter rather than a project one.
Four things have to be true.
The guarantee has to be a record on the contract, not a PDF in a folder. Issuing bank, beneficiary, face value, currency, issue date, expiry date, the notice window in front of the expiry, the type, and the contract it belongs to. A scanned original is evidence; it is not data, and nothing can be derived from it.
The expiry has to raise an obligation for a named person before the notice window opens, not before the expiry. This is the distinction the whole thing turns on. An alert on the expiry date is an alert that arrives after the decision had to be made — Article 418(1) requires renewal to be agreed prior to expiry, and an evergreen clause turns a missed window into a demand rather than a release. The clock a system has to watch is the earlier one.
The face value has to be reducible, and the reduction has to be triggered by something the system already knows. The advance guarantee steps down against a recovery balance the certificates are already computing. The performance bond steps down at taking over, an event the project already has. If the reduction depends on a person remembering to connect two records, the reduction does not happen — that is not a prediction, it is the observed behaviour of every contracting business that has not built the link.
The register has to net against the facility. Total issued, by bank, against the limit, with headroom as a live figure. A contractor who can see headroom before pricing a tender is making a different decision from one who finds out at issuance.
And a fifth that is small and worth stating because Article 414 requires it and nobody checks it: the letter shall state the object for which it has been issued. That stated object should match the contract the record is attached to. Where a guarantee has been rolled, extended, or reissued across a variation in scope, the object on the face and the obligation in the file can drift apart — and the moment that matters is the moment somebody is arguing about whether a demand was properly made.
What to make a vendor show you
On one contract, on a live screen, in this order:
- Record a guarantee against a contract with its type, face value, issue date and expiry, and show it as a record with fields rather than an attachment.
- Show the notice window computed in front of the expiry, and an obligation raised for a named person when that window opens.
- Recover a slice of an advance on a certificate and show the linked guarantee's reducible value moving with the balance.
- Close a project, and show every live guarantee against it surfacing as something to be released.
- Produce the register netted against the facility limit, by bank, with headroom.
- Show the total face value of guarantees live against projects closed more than twelve months ago.
- Lose a tender, and show the bid bond appearing on a list without anybody creating a document.
Item 7 is the one that separates a product from a demo, and it is the same shape as the twelve-month clock in the VAT article: a system that only reacts to documents cannot react to a document that was never produced. Losing a tender generates nothing. Somebody has to have decided, at design time, that the absence of an award is itself an event.
Item 4 is the one worth insisting on second, because project closure is exactly the moment when everyone's attention leaves, and the correct behaviour of a system is to hold on to the last obligations after the humans have moved on.
The wider set of things a contractor's system has to do before it is worth paying for is in what a contractor's system has to do before it is worth buying.
The short version
A guarantee is cash you have handed the client in advance, held at a bank, releasable on his demand and not defensible by your dispute with him. That is not an opinion about market practice — it is Articles 414 and 417 of Federal Decree-Law 50 of 2022, and the only exception in them is a court order obtained before the demand arrives.
It ends when a date passes, and only then, and renewal has to be agreed before that date rather than after it. So the field that controls the largest contingent exposure in a contracting business is an expiry date, sitting in a folder, owned by nobody in particular, watched at whatever interval a person happens to look.
The cost of not watching it comes in two parts. The commission you can see, and the facility headroom you cannot — which is spent on nothing, appears on no report, and shows up as a tender you quietly could not bond.
Every part of that is arithmetic on dates. None of it is difficult. It is simply not anybody's document, which is the same reason the hours spent rebuilding this picture by hand never get costed either.
What it looks like built — the guarantee as a record on the contract, the notice window ahead of the expiry, the face value stepping down against a balance the certificates already compute — is on the contracting page, and the system on it is Movinti, the contracting suite we built on Odoo. The payment certificate is what most of these instruments are attached to, and it is the document the whole loop runs through.
This article describes how the law is written and how the instruments behave. It is not legal advice on your guarantees, and the wording of a particular letter can and does displace the default. Read it, then read your own letters against it with your counsel and your bank.