Deep Dive into MT 767: Amendment to a Demand Guarantee or Standby Letter of Credit

Introduction

When a bank issues a demand guarantee or standby letter of credit, the parties must communicate changes through the SWIFT network. The MT 767 message type handles amendments to these financial instruments. This guide explores the regulatory framework, common failure modes, and resolution steps for MT 767 amendments.

Failure Modes

1. Ambiguous Amendment Language

Banks frequently reject MT 767 amendments when the narrative field contains vague or contradictory language. Phrases like "amend as per request" without specifying the exact changes create uncertainty.

2. Missing Beneficiary Consent

Under URDG 758, an amendment is not effective without the beneficiary's consent. Banks sometimes process amendments before obtaining this required consent, leading to disputes.

3. Incorrect Reference Numbers

Field 21 (Related Reference) must match the original guarantee reference exactly. Even minor discrepancies — such as extra spaces or different formatting — cause the amendment to be rejected.

4. Timing Issues

Amendments sent close to the expiry date of the original guarantee create confusion about whether the amendment or original terms govern the transaction.

5. Partial Amendment Rejection

When an MT 767 contains multiple changes, beneficiaries sometimes accept some terms but reject others. The SWIFT protocol does not support partial acceptance, creating operational challenges.

Resolution Steps

1. Review the original guarantee — Compare the MT 767 fields against the original MT 760 (issuance) or MT 761 (first advice) to ensure consistency.

2. Verify beneficiary consent — Confirm the beneficiary has received and accepted the amendment before the guarantor considers it effective.

3. Check reference field alignment — Ensure Field 21 matches the original guarantee reference without modifications.

4. Clarify narrative language — If Field 77A contains ambiguous terms, request a replacement MT 767 with precise language.

5. Confirm expiry dates — Verify that Field 31E (new expiry) aligns with the amended terms and any presentation deadlines.

6. Escalate to SWIFT operations — If technical issues prevent message processing, contact SWIFT operations for assistance.

7. Document the amendment chain — Maintain a complete record of all MT 767 messages, acknowledgments, and beneficiary responses.

8. Seek legal review — For complex amendments involving significant changes to guarantee terms, obtain legal counsel familiar with URDG 758.

Conclusion

MT 767 amendments require precision in both content and process. Banks, guarantors, and beneficiaries must align on the specific changes, obtain required consents, and maintain accurate reference information throughout the amendment lifecycle.

Frequently Asked Questions

Q: Can an MT 767 amendment reduce the guarantee amount?

A: Under URDG 758, amendments to reduce the guarantee amount are permitted if the beneficiary consents. However, banks may require additional documentation to confirm the beneficiary's acceptance of reduced coverage.

Q: What happens if the beneficiary does not respond to an MT 767?

A: Silence does not constitute acceptance under URDG 758. The guarantor should follow up with the beneficiary to obtain explicit consent before considering the amendment effective.

Q: Can an MT 767 change the guarantor?

A: Transferring a guarantee from one guarantor to another typically requires a new guarantee issuance rather than an amendment. The MT 767 is not designed for changing the issuing institution.

Q: Is there a deadline for processing MT 767 amendments?

A: SWIFT does not impose a specific deadline, but URDG 758 requires reasonable processing time. Amendments should be sent with sufficient lead time before expiry dates.

Q: Can multiple MT 767 messages be sent for the same guarantee?

A: Yes, multiple amendments can be issued sequentially. Each amendment should reference the original guarantee and be processed in order.

Source Notes

• Trade Finance Global: "Deep dive into MT 767: amendment to a demand guarantee/standby letter of credit" — Context only; used for background on SWIFT messaging standards and amendment procedures.