UCP 600

URDG 758 Article 12: Assignment Rights Under Demand Guarantees

📅 2026-07-18 8 min read UCP 600 / ISBP 745

Introduction

The assignment of proceeds under a demand guarantee is a mechanism that permits the beneficiary to transfer its right to payment to a third party — typically a financier, factor, or subcontractor — without altering the underlying guarantee obligation. Under the ICC Uniform Rules for Demand Guarantees (URDG 758), this mechanism is governed by Article 12, which establishes a deterministic framework for how assignment operates, what conditions must be satisfied, and what failure modes arise when parties misapply or ignore the assignment rules. Unlike UCP 600 Article 39, which addresses assignment of proceeds under documentary credits with a brief four-line provision, URDG 758 Article 12 provides a more detailed structural framework — but one that remains misunderstood in practice. This guide examines the operative provisions of Article 12, identifies the failure modes that arise from misapplication, and prescribes a resolution architecture that isolates each variable in the assignment chain.

Failure Mode Analysis

Failure Mode 1: Assignment Without Guarantor Notification

The most fundamental failure mode. Under Article 12(b), the assignment is ineffective against the guarantor until the guarantor receives notification. A beneficiary who executes an assignment agreement with an assignee but fails to notify the guarantor has created an enforceable obligation between itself and the assignee — but the guarantor remains bound to pay the beneficiary, not the assignee. The guarantor has no obligation to recognize an assignment it has not been notified of.

Consequence: The assignee has no right to demand payment from the guarantor. If the guarantor pays the beneficiary, the assignee's recourse is against the beneficiary only — a contractual claim that may be worthless if the beneficiary is insolvent or unreachable. This is a systemic failure that cannot be cured after payment to the beneficiary.

Failure Mode 2: Confusing Acknowledgment With Consent

Article 12(c) draws a binary distinction: acknowledgment confirms receipt; consent confirms agreement. A guarantor who acknowledges an assignment notification has not consented to pay the assignee. The guarantor remains free to pay the beneficiary directly unless the guarantee's terms or applicable law require otherwise. Parties who treat acknowledgment as consent create a false sense of security — the assignee believes it has an enforceable right against the guarantor when it does not.

Consequence: The assignee presents a demand to the guarantor expecting payment, only to discover that the guarantor has paid the beneficiary in the interim. The assignee's remedy is limited to a claim against the beneficiary — not the guarantor.

Failure Mode 3: Assignment Transferring More Than Proceeds

Article 12(e) explicitly limits assignment to the right to receive payment. The assignee does not acquire the right to make demands, enforce the guarantee, or exercise remedies under the underlying transaction. Parties who draft assignment agreements purporting to transfer these additional rights create a document that exceeds Article 12's scope. The guarantor is not bound by terms that URDG 758 does not authorize.

Consequence: The assignee attempts to present a demand in its own name, relying on the assignment agreement. The guarantor refuses the demand because the assignee is not the beneficiary under the guarantee. The assignee must then seek to compel the beneficiary to present the demand — a process that reintroduces the beneficiary as a necessary intermediary and defeats the purpose of the assignment.

Deterministic Resolution Architecture

Step 1: Pre-Assignment Due Diligence

Before executing the assignment, the beneficiary and assignee must verify: (a) the guarantee's terms do not prohibit assignment, (b) the guarantee is subject to URDG 758, (c) the assignment is limited to proceeds only, and (d) the assignee understands that acknowledgment is not consent. This step isolates the legal variables before they mutate into disputes.

Step 2: Assignment Execution

The assignment must be in writing and signed by the beneficiary. The assignment document should: (a) identify the guarantee by reference number, (b) specify the amount being assigned (which may be partial), (c) state that the assignment is limited to the right to receive payment, and (d) include the beneficiary's authorization for the guarantor to pay the assignee upon a complying demand. The assignment must not purport to transfer rights beyond what Article 12 permits.

Step 3: Guarantor Notification

The assignment notification must be delivered to the guarantor at the address specified in the guarantee or, if none, at the guarantor's principal place of business. The notification should include: (a) a copy of the assignment document, (b) a request for acknowledgment of receipt, and (c) a request for confirmation that the guarantor will pay the assignee upon a complying demand. The notification must be delivered before the guarantor pays the beneficiary — if the guarantor has already paid, the notification is too late to redirect payment.

Step 4: Guarantor Response

The guarantor must respond to the notification. Under Article 12(c), the guarantor may: (a) acknowledge receipt without consenting to pay the assignee (the default position), (b) consent to pay the assignee upon a complying demand (creating a binding obligation), or (c) refuse to acknowledge the notification entirely. The guarantor's response determines the assignee's rights. If the guarantor does not consent, the assignee's only recourse is against the beneficiary.

Step 5: Demand and Payment Protocol

When the guarantee is called, the demand must be presented by the beneficiary (or the assignee, if the guarantor has consented to pay the assignee). If the guarantor has consented to pay the assignee, the demand must be presented in compliance with Articles 6 and 7, and payment to the assignee discharges the guarantor's obligation under Article 12(d). If the guarantor has not consented, the demand must be presented by the beneficiary, and payment to the beneficiary discharges the guarantor regardless of the assignee's interest.

Conclusion

URDG 758 Article 12 creates a structured but unforgiving framework for assignment of proceeds under demand guarantees. The article's distinction between acknowledgment and consent, its limitation of assignment to proceeds only, and its requirement of guarantor notification before the assignment takes effect against the guarantor are the three operative variables that determine whether an assignment succeeds or fails. Parties who ignore these variables — by failing to notify, by treating acknowledgment as consent, or by purporting to assign more than proceeds — create disputes that URDG 758 resolves against the assignee. The deterministic resolution architecture prescribed above isolates each variable and prescribes the precise sequence of actions required to achieve a valid, enforceable assignment under Article 12.

FAQ

Q1: Can the beneficiary assign only part of the proceeds under a demand guarantee?

Yes. URDG 758 Article 12 permits partial assignment. The beneficiary may assign a specified amount of the proceeds, retaining the right to receive any remaining amount. The assignment document must clearly specify the amount being assigned. The guarantor must be notified of the partial assignment, and payment to the assignee is limited to the assigned amount.

Q2: Does the guarantor's acknowledgment of an assignment notification constitute consent to pay the assignee?

No. Article 12(c) explicitly distinguishes acknowledgment from consent. Acknowledgment confirms that the guarantor has received the notification. It does not create an obligation to pay the assignee. The guarantor remains free to pay the beneficiary directly unless it has separately consented to pay the assignee. This distinction is the most frequently misunderstood aspect of Article 12.

Q3: What happens if the guarantor pays the beneficiary after receiving the assignment notification but before responding?

The guarantor's payment to the beneficiary discharges the guarantor's obligation under the guarantee. The assignee's recourse is limited to a claim against the beneficiary under the assignment agreement. The guarantor is not liable to the assignee unless it has consented to pay the assignee before making payment to the beneficiary. This is a binary outcome: once the guarantor pays the beneficiary, the assignee's right to receive payment from the guarantor is extinguished.

Q4: Can the assignee present a demand under the guarantee in its own name?

Only if the guarantor has consented to pay the assignee and the guarantee's terms permit presentation by the assignee. Under Article 12(e), the assignee acquires only the right to receive payment — not the right to make demands. Unless the guarantor has agreed to accept demands from the assignee, the beneficiary must present the demand. The assignee's attempt to present a demand in its own name will be refused as non-complying.

Q5: Is the assignment of proceeds under URDG 758 effective against the counter-guarantor?

No. Article 12 addresses assignment only in the context of the primary guarantee. The counter-guarantee is a separate undertaking governed by its own terms. Assignment of proceeds under the primary guarantee does not automatically extend to the counter-guarantee. If the assignee wishes to have rights against the counter-guarantor, a separate assignment of the counter-guarantee's proceeds is required, subject to the counter-guarantor's notification and consent.

Did You Know?

Article 12 provides a more detailed structural framework — but one that remains misunderstood in practice.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 12NominationBinary determination (compliant/discrepant)
UCP 600Article 39Assignment of ProceedsBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 7 completed
Bank Expectations vs Common Beneficiary Mistakes
✓ What Banks Expect✗ What Beneficiaries Often Do Wrong
Assignment Without Guarantor NotificationThe most fundamental failure mode. Under Article 12(b), the assignment is ineffective against the...
Confusing Acknowledgment With ConsentArticle 12(c) draws a binary distinction: acknowledgment confirms receipt; consent confirms agree...
Assignment Transferring More Than ProceedsArticle 12(e) explicitly limits assignment to the right to receive payment. The assignee does not...

← 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 Compliance Engine

DraftLC generates compliant URDG 758 Article 12 — 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