Goods Description Inconsistent with MT700 45A: The Description Boundary Under UCP 600

Introduction: The Phrase That Binds the Entire Set

Field 45A of the SWIFT MT700 states the description of goods and/or services. Every other document in the presentation — invoice, packing list, certificate of origin, transport document — must be consistent with that description. When the goods description drifts between documents, the examining bank applies a binary data-consistency determination under UCP 600 Article 14(d) and ISBP 745. The error is rarely a factual dispute; it is a compilation mutation, where an automated system projects field 45A into a draft document line and a plural noun mutates into a singular, or a qualifier is dropped. The bank does not negotiate intent; it compares strings.

Failure Mode Analysis

Failure Mode 1: Automated Projection Mutation

Document-compilation systems project structured LC data into draft lines. A plural "steel pipes" may mutate into "steel pipe" in the invoice. Under ISBP 745 this is a data-consistency failure; under UCP 600 the examining bank has a truncated window to detect it.

Failure Mode 2: Qualifier Drop

Field 45A may specify "fresh bananas, USDA grade A." A packing list omits "USDA grade A," describing only "bananas." The bank treats the dropped qualifier as a conflict and rejects under Article 14(d).

Failure Mode 3: Unit or Packaging Drift

The credit specifies "100 cartons of widgets." The commercial invoice states "100 boxes." The examining bank isolates the packaging-term divergence and transmits a discrepancy notice. The substitution is operationally trivial but documentary fatal.

Deterministic Resolution Architecture

1. Compile field 45A as the canonical description before presentation. Every goods description in the set must trace to it. The credit's text is the only binding specification.
2. Isolate divergence at the compilation layer. Flag any document whose goods description conflicts with 45A. This flag is a pre-compiled failure mode that downstream verification cannot repair.
3. Decouple description correction from the examination clock. Correct the description before the presenting bank receives the set. Re-issuance after presentation races a deadline it cannot win.
4. Allow generic, forbid contradictory. A document may use a generic description; it must never state a conflicting one. Train compilers to truncate detail rather than mutate it.

Conclusion

The goods-description inconsistency is a data-consistency boundary problem, not a content problem. UCP 600 Article 14(d) grants no tolerance for variance from field 45A. The moment 45A states the description, consistency becomes a binary condition. Pre-compile the anchor, isolate divergence, and decouple timing — the only regime under which Article 14(d) functions as designed.

FAQ

Q1: Must every document repeat field 45A exactly?
No. A generic description is acceptable. The document must not conflict with 45A — contradiction, not abbreviation, is the failure mode.

Q2: If the invoice matches 45A but the packing list does not, is the set discrepant?
Yes. Each document is measured against 45A. A conflicting packing list is discrepant even if the invoice is perfect.

Q3: Can the applicant waive the description conflict after a discrepancy notice?
The applicant may accept under Article 16, but that is a post-discrepancy remedy. The cost — delayed payment, impaired trust — is already incurred.

Q4: Does a minor grammatical mutation (plural to singular) matter?
Under ISBP 745, yes. The examining bank treats descriptive variance as a discrepancy regardless of materiality.