URDG: Counter-Guarantee Flow
Introduction
A counter-guarantee is an undertaking issued by one bank (the counter-guarantor) to another bank (the guarantor or instructing party) in connection with a demand guarantee issued by the guarantor for the benefit of a beneficiary. The counter-guarantee flow creates a chain of obligations: the applicant requests the counter-guarantor to issue a counter-guarantee in favour of the guarantor, the guarantor uses the counter-guarantee as the basis for issuing the demand guarantee in favour of the beneficiary, and the beneficiary's demand under the primary guarantee triggers a corresponding demand under the counter-guarantee. This multi-layered structure is common in international transactions where the beneficiary requires a guarantee from a local bank in the beneficiary's country, but the applicant's bank is located elsewhere. Understanding the counter-guarantee flow under URDG 758 is essential for all parties in the guarantee chain.
Failure Mode Analysis
Failure Mode 1: Counter-Guarantor Refusal to Issue
The counter-guarantor may refuse to issue the counter-guarantee — due to credit concerns about the applicant, regulatory restrictions, or internal policy. If the counter-guarantor refuses, the guarantor cannot issue the primary guarantee, and the beneficiary is unprotected.
Consequence: The transaction cannot proceed under the guarantee structure.
Failure Mode 2: Demand Chain Disconnect
When the beneficiary presents a demand under the primary guarantee, the guarantor must present a corresponding demand under the counter-guarantee. If the guarantor fails to present the counter-guarantee demand — due to administrative error, internal processing delays, or disputes about compliance — the counter-guarantor is not obligated to pay.
Consequence: The guarantor pays the beneficiary from its own funds without counter-guarantee recovery.
Failure Mode 3: Counter-Guarantee Terms Mismatch
If the counter-guarantee's terms do not mirror the primary guarantee's terms (e.g., different expiry dates, different demand requirements, different amounts), the guarantor may face a situation where the beneficiary's demand complies with the primary guarantee but the corresponding demand does not comply with the counter-guarantee.
Consequence: The guarantor bears the payment obligation without counter-guarantee recourse.
Failure Mode 4: Fraud in the Counter-Guarantee Chain
If the beneficiary commits fraud under the primary guarantee, the counter-guarantor may seek to refuse the corresponding demand under the counter-guarantee. However, the autonomy principle (independent undertakings) means the counter-guarantor's obligation is separate from the primary guarantee. The counter-guarantor's ability to refuse based on fraud in the underlying transaction is limited.
Consequence: Complex dispute involving multiple parties and jurisdictions.
Failure Mode 5: Jurisdictional Conflicts
Counter-guarantees often involve banks in different jurisdictions. Each jurisdiction may have different legal requirements for guarantee validity, demand presentation, and fraud exception. These jurisdictional differences can complicate the counter-guarantee flow.
Consequence: Uncertainty about applicable law and dispute resolution.
Deterministic Resolution Architecture
Step 1: Counter-Guarantee Terms Alignment
Before issuance, the counter-guarantee's terms must be aligned with the primary guarantee's terms. Key alignment points: amount, currency, expiry date, demand requirements, and governing rules. The counter-guarantee should mirror the primary guarantee to ensure the demand chain functions correctly.
Step 2: Counter-Guarantor Due Diligence
The applicant should engage the counter-guarantor early to confirm its willingness to issue the counter-guarantee and to complete any required due diligence or credit assessment before the primary guarantee is issued.
Step 3: Demand Chain Protocol
The guarantor should establish a clear internal protocol for presenting demands under the counter-guarantee when a demand is received under the primary guarantee. This protocol should include: demand preparation, documentation, timing, and escalation procedures.
Step 4: Counter-Guarantee Demand Coordination
When the beneficiary presents a demand under the primary guarantee, the guarantor must present a corresponding demand under the counter-guarantee within the time limits required by the counter-guarantee. The guarantor should not delay, as the counter-guarantee's expiry may limit the window for recovery.
Step 5: Fraud Exception Management
If fraud is suspected in the demand chain, each party (beneficiary, guarantor, counter-guarantor, applicant) must assess its position under the applicable law and URDG 758. The counter-guarantor's ability to refuse a demand based on fraud in the primary guarantee depends on the counter-guarantee's terms and the applicable law.
Step 6: Jurisdictional Coordination
The counter-guarantee should specify the applicable law and dispute resolution mechanism. The primary guarantee and counter-guarantee may specify different jurisdictions, and the parties should be aware of the implications for demand presentation and dispute resolution.
Step 7: Counter-Guarantee Recovery Tracking
The guarantor should maintain records of all counter-guarantee demands presented, payments received, and any disputes. This tracking is essential for managing the guarantor's exposure and for resolving disputes about the counter-guarantee flow.
Conclusion
The counter-guarantee flow under URDG 758 creates a multi-layered obligation chain that requires careful alignment, coordination, and monitoring. Each link in the chain — applicant, counter-guarantor, guarantor, beneficiary — must understand its obligations and the flow of demands. Success depends on term alignment, timely demand presentation, and effective coordination across jurisdictions.
FAQ
Q1: Is the counter-guarantor liable to the beneficiary?
No. Under URDG 758 Article 4, the counter-guarantee is an undertaking from the counter-guarantor to the guarantor, not to the beneficiary. The beneficiary's rights are against the guarantor under the primary guarantee.
Q2: Can the counter-guarantor refuse to pay if the primary guarantee is valid?
Under URDG 758, the counter-guarantor's obligation is independent of the primary guarantee. If the demand under the counter-guarantee complies with its terms, the counter-guarantor must pay regardless of the primary guarantee's status.
Q3: What if the guarantor fails to present a demand under the counter-guarantee?
The counter-guarantor is not obligated to pay unless a complying demand is presented. If the guarantor fails to present the counter-guarantee demand, the counter-guarantor has no payment obligation.
Q4: Can the primary guarantee and counter-guarantee have different expiry dates?
Yes. The expiry dates are independent. However, the counter-guarantee's expiry should be coordinated with the primary guarantee to ensure the guarantor can recover payments made to the beneficiary.
Q5: How does the fraud exception apply to counter-guarantees?
The fraud exception's application to counter-guarantees depends on the applicable law and the counter-guarantee's terms. Under URDG 758, the autonomy principle applies — the counter-guarantee is independent of the primary guarantee. However, some jurisdictions may permit the counter-guarantor to refuse payment based on fraud in the underlying transaction.
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 as published by ICC.
- ICC Academy, "A guide to types of documentary credit" (Context only).
- ICC Academy, "Geopolitics, sanctions & trade finance: Challenges for UCP 600 & documentary credits" (Context only).
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 2 | Definitions | Binary determination (compliant/discrepant) |
| UCP 600 | Article 4 | Credits v. Contracts | Binary determination (compliant/discrepant) |
| UCP 600 | Article 6 | Availability, Expiry Date and Place for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 20 | Bill of Lading | Binary determination (compliant/discrepant) |
| UCP 600 | Article 24 | Road, Rail or Inland Waterway Transport Documents | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Counter-Guarantor Refusal to Issue | The counter-guarantor may refuse to issue the counter-guarantee — due to credit concerns about th... |
| Demand Chain Disconnect | When the beneficiary presents a demand under the primary guarantee, the guarantor must present a ... |
| Counter-Guarantee Terms Mismatch | If the counter-guarantee's terms do not mirror the primary guarantee's terms (e.g., different exp... |
| Fraud in the Counter-Guarantee Chain | If the beneficiary commits fraud under the primary guarantee, the counter-guarantor may seek to r... |
| Jurisdictional Conflicts | Counter-guarantees often involve banks in different jurisdictions. Each jurisdiction may have dif... |
← Scroll horizontally to see all columns
Get the Full LC Compliance Checklist
15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.
No spam. Unsubscribe anytime.
DraftLC generates compliant URDG — so you never face this failure mode.
DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.
No credit card required · See how DraftLC drafts compliant credits