UCP 600 Article 39: Rights and Obligations Under Assignment of Proceeds

Introduction

The structural illusion is that the assignee inherits the beneficiary's rights against the issuing bank. Operations teams then compile local manuals that mutate Article 39 into a four-part code — 39(a), 39(b), 39(c), 39(d) — as if UCP 600 published lettered sub-articles.

It did not. Article 39 is a single paragraph. The published text is:

The fact that a credit is not stated to be transferable shall not affect the right of the beneficiary to assign any proceeds to which it may be or may become entitled under the credit, in accordance with the provisions of applicable law. This article relates only to the assignment of proceeds and not to the assignment of the right to perform under the credit.

This guide isolates the assignee's position is derivative of proceeds the beneficiary may become entitled to. The failure mode is systemic: once a desk invents sub-articles, every later checklist, SWIFT clause, and dispute memo inherits a rule that does not exist. The binary test is simple. If a claim cannot be read out of those two sentences, it is not an Article 39 rule.

Failure Mode Analysis

Failure Mode 1: Fabricated sub-articles

A manual states "Article 39(a) lets the beneficiary assign, 39(b) excuses the bank, 39(c) requires written bank confirmation, 39(d) makes the assignee's right derivative." Those letters are not in UCP 600. Desks that treat them as law will violate the second sentence the moment they let an assignee perform. Truncate the manual. Cite the paragraph.

Failure Mode 2: Assignment treated as transfer

The credit is silent on transfer. A supplier is named as "assignee" and presents documents in its own name. Article 38 never ran. Article 39 says the right to perform was not assigned. The bank that honours that presentation as if a transfer occurred has mutated payment mechanics into a transfer without Article 38(a) consent.

Failure Mode 3: Applicable law skipped

The beneficiary emails the issuing bank "pay X." No instrument that applicable law would recognise as an assignment is completed. Operations treats the email as a UCP event. Article 39 does not compile that email into an assignment. The systemic result is competing claims to the same proceeds with no deterministic ranking under UCP.

Deterministic Resolution Architecture

1. Isolate the instrument. If the request is to move the right to perform, stop and test Article 38(a)–(e). If the request is only to redirect proceeds, stay on Article 39.
2. Quote the two sentences. Refuse any internal clause that cites Article 39(a), 39(b), 39(c), or 39(d).
3. Map "may be or may become entitled." No complying presentation, no proceeds. The assignee cannot outrun the beneficiary's documentary position.
4. Hand mechanics to applicable law: notice, acknowledgement, competing assignments, insolvency ranking. Do not invent UCP fields for those steps.
5. Keep presentation with the beneficiary (or its agent). Do not let the assignee present as if it were a second beneficiary under Article 38(b).
6. Examine documents under Article 14 on their face. If discrepant, refuse under Article 16. Do not launder a routing fight into a discrepancy label unless a document actually fails the credit.
7. Leave Articles 7, 8 and 10 untouched. Assignment does not mutate the undertaking or the amendment engine.
8. Compile an operational file: assignment instrument, law chosen or implied, bank acknowledgement if the bank agrees to honour routing, and a binary flag — proceeds only / not performance.

Conclusion

Article 39 is a binary scope rule, not a hidden code. It preserves assignment of proceeds even when the credit is not transferable, and it forbids treating that assignment as a transfer of the right to perform. Everything else — notice, consent, cut-off, ranking — is applicable law plus the bank's own decision to act. Inventing 39(a)–(d) is a systemic documentation failure. Read the paragraph. Isolate proceeds from performance. Stop there.

FAQ

Does UCP 600 Article 39 contain sub-articles (a) through (d)?

No. Article 39 is one paragraph of two sentences. Lettered 39(a)–(d) citations are not UCP 600 text.

Can the beneficiary assign proceeds if the credit is not transferable?

Yes. The first sentence of Article 39 states that the fact that a credit is not stated to be transferable shall not affect that right, in accordance with applicable law.

Does assignment of proceeds let the assignee present documents and perform?

No. The second sentence states that the article relates only to assignment of proceeds and not to assignment of the right to perform. Performance movement is Article 38, and only if the credit is transferable and a transferring bank consents under Article 38(a).

If the bank never acknowledges the assignment, has UCP 600 been violated?

Not by silence alone. Article 39 does not compile a mandatory bank acknowledgement form. Whether the assignment is effective against the bank is a question of applicable law and of whether the bank agrees to redirect payment.

Are assignment defects documentary discrepancies under Article 16?

Not merely because an assignment exists. Article 16 addresses a bank that determines a presentation is discrepant. Assignment of proceeds is a payment-routing construct sitting beside the presentation, not a substitute for Article 14 examination.