MT700 Field 39A: Relationship with UCP

Introduction

Field 39A of the MT700 is the message-level carrier of the credit amount tolerance. The UCP 600 framework gives that tolerance its legal effect. This guide describes how the UCP framework shapes what 39A must contain and how it is applied across the life of the credit.

Failure Modes

1. Treating 39A as SWIFT-only. Ignoring the UCP basis leaves the tolerance unanchored to Article 30.
2. Decoupling 39A from 32B. The UCP framework reads 39A as a percentage of 32B; isolating it removes its base.
3. Conflicting 39A/39B under the framework. Article 30 requires the maximum drawable amount to respect both constraints; conflicting values contradict the article.
4. Assuming default tolerance persists. Where 39A is stated, the framework displaces the Article 14(b) default; assuming both apply misstates the drawable amount.
5. Malformed percentage. The 2n/2n format breach fails the SWIFT rule even where UCP intent is correct.

Resolution

1. Anchor 39A on Article 30, stating the percentage of the 32B amount drawings may vary.
2. Confirm 32B is present so the percentage has a defined base.
3. Reconcile 39A with 39B so the maximum drawable amount equals the lower of the two bounds.
4. Apply 2n/2n exactly — two digits over, slash, two digits under.
5. Where 39A is present, set aside the Article 14(b) default and document the explicit tolerance.
6. Where no tolerance is wanted, omit 39A rather than imply one.
7. Correct conflicts via MT707, referencing Article 30 in the advice.
8. Pair 39A with its UCP basis in the credit worksheet to keep renewals consistent.

Conclusion

The relationship between 39A and UCP is definitional: 39A is the percentage, and Article 30 is the rule that makes it binding. Drafting the field with Article 30 in view — 32B as base, 39B as ceiling — prevents the tolerance discrepancies that surface at drawing.

FAQ

1. What is the UCP basis for 39A? Article 30 (Tolerance in credit amount, quantity, unit prices).
2. Is 39A set by UCP or SWIFT? The format (2n/2n) is SWIFT; the tolerance effect is Article 30.
3. Must 39A reference 32B? Yes — Article 30 reads it as a percentage of the 32B credit amount.
4. Does 39A replace Article 14(b)? Where 39A is stated, it displaces the Article 14(b) default tolerance.
5. Can 39A and 39B both appear? Yes, but the maximum drawable must satisfy both.

Practical Checklist

Practical Checklist

• Confirm the field appears only where the credit structure requires it.
• Cross-check the field value against the related MT700 fields before issuance.
• Verify the cited UCP 600 article is the one that governs the field's function.
• Where the SWIFT format is fixed, do not substitute free text.
• File the source note (SWIFT SR2018 + UCP 600) with the credit record.

Source Notes

Context only. SWIFT MT700 field 39A specification (SWIFT SR2018 Category 7): format 2n/2n, Optional, definition, MT700 Usage Rules and network rules C2/C3/C4. UCP 600 relationship: Article 30 (Tolerance in credit amount, quantity, unit prices). UCP 600 text in provided dossier; citations only.