MT700 Field 32B: Relationship with UCP

Introduction

Field 32B of the MT700 is the message-level carrier of the documentary credit's amount and currency. The UCP 600 framework gives that amount its legal and operational meaning. This guide sets out how the UCP framework shapes what 32B must contain and how it is applied during the life of the credit.

Failure Modes

1. Reading 32B as SWIFT-only. Ignoring the UCP framework leaves the tolerance and maximum structure undefined.
2. Decoupling 32B from 39A/39B. The UCP tolerance scheme requires 32B to be read with those fields; isolating it produces contradictions.
3. Wrong currency assumption. The UCP framework assumes single-currency consistency (Articles 18–19); a mixed-currency reading fails examination.
4. Over-reliance on default tolerance. Article 14(b) default is displaced once 39A or 39B is present; assuming it still applies misstates the drawable amount.
5. Invalid currency under T52. The framework does not cure a non-ISO 4217 code; the field fails the network rule regardless of UCP intent.

Resolution

1. Anchor 32B on the contract amount and currency, then validate the ISO 4217 code to clear T52.
2. Establish the tolerance scheme under Article 30: choose 39A, 39B, or the Article 14(b) default, and keep 32B consistent with it.
3. Hold 32B, 39B, and 41a in one currency to meet the Articles 18–19 consistency expectation.
4. Where no tolerance is stated, confirm the Article 14(b) default is intended and note it in the file.
5. During examination, check presented documents' currency and amounts against 32B using Articles 18–19 and 30.
6. Correct amount or currency conflicts through MT707, referencing the governing UCP article.
7. Pair every 32B entry with its UCP basis in the credit worksheet.
8. Review renewals for the same amount/currency pattern to prevent repeat defects.

Conclusion

The relationship between 32B and UCP is structural: 32B is the figure, and Articles 30, 14(b), and 18–19 are the rules that give it effect. Drafting the field with the UCP framework in view prevents the tolerance and currency discrepancies that surface at examination.

FAQ

1. What is the UCP basis for 32B? Article 30 (tolerance), with Article 14(b) default and Articles 18–19 on currency.
2. Is 32B currency set by UCP or SWIFT? The code format is SWIFT (ISO 4217, T52); the consistency requirement is UCP (Articles 18–19).
3. How does 39A connect to 32B under UCP? Article 30 uses 39A as a percentage tolerance around the 32B amount.
4. Does Article 14(b) always give tolerance? Only where the credit states no tolerance; 39A or 39B displaces it.
5. What if the invoice currency differs from 32B? Articles 18–19 treat that as a discrepancy subject to refusal.

Source Notes

Context only. SWIFT MT700 field 32B specification (SWIFT SR2018 Category 7): format Option B 3!a15d, Mandatory, definition, network-validated rule (ISO 4217, Error T52). UCP 600 relationship: Article 30 (tolerance), Article 14(b), Articles 18–19 (currency). UCP 600 text in provided dossier; citations only.