MT700 Field 32B and UCP 600 Articles
Introduction
Field 32B of the MT700 records the currency and amount of the documentary credit. While the field's format is defined by SWIFT, its monetary meaning is governed by UCP 600. This guide maps 32B to the specific UCP 600 articles that apply to the credit amount, tolerance, and currency treatment, so that drafters can justify each entry against a rule.
Failure Modes
- No tolerance awareness. Drafting 32B without reference to Article 30 leaves the 39A/39B relationship undefined.
- Assuming Article 14(b) always applies. Article 14(b) tolerance applies only where the credit permits no tolerance; it is displaced by an explicit 39A or 39B instruction.
- Currency mismatch with documents. Articles 18–19 require document currency consistency; a 32B code that differs from the invoice currency creates a refusal point.
- Amount outside 39B maximum. Article 30's maximum provision is contradicted when 32B exceeds the 39B ceiling.
- Invalid currency code. Even where UCP is satisfied, the SWIFT T52 rule rejects a non-ISO 4217 code.
Resolution
- Set 32B from the underlying contract currency and amount, then validate the ISO 4217 code (T52).
- Decide the tolerance posture: rely on Article 14(b) default, or state 39A percentage tolerance, or state 39B maximum under Article 30.
- Keep 32B, 39B, and 41a on a single currency to satisfy Articles 18–19 consistency.
- Where 39A is used, confirm the plus/minus band around 32B stays within any 39B ceiling.
- Where the credit allows no tolerance, confirm the Article 14(b) default is intended and documented.
- Review 32B against the invoice and draft currency during examination to apply Articles 18–19 correctly.
- Correct errors through MT707, citing the governing UCP article in the amendment advice.
- Maintain a mapping note linking 32B to Articles 14(b), 30, and 18–19 in the credit file.
Conclusion
Field 32B is where the credit's money terms meet the UCP tolerance and currency framework. Reading 32B through Articles 14(b), 30, and 18–19 — and respecting the SWIFT T52 currency rule — produces an amount that is both mechanically valid and substantively defensible.
FAQ
- Which UCP articles govern 32B? Article 14(b) (default tolerance), Article 30 (tolerance and maximum), and Articles 18–19 (currency treatment).
- What is the SWIFT T52 rule? It requires the 32B currency to be a valid ISO 4217 code.
- When does Article 14(b) apply? When the credit states no tolerance; it is overridden by an explicit 39A or 39B.
- How does 39B relate to 32B? 39B sets the maximum credit amount; 32B must be at or below it under Article 30.
- Must document currency match 32B? Articles 18–19 require consistency; a mismatch is a ground for 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 cited as Article 14(b), Article 30, and Articles 18–19. UCP 600 text available in provided dossier; citations only, no long passages reproduced.
Article 14(b) always applies.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 30 | Tolerance in Credit Amount, Quantity and Unit Prices | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
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 generates compliant MT700 Field 32B and UCP 600 Articles — 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