MT700 Field 32B: Field Contradicts Other Fields

Introduction

Field 32B of the SWIFT MT700 contains the currency code and amount of the documentary credit. The field is mandatory and uses format Option B — 3!a15d, three alphabetic characters for an ISO 4217 currency code followed by up to fifteen digits for the amount. Because the credit amount underpins tolerance, drawings, and the maximum credit rules, a conflict between 32B and a neighbouring field is a primary source of credit discrepancies.

This guide covers the contradictions that arise between 32B and other MT700 fields, why they occur, and how to resolve them.

Failure Modes

1. 32B amount exceeds the 39B maximum. When field 39B (Maximum Credit Amount) is present and its ceiling is lower than the 32B amount, the credit allows a drawing larger than the stated maximum.
2. 32B currency differs from the 39B or 41a currency. A mismatch in currency code between 32B and the availability or maximum fields contradicts the single-currency assumption of the credit.
3. 32B amount outside the 39A tolerance band. Field 39A (Percentage Credit Amount Tolerance) sets a plus/minus band around 32B; a 32B value that, combined with the stated tolerance, exceeds 39B is inconsistent.
4. Invalid ISO 4217 currency code. The network-validated rule (T52) rejects a currency that is not a valid ISO 4217 code, contradicting the mandatory field content.
5. Amount precision conflict with 39C additional amounts. When 39C (Additional Amounts Covered) is added, the sum must remain within any 39B ceiling; a 32B-plus-39C total that breaks the ceiling is contradictory.

Resolution

1. Confirm the 32B currency is a valid ISO 4217 code before submission to avoid T52 rejection.
2. Compare 32B against 39B; the 32B amount must be at or below the maximum credit amount.
3. Verify that 32B, 39B, and 41a all use the same currency code.
4. Apply the 39A tolerance band to 32B and confirm the upper bound does not exceed 39B.
5. Add 39C additional amounts to the 32B base and re-check against the 39B ceiling.
6. Issue an MT707 amendment where the amount, currency, or maximum must change.
7. Return conflicting instructions to the applicant for a reconciled amount and currency.
8. Record the reconciliation in the credit file to prevent repeat errors on renewals.

Conclusion

Field 32B anchors the monetary terms of the credit. Conflicts with 39A, 39B, 39C, and 41a are frequent but detectable through a structured comparison. Anchoring the check on the ISO 4217 rule (T52) and the Article 30 tolerance framework removes the most common amount discrepancies.

FAQ

1. Is 32B mandatory? Yes. The SWIFT specification lists it as Mandatory.
2. What format does 32B use? Option B, 3!a15d — a three-letter ISO 4217 currency code and up to fifteen digits.
3. What is error code T52? It signals that the 32B currency is not a valid ISO 4217 code under the network-validated rule.
4. Can 32B exceed 39B? No. The maximum credit amount in 39B must be at least the 32B amount.
5. How does 39A relate to 32B? 39A sets a percentage tolerance around the 32B amount; the resulting band must stay within any 39B ceiling.

Source Notes

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