SWIFT MT700 Field 32B: Currency Code and Amount — Best Practices for Accurate Completion

Introduction

The documentary credit amount is the single most consequential data element in an MT700 message. Field 32B (Currency Code, Amount) establishes the financial boundary of the issuing bank's undertaking. An error in this field — a misplaced decimal, a wrong currency code, or a format deviation — mutates the credit's economic substance. The receiving bank cannot honour or negotiate a complying presentation if the amount in the MT700 does not reconcile with the amount in the presented documents. This guide provides a deterministic reference for Field 32B format, validation, and failure modes.

Failure Mode Analysis

FM1: Wrong Currency Code

The most catastrophic error. If Field 32B reads USD10000000 but the credit was intended to be in Euros, the entire transaction is mispriced. The beneficiary presents documents for EUR 100,000.00, the bank examines against USD 100,000.00. The discrepancy is absolute — the amount "conflicts" under Article 14(d). The issuing bank must issue an MT707 amendment to correct the currency code. This error is systemic — it cannot be waived or ignored.

FM2: Decimal Misplacement

SWIFT Field 32B uses implied decimal placement. The last two digits represent decimal places for most currencies. If the intended amount is USD 10,000.00 but the field reads USD1000000 (one million), the decimal has been shifted by two positions. The credit becomes ten times larger than intended. The sending bank's validation should catch this, but human error in data entry remains a failure mode. The receiving bank must flag the inconsistency between the SWIFT message and the credit application.

FM3: Amount Exceeds ISO 4217 Maximum

ISO 4217 defines a maximum number of decimal places per currency. JPY and KRW have zero decimal places; most others have two. If the field contains JPY10000000 but the system interprets the last two digits as decimals, the amount becomes JPY 100,000.00 instead of JPY 10,000,000. The receiving bank must know the currency's decimal classification. Field 32B does not explicitly state the decimal precision — it relies on the receiving bank's knowledge of ISO 4217.

FM4: Field 32B Missing Entirely

SWIFT rejects MT700 messages that omit mandatory fields. If Field 32B is absent, the message is rejected by the SWIFT network before it reaches the receiving bank. The credit cannot be issued without an amount.

FM5: Amount Zero or Negative

A credit with an amount of zero is economically meaningless. The SWIFT network may accept USD0000000 but the issuing bank has undertaken nothing. A negative amount is not permitted in the format. The sending bank must validate that the amount is greater than zero.

Deterministic Resolution Architecture

Step 1: Verify Field 32B Exists

Confirm that the MT700 message contains Field 32B. If the field is missing, the message is non-compliant and must be rejected or corrected by the sending bank.

Step 2: Validate the Currency Code

Verify that the first three characters of Field 32B are a valid ISO 4217 currency code. Common codes: USD, EUR, GBP, JPY, CHF, CAD, AUD, CNY. If the code is not in the ISO 4217 register, the field is non-compliant.

Step 3: Validate the Numeric Amount

Verify that the remaining characters are numeric digits only. No alpha characters, no special characters, no spaces. The format is strictly 3a15n.

Step 4: Verify Decimal Precision Matches the Currency

Confirm that the implied decimal placement matches the currency's ISO 4217 decimal classification. For JPY and KRW (zero decimal places), the entire numeric string represents whole units. For USD, EUR, GBP (two decimal places), the last two digits are decimals.

Step 5: Cross-Reference Against the Credit Application

Compare the amount in Field 32B with the amount specified in the credit application. If they differ, the issuing bank must determine whether the discrepancy is a data entry error or an intentional deviation. An MT707 amendment is required to correct the amount.

Step 6: Cross-Reference Against Presented Documents

When documents are presented, verify that the commercial invoice amount does not conflict with Field 32B under Article 14(d). A commercial invoice for an amount less than the credit amount is acceptable. An invoice for an amount exceeding the credit amount is discrepant unless the bank exercises its discretion under Article 18(b).

Step 7: If the Field Is Non-Compliant, Request Correction

If Field 32B contains an error, the sending bank must issue a corrective MT707 amendment. The receiving bank should not advise the credit until the amount is correct. The amendment must be authenticated and transmitted through SWIFT.

Conclusion

Field 32B is the financial anchor of the MT700 message. The currency code must be a valid ISO 4217 code. The numeric amount must be correctly formatted with implied decimal precision. Any deviation — wrong currency, misplaced decimal, missing field — is a deterministic failure that prevents the credit from being advised or honoured. The sending bank must validate Field 32B against the credit application before transmission. The receiving bank must validate it against the ISO 4217 register and the presented documents. There is no ambiguity in this field: it is binary — correct or incorrect.

FAQ

Q1: Can Field 32B contain a currency code that is not in ISO 4217?

No. SWIFT validates currency codes against the ISO 4217 register. A non-standard code (e.g., a fictional currency) will be rejected by the SWIFT network. The issuing bank must use a recognized currency code.

Q2: What happens if the commercial invoice amount is less than the credit amount in Field 32B?

Under UCP 600 Article 14(d), data need not be identical but must not conflict. An invoice for less than the credit amount does not conflict — the bank may honour or negotiate for the invoice amount, not the credit amount. The credit amount is a maximum, not a mandate.

Q3: How does Field 32B interact with tolerance under UCP 600 Article 30?

Article 30 permits a tolerance of plus or minus 5% in the amount if the credit does not state otherwise. Field 32B defines the base amount. The 5% tolerance applies to the examination of documents, not to the SWIFT message itself. The SWIFT amount is fixed; the document amount is examined against it with tolerance.

Q4: Can Field 32B be amended after issuance?

Yes, through an MT707 amendment message. The amendment must follow the same format rules as the original Field 32B. The beneficiary must accept the amendment for it to take effect, per UCP 600 Article 10(c).

Q5: What is the maximum amount that can be encoded in Field 32B?

The format allows up to 15 numeric digits (format 3a15n). With two implied decimal places, this supports amounts up to 999,999,999,999.99 in most currencies. For currencies with zero decimal places (JPY, KRW), the maximum is 999,999,999,999,999.