URDG 758 Article 15: what a demand must contain so the bank pays
Article 15 of URDG 758 says what has to travel with a demand: the beneficiary’s own statement of how the principal has broken the underlying contract, plus any document the guarantee itself asks for. Add the basics from the rest of the rules and a demand the bank pays looks like this: signed, received by the guarantor before expiry, asking for a stated amount in the guarantee currency, carrying the Article 15(a) statement unless the guarantee expressly excludes it, and with no data that conflicts with the guarantee. The statement of breach is needed even when the guarantee says nothing about it. Under Russian law (Civil Code, art. 374) the demand is also in writing, with the documents the guarantee lists, and names the circumstance that triggers payment.
In the URDG 758 cases we have collected, almost every loss a beneficiary suffered came from its own demand: the amount was missing, the statement of breach was missing, or the order number did not match the guarantee.
What does a demand under URDG 758 have to contain?
At minimum: the beneficiary’s signature, a clear request for payment, an amount, the Article 15(a) statement unless the guarantee expressly excludes it, and every document the guarantee names. If any of these is missing, the guarantor may reject.
Any signed document from the beneficiary that plainly asks for payment under the guarantee counts as a demand (URDG 758, art. 2; ISDGP, para. 34). It needs no special title or form. ISDGP para. 111 boils the minimum down to a short list, which works well as a last check before sending:
- a signed original, or an authenticated message;
- a date no earlier than the guarantee allows demands to be made;
- the Article 15 statement, unless it is excluded;
- the amount.
On top of that comes whatever the guarantee itself calls for: an invoice, a certificate, a copy of a notice to the contractor. A guarantee can ask for more than the rules do, and then its wording governs.
Russian law gets to the same place by a different route. Article 374 of the Civil Code asks for a written demand, the documents listed in the guarantee, and a statement of the circumstance that entitles the beneficiary to payment, all before the guarantee expires.
Do you need a statement of breach if the guarantee does not ask for one?
Yes. Under URDG 758 the statement of breach is part of every demand unless the guarantee expressly excludes it (arts 15(a) and 15(c)). A guarantee that is simply silent has not excluded it.
Say the guarantee asks only for a “statement of entitlement to payment”, and the treasury team writes exactly that. The bank rejects: there is no statement of how the principal breached the contract.
In DOCDEX 375, the guarantees applied URDG 758 only to matters the guarantee did not itself regulate. The question was whether Article 15(a) still applied. The DOCDEX experts held that the clause did not displace the rules, and a demand without a statement of breach did not comply.
Only express wording removes the requirement. ISDGP (para. 109) treats a promise to pay without the need to prove or justify the demand as that kind of wording. If the guarantee has no such phrase and you are unsure, include the statement. It takes a line or two, and leaving it out can cost you the payment.
How much detail does the statement of breach need?
Short but specific: name the obligation the contractor failed to perform. You do not need to argue the contract dispute or attach evidence.
The sources differ here.
- The English court in Tecnicas Reunidas v Korea Development Bank said the Article 15(a) statement has to identify how, specifically, the principal has failed. That was said in passing (obiter), not as the ground of the decision, but the message is clear: a bare formula is not enough.
- In DOCDEX 374, the guarantor rejected because the statement gave no details of the breach. The experts did not uphold the rejection: Article 15(a) sets no level of detail, and a statement in the form the guarantee requires is enough.
ISDGP (paras 103–106) is closer to DOCDEX 374: you need not repeat the words of the rules, it is enough to identify the breach clearly, and short and precise is best. The safe middle for a beneficiary is one sentence that names a specific obligation.
Example wording for training, not a form to file:
The contractor is in breach of its obligations under construction contract No. [number as stated in the guarantee] dated [date as stated in the guarantee]: it failed to complete the works stage by the contractual date and has not repaid the advance.
It names the obligation and says it was not performed. Losses and correspondence can stay out of it.
How should the amount and currency be stated?
The amount is mandatory and must be in the guarantee currency. It cannot exceed what is still available under the guarantee on the day of the demand.
According to the summaries of ICC Banking Commission Opinion TA953, a demand that leaves out the amount is non-complying, so the guarantor may reject it. In the summaries, the beneficiary sent it on the expiry date, which left no time for a new demand. The opinion is known only through two summaries, so the conclusion here is a paraphrase of those.
Other points to check on the amount:
- if the amount appears in figures and in words, they must match (ISDGP, para. 112);
- the currency is the guarantee currency; a demand in another currency does not comply (ISDGP, paras 164–165);
- the amount is no more than the balance left after reductions and earlier payments (URDG 758, arts 12 and 17);
- if the guarantee asks for an invoice or another document showing an amount, the demand cannot exceed it (ISDGP, para. 118);
- give full payment details (ISDGP, para. 113). On the summaries of TA953, missing details do not by themselves make the demand non-complying, but payment can be delayed.
If the guarantee allows partial demands, you can ask for less than the full amount (art. 17). Make it obvious from the demand how much you are claiming this time.
Why would a bank reject a demand over a contract number?
Because the data in a demand must not conflict with the guarantee (URDG 758, art. 19(b)). If the demand shows a different number or date for the underlying contract, the guarantor sees a conflict and rejects.
The rules do not ask for identical wording, only for no conflict. A contract number is different: another number means another contract.
- In DOCDEX 353, the invoices and the notice of default referred to the order under a number and date that differed from the guarantee. The rejection was upheld. The beneficiary had also attached the contract, which the guarantee did not call for.
- On the summaries of Sea-Cargo Skips v State Bank of India, the demand failed to refer to the specific contract article the guarantee named, and the court found for the guarantor.
So copy the guarantee number and the contract number and date into every document from the guarantee text itself, not from your own system. The guarantee number also matters because without it the guarantor’s examination starts later (art. 14(f)). And do not attach anything the guarantee does not ask for. The guarantor disregards extra documents (art. 19(d)), but a conflict inside one of them can still start an argument.
Who signs the demand, and where does it go?
Someone with authority under the company’s records or a power of attorney signs it. It goes to the guarantor, at the address and through the channel the guarantee names, in time to arrive before expiry.
Under URDG 758:
- both the demand and a separate statement of breach must be signed; an authenticated SWIFT message is treated as signed (ISDGP, paras 44–45);
- the demand is presented to the guarantor at the place the guarantee states (art. 14). Handing it to the bank that only advised the guarantee is not presentation to the guarantor (ISDGP, para. 83);
- what counts is the date the guarantor receives it. Under URDG 758 the sending date does not save a late demand.
In two cases about the signatory, Russian courts applying the Civil Code sided with the beneficiary. In case No. А21-12367/2017 the bank rejected because no document proving the head’s authority was attached. The appeal court held that the head’s authority was visible from the state company register, and that the guarantee’s list of documents named acceptable options rather than a required set. In case No. А56-33327/2021 the head signed the demand and a different person, without a power of attorney, signed the calculation. The court read the signature condition as applying only to the demand and ordered payment. Both were won in court, not at the bank. It is simpler when one authorised signatory signs every document in the demand.
What if the bank rejects the demand anyway?
First check the rejection itself: did it arrive in time, and does it list every discrepancy? If the guarantee is still running, prepare a corrected demand and present it before expiry.
Under URDG 758 the guarantor examines the demand within 5 business days following the day it was presented and, if it rejects, to send a single notice listing every discrepancy (arts 20 and 24). If it is late or leaves something out, it can no longer say the demand does not comply. In DOCDEX 375 (C3) both demands were defective, but the guarantor missed the deadline for rejecting and lost the right to refuse them.
Do not prepare a demand counting on the guarantor to slip.
A short check before sending:
- Match the guarantee number and the contract number and date against the guarantee text.
- Check the amount, the currency and today’s available balance.
- Add the statement of breach unless the guarantee expressly excludes it.
- Attach exactly the documents the guarantee names, and nothing else.
- Check the signatory’s authority and the signatures on every document.
- Send it to the guarantor through the channel the guarantee names, well before expiry, and keep a back-up channel ready.
A URDG practice simulator, where these steps can be worked through on training scenarios, is in preparation.
Sources
- URDG 758, arts 2, 12, 14, 15(a), 15(c), 17, 19(b), 19(d), 20, 24 (paraphrased)
- ISDGP, paras 34, 44–45, 83, 103–106, 109, 111–113, 118, 164–165 (paraphrased; numbering from the online edition)
- Russian Civil Code, art. 374
- ICC Opinion TA953
- DOCDEX Decision 375
- Tecnicas Reunidas Saudia v The Korea Development Bank, [2020] EWHC 968 (TCC)
- Sea-Cargo Skips AS v State Bank of India, [2013] EWHC 177 (Comm)
- DOCDEX Decision 353
- Case No. А21-12367/2017, 13th Arbitrazh Appeal Court, 23.11.2018
- Case No. А56-33327/2021, 13th Arbitrazh Appeal Court, 22.09.2021
- DOCDEX Decision 374