Urdg 758 Article 15a Extra Quality Jun 2026

unless the guarantee expressly excludes it. It’s a "safety by default" setting for applicants. Documentary Only : Crucially, the bank (guarantor) does

The implications of Article 15a of URDG 758 are significant. The article provides a clear framework for guarantors to follow when extending credit to beneficiaries. By providing guidance on the circumstances under which credit may be extended, Article 15a helps to:

The compliance must be determined on a face-to-face comparison. The document must strictly appear to satisfy what the guarantee calls for. Common checks include: urdg 758 article 15a

Same as above.

Many guarantors mistakenly treat an “extend or pay” demand as automatically non-compliant because it asks for two things (extension, failing which, payment). But Article 15(a) requires the guarantor to look at the face: if the guarantee permits such a demand, it is compliant. The guarantor cannot impose a requirement that does not exist on the face of the guarantee. unless the guarantee expressly excludes it

Here’s a helpful post explaining in clear, practical terms. You can share this on a blog, LinkedIn, or internal team update.

If the guarantee requires a “Certificate of Default signed by an engineer,” and the beneficiary presents a certificate signed by “John Smith, Engineer,” the guarantor accepts it on its face even if the guarantor knows John Smith was fired last week. The bank’s role ends at visual compliance. The article provides a clear framework for guarantors

Remember: The bank looks at the paper, not the story behind it.

Article 15(a) does not require “mirror image” compliance for trivial data errors (see URDG 758 Article 14(d) for data inconsistencies). But the existence of required documents and their essential content must be there on the face.