Multiple Demand Guarantees Supporting One Contract

Introduction

A single commercial contract may be supported by several guarantees: advance-payment, performance, retention, warranty, or counter-guarantee instruments. The existence of a common underlying contract does not make the guarantees one instrument. Each guarantee has its own wording, expiry, presentation route, and payment conditions.

Current guarantee-market reporting provides operational context. The controlling analysis is instrument-by-instrument against the operative guarantee and URDG 758 when incorporated.

Failure Mode Analysis

Failure Mode 1: One expiry date used for every guarantee

The operations team records the contract end date as the expiry for all guarantees. Individual instruments may expire earlier, later, or on different conditions.

Failure Mode 2: Demand under the wrong instrument

A beneficiary sends a demand that identifies the contract but does not identify which guarantee is called, or applies the supporting statement required by one guarantee to another.

Failure Mode 3: Counter-guarantee treated as beneficiary payment instrument

The counter-guarantee is used as though it were the guarantee issued to the beneficiary. The presentation channel and documents may be different, causing an avoidable failure.

Deterministic Resolution Architecture

1. Build a separate record for every guarantee and counter-guarantee.
2. Capture instrument number, amount, expiry, presentation place, channel, and required demand wording.
3. Map each guarantee to the contract obligation it supports without merging document rules.
4. Test a demand against the specific guarantee being called.
5. Preserve reduction, release, amendment, and extension records separately.
6. Route beneficiary and bank-to-bank presentations through the correct channels.
7. Review overlapping guarantees for double-call risk and governing-law consequences.

Instrument Control Matrix

The matrix prevents one contract identifier from becoming a substitute for the guarantee number and terms. A demand must identify the instrument being called and satisfy that instrument’s requirements.

Conclusion

Multiple guarantees are a portfolio of separate obligations, not one enlarged documentary credit. The correct control is instrument-level isolation: one record, one expiry, one presentation route, and one demand checklist for each guarantee.

Each demand should be independently approved against the guarantee record before delivery. This isolates amount, expiry, delivery, and supporting-document risk even when all instruments arise from the same commercial contract.

The correct control is instrument-level isolation: one record, one expiry, one presentation route, and one demand checklist for each guarantee.

FAQ

Can one demand call several guarantees?
Only if the instruments and applicable rules permit that structure. Identify each guarantee and satisfy each separate requirement.

Does the contract expiry control every guarantee?
No. Each guarantee’s operative wording controls its expiry and extension mechanics.

Is a counter-guarantee presented by the beneficiary?
Not necessarily. Its parties and presentation route must be read from the counter-guarantee itself.

Why keep separate records?
Separate records prevent expiry, amount, wording, and delivery evidence from one instrument being applied incorrectly to another.

Source Notes

• Canonical authority: each operative guarantee and URDG 758 where incorporated.
• Live context: current URDG 758 and guarantee-market coverage surfaced through Google News RSS. Context only.