MT700 Field 45A and Its Relationship with UCP 600 Articles

Introduction

SWIFT MT700 field 45A is the goods-and-services description field. Although optional in the message structure (Option A, 100×65z narrative), it carries the definition of what the credit finances and therefore sits at the center of the UCP 600 examination. The commercial invoice — the one document required in nearly every credit — must correspond with the field 45A description, and the field's Incoterm and quantity statements ripple through the insurance, transport, and packing requirements.

This guide maps field 45A to the specific UCP 600 articles that govern its content and its interaction with the documents built from it: primarily Article 14 (standard of examination, including the no-conflict rule) and Article 18 (commercial invoice). It explains how the SWIFT narrative field becomes a UCP 600 compliance anchor.

Failure Mode Analysis

Failure Mode 1: Invoice Goods Description Does Not Correspond with Field 45A

The credit's field 45A describes "400,000 BOTTLES OF BEER." The invoice describes "BEER, ASSORTED." Under Article 18(c) the description must correspond; the vague invoice description is a discrepancy.

Failure Mode 2: Field 45A Incoterm Drives an Insurance Requirement the Document Set Misses

Field 45A states "CIF AMSTERDAM," placing insurance obligation on the seller. If field 46A requires an insurance document and the presented policy is in the buyer's name or covers the wrong voyage, the document fails to reflect the field 45A Incoterm's allocation.

Failure Mode 3: Quantity in Field 45A Conflicts with Evidenced Quantity

Field 45A states a quantity that the packing list or certificate of quantity does not evidence. The conflict is caught under Article 14(d) and the presentation is refused.

Failure Mode 4: Goods Description in Field 45A Conflicts with the Transport Document

The transport document's goods description (or package count) differs from field 45A. Although transport documents need not show a full goods description, the data they do show must not conflict with field 45A under Article 14(d).

Failure Mode 5: Field 45A References a Delivery Term That the Credit's Other Fields Undermine

Field 45A states "FCA AMSTERDAM" while field 47A imposes a condition requiring the seller to arrange ocean freight. The conflict between the Incoterm's allocation and the additional condition creates an ambiguous credit that the beneficiary cannot satisfy coherently.

Deterministic Resolution Architecture

Step 1: Treat Field 45A as the Canonical Goods Description

Record the full field 45A narrative as the benchmark for all goods-related documents. Every subsequent document preparation starts from this text.

Step 2: Map Article 18(c) Compliance for the Invoice

Draft the commercial invoice so its goods description corresponds with field 45A. Use the same product identity and quantity framing; shorten only where the credit permits, never in a way that introduces conflict.

Step 3: Translate the Incoterm into Document Requirements

Read the Incoterm in field 45A and derive which party bears freight and insurance. Confirm field 46A's document list reflects that allocation — for example, a CIF term requires a seller-arranged insurance document.

Step 4: Align Quantity and Packing Across Documents

Ensure the packing list, certificate of quantity (if any), and transport document package count all evidence the quantity and packing stated in field 45A. Resolve any variance before presentation.

Step 5: Apply Article 14(d) Across the Document Set

Check that no document carries goods data conflicting with field 45A. The no-conflict rule applies to every document, not only the invoice.

Step 6: Reconcile Field 45A with Field 47A Additional Conditions

Confirm any additional condition in field 47A is consistent with the field 45A description and Incoterm. Request amendment where a condition undermines the goods description.

Step 7: Confirm Field 44B and Routing Consistency

Where field 45A's Incoterm names a place, verify it matches field 44B and the transport routing under Article 14(e). Internal consistency avoids routing discrepancies.

Step 8: Build a Pre-Presentation Field 45A Checklist

Before submission, verify: invoice corresponds (Art 18(c)), Incoterm reflected in documents, quantity evidenced, no cross-document conflict (Art 14(d)), and 47A conditions consistent. Present only when every item is satisfied.

Conclusion

Field 45A is the SWIFT narrative that UCP 600 turns into the credit's goods benchmark. Its relationship with the articles is direct: Article 18(c) measures the invoice against it, Article 14(a) examines all documents against it, and Article 14(d) forbids any conflicting goods data. The Incoterm embedded in field 45A further drives the insurance and routing obligations scattered across the message. Treating field 45A as the single canonical description — and building every goods-related document to correspond with it — is the disciplined path to a complying presentation.

FAQ

Q1: Which UCP 600 articles govern field 45A?
Primarily Article 18 (commercial invoice, especially 18(c) correspondence) and Article 14 (standard of examination and the no-conflict rule in 14(d)). Incoterm-driven consequences also touch Article 14(e) and the insurance articles where applicable.

Q2: Must the invoice copy field 45A exactly?
No. Article 18(c) requires correspondence, not identity. The invoice may abbreviate, but it must not conflict with field 45A's goods description.

Q3: Why does the Incoterm in field 45A matter for UCP 600?
The Incoterm determines which party arranges and pays for freight and insurance. That allocation shapes which documents must appear and in whose name, engaging Article 14 and the relevant insurance or transport articles.

Q4: Is field 45A mandatory under SWIFT?
No, field 45A is optional. Most credits populate it because the invoice must correspond to a stated goods description, and a blank field 45A leaves the description to be inferred from elsewhere in the credit.

Q5: Can a discrepancy in field 45A correspondence be waived?
The applicant may waive a discrepancy after presentation, but the examining bank is not required to take up non-complying documents. Amending field 45A or correcting the invoice before presentation is the cleaner route.

Q6: Does field 45A's goods description bind the transport document?
The transport document need not show a full goods description, but any goods data it does show must not conflict with field 45A under Article 14(d). A package count or marking that contradicts field 45A is discrepant.

Source Notes

Context only: The source dossier for this guide contained the SWIFT MT700 field 45A specification (SWIFT SR2018, Category 7) and the UCP 600 article cross-reference for field 45A (Articles 14(d) and 18). No text from those sources has been reproduced. This guide was composed from first principles using the SWIFT MT700 field specification, the UCP 600 article framework, and independent analysis of field 45A's article relationships.