URDG: Extension of Expiry

Introduction

The expiry of a demand guarantee under URDG 758 marks the end of the beneficiary's right to present a demand for payment. When the underlying transaction requires more time than originally anticipated — possibly due to construction delays, performance issues, or commercial disputes — the beneficiary or applicant may seek to extend the guarantee's expiry. Extension of expiry under URDG 758 is a formal process that requires the agreement of all parties: the applicant (who provides the undertaking to the guarantor), the guarantor (who issues the guarantee), and the beneficiary (who holds the right to demand payment). The mechanics of extension are governed by the guarantee's terms and URDG 758's provisions on amendment and expiry. This guide examines the regulatory framework, failure modes, and resolution architectures for extension of expiry under URDG 758.

Failure Mode Analysis

Failure Mode 1: Extension Request After Expiry

The most essential failure mode. If the guarantee has already expired and the beneficiary presents a demand, the demand must be refused regardless of whether an extension was discussed. URDG 758 Article 21 is absolute — expiry terminates the right to demand. An extension request submitted after expiry is futile unless a new guarantee is issued.

Consequence: Irrevocable loss of the beneficiary's right to payment.

Failure Mode 2: Incomplete Extension Request

The extension request may be submitted without all required information — the original guarantee number, the requested new expiry date, the reason for extension, and the applicant's authorisation. An incomplete request delays processing and may result in the extension not being implemented before the original expiry.

Consequence: Gap in coverage if the extension is not processed before expiry.

Failure Mode 3: Applicant Refusal

The applicant may refuse to consent to the extension, for commercial reasons (e.g., the underlying contract has been terminated) or financial reasons (e.g., the applicant does not wish to maintain the guarantee obligation). Without the applicant's consent, the guarantor cannot amend the guarantee under Article 10.

Consequence: The guarantee expires without extension. The beneficiary loses coverage.

Failure Mode 4: Guarantor Processing Delay

Even with all parties' agreement, the guarantor may take time to process the amendment. If the extension is not formally issued before the original expiry date, the guarantee expires. The gap between the extension request and the formal amendment issuance creates a window of vulnerability.

Consequence: Temporary or permanent loss of coverage during the processing gap.

Failure Mode 5: Amendment Not Reflected in Counter-Guarantee

If the guarantee is issued through a counter-guarantee chain, the extension of the primary guarantee must also be reflected in the counter-guarantee. If the counter-guarantor does not extend its counter-guarantee, the primary guarantor may face exposure without counter-guarantee coverage.

Consequence: The primary guarantor bears risk without counter-guarantee protection.

Deterministic Resolution Architecture

Step 1: Early Extension Request

The beneficiary should submit the extension request well before the guarantee's expiry date — ideally 30–60 days in advance. This provides sufficient time for the applicant to consider the request, the guarantor to process the amendment, and the counter-guarantor (if any) to extend its counter-guarantee.

Step 2: Applicant Engagement

The beneficiary should engage the applicant directly to obtain preliminary agreement to the extension before submitting the formal request to the guarantor. The applicant's consent is a prerequisite for the guarantor to amend the guarantee under Article 10.

Step 3: Formal Extension Request to Guarantor

The beneficiary should submit a formal written extension request to the guarantor, referencing the original guarantee number, the requested new expiry date, and attaching the applicant's written consent (or evidence of the applicant's agreement).

Step 4: Counter-Guarantee Coordination

If the guarantee is issued through a counter-guarantor, the guarantor must request the counter-guarantor to extend its counter-guarantee in parallel with the primary guarantee extension. This ensures the guarantor's exposure remains covered.

Step 5: Formal Amendment Issuance

The guarantor issues a formal amendment to the guarantee, extending the expiry date. The amendment must be communicated to the beneficiary and (if applicable) the counter-guarantor.

Step 6: Interim Coverage Arrangements

If the extension process will not be completed before the original expiry, the parties should consider interim coverage arrangements — such as a short-term bridge guarantee or an undertaking from the applicant to extend the credit period.

Step 7: Post-Extension Verification

After the extension is issued, the beneficiary should verify the new expiry date, confirm receipt of the amendment, and ensure the counter-guarantee has been extended accordingly.

Conclusion

Extension of expiry under URDG 758 requires coordinated action among the beneficiary, applicant, guarantor, and (where applicable) counter-guarantor. The process must be initiated well before expiry to avoid gaps in coverage. URDG 758 Article 10 requires agreement of all parties for amendments, and Article 21's expiry provisions are absolute. Success depends on early planning, direct applicant engagement, and efficient guarantor processing.

FAQ

Q1: Can the beneficiary extend a guarantee without the applicant's consent?
No. Under URDG 758 Article 10(a), amendment of a guarantee requires the agreement of the guarantor, the applicant, and the counter-guarantee. The beneficiary cannot unilaterally extend a guarantee.

Q2: What if the guarantee contains an "auto-extension" or "evergreen" clause?
If the guarantee includes an auto-extension clause (e.g., "the guarantee shall extend for successive one-year periods unless the guarantor gives 90 days' notice of non-extension"), the guarantee extends automatically unless notice is given. The beneficiary should monitor the auto-extension mechanism and ensure timely notice (if applicable) from the guarantor.

Q3: Is there a standard extension period under URDG 758?
URDG 758 does not prescribe a standard extension period. The extension period is determined by the parties' agreement and reflected in the guarantor's amendment.

Q4: Can the guarantor refuse to extend without giving reasons?
Under URDG 758 Article 10(c), the guarantor is not bound by an amendment unless it agrees. The guarantor may refuse to extend for any reason, including commercial risk assessment or internal policy.

Q5: What happens to demands already presented before expiry?
If a demand has been presented before expiry, it remains subject to the guarantor's examination under Article 20. The expiry of the guarantee after demand presentation does not affect the validity of a demand that was timely presented.

Source Notes

• Sources referenced are from ICC Academy course descriptions and ICC publication listings (Context only). No substantive source article content was available for extraction. All regulatory citations are drawn from the official text of URDG 758 and ISDGP as published by ICC.
• ICC Academy, "Certified URDG 758 Specialist (CURDG)" (Context only).
• ICC, "International Standard Demand Guarantee Practice (ISDGP) for URDG 758" (Context only).
• ICC, "UCP 600 and ISP98: Key differences and applications" (Context only).