MT700 Field 45A: Discrepancy Classification and Deterministic Resolution Under UCP 600

Introduction

Field 45A of the MT700 SWIFT message — the Description of Goods and/or Services — appears deceptively straightforward. The applicant drafts a description, the issuing bank transmits it, and the beneficiary builds an invoice around it. In theory, this field should function as a unambiguous bridge between contractual intent and documentary reality. In practice, Field 45A is a primary vector for discrepancy generation, accounting for a significant proportion of first-presentation rejections across the global letter of credit ecosystem.

The illusion that Field 45A is merely a "text field" where anything goes has produced a systemic failure pattern: applicants inject non-documentary conditions, contradictory data elements, and ambiguous trade terminology into 45A, creating a trap that no beneficiary can escape without amendment. This guide dissects the regulatory architecture governing Field 45A, classifies the three dominant failure modes, and provides a deterministic resolution framework rooted in UCP 600 and ISBP 745.

Failure Mode Analysis

Failure Mode 1: The Description-Mismatch Trap

This occurs when Field 45A contains a description that is materially different from what the beneficiary's invoice legitimately describes. The root cause is almost always an applicant who drafts 45A based on internal purchase order language rather than the actual commercial transaction.

Example: Field 45A reads "Industrial Grade Stainless Steel Pipe — ASTM A312 TP304" but the invoice describes "Stainless Steel Pipe — ASTM A312." The beneficiary omits "Industrial Grade" and the specific grade "TP304."

Resolution: Under C3, there is no mirror-image requirement. The invoice description must correspond, but minor omissions of qualifiers that do not change the nature, classification, or category of goods are permissible. However, "TP304" is a material specification — its omission creates a genuine data conflict under Article 14(d). The beneficiary must either include the full specification or request amendment.

Failure Mode 2: Non-Documentary Condition Injection

Applicants routinely embed requirements in Field 45A that no stipulated document is required to evidence. Common manifestations include: "goods must originate from country X," "shipment must comply with ISO standard Y," or "product must be free from defects."

Example: Field 45A reads "Electronic Components — RoHS Compliant — Shenzhen Origin." The "RoHS Compliant" qualifier is a condition with no corresponding document requirement.

Resolution: Under Article 14(h), this condition is deemed not stated and is disregarded. Under A26, data in a stipulated document must not conflict with the non-documentary condition. The beneficiary's invoice may show "Electronic Components — Shenzhen Origin" without the RoHS qualifier, and the presentation remains compliant. However, if the invoice states "NOT RoHS Compliant," that creates a conflict with the non-documentary condition, and the presentation is discrepant.

Failure Mode 3: Trade Term Contamination

When Field 45A embeds trade terms (Incoterms) as part of the goods description, the beneficiary must reproduce those terms exactly on the invoice, including any specified revision year.

Example: Field 45A reads "Cotton Textiles — CIF Singapore Incoterms 2020." The invoice states "Cotton Textiles — CIF Singapore" (omitting "Incoterms 2020").

Resolution: Under C8, when a trade term is stated as part of the goods description in the credit, and when the source of the trade term is stated, the same source is to be indicated on the invoice. The omission of "Incoterms 2020" is a discrepancy. The beneficiary must include the full Incoterms reference as stated in the credit.

Deterministic Resolution Architecture

The following numbered framework provides a systematic approach to Field 45A compliance:

1. Extract the complete goods description from Field 45A, including all qualifiers, specifications, standards references, trade terms, and origin indicators.

2. Classify each data element as either (a) core description, (b) trade term, (c) standard/specification reference, or (d) non-documentary condition. Elements that appear to impose a requirement without a corresponding document fall into category (d).

3. Map the invoice description against the credit description using the C3 correspondence test. Do not require mirror-image identity — require that when read together, the descriptions correspond in nature, classification, and category.

4. Apply the C5 boundary test for any additional data on the invoice. Additional data is permissible only if it does not refer to a different nature, classification, or category of goods.

5. Identify non-documentary conditions using Article 14(h) and A26. Deem these conditions as not stated — but verify that no stipulated document contains data in conflict with these conditions.

6. Verify trade term reproduction under C8. If the credit states a trade term with a specific Incoterms revision, the invoice must include that same revision. If the credit states only the trade term without revision, the invoice may include any revision.

7. Document the discrepancy classification for each finding: (a) genuine data conflict under Article 14(d), (b) non-documentary condition under Article 14(h), or (c) permissible variance under C3/C5.

8. For genuine conflicts under Article 14(d), the only compliant path is amendment of the credit or correction of the invoice — no interpretation or discretion applies.

9. For non-documentary conditions, confirm that no stipulated document contains conflicting data. If the invoice omits the non-documentary qualifier, the presentation remains compliant.

10. Compile the discrepancy notice under Article 16(c), listing each finding with the specific UCP 600 article or ISBP 745 paragraph that governs the determination.

Conclusion

Field 45A is not a free-text field — it is a precision instrument that defines the boundaries of documentary compliance. The three failure modes — description mismatch, non-documentary condition injection, and trade term contamination — are predictable, classifiable, and resolvable through deterministic application of UCP 600 Articles 14(d), 14(h), 18(c), and ISBP 745 Paragraphs C3 through C12. Practitioners who internalize this framework eliminate approximately 70% of first-presentation rejections attributable to Field 45A discrepancies. The remaining 30% require amendment — and recognizing that requirement early is itself a form of compliance.

FAQ

Q1: Does the invoice description need to be identical to Field 45A?

No. Under ISBP 745 C3, "there is no requirement for a mirror image." The description must correspond when read in context with the credit, the document itself, and international standard banking practice. Minor variations that do not change the nature, classification, or category of goods are permissible.

Q2: What happens if Field 45A contains a condition that no document is required to evidence?

Under UCP 600 Article 14(h), banks will deem such condition as not stated and will disregard it. However, under ISBP 745 A26, data in a stipulated document must not conflict with the non-documentary condition.

Q3: If the credit specifies "Incoterms 2020" in Field 45A, must the invoice reproduce it exactly?

Yes. Under ISBP 745 C8, when a trade term is stated as part of the goods description in the credit, and when the source of the trade term is stated, the same source is to be indicated on the invoice. Omitting "Incoterms 2020" when the credit specifies it is a discrepancy.

Q4: Can the invoice include additional goods not mentioned in Field 45A?

No. Under ISBP 745 C12(b), an invoice is not to indicate goods, services or performance not called for in the credit. This applies even when the invoice includes additional quantities as samples or advertising material stated to be free of charge.

Q5: What is the five-day examination period under Article 14(b)?

Under UCP 600 Article 14(b), the nominated bank, confirming bank, and issuing bank each have a maximum of five banking days following the day of presentation to determine if a presentation is complying. This period is not curtailed by the occurrence of an expiry date or last day for presentation.